frame me...

i've begun actually to enjoy jerking around with frame lately... it takes more effort to avoid it...

hub and spoke... ip only... the interfaces ping because they are in the same subnet...

R1#sh run int s2/0
Building configuration...

Current configuration : 227 bytes
!
interface Serial2/0
 ip address 10.1.1.1 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 10.1.1.3 103 broadcast
 frame-relay map ip 10.1.1.2 102 broadcast
 no frame-relay inverse-arp

R2#sh run int s2/0
Building configuration...

Current configuration : 217 bytes
!
interface Serial2/0
 ip address 10.1.1.2 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 10.1.1.1 202 broadcast
 frame-relay map ip 10.1.1.3 202
 no frame-relay inverse-arp

R3#sh run int s2/0
Building configuration...

Current configuration : 217 bytes
!
interface Serial2/0
 ip address 10.1.1.3 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 10.1.1.2 303
 frame-relay map ip 10.1.1.1 303 broadcast
 no frame-relay inverse-arp

R3#trace 10.1.1.2
Type escape sequence to abort.
Tracing the route to 10.1.1.2
VRF info: (vrf in name/id, vrf out name/id)
  1 10.1.1.1 28 msec 36 msec 20 msec
  2 10.1.1.2 32 msec *  48 msec

the ip ospf interface command gives you a lot of flexibility with the topology...
choose your weapons...

R1(config)#router ospf 1
R1(config-router)#netw 10.1.1.0 0.0.0.255 area 0
R1(config-router)#netw 1.1.1.0 0.0.0.255 area 0

R2(config)#router ospf 1
R2(config-router)#netw 10.1.1.0 0.0.0.255 area 0
R2(config-router)#netw 2.2.2.0 0.0.0.255 area 0
R2(config-router)#end

R3(config)#router ospf 1
R3(config-router)#netw 10.1.1.0 0.0.0.255 area 0
R3(config-router)#netw 3.3.3.0 0.0.0.255 area 0

note: you'll get no adjacencies until you declare the interface network types...

once ip ospf network point-to-multipoint is placed on the interfaces, you have a happy ospf situation...

R3#sh ip route | b Gate
Gateway of last resort is not set

      1.0.0.0/32 is subnetted, 1 subnets
O        1.1.1.1 [110/65] via 10.1.1.1, 00:02:11, Serial2/0
      2.0.0.0/32 is subnetted, 1 subnets
O        2.2.2.2 [110/129] via 10.1.1.1, 00:02:11, Serial2/0
      3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        3.3.3.0/24 is directly connected, Loopback0
L        3.3.3.3/32 is directly connected, Loopback0
      10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C        10.1.1.0/24 is directly connected, Serial2/0
O        10.1.1.1/32 [110/64] via 10.1.1.1, 00:02:11, Serial2/0
O        10.1.1.2/32 [110/128] via 10.1.1.1, 00:02:11, Serial2/0
L        10.1.1.3/32 is directly connected, Serial2/0

R3#sh ip ospf int
Loopback0 is up, line protocol is up
  Internet Address 3.3.3.3/24, Area 0, Attached via Network Statement
  Process ID 1, Router ID 3.3.3.3, Network Type LOOPBACK, Cost: 1
  Topology-MTID    Cost    Disabled    Shutdown      Topology Name
        0           1         no          no            Base
  Loopback interface is treated as a stub Host
Serial2/0 is up, line protocol is up
  Internet Address 10.1.1.3/24, Area 0, Attached via Network Statement
  Process ID 1, Router ID 3.3.3.3, Network Type POINT_TO_MULTIPOINT, Cost: 64
  Topology-MTID    Cost    Disabled    Shutdown      Topology Name
        0           64        no          no            Base
  Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT
  Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
    oob-resync timeout 120
    Hello due in 00:00:03
  Supports Link-local Signaling (LLS)
  Cisco NSF helper support enabled
  IETF NSF helper support enabled
  Index 1/1, flood queue length 0
  Next 0x0(0)/0x0(0)
  Last flood scan length is 1, maximum is 1
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 1.1.1.1
  Suppress hello for 0 neighbor(s)

the loopbacks show up as loopbacks... make them networks with ip ospf network point-to-point

R1#sh ip ospf int lo0
Loopback0 is up, line protocol is up
  Internet Address 1.1.1.1/24, Area 0, Attached via Network Statement
  Process ID 1, Router ID 1.1.1.1, Network Type POINT_TO_POINT, Cost: 1
  Topology-MTID    Cost    Disabled    Shutdown      Topology Name
        0           1         no          no            Base
  Transmit Delay is 1 sec, State POINT_TO_POINT

the points network types have no dr/bdr (point-to-point and multipoint)

R1#sh ip ospf neigh

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.2           0   FULL/  -        00:01:58    10.1.1.2        Serial2/0
3.3.3.3           0   FULL/  -        00:01:47    10.1.1.3        Serial2/0

so there is no need to worry over ospf priority on the spokes...

R2#sh ip ospf neigh

Neighbor ID     Pri   State           Dead Time   Address         Interface
1.1.1.1           0   FULL/  -        00:01:53    10.1.1.1        Serial2/0

now make an ipv6 tunnel between r2 and r3...

R3#sh run int tun0
Building configuration...

Current configuration : 118 bytes
!
interface Tunnel0
 no ip address
 ipv6 address 2001::3/64
 tunnel source 10.1.1.3
 tunnel destination 10.1.1.2

R3#ping 2001::2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001::2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/32/40 ms

change the tunnel mode to ipv6ip...

note the encapsulation type...

frame relay non-broadcast...

because you love frame...

http://ardenpackeer.com/tutorials/routeswitch/tutorial-ospf-network-types-and-frame-relay-part-1/

earlier in the week i wrote something about not elaborating on arden's stuff... i'm taking that back because this is my site and i can do take backs if i want, and you can always go somewhere else...

simple topology, complicated stuff...

the default timers for ospf on ethernet are 10, 40 and slower links (aka serial) 30, 120...

r2#sh ip ospf int s1/0
Serial1/0 is up, line protocol is up
  Internet Address 192.168.1.2/24, Area 0, Attached via Network Statement
  Process ID 1, Router ID 2.2.2.2, Network Type NON_BROADCAST, Cost: 64
  Topology-MTID    Cost    Disabled    Shutdown      Topology Name
        0           64        no          no            Base
  Transmit Delay is 1 sec, State DROTHER, Priority 0
  Designated Router (ID) 1.1.1.1, Interface address 192.168.1.1
  No backup designated router on this network
  Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
    oob-resync timeout 120

for us humans that means four times the hello interval... the fact is that cisco uses 30, 120 for all non-broadcast networks no matter the media, which we will see in a minute...

r1#sh ip ospf neigh

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.2           0   FULL/DROTHER    00:01:48    192.168.1.2     Serial1/0
3.3.3.3           0   FULL/DROTHER    00:01:59    192.168.1.3     Serial1/0

note that the spokes are neither dr/bdr by design, meaning that the ospf priority has been manually set to 0 to avoid any election confusion...

r2#sh run int s1/0
Building configuration...

Current configuration : 267 bytes
!
interface Serial1/0
 ip address 192.168.1.2 255.255.255.0
 encapsulation frame-relay
 ip ospf network non-broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 192.168.1.1 201
 frame-relay map ip 192.168.1.3 201
 no frame-relay inverse-arp

and the neighbor statements are used because it is non-broadcast, and the hub needs to use unicast to send it's shit out...

r1#sh run | sec router
router ospf 1
 router-id 1.1.1.1
 network 0.0.0.0 255.255.255.255 area 0
 neighbor 192.168.1.2
 neighbor 192.168.1.3

r1#sh run int s1/0
Building configuration...

Current configuration : 247 bytes
!
interface Serial1/0
 ip address 192.168.1.1 255.255.255.0
 encapsulation frame-relay
 ip ospf network non-broadcast
 serial restart-delay 0
 frame-relay map ip 192.168.1.3 103
 frame-relay map ip 192.168.1.2 102
 no frame-relay inverse-arp


to make a frame topology behave like a broadcast type, or the default broadcast type which is ethernet, frame has to be manipulated to broadcast...of course that sounds obvious...

since we want frame to support the broadcast type, eliminate the ospf neighbor statements and change the type to broadcast...

r1(config)#int s1/0
r1(config-if)#ip ospf netw broad
r1(config-if)#
*Nov 17 06:16:33.627: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Serial1/0 from FULL to DOWN, Neighbor Down: Interface down or detached
*Nov 17 06:16:33.631: %OSPF-5-ADJCHG: Process 1, Nbr 3.3.3.3 on Serial1/0 from FULL to DOWN, Neighbor Down: Interface down or detached

r1#sh run | sec router
router ospf 1
 router-id 1.1.1.1
 network 0.0.0.0 255.255.255.255 area 0

r1#sh run int s1/0
Building configuration...

Current configuration : 263 bytes
!
interface Serial1/0
 ip address 192.168.1.1 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 serial restart-delay 0
 frame-relay map ip 192.168.1.3 103 broadcast
 frame-relay map ip 192.168.1.2 102 broadcast
 no frame-relay inverse-arp

r2#sh run int s1/0
Building configuration...

Current configuration : 273 bytes
!
interface Serial1/0
 ip address 192.168.1.2 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 192.168.1.1 201 broadcast
 frame-relay map ip 192.168.1.3 201
 no frame-relay inverse-arp

note that the broadcast only has to be enabled on each router's map to the hub... (this avoids unnecessary multicasts)

r3#sh run int s1/0
Building configuration...

Current configuration : 273 bytes
!
interface Serial1/0
 ip address 192.168.1.3 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 192.168.1.1 301 broadcast
 frame-relay map ip 192.168.1.2 301
 no frame-relay inverse-arp

and of course the priority remains 0, so there is no confusion in the election...

here is the upshot...

r1#sh ip ospf int
Serial1/0 is up, line protocol is up
  Internet Address 192.168.1.1/24, Area 0, Attached via Network Statement
  Process ID 1, Router ID 1.1.1.1, Network Type BROADCAST, Cost: 64
  Topology-MTID    Cost    Disabled    Shutdown      Topology Name
        0           64        no          no            Base
  Transmit Delay is 1 sec, State DR, Priority 1
  Designated Router (ID) 1.1.1.1, Interface address 192.168.1.1
  No backup designated router on this network
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit

all of this is perfectly meaningless because arden explained it much better than me but i now feel better taking the time to prove it for myself, thus driving the salient points home... so there...

and finally, arden's summation:

• Non-Broadcast network type is the default on a physical serial interface with ospf configured
• Non-Broadcast networks send unicast packets, so must be configured with neighbor statements
• Non-Broadcast networks have Hello and Dead intervals of 30 seconds and 120 seconds respectively
• Broadcast network types is the default on an ethernet interface.
• Broadcast network types must support broadcasting capability on a layer 2 topology
• Non-Broadcast and Broadcast network types require a DR. Care should be taken in DR placement (should be the Hub).

arden packeer...

http://ardenpackeer.com/tutorials/routeswitch/tutorial-ospf-network-types-frame-relay-series/

this is my new favorite human this week...

compared to bgp, ospf is intuitive... ospf over frame relay is not intuitive... understanding the various types in ospf takes time; lsa, network, packet, router, area, et al...

with ospf over frame relay there are a slew more types to get used to... it never stops, but as i've said before, perhaps that is the beauty of this mess...

i have this idea that coming to grips with the various ways ospf functions over frame, and doesn't function (you know when you are configuring against type because ospf screams at you) will give me an even better understanding of ospf operation on the whole...

and just when i thought i had ospf pegged...  

i'm counting on frame relay being a large part of the ccie lab because it presents many obstacles...

the wisdom is that you should not have to worry about frame relay from the provider side for the lab (meaning you shouldn't have to configure the frame relay switch, or cloud, itself), just like mpls... however, the fear is, that like mpls, you had better know the client side operation five ways from sunday...

and in case we should forget, the goal is not to beat the LAB, the goal is to greet the LAB, like an old and dear friend...

ospf nbma and broadcast...

http://ardenpackeer.com/tutorials/routeswitch/tutorial-ospf-network-types-and-frame-relay-part-1/

this is an excellent tutorial to go through... the summary follows, which means little or nothing until you get through it... pay particular attention to the verification with the timers to prove the type of network that is being created...

i will not attempt to re-present something in my own hand that i cannot add to in some meaningful way... this is perfect and needs no embellishment... so turn to and get it done..

• Non-Broadcast network type is the default on a physical serial interface with ospf configured
• Non-Broadcast networks send unicast packets, so must be configured with neighbor statements
• Non-Broadcast networks have Hello and Dead intervals of 30 seconds and 120 seconds respectively
• Broadcast network types is the default on an ethernet interface.
• Broadcast network types must support broadcasting capability on a layer 2 topology
• Non-Broadcast and Broadcast network types require a DR. Care should be taken in DR placement (should be the Hub).

if you are like me, you simply wish frame relay would go away... the sad reality is that it has little use in modern production networks, but its idiosyncrasies are exploited to great effect by cisco to make your R&S life difficult...

the only solution is to bite the bullet and turn it on its end in your favor... for someone like me, that means beating the shit out of it...

an old friend...

i was reading an article today... from: http://blog.ipexpert.com/2009/12/14/frame-relay-switch-configuration/

Back in the “old days” of CCIE R&S, candidates were expected to know how to configure their own frame-relay switch. As time went on, and things went to CCIE R&S v3.0, that requirement went by the wayside. We were told specifically that we would not have to configure the frame-relay switch itself – Only the routers connecting into it. In fact, we were not even given access to the frame-relay switch itself. With CCIE R&S v4.0 here in full swing, it might be a good idea to revisit this old beast. We have not been told to definitely expect it (no mention on the blueprint) but we have not been specifically told not to know it either. Better safe than sorry! The good news is, a frame-relay switch configuration is relatively straight forward, and can even solidify your fundamental knowledge of how frame-relay works.

just when you thought you were out of the woods on this one frame comes back to bite your ass... thanks, joe, for stirring up some ghosts...

ah, frame...

i thought i'd dust her off a little tonight, been a while...

making the frame switch is a pain in the ass, but good practice...

here is a post i did last year...
http://insearchofthecert.blogspot.com/2011/12/frame-dash-relay.html

and below is tonight...

and there she is...

fr-sw#sh run int s1/1
Building configuration...

Current configuration : 208 bytes
!
interface Serial1/1
 no ip address
 encapsulation frame-relay
 clockrate 128000
 frame-relay intf-type dce
 frame-relay route 102 interface Serial1/2 101
 frame-relay route 103 interface Serial1/3 101
end

fr-sw#sh run int s1/2
Building configuration...

Current configuration : 208 bytes
!
interface Serial1/2
 no ip address
 encapsulation frame-relay
 clockrate 128000
 frame-relay intf-type dce
 frame-relay route 101 interface Serial1/1 102
 frame-relay route 103 interface Serial1/3 102
end

fr-sw#sh run int s1/3
Building configuration...

Current configuration : 208 bytes
!
interface Serial1/3
 no ip address
 encapsulation frame-relay
 clockrate 128000
 frame-relay intf-type dce
 frame-relay route 101 interface Serial1/1 103
 frame-relay route 102 interface Serial1/2 103
end

the tough part is getting the routes correct...
it makes it easier for me if i talk through it while building it...

of course you've turned on frame-relay switching in global config first... making all the fr-sw interfaces dce's seems obvious enough... i named r1's dlci 101, r2 dlci 102 (i like numbers to go together like peas and carrots)

so here's the talk....

int s1/1
dlci 102 coming in (it's s1/1, dlci 101's perspective)
needs to get shipped out it's connected interface (s1/2) knowing it came from  101

likewise dlci 103 coming in goes out it's connected  interface (1/3) tagged with 101...

and so on...

fr-sw#sh frame route
Input Intf     Input Dlci     Output Intf     Output Dlci     Status
Serial1/1       102         Serial1/2       101         active
Serial1/1       103         Serial1/3       101         active
Serial1/2       101         Serial1/1       102         active
Serial1/2       103         Serial1/3       102         active
Serial1/3       101         Serial1/1       103         active
Serial1/3       102         Serial1/2       103         active

so adding another router, another interface and another dlci is a piece of cake...

dlci 104 coming in needs to get shipped to it's interface tagged with the dlci that's shipping it..

i have to use s2/1 for dlci 104 because i'm  out of corresponding numbers...

on s1/1(dlci 101)

frame route 104 int s2/1 101

for s1/2(dlci 102)

frame route 104 int s2/1 102

for s1/3

incoming 104 goes out s2/1 as 103

for s2/1 (104) you'll have to add three route's

incoming 101 goes out s1/1 as 104
incoming 102 goes out s1/2 as 104
incoming 103 goes out s1/3 as 104

and 104 is already spoken for on it's own interface...

fr-sw#sh fram route
Input Intf     Input Dlci     Output Intf     Output Dlci     Status
Serial1/1       102         Serial1/2       101         active
Serial1/1       103         Serial1/3       101         active
Serial1/1       104         Serial2/1       101         active
Serial1/2       101         Serial1/1       102         active
Serial1/2       103         Serial1/3       102         active
Serial1/2       104         Serial2/1       102         active
Serial1/3       101         Serial1/1       103         active
Serial1/3       102         Serial1/2       103         active
Serial1/3       104         Serial2/1       103         active
Serial2/1       101         Serial1/1       104         active
Serial2/1       102         Serial1/2       104         active
Serial2/1       103         Serial1/3       104         active

suitable for framing...

eigrp frame lab...

make some loopbacks...

on r1

interface Loopback1
 ip address 10.1.1.1 255.255.224.0
!
interface Loopback33
 ip address 10.1.33.1 255.255.224.0
!
interface Loopback65
 ip address 10.1.65.1 255.255.224.0
!
interface Loopback97
 ip address 10.1.97.1 255.255.224.0
!

interface Loopback161
 ip address 10.1.161.1 255.255.224.0

on r2

r2(config)#int lo1
r2(config-if)#ip add 10.2.1.1 255.255.224.0
r2(config-if)#int lo33
r2(config-if)#ip add 10.2.33.1 255.255.224.0
r2(config-if)#int lo65
r2(config-if)#ip add 10.2.65.1 255.255.224.0
r2(config-if)#int lo97
r2(config-if)#ip add 10.2.97.1 255.255.224.0
r2(config-if)#int lo129
r2(config-if)#ip add 10.1.129.1 255.255.224.0
r2(config-if)#int lo161
r2(config-if)#ip add 10.2.161.1 255.255.224.0

on r4

interface Loopback1
 ip address 10.3.1.1 255.255.224.0
!
interface Loopback33
 ip address 10.3.33.1 255.255.224.0
!
interface Loopback65
 ip address 10.3.65.1 255.255.224.0
!
interface Loopback97
 ip address 10.3.97.1 255.255.224.0
!
interface Loopback129
 ip address 10.3.129.1 255.255.224.0
!
interface Loopback161
 ip address 10.3.161.1 255.255.224.0

set up the frame switch...

r3fr#sh run (only essential config is shown)

hostname r3fr
!
frame-relay switching
!
interface Serial1/0
 no ip address
 encapsulation frame-relay IETF
 clockrate 64000
 frame-relay lmi-type cisco
 frame-relay intf-type dce
 frame-relay route 301 interface Serial1/1 103
!
interface Serial1/1
 no ip address
 encapsulation frame-relay IETF
 clockrate 128000
 frame-relay lmi-type cisco
 frame-relay intf-type dce
 frame-relay route 102 interface Serial1/2 201
 frame-relay route 103 interface Serial1/0 301
!
interface Serial1/2
 no ip address
 encapsulation frame-relay IETF
 clockrate 64000
 frame-relay lmi-type cisco
 frame-relay intf-type dce
 frame-relay route 201 interface Serial1/1 102

then set up the interfaces on the various routers...

r1#sh run int s1/1
Building configuration...

Current configuration : 222 bytes
!
interface Serial1/1
 ip address 172.16.124.1 255.255.255.248
 encapsulation frame-relay IETF
 frame-relay map ip 172.16.124.2 102 broadcast
 frame-relay map ip 172.16.124.3 103 broadcast
 no frame-relay inverse-arp

r2#sh run int s1/2
Building configuration...

Current configuration : 212 bytes
!
interface Serial1/2
 ip address 172.16.124.2 255.255.255.248
 encapsulation frame-relay IETF
 frame-relay map ip 172.16.124.1 201 broadcast
 frame-relay map ip 172.16.124.3 201
 no frame-relay inverse-arp

r4#sh run int s1/0
Building configuration...

Current configuration : 212 bytes
!
interface Serial1/0
 ip address 172.16.124.3 255.255.255.248
 encapsulation frame-relay IETF
 frame-relay map ip 172.16.124.1 301 broadcast
 frame-relay map ip 172.16.124.2 301
 no frame-relay inverse-arp

every body ping everybody...

r1#ping 172.16.124.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.124.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/19/36 ms
r1#ping 172.16.124.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.124.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/20/40 ms

r2#ping 172.16.124.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.124.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/19/36 ms
r2#ping 172.16.124.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.124.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/24/44 ms

r4#ping 172.16.124.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.124.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/9/12 ms
r4#ping 172.16.124.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.124.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/37/56 ms

if you want the routers to ping themselves, add maps to their own addresses... i'm not interested...

as was discussed in an earlier lab, bandwidth should match the clock rate... since we are in mr. mcfeely's frame relay land of make believe, do it on the interfaces you can control...

r1#sh run int s1/1 | incl bandwidth
 bandwidth 128

r2#sh run int s1/2 | incl band
 bandwidth 64

r4#sh run int s1/0 | incl band
 bandwidth 64

oh boy... we get to turn off auto-summ this time... this is very exciting...
set up eigrp for the major networks...

r1#sh run | begin router
router eigrp 1
 network 10.0.0.0
 network 172.16.0.0
 no auto-summary

do this for r2 and r4 as well...  go ahead and scrape... you know you will...
the ip route table for r1  looks good...

r1#sh ip route eigrp
     10.0.0.0/19 is subnetted, 17 subnets
D       10.2.0.0 [90/20640000] via 172.16.124.2, 00:12:46, Serial1/1
D       10.3.0.0 [90/20640000] via 172.16.124.3, 00:12:46, Serial1/1
D       10.2.32.0 [90/20640000] via 172.16.124.2, 00:12:46, Serial1/1
D       10.3.32.0 [90/20640000] via 172.16.124.3, 00:12:46, Serial1/1
D       10.2.64.0 [90/20640000] via 172.16.124.2, 00:12:46, Serial1/1
D       10.3.64.0 [90/20640000] via 172.16.124.3, 00:12:46, Serial1/1
D       10.2.96.0 [90/20640000] via 172.16.124.2, 00:12:46, Serial1/1
D       10.3.96.0 [90/20640000] via 172.16.124.3, 00:12:46, Serial1/1
D       10.3.128.0 [90/20640000] via 172.16.124.3, 00:12:46, Serial1/1
D       10.1.128.0 [90/20640000] via 172.16.124.2, 00:12:46, Serial1/1
D       10.2.160.0 [90/20640000] via 172.16.124.2, 00:12:46, Serial1/1
D       10.3.160.0 [90/20640000] via 172.16.124.3, 00:12:46, Serial1/1

but r2 is looking kinda weak...

r2#  sh ip route eigrp
     10.0.0.0/19 is subnetted, 11 subnets
D       10.1.0.0 [90/40640000] via 172.16.124.1, 00:15:36, Serial1/2
D       10.1.32.0 [90/40640000] via 172.16.124.1, 00:15:36, Serial1/2
D       10.1.64.0 [90/40640000] via 172.16.124.1, 00:15:36, Serial1/2
D       10.1.96.0 [90/40640000] via 172.16.124.1, 00:15:36, Serial1/2
D       10.1.160.0 [90/40640000] via 172.16.124.1, 00:15:36, Serial1/2
r2#

i know you know what's coming...  the big no ip split horizon trick... oooooooooooooooooooooooohhhhhhhhhhhhhhhhhhhh...

r1(config)#int s1/1
r1(config-if)#no ip split-horizon eigrp 1

r2#debug ip eigrp
IP-EIGRP Route Events debugging is on
00:43:40: IP-EIGRP: 10.2.0.0/19 - do advertise out Serial1/2
00:43:40: IP-EIGRP: Int 10.2.0.0/19 metric 128256 - 256 128000
00:43:40: IP-EIGRP: 10.2.32.0/19 - do advertise out Serial1/2
00:43:40: IP-EIGRP: Int 10.2.32.0/19 metric 128256 - 256 128000
00:43:40: IP-EIGRP: 10.2.64.0/19 - do advertise out Serial1/2
00:43:40: IP-EIGRP: Int 10.2.64.0/19 metric 128256 - 256 128000
00:43:40: IP-EIGRP: 10.2.96.0/19 - do advertise out Serial1/2
00:43:40: IP-EIGRP: Int 10.2.96.0/19 metric 128256 - 256 128000
00:43:40: IP-EIGRP: 10.1.128.0/19 - do advertise out Serial1/2
00:43:40: IP-EIGRP: Int 10.1.128.0/19 metric 128256 - 256 128000
00:43:40: IP-EIGRP: 10.2.160.0/19
r2#sh - do advertise out Serial1/2
00:43:40: IP-EIGRP: Int 10.2.160.0/19 metric 128256 - 256 128000
00:43:40: IP-EIGRP: 172.16.124.0/29 - do advertise out Serial1/2
00:43:42: IP-EIGRP: Processing incoming UPDATE packet
00:43:42: IP-EIGRP: Int 10.1.0.0/19 M 40640000 - 40000000 640000 SM 128256 - 256 128000
00:43:42: IP-EIGRP: Int 10.1.32.0/19 M 40640000 - 40000000 640000 SM 128256 - 256 128000
00:43:42: IP-EIGRP: Int 10.1.64.0/19 M 40640000 - 40000000 640000 SM 128256 - 256 128000
00:43:42: IP-EIGRP: Int 10.1.96.0/19 M 40640000 - 40000000 640000 SM 128256 - 256 128000
00:43:42: IP-EIGRP: Int 10.1.160.0/19 M 40640000 - 40000000 640000 SM 128256 - 256 128000
00:43:42: IP-EIGRP: Int 172.16.124.0/29 M 41024000 - 40000000 1024000 SM 20512000 - 20000000 512000
00:43:42: IP-EIGRP: 172.16.124.0/29 routing table not updated
00:43:42: IP-EIGRP: Int 10.1.0.0/19 metric 40640000 - 40000000 640000
00:43:42: IP-EIGRP: Int 10.1.32.0/19 metric 40640000 - 40000000 640000
00:43:42: IP-EIGRP: Int 1
r2#sh 0.1.64.0/19 metric 40640000 - 40000000 640000
00:43:42: IP-EIGRP: Int 10.1.96.0/19 metric 40640000 - 40000000 640000
00:43:42: IP-EIGRP: Int 10.1.160.0/19 metric 40640000 - 40000000 640000
00:43:42: IP-EIGRP: Processing incoming UPDATE packet
00:43:42: IP-EIGRP: Int 10.2.0.0/19 M 41152000 - 40000000 1152000 SM 20640000 - 20000000 640000
00:43:42: IP-EIGRP: 10.2.0.0/19 routing table not updated
00:43:42: IP-EIGRP: Int 10.2.32.0/19 M 41152000 - 40000000 1152000 SM 20640000 - 20000000 640000
00:43:42: IP-EIGRP: 10.2.32.0/19 routing table not updated
00:43:42: IP-EIGRP: Int 10.2.64.0/19 M 41152000 - 40000000 1152000 SM 20640000 - 20000000 640000
00:43:42: IP-EIGRP: 10.2.64.0/19 routing table not updated
00:43:42: IP-EIGRP: Int 10.2.96.0/19 M 41152000 - 40000000 1152000 SM 20640000 - 20000000 640000
00:43:42: IP-EIGRP: 10.2.96.0/19 routing table not updated
00:43:42: IP-EIGRP: Int 10.1.128.0/19 M 41152000 - 40000000 1152000 SM 20640000 - 20000000 640000
00:43:42: IP-EIGRP: 10.
r2#sh 1.128.0/19 routing table not updated
00:43:42: IP-EIGRP: Int 10.2.160.0/19 M 41152000 - 40000000 1152000 SM 20640000 - 20000000 640000
00:43:42: IP-EIGRP: 10.2.160.0/19 routing table not updated
r2#  

it's a twofer...

r2# sh ip route eigrp
     10.0.0.0/19 is subnetted, 17 subnets
D       10.3.0.0 [90/41152000] via 172.16.124.1, 00:03:51, Serial1/2
D       10.1.0.0 [90/40640000] via 172.16.124.1, 00:04:50, Serial1/2
D       10.3.32.0 [90/41152000] via 172.16.124.1, 00:03:51, Serial1/2
D       10.1.32.0 [90/40640000] via 172.16.124.1, 00:04:50, Serial1/2
D       10.3.64.0 [90/41152000] via 172.16.124.1, 00:03:51, Serial1/2
D       10.1.64.0 [90/40640000] via 172.16.124.1, 00:04:50, Serial1/2
D       10.3.96.0 [90/41152000] via 172.16.124.1, 00:03:51, Serial1/2
D       10.1.96.0 [90/40640000] via 172.16.124.1, 00:04:50, Serial1/2
D       10.3.128.0 [90/41152000] via 172.16.124.1, 00:03:51, Serial1/2
D       10.3.160.0 [90/41152000] via 172.16.124.1, 00:03:51, Serial1/2
D       10.1.160.0 [90/40640000] via 172.16.124.1, 00:04:50, Serial1/2

the book wants to run a tcl script to ping everybody... go ahead...

ok so we know split horizon is on by default and it makes frame misbehave...

who still uses frame?

word is they hang on to frame as a testable subject because it makes routing protocols do weird shit... great...

i made the multicast hello's into unicast with this...

router eigrp 1
 network 10.0.0.0
 network 172.16.0.0
 neighbor 172.16.124.3 Serial1/1
 neighbor 172.16.124.2 Serial1/1
 no auto-summary

and proved it with some caps below... note destinations, before and after...

please be my neighbor...

...i'll give you my lunch money

when a neighbor moves in all topology information is initially exchanged

after that, no more periodic visits from your neighbor

when your neighbor changes, he/she will only impart those changes (partial update)

if your neighbor dies, and is then resurrected, he/she will give you a full update  about the whole near death experience (brilliant white light, sense of calm, or if he/she is a new adjacency)

eigrp uses split horizon rules by default

for a refresher on eigrp and complications with frame and split horizon see the links in this older post... excellent keith barker video...


http://insearchofthecert.blogspot.com/2012/03/eigrp-and-split-horizon.html

and this quick and easy frame switch setup:

 http://insearchofthecert.blogspot.com/2011/12/frame-dash-relay.html

and now a word from alec baldwin:

right around 5:29 alec starts expounding upon split horizon...