Error registering with the Network Management Card(s).

[apc15kva_apc]

This was originally posted on APC forums on 1/16/2015

---

Hello Community,

I'm trying to configure PowerChute on vMA in order to shutdown virtual machines on vmware.

After installing PowerChute, I'm starting setup wizard and getting in trouble:

The Error message: PowerChute is not receiving data from the Network Management Card.

I've already checked all this options, but nothings resolve the issue.

1. Verify that the Administrator Username and AuthenticationPhrase are the same for PowerChute and the NMC.
2. Verify that UDP port 3052 is not being blocked by a firewall.
3. Check the IP settings on the PowerChute machine and on the NMC user interface to verify that the default gateway and subnet mask are correct.
4. Update the firmware on the NMC to the latest version which can be downloaded from the APC Web site, or contact APC Customer Support.

In the PowerChute logs I can see:

Time	IP address	Description
14:21:18	x.x.x.31	Waiting for Network Management Card response.
14:21:18	x.x.x.31	Registering x.x.x.35 http://x.x.x.31:80.
14:21:18	x.x.x.31	Connected to Network Management Card.
14:21:18	x.x.x.31	Checking connection to http://x.x.x.31:80

The UPS Network Management Card is  AP9631

Please help

[BillP]

This reply was originally posted by Robert on APC forums on 1/16/2015

---

Hi,

I am getting the same error, but not with a VM. I have installed this with no problem on several servers, but for some reason it won't register with this one server. I have tried all the same steps to resolve the issue, but nothing has worked. The weird thing is I know its talking to the Network Management Card because when I go into the card directly under PowerChute Network Shutdown Clients it shows the IP of the server failing to register.

However, when I am going through the cfg wizard to register this server no matter what I try I always get the following.

The Error message: PowerChute is not receiving data from the Network Management Card.

I would also appreciate some troubleshooting assistance.

Thanks,

Bob

[BillP]

This reply was originally posted by Bill on APC forums on 1/16/2015

---

Hi,

I assume you are installing PCNS 3.1 on vMA 5.5.

PCNS uses port 80 when registering with the NMC so you need to verify that port 80 is open. If it is then I suggest manually registering PCNS with the card. First stop PCNS daemon on the vMA. The command is sudo /etc/init.d/PowerChute stop. Then go to /opt/APC/PowerChute/group1 (this is assuming you installed to the default path) and edit pcnsconf.ini You should enter the ip address of the NMC, change enrolwithNMC to false, and enter the user name and password. NOTE: user name and password entries need to be added completely as they are not saved in the ini file and will be deleted once the daemon is restarted.

Example:

[NetworkManagementCard]
mode = single
IP_1 = (NMC IP address)
port = 80
protocol = http
enrolWithNMC = false

username = (must match NMC)

password = (your choice)
acceptCerts = false

Also, under the section for [Networking] enter the ip address of the vMA

Example:

localHostAddress = 192.168.1.100

Then log onto the NMC and under the PowerChute section add the IP address of the vMA. After adding the vMA IP address to the NMC log back into the vMA and restart PCNS sudo /etc/init.d/PowerChute start.

You should then be able to log into PCNS web interface on the vMA using the user name and password enter earlier and complete the setup. Once the setup is completed you should stop PCNS again, change enrolWithNMC back to true and then restart PCNS. If in the event log you get an error stating the “Security information for http://x.x.x.x:80 is incorrect.” go to communication settings and enter the authentication phrase and click apply.

If you are still having an issue have entering the IP address manually look in /opt/APC/PowerChute/group1/error.log It should list what the cause of the communication issues are.

[apc15kva_apc]

This was originally posted on APC forums on 1/19/2015

---

Thanks for your reply,

here is the error I'm receiving in log (/opt/APC/PowerChute/group1/error.log)

ERROR pool-1-thread-8 com.apcc.pcns.datagramservice.DatagramTask - java.net.SocketTimeoutException: Receive timed out
ERROR pool-1-thread-8 com.apcc.pcns.datagramservice.DatagramTask - java.net.SocketTimeoutException: Receive timed out
ERROR pool-1-thread-8 com.apcc.pcns.datagramservice.DatagramTask - java.net.SocketTimeoutException: Receive timed out
ERROR pool-1-thread-8 com.apcc.pcns.datagramservice.DatagramTask - java.net.SocketTimeoutException: Receive timed out
ERROR Thread-2 com.apcc.m11.components.StdPowerSource.EventRules.OverloadStatusRule - com.apcc.m11.arch.CommunicationException
ERROR Thread-2 com.apcc.m11.components.StdPowerSource.EventRules.PowerSourceTurnOffInitiatedRule - com.apcc.m11.arch.CommunicationException

[BillP · Accepted solution]

This reply was originally posted by Bill on APC forums on 1/19/2015

---

Hi,

Where these errors logged after you followed the steps to add the IP address manually and started PCNS and are you running PCNS 3.1 on vMA 5.5? The errors indicate that PCNS is not receiving any packets from the NMC. Would you provide the pcnsconfig.ini file and the NMC config.ini file.

If your not comfortable providing the info through the forum you can contact local technical support http://www.apc.com/site/support/index.cfm/contact-information/ and they will be glad to help you.

[apc15kva_apc]

This was originally posted on APC forums on 2/3/2015

---

Thanks for the Help.

But I downloaded a PCNS as an .OVA and deployed it on vmware, after that the communication works perfect!

[PJW2016_apc · Accepted solution]

This was originally posted on APC forums on 3/2/2016

---

Hi. I had exactly the same issue. Turns out (on my system at least) when the install adds the Windows Firewall Rules it only adds them to the public network. I went into the Firewall settings and changed it to apply the rules to the Domain Network and it worked perfectly.

[premax]

Thank you for the public firewall hint. Worked for me too.