Hi Luc
After some research found following VMware KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003042
At the end of KB there was additional information which I missed first time round. This talks about how to make firewall persist after reboot. I have tested this in my lab and works fine. However, I am still unable to send netdump to the net dump server.
I have tested connection when ESXi host was running. Output
(Connection to 192.168.1.45 6500 port [udp/*] succeeded!
When I replicate purple screen I get following...
NetDump: Failed couldn't attach to dump server at 192.168.x.x (vSphere Dump tool is installed on vCenter server).
To make the firewall configuration (from step 3c above) persist after a reboot:
- Copy the newly defined netdump.xml file onto persistent storage (such as /store/) or onto a VMFS volume (/vmfs/volumes/volume/).
# cp /etc/vmware/firewall/netdump.xml location-of-xml
Note: A VMFS volume can be stored in a single location and copied to multiple hosts. - Add these lines to the/etc/rc.local file on the host:
# cp location-of-xml-file /etc/vmware/firewall
# esxcli network firewall refresh
Where location-of-xml file is the location to which the file was copied.
Kind regards,
Sultan