Dear @Navneet Kaur,

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.

MBTS-DAM2403-P2_SRAN
TRF2796-P2_SRAN
KHJ2M4304-P3
RIY2783-P3_SRAN
DAM2M4403-P2

This duplication issue also affects shelves and boards. I’ve attached a list of these cases for reference.

We should discuss this matter with the customer to determine the appropriate steps, as their guidance will be essential.

Thanks,
Indrasan

Dear @Sandya Sharma,

As discussed, please generate an XML for Huawei incorporating the updates we reviewed during our Teams call.

The existing rule can be retained with the following modification:

• 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.

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".

NodeB: NEName="DAM2M4403-P2"

SRAN: NEName="MBTS-DAM2403-P2_SRAN"

Please implement this rule while generating the XML.

Thank you!

Best regards,
Indrasan

Dear @Sandya Sharma,

As discussed, please do not apply the rule for serial number duplicity.

@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.

If standalone nodes are ignored:

• These nodes will not be parsed into the XML.
• Consequently, they will not be imported into NEP.
• LIC data associated with these nodes will also remain unparsed and unavailable in NEP.

Therefore, we need to stop applying this rule for now and ensure that all nodes are parsed as they currently are.

Let me know if you have further questions or require clarification.

Best regards,
Indrasan