Configure vSphere ESXi Dump Collector

Here is a quick post about configuring the vSphere Dump Collector for your ESXi hosts. I’m not going to cover the installation process because it is really simple and straightforward. You can install the Dump Collector as stand-alone instance or integrated with vCenter Server. If you choose the last option you will have to provide the IP address, port and log in credentials for the vCenter Server. After the installation, you can configure the Dump Collector using:

  • Host Profiles or

And probably PowerCLI but I didn’t look it up yet! 🙂

Host Profiles

  1. Edit the host profile you want to configure or create a new one if you don’t have one.
  2. Navigate to Network Configuration –> Network Coredump Settings and select Fixed Network Coredump Policy.
  3. Make sure that the Network Coredump Collector is enabled, provide the Host NIC to use, Network Core Server IP and Network Coredump Server Port. 
  4. Click OK to save the settings.
  5. Apply the profile to your hosts.


  1. Open console session to your host or log in through the ESXi Shell.
  2. Log in as root user.
  3. Check the current configuration of coredump settings:#esxcli system coredump network get
  4. Configure the coredump with: #esxcli system coredump network set --interface-name <VMkernel_Interface> --server-ipv4 <Server_IP_Address> --server-port 6500
  5. Enable the coredup by typing: #esxcli system coredump network set --enable true
  6. Verify that the coredump server is running (only available in ESXi 5.1): #esxcli system coredump network check
  7. You should see a message stating the following: “Verified the configured netdump server is running”.
  8. Log out from the host.

Note: mind the double dashes in the command syntax.

Check the firewall

Verify that the Dump Collector port is enabled in the ESXi firewall. 


To test if your host will dump the PSOD data to your Dump Collector force a PSOD on your host.

  1. Log in to the host locally or remotely.
  2. Type: #vsish and press Enter
  3. Next, type: set /reliability/crashMe/Panic followed by Enter.
  4. This will cause a PSOD. Note that the dump is being send over the network. 
  5. Wait until the dump is ready. Navigate to the directory where the dumps are stored and you should see the dump file that was just created.


– Marek.Z


  1. Incredibly timely for a test scenario where I needed to induce a crash to generate a dump and no other Google searches were fruitful.

    Thank you

Leave a reply...