[LS-302] Parent EnodeB mapping issue causing XML data to not parse in NEP Created: 11/Mar/25  Updated: 14/Apr/25  Due: 13/Mar/25  Resolved: 14/Apr/25

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

Type: Bug
Reporter: Priyasha Tiwari Assignee: Priyasha Tiwari
Resolution: Fixed Votes: 0
Labels: L3
Remaining Estimate: 0 minutes
Time Spent: 1 week, 2 hours
Original Estimate: Not Specified

Attachments: Microsoft Excel MH cell list.xlsx     PNG File Screenshot 2025-03-12 152147.png     PNG File Screenshot 2025-03-21 110128.png     PNG File image (13).png     PNG File image (14).png     PNG File image (15).png     PNG File image (16).png     PNG File pic.png    
Customer:
Airtel India
Planned Start:
Planned End:
Severity: Critical
Actual Start:
Date of Baselining:

 Description   

Hi Srishti,

Around 150 cells are stuck in error and are not being parsed in NEP because their parent EnodeB is not found, as reflected in the error snapshot.

In the MH circle CSV, I can see a code in the EnodeB column data, which is also present in the Prod XML. Ideally, these cells should not be stuck in error—please check.
This is a recurring issue and I have encountered this issue in multiple circles, but for now I am sharing the data only for MH Circle.

This issue also gets resolved automatically if we check the same cell after a few weeks, We need to perform an RCA for this as well.

 Comments   
Comment by Srishti Kashyap [ 11/Mar/25 ]

Hi Dear
I checked the issue of trailing mail. I found its not to be an issue as the cell which are not importing doesn’t have there parent enodeb imported in NEP. Also as checked in network error report there are error corresponding to parent Enodeb.
Checked for the cell :976420-7_MH_ZQ_F1_OM_NDG6420B_B with parent enodeb :LNBTS-976420.
SS attached for your reference.

Comment by Srishti Kashyap [ 12/Mar/25 ]

Hi Dear
As checked the shared error is coming from errorAlarms in XML indicating missing data with respect to enodeb. Kindly check the xml ss attched

Comment by Basant Kumar [ 18/Mar/25 ]

https://mobinets-my.sharepoint.com/:u:/g/personal/basant_kumar_nuiva_com/EVewJPiVcbtGoExkoz2ypLsBF_Y5OZlM2mYGpTPjMBRBvQ?e=6ue2Xg

Comment by Srishti Kashyap [ 20/Mar/25 ]

Need a small size xml containing the sample enodebs not importing.

Comment by Srishti Kashyap [ 21/Mar/25 ]

Following the investigation regarding the issue you shared, we found the following:
• The shared eNodeB sample is of type role4g, with its parent type being SRANBS.
• Upon further review, it was found that the parent SRANBS node is not being imported due to an existing BTS type or role already present in NEP. Please refer to the attached screenshot for more details.
As a result, the parent SRANBS is not imported, which consequently prevents the related role4g (eNodeB) from being imported as well.

Generated at Wed Apr 15 11:04:02 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.