- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect failover times
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
02-04-2011 08:22 AM
02-04-2011 08:22 AM
Virtual Connect failover times
Steve was looking for some advice on "normal" Virtual Connect failover times:
*******************
I’m looking for any general guidelines or experience for failover times from one VC to another. I have a customer that has a few servers configured with NIC teaming with connections coming from multiple VC modules –as expected these nodes do not lose IP connectivity during VC failover. However, they have more servers that are not configured with NIC teaming and as expected during VC failover they lose IP connectivity until the standby VC can takeover. In these cases, the failover and loss of IP connectivity is taking anywhere from 45 seconds to 2 minutes.
Is there a “normal” time for failover in these cases?
********************
Lionel gave his opinion:
***************
Really depends on your configuration and the raison of the failure but in all situations NIC teaming is really recommended. A 45s to 2mn is in my opinion something normal during VC FW upgrade operation but if you get such long delays after an uplink failure in an Active/Standby configuration, something else might be the cause of this long delay.
************************
Cullen also joined in:
*********************
As I recall, the major cause of long delays is the updating of tables in the upstream switches. The switches don’t change their MAC address tables until they either receive packet from the system or the existing entry ages out.
***********************
Share your experiences and what you have seen in failover times.