This article provides steps for troubleshooting the ESXi Dump Collector (netdump) functionality in vSphere 5.0.
During a purple diagnostic screen outage on a vSphere ESXi 5.0 host, you experience these symptoms:
To troubleshoot the network Dump Collector (netdump) functionality in vSphere 5.x:
esxcli network firewall refresh
esxcli system coredump network get
Enabled: True
Host VNic: vmk0
Network Server IP: 10.11.12.13
Network Server Port: 6500
esxcli network ip interface ipv4 get --interface-name=vmk0
Name IPv4 Address IPv4 NetMask IPv4 Broadcast Address Type DHCP DNS
---- ------------ ------------ -------------- ------------ --------
vmk0 10.55.66.77 255.0.0.0 10.255.255.255 STATIC false
nc
command reports a successful connection regardless of whether the remote Netdump Server receives the traffic.netdumper| Log for vmware-netdumper pid=PidNumber version=VVV build=build-BBBBB option=Release
netdumper| The process is 32-bit.
netdumper| Host codepage=UTF-8 encoding=UTF-8
log FIFO capture : Msg_Reset:
log FIFO capture : [msg.dictionary.load.openFailed] Cannot open file "/path": No such file or directory
netdumper| Configured to handle 1024 clients in parallel.
netdumper| Configuring /path/to/coredump/storage as the directory to store the cores
netdumper| Configured to use ListeningIPAddress:Port as the IP address:port
netdumper| Using /var/log/vmware/netdumper/netdumper.log as the logfile.
netdumper| Configure to daemonize netdumper
msg.dictionary.load.openFailed
entries refer to several configuration files that do not exist. This is normal.netdumper| Starting network coredump from VMkernelIPAddress to DumpCollectorIPAddress.
netdumper| Dump: nnnn: Compressed dump took bbbbbb bytes total.
netdumper| NetDump: Successful.
netdumper| Stopping Netdump.