Specifications

180 Chapter 7. Troubleshooting

Debugging Commands

The following commands may be available for debugging purposes. Please use them with caution because they

are not fully supported.

General Debug Commands

ifs

Shows which interfaces are configured or active. For an example of its output, see page 190.

BNCP is for bridging, ECP for encryption, and NCPSTATES for state table changes.

To turn off the trace, enter the command with the optional 0 at the end.

ipdebug icmp 1

ipdebug nat 1

These commands show data received. The ipdebug icmp 1 command is useful for showing the router can

receive cells ok.

dod whycall 80

Prints out the packet that is causing the link to come up. This is useful when system onewan on is set. (This

command makes PVCÕs look like dial-up links, that is, the link comes up only if user traffic exists and the

link times out on inactivity.) For more information, see SYSTEM ONEWANDIALUP, on page 225

dod debug <1 | 0>

Shows trace of when we bring up the link or time out link on inactivity. Specify 1 to turn on the trace; specify

0 to turn off the trace.

ping [-c count] [-i wait] [-s | -l size] [-I sourceipaddr] <ipaddr>

Sends an echo message to the specified IP address. You cannot ping your own LAN address; you can ping

your own WAN address.

You can set the length of user data down to 0 bytes (-s 0 or -l 0) so in routing mode it fits in one ATM cell.

(See page 194.)

traceroute [-c count] [-i wait] [-s | -l size] [-I sourceipaddr] <ipaddr>

Traces the route taken by packets sent from the target router to the specified IP address. A packet is sent for

each hop in the route. The output lists the IP addresses of the hops that returned packets. (See page 198.)

system log [start | stop | status]

Starts event logging when logged in via Telnet. Otherwise, you donÕt see any event messages. It is not needed

if you are using a console cable. (See page 223.)

system support