This issue is resolved in Spectrum 9.2 or higher.
Method 1: An individual incorrectly persistent alarm can be cleared by sending a corresponding clearing event to the ESX or virtual machine model:
1) Obtain the model handle of the ESX or virtual machine. This can be done by selecting the device then querying the Model_Handle attribute on its Attributes tab in the Component Detail panel.
2) Ensure the ESX or virtual machine is not in maintenance mode.
3) In a bash shell, connect to the SpectroSERVER's command line interface (CLI):
a. cd to $SPECROOT/vnmsh
4) Use the "create event" command to issue the clearing event corresponding to the type of the persistent alarm:
a. Powered Down: create event type=0x56e1005 text="" mh=<model handle found in step #1>
b. Suspended: create event type=0x56e1007 text="" mh=<model handle found in step #1>
c. Proxy Lost: create event type=0x56e1001 text="" mh=<model handle found in step #1>
Note: a leading '0x' should be used when specifying the model handle.
5) Disconnect from the SpectroSERVER's CLI:
Method 2: All incorrectly persistent alarms can be cleared by restarting the SpectroSERVER. ESXs and virtual machines do not have to be taken out of maintenance mode before or after the restart. However, the corrective clearing of a persistent Powered Down or Suspended alarm on a virtual machine will not take place until the device is taken out of maintenance mode.
VMware Powered Down, Suspended and Proxy Lost alarms are not cleared in Spectrum when they should be
VMware related alarms are not clearing
Virtual Host Manager (VHM)
Causes of this problem:
Placing an ESX host or virtual machine into maintenance mode can cause persistent VMware-related alarms. After removal from maintenance mode, alarms may not clear even though the alarm cause is no longer valid.
PROBLEM IDENTIFICATION: For an ESX host or a virtual machine, if you suspect a persistent Proxy Lost alarm, check the Connection State field. This field can be found in the System subview under Host Information or Virtual Machine Information for ESXs and virtual machines respectively. If the Connection State value is 'connected' yet the alarm persists, the problem has been identified. This check is valid whether or not the ESX or virtual machine is in maintenance mode.
For a virtual machine, if you suspect a persistent Powered Down or Suspended alarm, check the Power field. This field can be found in the Power and Heartbeat subview under Virtual Machine Information. If the Power value is 'poweredOn' and the virtual machine is not in maintenance mode yet the alarm persists, the problem has been identified.
(Legacy KB ID CNC TS33865 )