- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Cisco Blade Switch 3120x SFP failure
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
03-02-2012 12:14 PM
03-02-2012 12:14 PM
Cisco Blade Switch 3120x SFP failure
John had a question on link failover:
******************
I have a customer who, after having a SFP fail on a Cisco Catalyst Blade Switch 3120x, are saying all but one of the 13 BL465 G6 installed in the enclosure failed to fail over their network connectivity. This is because on 12 of the Blades had their primary connection on port 1 which is connected to the switch which had the SFP failure and the other one just happended to have it’s primary link on port 2 through the switch in bay 2.
*****************
Comment from Anton:
*******************
If an uplink fails, by default the NIC port that lost connectivity will still be connected to the switch and won’t failover even if the uplink path has failed as it’s unaware.
To tell the switch to disable the corresponding downlinks in case of an uplink failure(this is what will tell the teaming software to failover as the port lost its link) you need to configure it– like smartlink for VC, Uplink Failure Detection(UFD) for Gbe2c switch and for the Cisco switch it will be the “Link Sate Tracking” feature.
Some articles and docs that can help with the concept and the config would be:
http://blog.scottlowe.org/2007/06/22/link-state-tracking-in-blade-deployments/
From page 17 onwards : http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_25_see/configuration/guide/swethchl.pdf
******************
Any other help for John?