RIP updates not getting from 1811 to 3750x

mike-elliott · ‎01-09-2013

I am trying to get a 1811 to update routes on a 3750x. My static routes are being redistributed to the switch fine, however my connected networks are not

My router has Vlan with several subnets attached.

interface Vlan1

description $ETH-SW-LAUNCH$$INTF-INFO-FE 2$$ES_LAN$$FW_INSIDE$

ip address xxx.xx.xx7.185 255.255.255.0 secondary

ip address 172.90.0.185 255.255.255.0 secondary

ip address 172.99.0.1 255.255.255.0 secondary

ip address 10.170.10.254 255.255.255.0 secondary

ip address 10.173.10.254 255.255.255.0 secondary

ip address 10.162.10.254 255.255.255.0 secondary

ip address 172.21.10.1 255.255.252.0 secondary

ip address 172.21.40.1 255.255.255.0 secondary

ip address 172.30.110.185 255.255.255.0 secondary

ip address 10.4.158.1 255.255.255.0 secondary

ip address 10.109.111.1 255.255.255.0 secondary

ip address 192.168.100.1 255.255.255.0 secondary

ip address 192.168.22.129 255.255.255.192 secondary

ip address 10.19.250.185 255.255.255.0 secondary

ip address 10.236.80.254 255.255.255.0 secondary

ip address 10.8.21.1 255.255.255.0 secondary

ip address 10.10.23.185 255.255.255.0 secondary

ip address 10.10.50.185 255.255.252.0 secondary

ip address 192.168.219.2 255.255.255.0 secondary

ip address xxx.xx.xx6.185 255.255.255.0

ip accounting output-packets

ip nbar protocol-discovery

ip flow ingress

ip flow egress

ip nat inside

no ip virtual-reassembly

ip route-cache flow

ip tcp adjust-mss 1452

ip policy route-map vterm

auto discovery qos trust

end

router rip

version 2

no validate-update-source

redistribute static

network 10.0.0.0

network 192.168.219.0

network xxx.xx.xx6.0

network xxx.xx.xx7.0

neighbor 10.10.44.185

neighbor 192.168.219.1

no auto-summary

My Switch has the following config

interface Vlan1

ip address 10.10.80.185 255.255.255.0 secondary

ip address 192.168.219.1 255.255.255.0 secondary

ip address 10.10.44.185 255.255.252.0

ip rip send version 2

end

router rip

version 2

no validate-update-source

passive-interface FastEthernet0

network 10.0.0.0

network 192.168.219.0

neighbor 192.168.219.2

distribute-list 12 in FastEthernet0

no auto-summary

A host on the xxx.xx.xx6.0 network cannot ping a host on the 10.10.44.0 network. All ports on the switch and the router are in vlan1

NormMuelleman · ‎01-09-2013

Can you post the ip route output?

Where are the routes not propogating to? Is it on the 3750 or the 1811?

I see one thing that caught my eye...in your switch, you have

router rip

version 2

no validate-update-source

passive-interface FastEthernet0

network 10.0.0.0

network 192.168.219.0

neighbor 192.168.219.2

distribute-list 12 in FastEthernet0

no auto-summary

My thought is the command "passive-interface FastEthernet0". It's not going to send multicast updates OUT the Fa0 interface. But I am just doing a quick assessment (heck, I just took and passed my ROUTE, so my head is mush lol). But I think you said it's not working from the router to the switch.

Has this worked before? Is this a new config? Or was something done recently?

mike-elliott · ‎01-09-2013

This is something I've been working on recently. We want to move our perimeter routing back to the switch. We have two adjacent class C (not private) and the rest are private networks. These are listed as xxx.xx.xx

My ISP's network is yyy.yyy.yyy.x. They have provided me a class C range. I use NAT on the 1811.

I want to bring the xxx.xxx.xx networks off the router and have the switches perform the routing. I don't want to do it all at once so I was hoping to get RIP to take care of the networks as I bring them over one by one.

I created the distribute list on FA0 because I want one of the Gig interfaces to be the interface to the router. FA0 is a management interface on the 10.10.23.x network.

On the 1811, i can see that the 10.10.44.x network has been distributed from the 3750. I underlined it. Any routes that came from RIP or Static, on the 1811 are being seen on the 3750x but none of the connected networks.... aahhhhh... I just realized what I need to do. I have redistribute static setup on the 1811, but not redistribute connected. Let me try this

1811 sh ip route

1.0.0.0/24 is subnetted, 1 subnets

C 1.1.1.0 is directly connected, Loopback0

69.0.0.0/24 is subnetted, 1 subnets

S 69.225.150.0 [1/0] via xxx.xx.xx6.165

172.90.0.0/24 is subnetted, 1 subnets

C 172.90.0.0 is directly connected, Vlan1

172.99.0.0/24 is subnetted, 1 subnets

C 172.99.0.0 is directly connected, Vlan1

172.21.0.0/16 is variably subnetted, 2 subnets, 2 masks

C 172.21.40.0/24 is directly connected, Vlan1

C 172.21.8.0/22 is directly connected, Vlan1

172.30.0.0/24 is subnetted, 1 subnets

C 172.30.110.0 is directly connected, Vlan1

yyy.yyy.0.0/24 is subnetted, 1 subnets

C yyy.yyy.yy.0 is directly connected, FastEthernet1

C 192.168.219.0/24 is directly connected, Vlan1

S 192.168.232.0/24 [1/0] via xxx.xx.xx7.33

10.0.0.0/8 is variably subnetted, 16 subnets, 2 masks

C 10.109.111.0/24 is directly connected, Vlan1

S 10.2.3.0/24 [1/0] via xxx.xx.xx6.46

S 10.2.4.0/24 [1/0] via xxx.xx.xx6.165

C 10.10.20.0/24 is directly connected, Tunnel0

C 10.10.23.0/24 is directly connected, Vlan1

C 10.8.21.0/24 is directly connected, Vlan1

R 10.10.24.0/24 [120/1] via 10.10.44.185, 00:00:24

S 10.10.44.0/22 [1/0] via 192.168.219.1

C 10.10.48.0/22 is directly connected, Vlan1

S 10.164.223.0/24 [1/0] via xxx.xx.xx6.2

C 10.4.158.0/24 is directly connected, Vlan1

C 10.162.10.0/24 is directly connected, Vlan1

C 10.170.10.0/24 is directly connected, Vlan1

C 10.173.10.0/24 is directly connected, Vlan1

C 10.236.80.0/24 is directly connected, Vlan1

C 10.19.250.0/24 is directly connected, Vlan1

192.168.22.0/26 is subnetted, 1 subnets

C 192.168.22.128 is directly connected, Vlan1

R 192.168.1.0/24 [120/1] via 10.10.20.2, 00:00:12, Tunnel0

C xxx.xx.xx7.0/24 is directly connected, Vlan1

C 192.168.100.0/24 is directly connected, Vlan1

216.35.130.0/32 is subnetted, 1 subnets

S 216.35.130.98 [1/0] via xxx.xx.xx6.165

R 192.168.3.0/24 [120/1] via 10.10.20.3, 00:00:01, Tunnel0

C xxx.xx.xx6.0/24 is directly connected, Vlan1

S* 0.0.0.0/0 [1/0] via yyy.yyy.yy.1

3750x sh ip route

Gateway of last resort is 10.10.23.185 to network 0.0.0.0

C 192.168.219.0/24 is directly connected, Vlan1

10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

R 10.10.20.0/24 [120/1] via xxx.xx.xx7.185, 00:00:11

[120/1] via xxx.xx.xx6.185, 00:00:11

[120/1] via 2.3.0.1, 00:00:11

C 10.10.23.0/24 is directly connected, FastEthernet0

C 10.10.24.0/24 is directly connected, Vlan2

C 10.10.44.0/22 is directly connected, Vlan1

C 10.10.80.0/24 is directly connected, Vlan1

R 192.168.1.0/24 [120/2] via xxx.xx.xx7.185, 00:00:11

[120/2] via xxx.xx.xx6.185, 00:00:11

[120/2] via 2.3.0.1, 00:00:11

R 192.168.3.0/24 [120/2] via xxx.xx.xx7.185, 00:00:11

[120/2] via xxx.xx.xx6.185, 00:00:11

[120/2] via 2.3.0.1, 00:00:11

S* 0.0.0.0/0 [1/0] via 10.10.23.185

mike-elliott · ‎01-09-2013

Ok when I redistrubted the connected routes, it caused some other weirdness. I will take another boo tomorrow