[ZKU-264] Need To Modify The Rule To Parse LIC ID_Huawei Created: 05/Mar/25 Updated: 10/Apr/25 Due: 10/Mar/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: | 1 |
Labels: | AI_All_incidents, ZAINKSAAUDIT, ZAINKSAUAT | ||
Remaining Estimate: | 0 minutes | ||
Time Spent: | 3 days, 30 minutes | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() |
Customer: |
Zain KSA 3.X
|
Planned Start: | |
Planned End: | |
Actual Start: | |
Date of Baselining: |
Description |
Dear @Bassem Sabbagh, I would like to request the assignment of an AI development resource to implement the updated rules for parsing licenses for Huawei, as detailed below. Current Scenario: Currently, all LIC IDs are being parsed in XML according to the provided dump, as described in my previous email in Updated Case: To ensure all licenses can be imported into NEP, we need to add a condition to make each LIC ID unique. SRAN Controller Case: Example: In the SRAN Controller node DM1MBSCH01, the same LIC ID is currently parsed with the same license details in the XML, but for different technologies. We need to modify the LIC ID as follows: Current XML: In NEP, only the 3G license is being imported, while the 2G license is ignored. NEP Import: Other Node Case: In this case, there are two licenses with the same LIC ID and LIC details for one node, yet only one is being imported into NEP. NEP Import: Note: This rule is needed to add in the existing rule there should no changes in existing data parsing. And it will apply for those cases where duplicate LIC ID/Licences details available for a same node ID. Thank you for your attention to this matter. I look forward to your prompt response. Best regards, |
Comments |
Comment by Bassem Sabbagh [ 10/Mar/25 ] |
Assigned to Jharna to define the WL |
Comment by Jharna Thakur [ 13/Mar/25 ] |
wl-1.5 days |
Comment by Bassem Sabbagh [ 13/Mar/25 ] |
to be started on 17-3-25 |
Comment by Jharna Thakur [ 17/Mar/25 ] |
Kindly share the dumps related to it |
Comment by Indrasan Yadav [ 17/Mar/25 ] |
Require dump is attached here for your reference. |
Comment by Jharna Thakur [ 17/Mar/25 ] |
Kindly share the remaining dump data as well, as the provided dumps are not generating any licenses. |
Comment by Indrasan Yadav [ 18/Mar/25 ] |
Hi Jharna, require dump has been shared to you now. |
Comment by Bassem Sabbagh [ 18/Mar/25 ] |
to be delivered by latest 19-3 the first half |
Comment by Jharna Thakur [ 18/Mar/25 ] |
Xml has been shared |
Comment by Indrasan Yadav [ 19/Mar/25 ] |
Hi Jharna, please commit the code. |
Comment by Jharna Thakur [ 19/Mar/25 ] |
Code has been committed |
Comment by Indrasan Yadav [ 19/Mar/25 ] |
Dear @Khaled Khalil, Could you please generate an AI patch as code commit has been done by @Jharna Thakur for the same. Thank you |
Comment by Indrasan Yadav [ 24/Mar/25 ] |
From: Khaled Khalil <Khaled.Khalil@nuiva.com> Dear Bassem, I already created a patch yesterday as below, do you need another new one? Build 3.7.2.24 (19-Mar-2025 4:03:59 PM) |
Comment by Indrasan Yadav [ 24/Mar/25 ] |
From: Indrasan Yadav <Indrasan.Yadav@nuiva.com> Dear @ABHINAV PARASHAR, Please deploy mentioned patch on production and after successfully deploy it also generate full xml on same platform. Build 3.7.2.24 (19-Mar-2025 4:03:59 PM) Thank you |
Comment by Indrasan Yadav [ 24/Mar/25 ] |
Dear Indrasan, Build 3.7.2.24 Patch deployed and 2025-03-20-01.31.54_ZainKsa.xml full XML file generated after deployment. NETWORKS TRANSFORMED Abhinav Parashar| Sr. System Engineer |
Comment by Indrasan Yadav [ 24/Mar/25 ] |
Require data is seems parsing correctly in XML on production also. I need to import full XML (2025-03-20-01.31.54_ZainKsa.xml) on production by today EOD because full xml import is not happening automatically since last few days. |
Comment by Indrasan Yadav [ 25/Mar/25 ] |
Above mentioned XML imported manually on production and now all data related to LIC are parsing in NEP correctly. |