Force PC/Server Shutdown?

[Anonymous user]

Is there a way (possible from the console) to force the UPS to send the shutdown command to the clients? Currently, I'm setting the shutdown percentage to 80%, unplugging the UPS and waiting for the battery to drain. It would be quicker if I could force the UPS to send to the shutdown command.
Thanks in advance.
-Shawn

[Anonymous user]

IPAW and Kulot:
I FINALLY got it working! Woo-hoo! The problem was a combination of IP address changes and the authenication phrase.
Early on, when things were not working properly, I had made changes and didn't keep the changes consistant across the UPS and the 2 PC's.
Thanks again for your help and patience.
-Shawn

[BillP]

Sweet. Good job! Thanks for choosing APC.

[BillP]

what does the PCNS event log say? the PCNS service needs to be talking and communicating with the NMC properly or else it doesnt matter if the service is running. if it says powerchute cannot communicate with the management card then that is our issue.

[BillP]

hi shawn, do you want to do this from the NMC? if so, you can go to the UPS tab ->control section and do a shutdown or reboot command and there is a checkbox you can select to signal a graceful shutdown or signal powerchute client shutdown or something similar.

[Anonymous user]

Thanks! I had missed that setting in the software.
I am still having problems getting the UPS to signal the PC's to shutdown. The PC's are running Windows XP. They have PCNS version 2.24 installed. pcns.exe and pcshSvc.exe processes are running.
The PC's are listed as clients in the UPS' client list.
What am I missing?!?!?

[Anonymous user]

IPAW:
I have 2 PC's. One is located next to the UPS and the other is in my office. Communication from the client to the UPS is the issue. I made some IP address changes and lost track of the changes. The PC closest to the UPS is working properly. It is being shut down. Thank you. 🙂

The PC in my office is not being shutdown. It is listed as a client of the UPS. The event log on the client says that PowerChute cannot communicate with the Management Card. The PCNS web browser can connect to the UPS. I can see and configure the UPS from my office. I do have administravie privledge on this PC. The PNCS software was installed with admin privledge. I've rebooted the client at least twice.
There are two network switches between my office and the lab (where the UPS is located). Everything is on the same subnet. The first is a managed switch. Broadcasts and connections from the lab are not blocked. AFAIK, nothing is blocked between the lab and offices and connections can go either way on just about any port.

But for whatever reason, the UPS is not shutting down my office PC. Is there a way to see where the communication path for PCNS is broken?
Thanks,
-Shawn

[Anonymous user]

I forgot to add the the 2nd network switch is a "dumb" 5 port switch for the UPS and PC's in the lab.
Thanks,
-Shawn

[BillP]

Hi Shawn,

Have you tried running [this utility|http://nam-en.apc.com/app/answers/detail/a_id/651] to update the ip address that the PCNS client communicates with? Check and make sure that the username, password and the authentication phrase of the PCNS client & the NMC matches.You can also uninstall & reinstall the PCNS client to update those fields, there is a part in the installation process wherein the client attempts to communicate and register the client to the NMC.

Also PowerChute Network Shutdown utilizes the following TCP/IP ports: tcp/udp 3052 and tcp/udp 80. Versions 2.2.X utilizes port 6547 for instance 1, 6548 for instance 2, and 6549 for instance 3 ([from this document|http://nam-en.apc.com/app/answers/detail/a_id/2910].)

[BillP · Accepted solution]

yes, the problem is that the service is not communicating with the NMC. thus, its not getting the signal from the NMC for when to shutdown. you will want to check the items that kulot mentioned like the authentication phrase. it should be admin user phrase in both spots as default or at least the same in both spots. as a test, i don't suppose you can directly connect the NMC and client PC together? i assume they arent close enough.