No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Ethernet trail alarms are not synchronized with real alarms on NEs

Publication Date:  2012-07-25 Views:  2 Downloads:  0
Issue Description
customer M complains that ethernet trails status is "not alarmed" but when he check the relevent NE he found that there are some alarms. so the ethernet trail alarm status is not automatically updated with NE alarms.
Alarm Information
Handling Process

to solve this problem follow the following steps:

  1. Stop the nmleth process manually.
  2. Modify bRelocateAlarmByTrailAssociate from 0 to 1 in U2000server\nml\nmleth\conf\cfg\nmleth.cfg
  3. Restart the nmleth process.
  4. 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 synchronise the trail alarm.