- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Flex-10 modules lose access to server profiles
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
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
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
тАО04-19-2011 03:53 AM
тАО04-19-2011 03:53 AM
Flex-10 modules lose access to server profiles
We have a c7000 Blade enclosure with 2 Flex-10 modules. On occasion both Flex-10 modules hang. We try re-seating the Flex-10 modules, powering off the chassis, etc. etc. nothing seems to work.
We then did a firmware upgrade from 3.15 to 3.17 and the Flex-10s worked again, and all the profiles were present.
I have been told it could be related to a DNS problem embedded in the Flex-10?
We are considering implementing a second c7000 to provide redundancy for the first one. The Blades are running the VMware virtualisation software. But if we lose the first c7000 enclosure will the virtual machines be able to failover to the second c7000 if the Flex-10 modules are down?
Any input would be appreciated.
Thanks
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2011 05:37 AM
тАО04-19-2011 05:37 AM
Re: Flex-10 modules lose access to server profiles
Problem was with all vc enet interconnects with dns set, not just flex 10.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2011 06:21 AM
тАО04-19-2011 06:21 AM
Re: Flex-10 modules lose access to server profiles
Regards
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2011 06:27 AM
тАО04-19-2011 06:27 AM
Re: Flex-10 modules lose access to server profiles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2011 01:10 PM
тАО04-20-2011 01:10 PM
Re: Flex-10 modules lose access to server profiles
Did you assign 10.x.x.x IP addresses to your flex / VC modules? If so, this caused the problem.
What is frustrating is: it appears HP was aware of this problem. This is a bug, which translated 10. from ASCII to binary (ASCII 1 is 49, ASCII 0 is 48, ASCII . (period) is 46) giving a class C address in the 49.48.46.0 range. The bug was ignored, because that class C was not valid.
This Class C was allocated mid February. DNS queries to this (previously bogus) class C began to resolve, and returned errors. For instance, nslookup (for the 4 ASCII characters of 10.1) of 49.48.46.49 shows
mx-ll-49.48.46-49.dynamic.3bb.co.th
This was discovered (and reported on the SAN security mailing list) when outbound SSH connections to this Class C were observed by sites following best practice and monitoring outbound connection attempts
This caused a huge problem around the world. You could be affected if you were running any c class chassis with any virtual connect. The temporary fix was to erase the DNS server settings in the OnBoard admin under Enclosure Bay IP Addressing (for each tab). Sometimes that resulted in a complete reset of the V/C interconnect devices.
You can find several other ITRC threads on this topic, including the customer advisory; but now the firmware upgrade should fix it.
A powerful reminder: firmware is the new single point of failure. You could have 100 chassis, and every one of them might have failed at the same time if 10.x.x.x addresses were in use...