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

        Indrasan Yadav logged work - 29/Sep/25 12:00 AM
        • Time Spent:
          30 minutes
           

          Added a updated connector name in FRS and created a JIRA for same and discussed with Sadnay & Jharna for same.

        Ashutosh Shendye logged work - 30/Sep/25 12:00 AM
        • Time Spent:
          5 hours
           

          Issue fixed and csv shared

        Indrasan Yadav logged work - 03/Oct/25 12:00 AM - edited
        • Time Spent:
          1 hour
           

          Checked for Importer ID/Importer Connector are still missing in all tables in CSV Output files for Nokia RAN. & discussed with Sandya for the same.

        Sandya Sharma logged work - 14/Oct/25 12:00 AM
        • Time Spent:
          6 hours
           

          work on the issue

        Basant Kumar logged work - 16/Oct/25 12:00 AM
        • Time Spent:
          1 hour
           

          I have uploaded the CSV output provided by Sandya and generated the csv2db. After verification, the data is reflecting properly in SD.

        Indrasan Yadav logged work - 22/Oct/25 12:00 AM
        • Time Spent:
          1 hour
           

          Checked the data on staging-DB related to Iporter Connector as CSV Output was shared by Sandhya. and feedback shared over an email.

        Jharna Thakur logged work - 04/Nov/25 12:00 AM
        • Time Spent:
          3 hours
           

          working on importer connector

        Indrasan Yadav logged work - 05/Nov/25 12:00 AM - edited
        • Time Spent:
          3 hours
           

          Validated the tables regarding this issue in staging DB for Nokia RAN and shared feedback over an email.

          Again updated the sheet as suggested by @Bassem and shared over an email.

          Discussed with @Jharna regarding same issue in Huawei RAN to fix this & checked in local CSV Output still issue persist in some tables.

        Jharna Thakur logged work - 05/Nov/25 12:00 AM
        • Time Spent:
          3 hours
           

          working on requirement

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

          Checked importer connector details in each tables for Huawei RAN, and shared feedback to Jharna over an email.

        Indrasan Yadav logged work - 11/Nov/25 12:00 AM
        • Time Spent:
          1 hour
           

          Validated the each tables for Importer Connector and shared feedback to Sandya over an email.

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

          Validated the Importer Connector for Huawei RAN & shared feedback in JIRA OT-85.

        Indrasan Yadav logged work - 13/Nov/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          Checked for Importer Connector issue for Nokia RAN & reverted to Sandya (Validation is based on latest Importer ID-Shared by Basant)

        Basant Kumar logged work - 14/Nov/25 12:00 AM
        • Time Spent:
          1 hour
           

          I have uploaded the CSV output after applying the patch and verified the record counts. The CSV counts before upload and the SD counts after upload are matching correctly for all tables

        Basant Kumar logged work - 17/Nov/25 12:00 AM
        • Time Spent:
          1 hour
           

          shared huweai ran logs from 102 to sandya

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

          Validated the data in staging-DB for connector name.

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

          Validate data on S-DB.

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

          Check & found issue related to importer connector in Huawei RAN which was fixed for all tables almost and raised to Jharna.

        Indrasan Yadav logged work - 07/Jan/26 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          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