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
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2024-12-30 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2024-12-30 24:00 (milestone: set planned end date to due date) |
| Summary | Antenna Serial Numbers Are Not Imported In NEP(.14)_Nokia | Antenna Serial Numbers Are Not Imported In NEP(.14) Under Addinfo_Nokia |
| 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 |
| Assignee | Khaled Khalil [ kkhalil ] | Mustapha Al-Hage [ malhage ] |
| Attachment | 2024-12-23-02.07.13_ZainKsa.rar [ 103518 ] |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Assignee | Mustapha Al-Hage [ malhage ] | Khaled Khalil [ kkhalil ] |
| Assignee | Khaled Khalil [ kkhalil ] | Mustapha Al-Hage [ malhage ] |
| Attachment | Case-1=Serial Not Imported In NEP(.14).xlsx [ 103538 ] | |
| Attachment | Case-2=Serial Not Imported In NEP(.14) On Same Node As Available In XML.xlsx [ 103539 ] |
| Status | Implementation in progress [ 10016 ] | Rejected [ 10100 ] |
| Assignee | Mustapha Al-Hage [ malhage ] | Indrasan Yadav [ iyadav ] |
| Resolution | Incomplete [ 4 ] |
-
- Time Spent:
- 2 hours
-
Checked received feedback from @Mustapha & cross verify then discussed with him & reverted on same mail.
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 2 hours [ 7200 ] | |
| Worklog Id | 258709 [ 258709 ] |
| Baseline Start | 2024-12-30 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2024-12-30 24:00 (set baseline based of initial work logging) |
| Status | Rejected [ 10100 ] | Cancelled [ 10013 ] |
| Resolution | Incomplete [ 4 ] | Cancelled [ 10100 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
8d 12h 26m | 1 | Khaled Khalil | 02/Jan/25 3:08 AM | |||||
|
7s | 1 | Khaled Khalil | 02/Jan/25 3:08 AM | |||||
|
10h 47m | 1 | Mustapha Al-Hage | 02/Jan/25 1:55 PM | |||||
|
25d 18h 43m | 1 | Indrasan Yadav | 28/Jan/25 8:39 AM |
|
Links Hierarchy |
Documentation
|
Documentation
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