BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Shared Uplink Set (SUS) or Tunnel mode advice

chuckk281
Trusted Contributor

Shared Uplink Set (SUS) or Tunnel mode advice

Ed had a customer looking for advice on VLAN or Tunnel mode:

 

****************

 

We have an integrator about to go live with several c7000 chassis’ (ESX servers) in about 2 weeks and we are trying to determine the best route to take on the setup.

 

This is a hosting situation where it will be Desktop as a Service – multi-tenancy.

So they expect as they bring on new customers with their own separate VLAN(s) that they will have to modify the VC side of the house as well as the server profiles to accommodate the new VLAN(s).

 

In testing today, we have come up with a SUS that references the current VLANs and created a test profile with those Network mappings. The discussion then was based around the fact that if a new customer comes on board they will have to modify the SUS to reflect the new network (VLAN or vNet) – not a big deal.

 

The question is… is there a “graceful” way to propagate that new network to all of the existing server profiles without having to go into each profile one by one to manually add it?

If VCM cannot do this is VCEM able to do this?

 

OR>

 

Would it make more sense to use Tunnel Mode (FYI: we’re setting up ESX vDistributed switches and standard vSwitches) and when new VLANs are needed just modify the Trunk (802.1Q) on the 6509 LOMs and on the vSwitches and not worry about individual server profile modification?

 

Any thoughts are appreciated!

 

***************

 

From Chris:

 

**************

 

Tunnel mode would certainly make it easy.  However, there are draw backs:

 

 

·        Use more uplink ports for systems that need different networking requirements

 

·        Can introduce excessive broadcast traffic that will interrupt systems that may not be configured for that L2 network

 

VCEM won’t be able to assist here.  Your best bet is to script this from the CLI.  It’s quite easy to do. 

 

*************

 

And from Steve:

 

******************

 

If you needed to add a net VLAN to a SUS or pair of SUS’, and then add those VLANs to servers NICs, this could be done in one simple script and executed while the servers are running.  AND, using PLINK or some other tools, you could run one script and have it take action across multiple enclosures/servers in one swoop….

 

Example….

Let’s say you have a pair of SUS in Active/Active config….  VLAN-Trunk-1 and VLAN-Trunk-2 and we need to ADD VLANs 200-225 to those trunks, The script would look like this;

 

 

# Create the VLANS (SUS’s already exist), so just adding VLANs to them.

 

# Create Networks VLAN-200-1 through VLAN-225-1 for Shared Uplink Set "VLAN-Trunk-1" and enable SMARTLINK

 

add network-range -quiet UplinkSet=VLAN-Trunk-1 NamePrefix=VLAN-NameSuffix=-1 VLANIds=200-225 State=enabled PrefSpeedType=auto SmartLink=enabled

 

# Create Networks VLAN-200-2 through VLAN-225-2 for Shared Uplink Set "VLAN-Trunk-2" and enable SMARTLINK

 

add network-range -quiet UplinkSet=VLAN-Trunk-2 NamePrefix=VLAN-NameSuffix=-2 VLANIds=200-225 State=enabled PrefSpeedType=auto SmartLink=enabled

 

let’s assume the Profiles are called ESX-1, ESX-2 etc… and they have 6 NICs configured and we want to ADD these VLANs to NICs 5 and 6.

 

#Add them to the profiles

#ESX-1

 

add server-port-map-range ESX-1:5 UplinkSet=VLAN-Trunk-1 VLanIds=200-225

 

add server-port-map-range ESX-1:6 UplinkSet=VLAN-Trunk-2 VLanIds=200-225

#ESX-2

 

add server-port-map-range ESX-2:5 UplinkSet=VLAN-Trunk-1 VLanIds=200-225

 

add server-port-map-range ESX-2:6 UplinkSet=VLAN-Trunk-2 VLanIds=200-225

#ESX-3

 

add server-port-map-range ESX-3:5 UplinkSet=VLAN-Trunk-1 VLanIds=200-225

 

add server-port-map-range ESX-3:6 UplinkSet=VLAN-Trunk-2 VLanIds=200-225 etc…..

 

Now, if they are random VLANs, it would look like this….

or even VLANs that are not consecutive, such as 20,24,47,322 (you get the picture), then add them to a set of servers….

 

 

# Create the VLANS

 

# Create Networks VLAN-20,24,47,322 -1 for Shared Uplink Set "VLAN-Trunk-1" and enable SMARTLINK

 

add network-range -quiet UplinkSet=VLAN-Trunk-1 NamePrefix=VLAN- NameSuffix=-1 VLANIds=20,24,47,322 State=enabled PrefSpeedType=auto SmartLink=enabled

 

# Create Networks VLAN-200-2 through VLAN-225-2 for Shared Uplink Set "VLAN-Trunk-2" and enable SMARTLINK

 

add network-range -quiet UplinkSet=VLAN-Trunk-2 NamePrefix=VLAN- NameSuffix=-2 VLANIds=20,24,47,322 State=enabled PrefSpeedType=auto SmartLink=enabled

 

#Add them to the profiles

#ESX-1

 

add server-port-map-range ESX-1:5 UplinkSet=VLAN-Trunk-1 VLanIds=20,24,47,322

 

add server-port-map-range ESX-1:6 UplinkSet=VLAN-Trunk-2 VLanIds=20,24,47,322

#ESX-2

 

add server-port-map-range ESX-2:5 UplinkSet=VLAN-Trunk-1 VLanIds=20,24,47,322

 

add server-port-map-range ESX-2:6 UplinkSet=VLAN-Trunk-2 VLanIds=20,24,47,322

#ESX-3

 

add server-port-map-range ESX-3:5 UplinkSet=VLAN-Trunk-1 VLanIds=20,24,47,322

 

add server-port-map-range ESX-3:6 UplinkSet=VLAN-Trunk-2 VLanIds=20,24,47,322

 

**************

 

Reply from Dan to Steve:

 

**************

 

I’m less worried about the scripting and more worried about the VLAN limits.  What happens when they get up to 150+ clients (and thus VLANs) and start running into the 162 barrier?

 

**************

 

And back from Steve:

 

*************

 

Two options....

 

1- create a vNet tunnel, which will require addition uplinks and attach it to the vswitch, trunk vlans to here.

 

2 - install another pair of vc modules and a two port nic... Add more NICs to the servers, config an additional vswitch and go...

 

Option 1 would likey be the better solution.

 

*************

 

Comments or suggestions? Kind of a common scenario for service providers or hosting.