APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
This is my first discussion here, i hope it will be useful for me and others.
I'm trying to install powerchute on TMG 2010 and i had this annoying message
PCNS is not recieving data from NMC
I don't know what to do.
FYI my UPS is APC Smart-UPS RT 8000VA
Thanks in advance
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Well, I'm flummoxed as to WHY this makes a difference, but it certainly does.
A subnet mask of (server) 255.255.0.0 with (ups) 255.255.255.0 causes a failure in registration and communication.
Changing either one to match fixes the issue. I have been a network engineer for 20+ years and this is the first time I've ever encountered such a thing. Is it an artifact of how you guys are doing your UDP stack?
Regardless I'm just happy to have an answer. It's much easier for me to change the server routing than to try a work-around for the powerchute notification.
I would suggest that you add matching subnet masks to the checklist on the configuration page, because it took me 2 days of searching to find this bit of info.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Hi,
Please review Kbase FA159624 "Communication lost with Powerchute Network Shutdown" In most cases if PowerChute registers with the NMC and then losses communications the issue is with the subnet mask of the NMC not matching the system PowerChute has been installed on.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
subnet mask of NMC is right i already register 4 servers to that UPS and connection is up no loss of communications
The problem shows with TMG only !!!!
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Hi,
What are the network settings for the NMC and Computer (please provide screenshots)? Also, when is the failure happening? When running the configuration wizard or once the configuration has been completed?
FYI: When attempting to connect using the configruation wizard TCP port 80 is used. Once the system has registered with the NMC comminucation between the OS and NMC is over UDP port 3052.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:40 AM . Last Modified: 2024-02-29 10:37 PM
Well, I'm flummoxed as to WHY this makes a difference, but it certainly does.
A subnet mask of (server) 255.255.0.0 with (ups) 255.255.255.0 causes a failure in registration and communication.
Changing either one to match fixes the issue. I have been a network engineer for 20+ years and this is the first time I've ever encountered such a thing. Is it an artifact of how you guys are doing your UDP stack?
Regardless I'm just happy to have an answer. It's much easier for me to change the server routing than to try a work-around for the powerchute notification.
I would suggest that you add matching subnet masks to the checklist on the configuration page, because it took me 2 days of searching to find this bit of info.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.