Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Error message on blade enclosure
ProLiant Servers (ML,DL,SL)
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-03-2004 06:18 AM
03-03-2004 06:18 AM
Error message on blade enclosure
We have 5 blade enclosures with the integrated switches that we connect to Cisco 6006 switches via etherchanneling the gigabit ports (Compaq nomenclature is trunk). They've run OK for almost 2 years. We had a problem last week where one of the blade enclosures began spewing the following error message in the Integrated Admin log:
crit mgmt: Integrated Administrator was reset by ESR / Watchdog Timer.
This was happening every 30 seconds or so. The other four enclosures then began showing the same message; then the Cisco switch ports went into errdisable mode and began reporting a spanning tree loop on the ports connected to the enclosures. I had to unplug the gigabit ports on all five enclosures, leaving only the port 24 management port on switch A active. Then I was able to plug the gigabit ports back in. Resetting the first enclosure had no effect.
What would cause this error message? I've found no reference to it in any documentation.
crit mgmt: Integrated Administrator was reset by ESR / Watchdog Timer.
This was happening every 30 seconds or so. The other four enclosures then began showing the same message; then the Cisco switch ports went into errdisable mode and began reporting a spanning tree loop on the ports connected to the enclosures. I had to unplug the gigabit ports on all five enclosures, leaving only the port 24 management port on switch A active. Then I was able to plug the gigabit ports back in. Resetting the first enclosure had no effect.
What would cause this error message? I've found no reference to it in any documentation.
1 REPLY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-04-2004 01:17 AM
03-04-2004 01:17 AM
Re: Error message on blade enclosure
This may sound like I'm stating the obvious but... apparently the enclosure couldn't refresh the watchdog timer before it expired. So - I would normally suspect a firmware or hardware issue with the enclosure.
You would want to have the latest firmware on the enclosure and then look at the health LEDs for other signs of problems.
You said 4 enclosures did this around the same time so it doesn't make sense that you would have so many hardware failures.
Perhaps something happened on the network that exposed a firmware bug? Why would it go away all of a sudden?
You would want to have the latest firmware on the enclosure and then look at the health LEDs for other signs of problems.
You said 4 enclosures did this around the same time so it doesn't make sense that you would have so many hardware failures.
Perhaps something happened on the network that exposed a firmware bug? Why would it go away all of a sudden?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP