Alarms that can be configured in vCenter Server 4.x and triggered on ESX 4.x hosts

Products

• VMware vCenter Server

Issue/Introduction

Some alarms and events configured in vCenter Server 4.x only trigger when applied to ESX 4.x hosts.

 

This article provides information about the alarms and events that do not trigger when applied to ESX 3.5 hosts.

Environment

VMware vCenter Server 4.1.x
VMware vCenter Server 4.0.x

Resolution

This table outlines the event based alarms that can be created in vSphere Client and triggered in ESX 4.x (but not in ESX 3.5), as well as the KB article that provides more information:

 

Trigger	Event	KB Article
Lost Storage Connectivity	vprob.storage.connectivity.lost	Lost or Degraded connectivity to storage device (1009553)
Lost Storage Path Redundancy	vprob.storage.redundancy.lost	Lost redundant path to storage device (1009554)
Degraded Storage Path Redundancy	vprob.storage.redundancy.degraded	Path redundancy to storage devices are degrading (1009555)
Lost Network Connectivity	vprob.net.connectivity.lost	Network Connectivity Lost Due to Physical Link Down (1009515)
Lost Network Redundancy	vprob.net.redundancy.lost	Physical Link Down with Loss of Redundancy (1009542)
Network Redundancy Degraded	vprob.net.redundancy.degraded	Physical Link Down with Redundancy Degraded (1009546)
No IPv6 TSO support	vprob.net.e1000.tso6.notsupported	TCP Segmentation Offload (TSO) over IPv6 with e1000 Virtual Adapters (1009548)
Invalid vmknic specified in /Migrate/Vmknic	vprob.net.migrate.bindtovmk	VMkernel NIC Not Correctly Configured (1009550)

 

This table outlines events triggered in ESX 4.x (but not in ESX 3.5) that do not correspond directly to any individual alarms configurable in vSphere Client as they are host generated triggers:

 

Event	KB Article
vprob.net.proxyswitch.port.unavailable	vNetwork Distributed Switch Proxy Switch Port Unavailable (1014099)
vprob.vmfs.heartbeat.recovered	Host Connectivity Restored (1009556)
vprob.vmfs.heartbeat.timedout	Host Connectivity Degraded (1009557)
vprob.vmfs.heartbeat.unrecoverable	Host Connectivity Permanently Lost (1009559)
vprob.vmfs.journal.createfailed	VMFS volume open without Filesystem Journal (1010931)
vprob.vmfs.lock.corruptondisk	VMFS Lock Volume is Corrupted (1009565)
vprob.vmfs.nfs.server.disconnect	Connectivity to NFS Server Lost (1009566)
vprob.vmfs.nfs.server.restored	Understanding the messages: Connectivity to NFS Server Lost and Connectivity to NFS Server Restored (1009568)
vprob.vmfs.resource.corruptondisk	VMFS Lock Volume is Corrupted (1009565)
vprob.vmfs.volume.locked	VMFS Volume is Locked (1009570)