Table Of Contents
Frame Relay Switching Diagnostics
and TroubleshootingSupported Standards, MIBs, and RFCs
Monitoring and Maintaining Frame Relay Switching
Frame Relay Switching Diagnostics
and Troubleshooting
This feature module describes the Frame Relay Switching Diagnostics and Troubleshooting feature. It includes information on the benefits of the new feature, supported platforms, related documents, and more.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Monitoring and Maintaining Frame Relay Switching
Feature Overview
If a problem is observed, the new debug frame-relay switching command can be used to display the status of packets on switched PVCs at regular intervals. This new debug command displays information such as the number of packets that were switched, why packets were dropped, and changes in status of physical links and PVCs. Debug information is displayed only when there has been a change from one configured interval to the next.
Benefits
The Frame Relay Switching Diagnostics and Troubleshooting feature provides tools for diagnosing problems in switched Frame Relay networks. If packets are being dropped from switched PVCs, network administrators can use these tools to quickly find out why. In addition, the NNI status display has been enhanced to give a more accurate picture of overall PVC health.
Restrictions
The Frame Relay Switching Diagnostics and Troubleshooting feature is not supported on terminated PVCs.
Related Documents
Cisco IOS Wide-Area Networking Configuration Guide, Release 12.0
Cisco IOS Wide-Area Networking Command Reference, Release 12.0
Supported Platforms
Cisco 12000 series
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
Configuration Tasks
None.
Monitoring and Maintaining Frame Relay Switching
To diagnose problems in switched Frame Relay networks, use one or both of the following privileged EXEC commands:
Command PurposeRouter# show frame-relay pvc
Displays statistics about PVCs for Frame Relay interfaces.
Router# debug frame-relay switching
Displays debug messages for switched Frame Relay PVCs.
Configuration Examples
None.
Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.
show frame-relay pvc
To display statistics about PVCs for Frame Relay interfaces, use the show frame-relay pvc EXEC command.
show frame-relay pvc [type] [number] [dlci]
Syntax Description
Command Modes
EXEC
Command History
Release Modification10.0
This command was introduced.
12.0(12)S
This command was modified to display reasons for packet drops and complete PVC status information for switched PVCs.
Usage Guidelines
Statistics Reporting
To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.
Per-VC counters are not incremented at all when either autonomous or SSE switching is configured; therefore, PVC values will be inaccurate if either switching method is used.
DCE, DTE, and Logical Interfaces
When the interface is configured as a DCE and the data-link connection identifier (DLCI) usage is SWITCHED, the value displayed in the PVC STATUS field is determined by the status of outgoing interfaces (up or down) and the status of the outgoing PVC. The status of the outgoing PVC is updated in the Local Management Interface (LMI) message exchange. PVCs terminated on a DCE interface use the status of the interface to set the PVC STATUS.
In the case of a hybrid DTE switch, the PVC status on the DTE side is determined by the PVC status reported by the external Frame Relay network through the LMI.
If the outgoing interface is a tunnel, the PVC status is determined by what is learned from the tunnel.
Traffic Shaping
Congestion control mechanisms are currently not supported on switched PVCs, but the switch passes forward explicit congestion notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligibility (DE) bits unchanged from entry to exit points in the network.
If an LMI status report indicates that a PVC is not active, then it is marked as inactive. A PVC is marked as deleted if it is not listed in a periodic LMI status message.
Examples
Switched PVC Example
Following is sample output from the show frame-relay pvc command for a switched Frame Relay PVC:
FRSW-2# show frame-relay pvc 16PVC Statistics for interface POS5/0 (Frame Relay NNI)DLCI = 16, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE = POS5/0LOCAL PVC STATUS = INACTIVE, NNI PVC STATUS = ACTIVEinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 100 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0switched pkts 0Detailed packet drop counters:no out intf 0 out intf down 100 no out PVC 0in PVC down 0 out PVC down 0 pkt too big 0pvc create time 00:25:32, last time pvc status changed 00:06:31Table 1 describes the fields shown in the display relevant switched PVCs.
1 The LOCAL PVC STATUS and NNI PVC STATUS fields are displayed only for PVCs configured on Frame Relay NNI interface types. These fields are not displayed if the PVC is configured on DCE or DTE interface types.
2 The detailed packet drop fields are displayed for switched Frame Relay PVCs only. These fields are not displayed for terminated PVCs.
DCE Interface with Traffic Shaping
The following is sample output from the show frame-relay pvc command:
Router# show frame-relay pvcPVC Statistics for interface Serial (Frame Relay DCE)DLCI = 22, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial3/1:1.1input pkts 9 output pkts 300008 in bytes 2754out bytes 161802283 dropped pkts 0 in FECN pkts 0in BECN pkts 1 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0Shaping adapts to ForeSight in ForeSight signals 1304pvc create time 1d05h, last time pvc status changed 00:11:00If the circuit is configured for shaping to adapt to BECN, it is indicated in the display:
Shaping adapts to BECNIf traffic shaping on the circuit does not adapt to either BECN or ForeSight, nothing extra shows:
DLCI = 100, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVEinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:03:03 last time pvc status changed 0:03:03Num Pkts Switched 0Multipoint Subinterfaces Example
The following is sample output from the show frame-relay pvc command for multipoint subinterfaces. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing.
DLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103input pkts 10 output pkts 7 in bytes 6222out bytes 6034 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:13:11 last time pvc status changed 0:11:46DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104input pkts 20 output pkts 8 in bytes 5624out bytes 5222 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:03:57 last time pvc status changed 0:03:48Table 2 describes the fields shown in the displays.
1 DLCI = data-link connection identifier.
DTE Interface Without Traffic Shaping Example
The following is sample output from the show frame-relay pvc command with no traffic shaping configured on the interface.
Router# show frame-relay pvcPVC Statistics for interface Serial1 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1input pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0DTE Interface With Traffic Shaping Example
The following is sample output from the show frame-relay pvc command when traffic shaping is in effect:
Router# show frame-relay pvcPVC Statistics for interface Serial1 (Frame Relay DTE)DLCI = 101, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1input pkts 14046 output pkts 4339 in bytes 960362out bytes 675566 dropped pkts 0 in FECN pkts 0in BECN pkts 148 out FECN pkts 0 out BECN pkts 0in DE pkts 44 out DE pkts 0out bcast pkts 4034 out bcast bytes 427346pvc create time 11:59:29, last time pvc status changed 11:59:29CIR 64000 BC 8000 BE 1600 limit 2000 interval 125mincir 32000 byte incremen 500 BECN response yespkts 9776 bytes 838676 pkts delayed 0 bytes delayed 0shaping inactiveList Queue Args1 4 byte-count 100Output queues: (queue #: size/max/drops)0: 0/20/0 1: 0/20/0 2: 0/20/0 3: 0/20/0 4: 0/20/05: 0/20/0 6: 0/20/0 7: 0/20/0 8: 0/20/0 9: 0/20/010: 0/20/0 11: 0/20/0 12: 0/20/0 13: 0/20/0 14: 0/20/015: 0/20/0 16: 0/20/0Table 3 describes the additional fields shown in the display when traffic shaping is in effect.
1 CIR = committed information rate.
2 Bc = committed burst size.
3 Be = excess burst size.
Debug Commands
This section documents the new debug command related to the Frame Relay Switching Diagnostics and Troubleshooting feature.
debug frame-relay switching
To display debug messages for switched Frame Relay PVCs, use the debug frame-relay switching EXEC command. To disable Frame Relay switching debugging, use the no form of this command.
debug frame-relay switching interface interface dlci [interval interval]
no debug frame-relay switching
Syntax Description
Defaults
The default interval is 1 second.
Command History
Usage Guidelines
The debug frame-relay switching command can be used only on switched Frame Relay PVCs, not terminated PVCs.
Debug statistics are displayed only if they have changed.
Note
Although statistics are displayed at configured intervals, there may be a delay between the occurrence of a debug event (such as a packet drop) and the display of that event. The delay may be as much as the configured interval plus 10 seconds.
Examples
The following example shows sample output for the debug frame-relay switching command:
FRSWDiag-2# debug frame-relay switching interface pos 2/2 116 interval 1Frame Relay switching debugging is onDisplay frame switching debug on interface POS2/2 dlci 11602:09:00: POS2/2 dlci 116: 230074 packets switched to POS2/3 dlci 11602:09:00: POS2/2 dlci 116: 115037 packets output02:09:00: POS2/2 dlci 116: Incoming PVC status changed to ACTIVE02:09:00: POS2/2 dlci 116: Outgoing PVC status changed to ACTIVE02:09:00: POS2/2 dlci 116: Incoming interface hardware module state changed to UP02:09:00: POS2/2 dlci 116: Outgoing interface hardware module state changed to UP02:09:11: POS2/2 dlci 116: 6812 packets switched to POS2/3 dlci 11602:09:11: POS2/2 dlci 116: 3406 packets output02:09:23: POS2/2 dlci 116: 8032 packets switched to POS2/3 dlci 11602:09:23: POS2/2 dlci 116: 4016 packets output

