Hello, everyone!
This post will tell you one issue for different alarms due to SCC Resetting for the OSN 3500.
Problem description
The OSN 3500 is configured with dual SSN1GSCCs. Eight NEs form an MS ring (host version: 5.21.12.40P01). After a period, an individual in-service NE reports COMMUN_FAIL (GSCC in slot 17) transiently. Some other NEs reports NE_COM_BREAK and NE_NOT_LOGIN transiently.
Alarm
COMMUN_FAIL, NE_COM_BREAK, and NE_NOT_LOGIN.
Handling procedure
1. As all alarms are reported transiently, the COMMUN_FAIL alarm is not the real failure of the bus.
2. The OSN 3500 may mis-report alarms.
3. NE_COM_BREAK and NE_NOT_LOGIN are reported transiently. Maybe it is transient out-of-control during SCC resetting.
4. Different alarms may result from the same reason: SCC resetting.
Root cause
NA
Solution
1. Issue "err log" to query the NEs reporting NE_COM_BREAK and NE_NOT_LOGIN. As expected, the related resetting record exists in the process of alarm reporting.
2. Switch the SCC reporting COMMUN_FAILNE to change slot 17 to be active.
3. Query the resetting record. As expected, the related resetting record exists in the process of alarm reporting.
That's all, I welcome everyone to leave a message and exchange in the comment area!
Thank you！
