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
84629members
353953posts

AP9640 9.5 Minute Network Timeout Error

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.

AlexD
Crewman
Crewman

AP9640 9.5 Minute Network Timeout Error

My APC NIC appears to hit the 9.5 minute timeout. I have multiple UPS NICs on the same network/subnet that all work. I can ssh into the NIC and ping the default gateway. I have snmpv3 setup and can poll from the snmp server. The polling is set to occur every 60 seconds. I have tried rebooting the NIC and have not had any success.  I have tried disabling the firewall and still no change. Is there a bug related to the timeout not being refreshed?

 

 

Attachments
Tags (1)
2 Replies 2
BillP
Administrator Administrator
Administrator
0 Likes
1
524

Re: AP9640 9.5 Minute Network Timeout Error

@AlexD 

 

I suggest you upgrade to the latest firmware. 

UPS Network Management Card 3 Firmware v2.0 for Smart-UPS with AP9640/41/43 - APC USA

 

 

A very important point to keep in mind for the 2.0.0.5 update is that once an NMC3 is updated to this version, it cannot be downgraded back prior to this revision. 

Tags (1)
AlexD
Crewman
Crewman
0 Likes
0
466

Re: AP9640 9.5 Minute Network Timeout Error

@BillP 

 

I upgraded to v2.0.0.5 on 3/14 for all eight NICs we have and am still experiencing the same issue with this one NIC.  The other seven NICs do not have this issue.  They all reside on the same subnet. I am able to web and ssh from another subnet to all the NICs. I am able to poll using our snmp server, which is in another subnet. I don't believe this to be a routing issue at this point. Disable/enabling the firewall does not make a difference either.

Tags (1)