Timeout waiting for response from NMC while installing PCNS

[Anonymous user]

Hello,

I've run into the following issue while trying to install PowerChute Network Shutdown connecting to two particular UPS's: "A time out occurred while waiting for a response from +IP Address+". I can ping the NMC as well as log into the web interface from the servers I'm trying to install these on. Any ideas?

Thanks,
Gary

[Anonymous user]

Registering with Management Card(s)
Please wait.
Gathering Management Card addresses
Connecting to Management Card(s)
Sending registration to Management Card(s)
Verifying communication with Management Card(s) . . .
Registration Results:
A time out occurred while waiting for a response from 192.168.250.2

--------------

Installing on windows 7, double checked firewall, 3052 & 80 udp/tcp inbound/outbound are open. I can access the NMC web interface no problem. I logged out from the NMC web interface before installing pcns. I changed default user/pass/auth key using the same combinations in PCNS, and it's not working! I can't get passed the "A time out occurred while waiting for a response from". I am using the network interface connected to the same network where the battery is hooked up to. Netmask setting seems fine with 255.255.255.0.
Incase it helps, the NMC is running with the firmware 3.7.2 (sumx) + 3.7.3 (aos)

Aside from this issue, I have a question regarding the actual shutdown of each machine running PCNS. Is there any way to get it to hibernate instead of shutdown? Shutdown, whether it's graceful or not, kills all my procs running in the bg, and this is unacceptable!
Sorry to deviate from the current topic.. I'm lazy to make another post. 🙂

I also have a ReadyNAS NV+ which is hooked up to the same battery and supports network shutdown.. I still have yet to figure out how to make them talk to each other.. The good thing, is the NAS is debian linux, so I can hack something naughty in last case scenario.

A purely cosmetic question, is there any APC battery widget on windows 7 desktop that shows battery state? If there isn't, the devs over at APC should really make one. While functionality is my primary concern, it would blow my mind if something like this exists.

kryo edited this because kryo hit the save btn too early. Bad kryo.

[BillP]

can you please provide the config.ini from the NMC via [these instructions|http://nam-en.apc.com/app/answers/detail/a_id/9321/] and tell me what model UPS the NMC is installed into? this usually means the port that the PCNS client is registering on is unreachable, meaning its really closed or there is a subnet issue, which you mentioned both. if it was the authentication phrase, you'd get a "security information" mismatch error.

lets start with the config.ini - it could just be wrong firmware.

a gadget is not available but has been toyed around with for google gadgets by the way.

[Anonymous user]

I believe all that are left are 32-bit, though I have installed it on 64-bit machines without any issues.

[Anonymous user]

Thanks for the help. Here are the answers to your questions:

-All the machines that have this issue only have a single NIC.
-The firewall on the machines are disabled, so I'm assuming the ports are open.
-At this time I can't directly connect them, as they are production servers. I will give this a shot after hours if nothing else works.
-This is the only error I've had installing the software.
-I've been installing it on about 50 servers w/ 12 UPS's. 9 of the servers are experiencing this issue.

[BillP]

a couple questions come to mind:

* do you have multiple network interfaces on this machine? PCNS 2.2.3 should give you an option of what network interface to bind the PCNS installation to, but just incase it doesnt, PCNS will bind to the first network interface listed in the OS's binding order.
* PCNS registers with the management card on port 80. you need to verify that port 80 TCP and UDP are open as well as port 3052 TCP and UDP are open.
* if you believe these are open, you could try directly connecting the network management card to the server to rule out any network issues.
* is this the only error you have seen while installing it? no security errors? if you have seen any other errors - you need to make sure the administrator user name is the same on the PCNS installation as well as the network management card.
* lastly, you could try installating it on a different machine on the network just to see.

hope this helps and gets us started towards a resolution!

[BillP · Accepted solution]

it really sounds like a network issue to me somehow. im assuming the default gateway is the same on both the card and the client?

[Anonymous user]

Yes, I've verified that the gateway is the same.

[BillP]

Hi,

What's OS were you installing PCNS on ? Is it 64-bits eidtion?

[Anonymous user]

Issue resolved. Turns out these servers had a default subnet mask of 255.255.255.0 when they should be 255.255.252.0.

Thank you everyone for your suggestions.

Gary

[BillP]

Thank you for updating...