- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Cycling the VC ENet modules.
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
тАО10-22-2008 08:26 AM
тАО10-22-2008 08:26 AM
Cycling the VC ENet modules.
The integrated NICs are set up on the OS side as 2 x Teamed-Pairs, and currently the NICs connected to IC1, (i.e. NIC1 and NIC3) are active.
The uplinks on the two VC modules are setup as uplink sets where each module has a single uplink set comprising 8x1GB links to a single network switch. The other VC module is set up the same, except that it connects to a different network switch.
Currently, the VC module in IC1 is active.
1. If I cycle (pull) the module in IC1, the connectivity will fail over to the module in IC2, correct.
2. Would I be correct in assuming that anyone connected to one of the blades would loose connectivity?
3. How long would the failover take?
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-22-2008 12:12 PM
тАО10-22-2008 12:12 PM
Re: Cycling the VC ENet modules.
3. 3-4 pings when for example total failure for IC1
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2008 03:22 AM
тАО10-23-2008 03:22 AM
Re: Cycling the VC ENet modules.
Dave.
The reason I ask is that I just completed a VC firmware upgrade, (to 1.32), and finished with the module in IC2 as the active module.
Just for consistency, I would like to fail it back to IC1.
Also, unlike the OA, there is no indicator (LED) to show which module is currently active.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2008 09:24 AM
тАО10-23-2008 09:24 AM
Re: Cycling the VC ENet modules.
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2008 09:30 AM
тАО10-23-2008 09:30 AM
Re: Cycling the VC ENet modules.
DAve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2008 09:31 AM
тАО10-23-2008 09:31 AM