Why sometimes NMS report alarm delayed. We may also be found some alarm by NMS after a long time (some hours or some days).
Devicetype : OSN 3500; version:v1r8c02spc200; U2000：V100R005C00CP6032
1. szhw user has been used login the NE by NMS.
2. check the user report state,it display “pause”. In this case the alarm has not automatically been reported to NMS.
3. It will be recover after login NMS by user “root”.
It will be notified all online users after the alarm status changes.
For ems user,alarm will continue to be repeat reported in order to ensure NMS can receive alarms.
Whether reporting alarm have been control by two commands.
1.alm-set-usersta settings for reporting to which online user.Alarm would automatically reported to all online user in addition to “szhw” by default;
2.alm-set-autorep settings for which alarm report to user. this settings of the user may be different from each other.
1. NE is not out of management and automatically reporting of the alarm has been set to enable.[alm-get-autorep]
2. Alarm automatically reported to NMS delay.
3. szhw user has been used login the NE by NMS.
1. check the user report state,it display “pause”. In this case the alarm has not automatically been reported to NMS.
#9-21:szhw [][][2013-08-12 18:45:13+00:00]>
>>> :alm-get-usersta
ALM-AUTOREP-USER-PAUSE-STATE
PAUSE-STATE
pause
Total records :1
#9-21:szhw [][][2013-08-12 18:45:20+00:00]>
It will be recover after login NMS by user “root”.
Recommended not to use the user(szhw) login NE.
All versions of the transmission network elements are present the problem.
Comments are closed