- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect for a c7000 chassis
BladeSystem - General
1752810
Members
6027
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО08-04-2010 06:55 AM
тАО08-04-2010 06:55 AM
Have a c7000 chassis with a number of blades in and two Virtual Connect 10GB modules/cards to provide networking.
When connecting a blade server to a iSCSI san via two networks. I created two virtual networks, each with an uplink that goes to a separate switch and network. Does having two Virtual Connect modules mean I have to connect 4 network leads, two from one VC module and two from the second module. Really asking how does the failover work between Virtual connect modules.
When connecting a blade server to a iSCSI san via two networks. I created two virtual networks, each with an uplink that goes to a separate switch and network. Does having two Virtual Connect modules mean I have to connect 4 network leads, two from one VC module and two from the second module. Really asking how does the failover work between Virtual connect modules.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2010 07:29 AM
тАО08-04-2010 07:29 AM
Solution
port x7 (crossover) is used as an internal connection for horizontal VC's in a c7000 enclosure. this creates redundant paths for servers in case of a VC failure however if only one port is connected to the VC and this fails...there will be nothing communicating to this uplink losing all communications to it.
for best redundancy you should use (as an example) port x2 from VC1 and VC2 to the data-LAN
and port x3 from VC1 and VC2 to the iSCSI-LAN, be aware that you can LACP team (which is recommended) the uplinks ports even is they belong to diff VC's.
JQ
for best redundancy you should use (as an example) port x2 from VC1 and VC2 to the data-LAN
and port x3 from VC1 and VC2 to the iSCSI-LAN, be aware that you can LACP team (which is recommended) the uplinks ports even is they belong to diff VC's.
JQ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2010 12:19 AM
тАО08-05-2010 12:19 AM
Re: Virtual Connect for a c7000 chassis
Ok thanks so LACP equals trunking of the two uplinks so it can be seen as one network pipe, believe this has to be done as the switch end. Thanks for the quick and informative reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2010 01:13 PM
тАО08-06-2010 01:13 PM
Re: Virtual Connect for a c7000 chassis
yes but LACP is not the same as CISCO trunking (same concept but diff protocols).
VC is configure for dymamic LACP so if ...in your case... both uplink ports are connected to an static/dynamic LACP configured switch it will auto set up the team/trunk.
to confirm that the trunk was created check at the networks tab, both ports should be seen as active (i had to reset the VC after i setted lacp on my Cisco... no idea why VC will not try to change the status in hot)
regards,
VC is configure for dymamic LACP so if ...in your case... both uplink ports are connected to an static/dynamic LACP configured switch it will auto set up the team/trunk.
to confirm that the trunk was created check at the networks tab, both ports should be seen as active (i had to reset the VC after i setted lacp on my Cisco... no idea why VC will not try to change the status in hot)
regards,
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP