L3 Support
  1. L3 Support
  2. LS-804

RU Index Is Correct In Board & Inventory Report But Incorrect In Shelf Report (Huawei RAN)

    Details

    • Customer:
      Ooreedo Tunisia

      Description

      Dear @Khaled Khalil,

      Could you please assign a NEP DEV resource to investigate and resolve the following issue?

      • XML: 2025-12-02-10.22.48_Ooredoo
      • Import Date: 03-12-2025
      • Platform: .102
      • Server Logs: Attached on JIRA

      The RU Index value is being imported correctly from the XML and is displayed properly in both the Board and Inventory reports for the same node (e.g., KEB4042-SRAN Node). However, in the Shelf report, the RU Index value appears as “-1”.

      Please refer to the snippets below for reference:

      Board Report

      Inventory Report

      Shelf Report

      Due to the RU Index issue showing as “-1,” the following pop-up error appears when I attempt to correct the catalogue layout issue. Additionally, there is no “-1” value for the Start RU field under the cabinet in the catalogue.

      Physical Configuration Error Snippet

      Thank you
      Indrasan

        Activity

        Indrasan Yadav logged work - 09/Dec/25 12:00 AM - edited
        • Time Spent:
          3 hours, 30 minutes
           

          Create JIRA for same, before create checked & analysed from my side & troubleshoot then raised to NEP DEV.

        Marwan Kanaan logged work - 15/Dec/25 12:00 AM
        • Time Spent:
          4 hours
           

          checking actual found no issue presist

        Indrasan Yadav logged work - 18/Dec/25 12:00 AM
        • Time Spent:
          2 hours, 30 minutes
           

          Checked & validate the data after given NEP patch deployed and reverted to NEP DEV.

        Indrasan Yadav logged work - 22/Dec/25 12:00 AM - edited
        • Time Spent:
          1 hour, 30 minutes
           

          Marwan discussed over the teams & shared a small XML to import on .102 and check if issue is persist yet, however I check for same and still issue persist. Updated the same to Marwan over teams. Then he suggested to restart the server and check again and now this time issue is fixed based on small XML, Now I will check for full XML & update on same.

        Marwan Kanaan logged work - 22/Dec/25 12:00 AM
        • Time Spent:
          2 hours
           

          fix provided

        Indrasan Yadav logged work - 26/Dec/25 12:00 AM
        • Time Spent:
          2 hours
           

          Worked on same for check & validate the issue.

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
            Rejected By:
            Marwan Kanaan
          • 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 day, 7 hours, 30 minutes
              1d 7h 30m

                Drag and Drop