Ask our Experts
Didn't find what you are looking for? Ask our experts!
Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Search in
Free
EnglishStrengthen your foundational knowledge in Data Centers for free, enroll in this path today and start your learning journey!
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-08 01:39 AM . Last Modified: 2024-02-29 10:38 PM
Hi everyone,
I'm seeing this across the board on several identical AP9631 cards all connected to a Cisco switch (that seems to be the common denominator):
Chronic problem with AP9631 management card rebooting itself with DNS Network Error No route to host and repeating the two errors 20-30 times right before the watch dog reboot:
09/12/2015 11:07:47 System DNS Network Error, Host is down.
09/12/2015 11:07:47 System DNS Network Error, No route to host.
09/12/2015 11:07:46 System DNS Network Error, Host is down.
09/12/2015 11:07:46 System DNS Network Error, No route to host.
09/12/2015 11:07:46 System DNS Network Error, Host is down.
09/12/2015 11:07:46 System DNS Network Error, No route to host.
09/12/2015 11:07:45 System DNS Network Error, Host is down.
09/12/2015 11:07:45 System DNS Network Error, No route to host.
09/12/2015 11:07:45 System DNS Network Error, Host is down.
When looking at the crash dump of the AP9631 one clearly sees a watch dog timer forced reboot:
Bottom of stack written to and Unknown Reset
I've taken this up with support and they had sensible suggestions but they don't know the cause. Obvisouly the DNS server isn't down and that's some kind of fake error. I have ton of AP9631 but only those connected to the Catalyst seem to be experienceing this issue. The rest have never rebooted by writing to the bottom of the stack. Support had suggested defective AP9631 but I'm just not buying it.
If you have seen this issue and know of a true cause please let me know! Thank you everyone!
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:39 AM . Last Modified: 2024-02-29 10:38 PM
Haven't seen it myself, but after it happens, you might want to post the debug tarball. In the latest firmware it's under About->Support->Generate Logs.
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:39 AM . Last Modified: 2024-02-29 10:38 PM
Haven't seen it myself, but after it happens, you might want to post the debug tarball. In the latest firmware it's under About->Support->Generate Logs.
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
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.