requested L2 to share the XML with l3 team

Dear Priyasha,
Upon investigation, it was found that the IDUs are being imported into NEP and are reflecting in the Autocreated IDU Report. Please find the attached screenshot for sample node reference.
As discussed, kindly provide the list of IDUs along with their model types from the Autocreated IDU Report that are expected to reflect in the IDU Report.

build 3.7.71.553 is released with added logs to track autocreation of nodes

Please share the logs of 28-01-2026 from BR circle.

Hi Dear,
As observed, the IDU nodes are being configured as auto-created because, during the import process, the slot and board details are missing in the XML. As per the current implementation, when this information is absent, the system applies the default physical configuration, due to which the IDU node is marked as auto-created.
This behaviour was verified for the sample case BHSOZ01-1, which was imported on 28-01-2026. The corresponding XML used for this import is dated 27-01-2026.
Please let us know if further clarification is required.

checking the input shared by L3 team, will update asap

snapshot of sample node attached where its shows that the node was present in slot and board xml still was imported to auto created report please check and share the input.. also let us know how can these ceragon node can be removed from the auto created report , we have already executed the script multiple times. 10.48.171.45_BR sample node

ALSO DO SHARE THE SCRIPT DETAILS HERE IN JIRA FOR FUTURE REFERNECE .

CLOSED