6.3

Alert Definition Symptoms Recommendations
down each ESX host port on the
physical switch, run esxcfg-nics
-l", and observe the aected
vmnics.
Verify that the vmnic identied in the
alert is still connected to the switch
and congured properly:
n
Make sure that the network cable
is still connected to the switch and
to the host.
n
Make sure that the switch is
connected to the system, is still
functioning properly, and has not
been inadvertently miscongured.
For more information, see the
switch documentation.
n
Check for activity between the
physical switch and the vmnic.
You can check activity by
performing a network trace or
observing activity LEDs.
n
Check for network port seings on
the physical switch.
To recongure the service console IP
address if the aected vmnic is
associated with a service console, see
hp://kb.vmware.com/kb/1000258 If
the problem is caused by your
hardware, contact your hardware
vendor for replacement hardware.
The host lost connectivity to a
Network File System (NFS) server.
Lost connection to NFS server (fault
symptom).
1 Verify the NFS server is running.
2 Check the network connection to
make sure the ESX host can
connect to the NFS server.
3 Determine whether the other hosts
that use the same NFS mount are
experiencing the same problem,
and check the NFS server status
and share points.
4 Make sure that you can reach the
NFS server by logging into the
service console and using vmkping
to ping the NFS server: "vmkping
<nfs server>".
5 For advanced troubleshooting
information,
seehp://kb.vmware.com/kb/10039
67
A fatal error occurred on a PCIe bus
during system reboot.
A fatal PCIe error occurred. Check and replace the PCIe device
identied in the alert as the cause of
the problem. Contact the vendor for
assistance.
A fatal memory error was detected at
system boot time.
A fatal memory error occurred. Replace the faulty memory or contact
the vendor.
Chapter 3 Alert Definitions in vRealize Operations Manager
VMware, Inc. 139