Details

    • Customer:
      OMAN-Tel

      Description

      Please we need to find a way to build automatically a physical connectivity between two nodes that are already routed logically.
      Following the below steps for one sample case:

      In case of end to end fully routed case, without physical connectivity please find the case in below. As you can see ,

      NGN Node: SOHAR_C5_UMG

      Node1:NGN-SOH-SX-EXT-LSW-0
      Node2:RB0001-01-NE40E-X16A-PE-SOHAR

      Routing Info

      AS you can both nodes are now routed through logical information based on routing table. Hence, we need to complete the process by checking if they will be done physically, and nothing was connected between those two nodes. So, we build the connectivity manually between GETH ports from both extremities.

      Created link:

      You can notice in below how the connectivity now is fully routed after creating a link between the GETH, UP interfaces for both Extremities.

        Activity

        Salem Dannawi made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2025-07-07 24:00 (milestone: set planned start date to due date)
        Planned End 2025-07-07 24:00 (milestone: set planned end date to due date)
        Hide
        Bessem Manita added a comment -

        Dear Khaled,
        Kindly provide detailed rules outlining how the physical connectivity should be implemented between routers.
        Specifically, we would appreciate clarification on the following points:

        • What are the criteria or indicators to determine that a physical connection is required between two routers.
        • How should we identify the appropriate ports to use at each end.
        • How can we deduce the Link Type, and are there any other parameters or configurations that need to be considered during link creation.
        Show
        Bessem Manita added a comment - Dear Khaled, Kindly provide detailed rules outlining how the physical connectivity should be implemented between routers. Specifically, we would appreciate clarification on the following points: What are the criteria or indicators to determine that a physical connection is required between two routers. How should we identify the appropriate ports to use at each end. How can we deduce the Link Type, and are there any other parameters or configurations that need to be considered during link creation.
        Bessem Manita made changes -
        Assignee Khaled Khalil [ kkhalil ] Bessem Manita [ bmanita ]
        Hide
        Abir Messaikeh added a comment -

        patch .1328 released , Added a pre-RB process to handle link creation based on neighbor record

        Show
        Abir Messaikeh added a comment - patch .1328 released , Added a pre-RB process to handle link creation based on neighbor record
        Abir Messaikeh made changes -
        Labels Service_routing
        Khaled Khalil made changes -
        Status Opened [ 1 ] Pending Requirements [ 10300 ]
        Khaled Khalil made changes -
        Status Pending Requirements [ 10300 ] Pending Design Session [ 10112 ]
        Assignee Bessem Manita [ bmanita ] Khaled Khalil [ kkhalil ]
        Khaled Khalil made changes -
        Status Pending Design Session [ 10112 ] Dev Scheduled [ 10014 ]
        Assignee Khaled Khalil [ kkhalil ] Bessem Manita [ bmanita ]
        Khaled Khalil made changes -
        Status Dev Scheduled [ 10014 ] Implementation in progress [ 10016 ]
        Assignee Bessem Manita [ bmanita ] Khaled Khalil [ kkhalil ]
        Khaled Khalil made changes -
        Assignee Khaled Khalil [ kkhalil ] Bessem Manita [ bmanita ]
        Hide
        Bessem Manita added a comment -

        released in patch 3.7.0.1328

        Show
        Bessem Manita added a comment - released in patch 3.7.0.1328
        Bessem Manita made changes -
        Status Implementation in progress [ 10016 ] To Be Released [ 10400 ]
        Abir Messaikeh made changes -
        Status To Be Released [ 10400 ] Ready for QA [ 10023 ]
        Assignee Bessem Manita [ bmanita ] Salem Dannawi [ sdannawi ]
        Abir Messaikeh made changes -
        Status Ready for QA [ 10023 ] QA In Progress [ 10015 ]
        Assignee Salem Dannawi [ sdannawi ] Abir Messaikeh [ amessaikeh ]
        Abir Messaikeh made changes -
        Assignee Abir Messaikeh [ amessaikeh ] Aurobinda Panda [ apanda ]
        Abir Messaikeh made changes -
        Reporter Salem Dannawi [ sdannawi ] Aurobinda Panda [ apanda ]
        Abir Messaikeh made changes -
        Reporter Aurobinda Panda [ apanda ] Khaled M Ayoubi [ khaled.ayoubi ]
        Abir Messaikeh made changes -
        Assignee Aurobinda Panda [ apanda ] Khaled M Ayoubi [ khaled.ayoubi ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Opened Opened Pending Requirements Pending Requirements
        33d 5h 8m 1 Khaled Khalil 06/Aug/25 12:52 PM
        Pending Requirements Pending Requirements Pending Design Session Pending Design Session
        5s 1 Khaled Khalil 06/Aug/25 12:52 PM
        Pending Design Session Pending Design Session Dev Scheduled Dev Scheduled
        13s 1 Khaled Khalil 06/Aug/25 12:53 PM
        Dev Scheduled Dev Scheduled Implementation in progress Implementation in progress
        5s 1 Khaled Khalil 06/Aug/25 12:53 PM
        Implementation in progress Implementation in progress To Be Released To Be Released
        2m 48s 1 Bessem Manita 06/Aug/25 12:56 PM
        To Be Released To Be Released Ready for QA Ready for QA
        1d 22m 1 Abir Messaikeh 07/Aug/25 1:18 PM
        Ready for QA Ready for QA QA In Progress QA In Progress
        8s 1 Abir Messaikeh 07/Aug/25 1:18 PM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Khaled M Ayoubi
            Reporter:
            Khaled M Ayoubi
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:

              Drag and Drop