From: Daniel C. Young (danyoung99@xxxxxxxxxxxx)
Date: Sun Aug 19 2001 - 13:08:33 GMT-3
Hey Yonger,
PPP encapsulation automatically inserts a host route into the routing table
per RFC. Since it is a point-to-point link, they (the folks at IETF) must
have thought that the only address they need to know is the remote end, not
the entire subnet. You can override this behavior with the 'no peer
neighbor-route' command.
The redistribute static command here is being used for the floating-static
route. This is so that other routers can bring up the ISDN line immediately
when the primary link fails. Remember that redistribution occurs from the
forwarding table. Do a 'show ip route' and if you have a route with an 'S'
flag, you will have to redistribute static in order to propagate the route.
Regards,
Daniel
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
CCIE yong
Sent: Sunday, 19 August 2001 4:34 AM
To: ccielab@groupstudy.com
Subject: CCBootcamp Lab 13
Hi,
I'm doing the bootcamp lab 13 Section 2 Task 3 (last task) and found
something that puzzle me.
Why the host route of BRI interface appeared in the routing table of all the
routers in the diagram after the ATM0/1/0 shut down and ISDN being kick in.
what is the reason of the host route appear ?
Is it normal ?
This recall me when I did the ISDN demand circuit for OSPF routing in other
practise lab, the host route for the BRI interface is also appeared in the
routing table, why ?
One more question on this lab is that :
Is "redistribute static" in R5 & R6 needed in this case (as provided by the
solution)?? since the network 172.16.56.0 (for BRI Inter) already
participate in the EIGRP process on R5 & R6, the rest of the routers will
have full connectivity to all the network after BRI came up, therefore I
don't understand why we need to redistribute static at R5 & R6. ?
I'm posting the config for R6 & R5 and at the same time the route table for
R8 for bootcamp lab 13.
APPRECIATE your input.
Thanks in Advance.
YONGER
r5#
r5#sh ru
hostname r5
!
username user6 password 0 cisco
no ip domain-lookup
isdn switch-type basic-net3
dlsw local-peer peer-id 172.16.3.2
dlsw remote-peer 0 tcp 172.30.10.1
dlsw bridge-group 1
!
interface Ethernet0
ip address 172.16.3.2 255.255.255.0
bridge-group 1
!
interface BRI0
ip address 172.16.56.2 255.255.255.0
encapsulation ppp
dialer map ip 172.16.56.1 name user6 broadcast 3173
dialer-group 1
ppp authentication chap
ppp chap hostname user5
!
router eigrp 1
network 172.16.0.0
no auto-summary
!
no ip classless
ip route 172.30.0.0 255.255.0.0 172.16.56.1 200
access-list 100 deny eigrp any any
access-list 100 permit ip any any
!
dialer-list 1 protocol ip list 100
bridge 1 protocol ieee
!
end
r6#sh run
hostname r6
!
!
username user5 password 0 cisco
memory-size iomem 15
ip subnet-zero
no ip domain-lookup
isdn switch-type basic-net3
!
interface Ethernet0/0
ip address 172.30.20.1 255.255.255.0
no ip directed-broadcast
!
interface BRI0/0
ip address 172.16.56.1 255.255.255.0
no ip directed-broadcast
encapsulation ppp
dialer map ip 172.16.56.2 name user5 broadcast 3172
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap
ppp chap hostname user6
!
router eigrp 1
redistribute static
network 172.16.0.0
network 172.30.0.0
no auto-summary
!
ip classless
ip route 172.16.0.0 255.255.0.0 172.16.56.2 200
!
access-list 100 deny eigrp any any
access-list 100 permit ip any any
dialer-list 1 protocol ip list 100
!
allocate
end
r8#sh ip ro
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default
U - per-user static route, o - ODR
Gateway of last resort is not set
172.16.0.0/16 is variably subnetted, 8 subnets, 3 masks
D 172.16.56.0/24 [90/40537600] via 172.30.20.1, 00:11:19, Ethernet0/0
D 172.16.56.2/32 [90/40537600] via 172.30.20.1, 00:10:23, Ethernet0/0
D 172.16.50.0/24 [90/2214144] via 172.30.10.2, 00:11:19, TokenRing0/0
D 172.16.10.0/24 [90/2211584] via 172.30.10.2, 00:11:19, TokenRing0/0
D 172.16.11.0/24 [90/2214144] via 172.30.10.2, 00:11:19, TokenRing0/0
D EX 172.16.0.0/16 [170/40537600] via 172.30.20.1, 00:05:25, Ethernet0/0
D 172.16.2.0/24 [90/2214144] via 172.30.10.2, 00:11:19, TokenRing0/0
D 172.16.3.0/24 [90/40563200] via 172.30.20.1, 00:10:20, Ethernet0/0
172.30.0.0/16 is variably subnetted, 4 subnets, 2 masks
C 172.30.20.0/24 is directly connected, Ethernet0/0
D EX 172.30.0.0/16 [170/41049600] via 172.30.20.1, 00:05:32, Ethernet0/0
D 172.30.1.0/24 [90/2185984] via 172.30.10.2, 00:11:20, TokenRing0/0
C 172.30.10.0/24 is directly connected, TokenRing0/0
r8#
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:53 GMT-3