I did the following by accident:
I created a new vmkernel port for vMotion. When I created this port the default gateway was changed to the new vmkernel port. This prevented the management interface being reached as the default gateway was now pointing to the vmkernel port on vSwitch1.
So to fix:
Check the status of the NICs on the ESX host.
# esxcfg-nics -l
This showed that the NIC 'vmnic0' was active and 'vmnic1' was in a down state.
Checked the vSwitch configuration with the following
# esxcfg-vswitch -l
This confirmed a new vmkernel port 'vmk1' was created in a portgroup 'VMkernel' on 'vSwitch1'.
As this was the new vSwitch that I'd created, I removed it as it was working before the change.
# esxcfg-vmknic -d "VMkernel"
# esxcfg-vswitch -d vSwitch1
However, this didn't resolve the issue.
Tried to ping the default gateway
# vmkping x.x.x.x
This worked fine.
Then tried a diagnostic ping
# vmkping -D
This reported the default gateway wasn't set.
This was corrected by:
# esxcfg-route x.x.x.x
This resolved the issue and restored access to the ESX host.