The communication interrupt between OSN3500 and NMS after SCC switch
This time, I will share with you a case about communication interrupt between OSN3500 and NMS after SCC switch.
Issue description
An STM-4 ring configure with three OSN3500s, one OSN3500 configure as GNE. During the acceptance test, after the SCC board is switched to the standby board, the communication between the NMS and the NE fails, and no related alarm is reported.
Handling Process
1. Check configuration of NE on site by Weblct, find ECC work normal, OSN3500 also can login each other.
2. Check OSN3500 alarm and SCC DPS configure, find NE without alarm and SCC configuration also normal.
3. Ping from NMS to NE and find not success. So, it can confirm DCN from NMS to GNE with problem.
4. Ask customer engineer check and find external DCN Configuration:
NMS—SWITCH—OSN3500
Ping from NMS to Switch —success
Ping from NMS to OSN3500—fail
So, issue occur from switch to OSN3500
5. Contact the DCN service personnel of the network. It is found that the switch port on the DCN network is blocked. Although the OSN 3500 has only one ETH port, the MAC address of the port changes during the switching of the CXL board. The switch port will be blocked.
Solution
After the DCN service personnel enable two different MAC addresses for the same port on the switch, the communication recovers.
If you have any questions, please feel free to contact: [email protected].