VMware (VCSA 6.7/7.0): Changing the size of vSphere Dump Collector for VCSA 6.7 & 7.0

3 years ago   •   1 min read

By CloudNerve.com


When an ESXi host crashes, the generated core dump can be sent over the network to a remote core dump server. The vCenter Server Appliance (VCSA) can be configured as a destination by enabling the built-in vSphere Dump Collector service. By default, the storage repository for the vSphere Dump Collector service is configured to 2GB and can be increased up to 10GB, which is the supported maximum.

In earlier vSphere releases, configuring the vSphere Dump Collector repository size could be done using the vSphere Web (Flash) Client as shown in the screenshot below.

Configure and test of ESXi Dump Collector – Notes from MWhite
Screenshot courtesy from Michael White’s blog post https://notesfrommwhite.net/2016/01/20/configure-and-test-of-esxi-dump-collector/

However, as part of the vSphere (HTML5) UI Client transition, it looks like all general VCSA service configurations including the vSphere Dump Collector was not ported over. I can only assume the reasoning for this was due to the infrequency configuring or updating these settings. This has been a question that has come up a few times across both VCSA 6.7 and 7.0 environments and I was recently reminded of the solution and I realized I had not blogged about the solution.

Step 1 – SSH to your VCSA and then edit /etc/sysconfig/netdumper and update the NETDUMPER_DIR_MAX_GB parameter to the desired value (10GB Max)

Step 2 – Restart the vSphere Dump Collector service for changes to go into effect

VCSA 7.0

service-control –restart vmware-netdumper

VCSA 6.7

service-control –stop vmware-netdumper
service-control –start vmware-netdumper

Spread the word