[LS-851] AZRC | Addinfo missing for Huawei SRANBS nodes in NEP Created: 30/Dec/25  Updated: 06/Mar/26  Due: 06/Jan/26  Resolved: 06/Feb/26

Status: Ready for QA
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Aurobinda Panda Assignee: Aurobinda Panda
Resolution: Not Fixed Votes: 0
Labels: service_routing
Remaining Estimate: 0 minutes
Time Spent: 3 days, 4 hours, 15 minutes
Original Estimate: Not Specified

Attachments: JPEG File Add info of SRABS nodes.jpg     JPEG File Interface Details under RAN manager.jpg    
Issue Links:
Blocks
Customer:
Azerconnect
Planned Start:
Planned End:
Complexity: High
Severity: Major
Product: NEP
REQUESTER: INTERNAL
Actual Start:
Date of Baselining:

 Description   

Dear khaled khalil,
Kindly assign a resource to check for below issue.

It is found that Addinfo missing for Huawei SRANBS nodes in NEP.
Whereas when addinfo is checked on Nodes it is available.
i have attached SS below.

 Comments   
Comment by Marwan Kanaan [ 03/Feb/26 ]

Dear @Aurobinda Panda,

Kindly apply patch 3.7.71.80.451.
Previously, roles were excluded from the Additional Info report; with this patch, they are now included and visible.
Best Regards,

Marwan Kanaan I Software Developer

Comment by Marwan Kanaan [ 09/Feb/26 ]

Dear Aurobinda,

What is the issue exactly ? The additional info are available in XML and imported to NEP at eNodeB (role 4g) not at SRAN, this is why in the additional info it's showing eNodeB.

So is the issue in the report ? Of this impact the building of RAN logical interfaces ?

changing the source of additional info to SRAN will be misleading, because if you open the additional info of the SRAN you will not find them

Comment by Aurobinda Panda [ 09/Feb/26 ]

Shared comments for the parsing rule.

As the 4G role node is a part of SRAN, So in NEP the role 4G node should report under SRAN in addinfo.

Thus the Interfaces will be created for SRAN under Inter report catagory.

Comment by Marwan Kanaan [ 06/Mar/26 ]

this ticket will be released as there is nothing can be done from L3 level and the requested implementation will lead for a misleading in the Addinfo report.

Generated at Fri Apr 17 08:27:48 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.