L3 Support
  1. L3 Support
  2. LS-302

Parent EnodeB mapping issue causing XML data to not parse in NEP

        Details

        • 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.

          1. Microsoft Excel
            MH cell list.xlsx
            18 kB
            Priyasha Tiwari
          1. image (13).png
            38 kB
          2. image (14).png
            26 kB
          3. image (15).png
            26 kB
          4. image (16).png
            74 kB
          5. pic.png
            35 kB
          6. Screenshot 2025-03-12 152147.png
            25 kB
          7. Screenshot 2025-03-21 110128.png
            59 kB

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            Srishti Kashyap added a comment -

            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.

            Show
            Srishti Kashyap added a comment - 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.
            Hide
            Permalink
            Srishti Kashyap added a comment -

            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

            Show
            Srishti Kashyap added a comment - 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
            Hide
            Permalink
            Basant Kumar added a comment -

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

            Show
            Basant Kumar added a comment - https://mobinets-my.sharepoint.com/:u:/g/personal/basant_kumar_nuiva_com/EVewJPiVcbtGoExkoz2ypLsBF_Y5OZlM2mYGpTPjMBRBvQ?e=6ue2Xg
            Hide
            Permalink
            Srishti Kashyap added a comment -

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

            Show
            Srishti Kashyap added a comment - Need a small size xml containing the sample enodebs not importing.
            Hide
            Permalink
            Srishti Kashyap added a comment -

            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.

            Show
            Srishti Kashyap added a comment - 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.
            Cancel

              People

              • Assignee:
                Priyasha Tiwari
                Reporter:
                Priyasha Tiwari
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved:
                  Planned Start:
                  Planned End:
                  Actual Start:
                  Date of Baselining:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week, 2 hours
                  1w 2h

                    Drag and Drop