[ZKU-233] Need To Implement Rule To Disregard Node With NEType=MBTS_Huawei Created: 02/Jan/25 Updated: 08/Jan/25 Due: 06/Jan/25 |
|
| Status: | Done |
| Project: | Zain KSA upgradation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | Indrasan Yadav | Assignee: | Indrasan Yadav |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | AI_All_incidents, ZAINKSAAUDIT, ZAINKSAUAT | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day, 2 hours, 30 minutes | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Customer: |
Zain KSA 3.X
|
||||||||
| Planned Start: | |||||||||
| Planned End: | |||||||||
| Actual Start: | |||||||||
| Date of Baselining: | |||||||||
| Description |
|
Dear @Bassem Sabbagh, As discussed in our meeting with CyberMak, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below: Note: This rule will apply to all nodes where NEType="MBTS" appears (see example for reference). Example: Two examples of nodes where NEType="MBTS" is displayed are: • NEName="MBTS-AFL0515-P2_SRAN" Best regards, |
| Comments |
| Comment by Bassem Sabbagh [ 02/Jan/25 ] |
|
Assigned to dhmendra to define the WL |
| Comment by Dharmendra Patel [ 03/Jan/25 ] |
|
xml shared!! |
| Comment by Indrasan Yadav [ 06/Jan/25 ] |
|
Hi Dharmendra, I have validated the shared XML (2025-01-03-05.08.11_ZainKsa) and here are my findings: No nodes with NEType=MBTS are parsing in npsranbs. "MBTS" is not appearing in ran-bs-type. No nodes with MBTS NEType are parsing in the cabinet section (so, consider not parsing them in shelf/boards). No nodes with MBTS type are parsing in nelicenses. In the radioantenna section, I checked a sample of MBTS type nodes (listed below), and they are not available in the radioantenna CSV: DAM2472 Please commit the code for the same. Best regards, |
| Comment by Dharmendra Patel [ 06/Jan/25 ] |
|
code commit done. |
| Comment by Indrasan Yadav [ 06/Jan/25 ] |
|
We are now closing this child JIRA as it pertains to an individual issue. As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA. |