Dear @Ahad Siddiqui,

As discussed, the current Nokia inventory dumps are missing essential classes required for parsing node types effectively. We should confirm with the customer to ensure they can provide an updated dump that includes these classes for a more comprehensive data parse.

Currently, the rule allows parsing only three node types: BSC, RNC, and SRAN, with SRAN covering BTS, NodeB, and eNodeB. However, to align with the parsing approach used in other connectors, we should aim to parse all node types individually, specifically BTS, BSC, RNC, NodeB, eNodeB, and SRAN. (As this also suggested by you & @Bassem Sabbagh)

Thank you for your support in confirming this with the customer.

Best regards,
Indrasan

Hi navneet,

This was raised to customer in consolidated sheet.

As discussed with Bassem, Node will be imported as SRAN : Anything to do here?

Please update ?

This is pending with the customer, which is why we created JIRA tickets ZKU-145 and ZKU-156, based on the current dump availability after confirmation with @Bassem.

This issue has been highlighted to customer, and giving comment here as suggested by @Bassem.(Mail attached also for reference with attached file name of "Mail_20-03-2025")
_________________________________________________________________________________________________
Owner: Mubarak Ahmed Altamini
Closure date: Zain TBC
Mail details:
Sent By : Ahad Siddiqui
Sent to : Walid Boulos
Date&Time : Tue 26-11-2024 18:15 (IST)
Status: In progress
_________________________________________________________________________________________________
Same is available on sharepoint on below path:

Sharepoint path: Project documents> Zain KSA 3.X> Dump Issues> Dump_Status_ZAIN_KSA_Summary (Excel sheet_File name)> Overall Status (TAB) at row serial number '14'

I am going to close this JIRA as this issue is already highlighted to customer & updated on sharepoint also.