Details

    • Customer:
      Airtel India

      Description

      as observed , for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
      this issue is observed for all the circle and i have shared one sample case for UW Circle .

      this NE name in RB report have only 5 routes for 5 different destination and in the logical view for this sites we have 7 different routes than all these Vlan's are not there in vlan report .. ideally the old route should be deleted for which the interface is not defined in the interface report. and only single route should be reflected in the logical view through one L2 pop and same L2 should reflect in the Site pop path report and traffic report and other enteries should be deleted ..
      here the sample case as we can see the vlan 2616 and 2776 as highlighted in snap should be removed and this Vlan is not avilable in the Vlan report also.

      1. ABUP01 INTERFACE REPORT.png
        27 kB
      2. ABUP01 INTERFACE REPORT 1.png
        44 kB
      3. abup01 ip data.png
        12 kB
      4. abup01 ipv6.png
        18 kB
      5. ABUP01 OSSIP.png
        47 kB
      6. ABUP01 ROUTE.png
        60 kB
      7. ABUP01 ROUTE 2.png
        39 kB
      8. LS-627.jpg
        36 kB
      9. RB ABUP01 SITE.png
        37 kB
      10. SITE POP SNAP .png
        23 kB
      11. TRAFFIC SNAP ABUP01.png
        31 kB
      12. vlan abup01.png
        21 kB

      Issue Links

        Activity

        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Bug Open Bug Need More Info Need More Info
        1d 1m 1 Hassan Abdine 05/Sep/25 8:12 AM
        Need More Info Need More Info Open Bug Open Bug
        5h 33m 1 Priyasha Tiwari 05/Sep/25 1:46 PM
        Open Bug Open Bug Rejected Rejected
        31d 21h 54m 1 Srishti Kashyap 07/Oct/25 11:41 AM
        Rejected Rejected Reopened Reopened
        22d 20h 54m 1 Priyasha Tiwari 30/Oct/25 7:35 AM
        Dev Scheduled Dev Scheduled Implementation in progress Implementation in progress
        29s 1 Khaled Khalil 18/Nov/25 9:42 AM
        Implementation in progress Implementation in progress To Be Released To Be Released
        11s 1 Khaled Khalil 18/Nov/25 9:42 AM
        To Be Released To Be Released Ready for QA Ready for QA
        5s 1 Khaled Khalil 18/Nov/25 9:42 AM
        Ready for QA Ready for QA QA In Progress QA In Progress
        51d 3m 1 Priyasha Tiwari 08/Jan/26 9:45 AM
        QA In Progress QA In Progress Reopened Reopened
        88d 19h 25m 1 Priyasha Tiwari 07/Apr/26 6:11 AM
        Reopened Reopened Dev Scheduled Dev Scheduled
        26d 7h 45m 2 Khaled Khalil Tuesday 11:49 AM
        Khaled Khalil made changes -
        Status Reopened [ 4 ] Dev Scheduled [ 10014 ]
        Khaled Khalil made changes -
        Assignee Khaled Khalil [ kkhalil ] Srishti Kashyap [ skashyap ]
        Priyasha Tiwari made changes -
        Status QA In Progress [ 10015 ] Reopened [ 4 ]
        Assignee Bessem Manita [ bmanita ] Khaled Khalil [ kkhalil ]
        Resolution Not Fixed [ 10200 ] Incomplete [ 4 ]
        Hide
        Priyasha Tiwari added a comment -

        i need the detailed working of the API,

        Show
        Priyasha Tiwari added a comment - i need the detailed working of the API,
        Priyasha Tiwari made changes -
        Assignee Priyasha Tiwari [ ptiwari ] Bessem Manita [ bmanita ]
        Hide
        Priyasha Tiwari added a comment -

        please share the API detailed working in JIRA also ,to avoid any confusion

        Show
        Priyasha Tiwari added a comment - please share the API detailed working in JIRA also ,to avoid any confusion
        Priyasha Tiwari made changes -
        Status Ready for QA [ 10023 ] QA In Progress [ 10015 ]
        Hide
        Priyasha Tiwari added a comment -

        API is still under validation , and awaiting customer confirmation

        Show
        Priyasha Tiwari added a comment - API is still under validation , and awaiting customer confirmation
        Priyasha Tiwari made changes -
        Time Spent 2 days, 6 hours, 42 minutes [ 81720 ] 2 days, 7 hours, 42 minutes [ 85320 ]
        Worklog Id 284727 [ 284727 ]
        Priyasha Tiwari logged work - 27/Nov/25 12:00 AM
        • Time Spent:
          1 hour
           

          MORE SAMPLE CASES SHARED FROM SMALL CIRCLE AS REQUESTED BY L3 TEAM

        Hide
        Priyasha Tiwari added a comment -

        as discussed API is requested from the customer for the old node deletion

        Show
        Priyasha Tiwari added a comment - as discussed API is requested from the customer for the old node deletion
        Basant Kumar made changes -
        Time Spent 2 days, 4 hours, 42 minutes [ 74520 ] 2 days, 6 hours, 42 minutes [ 81720 ]
        Worklog Id 284147 [ 284147 ]
        Basant Kumar logged work - 21/Nov/25 12:00 AM
        • Time Spent:
          2 hours
           

          Build 3.7.71.528 applied on AP prod server.

        Khaled Khalil made changes -
        Status To Be Released [ 10400 ] Ready for QA [ 10023 ]
        Assignee Khaled Khalil [ kkhalil ] Priyasha Tiwari [ ptiwari ]
        Khaled Khalil made changes -
        Status Implementation in progress [ 10016 ] To Be Released [ 10400 ]
        Khaled Khalil made changes -
        Status Dev Scheduled [ 10014 ] Implementation in progress [ 10016 ]
        Assignee Bessem Manita [ bmanita ] Khaled Khalil [ kkhalil ]
        Khaled Khalil made changes -
        Status Reopened [ 4 ] Dev Scheduled [ 10014 ]
        Bessem Manita made changes -
        Assignee Srishti Kashyap [ skashyap ] Bessem Manita [ bmanita ]
        Hide
        Bessem Manita added a comment -

        Fix for deleting old invalid routes was released in patch 3.7.71.526.

        Show
        Bessem Manita added a comment - Fix for deleting old invalid routes was released in patch 3.7.71.526.
        Srishti Kashyap made changes -
        Time Spent 2 days, 1 hour [ 61200 ] 2 days, 4 hours, 42 minutes [ 74520 ]
        Worklog Id 283315 [ 283315 ]
        Srishti Kashyap made changes -
        Time Spent 1 day, 1 hour, 30 minutes [ 34200 ] 2 days, 1 hour [ 61200 ]
        Worklog Id 283310 [ 283310 ]
        Srishti Kashyap made changes -
        Time Spent 6 hours, 30 minutes [ 23400 ] 1 day, 1 hour, 30 minutes [ 34200 ]
        Worklog Id 283309 [ 283309 ]
        Srishti Kashyap logged work - 13/Nov/25 12:00 AM
        • Time Spent:
          3 hours, 42 minutes
           

          checked the sample cases shared by telco on prod compared the vlan existing in db shared queries with integration found old entry of unrequired route in circuit traffic not updating..requested 17 aug xml

        Priyasha Tiwari made changes -
        Time Spent 3 hours, 30 minutes [ 12600 ] 6 hours, 30 minutes [ 23400 ]
        Worklog Id 283152 [ 283152 ]
        Hide
        Priyasha Tiwari added a comment -

        as requested ,sample case from a small circle HP prod shared on email please check .. Node name -LABWL01

        Show
        Priyasha Tiwari added a comment - as requested ,sample case from a small circle HP prod shared on email please check .. Node name -LABWL01
        Hide
        Srishti Kashyap added a comment -

        Hi Dear,
        Please provide some sample cases related to the issue from the PROD small circle environment.
        This will help in verifying and analyzing the problem more effectively.

        Show
        Srishti Kashyap added a comment - Hi Dear, Please provide some sample cases related to the issue from the PROD small circle environment. This will help in verifying and analyzing the problem more effectively.
        Priyasha Tiwari made changes -
        Description
        For example, for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        this issue is observed for all the circle and i have shared one sample case for UW Circle .

        this NE name in RB report have only 5 routes for 5 different destination and in the logical view for this sites we have 7 different routes than all these Vlan's are not there in vlan report .. ideally the old route should be deleted for which the interface is not defined in the interface report. and only single route should be reflected in the logical view through one L2 pop and same L2 should reflect in the Site pop path report and traffic report and other enteries should be deleted ..
        here the sample case as we can see the vlan 2616 and 2776 as highlighted in snap should be removed and this Vlan is not avilable in the Vlan report also.

        as observed , for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        this issue is observed for all the circle and i have shared one sample case for UW Circle .

        this NE name in RB report have only 5 routes for 5 different destination and in the logical view for this sites we have 7 different routes than all these Vlan's are not there in vlan report .. ideally the old route should be deleted for which the interface is not defined in the interface report. and only single route should be reflected in the logical view through one L2 pop and same L2 should reflect in the Site pop path report and traffic report and other enteries should be deleted ..
        here the sample case as we can see the vlan 2616 and 2776 as highlighted in snap should be removed and this Vlan is not avilable in the Vlan report also.

        Srishti Kashyap logged work - 12/Nov/25 12:00 AM
        • Time Spent:
          3 hours
           

          checking PROD for scenerios discussed with bessem raised a request to share sample case from small circle so that related db xlone could be asked

        Priyasha Tiwari logged work - 12/Nov/25 12:00 AM
        • Time Spent:
          3 hours
           

          SAMPLE CASE FROM SMALL CIRCLE PROD REQUESTED FROM L3 TEAM.

        Srishti Kashyap logged work - 11/Nov/25 12:00 AM
        • Time Spent:
          7 hours, 30 minutes
           

          working on testing of routes build issue for sample cases in HP circle connectng dev couldnt find same sample case and scenerio , reconnected DL copy checked there no similar sample exist again reconnecting HP for simple debug

        Priyasha Tiwari made changes -
        Attachment LS-627 1.jpg [ 117014 ]
        Priyasha Tiwari made changes -
        Attachment LS-627 2.jpg [ 117013 ]
        Priyasha Tiwari made changes -
        Attachment ABUP01 INTERFACE REPORT 1.png [ 120914 ]
        Attachment ABUP01 INTERFACE REPORT.png [ 120915 ]
        Attachment ABUP01 OSSIP.png [ 120916 ]
        Attachment abup01 ipv6.png [ 120917 ]
        Attachment abup01 ip data.png [ 120918 ]
        Attachment vlan abup01.png [ 120919 ]
        Attachment TRAFFIC SNAP ABUP01.png [ 120920 ]
        Attachment ABUP01 ROUTE 2.png [ 120921 ]
        Attachment ABUP01 ROUTE.png [ 120922 ]
        Attachment SITE POP SNAP .png [ 120923 ]
        Attachment RB ABUP01 SITE.png [ 120924 ]
        Priyasha Tiwari made changes -
        Description We have observed that the POP details from the Route Builder report are not updating correctly in the Site POP Path and Site Traffic reports. This issue is occurring across all circles.

        For example, for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        this issue is observed for all the circle and i have shared one sample case for UW Circle .

        For example, for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        this issue is observed for all the circle and i have shared one sample case for UW Circle .

        this NE name in RB report have only 5 routes for 5 different destination and in the logical view for this sites we have 7 different routes than all these Vlan's are not there in vlan report .. ideally the old route should be deleted for which the interface is not defined in the interface report. and only single route should be reflected in the logical view through one L2 pop and same L2 should reflect in the Site pop path report and traffic report and other enteries should be deleted ..
        here the sample case as we can see the vlan 2616 and 2776 as highlighted in snap should be removed and this Vlan is not avilable in the Vlan report also.

        Priyasha Tiwari made changes -
        Assignee Priyasha Tiwari [ ptiwari ] Srishti Kashyap [ skashyap ]
        Priyasha Tiwari made changes -
        Resolution Cancelled [ 10100 ] Not Fixed [ 10200 ]
        Status Rejected [ 10100 ] Reopened [ 4 ]
        Hide
        Priyasha Tiwari added a comment -

        srishit, this issue is not related to site pop category .. in this issue the L2 pop in rb report and site pop path and traffic report are not same .. ideally the l2 pop for the mentioned site should be same in all the reports .

        Show
        Priyasha Tiwari added a comment - srishit, this issue is not related to site pop category .. in this issue the L2 pop in rb report and site pop path and traffic report are not same .. ideally the l2 pop for the mentioned site should be same in all the reports .
        Hide
        Priyasha Tiwari added a comment -

        srishit, this issue is not related to site pop category .. in this issue the L2 pop in rb report and site pop path and traffic report are not same .. ideally the l2 pop for the mentioned site should be same in all the reports .

        Show
        Priyasha Tiwari added a comment - srishit, this issue is not related to site pop category .. in this issue the L2 pop in rb report and site pop path and traffic report are not same .. ideally the l2 pop for the mentioned site should be same in all the reports .
        Hide
        Srishti Kashyap added a comment -

        Dear Priyasha,
        It was found that all the sites which are not reflecting on pop site report are not pop site also they have ,Access Route Status: Vlan Path Broken. and showing routed in rb report which is not correct hence it is proposed to set the Access Route Status as Failed and move the current Access Route Status to Access Error Details for sites that are not reflecting in POP site and have Access Route Status: Vlan Path Broken.
        This porposal last denied and we reverted you back for LS-700 that sites are missing pop info from xml.

        Show
        Srishti Kashyap added a comment - Dear Priyasha, It was found that all the sites which are not reflecting on pop site report are not pop site also they have ,Access Route Status: Vlan Path Broken. and showing routed in rb report which is not correct hence it is proposed to set the Access Route Status as Failed and move the current Access Route Status to Access Error Details for sites that are not reflecting in POP site and have Access Route Status: Vlan Path Broken. This porposal last denied and we reverted you back for LS-700 that sites are missing pop info from xml.
        Hide
        Abir Messaikeh added a comment -

        pending LS-700 Missing PoP site as the issue is broken path

        Show
        Abir Messaikeh added a comment - pending LS-700 Missing PoP site as the issue is broken path
        Abir Messaikeh made changes -
        Link This issue relates to LS-303 [ LS-303 ]
        Srishti Kashyap made changes -
        Status Open Bug [ 10108 ] Rejected [ 10100 ]
        Assignee Srishti Kashyap [ skashyap ] Priyasha Tiwari [ ptiwari ]
        Resolution Cancelled [ 10100 ]
        Khaled Khalil made changes -
        Assignee Priyasha Tiwari [ ptiwari ] Srishti Kashyap [ skashyap ]
        Priyasha Tiwari made changes -
        Time Spent 2 hours [ 7200 ] 3 hours, 30 minutes [ 12600 ]
        Worklog Id 277355 [ 277355 ]
        Priyasha Tiwari made changes -
        Assignee Basant Kumar [ bkumar ] Priyasha Tiwari [ ptiwari ]
        Priyasha Tiwari made changes -
        Assignee Khaled Khalil [ kkhalil ] Basant Kumar [ bkumar ]
        Hide
        Priyasha Tiwari added a comment -

        @Basant share small xml of UW circle .. path mention below..
        /product/Airtel/nep_packages/auto-importer/Dumps/huawei/m2000/logical/CFG/PAN INDIA LOGICAL HUA CORE/10.35.133.11

        Show
        Priyasha Tiwari added a comment - @Basant share small xml of UW circle .. path mention below.. /product/Airtel/nep_packages/auto-importer/Dumps/huawei/m2000/logical/CFG/PAN INDIA LOGICAL HUA CORE/10.35.133.11
        Priyasha Tiwari logged work - 12/Sep/25 12:00 AM
        • Time Spent:
          1 hour, 30 minutes
           

          CALL with aurobinda sir and customer

        Priyasha Tiwari made changes -
        Labels nep_dev
        Priyasha Tiwari made changes -
        Assignee Priyasha Tiwari [ ptiwari ] Khaled Khalil [ kkhalil ]
        Priyasha Tiwari made changes -
        Description We have observed that the POP details from the Route Builder report are not updating correctly in the Site POP Path and Site Traffic reports. This issue is occurring across all circles.

        For example, for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        We have observed that the POP details from the Route Builder report are not updating correctly in the Site POP Path and Site Traffic reports. This issue is occurring across all circles.

        For example, for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        this issue is observed for all the circle and i have shared one sample case for UW Circle .
        Priyasha Tiwari made changes -
        Status Need More Info [ 10011 ] Open Bug [ 10108 ]
        Priyasha Tiwari made changes -
        Description We have observed that the POP details from the Route Builder report are not updating correctly in the Site POP Path and Site Traffic reports. This issue is occurring across all circles.

        For example, for node SRAN_ABUP01, the Route Builder report shows L2 POP as MDN31_UW, while the Site POP Path and Traffic reports are showing MDN02_UW.
        Priyasha Tiwari made changes -
        Attachment LS-627 2.jpg [ 117013 ]
        Attachment LS-627 1.jpg [ 117014 ]
        Attachment LS-627.jpg [ 117015 ]
        Priyasha Tiwari made changes -
        Baseline Start 2025-09-12 24:00 (set baseline based of initial work logging)
        Baseline End 2025-09-12 24:00 (set baseline based of initial work logging)
        Priyasha Tiwari made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours [ 7200 ]
        Worklog Id 276527 [ 276527 ]
        Hassan Abdine made changes -
        Status Open Bug [ 10108 ] Need More Info [ 10011 ]
        Assignee Khaled Khalil [ kkhalil ] Priyasha Tiwari [ ptiwari ]
        Hide
        Hassan Abdine added a comment -

        provide the details with last status and clear use case.

        Show
        Hassan Abdine added a comment - provide the details with last status and clear use case.
        Hassan Abdine made changes -
        Component/s NEP [ 16200 ]
        Priyasha Tiwari logged work - 05/Sep/25 12:00 AM
        • Time Spent:
          2 hours
           

          analysis and jira update

        Priyasha Tiwari made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2025-09-12 24:00 (milestone: set planned start date to due date)
        Planned End 2025-09-12 24:00 (milestone: set planned end date to due date)

          People

          • Assignee:
            Srishti Kashyap
            Reporter:
            Priyasha Tiwari
            Rejected By:
            Srishti Kashyap
          • 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 days, 7 hours, 42 minutes
              2d 7h 42m

                Drag and Drop