Hi Indrasan,

As discussed and agreed please create JIRA and provide rule for parse the Node name from userLabel.

Check if its affect the License , in that case you have to provide rule for mapping with the License.

Regards,
Ahad Siddiqui

A JIRA has been created for this, and work will commence once @Bassem provides the plan.

Dear @Bassem Sabbagh,

As discussed, I am assigning this JIRA to @Juned Ali to parse the node name from the dump to XML for node types BSC, SRAN, and eNodeB only, as the node name is available for these specific node types.

Please find below the snippet for your reference regarding the node types to parse the node name:

BSC: Take the value of <p name="systemTitle"> from class=HW to parse the node name.

SRAN: Take the value of <p name="userLabel"> from class=HW to parse the node name.

eNodeB: Take the value of <p name="userLabel"> from class=HW to parse the node name.

(Note: For eNodeB, only one node name, “FSM,” is showing for all nodes. @Ahad Siddiqui, please advise if we should parse the same node name for all different node IDs or need to confirm with customer?)

@Juned Ali, please apply this rule and share the XML once completed.

Best regards,
Indrasan
____________________
Same mail is attached here with file name: "26-12-2024_1st Mail"

delivery date :- 27-12-2024 EOD

Xml and csv delivered

Dear @Juned Ali,

Kindly use the latest dump that I shared with you via Teams and share the XML again.

Additionally, for the node type "NodeB," please parse the Node name from the 3G LIC dump (available in CSV format, as shown in the snippet below for your reference).

Note that the Node ID will match the value in column ‘C,’ excluding the “PLMN-PLMN/” prefix.

Thanks//
Indrasan

Dear @Juned Ali,

Kindly parse the node name for RNC from the RNC dump, as per the snippet provided below.

@Ahad Siddiqui please confirm about the eNodeB case where the node node is consistent for all as "FSM."

Best regards,
Indrasan

Indrasan Yadav provide a clear rule and update the FRS then assign this ticket to Juned

Dear @Juned Ali,

Please find attached updated FRS for the same. (Here, I didn’t add the rule for eNodeB as @Ahad Siddiqui confirmation is pending for same)

Best regards,
Indrasan

no confirmation pending with Ahad

WL = 1 mday ....to be started on 31-12

As discusssed first we create Physical Then we creat License on basis of nodeName mapping betweeen Physical Dump and License dump but you want that name for Physical inventory should be taken from licesnes. For your kind information we are first creating physical so how we can simultaneosuly parse license dump to get node name.I Suggest rule created for nodeName have to be revised!!

Hi Juned,

I checked that the BSC and SRAN node names are being parsed correctly, as I checked all BSC and 5 sample SRAN cases (MRBTS-6200493, MRBTS-777053, MRBTS-6200492, MRBTS-411389, MRBTS-6200495).

For the remaining nodes, I will provide confirmation on Monday:

eNodeB: Confirmation pending from Ahad's end.
RNC/NodeB: I will discuss on Monday whether the given rule will be applicable.
BTS: No rule is applicable.

Dear @Juned Ali,

I have verified that the BSC and SRAN node names are being parsed correctly, as I reviewed all BSC and 5 sample SRAN cases (MRBTS-6200493, MRBTS-777053, MRBTS-6200492, MRBTS-411389, MRBTS-6200495).

@Ahad Siddiqui, could you kindly confirm the status of the eNodeB as discussed in the previous email?
Additionally, please confirm the status of RNC & NodeB for which the rule was provided to parse the node name from the License dump, as it seems to be impossible according to @Juned Ali. Please advise on this matter.

Best regards,
Indrasan

Dear @Juned Ali,

I discussed and confirmed with @Ahad Siddiqui, please parse the value “FSM” for eNodeB, as it is the correct value and was previously parsed in 2.x. The rule has also been added in the FRS.

Additionally, the rule for NodeB and RNC has been added in the FRS. Please use the attached static sheet to parse the node name for both NodeB and RNC.

Best regards,
Indrasan

WL = 1 mday, to be started 8-1 and delivered by 9-1

to be started on 7-1 since the ZKU-230 is on hold

to be delivered on 8-1

xml and csv shared !!

The node names are now being parsed correctly for NodeB, RNC (as per the RAN node matching sheet), BSC, SRAN, and eNodeB, in accordance with the rules specified in the FRS.

@Juned, please commit the code for same.

ok i will commit the code

Dear @Juned Ali,

Now, node name is appearing as per given rule except below 4080 nodes (List attached) where node name is not available in inventory & license dump.

Row Labels Count of Node type
BTS 3661
eNodeB 3
NodeB 416
(blank)
Grand Total 4080

@Juned Ali, please commit the code for same.

Best regards,
Indrasan

@Juned: Please confirm if code committed and then close

CODE COMMITTED ++

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.