Extend vlan to another core

[jfkweb]

Here my network

Situation: We need to enable subnet 172.16.67.x (Vlan199) on core 3. We using stack Cat3750 on each core with eigrp for core vlan 32,33,34. There anyway i can do this.

I know that i could probably trunk vlan199 on between core 1 and 3, but it is a good idea to trunk L2 vlan at same level of routing and L3 Vlan.

Thanks

 

[brianinms]

Are your links between Core 1,2,3 layer 3 interfaces or are they trunks?

 

[jfkweb]

L3 routing between cores

 

[brianinms]

Are you using an actual layer 3 interface or an address of an SVI?

 

[jeter]

If your trunking between the switches and all is connected correctly this should work. Vlans can and do extend out to remote switches. Post a config (break it down to actual trunk port and routes).




Spc NVARNG
Tek-TIP Member 19,650

 

[jfkweb]

Do i absolutely need to trunk this vlan between core interface, because we using Eigrp routing and Vlan L3. Server vlan 199 is a L2 vlan.

 

[brianinms]

Post a scrubbed config of your switches.

 

[jfkweb]

CORE 1

hostname SW-CORE01
!

clock timezone EST -5
clock summer-time EDT recurring
switch 1 provision ws-c3750g-24ts
switch 2 provision ws-c3750g-24ts
ip subnet-zero
no ip source-route
ip routing
no ip gratuitous-arps
!
ip tcp synwait-time 5
ip telnet source-interface Loopback0
ip tftp source-interface Loopback0
no ip domain-lookup
ip domain-name **REMOVE**
ip name-server **REMOVE**
ip multicast-routing distributed
vtp domain Core-1
vtp mode transparent
udld enable

!
**REMOVE**
!
spanning-tree mode pvst
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree vlan 100-198,500,901,1020 priority 24576
!
vlan 32
name Core1-Core2_Backbone_Link
!
vlan 33
name Core1-Core3_Backbone_Link
!
vlan 199
name Server_Farm
!
interface Loopback0
description Service Interface
ip address 172.30.16.1 255.255.255.0
ip pim sparse-dense-mode
ip mroute-cache distributed
!
interface Port-channel1
description Core
switchport access vlan 32
switchport mode access
!
interface Port-channel2
description Core
switchport access vlan 33
switchport mode access
!

!
interface GigabitEthernet1/0/25
description Fiber link to Core2 gi2/0/25,gi1/0/25
switchport access vlan 32
switchport mode access
channel-group 1 mode on
!
interface GigabitEthernet1/0/26
description Fiber link to Core3 gi2/0/25,gi1/0/25
switchport access vlan 33
switchport mode access
channel-group 2 mode on
!

!
interface GigabitEthernet2/0/25
description Fiber link to Core3 gi2/0/25,gi1/0/25
switchport access vlan 33
switchport mode access
channel-group 2 mode on
!
interface GigabitEthernet2/0/26
description Fiber link to Core2 gi2/0/25,gi1/0/25
switchport access vlan 32
switchport mode access
channel-group 1 mode on
!
interface Vlan32
description Core1-Core2 Inter-core Point-to-Point VLAN
ip address 172.30.32.1 255.255.255.252
ip pim sparse-dense-mode
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 EIGRP
ip mroute-cache distributed
bridge-group 1
!
interface Vlan33
description Core1-Core3 Inter-core Point-to-Point VLAN
ip address 172.30.33.1 255.255.255.252
ip pim sparse-dense-mode
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 EIGRP
ip mroute-cache distributed
bridge-group 1
!




!
interface Vlan199
description Server VLAN
ip address 172.16.67.1 255.255.255.0
no ip redirects
no ip proxy-arp



!
router eigrp 100
redistribute connected route-map Connected
redistribute static route-map Static
passive-interface default
no passive-interface Vlan32
no passive-interface Vlan33
network 172.30.16.0 0.0.0.255
network 172.30.32.0 0.0.0.3
network 172.30.33.0 0.0.0.3
default-metric 1000000 10 255 1 1500
no auto-summary
!
router rip
version 2
redistribute eigrp 100
passive-interface default
network 172.16.0.0
network 172.30.0.0
network 172.31.0.0
default-metric 3
distribute-list 3 out eigrp 100
no auto-summary
!
ip classless
ip forward-protocol udp bootps
ip forward-protocol udp bootpc
ip route 172.31.128.0 255.255.255.0 172.30.32.2
no ip http server
!
!
access-list 1 permit 172.16.64.0 0.0.0.255
access-list 1 permit 172.16.65.0 0.0.0.255
access-list 1 permit 172.16.66.0 0.0.0.255
access-list 1 permit 172.16.68.0 0.0.0.255
access-list 1 permit 172.16.72.0 0.0.0.255
access-list 1 permit 172.16.76.0 0.0.0.255
access-list 1 permit 172.16.80.0 0.0.0.255
access-list 1 permit 172.16.84.0 0.0.0.255
access-list 1 permit 172.16.88.0 0.0.0.255
access-list 1 permit 172.16.92.0 0.0.0.255
access-list 1 permit 172.16.67.0 0.0.0.255
access-list 1 permit 172.31.64.0 0.0.0.255
access-list 2 permit 0.0.0.0
access-list 3 permit 172.16.0.0 0.0.255.255
access-list 20 permit 172.31.0.0 0.0.255.255
access-list 20 permit 172.30.16.0 0.0.15.255
access-list 20 deny any log
route-map Static permit 10
match ip address 2
!
route-map Connected permit 10
match ip address 1
!

control-plane
!
bridge 1 protocol vlan-bridge
bridge 1 priority 8092




SHOW IP ROUTE CORE 1


Gateway of last resort is 172.16.67.80 to network 0.0.0.0

D EX 114.0.0.0/8 [170/51456] via 172.30.32.2, 4w2d, Vlan32
172.16.0.0/24 is subnetted, 30 subnets
D EX 172.16.160.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.156.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.153.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.154.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.148.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.144.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.136.0 [170/3072] via 172.30.32.2, 1w0d, Vlan32
D EX 172.16.132.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.128.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.129.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.130.0 [170/3072] via 172.30.32.2, 3w1d, Vlan32
D EX 172.16.131.0 [170/3072] via 172.30.32.2, 4w2d, Vlan32
D EX 172.16.224.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.220.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.216.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.212.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.208.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.200.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.196.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
D EX 172.16.192.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
C 172.16.92.0 is directly connected, Vlan109
C 172.16.88.0 is directly connected, Vlan108
C 172.16.84.0 is directly connected, Vlan107
C 172.16.72.0 is directly connected, Vlan104
C 172.16.68.0 is directly connected, Vlan103
C 172.16.69.0 is directly connected, Vlan198
C 172.16.64.0 is directly connected, Vlan100
C 172.16.65.0 is directly connected, Vlan101
C 172.16.66.0 is directly connected, Vlan102
C 172.16.67.0 is directly connected, Vlan199
172.31.0.0/24 is subnetted, 3 subnets
S 172.31.128.0 [1/0] via 172.30.32.2
D EX 172.31.192.0 [170/3072] via 172.30.33.2, 4w2d, Vlan33
C 172.31.64.0 is directly connected, Vlan901
172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
D 172.30.34.0/30 [90/3072] via 172.30.32.2, 4w2d, Vlan32
[90/3072] via 172.30.33.2, 4w2d, Vlan33
C 172.30.32.0/30 is directly connected, Vlan32
C 172.30.33.0/30 is directly connected, Vlan33
C 172.30.16.0/24 is directly connected, Loopback0
D 172.30.20.0/24 [90/130816] via 172.30.32.2, 4w2d, Vlan32
D 172.30.24.0/24 [90/130816] via 172.30.33.2, 4w2d, Vlan33
172.35.0.0/24 is subnetted, 1 subnets
C 172.35.1.0 is directly connected, Vlan800
10.0.0.0/8 is variably subnetted, 3 subnets, 3 masks
S 10.130.0.0/16 [1/0] via 172.16.67.80
C 10.130.96.0/24 is directly connected, Vlan1020
S 10.130.96.0/21 [1/0] via 172.16.67.80
D EX 94.0.0.0/8 [170/51456] via 172.30.32.2, 4w2d, Vlan32
S* 0.0.0.0/0 [1/0] via 172.16.67.80

 

[brianinms]

So you are using access ports as part of a port channel group and the using an SVI. Are all these switches in the same building?

You would have to reconfigure your access points as trunk ports and allow those vlans to pass.

 

[jfkweb]

Yes Core 2 and 3 are the same.

So, there no way we can extend vlan through routing, we absolutely need trunking?

 

[vipergg]

That is correct , if you the same subnet on all switches then you have to trunk between switches . Why do they have to be extended ? Just put them on different subnets and let them route , in this day age the speed difference is minimal.

 

[brianinms]

For core 2 and 3 to be in the same building that is a wacky configuration.

 

[jfkweb]

No... sorry miss understanding. Core 2 and 3 are not in same building... but have same conf.

Why extend ? We got a Multiple Vware machine and we want to put some ESX server on core 2. When you transfert VM we need to keep same ip address, same subnet... it why we want to extend the same subnet.

One solution we find it to add 1 fiber to trunk this vlan only... but server side (fiber) is a point of failure in case of recovery site.