PeraHoman
asked on
Native VLAN question
Native VLAN has to be the same on both ends of a trunk, but if I had multiple trunks on one switch can I have different native VLANs?
R1 R2
| |
SW1 - SW2
| |
|-------SW3
SW1 = Core switch
SW2 = Core switch
SW3 = Access Switch
SW1 - SW2 = portchannel + trunk with native vlan 30
SW2 - SW3 = Trunk + Native VLAN 1 (needs to be 30?)
SW1 - SW3 = Trunk + Native VLAN 1 (needs to be 30?)
Would I need to make the native VLAN the same every where or just ensure they are the same at both ends of each trunk? If there are issues, what are they?
R1 R2
| |
SW1 - SW2
| |
|-------SW3
SW1 = Core switch
SW2 = Core switch
SW3 = Access Switch
SW1 - SW2 = portchannel + trunk with native vlan 30
SW2 - SW3 = Trunk + Native VLAN 1 (needs to be 30?)
SW1 - SW3 = Trunk + Native VLAN 1 (needs to be 30?)
Would I need to make the native VLAN the same every where or just ensure they are the same at both ends of each trunk? If there are issues, what are they?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry I don't' normally correct other's comments but you are giving duff information...
:| natively the ID doesn't matter when connecting two devices together... as its not encapsulated therefor the flag is not set.
try it.
core switch untag vlan # (id with dhcp addresses) on an interface going to another switch,
untag vlan 523 (whatever ID not being used) to the interface going to the core, config vlan 523 with ip dhcp boot. show ip on the switch, vlan 523 will get IP address on the vlan # network..
Of coarse you need native vlans to match in your network if you have 20 client ports you don't want 20 native networks going to each port you would need 20 separate address and router entries...
:| natively the ID doesn't matter when connecting two devices together... as its not encapsulated therefor the flag is not set.
try it.
core switch untag vlan # (id with dhcp addresses) on an interface going to another switch,
untag vlan 523 (whatever ID not being used) to the interface going to the core, config vlan 523 with ip dhcp boot. show ip on the switch, vlan 523 will get IP address on the vlan # network..
Of coarse you need native vlans to match in your network if you have 20 client ports you don't want 20 native networks going to each port you would need 20 separate address and router entries...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
reading more of what you put down you would then loose coms with devices if
SW1 had the DHCP server supplying ranges to Vlan 10....
DHCP server Vlan 10 IP
|
SW1 (vlan10native)--------SW2 (vlan20native)-----SW3(vla
all 3 vlans would get IP address on the vlan 10 range
your example would break that and you would need to encapsulate vlans 20 & 30 to along the links to ensue they got addresses and have an addition al two DHCP scope... why you would have your switches on different IP address ranges is not something I would have on a SOHO network
SW1 had the DHCP server supplying ranges to Vlan 10....
DHCP server Vlan 10 IP
|
SW1 (vlan10native)--------SW2 (vlan20native)-----SW3(vla
all 3 vlans would get IP address on the vlan 10 range
your example would break that and you would need to encapsulate vlans 20 & 30 to along the links to ensue they got addresses and have an addition al two DHCP scope... why you would have your switches on different IP address ranges is not something I would have on a SOHO network
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Example:
Switch1 ------ native VLAN10 ---- Switch2 ------ native VLAN 30 ----- Switch3
|
|
native VLAN 50
|
|
Switch4
So, as long as native VLAN is the same on both sides of link between devices - it is OK.