Details

    • Customer:
      OMAN-Tel
    • Complexity:
      High
    • Severity:
      Major
    • REQUESTER:
      INTERNAL

      Description

      It is found that In NEP RAN Logical Interface report for SRAN, the Port IP details are missing for few Interfaces of RAN node. The IPs used in addinfo are available in NEP IP data report for the RAN nodes.

      and IP 10.238.24.60 available in addinfo and IP data is missing in RAN logical interface report at all.

      Details are attached as SS.

      Sample NE: LM05500 ( Parent Node BM05500)

      XML and Server logs are also attached.

      This issue has been observed in PRODCUTION ACTUAL Version

      Serverlink
      https://mobinets-my.sharepoint.com/:f:/p/mohan_rathor/Ei75Y2a9jQlFoiXyRhvufrgB2f9qN-keUMqERzXtJyfyGA?e=WTZ6GX
      Dear @Khaled Khalil,

      Please assign a resource to check for below issue.

      It is found that there are blank PORT details for RAN nodes for SI-U and SI-MME.

      As checked the required IPs are available in NEP IP data as well as Addinfo.

      This is causing “Missing RAN Port @source” error in RB report.

      I have attached the required SS, XML and Server logs in JIRA.

        Activity

        Hide
        Abir Messaikeh added a comment -

        this was raised after the analysis of failure reason " missing source @port" for 4G ones

        Show
        Abir Messaikeh added a comment - this was raised after the analysis of failure reason " missing source @port" for 4G ones
        Hide
        Nouha Mhadhbi added a comment -

        After investigation, we found that the interfaces were not created due to duplicate IPs, and some local IPs are associated with more than one remote IP also there's ip conflict issue.
        Please find below a snapshot of the error report.
        Best regards,
        Nouha

        Full message is:[NE: BM05500] [Subinterface: SFP 0/0/7/0/1.4]
        IP already in used : [ 10.238.24.60 ] for NE [ BM05500 ] of type [ SRanBs ] on
        Interface [ SFP 0/0/7/0/1.4] by Conflict NE [ BM05500 ] of Conflict type [
        SRanBs ] on Conflict Interface [ SFP 0/0/7/0/1.5 ]

        Show
        Nouha Mhadhbi added a comment - After investigation, we found that the interfaces were not created due to duplicate IPs, and some local IPs are associated with more than one remote IP also there's ip conflict issue. Please find below a snapshot of the error report. Best regards, Nouha Full message is: [NE: BM05500] [Subinterface: SFP 0/0/7/0/1.4] IP already in used : [ 10.238.24.60 ] for NE [ BM05500 ] of type [ SRanBs ] on Interface [ SFP 0/0/7/0/1.4] by Conflict NE [ BM05500 ] of Conflict type [ SRanBs ] on Conflict Interface [ SFP 0/0/7/0/1.5 ]
        Hide
        Aurobinda Panda added a comment -

        As checked, there is only one Interface available in NEP for the IP. Though in XML the subinterface 4 has this IP. So, NEP should change the Interface from subinterface 5 to subinterface 4 and create the logical RAN Interfaces accordingly.

        Show
        Aurobinda Panda added a comment - As checked, there is only one Interface available in NEP for the IP. Though in XML the subinterface 4 has this IP. So, NEP should change the Interface from subinterface 5 to subinterface 4 and create the logical RAN Interfaces accordingly.
        Hide
        Mustapha Al-Hage added a comment -

        Dear @Aurobinda Panda,

        I was checking the NEP production "Actual Network" version and found that the issue has been resolved, as shown in the following snippets:

        IP address "10.238.24.60" was assigned to subinterface "SFP 0/0/7/0/1.4"

        Ip address "10.238.24.60" in interface SranBs report:

        Please confirm whether the issue has been resolved. If it has, kindly close the ticket.

        Regards,
        Mustapha Al Hage

        Show
        Mustapha Al-Hage added a comment - Dear @Aurobinda Panda, I was checking the NEP production "Actual Network" version and found that the issue has been resolved, as shown in the following snippets: IP address "10.238.24.60" was assigned to subinterface "SFP 0/0/7/0/1.4" Ip address "10.238.24.60" in interface SranBs report: Please confirm whether the issue has been resolved. If it has, kindly close the ticket. Regards, Mustapha Al Hage
        Hide
        Aurobinda Panda added a comment -

        Dear @Mustapha,
        Don't reject the tickets without validation.
        If any issue is resolved, the testing will be carried out and closed by L1. I am reopening the ticket.

        Show
        Aurobinda Panda added a comment - Dear @Mustapha, Don't reject the tickets without validation. If any issue is resolved, the testing will be carried out and closed by L1. I am reopening the ticket.
        Hide
        Marwan Kanaan added a comment -

        dear @aurobinda kindly share a valid case so Mustapha can work on it from his side.

        Show
        Marwan Kanaan added a comment - dear @aurobinda kindly share a valid case so Mustapha can work on it from his side.
        Hide
        Abir Messaikeh added a comment -

        to be checked after import

        Show
        Abir Messaikeh added a comment - to be checked after import
        Hide
        Aurobinda Panda added a comment -

        Dear @Mustapha, As i checked, it is found that for NE BK09790 the Port detail is available in IP data for the IP address used in addinfo. But in RAN logical interface report the port is not assigned. Kindly check.
        new SS are added for the node in attachment.

        Show
        Aurobinda Panda added a comment - Dear @Mustapha, As i checked, it is found that for NE BK09790 the Port detail is available in IP data for the IP address used in addinfo. But in RAN logical interface report the port is not assigned. Kindly check. new SS are added for the node in attachment.
        Hide
        Mustapha Al-Hage added a comment -

        Dear @Aurobinda Panda,

        The XML shared does not include the SRanBs case "BK09790" you mentioned in previous email.  We need a valid XML file so we can check the issue. 

        Regards, 
        Mustapha 

        Show
        Mustapha Al-Hage added a comment - Dear @Aurobinda Panda, The XML shared does not include the SRanBs case "BK09790" you mentioned in previous email.  We need a valid XML file so we can check the issue.  Regards,  Mustapha 

          People

          • Assignee:
            Aurobinda Panda
            Reporter:
            Aurobinda Panda
            Rejected By:
            Mustapha Al-Hage
          • Votes:
            0 Vote for this issue
            Watchers:
            5 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 - 2 weeks, 1 day, 4 hours, 15 minutes
              2w 1d 4h 15m

                Drag and Drop