BladeSystem - General
1826524 Members
4277 Online
109695 Solutions
New Discussion

Re: Virtual connect, mapped vlans and Private Networks, Windows and ESX on same C7000 chassis?

 
BeltwayBenny
Advisor

Virtual connect, mapped vlans and Private Networks, Windows and ESX on same C7000 chassis?

Hello,

 

[edited to fix Lom:Xx notations]

 

I'm looking at the docs / blogs for virtualconnect and flex-nics.  Trying to figure out how to support the following using only (2) VC modules, (1) 10Gb connection per module (2 total), uplinked to (2) Nexus 5K connected to each other with a VPC so they look like one logical switch.

 

Windows and ESX servers in the same C7000 chassis:

- Windows server flex-Nic Lom:1a & Lom:2a on VLAN 100:  This would be a VC mapped vlan, no tagging to host

- ESX server flex-NIC Lom:1a & Lom:1b on VLAN 200: This would be a VC mapped vlan, no tagging to host

- ESX server flex-NIC Lom:2a & Lom:2b on VLAN 300,301,302, etc: This would be a VC mapped vlan using the 'multiple networks' section so that I can pass tagged packets into these flex-nics.

 

The stuff above looks very similar to cookbook scenario :

Scenario 2:3 - Flex-10 - VLAN Tagging (802.1Q)with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - ESX 4

 

I think the above will work, I believe I have limitation of 28 mapped vlans per downstream flex-nic?

 

The one thing I'm having issues with is figuring out how to do Private VLANs/Private Networks.  I understand that I can set a private network and the VC will pass those frames up to the uplinks and to the Nexus 5Ks.  On the Nexus, I would like to set vlan 500 as primary/promiscuous and 501 as isolated.  So on the 5K <> VC 10Gb trunks I would allow for vlans 500,501 and then on the VC I'd define a Private Network on vlan ... 501, and assign the server flex-nic (Lom:3a, Lom:3b) mapped vlan) to VLAN 501.  The server would send untagged frames out, the VC taggs them with v501, they are sent out the uplinks, the Nexus would then apply the PVLAN mappings and treat that frame as isolated (v501).

 

Does this sound right?  Are there any technical limitations that prevent me from setting all this up with only  (2) 10Gb uplinks? 

 

Thanks,

 

Ben

2 REPLIES 2
chuckk281
Trusted Contributor

Re: Virtual connect, mapped vlans and Private Networks, Windows and ESX on same C7000 chassis?

Ben:

 

I will ask for someone to confirm. Just look at your FlexNIC number:

NIC1: LOM1-a, LOM1-b, LOM1-c, LOM1-d

NIC2: LOM2-a, LOM2-b, LOM2-c, LOM2-d

 

I see that you are referring to a LOM3 and I don't know where that numbering is coming from.

Stevem
Frequent Advisor

Re: Virtual connect, mapped vlans and Private Networks, Windows and ESX on same C7000 chassis?

Yes, the config you are suggesting for Windows and ESX hosts is fine.  Follow the Cookbook scenario and you should be fine.

 

VC's Private Networks feature is not compatible with CISCO's PVLANs, however, I think what you are asking may work.  I'll look into this and advise.

 

Steve....