[LS-595] Import Issue – Missing Service Port Descriptions in NEP for some accounts Created: 26/Aug/25 Updated: 03/Nov/25 Due: 29/Aug/25 Resolved: 19/Sep/25 |
|
| Status: | Cancelled |
| Project: | L3 Support |
| Component/s: | NEP |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Salem Dannawi | Assignee: | Salem Dannawi |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 6 hours | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Customer: |
OMAN-Tel
|
| Planned Start: | |
| Planned End: | |
| Rejected By: | Marwan Kanaan |
| Actual Start: | |
| Date of Baselining: |
| Description |
|
I have noticed that not all data under service-port description is being parsed in NEP, even though the same information is available in the XML. This is causing missing MPLS subscriber records in the Service Port Description Report, as also reported by Anees. Sample XML snippet and logical dump entries are provided below for clarity.Kindly align someone to check the same. Logical Dump for Node ABI1_01_MA5600T_OLT:: service-port desc 4 description "26708645" |
| Comments |
| Comment by Abir Messaikeh [ 26/Aug/25 ] |
|
server logs link during import |
| Comment by Abir Messaikeh [ 28/Aug/25 ] |
|
to provide small xml for this model and the equipement model |
| Comment by Abir Messaikeh [ 28/Aug/25 ] |
|
link for small xml |
| Comment by Hassan Abdine [ 29/Aug/25 ] |
|
kindly to provide a small XML for one NE and the equipment model XML from catalog. |
| Comment by Abir Messaikeh [ 10/Sep/25 ] |
|
XML provided by Driss to Marwan |
| Comment by Hassan Abdine [ 18/Sep/25 ] |
|
still not received an xml for this NE |
| Comment by Marwan Kanaan [ 18/Sep/25 ] |
|
Dears, First, please note that the 2025-08-19-11.30.33_OmanTel.tar.gz folder contains only CSV files, with no XML available to work with or extract data from. Second, regarding the Jira information and screenshots, there seems to be a misunderstanding with the search criteria. As shown in the CSV, the search was for 931207, which corresponds to the sample node in Jira (ABI1_01_MA5600T_OLT – 10.126.96.65). However, in the NE configuration, the search was for 931027, which refers to service-port descriptions for a completely different node (10.126.67.151). Therefore, please note that before generating a suitable XML, we cannot proceed further with this issue. Best Regards, Marwan Kanaan I Software Developer |
| Comment by Abir Messaikeh [ 19/Sep/25 ] |
|
small xml attached |
| Comment by Marwan Kanaan [ 19/Sep/25 ] |
|
Dear @Shamim Ahmed, Kindly note that the problem is most likely related to the issue already solved by Driss in the dumps. SS I suggest generating a new XML and ensuring that the dumps are properly fixed, then attempting the re-import, as there is no issue from our side. Best Regards, |
| Comment by Khaled Khalil [ 22/Sep/25 ] |
|
There is a rule in that FN report: it only shows ports related to subscriber numbers that start with 9 |