cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1448
Views
5
Helpful
3
Replies
parakiteiz
Beginner

VLAN's over a routed interface, is it possible?

I have a 3560 that is hooked to a 6509. The following SVI's live on the 3560:

 

192.168.180.1 (VLAN 180), 192.168.181.1(VLAN 181),  192.168.182.1 (VLAN 182) , 192.168.183.1 (VLAN 183) , 192.168.184.1 (VLAN 183),

 

I have the following routed interfaces between the 6509 (192.168.0.17/32, and the 3506 (192.168.0.18/32).  Right now I have using a gateway of last resort to route traffic off the switch and a static route to send traffic for those SVI's.

I have a few VLAN's that I use for vSpere and ESXI's traffic (239(vMotion), 243(Fault Tolerance), (250, iSCSIStorage), 254, ESXi), 255 Network management).

Is there any way to send these VLAN's over the routed interface?

I have a few ESXi hosts that need 254, 239 and 243 for vSphere functions.

 

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Jon Marshall
VIP Community Legend

Short answer is with the equipment you have no you can't.

What you can do is -

1) create a new vlan purely for the link between the switches and create an SVI for that vlan on each switch.

The IP addresses for the SVIs will be the IPs you currently have on the routed ports.

2) make the link a trunk link and allow the new vlan and an vlans you want to extend eg. between switches.

The important thing here is to only allow on the trunk link the new vlan and the vlans you are extending.

3) the vlans you are not extending ie. vlans 180, 181 etc are not allowed on the trunk link and so will still be routed between switches across the new vlan because the SVIs for that vlan have the IPs you originally had allocated to the L3 ports.

Jon

View solution in original post

3 REPLIES 3
Jon Marshall
VIP Community Legend

Short answer is with the equipment you have no you can't.

What you can do is -

1) create a new vlan purely for the link between the switches and create an SVI for that vlan on each switch.

The IP addresses for the SVIs will be the IPs you currently have on the routed ports.

2) make the link a trunk link and allow the new vlan and an vlans you want to extend eg. between switches.

The important thing here is to only allow on the trunk link the new vlan and the vlans you are extending.

3) the vlans you are not extending ie. vlans 180, 181 etc are not allowed on the trunk link and so will still be routed between switches across the new vlan because the SVIs for that vlan have the IPs you originally had allocated to the L3 ports.

Jon

parakiteiz
Beginner

so the changes should look like this:

vlan 300

name TESTSW01toCORESW01

 

TESTSW01

int vlan 300

ip add 19.168.0.17 255.255.255.252

 

int GIG0/25

switchport trunk encapsulation dot1q

switchport mode trunk

switchport trunk vlan allowed vlan 180,181,182,183,184, 254,255,239,243,250

 

CORESW01

int vlan 300

ip add 19.168.0.18 255.255.255.252

 

int GIG1/10

switchport trunk encapsulation dot1q

switchport mode trunk

switchport trunk vlan allowed vlan 180,181,182,183,184, 254,255,239,243,250

 

 

 

Not quite.

You only allow the vlans you want to extend so not vlans 180 - 184 because , if I have understood correctly, you aren't extending these, you are still routing these between the switches.

You also need to allow vlan 300.

Jon