From: Tony Schaffran (tschaffran@cconlinelabs.com)
Date: Mon Feb 03 2003 - 19:31:28 GMT-3
Joe,
Then, how would your ISDN ever come down?
Tony Schaffran
Network Analyst
CCNP, CCNA, CCDA,
NNCSS, NNCDS, CNE, MCSE
www.cconlinelabs.com
"Your #1 choice for Cisco rack rentals."
----- Original Message -----
From: "Joe Chang" <changjoe@earthlink.net>
To: <Sam.MicroGate@usa.telekom.de>; <ccielab@groupstudy.com>
Sent: Monday, February 03, 2003 12:50 PM
Subject: Re: ISDN link is not any routing protocols
> Set dialer idle-timeout to 0 on both ends.
>
> ----- Original Message -----
> From: <Sam.MicroGate@usa.telekom.de>
> To: <ccielab@groupstudy.com>
> Sent: Monday, February 03, 2003 5:10 PM
> Subject: ISDN link is not any routing protocols
>
>
> > Hello,
> >
> > I have a scenario that states the following:
> > 1- ISDN link does not belong to any routing protocols.
> > 2- You are allowed one default route in one side and a static route in
the
> > other side.
> > 3- The side that has a default route should able to initiate an isdn
call
> if
> > it loses its connectivity to the network.
> > 4- Only the side that has the default route should be able to initiate
an
> > isdn call.
> >
> > To meet these requirement I configure a default route pointing to next
hop
> > address (address in the dialer map statement) and then I redistribute
> static
> > into the IGP. This works fine. If I shut down the serial interface, the
ip
> > traffic initiate the isdn link and I can reach every part of the
network.
> > However, after the idle time out, I can not reach the ip address of the
> isdn
> > link from various parts of the network (because it is down) Is any
> > workaround for this. Thanks.
> >
> > Sam
> > .
> .
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:04 GMT-3