We are now closing this child JIRA as it pertains to an individual issue.

As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.

commit done.

Now, serial number of cabinet & shelf is appearing in NEP.

@Sandya, please proceed to commit the code for same changes.

The required attribute "nodeId" is now under the CSV "nodecabinet" in the XML.

The XML (2024-12-09-09.33.09_ZainKsa) import is currently ongoing on .14. Once the import is complete, I will verify whether the serial number has been successfully imported.

Dear @Sandya Sharma,

As discussed, please proceed with the necessary updates.

We need to add an additional attribute, "nodeId", under the CSV nodecabinet in Huawei_RAN XML.

Thank you for your support.

Best regards,
Indrasan

Dear Ahad,

There is no specific rule for Zain KSA, it's the same for all:
• The cabinets shall have the node id available, otherwise NEP is not able to identify the cabinet is belong which node. If you have cabinets available in NEP without related details serial number, etc.)
o either while importing slots if no cabinet and shelves are available, NEP try to create a default based on the equipment definition
o Or there is a default physical configuration template for this type
• The shelves shall have cabinets details
• the slots shall have nodeid and shelf details (if shelf details not available NEP try to map it to cabinet 1 and shelf 1)
• the board shall have slot details
• the port shall have bord details
Thank you,
Hassan

Dear Mustafa,

Please confirm if this rule is applicable only for cabinets , or for shelves , boards and node interface level, also confirm why this rule is not same among different operators , for example in Omantel there is no nodeid but still serial number getting imported for shelves,boards as I checked.

Also please confirm the significance of Id in the XML , basis on id NEP allowing to import the cabinet itself but not allowing to import its associated data.

+++Hassan

@Indrasan Yadav : You please ask AI DEV to include nodeId.

Regards,
Ahad Siddiqui

Dear @Indrasan Yadav,

After reviewing the XML and the logic implemented for the cabinets import, we identified an issue in the XML.

Data related to each nodeCabinet (such as SerialNumber in this case) is being imported based on the nodeId. If we check the nodeCabinets folder, we can see that the nodeId column is missing in this XML (as shown in the attached snippet)

However, if we check other XML files we notice that the nodeCabinets folder contains the nodeId column, (as shown in the attached snippet)

In conclusion, the SerialNumber is not being imported into NEP because the nodeId is missing in the XML.

Regards,
Mustapha Al Hage

Dear @Khaled Khalil,

I hope this email finds you well.

Could you kindly assign a DEV resource to investigate the issue where the serial numbers of cabinets and shelves are not being imported into NEP, despite being available in the XML?

Details for Reference:
• XML Snippet of Nodecabinet & Nodeshelf:

NEP Report Snippet of Cabinet & Shelf:
(Currently, no serial numbers are appearing in the Cabinet & Shelf report.)

And, when I tried to investigate in error report there are not any errors are showing related to this.

Please let me know if any additional information is required to resolve this issue.

Thank you for your support.

Best regards,
Indrasan