AutoPatrol, Bureaucrats, Administrators
481
edits
Difference between revisions of "Reseting state of all alarms and node statuses"
Reseting state of all alarms and node statuses (view source)
Revision as of 16:13, 13 September 2022
, 16:13, 13 September 2022Text replacement - "^" to "{{deprecated}}"
Tomas Kirnak (talk | contribs) (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 (Text replacement - "^" to "{{deprecated}}") |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
Sometimes, it can be useful to reset the "state" of all your NetXMS objects completely. | {{deprecated}}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 statuses will be outdated.<br> | For example, if you recover the DB from an older date, a lot of alarms and node statuses will be outdated.<br> | ||
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 15: | Line 15: | ||
To completely reset the state of all object you can:<br> | To completely reset the state of all object you can:<br> | ||
(these commands should be run on the database NetXMS uses) | |||
UPDATE thresholds SET current_state=0; | UPDATE thresholds SET current_state=0; | ||
UPDATE alarms SET alarm_state=3; | UPDATE alarms SET alarm_state=3; | ||