Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

What does this dial reason mean: Dial reason: Dialing on overload?

I have a 1604 router running 11.2(15a)P code that is setup for DDR using floating static routes.

Last night the ISDN interface was flapping, making 5 minute call after 5 minute call. The routing does not appear to have gone down during that time.

Here is the output of the show dialer command from the last call that the router made.

Dist_Hayward#sh dialer

BRI0 - dialer type = ISDN

Rotary group 1, priority = 0

0 incoming call(s) have been screened.

BRI0:1 - dialer type = ISDN

Idle timer (360 secs), Fast idle timer (20 secs)

Wait for carrier (30 secs), Re-enable (15 secs)

Dialer state is data link layer up

Dial reason: Dialing on overload

Time until disconnect 339 secs

Connected to 17007374164 (McGaw7507)

BRI0:2 - dialer type = ISDN

Idle timer (360 secs), Fast idle timer (20 secs)

Wait for carrier (30 secs), Re-enable (15 secs)

Dialer state is data link layer up

Dial reason: Dialing on overload

Time until disconnect 283 secs

Connected to 17007374164 (McGaw7507)

Dialer1 - dialer type = IN-BAND SYNC NO-PARITY

Load threshold for dialing additional calls is 1

What does a dial reason of Dial on Overload mean? Logically it sounds like something to do w/ bandwidth on demand, but that is a function of backup interface and not floating static route setup.

1 REPLY
Anonymous
N/A

Re: What does this dial reason mean: Dial reason: Dialing on ove

Yes, overload implies BOD (multilink

PPP). I'm guessing you have a load-

threshold set to 1 (Load threshold for

dialing additional calls is 1), in which

case what _should_ happen is that the first

link dials due to interesting traffic,

and subsequent links dial due to the load

threshold. You have some old code, so

there could be a bug here. You can enable

"debug dialer packet" to see what packet

(if any) is causing dialing, and then

verify if that packet makes sense. Otherwise,

you might try bumping the load-threshold

up to 3. As a last resort, you might try

upgrading the code to latest 12.1.

224
Views
0
Helpful
1
Replies