Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Resolution: Fixed
-
Component/s: None
-
Customer:Airtel India
-
Severity:Critical
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.
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.