Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84437members
353635posts

Powerchute stops communicating after config.ini upload

APC UPS Data Center & Enterprise Solutions Forum

Schneider Electric support forum for our Data Center and Business Power UPS, UPS Accessories, Software, Services, and associated commercial products designed to share knowledge, installation, and configuration.

Solved
Ryder_apc
Crewman
Crewman
0 Likes
1
165

Powerchute stops communicating after config.ini upload

This was originally posted on APC forums on 3/24/2020


I'm currently looking at updating Power Group settings and Battery Low Durations on about 100 UPSs with NMC2 cards in them. I understand the best way to do this in a bulk operation is using the FTP based APC INI Utility?

I've been testing this and after uploading the config.ini to the NMC I've been discovering that PowerChute on the associated server is no longer able to communicate with the NMC. The PowerChute log displays: "PowerChute is not Receiving Data from the Network Management Card"

To fix the issue I have found I needed to uninstall PowerChute on the server and re-register it with the NMC. I'm after clarification on what may be happening here? Is there a key I'm wiping out on the NMC and breaking the association and if so is there a way to still perform the bulk upload without breaking the NMC's association with PowerChute?

Anyone's advise greatly appreciated, thanks in advance!


Accepted Solutions
BillP
Administrator Administrator
Administrator
0 Likes
0
165

Re: Powerchute stops communicating after config.ini upload

This reply was originally posted by Bill on APC forums on 3/24/2020


Hi,

When running the PowerChute Setup wizard PowerChute registers with the NMC. Once registered the NMC send a UDP packet every 25 seconds to the network segment of the registered PowerChute Clients. Example: PowerChute server is on network segment 10.0.0.1. Every 25 seconds the NMC send a UDP packet to 10.0.0.255. 

I would first check to see if the PowerChute Agent IP is still registered with the NMC. You can check via the GUI under Configuration - PowerChute Clients. To check using config.ini the info is saved under [PowerChute]. If still registered the next thing to check is to see if the packets are being sent and that the IP address of the sender matches the NMC address the PowerChute Client is expecting the packet from. To check the registered NMC in the PCNS GUI go to UPS Configuration. To check in the pcnsconfig.ini the NMC IP is save under [NetworkManagementCard]. To check for the packet, I run Wireshark.

As for uninstalling, have you tried to stop the PowerChute service and restart? When the service is started PowerChute will connect to the NMC assuming you have not changed enrolWithNMC = true to enrolWithNMC = false in pcnsconfig.ini. 

 

See Answer In Context

1 Reply 1
BillP
Administrator Administrator
Administrator
0 Likes
0
166

Re: Powerchute stops communicating after config.ini upload

This reply was originally posted by Bill on APC forums on 3/24/2020


Hi,

When running the PowerChute Setup wizard PowerChute registers with the NMC. Once registered the NMC send a UDP packet every 25 seconds to the network segment of the registered PowerChute Clients. Example: PowerChute server is on network segment 10.0.0.1. Every 25 seconds the NMC send a UDP packet to 10.0.0.255. 

I would first check to see if the PowerChute Agent IP is still registered with the NMC. You can check via the GUI under Configuration - PowerChute Clients. To check using config.ini the info is saved under [PowerChute]. If still registered the next thing to check is to see if the packets are being sent and that the IP address of the sender matches the NMC address the PowerChute Client is expecting the packet from. To check the registered NMC in the PCNS GUI go to UPS Configuration. To check in the pcnsconfig.ini the NMC IP is save under [NetworkManagementCard]. To check for the packet, I run Wireshark.

As for uninstalling, have you tried to stop the PowerChute service and restart? When the service is started PowerChute will connect to the NMC assuming you have not changed enrolWithNMC = true to enrolWithNMC = false in pcnsconfig.ini.