- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect & Cisco Virtual Switching System (...
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
Forums
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
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-17-2013 11:54 AM - edited 10-17-2013 11:56 AM
10-17-2013 11:54 AM - edited 10-17-2013 11:56 AM
Virtual Connect & Cisco Virtual Switching System (VSS) Cabling Question
Aniekan was looking to validate a configuration:
***************
Can we setup a Virtual Connect ànd a Cisco VSS with just one uplink port from VC to Cisco VSS switch?
Here’s the scenario. We designed this solution for a customer last year: 2 x c7000, 2 x (VC Flex-10 + VC FC) per enclosure, A/A SUS uplink, upstream Cisco switches (Production SW-x):
The above environment has been running for a year.
Note: The dashed lines do not exist, only recommended.
The customer is now ready to migrate to a single logical switch configuration (i.e. VSS). We are proposing the following cabling changes, with no changes to VC config:
Customer wants to do this in two steps:
- Above configuration with only a single uplink port per VC module (i.e. without the dashed lines)
- At some time later, add the 2nd uplink ports (dashed lines) per VC module
Out of an abundance of caution, I want to confirm that it will work, even if it is not a best practice.
**************
Input from Lionel:
**************
This scenario is called Dual Homed Active/Active (versus Single Homed). It’s in fact a VC best practice and is usually recommended for its higher availability. It works well and is the recommended design when VSS/vPC is available. If you have a maintenance or failure (this happens sometimes when using Cisco J ) with one of the Cisco switch, Smartlink is not triggered, all server downlinks stay up, therefore no NIC failover takes place and no server SNMP alarms are sent.
***************
Any other comments or suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2013 06:37 AM
12-18-2013 06:37 AM
Re: Virtual Connect & Cisco Virtual Switching System (VSS) Cabling Question
How did this work out in the end, have you seen this whitepaper?