- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Virtual connect and port mapping
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
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
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
тАО04-23-2008 12:24 AM
тАО04-23-2008 12:24 AM
Virtual connect and port mapping
NIC1 mapped to port 2 on Virtual connect Bay 1 and NIC2 mapped to port 2 on Virtual connect Bay 2.
Both Virtual connect bays connected to Nortel switches with 8 * 1 Gb connections. In Virtual connect manager we defined Ethernet network "VC-Bay1" (include all 8 connections, LACP used) for Virtual connect in Bay 1 and Ethernet network "VC-Bay2" for Virtual connect in Bay 2.
Now we define profile for BL460 in bay 2 in following matter:
NIC1 -> "VC-Bay1"
NIC2 -> "VC-Bay1"
In that way we connect both NIC to Virtual connect Bay 1.
I assume that in this scenario NIC2 will not connected to network,
but NIC2 is connected and work - probably because internal stacking link between two Virtual connects.
So question is - is it normal situation to connect both NIC (or 4 NIC in BL480) to same Virtual connect bay ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2008 09:46 AM
тАО04-23-2008 09:46 AM
Re: Virtual connect and port mapping
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2008 04:43 AM
тАО04-24-2008 04:43 AM
Re: Virtual connect and port mapping
I think you have set up what is called an Active/Active VC configuration. I.E. you have 2 VC Networks that connect to the external infrastructure with the same VLAN or VLANs.
In this situation, we would connect:
NIC1 -> "VC-Bay1"
NIC2 -> "VC-Bay2"
and team the 2 NICs together. This gives full redundancy.
In your situation, yes NIC 2 can communicate out of the VC-Bay1 network because of the VC stacking links.
But you are not providing redundancy. 1) you are not using the Bay 2 uplinks at all and 2) if the Bay 1 VC module fails the server will be down.
hope this helps.
Also, if you are using an Active/Active configuration and doing NIC teaming, take a look at the SmartLink feature of VC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2008 06:59 AM
тАО04-24-2008 06:59 AM
Re: Virtual connect and port mapping
We don't use teaming for several BL460 and BL480 because they run Microsoft Virtual server 2005 and we connect one NIC only to Host and other NIC's (one in BL460 and three in BL480) only to Guests.
We use teaming for all other servers.
>>I think you have set up what is called an Active/Active VC configuration
Yes, you are right. Same VLAN used and all 8 ports of each VC aggregated.
Just until now I thought VC can work only in Active/Passive. Is any document about Active/Active configuration exist ?
>>In your situation, yes NIC 2 can communicate out of the VC-Bay1 network because of the VC stacking links.
I assume that VC stacking link cannot be disabled ?
>>Also, if you are using an Active/Active configuration and doing NIC teaming, take a look at the SmartLink feature of VC.
Thanks, we will set SmartLink to servers with NIC teaming.
HEM, your answers on this forum are extremely useful !!! Many thanks !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2008 09:38 AM
тАО04-24-2008 09:38 AM
Re: Virtual connect and port mapping
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf
You can find me from Twitter @JKytsi