So after spinning my tires thinking of how to make it work on my very awesome looking Topology from the previous post, I just need to know this works in general for my own sanity.
As can be seen, the above Topology is as easy as it gets, I am humbly stepping back, and admitting with the new / advanced material I am going to need to learn to flap before I can fly.
So this brought me back to some of the basics of configuring, like find the right end of the cable (DCE vs DTE) and configuring clock rates, and ran into a cable related issue on my physical equipment that hadn’t crossed my mind as I thought I had them labeled properly.
I could get any serial interfaces for the life of me, and when removing the cables from the Frame Switch, I could have sworn they were all plugged into the top slot of the WIC card which was NOT the case. So after some head scratching, I found it out the good old fashioned CCNA way:
R3#show controllers serial 0/2 <- Very good command to check if cable is connected, and if it is a DTE or a DCE end of the cable as you may need to configure clock rate
Interface Serial0/2
Hardware is PowerQUICC MPC860
No serial cable attached <- So much for that top slot being my connecting interface
idb at 0x855A8AD4, driver data structure at 0x855B0240
SCC Registers:
General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8
Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x00
(Output removed)
So after I was able to remove my palm from my face, I switched both cables, and with all the configs already in place as far as protocols on each side and the serial interfaces now up we are ready to get this Distribute-List command to work! Also to note, I put both DCE’s on R1 to keep the clock rates in one spot, clock rate set for both.
So I am going to redistribute both protocols into each other so everything should be reachable, put their route tables on here to confirm, but I see R1 is not seeing any OSPF or EIGRP routes.
After I felt certain that I had the cables finally correct, and reloaded to see the same behavior, I swapped the cables on R1 and look what we finally have here:
R1#
R1#
*Mar 1 14:28:56.871: %LINK-3-UPDOWN: Interface Serial0/1, changed state to down
*Mar 1 14:28:57.873: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1, changed state to down
R1#
*Mar 1 14:29:05.037: %LINK-3-UPDOWN: Interface Serial0/0, changed state to down
*Mar 1 14:29:06.038: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to down
R1#
*Mar 1 14:29:10.850: %LINK-3-UPDOWN: Interface Serial0/1, changed state to up
*Mar 1 14:29:11.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1, changed state to up
R1#
*Mar 1 14:29:12.834: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 172.12.13.3 (Serial0/1) is up: new adjacency
R1#
*Mar 1 14:29:31.392: %LINK-3-UPDOWN: Interface Serial0/0, changed state to up
*Mar 1 14:29:32.394: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to up
R1#
*Mar 1 14:29:41.505: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Serial0/0 from LOADING to FULL, Loading Done
R1#
It had been so long since I’ve touched the NBMA network on the physical lab, I’ve apparently forgotten how to cable things correctly, and got too dependent on my Octal cable from my 2509 Access-Server with numbers on them to ID the logical layout by the physical cabling of the devices.
NOW lets look at these route tables and see something more than their loopbacks and directly connected routes:
R3#show ip route
Gateway of last resort is not set
2.0.0.0/32 is subnetted, 1 subnets
D EX 2.2.2.2 [170/2172416] via 172.12.13.1, 00:07:01, Serial0/2
33.0.0.0/24 is subnetted, 1 subnets
C 33.33.33.0 is directly connected, Loopback33
3.0.0.0/24 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Loopback3
172.12.0.0/24 is subnetted, 2 subnets
D EX 172.12.12.0 [170/2172416] via 172.12.13.1, 00:07:17, Serial0/2
C 172.12.13.0 is directly connected, Serial0/2
R3#
ASR#1
[Resuming connection 1 to r1 … ]
R1#sh ip route
Gateway of last resort is not set
2.0.0.0/32 is subnetted, 1 subnets
O IA 2.2.2.2 [110/65] via 172.12.12.2, 00:07:21, Serial0/0
33.0.0.0/24 is subnetted, 1 subnets
D 33.33.33.0 [90/2297856] via 172.12.13.3, 00:07:55, Serial0/1
3.0.0.0/24 is subnetted, 1 subnets
D 3.3.3.0 [90/2297856] via 172.12.13.3, 00:07:55, Serial0/1
172.12.0.0/24 is subnetted, 2 subnets
C 172.12.12.0 is directly connected, Serial0/0
C 172.12.13.0 is directly connected, Serial0/1
R1#
ASR#2
[Resuming connection 2 to r2 … ]
R2#sh ip route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback2
33.0.0.0/24 is subnetted, 1 subnets
O E2 33.33.33.0 [110/1] via 172.12.12.1, 00:07:28, Serial0/0
3.0.0.0/24 is subnetted, 1 subnets <- This route is about to get filtered
O E2 3.3.3.0 [110/1] via 172.12.12.1, 00:07:28, Serial0/0
172.12.0.0/24 is subnetted, 2 subnets
C 172.12.12.0 is directly connected, Serial0/0
O E2 172.12.13.0 [110/1] via 172.12.12.1, 00:07:28, Serial0/0
R2#u all
All possible debugging has been turned off
R2#
Firstly, I’ve made the unilateral decision to remove Route Code tables all together from sh ip route output as I don’t feel like typing the Route Codes Redacted thing over and over.
Second(ly), I have gone in a topologically (is that a word?) left to right way, so that when looking at the Topology above you see R3 is the EIGRP router with OSPF routes, R1 has both, and so on for clarity sake. Redistribution into both realms has been configured, each router can see every interface, this is where divine intervention comes in the form of a distribute-list that finally works (starting of course with an ACL):
R1(config)#access-list 3 deny 3.3.3.0 255.255.255.0
R1(config)#access-list 3 permit any
R1(config)#router ospf 1
R1(config-router)#distribute-list 3 ?
in Filter incoming routing updates
out Filter outgoing routing updates
R1(config-router)#distribute-list 3 out eigrp ?
<1-65535> Autonomous system number
R1(config-router)#distribute-list 3 out eigrp 100 ?
<cr>
R1(config-router)#distribute-list 3 out eigrp 100
R1(config-router)#
ASR#2
[Resuming connection 2 to r2 … ]
R2#sh ip route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback2
172.12.0.0/24 is subnetted, 1 subnets
C 172.12.12.0 is directly connected, Serial0/0
R2#
… What? So apparently my ACL was an EIGRP Redistribution killer, so I looked back upon my Access-List on R1 to see if I made a ‘deny any’ statement:
R1#sh access-list 3
Standard IP access list 3
10 deny 0.0.0.0, wildcard bits 255.255.255.0 (8 matches)
20 permit any (1 match)
I forgot the wildcard mask on the ACL. I am feeling quite silly right now, time to fix this:
R1(config)#no access-list 3
R1(config)#access-list 33 deny 3.3.3.0 0.0.0.255
R1(config)#access-list 33 permit any
R1(config)#router ospf 1
R1(config-router)#distribute-list 33 out eigrp 100
And over on R2:
R2#sh ip route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback2
33.0.0.0/24 is subnetted, 1 subnets
O E2 33.33.33.0 [110/1] via 172.12.12.1, 00:16:13, Serial0/0
3.0.0.0/24 is subnetted, 1 subnets
O E2 3.3.3.0 [110/1] via 172.12.12.1, 00:16:13, Serial0/0
172.12.0.0/24 is subnetted, 2 subnets
C 172.12.12.0 is directly connected, Serial0/0
O E2 172.12.13.0 [110/1] via 172.12.12.1, 00:16:13, Serial0/0
R2#
It is still there. This is starting to frustrate me. I am just going to honestly watch the rest of the video series on this topic, as I see some titled 2 way distribution, and EIGRP differs a bit from distribute-list’s than OSPF.
You have won the battle Cisco, but you have not won the war. I will get that CCNP R/s.
The DEVNET GRIND! 