Cause of the error message indicating that the source port is already occupied during manual creation of a logical fiber upon a failure to synchronize logical fiber connections on the U2000

5

The cause is as follows: Before you synchronize inter-NE logical fiber connections, the NE ID has been changed but the created inter-NE logical fiber connections have not been deleted. As a result, the logical fiber connections recorded in the database on the NE side are incorrect and cannot be synchronized to the U2000.

Other related questions:
Whether ODUk SNCP protection switching will fail if logical fiber connections and physical fiber connections are reverse
Yes, ODUk SNCP switching will fail.

Method used to verify the consistency between physical fiber connections and logical fiber connections on Metro 1000
1. The Metro 1000 V2 does not support query for received J0 bytes. You can change the number of J0 bytes to be transmitted at the local end to be different from the number of J0 bytes to be received at the peer end, and then check whether the J0_MM alarm is reported. 2. You can also insert an MS_AIS alarm and check whether the peer end reports the MS_AIS alarm. Exercise caution because this operation will interrupt services.

Command for deleting fiber connections of OTN devices
:cfg-del-fibermgr:SrcNeid,SrcBid,SrcPort,DstNeid,DstBid,DstPort

Methods for querying and deleting logical fiber connections on an OptiX OSN 6800 board by using commands
Command for querying: :cfg-get-fibermgr:SrcNeid,SrcBid,DstNeid,DstBid. Command for deleting: :cfg-del-fibermgr:SrcNeid,SrcBid,SrcPort,DstNeid,DstBid,DstPort.

Reason for a WAVELEN_OVER alarm reported on the WMU board when physical and logical fiber connections are inconsistent
When physical and logical fiber connections are inconsistent, the wavelength locking function triggers a false wavelength adjustment. As a result, a WAVELEN_OVER alarm is reported.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top