From: Steve Clubb (SClubb@xxxxxxxxxxx)
Date: Fri Oct 13 2000 - 20:19:40 GMT-3
This works.... (Tony)
r4
username r4 password 0 cisco
isdn switch-type basic-ni1
!
interface Serial0
ip address 172.16.34.4 255.255.255.0
encapsulation frame-relay
ip ospf network point-to-multipoint
shutdown
ipx network 1034
no fair-queue
frame-relay map ip 172.16.34.1 204 broadcast
frame-relay map ip 172.16.34.3 204 broadcast
frame-relay map ipx 1034.3000.0001.0001 204 broadcast
!
interface BRI0
ip address 172.16.14.4 255.255.255.0
encapsulation ppp
isdn spid1 40888870000101
isdn spid2 40888870000102
dialer map ip 172.16.14.1 name r1 broadcast 8883000
dialer-group 1
no cdp enable
ppp authentication chap
!
router ospf 10
network 172.16.34.0 0.0.0.255 area 40
network 172.16.14.0 0.0.0.255 area 40
r1
username r4 password 0 cisco
isdn switch-type basic-ni1
!
interface Serial0.1 multipoint
ip address 172.16.34.1 255.255.255.0
ip ospf network point-to-multipoint
ipx network 1034
no ipx split-horizon eigrp 1
frame-relay map ip 172.16.34.3 103 broadcast
frame-relay map ip 172.16.34.4 104 broadcast
!
interface BRI0
ip address 172.16.14.1 255.255.255.0
encapsulation ppp
ip ospf demand-circuit
isdn spid1 40888830000101
isdn spid2 40888830000102
dialer map ip 172.16.14.4 name r4 broadcast
dialer-group 1
no cdp enable
ppp authentication chap
!
router ospf 10
redistribute igrp 20 metric 12 metric-type 1 subnets
network 172.16.12.0 0.0.0.255 area 0
network 172.16.34.0 0.0.0.255 area 40
network 172.16.14.0 0.0.0.255 area 40
area 10 virtual-link 172.16.40.1
area 40 virtual-link 172.16.3.33
Steve Clubb
-----Original Message-----
From: Tony Olzak [mailto:aolzak@buckeye-express.com]
Sent: Friday, October 13, 2000 3:53 PM
To: Steve Clubb; 'Tony Medeiros'; B Fridie; cciemail; Feliz, Edgar
Subject: Re: ISDN staying up!!!
Send a copy of your configs. Are you using "backup interface" on the serial
interface?
Tony
----- Original Message -----
From: "Steve Clubb" <SClubb@cattech.com>
To: "'Tony Medeiros'" <tonygreat@home.com>; "Tony Olzak"
<aolzak@buckeye-express.com>; "B Fridie" <bfridie1@hotmail.com>; "cciemail"
<ccielab@groupstudy.com>; "Feliz, Edgar" <Edgar.Feliz@BTNA.com>
Sent: Friday, October 13, 2000 6:04 PM
Subject: RE: ISDN staying up!!!
> I'm having the same problem.
>
> I can get ISDN to dial one-way. But I'm not getting routes on the ISDN
> link.
>
> I shut the serial link.
>
> The ISDN network is in the same area as the Serial link.
>
> R4 goes FR to R1 (shut)
> R4 calls ISDN to R1
>
> I don't get routes when the ospf interface for bri0 is point-to-point,
> broadcast, or non-broadcast, with or without demand-circuit.
>
> I CAN get routes when I put neighbor statements on the OSPF process, but
the
> link stays up.
>
> Any comments?
>
> Steve
>
> -----Original Message-----
> From: Tony Medeiros [mailto:tonygreat@home.com]
> Sent: Friday, October 13, 2000 7:09 AM
> To: Tony Olzak; B Fridie; cciemail; Feliz, Edgar
> Subject: Re: ISDN staying up!!!
>
>
> Your right Tony.
> However, OSPF bringing up the link during a topology change actually
depends
> on the topology. If the ISDN link is used in a pure backup capacity, OSPF
> will bring up the link just fine even if you make OSPF non-interesting.
> Once you bring up the link for the first time, ( by using a tempory static
> route or just pinging the far side of the ISDN link), OSPF will converge
> and the database will have DNA entries in it. Then if your primary link
> goes down and primary routes go away, The ISDN link will become the
> prefered route and regular traffic will bring the link up and time out
when
> the traffic ends. You might have to play with OSPF costs if the serial
> links are slow to make sure that the ISDN link is less prefered. I have
set
> this up many times and it works great.
>
> Tony Medeiros
> CCIE 6172
> ----- Original Message -----
> From: "Tony Olzak" <aolzak@buckeye-express.com>
> To: "B Fridie" <bfridie1@hotmail.com>; "cciemail"
<ccielab@groupstudy.com>;
> "Feliz, Edgar" <Edgar.Feliz@BTNA.com>
> Sent: Thursday, October 12, 2000 6:07 AM
> Subject: Re: ISDN staying up!!!
>
>
> > Actually, OSPF would still be able to establish a neighbor relationship
> when
> > the line comes up. His config only filters 224.0.0.5 when defining
> > "interesting" traffic. It just won't bring the line up for anything
> > addressed to 224.0.0.5. His problem with that config is that topology
> > changes in other parts of the network won't be able to bring the line up
> (by
> > flooding on 224.0.0.5).
> >
> > Tony
> >
> > ----- Original Message -----
> > From: "B Fridie" <bfridie1@hotmail.com>
> > To: "cciemail" <ccielab@groupstudy.com>; "Feliz, Edgar"
> > <Edgar.Feliz@BTNA.com>
> > Sent: Thursday, October 12, 2000 1:52 AM
> > Subject: Re: ISDN staying up!!!
> >
> >
> > > Try putting a passive interface on dialer 0 for IGRP. According to
this
> > > config it is enabled on the dialer interface. That would keep the
link
> > up.
> > > Plus don't filter 224.0.0.5. OSPF would not be able to make a
neighbor
> > > relationship once the line is up.
> > >
> > > -Brian
> > > ----- Original Message -----
> > > From: Feliz, Edgar <Edgar.Feliz@BTNA.com>
> > > To: Clifton Stewart <cliftonlstewart@home.com>; 'Ccielab
> > > <ccielab@groupstudy.com>
> > > Sent: Thursday, October 12, 2000 1:10 AM
> > > Subject: RE: ISDN staying up!!!
> > >
> > >
> > > > I did not think I needed to do this because the "ospf on-demand"
> command
> > > > should only be used on one side, but I tried it anyway, but the link
> > still
> > > > comes up.
> > > >
> > > > EF
> > > >
> > > > -----Original Message-----
> > > > From: Clifton Stewart [mailto:cliftonlstewart@home.com]
> > > > Sent: Thursday, October 12, 2000 12:59 AM
> > > > To: Feliz, Edgar
> > > > Subject: ISDN staying up!!!
> > > >
> > > >
> > > > Feliz,
> > > >
> > > > While I look through your config could you place the ip ospf
on-demand
> > > > command on both sides of your ISDN connection. Thanks.
> > > >
> > > > -Cliff
> > > >
> > > > "Feliz, Edgar" wrote:
> > > > >
> > > > > Here is the config of r5. This lab is based on CCBOOTCAMP lab #5,
> but
> > I
> > > > > always add other twist to see how thing work with some changes. In
> > this
> > > > case
> > > > > I changed from a legacy DDR to a Dialer profile based DDR. I like
> the
> > > old
> > > > > way better it seems to have less headache associated with it but
as
> we
> > > all
> > > > > know you have to be ready to do just about everything on the LAB.
> > > > >
> > > > > EF
> > > > >
> > > > > r5#sr
> > > > > Building configuration...
> > > > >
> > > > > Current configuration:
> > > > > !
> > > > > version 11.3
> > > > > service timestamps debug datetime localtime
> > > > > service timestamps log datetime localtime
> > > > > no service password-encryption
> > > > > !
> > > > > hostname r5
> > > > > !
> > > > > enable password cisco
> > > > > !
> > > > > username r6 password 0 cisco
> > > > > username ccie password 0 cisco
> > > > > ip subnet-zero
> > > > > no ip domain-lookup
> > > > > isdn switch-type basic-ni1
> > > > > !
> > > > > !
> > > > > interface Ethernet0
> > > > > ip address 137.20.20.5 255.255.255.0
> > > > > ip ospf cost 1
> > > > > ip ospf priority 200
> > > > > !
> > > > > interface Serial0
> > > > > no ip address
> > > > > encapsulation frame-relay IETF
> > > > > no ip mroute-cache
> > > > > frame-relay lmi-type cisco
> > > > > !
> > > > > interface Serial0.1 multipoint
> > > > > ip address 172.16.100.5 255.255.255.0
> > > > > ip ospf network point-to-multipoint
> > > > > frame-relay interface-dlci 503
> > > > > frame-relay interface-dlci 506
> > > > > !
> > > > > interface Serial0.2 point-to-point
> > > > > ip address 172.16.200.1 255.255.255.0
> > > > > frame-relay interface-dlci 504
> > > > > !
> > > > > interface Serial1
> > > > > no ip address
> > > > > shutdown
> > > > > !
> > > > > interface BRI0
> > > > > no ip address
> > > > > encapsulation ppp
> > > > > dialer pool-member 1
> > > > > isdn spid1 0835866101 8358661
> > > > > isdn spid2 0835866301 8358663
> > > > > no cdp enable
> > > > > ppp authentication chap
> > > > > !
> > > > > interface Dialer0
> > > > > ip address 172.16.65.5 255.255.255.0
> > > > > encapsulation ppp
> > > > > ip ospf demand-circuit
> > > > > dialer remote-name r6
> > > > > dialer idle-timeout 300
> > > > > dialer string 8358662
> > > > > dialer string 8358664
> > > > > dialer pool 1
> > > > > dialer-group 1
> > > > > no peer neighbor-route
> > > > > no cdp enable
> > > > > ppp authentication chap
> > > > > ppp chap hostname ccie
> > > > > !
> > > > > router ospf 5
> > > > > redistribute igrp 5 subnets
> > > > > network 137.20.20.0 0.0.0.255 area 0
> > > > > network 172.16.65.0 0.0.0.255 area 10
> > > > > network 172.16.100.0 0.0.0.255 area 10
> > > > > area 10 virtual-link 172.16.3.65
> > > > > area 10 virtual-link 172.16.100.6
> > > > > area 10 virtual-link 172.16.65.6
> > > > > !
> > > > > router igrp 5
> > > > > redistribute ospf 5 metric 2000 100 255 1 1500
> > > > > network 172.16.0.0
> > > > > !
> > > > > ip classless
> > > > > !
> > > > > access-list 100 deny ip any host 224.0.0.5
> > > > > access-list 100 permit ip any any
> > > > > dialer-list 1 protocol ip list 100
> > > > > alias exec sr sh runn
> > > > > alias exec sir sh ip route
> > > > > alias exec ct conf term
> > > > > alias exec sio sh ip ospf int
> > > > > alias exec wm wr mem
> > > > > !
> > > > > line con 0
> > > > > exec-timeout 0 0
> > > > > privilege level 15
> > > > > line aux 0
> > > > > privilege level 15
> > > > > line vty 0 4
> > > > > privilege level 15
> > > > > login local
> > > > > !
> > > > > end
> > > > >
> > > > > -----Original Message-----
> > > > > From: Clifton Stewart [mailto:cliftonlstewart@home.com]
> > > > > Sent: Thursday, October 12, 2000 12:29 AM
> > > > > To: Feliz, Edgar; ccielab@groupstudy.com
> > > > > Subject: ISDN staying up!!!
> > > > >
> > > > > Feliz,
> > > > >
> > > > > Which routing protocol are you using? Using a backup interface
will
> > > > > definitely keep the line down until your serial drops. If using
OSPF
> > > > > then implement ip ospf on demand circuit. If EIGRP then use a
> > > > > dialer-watch. If your using distance vector protocols then think
> about
> > > > > snapshot routing as an option. Could you post your configs? Let's
> have
> > > > > some fun!
> > > > >
> > > > > -Cliff
> > > > >
> > > > > "Feliz, Edgar" wrote:
> > > > > >
> > > > > > How can I stop the following that I believe is keeping up my
ISDN
> > line
> > > > > > without restricting PPP, as I am using PPP as my encap type? I
get
> > the
> > > > > > following when I "deb PPP packet, authentication, and
negotiation.
> > > > > >
> > > > > > Mar 1 11:36:56: BR0:1 LCP: O ECHOREQ [Open] id 3 len 12 magic
> > > > 0x028A54B4
> > > > > > *Mar 1 11:36:56: BR0:1 LCP: echo_cnt 1, sent id 3, line up
> > > > > > *Mar 1 11:36:56: BR0:1 PPP: I pkt type 0xC021, datagramsize 16
> > > > > > *Mar 1 11:36:56: BR0:1 LCP: I ECHOREP [Open] id 3 len 12 magic
> > > > 0x02AEF0A1
> > > > > > *Mar 1 11:36:56: BR0:1 LCP: Received id 3, sent id 3, line up
> > > > > > *Mar 1 11:37:04: BR0:1 PPP: I pkt type 0xC021, datagramsize 16
> > > > > > *Mar 1 11:37:04: BR0:1 LCP: I ECHOREQ [Open] id 3 len 12 magic
> > > > 0x02AEF0A1
> > > > > > *Mar 1 11:37:04: BR0:1 LCP: O ECHOREP [Open] id 3 len 12 magic
> > > > 0x028A54B4
> > > > > > *Mar 1 11:37:06: BR0:1 LCP: O ECHOREQ [Open] id 4 len 12 magic
> > > > 0x028A54B4
> > > > > > *Mar 1 11:37:06: BR0:1 LCP: echo_cnt 1, sent id 4, line up
> > > > > > *Mar 1 11:37:06: BR0:1 PPP: I pkt type 0xC021, datagramsize 16
> > > > > > *Mar 1 11:37:06: BR0:1 LCP: I ECHOREP [Open] id 4 len 12 magic
> > > > 0x02AEF0A1
> > > > > > *Mar 1 11:37:06: BR0:1 LCP: Received id 4, sent id 4, line up
> > > > > > *Mar 1 11:37:14: BR0:1 PPP: I pkt type 0xC021, datagramsize 16
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Edgar Feliz
> > > > > >
> > > > > > Brazil x 2 11/13-14
> > > > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:26 GMT-3