Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Urgent
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
Description
Click to add description
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
SRANController nodes are not showing correctly in NEP under SRANController report, for which JIRA ZKU-209 has been raised.
Show
Indrasan Yadav
added a comment - SRANController nodes are not showing correctly in NEP under SRANController report, for which JIRA ZKU-209 has been raised.
The issue related to ZKU-166 has been fixed now.
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.
________________________________________________
Show
Indrasan Yadav
added a comment - The issue related to ZKU-166 has been fixed now.
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.
________________________________________________
Sandya, please commit the code for same ZKU-166.
Show
Indrasan Yadav
added a comment - Sandya, please commit the code for same ZKU-166 .
commit done.
Show
Sandya Sharma
added a comment - commit done.
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.
Show
Indrasan Yadav
added a comment - 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.
Dear @Hassan Abdine @Hassan Abdine,
Could you please provide guidance on the following case, where the parent RNC is not parsing against a NodeB?
The current rule in the connector is applicable only for RNC, not for MBSC. However, in this scenario, the NodeB is available in the MBSC dump, and as per the dump, the NodeB is connecting to the MBSC.
Details:
MBSC Type: BSC6910GU (Supports both 2G & 3G technologies)
Huawei BSC6910GU is a Base Station Controller (BSC) designed to support both 2G (GSM) and 3G (UMTS) technologies. The BSC6910GU is part of Huawei's network infrastructure equipment and provides integrated management for both GSM and UMTS base stations in a single platform. This means it can handle traffic and management for both 2G and 3G radio access networks, allowing operators to optimize their networks and provide seamless service across multiple generations of technology.
It can support:
• GSM (2G): The traditional 2G mobile technology for voice and basic data services.
• UMTS (3G): A more advanced standard for mobile communication, providing faster data speeds and additional services compared to 2G.
Observations:
1. The NodeB (DRN2M3106-P3) is present in the dump and is shown as connected to the MBSC (BSC6910GU).
2. The rule in the connector currently applies only for RNC parenting, not MBSC.
3. As per the dump and rule logic, the MBSC should appear as the parent node for this NodeB. However, it is not being reflected in the npsnodeb snippet.
Queries:
1. Will NEP accept the NodeB with a parenting BSC (in this case, MBSC)?
2. If not, should we implement a modification to the connector rule to account for MBSC parenting in similar cases?
Supporting Snippets:
1. Dump Snippet for NodeB (DRN2M3106-P3):
2. MBSC Snippet:
3. XML Snippet:
Best regards,
Indrasan