- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Virtual Connect (VC) communication to another ...
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
05-04-2015 11:51 AM - edited 05-04-2015 11:53 AM
05-04-2015 11:51 AM - edited 05-04-2015 11:53 AM
Virtual Connect (VC) communication to another enclosure
A question from Sanyi:
***********
Can I connect two VC FlexFabric module in different C7000 chassis directly? I don’t want to put both c7000 in the same domain I just want to connect them without a switch in order to both C7000 could communicate directly with each other.
***********
Reply from Robert:
************
You can use this knowledgebase article. It should help:
http://h41302.www4.hp.com/km/saw/view.do?docId=mmr_kc-0110609&hsid=64648787&sz=9827
***********
From Dan:
***********
Yes but the VLAN/Network(s) you plumb can only be access by blades in both chassis.
You cannot bounce that network out another uplink and up to the customer’s core due to the way VC handles networks.
So vMotion, SQL Heartbeat, Oracle RAC, etc are all fine as long as all the members are blades.
When you setup the link between the 2 sides, you need to change the mode from Auto to Manual/Failover or whatever it says.
This way you can control which link they use to talk and which link is your backup.
************
Other comments?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2016 05:59 AM
02-09-2016 05:59 AM
Re: Virtual Connect (VC) communication to another enclosure
The link is broken. It is possible to recover it or redirecting it.
http://h41302.www4.hp.com/km/saw/view.do?docId=mmr_kc-0110609&hsid=64648787&sz=9827
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2016 07:20 PM - edited 02-13-2016 07:21 PM
02-13-2016 07:20 PM - edited 02-13-2016 07:21 PM
Re: Virtual Connect (VC) communication to another enclosure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2016 12:00 AM
02-17-2016 12:00 AM
Re: Virtual Connect (VC) communication to another enclosure
Thanks Dennis.
I found this other link too:
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0110609