Information Technology Reference
In-Depth Information
Table17-6
Traffic Does Not Initiate a Dial Attempt (continued)
Possible Causes
Suggested Actions
Interface that is
“administratively
down”
The dialer interface has been configured with the command
shutdown
. This is also the default state of any interface when a
Cisco router is booted for the very first time. Use the interface
configuration command
no shutdown
to remove this impediment.
Incorrect routing
Issue the exec command
show ip route [
a.b.c.d
]
, where
a.b.c.d
is
the address of the dialer interface of the remote router. (If
ip
unnumbered
is used on the remote router, use the address of the
interface listed in the
ip unnumbered
command.)
The output should show a route to the remote address via the
dialer interface. If there is no route, ensure that static or floating
static routes have been configured by examining the output of
show running-config
.
If there is a route via an interface other than the dialer interface,
the implication is that DDR is being used as a backup. Examine
the router configuration to make sure that static or floating static
routes have been configured. The surest way to test the routing in
this case is to disable the primary connection and then execute the
show ip route [
a.b.c.d
]
command to verify that the proper route
has been installed in the routing table.
Note:
If you attempt this during live network operations, a dial
event may be triggered. This sort of testing is best accomplished
during scheduled maintenance cycles.
Placing the Call
If the routing and the interesting traffic filters are correct, a call should be initiated. This can be seen by
using
debug dialer events
:
Async1 DDR: Dialing cause ip (s=10.0.0.1, d=10.0.0.2)
Async1 DDR: Attempting to dial 5551212
