- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: More strange OA3.20 / VC3.10 Firmware behaviou...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2010 07:55 AM
11-09-2010 07:55 AM
More strange OA3.20 / VC3.10 Firmware behaviour
Following on from earlier post, we recently saw very bizarre behaviour (only affecting ESX blades)... We were doing some final proving of a new chassis to make sure HPSIM alerts came through etc and performed these tasks in a chassis with ALL firmware up to date, blades, interconnects OAs etc...
- OA switched Active to Standby (1 -->2) (F/W v3.20)
- OA switched Active to Standby (2 -->1) (F/W v3.20)
- Fibre uplink removed from Bay 2, Connection X1
- Link down confirmed
- Fibre uplink replaced into Bay 2, Connection X1
- Link up confirmed
- Flex10 in Bay 2 powered down via OA (F/W v3.10)
- Link down confirmed
- Flex10 in Bay 2 powered on via OA (F/W v3.10)
- Link up confirmed
All Windows and RHEL blades were fine - detecting down links and sending alerts happily. But... One of the 3 ESX blades we have went Profile Pending and needed to be powered down to recover as it stopped responding. The other 2 blades stayed up but their VC profiles showed no networks. When they were powered down they had to be physically removed and reinserted into their bays as they would not power on...
Strange thing is this issue from 2008 is almost the same scenarios just in a different order: http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1288974357011+28353475&threadId=1207080
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2010 11:28 AM
11-10-2010 11:28 AM
Re: More strange OA3.20 / VC3.10 Firmware behaviour
Can you give more details about the ESX blades (ESX or ESXi Build Number and ProLiant type/generation) and the nic firmware and driver, please?