Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
Description
Attachments
Issue Links
- blocks
-
ZKU-94
Huawei RAN_Dumps , XML and NEP data Validation
-
Activity
-
- Time Spent:
- 1 hour, 30 minutes
-
Checked dump & found serial number duplicity in dump & raised to concerned person.
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2024-11-29 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2024-11-29 24:00 (milestone: set planned end date to due date) |
| Summary | Duplicacy Of Serial Numbers In Physical_Huawei | Nokia RAN_Dumps , XML and NEP data Validation_Huawei-RAN |
| Summary | Nokia RAN_Dumps , XML and NEP data Validation_Huawei-RAN | Serial Number Duplicity in Physical Inventory Data_Huawei |
| Assignee | Indrasan Yadav [ iyadav ] | Navneet Kaur [ nkaur ] |
| Attachment | Serial Number Duplicity in Physical Inventory Data_Huawei.xlsx [ 102866 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour, 30 minutes [ 5400 ] | |
| Worklog Id | 257251 [ 257251 ] |
| Baseline Start | 2024-11-29 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2024-11-29 24:00 (set baseline based of initial work logging) |
-
- Time Spent:
- 2 hours, 30 minutes
-
I’ve prepared a brief summary of the issue along with sample nodes and shared the parsing rule as requested. I had initially requested XML generation for Huawei based on this rule.
However, after further consideration, I would like to request not to apply this rule. If nodes are excluded from parsing due to duplicity, the associated LIC data for these nodes will also not be parsed.
| Assignee | Navneet Kaur [ nkaur ] | Sandya Sharma [ ssharma ] |
Dear @Sandya Sharma,
As discussed, please generate an XML for Huawei incorporating the updates we reviewed during our Teams call.
The existing rule can be retained with the following modification:
• We need to apply the rule for serial number duplicity, similar to the approach used for OmanTel. Specifically, this involves parsing only SRAN nodes where the cabinet or shelf serial number has a duplication issue with another standalone node.
Below is an example from the NodeB dump snippet for NEName="DAM2M4403-P2", where a serial number duplication issue occurs. The serial number 21021131694JB1000000 is also present in another SRAN node, NEName="MBTS-DAM2403-P2_SRAN".
NodeB: NEName="DAM2M4403-P2"
SRAN: NEName="MBTS-DAM2403-P2_SRAN"
Please implement this rule while generating the XML.
Thank you!
Best regards,
Indrasan
Dear @Sandya Sharma,
As discussed, please do not apply the rule for serial number duplicity.
@Ahad Siddiqui, as per our discussion, applying this rule would result in only SRAN nodes being parsed while standalone nodes are ignored. However, the LIC data in these standalone nodes is available technology-wise, and your suggestion on this matter would be highly appreciated.
If standalone nodes are ignored:
• These nodes will not be parsed into the XML.
• Consequently, they will not be imported into NEP.
• LIC data associated with these nodes will also remain unparsed and unavailable in NEP.
Therefore, we need to stop applying this rule for now and ensure that all nodes are parsed as they currently are.
Let me know if you have further questions or require clarification.
Best regards,
Indrasan
| Assignee | Sandya Sharma [ ssharma ] | Indrasan Yadav [ iyadav ] |
| Time Spent | 1 hour, 30 minutes [ 5400 ] | 3 hours, 30 minutes [ 12600 ] |
| Worklog Id | 257319 [ 257319 ] |
| Time Spent | 3 hours, 30 minutes [ 12600 ] | 4 hours [ 14400 ] |
| Worklog Id | 257319 [ 257319 ] |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
As license parsing is required and SN is anyhow duplicate , its important to parse botht he nodes, so this changes not recommneded.
| Status | In Progress [ 3 ] | To Do [ 10001 ] |
| Status | To Do [ 10001 ] | Done [ 10000 ] |
-
- Time Spent:
- 1 hour
-
Dear @Ahad Siddiqui,
As per our discussion, please find below the updated details:
Case 1: Duplicate node appearing in dump with different models.
Example: The node "HHR2068-P3_SRAN-PC" is listed with models BTS3900 and BTS5900.
Case 2: Duplicate child node persists under different nodes.
Example: The child node "MDN2C2996-MMM-P1-VIP" is found under two different nodes: "MDN2996-P1-VIP_SRAN" and "MDN2996-MMM-P1-VIP".
Case 3: Nodes missing in LIC nodes after removing MBTS & HUB nodes.
Please find the attached updated sheet.Case 4: Missing serial numbers excluding MBTS nodes.
Please find the attached updated sheet.Case 5: Duplicate serial numbers excluding MBTS type nodes.
Please find the attached updated sheet.Best regards,
Indrasan
| Time Spent | 4 hours [ 14400 ] | 5 hours [ 18000 ] |
| Worklog Id | 258705 [ 258705 ] |
| Worklog Id | 258705 [ 258705 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
5d 20h 4m | 1 | Indrasan Yadav | 18/Nov/24 4:44 AM | |||||
|
1m 11s | 1 | Indrasan Yadav | 18/Nov/24 4:45 AM | |||||
|
5s | 1 | Indrasan Yadav | 18/Nov/24 4:45 AM |
|
Links Hierarchy |
 Documentation
|
Dear @Navneet Kaur,
While reviewing the Huawei_RAN physical inventory data in the dump, I identified cases of serial number duplication for cabinets, shelves, and boards. A sample case for cabinet serial number "21021131694JB1000000" shows it is present in the dumps for multiple nodes, as listed below. The same serial number is also parsed in the XML; relevant snippets are attached for your reference.
MBTS-DAM2403-P2_SRAN
TRF2796-P2_SRAN
KHJ2M4304-P3
RIY2783-P3_SRAN
DAM2M4403-P2
This duplication issue also affects shelves and boards. I’ve attached a list of these cases for reference.
We should discuss this matter with the customer to determine the appropriate steps, as their guidance will be essential.
Thanks,
Indrasan