Details
-
Type:
Bug
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain 2.X
-
Classification:BUG
Description
Huawei Ran and core path
/product/nep_packages/dataforimporter/Huawei/Dumps/ATAE_U2000
Huawei Transmission path
/product/nep_packages/dataforimporter/Huawei/Dumps/U2000
Attachments
-
- Example for mentioned points.msg
- 593 kB
- Shamim Ahmed
-
- FRS for Physical.docx
- 139 kB
- Shamim Ahmed
-
- Huawei Core Physical connector to be checked in 3.X platform--ZKU-49.msg
- 1.50 MB
- Shamim Ahmed
-
- HuaweiRancore_26Apr24.tar.gz
- 54.46 MB
- Mostafa Kalawoun
-
- HuaweiTx_26Apr24.tar.gz
- 36.92 MB
- Mostafa Kalawoun
-
- Nodes_matching 1_Updated_16-05-2024.xls
- 78 kB
- Shamim Ahmed
-
- Physical_Configuration_Issues.xlsx
- 10 kB
- Diana Hamdouche
-
- Re_ Huawei Core Physical connector to be checked in 3.X platform--ZKU-49.eml
- 1.28 MB
- Diana Hamdouche
-
- RE Huawei Core Physical connector to be checked in 3.X platform.msg
- 466 kB
- Shamim Ahmed
-
- ZKSA_CORE DUMP.rar
- 287 kB
- Shamim Ahmed
-
- ZKSA Node Level FRS.docx
- 17 kB
- Shamim Ahmed
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
assigned to shamim to define the WL
WL = 1-2 mdays from receiving the XML ... Shamim to align with Mostapha to share the dumps with Sandya for XML generation
Please find attached dump with name ZKSA_Core Dump having path::/product/nep_packages/dataforimporter/Huawei/Dumps/ATAE_U2000
Please share the core elements details for the huawei connector .
Already shared on teams
WL = 1 mday to be started and delivered on 9-5
XML shared.
Analysis done.Importing on .14.Some nodes not coming will update static sheet and re import again.
Shamim Ahmed shall we close this Jira ?
HI Sandya,
As discussed please generate new xml considering update node matching sheet and correct Node Type data
will be delivered by 14-05-2024.
XML shared.
FRS need to be modified because data is not coming properly in xml.
Missing Nodes in XML::
DC01_RY1vSPSH02_CloudDB
JD1USCDBH01
JD1vENSBE01
JD1vUIMBE01
JEDUT-BE
RY1USCDBH01
RY1vENSBE01
RY1vUIMBE01
RYDUT_BE
vJED_UDM01_BE_USCDBUDM
vJED_UPCF01_BE_USCDBUPCF
vRYD_UDM01_BE_USCDBUDM
vRYD_UPCF01_BE_USCDBUPCF
vDAM01CG01
vJED01CG01
vRYD01CG01
vDAM01ePDG01
vJED01ePDG01
vRYD01ePDG01
DAM_ZDNS_vEPSN
JED_ZDNS_vEPSN
RYD_ZDNS_vEPSN
dmvccf01
jdccf01
jdvccf01
ryccf01
ryvccf01
DC01_DM1vISBCH03_ISBC
DC01_DM1vSBCH02_SBC
DC01_JD1vSBCH02_SBC
DC01_RY1vSBCH02_SBC
vRYD_CloudUDN01
vJED_SCP01
vJED_SCP01_CSP
vJED_UDM01_BE_CSP
vJED_UDM01_FE_CSP
vJED_UPCF01_BE_CSP
vJED_UPCF01_FE_CSP
vRYD_SCP01_CSP
vRYD_UDM01_BE_CSP
vRYD_UDM01_FE_CSP
vRYD_UPCF01_BE_CSP
vRYD_UPCF01_FE_CSP
AIM_ENS_JD1vENSFE01
AIM_ENS_RY1vENSFE01
DAM Fusionstage
JED Fusionstage
RYD Fusionstage
DAM-IPCLK01
DAM-IPCLK02
DM1IPCLK3000_2G_Act
DM1IPCLK3000_2G_std
DM1IPCLK3000_3G_Act
DM1IPCLK3000_3G_Std
DM1IPCLK3000_4G_Act
DM1IPCLK3000_4G_Std
MD1IPCLK3000_2G_Act
MD1IPCLK3000_2G_Std
MDN1IPCLK3000_3G_Act
MDN1IPCLK3000_3G_Std
MDN1IPCLK3000_4G_Act
MDN1IPCLK3000_4G_Std
R1_DAM_HWIPCLK01
R1_DAM_HWIPCLK02
R1_DAM_HWIPCLK03
R1_DAM_HWIPCLK04
R2_BR_HWIPCLK01
R2_BR_HWIPCLK02
R2_IP Clock
R2_RY1_HWIPCLK01
R2_RY1_HWIPCLK02
R2_RY3_HWIPCLK01
R2_RY3_HWIPCLK02
R2-RY2-HWIPCLK01
R2-RY2-HWIPCLK02
R2-RY4-HWIPCLK01
R2-RY4-HWIPCLK02
R3_MDN_HWIPCLK01
R3_MDN_HWIPCLK02
R3_MDN_HWIPCLK03
R3_MDN_HWIPCLK04
RIY1_IPCLK 2_3G
RIY1_IPCLK 3_3G
RIY-IPCLK01
RIY-IPCLK02
RY1_IPCLK1_TestBed
RY1_IPCLK2_TestBed
RY1IPCLK3000_2G_Act
RY1IPCLK3000_2G_Std
RY1IPCLK3000_3G_Act
RY1IPCLK3000_3G_Std
RY1IPCLK3000_4G_Act
RY1IPCLK3000_4G_Std
jdmrfp01
rymrfp01
dmvmrf01
jdvmrf01
ryvmrf01
jdspg02
jdvspg01
ryspg02
ryvspg01
Dammam SVA3200 Basic
Jeddah SVA3200 Basic
Riyadh SVA3200 Basic
Dammam SVA3200 AC
Jeddah SVA3200 AC
Riyadh SVA3200 AC
vDAM_UPF01
vDAM_UPF02
vDAM_UPF03
vJED_UPF01
vJED_UPF02
vJED_UPF03
vJED_UPF04
vJED_UPF05
vJED_UPF06
vRYD_UPF01
vRYD_UPF02
vRYD_UPF03
vRYD_UPF04
vRYD_UPF05
vJED_UDM01_FE_UDM
vRYD_UDM01_FE_UDM
vDAM_AMF01
vDAM_SMF01
vJED_AMF01
vJED_NCG01
vJED_NRF01
vJED_NSSF01
vJED_SMF01
vJED_SMSF01
vRYD_AMF01
vRYD_NCG01
vRYD_NRF01
vRYD_NSSF01
vRYD_SMF01
vRYD_SMSF01
vJED_UPCF01_FE_UPCF
vRYD_UPCF01_FE_UPCF
vJED_SCP01_USC
vRYD_SCP01_USC
DC01_JD1vSPSH02_CloudDB
SOme rules need to modify,will let you know once get confirmation from DEV
WL is one day.
something will be updated in the frs about netype data , once done will start the work.
There are 2 issues:
1- Sandya to advise why above nodes are missing in XML --> Sandya to share her feedback by 16-5.
2- Netype rule to be provided to AI DEV by shamim --> 16-5
Hi Sandya,
Please find attched rule NE type & Model with Node Matching sheet.Please correct the name of node matching sheet.
deliver by 17-05-2024.
XML shared.
XML validation and import to be completed by 21 (to ensure missing catalogues are created in advance and before the import)
Creating catalogue,will import xml.Hopefully will complete till eod if no issue found found after import.
Hi Sandya,
As discussed please type i.e i5 & i6.
WL is half day.
to be delivered on 22-5
xml shared.
Hi Sandya,
Since inventory is not parsing in NEP therefore find updated FRS regarding Cabinet Shelf & Board.
Please ping for any clarification
WL is one day.
to be started and delivered on 28-5
XML shared.
Hi Sandya,
As checked and discussed please find below point after analyisis::
1-FM Module to be ignored spc for IPCLK
2-Duplicacy for shelf i.e actual with _99
3-Virtual should not have shelf & cabinet only model need to parse
4-In SPS existing both CGP and normal nodes,had to implement to avoid this duplicacy----Discus later
6-For SE2900 FM module has passed instead of board.
7-For IPCLK cabinet Dummpy has not taken instead Virtual Cabinet has teken
8-FOr CCF shelf and board is not coming
9-jdspg02 no board is parsed
10-jdmrfp01 no board is parsed
11-jdcscf01 no board is parsed
12-POWER_SWITCH in mgw has to ignored
WL is one day.
TO be started and delivered on 3-6-2024
XML shared.
checking
Hi Navneet,
Any update?
Thank U!!!
From: Shamim Ahmed
Sent: Tuesday, June 4, 2024 1:29 PM
To: Navneet Kaur <Navneet.Kaur@mobinets.com>
Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Sandya Sharma <Sandya.Sharma@nuiva.com>
Subject: Huawei Core Physical connector to be checked in 3.X platform
Hi Navneet,
For ZKSA core nodes there exist duplicacy of Serial Number..So as to avoid duplicacy physical inventory is parsing for one of the node.
Kindly consult with customer if this is fine.Attached is the the snaphot of hardware from dumps of below nodes.
1-jdmrfp
2-JED-IMS
3-jdcscf
4-jdccf
5-jdspg02
6-jdats01
Thank U!!!
Br
..
Shamim Ahmed
Hi Shamim,
Customer will revert by next week.
If there is any query for any other open Jira like ZKU 27, 34, 45, 36 or 49, it can be shared now only so that customer can give consolidated answer.
Regards,
Navneet.
Dear Khaled,
Getting below error while importing xml on ZKSA 3x testing(.14) platform.
Kindly align someone to check below bugs.
1-Where there is cabinet N68E-22 & Shelf T8280,shelf with RU Index 1 is not parsing getting below error.Although tried to add respect shelf on RU index 0,1 getting below as shown below.
Snapshot share below is for MSS node.
2-For MGW node service frame is not parsing and while adding manually also getting below error.
Customer revert shared with Ahad and Shamim.
Please find below response from customer.
The IMS is the physical device, and the cscf,ats,ccf and mrf is the logical NEs, the duplicate SN board belongs to the same physical board.
Please find below the following:
Considering Core Element Node "DM1MSSH01_CGP":
First of Everything, Make sure that there is no Upgrade on Equipment Model Level.
All Errors are now fixed and no more are available in "Show Errors" Option
This node has as an Equipment Model "MSS" having as "Number of Cabinet" as 1 means it can hold only 1 cabinet type. Hence, "MSS" contains 2 types: "N68E-22" and "Virtual_Cabinet".
As per XML, Cabinet "N68E-22" will only be available under "MSS" Model
Anyhow, I removed the "Virtual_Cabinet" cabinet under "MSS" Model and Configuration is now fine.
Then, if still needed you can Fix the cabinet space using "Put space on cabinet" Option. This will solve the error "T8280 You can't set shelf in RU : 1 shelf size: 5 ,space above : 2 ,space down : 0"
Considering the issue "The Board USIA1 not loaded, the shelf :T8280 hasn't the slot 9_1" , it will be fixed in 2 ways:
A fix will be released related to this message display (in case we have 2 slots 9_1 and 9_10 for example, logic was reading this as same slot.. After fix it will be solved)
Slots can be set as "Back Slot" in "Put Slots On Shelf". Just fix this (disable the "Back Slot" Option and it will appear
"please choose another shelf index, because 1 is already used in this cabinet" Error appears when shelf index 1 is used. The shelf index is not always the same as RU Index such as in our case here RU Index = 6 where Shelf Index =1. You can see it from "Inventory Report"
One last thing, For "N68E-22", I removed a space configured on it via DB Query, so its format will be changed, However, after Restart it will remain as before. @Sanju Yadav as already informed , once patch is released, we need to restart the server to reflect the query into Client.
Considering MGW Core Element Node "DM1MGWH01":
Same Points are also applicabale here
You need to Re-Import Same XML for both nodes's physical Configuration to clean the error "The service frame You can't set shelf in RU : 1 shelf size: 10 ,space above : 0 ,space down : 1" in this case
"cannot add more shelfs of this type as the maximum number allowed is reached" Error appears when shelf index 1 is used. Maximum Per Equipment for this shelf is 2. Means, you cannot exceed this value that why you got thie error
Patch is needed: 3.7.1.577 and NEP Restart is Required
WL = 1 mday
Please add the final closure date of the ticket
Hi Sandya,
Please do the needful.
1-RU index showing 1 & -9.It has to be 1,6,11 and so on.
2-Please Ignore Board type Code FMModule
3-In SE2900 no board is parsed only FMmodule is parsed.
Snapshot shared on teams.
WL is one day.
Dear Sandya,
To avoid duplicacy please align physical configuration to main node as shown in attached mail,
will be deliver by 14-06-2024
XML shared
SE2900 model inventory is not parsed in NEP.If there exist duplication of SN.KIndly share the corelated nodes.If not please check and do the needful.
will confirm by today.
shared the nodes for duplicate serial numbers.
For error on Wquipment Model issue raised to Diana--Jira::ZKU-55
to be checked and assigned