Losing Connection to PCNS during ESXi shutdown

[Anonymous user]

I am running a 3-host cluster of ESXi (5.1.0, 799733) with PCNS 3.01 installed on vMA (5.1.0, 782391). My current set up is vMA running on ESXi host #2 with my ESXi host #1 configured as a target server in PCNS. I configured an event to shutdown the host when the UPS is on battery and rolled the UPS to battery to intiate the shutdown. The ESXi host shuts down correctly, however at some point during the process i lose connectivity to the PCNS web interface. The vMA appliance is still pingable and can be reached via SSH. The only way i can reconnect to the PCNS web is restart the network on vMA using sudo /etc/init.d/network restart or rebooting the appliance.

To take the testing one step further, i configured a test VM on host #1. I copied and enabled the shtudownvms.sh script on the vMA appliance and configured a 3 minute interval between the shutdown of the VM and host. Again, rolled the UPS to battery and waited as it successfully initiated a shutdown of the VM. However, seconds later i found the PCNS Web UI unreachable and the shutdown of the ESXi host never happens.

Also to clarify, i've already used the FA159783 article to "export PERL_" line to the shutdown script. And from a networking standpoint all devices including the ESXi host, VMs, and vMA are all on the same VLAN so i don't think this is a firewall issue.

Message was edited by: lesgram

[Anonymous user]

**UPDATE**
I have the shutdown of VMs and ESXi Host working correctly. However, i still have what i perceive to be an issue with the PCNS software. After initiating a test i see the following in the Event Log of the PCNS - "Shutdown process started. Linux will shut down soon". Seconds later i lose connectivity to the PCNS Web UI. The ony way to reconnect is to SSH to the vMA and restart the network and PCNS daemon (or reboot the vMA appliance). Is this normal behavior for the PCNS service to shut itself down after initiating the shut down of the configured target servers?

Message was edited by: lesgram

[BillP · Accepted solution]

hello,

i just double checked and unfortunately we do not yet currently support ESXi and vMA v5.1..testing is on going now...I think we only do 5.0.1 currently.

EDIT - i forgot to add, since the testing is ongoing, I presented your issue to the team testing this to make sure that when we do fully support it, we don't see the problem you are experiencing.