[LS-249] Active node not found B650G Created: 26/Feb/25  Updated: 29/Dec/25  Due: 28/Feb/25  Resolved: 09/May/25

Status: Open Bug
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Shamim Ahmed Assignee: Marwan Kanaan
Resolution: Not Fixed Votes: 0
Labels: FN
Remaining Estimate: 0 minutes
Time Spent: 1 day
Original Estimate: Not Specified

Attachments: PNG File 2621.png     PNG File 2622.png     PNG File 2623.png     PNG File L31.png     PNG File L32.png     PNG File L33.png    
Customer:
OMAN-Tel
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

As you suggested, I attempted a BONT Autoload for one of the nodes Yassin shared. However, I'm encountering the following error, and the OSP connection is also not updating.
I spoke with Amir, and he suggested deleting the passive part, which he believes will allow the Autoload to succeed. My concern is that the node already has active subscribers.
How can we delete the passive part in this situation?Snapshot are shared below for reference.
Could you please review this and advise on the best course of action?



 Comments   
Comment by Salem Dannawi [ 11/Mar/25 ]

L3 response:

As I have checked, there is no issue now on BONT side all is configured correctly.

But I figured out that the default template/configuration of MDFH type : MDFH_Huawei_2 has been changed, when trying to create osp connections and based on the configuration in code specification below, we are trying to fetch the port 1-1 and 1-9 on MDFH : XE22_02_H2_MH
but as I checked, I couldn’t find the port 1-1, neither the port 1-9 on the mentioned MDFH, as you can see below port format is different.

I checked all MDFHs to see the ports format and it matched the expected format:

So kindly check how the default template configuration has been changed, and why? And you need to revert it back or change the configuration in code specification based on the start port of MDFH for each configuration.

New Attached images from L3

Comment by Abir Messaikeh [ 18/Mar/25 ]

Dawlat has highlighted an issue regarding the MDFH port format, specifically for the MDF model XE22_02_H2_MH (MDFH_Huawei_2).

As you know, the template for MDFH_Huawei_2 doesn't enforce a specific naming rule, and the current configuration for XE22_02_H2_MH appears to be incorrect while MM44 is correct.

Thus there exists a discrepancy in the node port pattern between XE22 and MM44, despite both nodes using the same MDFH_Huawei_2 model as shown below.

My concern is:

• Why are the node port patterns different for XE22 and MM44, given that they share the same MDFH model?

This inconsistency needs to be resolved to ensure uniformity and prevent potential errors in future configurations.

Could you please investigate this issue and provide a solution to ensure consistent port patterns across all nodes using the MDFH_Huawei_2 model?

Please let me know if you require any further information.

Thank you for your assistance.
.

Comment by Diana Hamdouche [ 24/Mar/25 ]

Please find the details below regarding the MDF configuration:
MDF "XE22_02_H2_MH" was initially created on 13-DEC-22 with a specific configuration (Cabinet, Magazine).
The same node was later updated on 11-MAR-25, reflecting a new configuration.
Ports with an incorrect format (count: 16) were created on 11-MAR-25.
MDF "MM44_02_H2_MH" was created on 07-JAN-25 with its specific configuration (Cabinet, Magazine, Ports).

This confirms that the MDF Model "MDFH_Huawei_2" is not the cause of this discrepancy. The main reason is that MDF "XE22_02_H2_MH" was originally created with an outdated configuration in 2022 and later updated in 2025.

Comment by Abir Messaikeh [ 24/Apr/25 ]

As discussed with shamim , he will be working with Amir to delete in batches BONT nodes without OSP connection and autoload again from FN side and check the outcome

we will update this ticket once action completed

Comment by Abir Messaikeh [ 09/May/25 ]

Had to delete BONT nodes in bulk so that same will recreated through API properly.
Although we have option to delete same in bulk from ONT report in NEP but unfortunately active node were getting deleted without deleting passive nodes because cabinet linked to that active node has OSP connection its not getting deleted.
So deleting osp connection and deleting passive nodes is very time consuming process.Please need you suggestion for the same.

Note::Some nodes has been created but still count is high for nodes need deletion and recreation.

XD85_01_B650G
XD87_01_B650G
XO31_01_B650G
XM70_01_B650G
XS35_01_B650G
XJ52_01_B650G
XM75_01_B650G
XB06_01_B650G
OX14_01_B650G
XG86_01_B650G
XD72_01_B650G
XK62_01_B650G
XE33_06_B650G
XS87_01_B650G
XR50_01_B650G
XJ31_01_B650G
XR03_01_B650G
XD41_01_B650G
XE29_01_B650G
XE19_03_B650G
XC66_01_B650G

Generated at Fri Apr 17 09:37:32 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.