Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: None
-
Customer:OMAN-Tel
-
Complexity:High
-
Severity:Critical
-
Product:NEP
-
REQUESTER:INTERNAL
Description
Could you please assign a resource to check below issue.
It is found that, the Add info is not importing well for IUB links in NEP. The XML contains the required details & the IP details are also Available.
The trailing mail shows the data available in NEP & XML. But still RAN interfaces are missing.
The error report shows that “No compliant interface type” and data redundancy.
Last imported full XML is 2025-02-07-10.17.44_OmanTel on 7th Feb.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Dear @Mustapha,
Please help to remove the wrong values from add info. As the addinfo can't be removed without removing the RNC from NEP.
Dears,
I have attached the requested script to delete all "ADJNODE" and "ASSOCIATION" additional info for "ERNC01", "ERNC02", "ERNC03", "ERNC04" nodes that have the keyword “CONNECTION_TYPE=IUPS;CONNECTION_TYPE=IUCS;” as suggested by @Aurobinda Panda.
Please specify the required version in the script where it says: 'PUT REQUIRED VERSION HERE'.
regards,
Mustapha Al Hage
Script run in 180 & found OK. Ticket closed.
Dear @Aurobinda Panda,
After exploring XML, prod and implemented logic, we have found the following:
The following errors: "Association on node with remote ip 10.117.70.50of adjancency Iub_UD00030 on node ERNC01 was ignored due to redundancy" and "Association on node with remote ip 10.117.70.50of adjancency 1-10.225.38.123_5113-10.117.70.50 on node ERNC01 was ignored due to redundancy" Indicate redundancy as the remote IP "10.117.70.50" is used multiple times, causing the RAN logical interface to fail import.
Moreover, the additional info of value Iub_UD00030 are actually imported into NEP.
Regards,
Mustapha Al Hage