Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

PowerChute 4.1 starts vCenter server before last host is going down

APC UPS Data Center & Enterprise Solutions Forum

Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • APC UPS, Critical Power, Cooling and Racks
  • APC UPS Data Center & Enterprise Solutions Forum
  • PowerChute 4.1 starts vCenter server before last host is going down
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
BillP
Administrator BillP Administrator
5060
voidstar_apc
Janeway voidstar_apc
196
Erasmus_apc
Sisko Erasmus_apc
112
TheNotoriousKMP_apc
Sisko TheNotoriousKMP_apc
108
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to APC UPS Data Center & Enterprise Solutions Forum
Solved
BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

0 Likes
6
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

PowerChute 4.1 starts vCenter server before last host is going down

Hello all,

We decided to use last version of PCNS 4.1 in our company for shutdown VMs, hosts and UPS after switching on battery. So before using it in production we run some tests. In our test environment we can`t shutdown the UPS.

Test environment:
2 ESXi hosts in HA cluster (ESXi 5.5 Update 3b build: 3248547)
1 UPS - Symmetra RM6000 with NMC - AP9619
vCenter Server 5.5 Update 3b (build: 3252642) running on VM (OS: Windows Server 2008 R2)
PowerChute Network Shutdown 4.1 deployed on cluster as VMware Virtual Appliance. PowerChute is configured to shutdown after getting UPS event "Manual Bypass" with delay 30 seconds.

Before switching UPS to Manual Bypass two VMs (vCenter server and PowerChute) are located on second host and there are tied to second host by DRS rules.

After switching UPS to Manual Bypass all going well, all VMs gracefully shutdown except VC and PowerChute, first host switches to maintenance mode and shutdown, then vCenter server shutdowns and after some time first host gets command to shutdown, but before it powered off PowerChute starts vCenter server. After some seconds second host goes down.

We performed test twice and both times vCenter server starts before second hosts goes down.

This is a normal behavior of the procedure of shutdown? We need to start vCenter server only after start up the hosts. How to achieve this?

Time period in log files of shutdown process is 08/04/2016 11:07:54 - 08/04/2016 11:37:48

Thanks in advance!

Labels
  • Labels:
  • UPS Management Devices & PowerChute Software
  • Tags:
  • appliance
  • esxi
  • firmware
  • pcns
  • PowerChute
  • shutdown
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2025-04-16 12:28 PM

0 Likes
0
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2025-04-16 12:28 PM

Hi,

Sorry for the delay in my response. I have been on holiday. 

I think the issue is due to the locking mechanism in VirtualizationFileStore.properties and a mismatch in the Hostname/FQDN between vCenter Server and what's configured locally on the ESXi hosts.

05-08-16 08:22:00,337 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - getHostUsingIPOrDNSName - Host IP: esxru0321cl001.mycompany.com
05-08-16 08:22:00,367 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found [1] hostSystemEntites
05-08-16 08:22:00,370 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found hostSystem esxru0321cl001

05-08-16 08:22:02,189 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - getHostUsingIPOrDNSName - Host IP: esxru0321cl002.mycompany.com
05-08-16 08:22:02,224 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found [1] hostSystemEntites
05-08-16 08:22:02,226 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found hostSystem esxru0321cl002

While vCenter Server is online the host lock will be added to VirtualizationFileStore.properties as:

esxru0321cl001.mycompany.com
esxru0321cl002.mycompany.com


After VCSA goes offline and PCNS connects directly to the host, the ESXi host name is returned as esxru0321cl001, and esxru0321cl002 instead of esxru0321cl001.mycompany.com, esxru0321cl002.mycompany.com - so the locks get removed and PCNS incorrectly attempts to start the VCSA VM.
-
The Solution to this is to update the Hostname on each of the ESXi hosts to make sure that it uses the FQDN. Using vSphere Client go to Configuration - DNS and Routing - check that Name and Domain are correct. Also in MOB browser check that FindByIP and FindByDNSName return the FQDN.

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Replies 6
BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

0 Likes
0
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

Hi,

I think increasing the value below in the pcnsconfig.ini file would prevent the issue from occurring. It seems to be taking awhile for the ESXi host to shut down.

[HostConfigSettings]
delay_after_exit_maintenance_mode = 30

Try increasing the number to 60 or 90 for example.

Reply

Link copied. Please paste this link to share this article on your social media post.

BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

0 Likes
0
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

Thanks Bill for the quick answer!

I will test shutdown process with new value of option delay_after_exit_maintenance_mode tomorrow and post the results. 

Reply

Link copied. Please paste this link to share this article on your social media post.

BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

0 Likes
0
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:05 AM . Last Modified: ‎2024-01-31 02:56 AM

Hi,

I performed three shutdown tests with options below:
1) delay_after_exit_maintenance_mode = 60
2) delay_after_exit_maintenance_mode = 90
3) delay_after_exit_maintenance_mode = 30 and delay_after_vcsa_powered_on_and_connected = 60

and I have the same issue with starting of vCenter server before last host is powered off.

I attached log files for three tests:
1) 1_error.log, 1_EventLog.txt, 1_pcnsconfig.ini (Time period of shutdown process: 08/05/2016 08:18:12 - 08/05/2016 08:24:18)
2) 2_error.log, 2_EventLog.txt, 2_pcnsconfig.ini (Time period of shutdown process: 08/05/2016 11:14:47 - 08/05/2016 11:20:25)
3) 3_error.log, 3_EventLog.txt, 3_pcnsconfig.ini (Time period of shutdown process: 08/05/2016 14:46:56 - 08/05/2016 14:52:30)

Do you have any suggestions for solve this issue?

Thanks!

Reply

Link copied. Please paste this link to share this article on your social media post.

BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2024-01-31 02:56 AM

0 Likes
0
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2024-01-31 02:56 AM

Up!

Reply

Link copied. Please paste this link to share this article on your social media post.

BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2025-04-16 12:28 PM

0 Likes
0
1904
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2025-04-16 12:28 PM

Hi,

Sorry for the delay in my response. I have been on holiday. 

I think the issue is due to the locking mechanism in VirtualizationFileStore.properties and a mismatch in the Hostname/FQDN between vCenter Server and what's configured locally on the ESXi hosts.

05-08-16 08:22:00,337 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - getHostUsingIPOrDNSName - Host IP: esxru0321cl001.mycompany.com
05-08-16 08:22:00,367 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found [1] hostSystemEntites
05-08-16 08:22:00,370 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found hostSystem esxru0321cl001

05-08-16 08:22:02,189 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - getHostUsingIPOrDNSName - Host IP: esxru0321cl002.mycompany.com
05-08-16 08:22:02,224 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found [1] hostSystemEntites
05-08-16 08:22:02,226 DEBUG Thread-32 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - Found hostSystem esxru0321cl002

While vCenter Server is online the host lock will be added to VirtualizationFileStore.properties as:

esxru0321cl001.mycompany.com
esxru0321cl002.mycompany.com


After VCSA goes offline and PCNS connects directly to the host, the ESXi host name is returned as esxru0321cl001, and esxru0321cl002 instead of esxru0321cl001.mycompany.com, esxru0321cl002.mycompany.com - so the locks get removed and PCNS incorrectly attempts to start the VCSA VM.
-
The Solution to this is to update the Hostname on each of the ESXi hosts to make sure that it uses the FQDN. Using vSphere Client go to Configuration - DNS and Routing - check that Name and Domain are correct. Also in MOB browser check that FindByIP and FindByDNSName return the FQDN.

Reply

Link copied. Please paste this link to share this article on your social media post.

BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2024-01-31 02:56 AM

0 Likes
0
1903
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-07-26 03:06 AM . Last Modified: ‎2024-01-31 02:56 AM

Hi,

After filling Domain name in all hosts of HA cluster the issue is no longer appear. I was checked this twice with shutdown the UPS on production environment. Before that Domain name was missing on all hosts.

Thank you Bill for your help!

Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of