[LS-867] MW Nodes Not Parsing in NEP IDU Report Created: 16/Dec/25  Updated: 10/Mar/26  Due: 12/Jan/26  Resolved: 27/Feb/26

Status: Closed
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Priyasha Tiwari Assignee: Srishti Kashyap
Resolution: Fixed Votes: 0
Labels: NEP_D
Remaining Estimate: 0 minutes
Time Spent: 1 week, 3 days, 4 hours, 30 minutes
Original Estimate: Not Specified

Attachments: Text File 15012026_changefromautocreationtonormalscript..txt     PNG File LS-867 REPORT.png     PNG File MW NODE ERROR SS.png     PNG File MW NODE NEP IDU REPORT.png     PNG File MW NODE XML SNAPSHOT.png     PNG File Screenshot 2026-01-13 174901.png     PNG File XML SS LS-867.png    
Customer:
Airtel India
Planned Start:
Planned End:
Classification: Query
Actual Start:
Date of Baselining:

 Description   

MW nodes with node types IP-20C, IP-20G, and IP-20GX are present in the XML but are not parsing into NEP.
Sample node 10.64.85.20_BR, no error for this node in error report .

 Comments   
Comment by Priyasha Tiwari [ 08/Jan/26 ]

requested L2 to share the XML with l3 team

Comment by Srishti Kashyap [ 09/Jan/26 ]

received sample xml doesnt have sample node consist RJ node. Please reshare correct one

Comment by Srishti Kashyap [ 13/Jan/26 ]

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.

Comment by Srishti Kashyap [ 27/Jan/26 ]

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

Comment by Srishti Kashyap [ 30/Jan/26 ]

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

Comment by Anonymous [ 03/Feb/26 ]

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.

Comment by Priyasha Tiwari [ 05/Feb/26 ]

checking the input shared by L3 team, will update asap

Comment by Priyasha Tiwari [ 09/Feb/26 ]

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

Comment by Priyasha Tiwari [ 09/Feb/26 ]

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

Comment by Priyasha Tiwari [ 27/Feb/26 ]

CLOSED

Generated at Fri Apr 17 12:10:42 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.