Details

    • Customer:
      Zain KSA 3.X

      Description

      Click to add description

      Issue Links

        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 2024-12-09 24:00 (milestone: set planned start date to due date)
        Planned End 2024-12-09 24:00 (milestone: set planned end date to due date)
        Indrasan Yadav made changes -
        Summary Nodes Not Imported In NEP_Huawei Nodes Are Not Imported In NEP_Huawei
        Hide
        Indrasan Yadav added a comment -

        Dear @Khaled Khalil,

        I hope this email finds you well.

        I kindly request your support in assigning a DEV resource to investigate an issue where certain nodes are not being imported into NEP. Below are the details for your reference:

        • Number of nodes not imported: 11
        • Environment: NEP (.14)
        • Imported XML: 2024-11-22-10.34.50_ZainKsa

        Node Id
        MDN2996-MMM-P1-VIP_SRAN
        MDN0143-P2_SRAN
        ARR0519-P1-HUB_SRAN-FON
        RIY2927-NNN_SRAN
        RIY2708-VIP-P1_SRAN-DIS
        FQR0998-P2_SRAN
        MDN0244-FWA-P1-VIP_SRAN
        BUR0979-P2_SRAN
        MDN0180-FWA-P1-VIP_SRAN
        MDN2879-P2_SRAN
        YNB0655-P1-HUB-WDM_SRAN

        Upon checking, the error log only indicates that the nodes are missing under the "Missing Node" category.

        Could you please prioritize this and assign a resource to investigate the issue? Let me know if you need any additional information.

        Thank you for your assistance.

        Best regards,
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @Khaled Khalil, I hope this email finds you well. I kindly request your support in assigning a DEV resource to investigate an issue where certain nodes are not being imported into NEP. Below are the details for your reference: • Number of nodes not imported: 11 • Environment: NEP (.14) • Imported XML: 2024-11-22-10.34.50_ZainKsa Node Id MDN2996-MMM-P1-VIP_SRAN MDN0143-P2_SRAN ARR0519-P1-HUB_SRAN-FON RIY2927-NNN_SRAN RIY2708-VIP-P1_SRAN-DIS FQR0998-P2_SRAN MDN0244-FWA-P1-VIP_SRAN BUR0979-P2_SRAN MDN0180-FWA-P1-VIP_SRAN MDN2879-P2_SRAN YNB0655-P1-HUB-WDM_SRAN Upon checking, the error log only indicates that the nodes are missing under the "Missing Node" category. Could you please prioritize this and assign a resource to investigate the issue? Let me know if you need any additional information. Thank you for your assistance. Best regards, Indrasan
        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Khaled Khalil [ kkhalil ]
        Khaled Khalil made changes -
        Assignee Khaled Khalil [ kkhalil ] Diana Hamdouche [ dhamdouche ]
        Diana Hamdouche made changes -
        Assignee Diana Hamdouche [ dhamdouche ] Mustapha Al-Hage [ malhage ]
        Mustapha Al-Hage logged work - 06/Dec/24 12:00 AM
        • Time Spent:
          4 hours
           

          .

        Hide
        Mustapha Al-Hage added a comment -

        Dear @Indrasan Yadav,

        After reviewing the XML and the error report, I have found the following :
        1. The nodes “FQR0998-P2_SRAN”, “ARR0519-P1-HUB_SRAN-FON” and “BUR0979-P2_SRAN” are imported into NEP with no issues.

        2. The node “RIY2708-VIP-P1_SRAN-DIS” is not being imported, because in the XML, its associated Role2G “RIY2M2927 “ is occurring twice as shown in the snippets.

        This duplication is causing the error “BTS: RUM2M2708-P3 missing data... BTS with the same object id or name exists.: RUM2M2708-P3/ RUM2M2708-P3 “ to appear in the error report.

        Note that the nodes “MDN2996-MMM-P1-VIP_SRAN”, “RIY2927-NNN_SRAN “ and “YNB0655-P1-HUB-WDM_SRAN” all have the same problem as “RIY2708-VIP-P1_SRAN-DIS”.

        3. The node “MDN0180-FWA-P1-VIP_SRAN” is not being imported, because in the XML, its associated Role2G “RIY2M2927 “ is occurring twice as shown in the snippets.

        his duplication is causing the error “BTS: RUM2M2708-P3 missing data... BTS with the same object id or name exists.: RUM2M2708-P3/ RUM2M2708-P3 “ to appear in the error report:

        Note that the nodes “MDN2M1143-P2-SRAN” and “MDN0244-FWA-P1-VIP_SRAN” and “MDN2879-P2_SRAN” have the same problem in XML as “MDN0180-FWA-P1-VIP_SRAN”.

        Note that I have also attached an excel file containing the error messages in the error report for each node.

        In conclusion, the nodes were not imported because in the XML we have duplicated role2g and role3g values.

        Regards,
        Mustapha Al Hage

        Show
        Mustapha Al-Hage added a comment - Dear @Indrasan Yadav, After reviewing the XML and the error report, I have found the following : 1. The nodes “FQR0998-P2_SRAN”, “ARR0519-P1-HUB_SRAN-FON” and “BUR0979-P2_SRAN” are imported into NEP with no issues. 2. The node “RIY2708-VIP-P1_SRAN-DIS” is not being imported, because in the XML, its associated Role2G “RIY2M2927 “ is occurring twice as shown in the snippets. This duplication is causing the error “BTS: RUM2M2708-P3 missing data... BTS with the same object id or name exists.: RUM2M2708-P3/ RUM2M2708-P3 “ to appear in the error report. Note that the nodes “MDN2996-MMM-P1-VIP_SRAN”, “RIY2927-NNN_SRAN “ and “YNB0655-P1-HUB-WDM_SRAN” all have the same problem as “RIY2708-VIP-P1_SRAN-DIS”. 3. The node “MDN0180-FWA-P1-VIP_SRAN” is not being imported, because in the XML, its associated Role2G “RIY2M2927 “ is occurring twice as shown in the snippets. his duplication is causing the error “BTS: RUM2M2708-P3 missing data... BTS with the same object id or name exists.: RUM2M2708-P3/ RUM2M2708-P3 “ to appear in the error report: Note that the nodes “MDN2M1143-P2-SRAN” and “MDN0244-FWA-P1-VIP_SRAN” and “MDN2879-P2_SRAN” have the same problem in XML as “MDN0180-FWA-P1-VIP_SRAN”. Note that I have also attached an excel file containing the error messages in the error report for each node. In conclusion, the nodes were not imported because in the XML we have duplicated role2g and role3g values. Regards, Mustapha Al Hage
        Mustapha Al-Hage made changes -
        Mustapha Al-Hage made changes -
        Attachment SRANBSNODES_NOT_IMPORTED_ERRORS.xlsx [ 103397 ]
        Mustapha Al-Hage made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 4 hours [ 14400 ]
        Worklog Id 257991 [ 257991 ]
        Mustapha Al-Hage made changes -
        Baseline Start 2024-12-09 24:00 (set baseline based of initial work logging)
        Baseline End 2024-12-09 24:00 (set baseline based of initial work logging)
        Mustapha Al-Hage made changes -
        Assignee Mustapha Al-Hage [ malhage ] Indrasan Yadav [ iyadav ]
        Hide
        Indrasan Yadav added a comment -

        Dear Team,

        I would like to inform you that, as part of my investigation and validation process, I have identified an issue regarding the data commented on by @Mustapha Al-Hage.

        The nodes in question are duplicates in the dump, differing only by node ID. Almost all the data, including physical serial numbers, are identical.

        For your reference, I am sharing the following examples:
        • Role2G Snippet:

        • Role3G Snippet:

        • Role4G Snippet:

        Example 1:
        The nodes SRANBs node MDN2996-P1-VIP_SRAN and MDN2996-MMM-P1-VIP_SRAN contain similar data, with only the node ID differing. Both nodes have the same Role2G node, MDN2C2996-MMM-P1-VIP. This Role2G (MDN2C2996-MMM-P1-VIP) is imported in NEP with the SRANBs node MDN2996-P1-VIP_SRAN. As a result, NEP is ignoring the second SRAN node, MDN2996-MMM-P1-VIP_SRAN.

        Please provide your suggestions regarding this issue, as we need to keep in out tracker or need to discuss with customer?

        Br//
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear Team, I would like to inform you that, as part of my investigation and validation process, I have identified an issue regarding the data commented on by @Mustapha Al-Hage. The nodes in question are duplicates in the dump, differing only by node ID. Almost all the data, including physical serial numbers, are identical. For your reference, I am sharing the following examples: • Role2G Snippet: • Role3G Snippet: • Role4G Snippet: Example 1: The nodes SRANBs node MDN2996-P1-VIP_SRAN and MDN2996-MMM-P1-VIP_SRAN contain similar data, with only the node ID differing. Both nodes have the same Role2G node, MDN2C2996-MMM-P1-VIP. This Role2G (MDN2C2996-MMM-P1-VIP) is imported in NEP with the SRANBs node MDN2996-P1-VIP_SRAN. As a result, NEP is ignoring the second SRAN node, MDN2996-MMM-P1-VIP_SRAN. Please provide your suggestions regarding this issue, as we need to keep in out tracker or need to discuss with customer? Br// Indrasan
        Hide
        Indrasan Yadav added a comment -

        From: Bassem Sabbagh <bassem.sabbagh@mobinets.com>
        Sent: 09 December 2024 17:54
        To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
        Cc: Navneet Kaur <Navneet.Kaur@nuiva.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Diana Hamdouche <Diana.Hamdouche@nuiva.com>; Mustapha Al-Hage <Mustapha.AlHage@nuiva.com>
        Subject: RE: Nodes Are Not Imported In NEP_Huawei || ZKU-196 ||

        Dear Ahad/Indrasan,

        It is your call… Hence, conclude it and let me know what your decision is.

        Thanks

        Show
        Indrasan Yadav added a comment - From: Bassem Sabbagh <bassem.sabbagh@mobinets.com> Sent: 09 December 2024 17:54 To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com> Cc: Navneet Kaur <Navneet.Kaur@nuiva.com>; Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Diana Hamdouche <Diana.Hamdouche@nuiva.com>; Mustapha Al-Hage <Mustapha.AlHage@nuiva.com> Subject: RE: Nodes Are Not Imported In NEP_Huawei || ZKU-196 || Dear Ahad/Indrasan, It is your call… Hence, conclude it and let me know what your decision is. Thanks
        Hide
        Indrasan Yadav added a comment -

        From: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>
        Sent: 09 December 2024 18:19
        To: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Navneet Kaur <Navneet.Kaur@mobinets.com>
        Cc: Navneet Kaur <Navneet.Kaur@nuiva.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Diana Hamdouche <Diana.Hamdouche@nuiva.com>; Mustapha Al-Hage <Mustapha.AlHage@nuiva.com>
        Subject: RE: Nodes Are Not Imported In NEP_Huawei || ZKU-196 ||

        Hi Indrasan,

        Can you check the Nestatus in dumps for both , if anyone is offline while other is online.

        Regards,
        Ahad Siddiqui

        Show
        Indrasan Yadav added a comment - From: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com> Sent: 09 December 2024 18:19 To: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Navneet Kaur <Navneet.Kaur@mobinets.com> Cc: Navneet Kaur <Navneet.Kaur@nuiva.com>; Khaled Khalil <Khaled.Khalil@nuiva.com>; Diana Hamdouche <Diana.Hamdouche@nuiva.com>; Mustapha Al-Hage <Mustapha.AlHage@nuiva.com> Subject: RE: Nodes Are Not Imported In NEP_Huawei || ZKU-196 || Hi Indrasan, Can you check the Nestatus in dumps for both , if anyone is offline while other is online. Regards, Ahad Siddiqui
        Hide
        Indrasan Yadav added a comment -

        Dear @Ahad Siddiqui,

        Each dump has Nestatus “Online” please find below dump snippet (MDN2996-P1-VIP_SRAN & MDN2996-MMM-P1-VIP_SRAN) for reference.

        Thanks//
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @Ahad Siddiqui, Each dump has Nestatus “Online” please find below dump snippet (MDN2996-P1-VIP_SRAN & MDN2996-MMM-P1-VIP_SRAN) for reference. Thanks// Indrasan
        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Ahad Siddiqui [ asiddiqui ]
        Hide
        Ahad Siddiqui added a comment -

        @indrasan : I think same thing happeining in OT and we are taking only one node in code ?

        Show
        Ahad Siddiqui added a comment - @indrasan : I think same thing happeining in OT and we are taking only one node in code ?
        Ahad Siddiqui made changes -
        Assignee Ahad Siddiqui [ asiddiqui ] Indrasan Yadav [ iyadav ]
        Hide
        Indrasan Yadav added a comment -

        Dear @Hassan Abdine,

        Could you please suggest about the same for below comment?

        Dear Team,

        I would like to inform you that, as part of my investigation and validation process, I have identified an issue regarding the data commented on by @Mustapha Al-Hage.

        The nodes in question are duplicates in the dump, differing only by node ID. Almost all the data, including physical serial numbers, are identical.

        For your reference, I am sharing the following examples:
        • Role2G Snippet:

        • Role3G Snippet:

        • Role4G Snippet:

        Example 1:
        The nodes SRANBs node MDN2996-P1-VIP_SRAN and MDN2996-MMM-P1-VIP_SRAN contain similar data, with only the node ID differing. Both nodes have the same Role2G node, MDN2C2996-MMM-P1-VIP. This Role2G (MDN2C2996-MMM-P1-VIP) is imported in NEP with the SRANBs node MDN2996-P1-VIP_SRAN. As a result, NEP is ignoring the second SRAN node, MDN2996-MMM-P1-VIP_SRAN.

        Please provide your suggestions regarding this issue, as we need to keep in out tracker or need to discuss with customer?

        Br//
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @Hassan Abdine, Could you please suggest about the same for below comment? Dear Team, I would like to inform you that, as part of my investigation and validation process, I have identified an issue regarding the data commented on by @Mustapha Al-Hage. The nodes in question are duplicates in the dump, differing only by node ID. Almost all the data, including physical serial numbers, are identical. For your reference, I am sharing the following examples: • Role2G Snippet: • Role3G Snippet: • Role4G Snippet: Example 1: The nodes SRANBs node MDN2996-P1-VIP_SRAN and MDN2996-MMM-P1-VIP_SRAN contain similar data, with only the node ID differing. Both nodes have the same Role2G node, MDN2C2996-MMM-P1-VIP. This Role2G (MDN2C2996-MMM-P1-VIP) is imported in NEP with the SRANBs node MDN2996-P1-VIP_SRAN. As a result, NEP is ignoring the second SRAN node, MDN2996-MMM-P1-VIP_SRAN. Please provide your suggestions regarding this issue, as we need to keep in out tracker or need to discuss with customer? Br// Indrasan
        Indrasan Yadav made changes -
        Assignee Indrasan Yadav [ iyadav ] Hassan Abdine [ habdine ]
        Indrasan Yadav made changes -
        Link This issue blocks ZKU-94 [ ZKU-94 ]
        Hide
        Indrasan Yadav added a comment -

        We can close this as separate JIRA ZKU-234 is created after customer confirmation.

        Show
        Indrasan Yadav added a comment - We can close this as separate JIRA ZKU-234 is created after customer confirmation.
        Indrasan Yadav made changes -
        Status To Do [ 10001 ] Done [ 10000 ]
        Indrasan Yadav made changes -
        Assignee Hassan Abdine [ habdine ] Indrasan Yadav [ iyadav ]
        Indrasan Yadav logged work - 23/Jan/25 12:00 AM
        • Time Spent:
          5 hours
           

          Worked on latest dump to check still duplicate child in different node is finding or not? and find that it is still available.

        Indrasan Yadav logged work - 24/Jan/25 12:00 AM
        • Time Spent:
          6 hours, 30 minutes
           

          Worked on latest dump & latest XML to check regarding duplicate child node in different nodes.

        Indrasan Yadav made changes -
        Time Spent 4 hours [ 14400 ] 1 day, 1 hour [ 32400 ]
        Worklog Id 259458 [ 259458 ]
        Indrasan Yadav made changes -
        Time Spent 1 day, 1 hour [ 32400 ] 1 day, 7 hours, 30 minutes [ 55800 ]
        Worklog Id 259461 [ 259461 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        To Do To Do Done Done
        35d 18h 43m 1 Indrasan Yadav 07/Jan/25 9:22 AM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

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

            Dates

            • Due:
              Created:
              Updated:
              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