Multiserver Shutdown using NMC2 (green) with Powerchute Network Shutdown

BillP · ‎2021-07-01

For the last twenty years, give or take, I have been using APC Smartup's with the Shareups, generally the AP9607 box to shutdown multiple servers, and it has worked well. I have just replaced two SU2200RM3U units with the newer SMT2200. When I purchased these, I also added the AP9630 Network Management Cards to each unit since these newer units no longer work with the 8 port share-ups box. Now I want this "new hardware" to perform the same functionality as the old. I've made two calls to support, and got no where. The first couldn't answer my questions, and then sent me links to things to read. Last night wasn't much better, other than I was told it's not possible to confirm the shutdowns, so I need to make a guesstimate of shutdown times for my Oracle and SQL servers. I find it very hard to believe after all these years that APC would take steps backwards, and I just need to find someone familiar with the ways the Shareups works, and "translate" that to the newer equipment and provide a bit of guidance on this.

The configuration I've used successfully over years is as follows:

Smartups (SU2200 - 3000's) > AP9607 Shareups > Basic Signaling to Servers with Power Chute Network Edition configured each device. AP9607 setup for Confirmed Shutdown before powering off

If power is out for 5 minutes, begin shutdown. (Buildings are generally have backup generators, if they don't start I got other problems)

Each unit shutdown is at it's own rate. Some servers on a single UPS will only take a minute or two, others like the DB servers make take 10+ minutes.

Each server signals the AP9607 that it is shutdown. If I remember correctly, it drops power to a pin on the cable connected to the AP9607 Share-ups

After ALL servers connected to an individual UPS are down, the Smartups then powers off. This method would guarantee no crashing of the servers. (Unless the batteries were bad/old and could not provide the needed runtime to begin with.)

Upon restoration of power, I wait 3 minutes to make sure power is back, and just not a short bump. ALSO, the UPS's were configured to NOT power on until they were recharged to 50% or better. Once both the time and the charge were satisfied, the Smartups would power back on bringing the equipment back on line.

The cards are the latest AP9630's version 6.0.6 with the green interface. They are installed, and they can be accessed via the browser. IP's assigned, notifications work, and client devices can see then with the Powerchute Network Shutdown software. I need info on how to get them configured like I have in the past. Any help would be appreciated.

Thanks

BillP · ‎2021-07-01

Hello,

This should definitely be possible without issue. It seems to be a pretty standard request so I am a little concerned you could not get the answers you needed. I'll see what I can comment on. Before I do, I did want to mention we will be coming out with a replacement for the AP9607 SmartSlot card that is compatible with SMT and SMX model UPSs. It won't be out until later this summer - AP9624. The Network Management Card is much more powerful though.

Firstly, firmware v6.0.6 has a few major issues we corrected in v6.1.1. I would suggest updating if you can. It will have no bearing on anything we'll discuss but I noticed you mentioned 6.0.6 (more info here -> Network Management Card 2 Firmware v6.X.X FAQ/Upgrade Issues | FAQs | Schneider Electric US).

Secondly, this should be pretty easy. I'd note your available runtime on battery. Then, on all of your PowerChute Network Shutdown clients, you'll just want to set the Event (Under Event Actions) of UPS: On Battery to trigger a system shutdown after 5 minutes (and depending on each server, you could set this time differently). Then, this should cause the particular client to start a shutdown. Alternatively, you can also do it using the Runtime remaining above/below threshold events. There is a good example in the help file doing it that way with some pictures that I think are helpful. This also might be a better way to do it depending on how much runtime you typically have available.

On the last server to shutdown (that takes the longest), then you can configure the PowerChute Network Shutdown setting for "Turn this UPS off" under Shutdown settings so that when that client is done, it tells the UPS to turn off. I think that is the bulk of the configuration right there..

Then, on the NMC, you can configure the UPS to wait until it has X amount of runtime available before it turns on. (The older UPS models used to do it based on capacity but the newer ones do it based on available runtime to make it easier for the user). You can also set any extra shutdown or return delays for the UPS here if you want a little extra padding.

I also find the PowerChute Network Shutdown help file very informative and it even provides example scenarios and timelines for shutdown. You can get to this by clicking the ? at the top of the screen.

I hope that gets you started. Let us know if you have further questions.

See Answer In Context

BillP · ‎2021-07-01

The AP9624 has two DB-9 ports for simple signaling and a mini USB for firmware upgrade only. And yes, with 6.0.6 we had some config.ini upload issues. But, if you upgraded from v5->v6 (meaning your card didn't come with 6.0.6) then event notifications would get reset since they cannot be maintained. And yes, I agree, i don't think it impacts any configuration, just the bugs.

Sounds good. Yes, please let us know if you have any further questions. I will have to defer to Bill P. on the "confirm" part of the shutdown because I think he knows it a little better but I did think there was some mechanism to confirm on the same level as the AP9607. Also, once the UPS gets to a low battery state, so by default with two minutes of runtime remaining, the UPS throws out a "low battery signal" that any associated PCNS client would see and shutdown if it hasn't been configured to shutdown earlier. So it is sort of a way to "idiot" proof the configuration but it could present a problem if two minutes is not long enough for a server to shutdown that hadn't been told to shutdown prior. I think is similar to what the AP9607 ultimately does too.

BillP · ‎2021-07-01