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.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 4 hours
-
checked the details of sran alingned them sahred to team
-
- Time Spent:
- 1 day
-
cheked the code for error in enodeb trouble shooting locally requested for xml... discussed with nazih checking with respect to its parent node type
-
- Time Spent:
- 1 day
-
checked the enodeb mention checking related data in db asking for pwrmission to check DB trying to check reports for same ..investigation the enodeb raised problem with checking the error in code
-
- Time Spent:
- 4 hours
-
checking the issue waiting for xml
-
- Time Spent:
- 6 hours
-
checking the issue of enodeb error report
-
- Time Spent:
- 4 hours
-
checked the issue on PROD and local
-
- Time Spent:
- 1 day
-
checked the issue celles not importing checking the cells related parent enodeb and trying to check the error trown in error network report
