- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- point of failure on c3000
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
тАО02-26-2010 10:00 AM
тАО02-26-2010 10:00 AM
point of failure on c3000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2010 10:20 AM
тАО02-26-2010 10:20 AM
Re: point of failure on c3000
Remember, the c3000 is designed for economy, not for redundancy. For example, all of your blade LOM NIC's are hard mapped to Interconnect Bay 1. If the module in Bay 1 fails....
(you can get around this by teaming with a NIC port on a MEZZ card, but this requires you to study the Port Mappings and configure accordingly.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2010 11:03 AM
тАО02-26-2010 11:03 AM
Re: point of failure on c3000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2010 11:38 AM
тАО02-26-2010 11:38 AM
Re: point of failure on c3000
The backplane or more correct the midplane, has no active components.
There's a few components on the midplane, that hold the chassis s/n and model no and pdu type. This is for house keeping information only.
The only problem on the midplane, is damage to connectors, due to human error.
This will caurse a bay to become unuseable, and you will have to shut down all servers to replace the midplane.
But agree, you do have a single point of failure on inteconnect bays 1 and 2.
I have seen once, where the communication between the OA and the VC module in Interconnectbay 1 was lost, and we had to reseat the VC module. This did caurse a few minutes outage on the network.
BR
/jag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2010 11:38 AM
тАО02-26-2010 11:38 AM
Re: point of failure on c3000
/jag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2010 11:41 AM
тАО02-26-2010 11:41 AM