Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IOS Software Releases 12.2 T

Frame Relay 64-Bit Counters

Downloads

Table Of Contents

Frame Relay 64-Bit Counters

Feature Overview

Benefits

Restrictions

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites

Configuration Tasks

Enabling Frame Relay Interfaces to Be Included in 64-Bit Interface MIB Counters

Monitoring and Maintaining Frame Relay 64-Bit Counters

Configuration Examples

Enabling Slower Frame Relay Interfaces and Subinterfaces to Be Included in 64-Bit Interface MIB Counters: Example

Enabling Only Slower Frame Relay Subinterfaces to Be Included in 64-Bit Interface MIB Counters: Example

Command Reference

frame-relay ifmib-counter64

show frame-relay pvc


Frame Relay 64-Bit Counters

Feature History

Release
Modification

12.0(17)S

This feature was introduced on the Cisco 12000 series.

12.2(4)T

This feature was integrated into Cisco IOS Release 12.2(4)T.

12.2(4)T3

Support for the Cisco 7500 series routers was added.

12.0(21)S

The frame-relay ifmib-counter64 command was introduced.

12.3(10)

The frame-relay ifmib-counter64 command was integrated into Cisco IOS Release 12.3(10).

12.3(11)T

The frame-relay ifmib-counter64 command was integrated into Cisco IOS Release 12.3(11)T.

12.2(18)SXE

The frame-relay ifmib-counter64 command was integrated into Cisco IOS Release 12.2(18)SXE.


This document describes the Frame Relay 64-Bit Counters feature in Cisco IOS Release 12.2(4)T. It includes the following sections:

•Feature Overview

•Supported Platforms

•Supported Standards, MIBs, and RFCs

•Prerequisites

•Configuration Tasks

•Monitoring and Maintaining Frame Relay 64-Bit Counters

•Configuration Examples

•Command Reference

Feature Overview

The Frame Relay 64-Bit Counters feature provides 64-bit counter support on Frame Relay interfaces and subinterfaces. This feature enables the gathering of statistics through Simple Network Management Protocol (SNMP) for faster interfaces operating at OC-3, OC-12, and OC-48 speeds.

The following counters are supported by this feature: Bytes In, Bytes Out, Packets In, and Packets Out.

The show frame-relay pvc command has been modified to display the 64-bit counters.

Benefits

The values in 32-bit counters sometime wrap because the field is too small. Wrapping causes the values in these fields to become meaningless. The 64-bit counters support the reliable gathering of statistics by SNMP by preventing the wrapping of counter values.

Restrictions

SNMP cannot retrieve 64-bit virtual-circuit (VC) counters.

Related Documents

For information on configuring Frame Relay using Cisco IOS software, refer to the following documents:

•The chapter "Configuring Frame Relay" in the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2

•The chapter "Frame Relay Commands" in the Cisco IOS Wide-Area Networking Command Reference, Release 12.2

For information on configuring SNMP using Cisco IOS software, see the following documents:

•The chapter "Configuring Simple Network Management Protocol" in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2

•The chapter "SNMP Commands" in the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2

Supported Platforms

•Cisco 7200 series

•Cisco 7500 series (Cisco IOS Release 12.2(4)T3 and later)

Platform Support Through Feature Navigator

Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Feature Navigator. Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.

Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image.

To access Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register.

Feature Navigator is updated when major Cisco IOS software releases and technology releases occur. As of May 2001, Feature Navigator supports M, T, E, S, and ST releases. You can access Feature Navigator at the following URL:

http://www.cisco.com/go/fn

Supported Standards, MIBs, and RFCs

Standards

No new or modified standards are supported by this feature.

MIBs

The frame-relay ifmib-counter64 command modifies the interface MIB (IF-MIB) by allowing slower Frame Relay interfaces and subinterfaces to be included in the 64-bit interface MIB counters.

To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs

No new or modified RFCs are supported by this feature.

Prerequisites

This document assumes that you know how to configure Frame Relay and SNMP support using Cisco IOS software.

Configuration Tasks

This section contains the following task:

•Enabling Frame Relay Interfaces to Be Included in 64-Bit Interface MIB Counters

Enabling Frame Relay Interfaces to Be Included in 64-Bit Interface MIB Counters

Note This task is supported in Cisco IOS releases 12.0(21)S, 12.3(10), 12.3(11)T, 12.2(18)SXE, and later releases.

Frame Relay interfaces and subinterfaces that have a line speed greater than 20 Mbps are included in the 64-bit interface MIB counters by default. Perform this task to enable Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps to be included in the 64-bit interface MIB counters.

 
Command
Purpose

Step 1 

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

Router# configure terminal

Enters global configuration mode.

Step 3 

Router(config)# interface serial interface-number

Specifies an interface to be configured and enters interface configuration mode.

Step 4 

Router(config-if)# encapsulation frame-relay

Enables Frame Relay encapsulation.

Step 5 

Router(config-if)# frame-relay ifmib-counter64 [if | subif]

Enables Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps to be included in 64-bit interface MIB counters.

•This command allows Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps to be included in the following 64-bit interface MIB counters:

–ifHCinOctets

–ifHCOutOctets

–ifHCinUcastPkts

–ifHCOutUcastPkts

Monitoring and Maintaining Frame Relay 64-Bit Counters

To view the values of the Frame Relay 64-bit counters, use the following command in EXEC mode:

Command
Purpose 
Router# show frame-relay pvc 64-bit [interface interface] [dlci]

Displays statistics about permanent virtual circuits (PVCs) for Frame Relay interfaces.


Configuration Examples

This section contains the following example:

•Enabling Slower Frame Relay Interfaces and Subinterfaces to Be Included in 64-Bit Interface MIB Counters: Example

•Enabling Only Slower Frame Relay Subinterfaces to Be Included in 64-Bit Interface MIB Counters: Example

Enabling Slower Frame Relay Interfaces and Subinterfaces to Be Included in 64-Bit Interface MIB Counters: Example

In the following example, the frame-relay ifmib-counter64 command is used with the if keyword to enable serial interfaces 6/0/1:0, 6/0/2:0, and 6/0/3:0 and related subinterfaces to be included in the 64-bit interface MIB counters. The example also shows corresponding output for the show frame-relay pvc command and the corresponding statistics for the 64-bit interface MIB counters. 

interface Serial6/0/1:0

 ip address 1.1.1.1 255.255.255.0

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 frame-relay interface-dlci 101

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 if 


interface Serial6/0/2:0

 no ip address

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 if 

!

interface Serial6/0/2:0.1 point-to-point  

 ip address 2.1.1.1 255.255.255.0  

 no ip route-cache

 frame-relay interface-dlci 201 

!

interface Serial6/0/3:0

 ip address 3.1.1.1 255.255.255.0

 encapsulation frame-relay

 frame-relay interface-dlci 301

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 if 


interface Serial6/0/3:0.1 point-to-point  

 ip address 3.1.2.1 255.255.255.0

 frame-relay interface-dlci 302

The following example shows corresponding sample output for the show frame-relay pvc command with the 64-bit keyword. Note that the frame-relay ifmib-counter64 command does not affect the output of the show frame-relay pvc command. 

Router# show frame-relay pvc 101 64-bit


DLCI = 101, INTERFACE = Serial6/0/1:0

  input pkts 231                     output pkts 228                 

  in bytes 23604                     out bytes 23502               

Router#

Router# show frame-relay pvc 201 64-bit 


DLCI = 201, INTERFACE = Serial6/0/2:0.1

  input pkts 1453                    output pkts 1408                

  in bytes 335024                    out bytes 327272              

Router#

Router# show frame-relay pvc 301 64-bit


DLCI = 301, INTERFACE = Serial6/0/3:0

  input pkts 510                     output pkts 508                 

  in bytes 52690                     out bytes 52622               

Router#

Router# show frame-relay pvc 302 64-bit


DLCI = 302, INTERFACE = Serial6/0/3:0.1

  input pkts 957                     output pkts 912                 

  in bytes 283246                    out bytes 275493              

Router#

The following output from an SNMP inquiry shows that the 64-bit interface MIB counters include the interfaces configured above: 

ifHCInOctets.5 = 0x000000000

ifHCInOctets.16 = 0x000000000

ifHCInOctets.17 = 0x003360d33

ifHCInOctets.18 = 0x000000000

ifHCInOctets.19 = 0x000000000

ifHCInOctets.20 = 0x000000000

ifHCInOctets.24 = 0x000000000

ifHCInOctets.25 = 0x000000000

ifHCInOctets.26 = 0x0001a7afc !! This is serial interface 6/0/1:0

ifHCInOctets.28 = 0x0001a7370 !! This is serial interface 6/0/2:0

ifHCInOctets.34 = 0x00006a45a !! This is serial interface 6/0/3:0

ifHCInOctets.36 = 0x000051cb0 !! This is serial subinterface 6/0/2:0.1

ifHCInOctets.37 = 0x00004526e !! This is serial subinterface 6/0/3:0.1

Enabling Only Slower Frame Relay Subinterfaces to Be Included in 64-Bit Interface MIB Counters: Example

In the following example, the frame-relay ifmib-counter64 command is used with the subif keyword to enable subinterfaces that are associated with serial interfaces 6/0/1:0, 6/0/2:0, and 6/0/3:0 to be included in the 64-bit interface MIB counters. Slower main interfaces are not included. The example also shows the corresponding statistics for the 64-bit interface MIB counters. 

interface Serial6/0/1:0

 ip address 1.1.1.1 255.255.255.0

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 frame-relay interface-dlci 101

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 subif 


interface Serial6/0/2:0

 no ip address

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 subif 


interface Serial6/0/2:0.1 point-to-point  

 ip address 2.1.1.1 255.255.255.0  

 no ip route-cache

 frame-relay interface-dlci 201 

!

interface Serial6/0/3:0

 ip address 3.1.1.1 255.255.255.0

 encapsulation frame-relay

 frame-relay interface-dlci 301

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 subif 


interface Serial6/0/3:0.1 point-to-point  

 ip address 3.1.2.1 255.255.255.0

 frame-relay interface-dlci 302

The following example shows corresponding sample output for the show frame-relay pvc command with the 64-bit keyword. Note that the frame-relay ifmib-counter64 command does not affect the output of the show frame-relay pvc command. 

Router# show frame-relay pvc 101 64-bit


DLCI = 101, INTERFACE = Serial6/0/1:0

  input pkts 231                     output pkts 228                 

  in bytes 23604                     out bytes 23502               

Router#

Router# show frame-relay pvc 201 64-bit


DLCI = 201, INTERFACE = Serial6/0/2:0.1

  input pkts 1453                    output pkts 1408                

  in bytes 335024                    out bytes 327272              

Router#

Router# show frame-relay pvc 301 64-bit


DLCI = 301, INTERFACE = Serial6/0/3:0

  input pkts 510                     output pkts 508                 

  in bytes 52690                     out bytes 52622               

Router#

Router# show frame-relay pvc 302 64-bit


DLCI = 302, INTERFACE = Serial6/0/3:0.1

  input pkts 957                     output pkts 912                 

  in bytes 283246                    out bytes 275493

The following output from an SNMP inquiry shows that the 64-bit interface MIB counters include the subinterfaces configured above: 

ifHCInOctets.5 = 0x000000000

ifHCInOctets.16 = 0x000000000

ifHCInOctets.17 = 0x00337a158

ifHCInOctets.18 = 0x000000000

ifHCInOctets.19 = 0x000000000

ifHCInOctets.20 = 0x000000000

ifHCInOctets.24 = 0x000000000

ifHCInOctets.25 = 0x000000000

ifHCInOctets.36 = 0x000051cb0 !! This is serial subinterface 6/0/2:0.1

ifHCInOctets.37 = 0x00004526e !! This is serial subinterface 6/0/3:0.1

Command Reference

This section documents modified commands only.

•frame-relay ifmib-counter64

•show frame-relay pvc

frame-relay ifmib-counter64

To include Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps in 64-bit interface MIB counter statistics, use the frame-relay ifmib-counter64 command in interface configuration mode. To exclude slower Frame Relay interfaces and subinterfaces from interface MIB counters, use the no form of this command.

frame-relay ifmib-counter64 [if | subif]

no frame-relay ifmib-counter64 [if | subif]

Syntax Description

if

(Optional) Enables Frame Relay interfaces and subinterfaces to be included in the 64-bit interface MIB counters.

subif

(Optional) Enables Frame Relay subinterfaces only to be included in the 64-bit interface MIB counters.


Command Default

Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps are not included in interface MIB counters.

Command Modes

Interface configuration

Command History

Release
Modification

12.0(21)S

This command was introduced.

12.3(10)

This command was integrated into Cisco IOS Release 12.3(10).

12.3(11)T

This command was integrated into Cisco IOS Release 12.3(11)T.

12.2(18)SXE

This command was integrated into Cisco IOS Release 12.2(18)SXE.


Usage Guidelines

The frame-relay ifmib-counter64 command allows Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps to be included in the following 64-bit interface MIB counters:

•ifHCinOctets

•ifHCOutOctets

•ifHCinUcastPkts

•ifHCOutUcastPkts

Entering the frame-relay ifmib-counter64 command with no keyword produces the same result as entering the frame-relay ifmib-counter64 command with the if keyword.

Examples

frame-relay ifmib-counter64 Command with the if Keyword: Example

In the following example, the frame-relay ifmib-counter64 command is used with the if keyword to enable serial interfaces 6/0/1:0, 6/0/2:0, and 6/0/3:0 and related subinterfaces to be counted by the 64-bit interface MIB counters. The example also shows the corresponding statistics for the 64-bit interface MIB counters. 

interface Serial6/0/1:0

 ip address 1.1.1.1 255.255.255.0

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 frame-relay interface-dlci 101

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 if 


interface Serial6/0/2:0

 no ip address

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 if 

!

interface Serial6/0/2:0.1 point-to-point  

 ip address 2.1.1.1 255.255.255.0  

 no ip route-cache

 frame-relay interface-dlci 201 

!

interface Serial6/0/3:0

 ip address 3.1.1.1 255.255.255.0

 encapsulation frame-relay

 frame-relay interface-dlci 301

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 if 


interface Serial6/0/3:0.1 point-to-point  

 ip address 3.1.2.1 255.255.255.0

 frame-relay interface-dlci 302

The following output from an SNMP inquiry shows that the 64-bit interface MIB counters include the interfaces configured above: 

ifHCInOctets.5 = 0x000000000

ifHCInOctets.16 = 0x000000000

ifHCInOctets.17 = 0x003360d33

ifHCInOctets.18 = 0x000000000

ifHCInOctets.19 = 0x000000000

ifHCInOctets.20 = 0x000000000

ifHCInOctets.24 = 0x000000000

ifHCInOctets.25 = 0x000000000

ifHCInOctets.26 = 0x0001a7afc !! Serial6/0/1:0

ifHCInOctets.28 = 0x0001a7370 !! Serial6/0/2:0

ifHCInOctets.34 = 0x00006a45a !! Serial6/0/3:0

ifHCInOctets.36 = 0x000051cb0 !! Serial6/0/2:0.1

ifHCInOctets.37 = 0x00004526e !! Serial6/0/3:0.1

frame-relay ifmib-counter64 Command with the subif Keyword: Example

In the following example, the frame-relay ifmib-counter64 command is used with the subif keyword to enable the subinterfaces that are associated with serial interfaces 6/0/1:0, 6/0/2:0, and 6/0/3:0 to be counted by the 64-bit interface MIB counters. The example also shows the corresponding statistics for the 64-bit interface MIB counters. 

interface Serial6/0/1:0

 ip address 1.1.1.1 255.255.255.0

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 frame-relay interface-dlci 101

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 subif 

end


interface Serial6/0/2:0

 no ip address

 encapsulation frame-relay

 no ip route-cache cef

 no ip route-cache

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 subif 


interface Serial6/0/2:0.1 point-to-point  

 ip address 2.1.1.1 255.255.255.0  

 no ip route-cache

 frame-relay interface-dlci 201 

!

interface Serial6/0/3:0

 ip address 3.1.1.1 255.255.255.0

 encapsulation frame-relay

 frame-relay interface-dlci 301

 no frame-relay inverse-arp

 frame-relay ifmib-counter64 subif 


interface Serial6/0/3:0.1 point-to-point  

 ip address 3.1.2.1 255.255.255.0

 frame-relay interface-dlci 302

The following output from an SNMP inquiry shows that the 64-bit interface MIB counters include the subinterfaces configured above: 

ifHCInOctets.5 = 0x000000000

ifHCInOctets.16 = 0x000000000

ifHCInOctets.17 = 0x00337a158

ifHCInOctets.18 = 0x000000000

ifHCInOctets.19 = 0x000000000

ifHCInOctets.20 = 0x000000000

ifHCInOctets.24 = 0x000000000

ifHCInOctets.25 = 0x000000000

ifHCInOctets.36 = 0x000051cb0 !! Serial6/0/2:0.1

ifHCInOctets.37 = 0x00004526e !! Serial6/0/3:0.1

Related Commands

Command
Description

show frame-relay pvc

Displays statistics about permanent virtual circuits (PVCs) for Frame Relay interfaces.


show frame-relay pvc

To display statistics about permanent virtual circuits (PVCs) for Frame Relay interfaces, use the show frame-relay pvc privileged EXEC command.

show frame-relay pvc [interface interface] [dlci] [64-bit]

Syntax Description

interface

(Optional) Indicates a specific interface for which PVC information will be displayed.

interface

(Optional) Interface number containing the data-link connection identifiers (DLCIs) for which you wish to display PVC information.

dlci

(Optional) A specific DLCI number used on the interface. Statistics for the specified PVC are displayed when a DLCI is also specified.

64-bit

(Optional) Displays 64-bit counter statistics.


Command Modes

Privileged EXEC

Command History

Release
Modification

10.0

This command was introduced.

12.0(1)T

This command was modified to display statistics about virtual access interfaces used for PPP connections over Frame Relay.

12.0(3)XG

This command was modified to include the fragmentation type and size associated with a particular PVC when fragmentation is enabled on the PVC.

12.0(4)T

This command was modified to include the fragmentation type and size associated with a particular PVC when fragmentation is enabled on the PVC.

12.0(5)T

This command was modified to include information on the special voice queue that is created using the queue keyword of the frame-relay voice bandwidth command.

12.1(2)T

This command was modified to display the following information:

•Details about the policy map attached to a specific PVC.

•The priority configured for PVCs within Frame Relay PIPQ.

•Details about Frame Relay traffic shaping and policing on switched PVCs.

12.0(12)S

This command was modified to display reasons for packet drops and complete status information for switched NNI PVCs.

12.1(5)T

This command was modified to display the following information:

•The number of packets in the post-hardware-compression queue.

•The reasons for packet drops and complete status information for switched NNI PVCs.

12.2(4)T

The 64-bit keyword was added.


Usage Guidelines

Use this command to monitor the PPP link control protocol (LCP) state as being open with an "up" state, or closed with a "down" state.

When "vofr" or "vofr cisco" has been configured on the PVC, and a voice bandwidth has been allocated to the class associated with this PVC, configured voice bandwidth and used voice bandwidth are also displayed.

Statistics Reporting

To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.

To obtain statistics about a PVC that include policy-map configuration or the priority configured for that PVC, use this command with the dlci argument.

Per-VC counters are not incremented at all when either autonomous or silicon switching engine (SSE) switching is configured; therefore, PVC values will be inaccurate if either switching method is used.

Traffic Shaping

Congestion control mechanisms are currently not supported on terminated PVCs nor on PVCs over ISDN. Where congestion control mechanisms are supported, the switch passes forward explicit congestion notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligible (DE) bits unchanged from entry to exit points in the network.

Examples

The various displays in this section show sample output for a variety of PVCs. Some of the PVCs carry data only; some carry a combination of voice and data.

Frame Relay 64-Bit Counter Example

The following sample output displays the Frame Relay 64-bit counters: 

Router# show frame-relay pvc 35 64-bit


DLCI = 35, INTERFACE = Serial0/0

  input pkts 0                       output pkts 0

  in bytes 0                         out bytes 0

Frame Relay Fragmentation and Hardware Compression Example

The following is sample output for the show frame-relay pvc command for a PVC configured with Cisco-proprietary fragmentation and hardware compression: 

Router# show frame-relay pvc 110


PVC Statistics for interface Serial0/0 (Frame Relay DTE)


DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0/0


  input pkts 409           output pkts 409          in bytes 3752      

  out bytes 4560           dropped pkts 1           in FECN pkts 0         

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0         

  in DE pkts 0             out DE pkts 0         

  out bcast pkts 0          out bcast bytes 0         

  pvc create time 3d00h, last time pvc status changed 2d22h

  Service type VoFR-cisco

   Voice Queueing Stats: 0/100/0 (size/max/dropped)

  Post h/w compression queue: 0

  Current fair queue configuration:

   Discard     Dynamic      Reserved

   threshold   queue count  queue count

   64          16           2    

  Output queue size 0/max total 600/drops 0

  configured voice bandwidth 16000, used voice bandwidth 0

  fragment type VoFR-cisco         fragment size 100

  cir 64000     bc   640       be 0         limit 80     interval 10  

  mincir 32000     byte increment 80    BECN response no 

  frags 428       bytes 4810      frags delayed 24        bytes delayed 770      

  shaping inactive    

  traffic shaping drops 0

  ip rtp priority parameters 16000 32000 20000

Switched PVC Example

The following is sample output from the show frame-relay pvc command for a switched Frame Relay PVC. This output displays detailed information about NNI status and why packets were dropped from switched PVCs. 

Router# show frame-relay pvc


 PVC Statistics for interface Serial2/2 (Frame Relay NNI) 


 DLCI = 16, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE = Serial2/2 

 LOCAL PVC STATUS = INACTIVE, NNI PVC STATUS = INACTIVE


   input pkts 0             output pkts 0            in bytes 0 

   out bytes 0              dropped pkts 0           in FECN pkts 0 

   in BECN pkts 0           out FECN pkts 0          out BECN pkts 0 

   in DE pkts 0             out DE pkts 0 

   out bcast pkts 0         out bcast bytes 0 

   switched pkts0 

   Detailed packet drop counters: 

   no out intf 0            out intf down 0          no out PVC 0 

   in PVC down 0            out PVC down 0           pkt too big 0 

   shaping Q full 0         pkt above DE 0           policing drop 0 

   pvc create time 00:00:07, last time pvc status changed 00:00:07

Frame Relay Congestion Management on a Switched PVC Example

The following is sample output from the show frame-relay pvc command that shows the statistics for a switched PVC on which Frame Relay congestion management is configured: 

Router# show frame-relay pvc 200

PVC Statistics for interface Serial3/0 (Frame Relay DTE)

DLCI = 200, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial3/0


  input pkts 341           output pkts 390          in bytes 341000

  out bytes 390000         dropped pkts 0           in FECN pkts 0

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0

  in DE pkts 0             out DE pkts 390

  out bcast pkts 0          out bcast bytes 0            Num Pkts Switched 341


  pvc create time 00:10:35, last time pvc status changed 00:10:06

  Congestion DE threshold 50 

  shaping active 

  cir 56000     bc 7000      be 0         byte limit 875    interval 125

  mincir 28000     byte increment 875   BECN response no

  pkts 346       bytes 346000    pkts delayed 339       bytes delayed 339000

  traffic shaping drops 0

  Queueing strategy:fifo

  Output queue 48/100, 0 drop, 339 dequeued

Frame Relay Policing on a Switched PVC Example

The following is sample output from the show frame-relay pvc command that shows the statistics for a switched PVC on which Frame Relay policing is configured: 

Router# show frame-relay pvc 100


PVC Statistics for interface Serial1/0 (Frame Relay DCE)


DLCI = 100, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial1/0  


  input pkts 1260          output pkts 0            in bytes 1260000

  out bytes 0              dropped pkts 0           in FECN pkts 0

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0

  in DE pkts 0             out DE pkts 0

  out bcast pkts 0          out bcast bytes 0            Num Pkts Switched 1260


  pvc create time 00:03:57, last time pvc status changed 00:03:19

  policing enabled, 180 pkts marked DE

  policing Bc  6000        policing Be  6000        policing Tc  125 (msec)

  in Bc pkts   1080        in Be pkts   180         in xs pkts   0

  in Bc bytes  1080000     in Be bytes  180000      in xs bytes  0

Frame Relay PVC Priority Queueing Example

The following is sample output for a PVC that has been assigned high priority: 

Router# show frame-relay pvc 100


PVC Statistics for interface Serial0 (Frame Relay DTE)


DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0

  input pkts 0             output pkts 0            in bytes 0

  out bytes 0              dropped pkts 0           in FECN pkts 0

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0

  in DE pkts 0             out DE pkts 0

  out bcast pkts 0          out bcast bytes 0

  pvc create time 00:00:59, last time pvc status changed 00:00:33

  priority high

Low Latency Queueing for Frame Relay Example

The following is sample output from the show frame-relay pvc command for a PVC shaped to a 64K committed information rate (CIR) with fragmentation. A policy map is attached to the PVC and is configured with a priority class for voice, two data classes for IP precedence traffic, and a default class for best-effort traffic. Weighted Random Early Detection (WRED) is used as the drop policy on one of the data classes. 

Router# show frame-relay pvc 100


PVC Statistics for interface Serial1/0 (Frame Relay DTE)


DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial1/0.1


  input pkts 0             output pkts 0            in bytes 0         

  out bytes 0              dropped pkts 0           in FECN pkts 0         

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0         

  in DE pkts 0             out DE pkts 0         

  out bcast pkts 0          out bcast bytes 0         

  pvc create time 00:00:42, last time pvc status changed 00:00:42

  service policy mypolicy

 Class voice

  Weighted Fair Queueing

      Strict Priority

      Output Queue: Conversation 72 

        Bandwidth 16 (kbps) Packets Matched 0

        (pkts discards/bytes discards) 0/0

 Class immediate-data

  Weighted Fair Queueing

      Output Queue: Conversation 73 

        Bandwidth 60 (%) Packets Matched 0

        (pkts discards/bytes discards/tail drops) 0/0/0

        mean queue depth: 0

        drops: class  random   tail     min-th   max-th   mark-prob 

               0      0        0        64       128      1/10

               1      0        0        71       128      1/10

               2      0        0        78       128      1/10

               3      0        0        85       128      1/10

               4      0        0        92       128      1/10

               5      0        0        99       128      1/10

               6      0        0        106      128      1/10

               7      0        0        113      128      1/10

               rsvp   0        0        120      128      1/10

 Class priority-data

  Weighted Fair Queueing

      Output Queue: Conversation 74 

        Bandwidth 40 (%) Packets Matched 0 Max Threshold 64 (packets)

        (pkts discards/bytes discards/tail drops) 0/0/0

 Class class-default

  Weighted Fair Queueing

      Flow Based Fair Queueing

      Maximum Number of Hashed Queues 64  Max Threshold 20 (packets)

  Output queue size 0/max total 600/drops 0

  fragment type end-to-end         fragment size 50

  cir 64000     bc   640       be 0         limit 80     interval 10  

  mincir 64000     byte increment 80    BECN response no 

  frags 0         bytes 0         frags delayed 0         bytes delayed 0        

  shaping inactive    

  traffic shaping drops 0

PPP over Frame Relay Example

The following is sample output from the show frame-relay pvc command that shows the PVC statistics for serial interface 5 (slot 1 and DLCI 55 are up) during a PPP session over Frame Relay: 

Router# show frame-relay pvc 55


PVC Statistics for interface Serial5/1 (Frame Relay DTE)

DLCI = 55, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial5/1.1

     input pkts 9             output pkts 16           in bytes 154

     out bytes 338            dropped pkts 6           in FECN pkts 0

     in BECN pkts 0           out FECN pkts 0          out BECN pkts 0

     in DE pkts 0             out DE pkts 0

     out bcast pkts 0         out bcast bytes 0

     pvc create time 00:35:11, last time pvc status changed 00:00:22

     Bound to Virtual-Access1 (up, cloned from Virtual-Template5)

Voice over Frame Relay Example

The following is sample output from the show frame-relay pvc command for a PVC carrying Voice over Frame Relay (VoFR) traffic configured via the vofr cisco command. The frame-relay voice bandwidth command has been configured on the class associated with this PVC, as has fragmentation. The fragmentation employed is proprietary to Cisco.

A sample configuration for this scenario is shown first, followed by the output for the show frame-relay pvc command. 

interface serial 0

 encapsulation frame-relay

 frame-relay traffic-shaping

 frame-relay interface-dlci 108

  vofr cisco

  class vofr-class

map-class frame-relay vofr-class

 frame-relay fragment 100

 frame-relay fair-queue

 frame-relay cir 64000

 frame-relay voice bandwidth 25000


Router# show frame-relay pvc 108


PVC Statistics for interface Serial0 (Frame Relay DTE)

DLCI = 108, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0

  input pkts 1260          output pkts 1271         in bytes 95671     

  out bytes 98604          dropped pkts 0           in FECN pkts 0         

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0         

  in DE pkts 0             out DE pkts 0         

  out bcast pkts 1271       out bcast bytes 98604     

  pvc create time 09:43:17, last time pvc status changed 09:43:17

  Service type VoFR-cisco

  configured voice bandwidth 25000, used voice bandwidth 0

  voice reserved queues 24, 25

  fragment type VoFR-cisco         fragment size 100

  cir 64000     bc 64000     be 0         limit 1000   interval 125 

  mincir 32000     byte increment 1000  BECN response no 

  pkts 2592      bytes 205140    pkts delayed 1296      bytes delayed 102570   

  shaping inactive    

  shaping drops 0

  Current fair queue configuration:

   Discard     Dynamic      Reserved

   threshold   queue count  queue count

    64          16           2    

  Output queue size 0/max total 600/drops 0

FRF.12 Fragmentation Example

The following is sample output from the show frame-relay pvc command for an application employing pure FRF.12 fragmentation. A sample configuration for this scenario is shown first, followed by the output for the show frame-relay pvc command. 

interface serial 0

 encapsulation frame-relay

 frame-relay traffic-shaping

 frame-relay interface-dlci 110

  class frag

map-class frame-relay frag

 frame-relay fragment 100

 frame-relay fair-queue

 frame-relay cir 64000


Router# show frame-relay pvc 110


PVC Statistics for interface Serial0 (Frame Relay DTE)

DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0

  input pkts 0             output pkts 243          in bytes 0         

  out bytes 7290           dropped pkts 0           in FECN pkts 0         

  in BECN pkts 0           out FECN pkts 0          out BECN pkts 0         

  in DE pkts 0             out DE pkts 0         

  out bcast pkts 243        out bcast bytes 7290      

  pvc create time 04:03:17, last time pvc status changed 04:03:18

  fragment type end-to-end         fragment size 100

  cir 64000     bc 64000     be 0         limit 1000   interval 125 

  mincir 32000     byte increment 1000  BECN response no 

  pkts 486       bytes 14580     pkts delayed 243       bytes delayed 7290     

  shaping inactive    

  shaping drops 0

  Current fair queue configuration:

   Discard     Dynamic      Reserved

   threshold   queue count  queue count

   64          16           2    

  Output queue size 0/max total 600/drops 0

Note that when voice is not configured, voice bandwidth output is not displayed.

Multipoint Subinterfaces Transporting Data

The following is sample output from the show frame-relay pvc command for multipoint subinterfaces carrying data only. 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. Note that neither fragmentation nor voice is configured on this PVC. 

Router# show frame-relay pvc


DLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103

input pkts 10  output pkts 7  in bytes 6222 

out bytes 6034  dropped pkts 0  in FECN pkts 0 

in BECN pkts 0  out FECN pkts 0  out BECN pkts 0 

in DE pkts 0  out DE pkts 0         

outbcast pkts 0  outbcast bytes 0

pvc create time 0:13:11  last time pvc status changed 0:11:46

DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104

input pkts 20  output pkts 8  in bytes 5624 

out bytes 5222  dropped pkts 0  in FECN pkts 0 

in BECN pkts 0  out FECN pkts 0  out BECN pkts 0 

in DE pkts 0  out DE pkts 0         

outbcast pkts 0  outbcast bytes 0

pvc create time 0:03:57  last time pvc status changed 0:03:48

PVC Transporting Voice and Data

The following is sample output from the show frame-relay pvc command for a PVC carrying voice and data traffic, with a special queue specifically for voice traffic created using the frame-relay voice bandwidth command queue keyword: 

Router# show frame-relay pvc interface serial 1 45

 PVC Statistics for interface Serial1 (Frame Relay DTE)

 DLCI = 45, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1

   input pkts 85            output pkts 289          in bytes 1730      

   out bytes 6580           dropped pkts 11          in FECN pkts 0         

   in BECN pkts 0           out FECN pkts 0          out BECN pkts 0         

   in DE pkts 0             out DE pkts 0         

   out bcast pkts 0          out bcast bytes 0         

   pvc create time 00:02:09, last time pvc status changed 00:02:09

   Service type VoFR

   configured voice bandwidth 25000, used voice bandwidth 22000

   fragment type VoFR         fragment size 100

   cir 20000     bc   1000      be 0         limit 125    interval 50  

   mincir 20000     byte increment 125   BECN response no 

   fragments 290       bytes 6613      fragments delayed 1         bytes delayed 33       

   shaping inactive    

   traffic shaping drops 0

    Voice Queueing Stats: 0/100/0 (size/max/dropped)

   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Current fair queue configuration:

    Discard     Dynamic      Reserved

    threshold   queue count  queue count

    64          16           2    

   Output queue size 0/max total 600/drops 0

Table 1 provides a listing of the fields in these displays and a description of each field.

Table 1 show frame-relay pvc Field Descriptions 

Field
Description

DLCI

One of the DLCI numbers for the PVC.

DLCI USAGE

Lists SWITCHED when the router or access server is used as a switch, or LOCAL when the router or access server is used as a DTE device.

PVC STATUS

Status of the PVC: ACTIVE, INACTIVE, or DELETED.

INTERFACE

Specific subinterface associated with this DLCI.

LOCAL PVC STATUS1

Status of PVC configured locally on the NNI interface.

NNI PVC STATUS1

Status of PVC learned over the NNI link.

input pkts

Number of packets received on this PVC.

output pkts

Number of packets sent on this PVC.

in bytes

Number of bytes received on this PVC.

out bytes

Number of bytes sent on this PVC.

dropped pkts

Number of incoming and outgoing packets dropped by the router at the Frame Relay level.

in FECN pkts

Number of packets received with the FECN bit set.

in BECN pkts

Number of packets received with the BECN bit set.

out FECN pkts

Number of packets sent with the FECN bit set.

out BECN pkts

Number of packets sent with the BECN bit set.

in DE pkts

Number of DE packets received.

out DE pkts

Number of DE packets sent.

out bcast pkts

Number of output broadcast packets.

out bcast bytes

Number of output broadcast bytes.

switched pkts

Number of switched packets.

no out intf2

Number of packets dropped because there is no output interface.

out intf down2

Number of packets dropped because the output interface is down.

no out PVC2

Number of packets dropped because the outgoing PVC is not configured.

in PVC down2

Number of packets dropped because the incoming PVC is inactive.

out PVC down2

Number of packets dropped because the outgoing PVC is inactive.

pkt too big2

Number of packets dropped because the packet size is greater than media MTU3 .

shaping Q full2

Number of packets dropped because the Frame Relay traffic shaping queue is full.

pkt above DE2

Number of packets dropped because they are above the DE level when Frame Relay congestion management is enabled.

policing drop2

Number of packets dropped because of Frame Relay traffic policing.

pvc create time

Time at which the PVC was created.

last time pvc status changed

Time at which the PVC changed status.

priority

Priority assigned to the PVC.

pkts marked DE

Number of packets marked DE because they exceeded the Bc.

policing Bc

Committed burst size.

policing Be

Excess burst size.

policing Tc

Measurement interval for counting Bc and Be.

in Bc pkts

Number of packets received within the committed burst.

in Be pkts

Number of packets received within the excess burst.

in xs pkts

Number of packets dropped because they exceeded the combined burst.

in Bc bytes

Number of bytes received within the committed burst.

in Be bytes

Number of bytes received within the excess burst.

in xs bytes

Number of bytes dropped because they exceeded the combined burst.

Congestion DE threshold

PVC queue percentage at which packets with the DE bit are dropped.

Congestion ECN threshold

PVC queue percentage at which packets are set with the BECN and FECN bits.

Service type

Type of service performed by this PVC. Can be VoFR or VoFR-cisco.

Post h/w compression queue

Number of packets in the post-hardware-compression queue when hardware compression and Frame Relay fragmentation are configured.

configured voice bandwidth

Amount of bandwidth in bits per second (bps) reserved for voice traffic on this PVC.

used voice bandwidth

Amount of bandwidth in bps currently being used for voice traffic.

voice reserved queues

Queue numbers reserved for voice traffic on this PVC. This field was removed in Cisco IOS Release 12.0(5)T.

service policy

Name of the output service policy applied to the VC.

Class

Class of traffic being displayed. Output is displayed for each configured class in the policy.

Output Queue

The WFQ4 conversation to which this class of traffic is allocated.

Bandwidth

Bandwidth in kbps or percentage configured for this class.

Packets Matched

Number of packets that matched this class.

Max Threshold

Maximum queue size for this class when WRED is not used.

pkts discards

Number of packets discarded for this class.

bytes discards

Number of bytes discarded for this class.

tail drops

Number of packets discarded for this class because the queue was full.

mean queue depth

Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a moving average. The minimum and maximum thresholds are compared against this value to determine drop decisions.

drops:

WRED parameters.

class

IP precedence value.

random

Number of packets randomly dropped when the mean queue depth is between the minimum threshold value and the maximum threshold value for the specified IP precedence value.

tail

Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence value.

min-th

Minimum WRED threshold in number of packets.

max-th

Maximum WRED threshold in number of packets.

mark-prob

Fraction of packets dropped when the average queue depth is at the maximum threshold.

Maximum Number of Hashed Queues

(Applies to class default only) Number of queues available for unclassified flows.

fragment type

Type of fragmentation configured for this PVC. Possible types are:

end-to-end—Fragmented packets contain the standard FRF.12 header

VoFR—Fragmented packets contain the FRF.11 Annex C header

VoFR-cisco—Fragmented packets contain the Cisco proprietary header

fragment size

Size of the fragment payload in bytes.

cir

Current CIR in bps.

bc

Current Committed Burst (Bc) size in bits.

be

Current Excess Burst (Be) size in bits.

limit

Maximum number of bytes sent per internal interval (excess plus sustained).

interval

Interval being used internally (may be smaller than the interval derived from Bc/CIR; this happens when the router determines that traffic flow will be more stable with a smaller configured interval).

mincir

Minimum CIR for the PVC.

byte increment

Number of bytes that will be sustained per internal interval.

BECN response

Indication that Frame Relay has BECN adaptation configured.

pkts

Number of packets associated with this PVC that have gone through the traffic-shaping system.

frags

Total number of fragments shaped on this VC.

bytes

Number of bytes associated with this PVC that have gone through the traffic-shaping system.

pkts delayed

Number of packets associated with this PVC that have been delayed by the traffic-shaping system.

frags delayed

Number of fragments delayed in the shaping queue before being sent.

bytes delayed

Number of bytes associated with this PVC that have been delayed by the traffic-shaping system.

shaping

Indication that shaping will be active for all PVCs that are fragmenting data; otherwise, shaping will be active if the traffic being sent exceeds the CIR for this circuit.

shaping drops

Number of packets dropped by the traffic-shaping process.

Voice Queueing Stats

Statistics showing the size of packets, the maximum number of packets, and the number of packets dropped in the special voice queue created using the frame-relay voice bandwidth command queue keyword.

Discard threshold

Maximum number of packets that can be stored in each packet queue. Additional packets received after a queue is full will be discarded.

Dynamic queue count

Number of packet queues reserved for best-effort traffic.

Reserved queue count

Number of packet queues reserved for voice traffic.

Output queue size

Size in bytes of each output queue.

max total

Maximum number of packets of all types that can be queued in all queues.

drops

Number of frames dropped by all output queues.

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.

3 MTU = maximum transmission unit

4 WFQ = weighted fair queueing.


Related Commands

Command
Description

frame-relay interface-queue priority

Enables FR PIPQ on a Frame Relay interface and assigns priority to a PVC within a Frame Relay map class.

frame-relay pvc

Configures Frame Relay PVCs for FRF.8 Frame Relay-ATM Service Interworking.

service-policy

Attaches a policy map to an input interface or VC, or an output interface or VC, to be used as the service policy for that interface or VC.

show dial-peer voice

Displays configuration information and call statistics for dial peers.

show frame-relay fragment

Displays Frame Relay fragmentation details.

show frame-relay vofr

Displays details about FRF.11 subchannels being used on VoFR DLCIs.

show interfaces serial

Displays information about a serial interface.

show policy-map interface

Displays the configuration of classes configured for service policies on the specified interface or PVC.

show traffic-shape queue

Displays information about the elements queued at a particular time at the VC (DLCI) level.