Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Labels:
-
Customer:OMAN-Tel
-
Complexity:High
-
Severity:Major
-
Product:NEP
-
REQUESTER:INTERNAL
Description
Dear Khaled Khalil,
It is found that, the Subinterfaces available in NEP IP data report is missing in NEP Subinterface report.
Due to which RAN Port information is missing in RAN logical Interface for the RAN nodes.
Please find sample Node below.
BB02401
As per IP data
10.132.70.33 255.255.254.0 10.132.70.1 BB02401 BB02401 SRanBs GETH 0/0/7/0/1.4
10.132.70.33 is assigned for Interface GETH 0/0/7/0/1.4
But as checked in Subinterface report it missing.
BB02401 SRanBs GETH 0/0/7/0/1 3 10.222.79.51 255.255.255.0
BB02401 SRanBs GETH 0/0/7/0/1 4
I have checked the XML and it is available.
SS details are shared in attachment.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours
-
Subinterface parsing issue checked in NEP post cleanup.
-
- Time Spent:
- 15 minutes
-
discussed with Abir and Mohan for the requirement.
-
- Time Spent:
- 3 hours
-
applying scripts on prod
-
- Time Spent:
- 1 hour
-
XML import and data analysis and internal discussion
-
- Time Spent:
- 1 day
-
applying the scripts on .180
-
- Time Spent:
- 30 minutes
-
discussion with L3 for the issue and solution.
-
- Time Spent:
- 1 day
-
creating the scripts for the clean up
-
- Time Spent:
- 1 day
-
Centralized IP lifecycle handling has been implemented across all interface types, unifying the save/remove logic into saveIPAddressing and introducing a consistent flow for IP creation, update, freeing, and deletion. Ownership resolution is now centralized via getIpDataOwner, covering NodeInterface, SubInterface, AbstractInterface, LogicalInterface, VirtualInterface, and HSRP, while IP uniqueness is standardized by using IP Data IDs instead of raw addresses. The freeing and deletion processes have been improved through freeIpDataFromNodes and deleteIpData, with reserved IP ranges validated before assignment. Redundant methods and unused classes have been cleaned up, and updates were applied across NodeConfigurationManager and PhysicalConfigurationManager to ensure smooth integration.
BREAKING CHANGE: old pre-IP Logic methods have been removed, and all code must now use the centralized saveIPAddressing and freeIpDataFromNodes and the rest of the new Logic.
Further more we need to wirte the scirpts to apply them on prod.
-
- Time Spent:
- 1 day
-
impelementing logic and change what needed to change
-
- Time Spent:
- 1 day
-
impelementing logic and change what needed to change
-
- Time Spent:
- 1 day
-
impelementing logic and change what needed to change
-
- Time Spent:
- 1 day
-
Focused on retrieving data and analyzing the problem in depth, discussed the issues with Hassan, and adjusted some validation logic to ensure checks are based on route domains rather than solely on IP addresses for used IPs. Implemented a new class for custom marshalling of large XML files to efficiently extract the required data and generate new XMLs, improving debugging speed and workflow, with plans to generalize the solution later.
-
- Time Spent:
- 6 hours
-
Checked data in production and discussed the requirements with Hassan as we checked many cases to be solved, then reviewed the code and underlying logic to analyze the issue and determine the proper fix; created queries to identify and view corrupted data, along with cleanup scripts to delete invalid entries and corrective queries to restore the affected records.
-
- Time Spent:
- 4 hours
-
Investigated multiple cases and performed repeated imports with large XML files to analyze behavior and outcomes, in order to proceed with defining a permanent solution.
-
- Time Spent:
- 30 minutes
-
Issue has been checked and updated the comments.
-
- Time Spent:
- 30 minutes
-
Subinterfaces checked in NEP post script run.
-
- Time Spent:
- 4 hours
-
I created the version MARWAN_TEST, reimported the data, and confirmed that all subinterfaces correctly received their IP addresses. We will wait for the cleanup script to be executed before requesting them to reimport and assess the impact.
-
- Time Spent:
- 1 day
-
after making sure from the nodeConfigurationManger i start debug into the PhyscialConfigurationManger to check it the IP are saved to the subinterfaces and worked with to sample and three imports to decide the next step
-
- Time Spent:
- 1 day
-
debuging in the nodeConfigurationManger to be sure that the data are imported from the xml
-
- Time Spent:
- 1 day
-
getting information about the Subinterfaces and Interfaces and take a deep look to the code and invistigate into the xml and logs to find if the issue is related to them