From: MMoniz (ccie2002@tampabay.rr.com)
Date: Fri Aug 08 2003 - 18:41:42 GMT-3
If you use loopback interfaces as your peers, then just let the backup for
routing
worry about it. You shouldn't have to do anything in DLSW except maybe
change
the keepalive so it won't constantly bring up the link.
R5 to R3 have ISDN backup R5 is 133.5.5.5 R3 is 133.5.3.3
Here is the peer state with primary link up.
R5#sho dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts TCP
uptime
TCP 133.5.2.2 CONNECT 3106 3106 conf 0 0 0
1d01h
TCP 133.5.3.3 CONNECT 3075 3076 conf 0 0 0
1d01h
TCP 133.5.6.6 CONNECT 2826 2826 prom 0 0 0
23:38:31
Total number of connected peers: 3
Total number of connections: 3
Now when I shut the primary link on R3
R5#sho dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts TCP
uptime
TCP 133.5.2.2 CONNECT 3111 3111 conf 0 0 0
1d01h
TCP 133.5.3.3 CONNECT 3084 3084 conf 0 0 0
1d01h
TCP 133.5.6.6 CONNECT 2831 2831 prom 0 0 0
23:41:08
Total number of connected peers: 3
Total number of connections: 3
R5#
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
ccie2be
Sent: Friday, August 08, 2003 1:43 PM
To: Group Study; Rob Laidlaw
Subject: Re: Dlsw over an ISDN link used as a backup for another link
Hi Rob,
thanks for your response.
I knew about the dlsw backup option but I don't think that's applicable to
this situation. If I'm wrong could you send me a sample config. Thanks
----- Original Message -----
From: "Rob Laidlaw" <laidlaw@consecro.com>
To: "ccie2be" <ccie2be@nyc.rr.com>
Sent: Friday, August 08, 2003 1:00 PM
Subject: Re: Dlsw over an ISDN link used as a backup for another link
> there is a dlsw peer x.x.x.x backup command.
>
>
> ----- Original Message -----
> From: "ccie2be" <ccie2be@nyc.rr.com>
> To: "Group Study" <ccielab@groupstudy.com>
> Sent: Friday, August 08, 2003 11:59 AM
> Subject: Dlsw over an ISDN link used as a backup for another link
>
>
> > Hi,
> >
> > I'm trying to figure out how to configure dlsw so that it's traffic can
> cross
> > the dialup link, but only when the primary link fails.
> >
> > Here's the situation:
> >
> >
> > /--- primary link----\
> > R1 R2
> > \-----isdn-------------/
> >
> >
> > I know how to config dlsw over the primary link and how to config dlsw
> over
> > the isdn link when there's only link. But, how do I make the dlsw
traffic
> > move from the primary to the isdn link when the primary fails?
> >
> > Normally, if you want dlsw to bring up the dialup link, the "dynamic"
> keyword
> > is added to the dlsw remote-peer command and interesting traffic is
> defined.
> > But, if this is configured, then how does dlsw know not to use this link
> as
> > long as the primary link is working?
> >
> > Thanks, dt
> >
> >
> > _______________________________________________________________________
> > You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:56 GMT-3