Details

    • Customer:
      Ooreedo Tunisia

      Description

      Dear @Khaled Khalil,

      Could you please assign a NEP DEV resource to investigate the following issues:

      Case 1 – Error: “The radio antenna already exists”

      (I) Radio antennas are not imported into NEP, although they are present in the XML.
      (II) While troubleshooting in NEP, the error report shows that the radio antenna already exists. However, upon verification, it is not available in NEP, whereas the parent node is present.
      (III) Please find the required snippet for reference (example node: NABF040).

      NEP Error Snippet:

      eNodeB report Snippet:

      Radio Antenna Report:

      XML Snippet:

      Case 2 – Error: “The radio antenna with same ID or name exists”
      (I) Like Case 1, the radio antennas are not imported into NEP but are available in the XML.
      (II) The NEP error report indicates that a radio antenna with the same ID or name already exists, but upon checking, it is not available in NEP, though the parent node is present.

      Error Snippet:

      Radio antenna report snippet:

      SRAN report where node is available

      XML Snippet

      Thank you
      Indrasan

      1. Antenna Already Exist.xlsx
        14 kB
        Indrasan Yadav
      2. HuaweiRanOoredoo_17-09.rar
        23.35 MB
        Indrasan Yadav
      3. Same id or same name exists.xlsx
        251 kB
        Indrasan Yadav
      4. server.tgz
        1.82 MB
      1. eNodeB report_where node is available_Case-1.png
        45 kB
      2. NEP_Error Snippet_Case-1.png
        89 kB
      3. NEP Error report_Case-2.png
        158 kB
      4. radio antenna report_case-2.png
        244 kB
      5. Radio antenna report_where radio antenna NA_Case-1.png
        40 kB
      6. SRAN Report_where node is available_Case-2.png
        43 kB
      7. thumbnail_image.png
        55 kB
      8. XML Snippet_Case-2.png
        30 kB
      9. XML Snippet_Where radio antenna available_Case-1.png
        31 kB

        Activity

        Indrasan Yadav made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2025-09-30 24:00 (milestone: set planned start date to due date)
        Planned End 2025-09-30 24:00 (milestone: set planned end date to due date)
        Indrasan Yadav made changes -
        Indrasan Yadav made changes -
        Description Dear @Khaled Khalil,

        Could you please assign a NEP DEV resource to investigate the following issues:

        Case 1 – Error: “The radio antenna already exists”

        (I) Radio antennas are not imported into NEP, although they are present in the XML.
        (II) While troubleshooting in NEP, the error report shows that the radio antenna already exists. However, upon verification, it is not available in NEP, whereas the parent node is present.
        (III) Please find the required snippet for reference (example node: NABF040).

        NEP Error Snippet:

          

        eNodeB report Snippet:

         

        Radio Antenna Report:

         

        XML Snippet:

         


        Case 2 – Error: “The radio antenna with same ID or name exists”
        (I) Like Case 1, the radio antennas are not imported into NEP but are available in the XML.
        (II) The NEP error report indicates that a radio antenna with the same ID or name already exists, but upon checking, it is not available in NEP, though the parent node is present.

        Error Snippet:

         

        Radio antenna report snippet:

         

        SRAN report where node is available

         

        XML Snippet

         


        Thank you
        Indrasan

        Indrasan Yadav made changes -
        Attachment HuaweiRanOoredoo_17-09.rar [ 117833 ]
        Hassan Abdine made changes -
        Component/s NEP [ 16200 ]
        Indrasan Yadav logged work - 18/Sep/25 12:00 AM - edited
        • Time Spent:
          2 hours
           

          Troubleshoot the issues based on error report and create the JIRA for same and send an email to @Dr. Khaled with all supportive file and snippet.

        Mustapha Al-Hage logged work - 18/Sep/25 12:00 AM
        • Time Spent:
          4 hours
           

          Fixing laptop issues,
          supporting marwan
          checking issue

        made changes -
        Attachment server.tgz [ 117904 ]
        Hassan Abdine made changes -
        Status Open Bug [ 10108 ] Dev Scheduled [ 10014 ]
        Assignee Khaled Khalil [ kkhalil ] Mustapha Al-Hage [ malhage ]
        Indrasan Yadav made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 hour, 30 minutes [ 5400 ]
        Worklog Id 277924 [ 277924 ]
        Indrasan Yadav made changes -
        Baseline Start 2025-09-30 24:00 (set baseline based of initial work logging)
        Baseline End 2025-09-30 24:00 (set baseline based of initial work logging)
        Indrasan Yadav made changes -
        Time Spent 1 hour, 30 minutes [ 5400 ] 2 hours [ 7200 ]
        Worklog Id 277924 [ 277924 ]
        Mustapha Al-Hage logged work - 19/Sep/25 12:00 AM
        • Time Spent:
          5 hours
           

          Exploring XML file, error report and debugging

        Mustapha Al-Hage made changes -
        Status Dev Scheduled [ 10014 ] Implementation in progress [ 10016 ]
        Hide
        Mustapha Al-Hage added a comment -

        Dear @Indrasan Yadav,

        After exploring the error report and the XML file, we have found the following:

        If we take the radio antenna with name "RRU60RET3500" and objectid "NABF040_Antenna_0" , we find that there is a duplication on the name as shown in the snippet below:

        This is causing both errors:

        “The radio antenna already exists”

        “The radio antenna with same ID or name exists”

        However, the name was not mentioned in the error report; it has now been added. A patch is required: 3.7.0.1350

        Regards,

        Mustapha

        Show
        Mustapha Al-Hage added a comment - Dear @Indrasan Yadav, After exploring the error report and the XML file, we have found the following: If we take the radio antenna with name "RRU60RET3500" and objectid "NABF040_Antenna_0" , we find that there is a duplication on the name as shown in the snippet below: This is causing both errors: “The radio antenna already exists” “The radio antenna with same ID or name exists” However, the name was not mentioned in the error report; it has now been added. A patch is required: 3.7.0.1350 Regards, Mustapha
        Mustapha Al-Hage made changes -
        Status Implementation in progress [ 10016 ] Rejected [ 10100 ]
        Assignee Mustapha Al-Hage [ malhage ] Indrasan Yadav [ iyadav ]
        Resolution Done [ 10000 ]
        Mustapha Al-Hage made changes -
        Attachment thumbnail_image.png [ 118014 ]
        Mustapha Al-Hage made changes -
        Time Spent 2 hours [ 7200 ] 7 hours [ 25200 ]
        Worklog Id 278033 [ 278033 ]
        Mustapha Al-Hage made changes -
        Time Spent 7 hours [ 25200 ] 1 day, 3 hours [ 39600 ]
        Worklog Id 278034 [ 278034 ]
        Indrasan Yadav logged work - 22/Sep/25 12:00 AM - edited
        • Time Spent:
          30 minutes
           

          Checked for same and requested to @Integration to deploy the given patch on .102. and taken a call with @Mustapha for all raised issues and discussed for the same

        Indrasan Yadav made changes -
        Time Spent 1 day, 3 hours [ 39600 ] 1 day, 3 hours, 30 minutes [ 41400 ]
        Worklog Id 278120 [ 278120 ]
        Indrasan Yadav made changes -
        Worklog Id 278120 [ 278120 ]
        Indrasan Yadav logged work - 25/Sep/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          Antenna was not imported due to already existing antenna in NEP the reason was name duplicate. So deleted all existing nodes from NEP & reimported the same XML then validated for same issue, now issue has been fixed.

        Indrasan Yadav made changes -
        Resolution Done [ 10000 ] Not Fixed [ 10200 ]
        Status Rejected [ 10100 ] Reopened [ 4 ]
        Hide
        Indrasan Yadav added a comment -

        Dear @Mustapha Al-Hage,

        Thank you for your support.

        All radio antennas have now been successfully imported in NEP after deploying the provided patch.

        Thank you
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @Mustapha Al-Hage, Thank you for your support. All radio antennas have now been successfully imported in NEP after deploying the provided patch. Thank you Indrasan
        Indrasan Yadav made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Not Fixed [ 10200 ] Fixed [ 1 ]
        Indrasan Yadav made changes -
        Time Spent 1 day, 3 hours, 30 minutes [ 41400 ] 1 day, 5 hours [ 46800 ]
        Worklog Id 278680 [ 278680 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Bug Open Bug Dev Scheduled Dev Scheduled
        17h 25m 1 Hassan Abdine 18/Sep/25 6:57 AM
        Dev Scheduled Dev Scheduled Implementation in progress Implementation in progress
        1d 3h 58m 1 Mustapha Al-Hage 19/Sep/25 10:56 AM
        Implementation in progress Implementation in progress Rejected Rejected
        31m 58s 1 Mustapha Al-Hage 19/Sep/25 11:28 AM
        Rejected Rejected Reopened Reopened
        6d 16h 52m 1 Indrasan Yadav 26/Sep/25 4:21 AM
        Reopened Reopened Closed Closed
        43s 1 Indrasan Yadav 26/Sep/25 4:22 AM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
            Rejected By:
            Mustapha Al-Hage
          • Votes:
            0 Vote for this issue
            Watchers:
            2 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 day, 5 hours
              1d 5h

                Drag and Drop