Observed that when maintenance was performed for UIM servers, alarms for other servers that were under maintenance will be sent out when the primary hub is up. It seems like the alarm already came in while the maintenance_mode probe was still querying the database for the configured maintenance windows. Is there any way to prevent or resolve this issue?
Please review the KB Article:
When the UIM service in the Primary HUB Robot is restarted, we saw alarms from maintenance mode device.
You can also try increasing the timeouts in the ems and nas probe as described below:
In <setup> section:
Add the key maintenance_mode_cmd_timeout = 300000
if it does not exist. The value is in ms.
in raw configuration or cfg file:
in <setup> section:
add the key
maint_max_resp_time = 300
if it does not exist. The value is in seconds.
3) Also in the nas <setup> section
add the key:
registrationIntervalLookAheadMinutes = 60