Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
Description
Dear @Bassem Sabbagh,
As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:
Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference).
Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900".
Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900".
Best regards,
Indrasan
Attachments
Issue Links
- blocks
-
ZKU-94
Huawei RAN_Dumps , XML and NEP data Validation
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 1 hour
-
Dear @Bassem Sabbagh,
As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:
Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference).
Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900".
Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900".
Best regards,
Indrasan
-
- Time Spent:
- 2 hours
-
Validate the XML and data was coming wrong so again confirmed to @Sandya to fix it.
again validate the revised XML and now it is parsing correctly.
