Mobinets-JIRA

Mobinets-JIRA http://jira.mobinets.com/jira This file is an XML representation of an issue en-us

6.1.4

6159

19-11-2013

[ZKU-49] Huawei Core Physical connector to be checked in 3.X platform http://jira.mobinets.com/jira/browse/ZKU-49 Zain KSA upgradation <p>Huawei Ran and core path<br/> /product/nep_packages/dataforimporter/Huawei/Dumps/ATAE_U2000</p> <p>Huawei Transmission path<br/> /product/nep_packages/dataforimporter/Huawei/Dumps/U2000</p> ZKU-49

Huawei Core Physical connector to be checked in 3.X platform

Bug Normal Done Unresolved Shamim Ahmed Navneet Kaur AI_All_incidents Wed, 24 Apr 2024 04:59:20 +0300 Fri, 29 Nov 2024 08:33:08 +0200 Mon, 29 Apr 2024 00:00:00 +0300 1 6 0 minutes 1 week, 1 day, 1 hour <p>to be checked and assigned </p> <p>assigned to shamim to define the WL</p> <p>WL = 1-2 mdays from receiving the XML ... Shamim to align with Mostapha to share the dumps with Sandya for XML generation</p> <p>Please find attached dump with name ZKSA_Core Dump having path::/product/nep_packages/dataforimporter/Huawei/Dumps/ATAE_U2000</p> <p>Please share the core elements details for the huawei connector .</p> <p>Already shared on teams </p> <p>WL = 1 mday to be started and delivered on 9-5</p> <p>XML shared.</p> <p>Analysis done.Importing on .14.Some nodes not coming will update static sheet and re import again.</p> <p><a href="http://jira.mobinets.com/jira/secure/ViewProfile.jspa?name=sahmed" class="user-hover" rel="sahmed">Shamim Ahmed</a> shall we close this Jira ?</p> <p>HI Sandya,</p> <p>As discussed please generate new xml considering update node matching sheet and correct Node Type data</p> <p>will be delivered by 14-05-2024.</p> <p>XML shared.</p> <p>FRS need to be modified because data is not coming properly in xml.</p> <p>Missing Nodes in XML::</p> <p>DC01_RY1vSPSH02_CloudDB<br/> JD1USCDBH01<br/> JD1vENSBE01<br/> JD1vUIMBE01<br/> JEDUT-BE<br/> RY1USCDBH01<br/> RY1vENSBE01<br/> RY1vUIMBE01<br/> RYDUT_BE<br/> vJED_UDM01_BE_USCDBUDM<br/> vJED_UPCF01_BE_USCDBUPCF<br/> vRYD_UDM01_BE_USCDBUDM<br/> vRYD_UPCF01_BE_USCDBUPCF<br/> vDAM01CG01<br/> vJED01CG01<br/> vRYD01CG01<br/> vDAM01ePDG01<br/> vJED01ePDG01<br/> vRYD01ePDG01<br/> DAM_ZDNS_vEPSN<br/> JED_ZDNS_vEPSN<br/> RYD_ZDNS_vEPSN<br/> dmvccf01<br/> jdccf01<br/> jdvccf01<br/> ryccf01<br/> ryvccf01<br/> DC01_DM1vISBCH03_ISBC<br/> DC01_DM1vSBCH02_SBC<br/> DC01_JD1vSBCH02_SBC<br/> DC01_RY1vSBCH02_SBC<br/> vRYD_CloudUDN01<br/> vJED_SCP01<br/> vJED_SCP01_CSP<br/> vJED_UDM01_BE_CSP<br/> vJED_UDM01_FE_CSP<br/> vJED_UPCF01_BE_CSP<br/> vJED_UPCF01_FE_CSP<br/> vRYD_SCP01_CSP<br/> vRYD_UDM01_BE_CSP<br/> vRYD_UDM01_FE_CSP<br/> vRYD_UPCF01_BE_CSP<br/> vRYD_UPCF01_FE_CSP<br/> AIM_ENS_JD1vENSFE01<br/> AIM_ENS_RY1vENSFE01<br/> DAM Fusionstage<br/> JED Fusionstage<br/> RYD Fusionstage<br/> DAM-IPCLK01<br/> DAM-IPCLK02<br/> DM1IPCLK3000_2G_Act<br/> DM1IPCLK3000_2G_std<br/> DM1IPCLK3000_3G_Act<br/> DM1IPCLK3000_3G_Std<br/> DM1IPCLK3000_4G_Act<br/> DM1IPCLK3000_4G_Std<br/> MD1IPCLK3000_2G_Act<br/> MD1IPCLK3000_2G_Std<br/> MDN1IPCLK3000_3G_Act<br/> MDN1IPCLK3000_3G_Std<br/> MDN1IPCLK3000_4G_Act<br/> MDN1IPCLK3000_4G_Std<br/> R1_DAM_HWIPCLK01<br/> R1_DAM_HWIPCLK02<br/> R1_DAM_HWIPCLK03<br/> R1_DAM_HWIPCLK04<br/> R2_BR_HWIPCLK01<br/> R2_BR_HWIPCLK02<br/> R2_IP Clock<br/> R2_RY1_HWIPCLK01<br/> R2_RY1_HWIPCLK02<br/> R2_RY3_HWIPCLK01<br/> R2_RY3_HWIPCLK02<br/> R2-RY2-HWIPCLK01<br/> R2-RY2-HWIPCLK02<br/> R2-RY4-HWIPCLK01<br/> R2-RY4-HWIPCLK02<br/> R3_MDN_HWIPCLK01<br/> R3_MDN_HWIPCLK02<br/> R3_MDN_HWIPCLK03<br/> R3_MDN_HWIPCLK04<br/> RIY1_IPCLK 2_3G<br/> RIY1_IPCLK 3_3G<br/> RIY-IPCLK01<br/> RIY-IPCLK02<br/> RY1_IPCLK1_TestBed<br/> RY1_IPCLK2_TestBed<br/> RY1IPCLK3000_2G_Act<br/> RY1IPCLK3000_2G_Std<br/> RY1IPCLK3000_3G_Act<br/> RY1IPCLK3000_3G_Std<br/> RY1IPCLK3000_4G_Act<br/> RY1IPCLK3000_4G_Std<br/> jdmrfp01<br/> rymrfp01<br/> dmvmrf01<br/> jdvmrf01<br/> ryvmrf01<br/> jdspg02<br/> jdvspg01<br/> ryspg02<br/> ryvspg01<br/> Dammam SVA3200 Basic<br/> Jeddah SVA3200 Basic<br/> Riyadh SVA3200 Basic<br/> Dammam SVA3200 AC<br/> Jeddah SVA3200 AC<br/> Riyadh SVA3200 AC<br/> vDAM_UPF01<br/> vDAM_UPF02<br/> vDAM_UPF03<br/> vJED_UPF01<br/> vJED_UPF02<br/> vJED_UPF03<br/> vJED_UPF04<br/> vJED_UPF05<br/> vJED_UPF06<br/> vRYD_UPF01<br/> vRYD_UPF02<br/> vRYD_UPF03<br/> vRYD_UPF04<br/> vRYD_UPF05<br/> vJED_UDM01_FE_UDM<br/> vRYD_UDM01_FE_UDM<br/> vDAM_AMF01<br/> vDAM_SMF01<br/> vJED_AMF01<br/> vJED_NCG01<br/> vJED_NRF01<br/> vJED_NSSF01<br/> vJED_SMF01<br/> vJED_SMSF01<br/> vRYD_AMF01<br/> vRYD_NCG01<br/> vRYD_NRF01<br/> vRYD_NSSF01<br/> vRYD_SMF01<br/> vRYD_SMSF01<br/> vJED_UPCF01_FE_UPCF<br/> vRYD_UPCF01_FE_UPCF<br/> vJED_SCP01_USC<br/> vRYD_SCP01_USC<br/> DC01_JD1vSPSH02_CloudDB</p> <p>SOme rules need to modify,will let you know once get confirmation from DEV</p> <p>WL is one day.</p> <p>something will be updated in the frs about netype data , once done will start the work.</p> <p>There are 2 issues:<br/> 1- Sandya to advise why above nodes are missing in XML --> Sandya to share her feedback by 16-5.<br/> 2- Netype rule to be provided to AI DEV by shamim --> 16-5</p> <p>Hi Sandya,</p> <p>Please find attched rule NE type & Model with Node Matching sheet.Please correct the name of node matching sheet.</p> <p>deliver by 17-05-2024.</p> <p>XML shared.</p> <p>XML validation and import to be completed by 21 (to ensure missing catalogues are created in advance and before the import)</p> <p>Creating catalogue,will import xml.Hopefully will complete till eod if no issue found found after import.</p> <p>Hi Sandya,</p> <p>As discussed please type i.e i5 & i6.</p> <p>WL is half day.</p> <p>to be delivered on 22-5</p> <p>xml shared.</p> <p>Hi Sandya,<br/> Since inventory is not parsing in NEP therefore find updated FRS regarding Cabinet Shelf & Board.<br/> Please ping for any clarification</p> <p>WL is one day.</p> <p>to be started and delivered on 28-5</p> <p>XML shared.</p> <p>Hi Sandya,</p> <p>As checked and discussed please find below point after analyisis::<br/> 1-FM Module to be ignored spc for IPCLK<br/> 2-Duplicacy for shelf i.e actual with _99<br/> 3-Virtual should not have shelf & cabinet only model need to parse<br/> 4-In SPS existing both CGP and normal nodes,had to implement to avoid this duplicacy----Discus later<br/> 6-For SE2900 FM module has passed instead of board.<br/> 7-For IPCLK cabinet Dummpy has not taken instead Virtual Cabinet has teken<br/> 8-FOr CCF shelf and board is not coming<br/> 9-jdspg02 no board is parsed<br/> 10-jdmrfp01 no board is parsed<br/> 11-jdcscf01 no board is parsed<br/> 12-POWER_SWITCH in mgw has to ignored</p> <p>WL is one day.</p> <p>TO be started and delivered on 3-6-2024</p> <p>XML shared.</p> <p>checking</p> <p>Hi Navneet,</p> <p>Any update?</p> <p>Thank U!!!</p> <p>From: Shamim Ahmed <br/> Sent: Tuesday, June 4, 2024 1:29 PM<br/> To: Navneet Kaur <Navneet.Kaur@mobinets.com><br/> Cc: Ahad Siddiqui <Ahad.Siddiqui@mobinets.com>; Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Sandya Sharma <Sandya.Sharma@nuiva.com><br/> Subject: Huawei Core Physical connector to be checked in 3.X platform</p> <p>Hi Navneet,</p> <p>For ZKSA core nodes there exist duplicacy of Serial Number..So as to avoid duplicacy physical inventory is parsing for one of the node.<br/> Kindly consult with customer if this is fine.Attached is the the snaphot of hardware from dumps of below nodes.</p> <p>1-jdmrfp<br/> 2-JED-IMS<br/> 3-jdcscf<br/> 4-jdccf<br/> 5-jdspg02<br/> 6-jdats01</p> <p>Thank U!!!</p> <p>Br<br class="atl-forced-newline" />..<br/> Shamim Ahmed</p> <p>Hi Shamim,</p> <p>Customer will revert by next week.</p> <p>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.</p> <p>Regards,</p> <p>Navneet.</p> <p>Dear Khaled,</p> <p>Getting below error while importing xml on ZKSA 3x testing(.14) platform.<br/> Kindly align someone to check below bugs.</p> <p>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.<br/> Snapshot share below is for MSS node.<br/> 2-For MGW node service frame is not parsing and while adding manually also getting below error.</p> <p>Customer revert shared with Ahad and Shamim.</p> <p>Please find below response from customer.</p> <p>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.</p> <p>Please find below the following:<br/> Considering Core Element Node "DM1MSSH01_CGP":<br/> First of Everything, Make sure that there is no Upgrade on Equipment Model Level.<br/> All Errors are now fixed and no more are available in "Show Errors" Option<br/> 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". <br/> As per XML, Cabinet "N68E-22" will only be available under "MSS" Model<br/> Anyhow, I removed the "Virtual_Cabinet" cabinet under "MSS" Model and Configuration is now fine.<br/> 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"<br/> Considering the issue "The Board USIA1 not loaded, the shelf :T8280 hasn't the slot 9_1" , it will be fixed in 2 ways:<br/> 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)<br/> Slots can be set as "Back Slot" in "Put Slots On Shelf". Just fix this (disable the "Back Slot" Option and it will appear<br/> "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"<br/> 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.</p> <p>Considering MGW Core Element Node "DM1MGWH01":<br/> Same Points are also applicabale here<br/> 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<br/> "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</p> <p>Patch is needed: 3.7.1.577 and NEP Restart is Required</p> <p>WL = 1 mday</p> <p>Please add the final closure date of the ticket</p> <p>Hi Sandya,</p> <p>Please do the needful.</p> <p>1-RU index showing 1 & -9.It has to be 1,6,11 and so on.<br/> 2-Please Ignore Board type Code FMModule<br/> 3-In SE2900 no board is parsed only FMmodule is parsed.</p> <p>Snapshot shared on teams.</p> <p>WL is one day.</p> <p>Dear Sandya,</p> <p>To avoid duplicacy please align physical configuration to main node as shown in attached mail,</p> <p>will be deliver by 14-06-2024</p> <p>XML shared</p> <p>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.</p> <p>will confirm by today.</p> <p>shared the nodes for duplicate serial numbers.</p> <p>For error on Wquipment Model issue raised to Diana--Jira::<a href="http://jira.mobinets.com/jira/browse/ZKU-55" title="Huawei Core Physical connector to be checked in 3.X platform" class="issue-link" data-issue-key="ZKU-55">ZKU-55</a></p> Actual Start Wed, 22 May 2024 00:00:00 +0300 Baseline End Mon, 29 Apr 2024 00:00:00 +0300 Baseline Start Mon, 29 Apr 2024 00:00:00 +0300 Classification Customer Date of Baselining Mon, 27 May 2024 05:14:50 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Mon, 29 Apr 2024 00:00:00 +0300 Planned Start Mon, 29 Apr 2024 00:00:00 +0300 Rank 0|xti9d5: Rank (Obsolete) 9223372036854775807 VTDirections