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-139] Serial Number Duplicity in Physical Inventory Data_Huawei http://jira.mobinets.com/jira/browse/ZKU-139 Zain KSA upgradation ZKU-139 Serial Number Duplicity in Physical Inventory Data_Huawei Task Normal Done Unresolved Indrasan Yadav Indrasan Yadav Tue, 12 Nov 2024 08:39:36 +0200 Wed, 8 Jan 2025 08:01:48 +0200 Fri, 29 Nov 2024 00:00:00 +0200 0 2 0 minutes 5 hours <p>Dear @Navneet Kaur,</p> <p>While reviewing the Huawei_RAN physical inventory data in the dump, I identified cases of serial number duplication for cabinets, shelves, and boards. A sample case for cabinet serial number "21021131694JB1000000" shows it is present in the dumps for multiple nodes, as listed below. The same serial number is also parsed in the XML; relevant snippets are attached for your reference.</p> <p>MBTS-DAM2403-P2_SRAN<br/> TRF2796-P2_SRAN<br/> KHJ2M4304-P3<br/> RIY2783-P3_SRAN<br/> DAM2M4403-P2</p> <p>This duplication issue also affects shelves and boards. I’ve attached a list of these cases for reference.</p> <p>We should discuss this matter with the customer to determine the appropriate steps, as their guidance will be essential.</p> <p>Thanks,<br/> Indrasan</p> <p>Dear @Sandya Sharma,</p> <p>As discussed, please generate an XML for Huawei incorporating the updates we reviewed during our Teams call.</p> <p>The existing rule can be retained with the following modification:</p> <p>• We need to apply the rule for serial number duplicity, similar to the approach used for OmanTel. Specifically, this involves parsing only SRAN nodes where the cabinet or shelf serial number has a duplication issue with another standalone node.</p> <p>Below is an example from the NodeB dump snippet for NEName="DAM2M4403-P2", where a serial number duplication issue occurs. The serial number 21021131694JB1000000 is also present in another SRAN node, NEName="MBTS-DAM2403-P2_SRAN".</p> <p>NodeB: NEName="DAM2M4403-P2"</p> <p>SRAN: NEName="MBTS-DAM2403-P2_SRAN"</p> <p>Please implement this rule while generating the XML.</p> <p>Thank you!</p> <p>Best regards,<br/> Indrasan</p> <p>Dear @Sandya Sharma,</p> <p>As discussed, please do not apply the rule for serial number duplicity.</p> <p>@Ahad Siddiqui, as per our discussion, applying this rule would result in only SRAN nodes being parsed while standalone nodes are ignored. However, the LIC data in these standalone nodes is available technology-wise, and your suggestion on this matter would be highly appreciated.</p> <p>If standalone nodes are ignored:</p> <p>• These nodes will not be parsed into the XML.<br/> • Consequently, they will not be imported into NEP.<br/> • LIC data associated with these nodes will also remain unparsed and unavailable in NEP.</p> <p>Therefore, we need to stop applying this rule for now and ensure that all nodes are parsed as they currently are.</p> <p>Let me know if you have further questions or require clarification.</p> <p>Best regards,<br/> Indrasan</p> <p>As license parsing is required and SN is anyhow duplicate , its important to parse botht he nodes, so this changes not recommneded.</p> Blocks ZKU-94 Actual Start Tue, 12 Nov 2024 00:00:00 +0200 Baseline End Fri, 29 Nov 2024 00:00:00 +0200 Baseline Start Fri, 29 Nov 2024 00:00:00 +0200 Customer Date of Baselining Wed, 13 Nov 2024 11:52:47 +0200 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 Fri, 29 Nov 2024 00:00:00 +0200 Planned Start Fri, 29 Nov 2024 00:00:00 +0200 Rank 0|xtiheh: Rank (Obsolete) 9223372036854775807 VTDirections