VCSA fails to start after power outage

[BillP]

This question was originally posted by Lee on APC forums on 7/15/2018

---

I have successfully configured my two ESXi hosts to shutdown during a power outage. After numerous tests, I have noticed everything successfully shuts down but when powering up, PCNS fails to start the VCSA. The part that doesn't make sense is since PCNS can communicate with VCSA to start the shutdown sequence, how can it somehow forget where the appliance is located when its time to start it back up?

Here's my configuration:

ESXi Host 1 - x.139.4

VCSA and PCNS

ESXi Host 2 - x.139.7

Successfull VCSA settings:

Error.log of my last tests:

15-07-18 10:56:30,064 ERROR main com.apcc.pcns.configservice.ConfigurationService - === Starting PowerChute Network Shutdown ===

15-07-18 10:56:59,992 ERROR main com.apcc.pcns.SNMP.PcnsBaseAgent - SNMP Agent Engine ID:80:00:01:3e:01:7f:00:00:01:51:0d:e6:b8

15-07-18 10:57:32,355 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - getVCenterServerConnection, Host 192.168.139.130 - . VI SDK invoke exception:java.net.NoRouteToHostException: No route to host

15-07-18 11:21:46,175 ERROR pool-3-thread-1 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.139.130 - java.rmi.RemoteException: VI SDK invoke exception:java.net.SocketTimeoutException: connect timed out

15-07-18 11:21:49,181 ERROR pool-3-thread-1 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - getVCenterServerConnection, Host 192.168.139.130 - . VI SDK invoke exception:java.net.NoRouteToHostException: No route to host

15-07-18 11:36:10,457 ERROR main com.apcc.pcns.configservice.ConfigurationService - === Starting PowerChute Network Shutdown ===

15-07-18 11:36:40,274 ERROR main com.apcc.pcns.SNMP.PcnsBaseAgent - SNMP Agent Engine ID:80:00:01:3e:01:7f:00:00:01:51:0d:e6:b8

15-07-18 11:37:12,466 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - getVCenterServerConnection, Host 192.168.139.130 - . VI SDK invoke exception:java.net.NoRouteToHostException: No route to host

Host Protection:

I would like to remind that PCNS does everything is supposed to in the event of a power outage. The only issue is VCSA shuts down properly but just can't be restarted by PCNS when the hosts return online. 

P.S. Eventlog of my last test is attached. 

[BillP]

This reply was originally posted by Bill on APC forums on 7/16/2018

---

Hi,

Are there any errors logged in the VCSA during the shutdown process?

The event log shows the host has come on-line is this based on you physically powering it on? 

Once the startup process has completed i.e. VMs on line and the VCSA remains off are there any entries remaining in the VirtualFileStoreProperties file?

Do you have the systems listed in a domain name server?

How many NIC are configured in host 139.4?

[BillP]

This reply was originally posted by Lee on APC forums on 7/16/2018

---

Hi,

Are there any errors logged in the VCSA during the shutdown process?

I don't see any errors in VCSA during the shutdown process. 

The event log shows the host has come on-line is this based on you physically powering it on? 

Yes. 

Once the startup process has completed i.e. VMs on line and the VCSA remains off are there any entries remaining in the VirtualFileStoreProperties file?

No, the file is empty. I made sure to check it. Unfortunately I don't remember if I did it before or after manually powering on the VCSA appliance. I could run another test if you'd like.

Do you have the systems listed in a domain name server?

No, I do not. Everything uses actual IP. 

How many NIC are configured in host 139.4?

Only one. 

[BillP · Accepted solution]

This reply was originally posted by Bill on APC forums on 7/17/2018

---

Hi Lee,

1 - would you put PCNS into debug mode and run a shutdown and start up test and then attach the error.log, EventLog.txt and the pcnsconfig.ini file. Information on how to put PCNS into debug mode will be found in FAQ FA230514

2 - In your configuration do you have a vSAN configured?