Place ESX Host in Maintenance Mode or Hibernation

casp1032
 
 
An 
ESX host 
is a physical computer that uses ESX Server virtualization software to run virtual machines. Hosts provide the CPU, memory, storage resources, and network connectivity for the virtual machines.This article describes how you can place an EXS host in maintenance and hibernation modes. Hibernation mode automatically restarts normal management traffic as soon as the SpectroSERVER detects successful communication with the device after a set of successful polls. Whereas, the Maintenance Mode requires you to disable the maintenance mode option before the device can resume normal management traffic. 
To place an ESX Host in maintenance mode, enable the In Maintenance option in the Information tab of the Component Detail panel. This action suspends management of the ESX Host. However, 
DX NetOps Spectrum
 still performs regular management on the ESX Host and on its virtual machines. 
In the maintenance mode, following conditions apply to the ESX Host:
 From 10.2.1, you can choose to place only the ESX Host server in maintenance mode, and not the VMs under the ESX Host. See Maintenance Mode Correlation for more information.
  • By default, all the VMs under the ESX Host are automatically placed in maintenance mode. If the maintenance mode is turned off on the ESX Host, all the VMs are removed from maintenance mode. 
     If a VM is already in maintenance mode before the ESX Host placed in maintenance mode; even after the ESX Host is out of maintenance mode, the state of VM remains maintenance mode only.
  • Traps are not processed.
  • Events are generated.
  • Maintenance Alarms of VMs are correlated to ESX Host Maintenance Alarm.
Schedule Maintenance Mode for ESX Host
Schedule the maintenance mode of an ESX Host by applying a maintenance schedule or by creating schedule. You can apply multiple schedules to an ESX Host. For more information on applying schedule and creating a schedule see the Schedule Maintenance Mode 
 
section.
See OneClick Schedules for information about how OneClick and 
DX NetOps Spectrum
 apply schedules across time zones in Distributed SpectroSERVER environments.
Maintenance Mode Correlation
The default, Maintenance Mode Correlation behavior is such that, when an ESX Host is placed in maintenance mode, all the VMs under the ESX Host are automatically placed in maintenance mode. The maintenance alarms on VMs are correlated to the ESX Host maintenance alarm. From 10.2.1, you can modify the default behavior, (where you can edit an attribute "SetMaintenanceModeToChildren /0x633002a") enabling you to choose only the ESX Host Server to be placed in maintenance, while ensuring that the the maintenance mode correlation does not apply to the VMs under the ESX Host. 
 
To enable maintenance mode only for the ESX Host and not for the VMs, follow these steps:
 
  1. In the 
    DX NetOps Spectrum
     OneClick console, Explorer Tab hierarchy, navigate to UIM Manager, select the List tab and then the Attributes tab in the Components Detail panel.
  2. In the Component Details panel, Search bar, enter one of the following:
    • Attribute Name: 
      SetMaintenanceModeToChildren
       
    • Attribute ID: 
      0x633002a
      By default, the value of this attribute is set to Yes.
      SetMaintenanceModeToChildren.png
       
  3. Double-Click the Attribute result on the right pane.
    The Edit UIM Manager dialog appears.
  4. Clear the No Change check-box and select No in the dialog.
  5. Click OK.
    The Attribute Edit Results dialog appears with a confirmation of the change in attribute value, along with landscape details.   
Click Undo on the Attribute Edits Results dialog to revert the Maintenance Mode correlation back to default. 
Once you have successfully edited the attribute; the maintenance mode correlation no longer applies to the VMs under the ESX Host. Now, only the ESX Host server will be placed in maintenance while the VMs under the same, will no longer be placed under maintenance. The VMs will remain in active state and will be monitored as usual for alarms and events.
Place ESX Host in Hibernation Mode
To place an ESX Host in hibernation mode, enable the In Hibernation option in the Information tab of the Component Detail panel. This action suspends management of the ESX Host.
When the ESX Host is placed in Hibernation mode, all the VMs under the ESX Host are automatically placed in maintenance mode. The maintenance alarms on VMs are correlated to ESX Host hibernation alarm. 
In the Hibernation mode, following conditions apply to the ESX Host:
  • Brown alarms are shown for interfaces in hibernation mode.
  • No polling, logging, or other device communication is performed until normal management is resumed.
  • Hibernation Alarm is shown on ESX Host and Maintenance Alarm is shown on VM.
  • Maintenance Alarms on all the VMs are correlated to single ESX Host Hibernation Alarm.
If an ESX Host is placed in Hibernation, which is already in maintenance, then Spectrum shows both Maintenance and Hibernation alarms on the ESX Host. 
 The Hibernation Alarms of VMs under an ESX are not correlated to ESX Host Maintenance Mode or Hibernation Alarm.
Hibernate After Maintenance
To place an ESX Host in hibernation mode after scheduled maintenance, refer to the steps explained in the Hibernate After Maintenance section.
Migrating a VM from an ESX Host to Another ESX Host
The following section describes scenarios of VM migration from a source ESX to a destination ESX. 
 
Scenario 1
 
 
Result
 
(A)
  • ESX1 (source) is in Maintenance Mode.
  • VM is in inherited Maintenance.
    (the ‘inheritedMaintenance’ attribute is ‘YES’)
  • ESX2 (destination) is in Maintenance Mode.
The migrated VM under ESX2 is in Inherited Maintenance Mode.
(B)
  • ESX1 (source) is in Maintenance Mode.
  • VM is in inherited Maintenance.
    (the ‘inheritedMaintenance’ attribute is ‘YES’)
  • ESX2 (destination) is NOT in Maintenance Mode.
The migrated VM under ESX2 (destination) is NOT in Inherited Maintenance Mode.
 
Scenario 2
 
 
Result
 
(A)
  • ESX1 (source) is NOT in Maintenance Mode.
  • VM is in Maintenance Mode.
  • ESX2 (destination) is in Maintenance Mode.
The migrated VM under ESX2 (destination) is in Maintenance Mode.
(B)
  • ESX1 (source) is in Maintenance Mode.
  • VM is in Maintenance Mode.
  • ESX2 (destination) is NOT in Maintenance Mode.
The migrated VM under ESX2 (destination) is in Maintenance Mode.
 
Scenario 3
 
 
Result
 
(A)
  • ESX1 (source) is in Maintenance Mode.
  • VM is in Maintenance Mode.
    (the ‘inheritedMaintenance’ attribute is ‘NO’)
  • ESX2 is in Maintenance Mode.
The migrated VM under ESX2 (destination) is in Maintenance Mode.
(B)
  • ESX1 (source) is in Maintenance Mode
  • VM is in Maintenance Mode
    (the ‘inheritedMaintenance’ attribute is ‘NO’)
  • ESX2 (destination) is NOT in Maintenance Mode
The migrated VM under ESX2 (destination) is in Maintenance Mode.