debug frame-relay events
debug frame-relay eventsno debug frame-relay events
This command has no arguments or keywords.
To display debugging information about Frame Relay ARP replies on networks that support a multicast
channel and use dynamic addressing, use the debug frame-relay events privileged EXEC command.
The no form of this command disables debugging output.
This command is useful for identifying the cause of end-to-end connection problems during the
installation of a Frame Relay network or node.
Note: Because the debug frame-relay events command does not generate much output, you can use it at
any time, even during periods of heavy traffic, without adversely affecting other users on the system.
The following is sample output from the debug frame-relay events command:
Router# debug frame-relay events
Serial2(i): reply rcvd 172.16.170.26 126
Serial2(i): reply rcvd 172.16.170.28 128
Serial2(i): reply rcvd 172.16.170.34 134
Serial2(i): reply rcvd 172.16.170.38 144
Serial2(i): reply rcvd 172.16.170.41 228
Serial2(i): reply rcvd 172.16.170.65 325
As the output shows, the debug frame-relay events command returns one specific message type. The
first line, for example, indicates that IP address 172.16.170.26 sent a Frame Relay ARP reply; this packet
was received as input on serial interface 2. The last field (126) is the data-link connection identifier
(DLCI) to use when communicating with the responding router.
� Cisco Systems, Inc. 2001, 2002, 2003
World Wide Education
|Converted from CHM to HTML with chm2web Pro 2.85 (unicode)|