Details

    • Customer:
      Ooreedo Tunisia

      Description

      Dear All,

      As discussed, the connector names need to be parsed exactly as defined in the FRS, and they should remain unique per project for both Nokia_RAN and Huawei_RAN.

      I have updated the FRS accordingly, and the finalized connector names are as follows (Which is generally parse under header “importerConnector”):

      • Huawei RAN: Huawei_RAN_Ooredoo_TUN
      • Nokia RAN: NSN_RAN_Ooredoo_TUN

      Currently, it is parsing as below:

      Huawei RAN: Huawei_M2000 (Snippet attached)
      Nokia RAN: Header is missing

      @Bassem Sabbagh, please advise if these names need to be revised and guide us further on this.

      Best regards,
      Indrasan

      1. csv-output_huawei-ran.rar
        10.51 MB
        Ashutosh Shendye
      2. csv-output_nsn-ran.rar
        4.72 MB
        Ashutosh Shendye
      3. OT_Huawei_RAN All Nodes_Physical.docx
        1.47 MB
        Indrasan Yadav
      4. OT_NSN_RAN_FRS_All Node Type_Physical.docx
        1.81 MB
        Indrasan Yadav
      5. OT-83 (Nokia RAN).xlsx
        11 kB
        Indrasan Yadav
      1. Huawei RAN_Connector Name.png
        42 kB

        Activity

        Hide
        Indrasan Yadav added a comment - - edited

        Hi Jharna Thakur please commit the code for connector name missing issue in Huawei RAN for table "Sub interface" as it is fixed now withing OT-45 CSV output.

        Show
        Indrasan Yadav added a comment - - edited Hi Jharna Thakur please commit the code for connector name missing issue in Huawei RAN for table "Sub interface" as it is fixed now withing OT-45 CSV output.
        Hide
        Indrasan Yadav added a comment - - edited

        Hi Jharna,

        The issue was initially identified in the Sub Interface table, where the importer connector was missing. You had fixed this earlier. However, while validating the latest data on the server using the importer ID 20251231015405_2025-12-31-01.54.05 (shared by Basant on 31-12-2025), I noticed that the importer connector issue is now appearing in additional tables as well either it is missing or incorrect 'Huawei_M2000'.

        The following tables are affected, even though they were previously fixed (except for Sub Interface):

        1- BATCH_ELEMENT_CELL_RADIO_BAND_WIDTH
        2- BATCH_ELEMENT_GSM_CELL_MAIO
        3- BATCH_ELEMENT_TRX
        4- BATCH_ELEMENT_TRX_ARFCN
        5- BATCH_IP_DATA
        6- BATCH_LOGICAL_INTERFACE
        7- BATCH_NETWORK_ELEMENT_DUMP
        8- BATCH_NODE_INTERFACE
        9- BATCH_RADIO_ANTENNA
        10- BATCH_SUB_INTERFACE
        11- BATCH_VIRTUAL_INTERFACE

        Kindly review and fix the importer connector issue for the above tables as well.

        Show
        Indrasan Yadav added a comment - - edited Hi Jharna, The issue was initially identified in the Sub Interface table, where the importer connector was missing. You had fixed this earlier. However, while validating the latest data on the server using the importer ID 20251231015405_2025-12-31-01.54.05 (shared by Basant on 31-12-2025), I noticed that the importer connector issue is now appearing in additional tables as well either it is missing or incorrect 'Huawei_M2000'. The following tables are affected, even though they were previously fixed (except for Sub Interface): 1- BATCH_ELEMENT_CELL_RADIO_BAND_WIDTH 2- BATCH_ELEMENT_GSM_CELL_MAIO 3- BATCH_ELEMENT_TRX 4- BATCH_ELEMENT_TRX_ARFCN 5- BATCH_IP_DATA 6- BATCH_LOGICAL_INTERFACE 7- BATCH_NETWORK_ELEMENT_DUMP 8- BATCH_NODE_INTERFACE 9- BATCH_RADIO_ANTENNA 10- BATCH_SUB_INTERFACE 11- BATCH_VIRTUAL_INTERFACE Kindly review and fix the importer connector issue for the above tables as well.
        Hide
        Bassem Sabbagh added a comment -

        XML and CSVs are generated with no issues on local laptop of Jharna ... it could be integration issue ... L2 to generate again the XML and share it for validation ...

        Show
        Bassem Sabbagh added a comment - XML and CSVs are generated with no issues on local laptop of Jharna ... it could be integration issue ... L2 to generate again the XML and share it for validation ...
        Hide
        Jharna Thakur added a comment -

        I have checked the staging database and the issues have now been resolved.
        Previously, the Omantel connector was executed instead of the Ooredoo Huawei RAN connector, which caused the discrepancy. This has been corrected.

        Show
        Jharna Thakur added a comment - I have checked the staging database and the issues have now been resolved. Previously, the Omantel connector was executed instead of the Ooredoo Huawei RAN connector, which caused the discrepancy. This has been corrected.
        Hide
        Indrasan Yadav added a comment -

        Now, issue has been fixed for both connector Nokia RAN (Already fixed earlier) & Huawei RAN (Now fixed):

        Connector name is parsing OK in all possible tables except below which can be ignored:
        (II) Site
        (III) Error alarm

        2- Huawei RAN:

        Connector name is parsing OK in all possible tables except below:
        (II) Site
        (III) Error alarm

        Show
        Indrasan Yadav added a comment - Now, issue has been fixed for both connector Nokia RAN (Already fixed earlier) & Huawei RAN (Now fixed): Connector name is parsing OK in all possible tables except below which can be ignored: (II) Site (III) Error alarm 2- Huawei RAN: Connector name is parsing OK in all possible tables except below: (II) Site (III) Error alarm

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

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

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 4 days, 5 hours, 30 minutes
              4d 5h 30m