Sunday, April 9, 2017

Ethernet trail alarms are not synchronized with real alarms on NEs

Issue Description
Customer M complains that Ethernet trails status is "not alarmed" but when he checks the relevant NE he found that there are some alarms. So the Ethernet trail alarm status is not automatically updated with NE alarms.
Alarm Information
Null
Handling Process
to solve this problem follow the following steps:
.          Stop the nmleth process manually.
.          Modify bRelocateAlarmByTrailAssociate from 0 to 1 in U2000server\nml\nmleth\conf\cfg\nmleth.cfg
.          Restart the nmleth process.
.          Browse current alarms about the faulty trail again.
Alarms are relocated and relationship between the trail and its alarms will be updated. As a result, alarm status is synchronized.
Root Cause
after checking and analyzing we found that the root cause of this problem is located in nmleth.cfg file that is stored in the folder server\nml\nmleth\conf\cfg , in fact there is one parameter that is responsible for displaying trail alarm:  bRelocateAlarmByTrailAssociate , this parameter has the value "0", that is why there was no mechanism to automatically synchronize the trail alarm.
Suggestions

Null
Telephone: 852-30623083
           Supports@Thunder-link.com            
Posted by at
Labels: , , , , , ,

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)