Isilon - Planned Maintenance and Notification from Support
Community,
Has anyone ran into the issue where management wanted the response from EMC support to be a little more efficient? Meaning that if we have a planned outage for a cluster that is connected to ESRS when we intentionally take down a node for maintenance we don't get emails some support stating that the node is offline. How might I be able to stop known maintenance from showing up as possible issues to EMC support? Is there a way to send a pre-notification via command line prior to shutting down a node that will stop ESRS from sending notification to support about something that is maintenance and known by the customer? If you have other ideas feel free to discuss.
Same info Peter notes on page 91 of the OneFS 8.0 CLI guide (docu65065_OneFS-8.0.0-CLI-Administration-Guide).
I'm curious if anyone has seen this odd behavior when using these maintenance windows. This has happened to me 2 or 3 times recently after patch installs using v8.0.0.2:
1. Place the cluster in a maintenance window for several hours (last time was 5).
2. Install patches and reboot nodes normally.
3. Finish all work well before the windows expires (last time still have over 1 hour on the "meter")
4. When the maintenance window ended at the 5 hour mark, the last node to reboot opened an SR automatically.
Like I say, this has happened 2 or 3 times, and I've learned to get in quick to close the case before I get a call from support.
Well I have an ESRS set up but I still use the maintenance windows as described in the admin guide for OneFS. I hadn't thought about maybe the ESRS being the cause. I will try both maintenance window and turning off the ESRS during the installs next time.
Maybe someone can enlight us how ESRS handles events. I would expect that if everything is "green" after maintenance (so no Events/failures or anything) and i turn on ESRS that there wouldn't be any message going out.
Peter_Sero
6 Operator
•
1169 Posts
1160
0
Posted February 15th, 2017 08:00
For OneFS 8.0 check out the "maintenance window" feature, as described in Configuring CELOG
hth
-- Peter