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

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

PowerChute 4.1 not behaving consistently or as expected with Smart-UPS X 3000 & VMware 5.0

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 not behaving consistently or as expected with Smart-UPS X 3000 & VMware 5.0
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
Teken
Spock Teken
110
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-08 01:47 AM . Last Modified: ‎2024-02-29 10:33 PM

0 Likes
1
552
  • 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-08 01:47 AM . Last Modified: ‎2024-02-29 10:33 PM

PowerChute 4.1 not behaving consistently or as expected with Smart-UPS X 3000 & VMware 5.0

I have a small two host VMware HA cluster that I am unable to get to (fully) gracefully shut down using the PowerChute VM.

I'm simulating a power outage by removing the main power lead from the UPS and the following occurs.

  • PowerChute reports switch to battery power
  • shutdown sequence started on hosts 1 & 2 in response to critical event: on battery
  • (most of the time, but not always) my vm's start to shut down in more or less the expected order (regular vm's, then vApps)
  • sometimes it will try and vmotion the VC and Chute VM's to another host at this point (despite the fact vmotion is not enabled in PowerChute), which fails due to the shutdown sequence having been initiated on the hosts.
  • When all the VM's on host 1 are powered down, that host DOES go into maint. mode, UNLESS it has the VC and chute on it at the time, in which case it tries to migrate them off, and (ALWAYS) fails and the process stalls entirely for that host.
  • *if* the VC and chute aren't on host 1 then generally speaking my vApp (with two VM's in it) will be on host 1 and WILL shut down the vApp and any other VM's successfully, although it has randomly started to power off the vApp VM's instead of shutting down the OS even though it is specifically defined in the vApp to shutdown the OS first for both VM's.

so then I'm left with one of either of the hosts (whichever one happens to have the VC and chute VM's on) and they sit there for a while doing nothing (checking the system logs, the Windows 2012 VC does not receive any OS shutdown request at all for some reason), THEN it gets to a point around the 30 minute mark where ChuteVM CANCELS the maint. mode of the host that still has the VM's for itself and the VC on (both still up and running), but after a couple more minutes it powers off that host without warning or maint. mode, which obviously kills both the VM's on the spot, BUT leaves the other host UP and in maint. mode and nothing further will happen without manual intervention.

When I restore power to the UPS and power the shut down host back up, it acts like you would expect after a dirty shutdown and powers up and restarts the two VM's that were already running when it went down (the VC and chute VM's), and there's where things end, no other VM's come back up and the other host stays in maint. mode even after the VC and Chute are fully up and running until I manually bring everything else up again.

I've  no AD in this environment so I have tried using a single user/pass for the chute, ups, esx hosts, vc and ilo's but it hasn't made any difference.

i've re-configured all the various shutdown timeouts both upwards and downwards by several minutes each and retested and the sequence (and failures) are always more or less the same.

the PowerChute VM has shown that as it is currently configured it IS able to shutdown VM's and vApp's, place hosts in maint. mode, shut down hosts and sometimes has shown it is able to bring it all back up again on the rare occasion most of the sequence goes correctly, but no matter what I try, it just won't do ALL of them together.

What could be going wrong?

I've attached a screenshot of the current config settings of the PowerChute VM, but I've gone as low as 0 seconds and as high as 600 seconds for all the startup/shutdown settings at this point with very little difference in the results other than the timings.

Attachments
Labels
  • Labels:
  • UPS Management Devices & PowerChute Software
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-08 01:47 AM . Last Modified: ‎2024-02-29 10:33 PM

0 Likes
0
552
  • 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-08 01:47 AM . Last Modified: ‎2024-02-29 10:33 PM

Chris,

On 10/10/2015 8:12 AM, Chris said:

(most of the time, but not always) my vm's start to shut down in more or less the expected order (regular vm's, then vApps)

Are you configuring the priority in PowerChute or on the individual hosts? With PowerChute version 4.1 and configured with vCenter shutdown priority should be configured within PowerChute not on the individual hosts. Shutdown on the host should be off.

On 10/10/2015 8:12 AM, Chris said:

sometimes it will try and vmotion the VC and Chute VM's to another host at this point (despite the fact vmotion is not enabled in PowerChute), which fails due to the shutdown sequence having been initiated on the hosts.

 Do you have HA enabled within vCenter? If so that would be the cause of the VMs attempting to migrate. 

See Answer In Context

Reply

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

Reply 1
BillP
Administrator BillP Administrator
Administrator

Posted: ‎2021-07-08 01:47 AM . Last Modified: ‎2024-02-29 10:33 PM

0 Likes
0
553
  • 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-08 01:47 AM . Last Modified: ‎2024-02-29 10:33 PM

Chris,

On 10/10/2015 8:12 AM, Chris said:

(most of the time, but not always) my vm's start to shut down in more or less the expected order (regular vm's, then vApps)

Are you configuring the priority in PowerChute or on the individual hosts? With PowerChute version 4.1 and configured with vCenter shutdown priority should be configured within PowerChute not on the individual hosts. Shutdown on the host should be off.

On 10/10/2015 8:12 AM, Chris said:

sometimes it will try and vmotion the VC and Chute VM's to another host at this point (despite the fact vmotion is not enabled in PowerChute), which fails due to the shutdown sequence having been initiated on the hosts.

 Do you have HA enabled within vCenter? If so that would be the cause of the VMs attempting to migrate. 

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