Snap From HW_Matching.png
Snap From NodeShelf.png
Ooreedo Tunisia
[OT-120] RU Index Is Not Parsing Correct_Huawei RAN Created: 01/Dec/25 Updated: 30/Dec/25 Due: 05/Dec/25 Resolved: 30/Dec/25 |
|
| Status: | Closed |
| Project: | Ooredoo Tunisia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | Indrasan Yadav | Assignee: | Indrasan Yadav |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | AI_All_incidents, Huawei_RAN_OO | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day, 6 hours | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
Snap From HW_Matching.png
Snap From NodeShelf.png
|
| Customer: |
Ooreedo Tunisia
|
| Planned Start: | |
| Planned End: | |
| Actual Start: | |
| Actual End: | |
| Date of Baselining: |
| Description |
|
Hi @Jharna Thakur, As discussed, please review and resolve the issue described below: According to the static sheet (HW_Matching), the RU Index should be parsed as per the rules defined in the sheet. However, it is currently being parsed with the value “-1”. Please refer to the HW_Matching_SS Nodeshelf_SS Request you to kindly check and fix the issue. Thank you, |
| Comments |
| Comment by Bassem Sabbagh [ 02/Dec/25 ] |
|
XML has been shared with Indrasan |
| Comment by Indrasan Yadav [ 09/Dec/25 ] |
|
XML validation completed & data is parsing correct based on available rule in static sheet "HW_MatchingFile". |
| Comment by Indrasan Yadav [ 22/Dec/25 ] |
|
Hi Jharna please commit the code for same. |
| Comment by Jharna Thakur [ 23/Dec/25 ] |
|
code committed |
| Comment by Indrasan Yadav [ 23/Dec/25 ] |
|
Dear @Khaled Khalil, Kindly release an AI patch as code commit has been done by @Jharna Thakur. Thank you, Best regards, |
| Comment by Indrasan Yadav [ 30/Dec/25 ] |
|
Latest AI patch has been deployed on .120 & requested to Basant to replace the static file "HW_MatchingFile" & generate XML & CSV on server and share to me for validation and I validated for same, now issue has been fixed. |
| Comment by Indrasan Yadav [ 30/Dec/25 ] |
|
Checked on staging-DB and now issue has been fixed. |