From: Price, Jamie (jprice@xxxxxxxxxxx)
Date: Sat Mar 25 2000 - 19:55:46 GMT-3
Title: RE: ISDN
And again - I think this one was a bit of a freak occurence but it
could easily be a gotcha in the lab. Working on profiles I had one
problem where I assigned dialer pool 1 and dialer-group 1 to the
dialer int, dial pool-member 1 to the BRI. I checked and rechecked
configs - had all the right assignations where they were needed -
nothing was missing or in error. However, interesting traffic totally
refused to to bring up the link until I reassigned the pool on the
dialer int and pool-membership on the BRI to a number other than that
of the dialer-list/dialer-group (i.e. 2) - and yes they did exist
before - I checked.
After it worked by assigning the dialer pool/pool-membership to 2, I
changed the dialer pool/pool-membership back to 1 and it performed
fine. That caused me quite a headache - needless to say I now make it
a standard policy to differentiate between dialer pool/pool-membership
numbers and dialer-list/dialer-group numbers.
There's no way I want to run into that again - especially on the big
day out.
Jamie
-----Original Message-----
From: David Russell
To: Price, Jamie; 'Ccielab@Groupstudy.Com'
Sent: 3/25/00 3:58 PM
Subject: Re: ISDN
As long as we are sharing ...
I used to have a problem with ISDN callback. I would set it up and
then
use ping to test it. The ping would always seem to fail. Looking at
the debug I noticed that the callback is scheduled for "Dialer
enable-timeout" seconds after the call is dropped. By default it is
15
secs which is longer than the standard ping. By dropping the value to
say 5 seconds (I am not very patient either) I can get the much
desired
"..!!!" that tells us that life is good.
Dave
-----Original Message-----
From: Price, Jamie < jprice@isgteam.com <mailto:jprice@isgteam.com> >
To: 'Ccielab@Groupstudy.Com' <mailto:'Ccielab@Groupstudy.Com'> <
Ccielab@groupstudy.com <mailto:Ccielab@groupstudy.com> >
Date: Saturday, March 25, 2000 4:12 PM
Subject: ISDN
Hi,
I've noticed that there have been a few queries/comments of late on
ISDN
interfaces flapping when they shouldn't be.
I was recently having the same sort of problem and what I found may be
related to what a few other peoplemhave been dealing with so I felt
this
was a good place to speak up.
Even in a straight BRI to BRI setup on 2 routers, no other interfaces,
no routing protocols etc, I found that when I was using encap ppp the
call would be made, then disconnect after the idle-timeout only to
reconnect again straight away. This wouldn't happen using HDLC.
Investigation using "sh dialer" and "debug ppp neg" showed me that the
ppp traffic was keeping the interface up - even though my dialer list
was set to define only IP as interesting traffic.
The interface would flap anywhere between 2 and 6 times before it
would
actually shutdown - sometimes it wouldn't shut down at all,
consistently
ending the call and then setting it back up again. Using "sh dialer"
again I noticed that the "wait-for-carrier-time" was 30 seconds. My
idle-timeout was set at 10 (ok...I'm an impatient guy!!!). Increasing
the idle-timeout in excess of the wait-for-carrier-time (i.e. >30
secs)
took care of the problem completely.
`Playing around a bit more I wondered if dropping the
wait-for-carrier-time to 20 and the idle-timeout to 25 would work.
Playing around with the wait-for-carrier-time though really started
messing things up.
End result is that as long as I have my idle-timeout in excess of 30
secs my ISDN configs work fine. As I said this may be related to
problems others have been having using demand-circuits etc.
Does anyone want to expand on this? I'm using 11.3, 2 x 2600's, and a
Teltone ISDN demonstrator. I'm keen to know if theres a reason this
happens (I have been looking but am at a loss so far), if this is an
IOS
"feature", or if I have a flaky ISDN demonstrator.
Thanks
Jamie
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:06 GMT-3