[ZKU-263] Site Id Not Parsing For NodeB_Nokia On Production Created: 04/Mar/25 Updated: 19/Mar/25 Due: 07/Mar/25 |
|
Status: | Done |
Project: | Zain KSA upgradation |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | 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, 1 hour, 30 minutes | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() ![]() |
Customer: |
Zain KSA 3.X
|
Planned Start: | |
Planned End: | |
Actual Start: | |
Date of Baselining: |
Comments |
Comment by Indrasan Yadav [ 04/Mar/25 ] |
Dear @Bassem Sabbagh, I have noticed that the Site ID is not parsing for NodeB (Nokia) in the XML, and the same issue is also present in NEP. It seems that the node name is not parsing, which is why it is not appearing, as it depends on the node name. As I recall, I had shared a static sheet titled “RAN_Node Name_Matching” with #Juned to assist in parsing the node name for NodeB (Nokia). @Sandya Sharma, could you please check and confirm whether the required static sheet (“RAN_Node Name_Matching”) is available in production before XML generation? Thank you, |
Comment by Indrasan Yadav [ 04/Mar/25 ] |
I have attached that require static sheet here, please use this. |
Comment by Bassem Sabbagh [ 10/Mar/25 ] |
WL = 0.5 mday , to be started and delivered on 12-3 |
Comment by Sandya Sharma [ 11/Mar/25 ] |
Pls check full xml and confirm. |
Comment by Indrasan Yadav [ 12/Mar/25 ] |
As discussed during our Teams call, most of the issues have been resolved, and the names are being parsed correctly for the NodeB in NPSNodeB, as per the static sheet. However, for approximately 405 nodes, the names are appearing blank, whereas they should be parsed as the same node ID if they are not available in static sheet, which is consistent with UAT. Please check and confirm. |
Comment by Bassem Sabbagh [ 12/Mar/25 ] |
start working on it on 12-3 the second half |
Comment by Sandya Sharma [ 13/Mar/25 ] |
commit done. |
Comment by Indrasan Yadav [ 17/Mar/25 ] |
Dear @Khaled Khalil, Could you please release AI patch for code commit done by @Sandya Sharma. Thank you |
Comment by Indrasan Yadav [ 17/Mar/25 ] |
++looping @Indrasan Yadav Regards, This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please delete it from your system and notify the sender immediately. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Build SUCCESS Date of build: Mon, 17 Mar 2025 10:06:02 +0200 |
Comment by Indrasan Yadav [ 17/Mar/25 ] |
Dear @ABHINAV PARASHAR, Could you please deploy the mentioned patch on production & after deploying this patch please generate full XML & share with csv. Thank you |
Comment by Indrasan Yadav [ 18/Mar/25 ] |
Dear Indrasan, Full XML generated on ZainKSA prod server after deploy latest AI patch. NETWORKS TRANSFORMED Abhinav Parashar| Sr. System Engineer |
Comment by Indrasan Yadav [ 18/Mar/25 ] |
Now, I checked in latest XML which is available on production server and there is no any blank data is parsing in column "name" under "npsnodeb". So, as per XML level it has been fixed once import will done on production need to validate the same. (As currently XML import is not happening on production due to some testing ongoing there) |
Comment by Indrasan Yadav [ 19/Mar/25 ] |
After confirmation with @Bassem/@Ahad manually full XML import was done on production. Then checked and found that now issue has been fix for Nokia NodeB(405) which has been now imported in NEP. |