Difference between revisions of "Reseting state of all alarms and node statuses"

Jump to navigation Jump to search
m
no edit summary
(Created page with "Sometimes, it can be useful to reset the "state" of all your NetXMS objects completely. For example, if you recover the DB from an older date, a lot of alarms and node status...")
 
m
Line 4: Line 4:
However, some alarms might not terminate due to the current status of the system differing from the previous state.<br>
However, some alarms might not terminate due to the current status of the system differing from the previous state.<br>


Its also possible that you miss-configured EPP to not close down alarms, etc.
Its also possible that you miss-configured EPP to not close down alarms, etc.<br>
There is many ways when the NetXMS alarms can become abandoned, or out-of-state due to user errors or infrastrucutre issues.
There is many ways when the NetXMS alarms can become abandoned, or out-of-state due to user errors or infrastrucutre issues.<br>


Basically, your NetXMS system will be reset to a state where it "thinks" all things are currently OK.
Basically, your NetXMS system will be reset to a state where it "thinks" all things are currently OK.<br>
So after it starts up, it will regenerate all alarms for things that are not in a state they should be.
So after it starts up, it will regenerate all alarms for things that are not in a state they should be.<br>


After performing this procedure, you can be sure that the outstanding alarms are current.
After performing this procedure, you can be sure that the outstanding alarms are current.
Line 32: Line 32:
*Any one-time alarms (from Syslog, SNMP traps, etc.)
*Any one-time alarms (from Syslog, SNMP traps, etc.)
*State of alarms (acknowledged, etc.)
*State of alarms (acknowledged, etc.)
*Comments on alarms
184

edits

Navigation menu