From: Hemant_Kumar@xxxxxxxxxx
Date: Fri Jul 12 2002 - 20:55:57 GMT-3
Carlos,
> Ok ...you can do it without dialer list since backup command will but the
> isdn interface on standby mode since no other protocol will be able to
use
> it.
I meant to say you don't need to deny ospf traffic using dialer-list. But
you do need dialer-list to trigger the dialing.
To summarize:
> 1. Configure OSPF for the network <--- ok run ospf on the ethernet
interface
> 2. Do not allow OSPF hello to keep the ISDN link up indefinitely <--
configure dialer list to permit all traffic. So if ethernet fails, isdn
link will become available. Dialer list will be used to trigger the
dialing. OSPF neighbors should be formed then.
> 3. The ISDN line should only come up when the ethernet connections failed
<-- backup interface bri; this will put the isdn line in standby mode. Note
eventhough there will be interesting traffic to initiate the call (because
you have dialer list to permit everything), there will be no physical
interface to make the call....isdn will be in the standby mode.
HK
Carlos G
Mendioroz
<tron@huapi.b To: Hemant_Kumar@BERLEX.COM
a.ar> cc: beda jain <bpjain@cisco.com>
Sent by: ccielab@groupstudy.com
nobody@groups Danny.Wang@alderwoods.com
tudy.com "Gyori Gabor" <Gabor.Gyori@lnx.hu>
P729 <p729@cox.net>
07/13/2002 Subject:
01:36 AM Re: ISDN and OSPF
Please
respond to
Carlos G
Mendioroz
Hemant,
I'm including your last two messages, inline:
Hemant_Kumar@BERLEX.COM wrote:
>
> Hi,
>
> Sorry my mistake...rather than passive interface, you need to deny ospf
via
> dialer list.
>
> 1. Configure OSPF for the network <--- ok run ospf on the ethernet
> interface
> 2. Do not allow OSPF hello to keep the ISDN link up indefinitely <--
> configure dialer list to deny ospf so that it does not bring up the link.
> But once the primary link fails, backup command will bring up the isdn.
> OSPF neighbors should be formed then.
Backup does not work by bringing a line up, rather it keeps a line down.
So when it is no longer disabled, something has to bring it up.
Then, if you don't let the OSPF traffic to be interesting, something
else
has to trigger the link up...
> 3. The ISDN line should only come up when the ethernet connections failed
> <-- backup interface bri
> >
> >HK
> Ok ...you can do it without dialer list since backup command will but the
> isdn interface on standby mode since no other protocol will be able to
use
> it.
>
> HK
If you don't have dialer list, you will not dial (unless you use dialer
watch).
>
>
> beda jain
> <bpjain@cisco
> .com> To: Hemant_Kumar@BERLEX.COM
> Sent by: Danny.Wang@alderwoods.com
> nobody@groups cc: ccielab@groupstudy.com
> tudy.com Gyori Gabor <Gabor.Gyori@lnx.hu>
> nobody@groupstudy.com
> "P729" <p729@cox.net>
> 07/12/2002 "Carlos G Mendioroz"
<tron@huapi.ba.ar>
> 04:33 PM Subject:
> Please RE: ISDN and OSPF
> respond to
> beda jain
>
>
>
> Hi,
> I think you should not configure passive interface for bri. If you do
that
> it will not form neighbor.
> When you configure back interface, the router will try to send hello
packet
>
> but it will not bring the link up.
> It will only bring the link up when the back int is down.
>
> Thanks,
> Beda
> At 01:48 AM 7/11/2002 +0200, Hemant_Kumar@BERLEX.COM wrote:
> >If you read you requirements i think it is asking for backup interface
> >rather ip ospf demand ckt.
> >
> >very simple scenario. R1 connected to R2 with both ISDN
> > and Ethernet.
> > > > > > > Requiment:
> > > > > > >
> > > > > > > 1. Configure OSPF for the network <--- ok run ospf on the
> >ethernet interface
> > > > > > > 2. Do not allow OSPF hello to keep the ISDN link up
> indefinitely
> ><-- configure passive interface for bri
> > > > > > > 3. The ISDN line should only come up when the ethernet
> >connections failed <-- backup interface bri
> >
> >HK
> >
> >
> >
> >
> > "Logan,
> >
> > Harold"
> >
> > <loganh@mccfl To: Gyori Gabor
> > <Gabor.Gyori@lnx.hu>
> > .edu> "Carlos G Mendioroz"
> > <tron@huapi.ba.ar>
> > Sent by: "P729"
> > <p729@cox.net>
> > nobody@groups
> > cc: <ccielab@groupstudy.com>
> >
> > tudy.com Subject:
> >
> > RE: ISDN and
> > OSPF
> >
> >
> > 07/10/2002
> >
> > 09:55
> > PM
> >
> > Please
> >
> > respond
> > to
> >
> > "Logan,
> >
> > Harold"
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >I think the bandwidth changing on interface dialer0 is key. If the ospf
> >cost is derived from the BW by default, then when the bri channels go
> down,
> >that represents a change in the ospf cost. If there's a change in cost,
> >that needs to be advertised as a change in the link state database,
which
> >will bring up the DDR link. The only question left unanswered is why the
> >link continued to flap in Danny's lab after he put an ospf cost on the
> >dialer interfaces.
> >
> > > -----Original Message-----
> > > From: Gyori Gabor [mailto:Gabor.Gyori@lnx.hu]
> > > Sent: Tuesday, July 09, 2002 7:45 AM
> > > To: Carlos G Mendioroz; P729
> > > Cc: ccielab@groupstudy.com
> > > Subject: RE: ISDN and OSPF
> > >
> > >
> > > I have tried ppp multilink on single bri without dialer profiles.
> > > The experiments:
> > > - dialer load-treshold 1 works (opens the second channel infitely)
> > > despite of documentation
> > > - the bandwith shown on interface is allways 64K regardless of the
> > > number of connected B channels.
> > >
> > > The results using dialer profiles:
> > > - dialer load-treshold 1 works (opens the second channel infitely)
> > > despite of documentation
> > > - The bandwith of Dialer0 is changing
> > > 56K when no channel is connected
> > > 64K when one channel is connected
> > > 128K when two channels are connected.
> > >
> > > Assigning bandwidth to Dialer interface is forbidden when the
> > > multilink ppp is
> > > active, so I think it is not recomened either (I had to
> > > relead the router
> > > after I have done this with no connected link).
> > >
> > > So when using native interface theres is no problem, using
> > > Dialer profile,
> > > ospf cost is the solution.
> > >
> > > I was using a 1603 with 12.1.14 on caller side, 2611 on
> > > remote using same
> > > IOS.
> > >
> > > Gabor
> > >
> > > > -----Original Message-----
> > > > From: Carlos G Mendioroz [mailto:tron@huapi.ba.ar]
> > > > Sent: Tuesday, July 09, 2002 3:01 AM
> > > > To: P729
> > > > Cc: ccielab@groupstudy.com
> > > > Subject: Re: ISDN and OSPF
> > > >
> > > >
> > > > Yup, I guess it will also do.
> > > >
> > > >
> > > > P729 wrote:
> > > > >
> > > > > Carlos,
> > > > >
> > > > > I never ran into this particular problem. Do you think
> > > > specifying the
> > > > > 'bandwidth' parameter will have the same effect as fixing
> > > > the ospf cost? Or
> > > > > is something else going on?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Mas Kato
> > > > > https://ecardfile.com/id/mkato
> > > > > ----- Original Message -----
> > > > > From: "Carlos G Mendioroz" <tron@huapi.ba.ar>
> > > > > To: <Danny.Wang@alderwoods.com>
> > > > > Cc: <ccielab@groupstudy.com>
> > > > > Sent: Monday, July 08, 2002 1:00 PM
> > > > > Subject: Re: ISDN and OSPF
> > > > >
> > > > > > Danny,
> > > > > > Short answer: fix the ospf cost of your ddr interfaces
> > > > (via ip ospf
> > > > > > cost).
> > > > > >
> > > > > > If you take a closer look, you should see that hellows
> > > > are supressed for
> > > > > > the
> > > > > > DDR interfaces. The link is being set because of an LSU
> > > > triggered by a
> > > > > > change in
> > > > > > cost of the link.
> > > > > >
> > > > > > HTH
> > > > > >
> > > > > > Danny.Wang@alderwoods.com wrote:
> > > > > > >
> > > > > > > Very simple scenario. R1 connected to R2 with both ISDN
> > > > and Ethernet.
> > > > > > >
> > > > > > > Requiment:
> > > > > > >
> > > > > > > 1. Configure OSPF for the network
> > > > > > > 2. Do not allow OSPF hello to keep the ISDN link up
> > > indefinitely
> > > > > > > 3. The ISDN line should only come up when the ethernet
> > > > connections
> > > > > failed
> > > > > > >
> > > > > > > But after i enable the 'ip ospf demand circuit' on the
> > > > dialer interface
> > > > > > > (one side only), the link still constantly up and down,
> > > > just wonderring
> > > > > if
> > > > > > > i missed something or it's a Teltone simulator "bug" ;-j
> > > > > > >
> > > > > > > When i enable debuy ip packet and dialer packet, it
> > > > shows the dialer
> > > > > caused
> > > > > > > by hello packet, source ip address from dialer 1 to
> > > 224.0.0.5 ).
> > > > > > >
> > > > > > > when i modified the dialer-list on the R1, it's
> > > > stopped, and leaving R2
> > > > > as
> > > > > > > is
> > > > > > >
> > > > > > > dialer list 1 protocol list 100
> > > > > > > access-list 100 deny ospf any any
> > > > > > > access-list 100 permit ip any any
> > > > > > >
> > > > > > > Any advice?
> > > > > > >
> > > > > > > R1------ISDN-------R2
> > > > > > > \ /
> > > > > > > \ /
> > > > > > > Ethernet
> > > > > > >
> > > > > > > r1# sh run
> > > > > > >
> > > > > > > Building configuration...
> > > > > > >
> > > > > > > Current configuration : 1551 bytes
> > > > > > > !
> > > > > > > version 12.1
> > > > > > > no service single-slot-reload-enable
> > > > > > > service timestamps debug uptime
> > > > > > > service timestamps log uptime
> > > > > > > no service password-encryption
> > > > > > > !
> > > > > > > hostname r1
> > > > > > > !
> > > > > > > !
> > > > > > > username CCIE2 password 0 cisco
> > > > > > > username r2 password 0 cisco
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip subnet-zero
> > > > > > > no ip domain-lookup
> > > > > > > !
> > > > > > > ip audit notify log
> > > > > > > ip audit po max-events 100
> > > > > > > isdn switch-type basic-ni
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface Loopback0
> > > > > > > ip address 10.10.11.1 255.255.255.255
> > > > > > > !
> > > > > > > interface Loopback1
> > > > > > > ip address 10.10.12.1 255.255.255.255
> > > > > > > !
> > > > > > > interface Loopback2
> > > > > > > ip address 10.10.13.1 255.255.255.255
> > > > > > > !
> > > > > > > interface Ethernet0/0
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > !
> > > > > > > interface Serial0/0
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > no fair-queue
> > > > > > > !
> > > > > > > interface BRI0/0
> > > > > > > no ip address
> > > > > > > encapsulation ppp
> > > > > > > dialer pool-member 1
> > > > > > > isdn switch-type basic-ni
> > > > > > > isdn spid1 0835866101 8358661
> > > > > > > isdn spid2 0835866301 8358663
> > > > > > > ppp authentication chap
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > interface Ethernet0/1
> > > > > > > ip address 192.168.1.211 255.255.255.0
> > > > > > > !
> > > > > > > interface Dialer1
> > > > > > > ip address 172.19.1.6 255.255.255.252
> > > > > > > encapsulation ppp
> > > > > > > ip ospf demand-circuit
> > > > > > > dialer pool 1
> > > > > > > dialer remote-name CCIE2
> > > > > > > dialer string 8358662
> > > > > > > dialer-group 1
> > > > > > > ppp authentication chap
> > > > > > > ppp chap hostname CCIE1
> > > > > > > ppp multilink
> > > > > > >
> > > > > > > !
> > > > > > > router ospf 64
> > > > > > > log-adjacency-changes
> > > > > > > network 10.10.11.1 0.0.0.0 area 0
> > > > > > > network 10.10.12.1 0.0.0.0 area 1
> > > > > > > network 10.10.13.1 0.0.0.0 area 2
> > > > > > > network 172.19.1.4 0.0.0.3 area 0
> > > > > > > network 192.168.1.0 0.0.0.255 area 0
> > > > > > > !
> > > > > > > ip classless
> > > > > > > ip http server
> > > > > > > ip ospf name-lookup
> > > > > > > !
> > > > > > > dialer-list 1 protocol ip permit
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec r show run
> > > > > > > alias exec c conf t
> > > > > > > !
> > > > > > > line con 0
> > > > > > > exec-timeout 0 0
> > > > > > > line aux 0
> > > > > > > line vty 0 4
> > > > > > > login
> > > > > > > !
> > > > > > > end
> > > > > > >
> > > > > > > r2#sh run
> > > > > > > Building configuration...
> > > > > > >
> > > > > > > Current configuration : 1627 bytes
> > > > > > > !
> > > > > > > version 12.1
> > > > > > > no service single-slot-reload-enable
> > > > > > > service timestamps debug uptime
> > > > > > > service timestamps log uptime
> > > > > > > no service password-encryption
> > > > > > > !
> > > > > > > hostname r2
> > > > > > > !
> > > > > > > logging buffered 10000 debugging
> > > > > > > !
> > > > > > > username CCIE1 password 0 cisco
> > > > > > > username r1 password 0 cisco
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip subnet-zero
> > > > > > > no ip domain-lookup
> > > > > > > !
> > > > > > > isdn switch-type basic-ni
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface Loopback0
> > > > > > > ip address 10.10.11.2 255.255.255.255
> > > > > > > !
> > > > > > > interface Loopback1
> > > > > > > ip address 10.10.12.2 255.255.255.255
> > > > > > > !
> > > > > > > interface Loopback2
> > > > > > > ip address 10.10.13.2 255.255.255.255
> > > > > > > !
> > > > > > > interface Ethernet0/0
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > !
> > > > > > > interface Serial0/0
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > no fair-queue
> > > > > > > !
> > > > > > > interface BRI0/0
> > > > > > > no ip address
> > > > > > > encapsulation ppp
> > > > > > > dialer pool-member 1
> > > > > > > isdn switch-type basic-ni
> > > > > > > isdn spid1 0835866201 8358662
> > > > > > > isdn spid2 0835866401 8358664
> > > > > > > ppp authentication chap
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > interface Ethernet0/1
> > > > > > > backup delay 2 2
> > > > > > > backup interface Dialer1
> > > > > > > ip address 192.168.1.212 255.255.255.0
> > > > > > > !
> > > > > > > interface Dialer1
> > > > > > > ip address 172.19.1.5 255.255.255.252
> > > > > > > encapsulation ppp
> > > > > > > dialer pool 1
> > > > > > > dialer remote-name CCIE1
> > > > > > > dialer string 8358661
> > > > > > > dialer load-threshold 128 either
> > > > > > > dialer-group 1
> > > > > > > ppp authentication chap
> > > > > > > ppp chap hostname CCIE2
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > router ospf 64
> > > > > > > log-adjacency-changes
> > > > > > > network 10.10.11.2 0.0.0.0 area 0
> > > > > > > network 10.10.12.2 0.0.0.0 area 12
> > > > > > > network 10.10.13.2 0.0.0.0 area 13
> > > > > > > network 172.19.1.4 0.0.0.3 area 0
> > > > > > > network 192.168.1.0 0.0.0.255 area 0
> > > > > > > !
> > > > > > > ip classless
> > > > > > > ip http server
> > > > > > > !
> > > > > > > dialer-list 1 protocol ip permit
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec r show run
> > > > > > > alias exec c conf t
> > > > > > >
> > > > > > > line con 0
> > > > > > > exec-timeout 0 0
> > > > > > > line aux 0
> > > > > > > line vty 0 4
> > > > > > > login
> > > > > > > !
> > > > > > > end
> > > > > > >
> > > > > > > Debug output:
> > > > > > >
> > > > > > > 00:44:45: IP: s=192.168.1.211 (local), d=224.0.0.5
> > > > (Ethernet0/1), len
> > > > > 68,
> > > > > > > sendin
> > > > > > > g broad/multicast
> > > > > > > 00:44:49: IP: s=192.168.1.212 (Ethernet0/1),
> > > > d=224.0.0.5, len 68, rcvd 0
> > > > > > > 00:44:54: IP: s=172.19.1.6 (local), d=224.0.0.5
> > > > (Dialer1), len 64,
> > > > > sending
> > > > > > > broad
> > > > > > > /multicast
> > > > > > > 00:44:54: Di1 DDR: ip (s=172.19.1.6, d=224.0.0.5), 64
> > > > bytes, outgoing
> > > > > > > interestin
> > > > > > > g (ip PERMIT)
> > > > > > > 00:44:54: IP: s=172.19.1.6 (local), d=224.0.0.5
> > > > (BRI0/0), len 64,
> > > > > > > encapsulation
> > > > > > > failed
> > > > > > > 00:44:55: IP: s=192.168.1.211 (local), d=224.0.0.5
> > > > (Ethernet0/1), len
> > > > > 68,
> > > > > > > sendin
> > > > > > > g broad/multicast
> > > > > > > 00:44:55: %LINK-3-UPDOWN: Interface BRI0/0:1, changed
> > > > state to up
> > > > > > > 00:44:55: %DIALER-6-BIND: Interface BR0/0:1 bound to
> > > profile Di1
> > > > > > > 00:44:56: %ISDN-6-CONNECT: Interface BRI0/0:1 is now
> > > > connected to
> > > > > 8358662
> > > > > > > 00:44:56: %ISDN-6-DISCONNECT: Interface BRI0/0:1
> > > > disconnected from
> > > > > 8358662
> > > > > > >
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:28 GMT-3