Dear Team,
As we are working on many customer environment, I've seen few customers are configuring transport vlan and few are mentioning as 0 or few are keeping blank.
if we mention transport VLAN as 100 then do I need to mention the same VLAN on PG as well?
if we mention 0 then do I need to mention VLAN 0 on PG as well?
if transport VLAN is blank then do I need to mention VLAN on PG?
Could someone please let me know the right place where to define the VLAN for the overlay network...
thank you in advance
are
Hi
if we mention transport VLAN as 100 then do I need to mention the same VLAN on PG as well --> In this case VLAN PORTGROUP on VDS must be configured as trunk. So you Specify VLAN Number in Uplink Profile, to ensure tagging is extended till your physical switchport.
if we mention 0 then do I need to mention VLAN 0 on PG as well? : In this case VLAN PORTGROUP on VDS must be configured as Access. This will use VLAN Number of PORTGROUP.
if transport VLAN is blank then do I need to mention VLAN on PG? - Same Above, VDS Portgroup VLAN number will be used.
HTH
Sandy
Hi
if we mention transport VLAN as 100 then do I need to mention the same VLAN on PG as well --> In this case VLAN PORTGROUP on VDS must be configured as trunk. So you Specify VLAN Number in Uplink Profile, to ensure tagging is extended till your physical switchport.
if we mention 0 then do I need to mention VLAN 0 on PG as well? : In this case VLAN PORTGROUP on VDS must be configured as Access. This will use VLAN Number of PORTGROUP.
if transport VLAN is blank then do I need to mention VLAN on PG? - Same Above, VDS Portgroup VLAN number will be used.
HTH
Sandy
In this case VLAN PORTGROUP on VDS must be configured as trunk. So you Specify VLAN Number in Uplink Profile, to ensure tagging is extended till your physical switchport.
Where is this configured? I have the VLAN tagged in the Uplink Profile, but vmk10 (with the TEP IP address) is not showing a VLAN
In case you configured trunk PGs on vDS, then (I'm supposing we are speaking here about edge networking):
- overlay VLAN 100 will be entered inside uplink profile like you mentioned - it will be used for overlay purposes
- inside same uplink profile create additional named teaming (failover order - per uplink1 and uplink2 that you use, leave default as load balanced srcid for overlay load balancing purposes) - best option different VLANs for edge outside uplink connectivity using some routing to ToRs
- create VLAN segments (ie two if using different VLANs) inside NSX which will be used by T0 for uplink connectivity with ToR switches, with respective interfaces on T0
It's short description of steps covering typical edge networking for overlay/uplink connectivity. There are more options of course but this one is absolutely supported.
HTH,
Dragan