redistribution_frenzy

It is late so I am going to crunch in a quick lab to get everything reconfigured so it is pinging and happy, so I can get into EIGRP, and forget troubleshooting the NBMA was such a painfully simple answer. Thinking doing these labs in the middle of the night / morning is probably not too productive, but it did help me learn valuable lessons, namely DO NOT GLOSS OVER THE SIMPLE DETAILS EVER!

Even with the more complex show commands, and the debugs with the troubleshooting output in bulk, all it took was “show run” to have the problem glaring in my face.

Anyways, the topology is back on, a new (same looking) topology coming soon! I put RIP back on there, with Area 51 on R4’s loopback connecting the virtual-link to R3 (making Area 34 the transit area), and here are the results when I got on a spoke first (!!!) and pinged the other spoke to begin with (!!!!!!!!) to make sure layers 1 and 2 where not an issue:

R2#sh ip route
(Route codes redacted)

Gateway of last resort is not set

     1.0.0.0/32 is subnetted, 1 subnets
R       1.1.1.1 [120/1] via 172.12.123.1, 00:00:16, Serial0/0
     2.0.0.0/32 is subnetted, 1 subnets
C       2.2.2.2 is directly connected, Loopback2
     3.0.0.0/32 is subnetted, 1 subnets
R       3.3.3.3 [120/2] via 172.12.123.3, 00:00:16, Serial0/0
     4.0.0.0/32 is subnetted, 1 subnets
R       4.4.4.4 [120/3] via 172.12.123.3, 00:00:13, Serial0/0
     172.12.0.0/16 is variably subnetted, 5 subnets, 2 masks
R       172.12.34.0/24 [120/2] via 172.12.123.3, 00:00:17, Serial0/0
R       172.12.33.3/32 [120/2] via 172.12.123.3, 00:00:17, Serial0/0
R       172.12.44.4/32 [120/3] via 172.12.123.3, 00:00:17, Serial0/0
R       172.12.15.0/24 [120/1] via 172.12.123.1, 00:00:17, Serial0/0
C       172.12.123.0/24 is directly connected, Serial0/0
R2#ping 3.3.3.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
R2#ping 4.4.4.4

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
…..

Again just to point out the difference in RIP metric in hop count / metric, preceded by its Administrative Distance 120. So as can be seen OSPF was Redistributed into the RIP domain by the routes we’re seeing, and I already know R4 has no RIP routes being injected into it’s domain. As like yesterday before we had the epic NBMA fail, I am going to try assigning a default route once more, and see if R2 can get a response:

R4(config)#ip route 0.0.0.0 0.0.0.0 172.12.34.3
R4(config)#^Z
*Jan 12 03:42:39.043: %SYS-5-CONFIG_I: Configured from console by console
R4#
ASR#2
[Resuming connection 2 to r2 … ]

R2#ping 4.4.4.4

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 128/129/132 ms
R2#

And there it is, I love when things work, and now that everything is working I shall see if I can break it by Redistributing all protocols into each other and dropping the default route off R4. Here is all it takes:

R3(config)#router ospf 1
R3(config-router)#redistribute rip subnets metric-type 1 <- NO DEFAULT METRIC
R3(config-router)#
ASR#3
[Resuming connection 1 to r1 … ]

R1(config)#router eigrp 100
R3(config-router)#redistribute rip metric 1544 10 1 255 1500

And that should be it, RIP should be routing into OSPF and EIGRP. So as per my new tradition, I will ping from R4 first to my spoke R2 to make sure it’s still alive, and then to 5.5.5.5 – The ultimate test:

R4#ping 2.2.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 128/128/132 ms
R4#ping 5.5.5.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 5.5.5.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 64/64/68 ms
R4#

Along with that I found a notable behavior from R4’s E1 routes that should not have a default metric of 20:

R4#sh ip route
(Route codes redacted)

Gateway of last resort is not set

      1.0.0.0/32 is subnetted, 1 subnets
O E1     1.1.1.1 [110/21] via 172.12.34.3, 00:01:28, FastEthernet0/1
      2.0.0.0/32 is subnetted, 1 subnets
O E1     2.2.2.2 [110/21] via 172.12.34.3, 00:01:28, FastEthernet0/1
      3.0.0.0/32 is subnetted, 1 subnets
O E1     3.3.3.3 [110/21] via 172.12.34.3, 00:01:28, FastEthernet0/1
      4.0.0.0/32 is subnetted, 1 subnets
C        4.4.4.4 is directly connected, Loopback4
      5.0.0.0/32 is subnetted, 1 subnets
O E1     5.5.5.5 [110/21] via 172.12.34.3, 00:01:28, FastEthernet0/1
      172.12.0.0/16 is variably subnetted, 7 subnets, 2 masks
O E1     172.12.15.0/24 [110/21] via 172.12.34.3, 00:01:28, FastEthernet0/1
O        172.12.33.3/32 [110/2] via 172.12.34.3, 00:49:37, FastEthernet0/1
C        172.12.34.0/24 is directly connected, FastEthernet0/1
L        172.12.34.4/32 is directly connected, FastEthernet0/1
C        172.12.44.0/24 is directly connected, Loopback44
L        172.12.44.4/32 is directly connected, Loopback44
O E1     172.12.123.0/24 [110/21] via 172.12.34.3, 00:01:28, FastEthernet0/1
R4#

***All of my E1 routes, with a distance of 21, the same as if you turn N2 routes into N1 routes in an NSSA OSPF Area, when the next connected router is an ASBR***

Now that I know this lab is fully configured and capable of routing across multiple protocols, I will start back on studying matching ACL’s and Route-Maps.

I aimed for Jan 1st to be all caught up, but I will take Jan 11th, next up I will be adding some routes (and adding an updated topology to these posts) to work with some new subjects!