Details
-
Type:
Bug
-
Status:
Cancelled
(View Workflow)
-
Priority:
Normal
-
Resolution: Cancelled
-
Component/s: None
-
Labels:
-
Customer:Zain KSA 3.X
Description
Dear @Khaled Khalil,
Could you please assign a NEP resource to investigate and resolve the following issues?
Case 1:
There are 19 instances of antenna serial numbers that are not being imported into NEP (.14) under the "Addinfo" report. However, the related antennas are being imported under the "Radio Antennas Report." Additionally, there are no errors shown in the "Error Report" for these cases.
XML Addinfo Snippet: XML Radio Antenna Snippet:
NEP Addinfo Snippet: NEP Radio Antenna Snippet:
Case 2:
There are 37,892 serial numbers associated with antenna IDs, but these serial numbers are not appearing in the "Addinfo" report under the corresponding antenna IDs. But same serial numbers are showing with different antenna IDs, (Could you please confirm this issue has happened due to duplicity or any other reason), The associated antenna IDs are correctly imported under the "Radio Antenna Report," and no related errors are appearing in the "Error Report."
Please refer to the attached list for further details.
For reference, I am sharing one example below:
XML Addinfo Snippet: NEP Radio Antenna Report:
NEP Addinfo Report:
Best regards,
Indrasan
Attachments
Issue Links
- blocks
-
ZKU-95
Nokia RAN_Dumps , XML and NEP data Validation_Sub Parent
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Dear @Mustapha Al-Hage,
Thanks for your feedback.
I would like to provide some clarification regarding the issue I raised.
Case 1: When I initially raised the JIRA, 19 serial numbers had not been imported, as shown in the snippet I shared. After raising the issue, I imported the Nokia XML file twice, and it is possible that the serial numbers were then imported successfully. As a result, these serial numbers are now available in the AddInfo report.
Case 2: At the time I raised the JIRA, no warning was displayed in the error report, as seen in the snippet below. The only errors shown were 2795 issues related to antenna type changes under the "unknown" category.
My concern was whether there is a duplicity rule in NEP for radio antennas, like the rule for physical serial numbers. I checked with @Ahad Siddiqui, who told that there should be no duplicity rule for radio antennas. As a result, I raised the issue for confirmation from the DEV team.
We have since received the final comment stating that a duplicity rule for radio antenna serial numbers exists in NEP, like the rule for physical serial numbers for cabinets, shelves, and boards.
Best regards,
Indrasan
Case-1: Fixed
Case-2: Will conclude within LS-141.
We can cancel this JIRA.
Dear @Indrasan Yadav,
After reviewing the XML file, error report, implemented logic and the .14 platform, we have found the following:
Case 1:
Upon investigating Case 1, we found that all the serial numbers were imported into NEP. For example, the SerialNumber mentioned “K00AF241600003-M2” was imported and visible in the additional information report as shown below:
Case 2:
Regarding case 2, we identified a warning in the error report: “Asset Uniqueness:Element RadioAntenna X has Serial Number EX (Y) that is already in use for another radio antenna.”, As shown below.
This warning indicates that the Serial Number is unique and cannot be assigned to more than one radio antenna node.
In conclusion, the warning found in the error report prevents the duplication of Serial Numbers.
Regards,
Mustapha Al Hage