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) m |
m (Text replacement - "^" to "{{deprecated}}") |
||
| (2 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> | ||
| 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; | ||
| Line 32: | Line 33: | ||
*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 | |||