Guest

Cisco IOS Software Releases 12.2 SB

Frame Relay Show Command and Debug Command Enhancements

Hierarchical Navigation

Downloads

Table Of Contents

Frame Relay show Command and debug Command Enhancements

Contents

Information About Frame Relay show Command and debug Command Enhancements

Overview of the Frame Relay show Command and debug Command Enhancements

Benefits of the Frame Relay Show Command and Debug Command Enhancements

Additional References

Related Documents

MIBs

Technical Assistance

Command Reference

show frame-relay ip rtp header-compression

show frame-relay ip tcp header-compression

show frame-relay map

show frame-relay pvc


Frame Relay show Command and debug Command Enhancements

First Published: September 12, 2005
Last Updated: June 19, 2006

The Frame Relay show Command and debug Command Enhancements feature provides the ability to filter the output of certain Frame Relay show and debug commands on the basis of the interface and data-link connection identifier (DLCI). These enhancements facilitate network scalability and simplify network management and troubleshooting.

History for the Frame Relay show Command and debug Command Enhancements Feature

Release
Modification

12.2(27)SBC

This feature was introduced.

12.4(9)T

This feature was integrated into Cisco IOS Release 12.4(9)T.


Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

• Information About Frame Relay show Command and debug Command Enhancements

• Additional References

• Command Reference

Information About Frame Relay show Command and debug Command Enhancements

This section contains the following concepts:

• Overview of the Frame Relay show Command and debug Command Enhancements

• Benefits of the Frame Relay Show Command and Debug Command Enhancements

Overview of the Frame Relay show Command and debug Command Enhancements

This feature introduces the following enhancments:

•The show frame-relay map command has been enhanced to allow map information to be displayed for specific interfaces and DLCIs.

•The show frame-relay ip tcp header-compression and show frame-relay ip rtp header-compression commands have been enhanced to allow header-compression information to be displayed for specific DLCIs.

•The summary keyword was added to the show frame-relay pvc command, allowing a summary of all PVCs on the system to be displayed.

•Conditional debugging support, which allows debug output to be filtered on the basis of interface and DLCI, was introduced for the following commands:

–debug frame-relay end-to-end

–debug frame-relay events

–debug frame-relay fragment

–debug frame-relay fragment event

–debug frame-relay ip

–debug frame-relay ppp

–debug frame-relay verbose

Note Conditional debugging for Frame Relay debug commands is configured by using the debug condition command.

Benefits of the Frame Relay Show Command and Debug Command Enhancements

The Frame Relay show Command and debug Command Enhancements allow the output for some Frame Relay show commands and debug commands to be filtered on the basis of interface and DLCI. This enhancement saves network administrators time and frustration by eliminating the need to look through a large amount of output for information about a specific interface or DLCI. These enhancements can also reduce the amount of CPU processing time that is required to generate large amounts of show and debug output.

Additional References

The following sections provide references related to the Frame Relay show Command and debug Command Enhancements feature.

Related Documents

Related Topic
Document Title

Frame Relay configuration tasks

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

Frame Relay commands

Cisco IOS Wide-Area Networking Command Reference, Release 12.4T

debug commands

Cisco IOS Debug Command Reference, Release 12.4T


MIBs

MIB
MIBs Link

None

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

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


Technical Assistance

Description
Link

The Cisco Technical Support & Documentation website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport


Command Reference

This section documents modified commands only.

• show frame-relay ip rtp header-compression

• show frame-relay ip tcp header-compression

• show frame-relay map

• show frame-relay pvc

show frame-relay ip rtp header-compression

To display Frame Relay Real-Time Transport Protocol (RTP) header compression statistics, use the show frame-relay ip rtp header-compression command in user EXEC or privileged EXEC mode.

show frame-relay ip rtp header-compression [interface type number] [dlci]

Syntax Description

interface type number

(Optional) Specifies an interface for which information will be displayed. A space between the type and number is optional.

dlci

(Optional) Specifies a data-link connection identifier (DLCI) for which information will be displayed. Range is from 16 to 1022.


Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

11.3

This command was introduced.

12.2(13)T

This command was modified to support display of RTP header compression statistics for Frame Relay permanent virtual circuit (PVC) bundles.

12.2(27)SBC

This command was integrated into Cisco IOS Release 12.2(27)SBC, and the dlci argument was added.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.4(9)T

The dlci argument was added.


Examples

The following is sample output from the show frame-relay ip rtp header-compression command: 

Router# show frame-relay ip rtp header-compression


 DLCI 21         Link/Destination info: ip 10.1.4.1

  Interface Serial3/0 DLCI 21 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 20         Link/Destination info: ip 10.1.1.1

  Interface Serial3/1 DLCI 20 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 21         Link/Destination info: ip 10.1.2.1

  Interface Serial3/1 DLCI 21 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 22         Link/Destination info: ip 10.1.3.1

  Interface Serial3/1 DLCI 22 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts

In the following example, the show frame-relay ip rtp header-compression command displays information about DLCI 21: 

Router# show frame-relay ip rtp header-compression 21


 DLCI 21         Link/Destination info: ip 10.1.4.1

  Interface Serial3/0 DLCI 21 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 21         Link/Destination info: ip 10.1.2.1

  Interface Serial3/1 DLCI 21 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts

In the following example, the show frame-relay ip rtp header-compression command displays information for all DLCIs on serial interface 3/1: 

Router# show frame-relay ip rtp header-compression interface serial3/1


 DLCI 20         Link/Destination info: ip 10.1.1.1

  Interface Serial3/1 DLCI 20 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 21         Link/Destination info: ip 10.1.2.1

  Interface Serial3/1 DLCI 21 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 22         Link/Destination info: ip 10.1.3.1

  Interface Serial3/1 DLCI 22 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts

In the following example, the show frame-relay ip rtp header-compression command displays information for only DLCI 21 on serial interface 3/1: 

Router# show frame-relay ip rtp header-compression interface serial3/1 21


 DLCI 21         Link/Destination info: ip 10.1.2.1

  Interface Serial3/1 DLCI 21 (compression on, Cisco)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts

The following sample output from the show frame-relay ip rtp header-compression command shows statistics for a PVC bundle called MP-3-static: 

Router# show frame-relay ip rtp header-compression interface Serial1/4


 vc-bundle MP-3-static      Link/Destination info:ip 10.1.1.1

  Interface Serial1/4:

    Rcvd:   14 total, 13 compressed, 0 errors

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:   15 total, 14 compressed,

             474 bytes saved, 119 bytes sent

             4.98 efficiency improvement factor

    Connect:256 rx slots, 256 tx slots,

             1 long searches, 1 misses 0 collisions, 0 negative cache hits

             93% hit ratio, five minute miss rate 0 misses/sec, 0 max

Table 1 describes the significant fields shown in the display.

Table 1 show frame-relay ip rtp header-compression Field Descriptions 

Field
Description

Interface Serial0

Type and number of the interface.

Rcvd:

Table of details concerning received packets.

total

Number of packets received on the interface.

compressed

Number of packets with compressed header.

errors

Number of errors.

dropped

Number of dropped packets.

buffer copies

Number of buffers that were copied.

buffer failures

Number of failures in allocating buffers.

Sent:

Table of details concerning sent packets.

total

Total number of packets sent.

compressed

Number of packets sent with compressed header.

bytes saved

Total savings in bytes due to compression.

bytes sent

Total bytes sent after compression.

efficiency improvement factor

Compression efficiency.

Connect:

Table of details about the connections.

rx slots

Total number of receive slots.

tx slots

Total number of transmit slots.

long searches

Searches that needed more than one lookup.

misses

Number of new states that were created.

hit ratio

Number of times existing states were revised.

five minute miss rate

Average miss rate.

max

Maximum miss rate.


Related Commands

Command
Description

frame-relay ip rtp compression-connections

Specifies the maximum number of RTP header compression connections on a Frame Relay interface.

frame-relay ip rtp header-compression

Enables RTP header compression for all Frame Relay maps on a physical interface.

frame-relay map ip compress

Enables both RTP and TCP header compression on a link.

frame-relay map ip nocompress

Disables both RTP and TCP header compression on a link.

frame-relay map ip rtp header-compression

Enables RTP header compression per DLCI.

show ip rpf events

Displays RTP header compression statistics.


show frame-relay ip tcp header-compression

To display Frame Relay Transmission Control Protocol (TCP)/IP header compression statistics, use the show frame-relay ip tcp header-compression command in user EXEC or privileged EXEC mode.

show frame-relay ip tcp header-compression [interface type number] [dlci]

Syntax Description

interface type number

(Optional) Specifies an interface for which information will be displayed. A space is optional between the type and number.

dlci

(Optional) Specifies a data-link connection identifier (DLCI) for which information will be displayed. Range is from 16 to 1022.


Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

10.3

This command was introduced.

12.2(13)T

This command was modified to support display of TCP/IP header compression statistics for Frame Relay permanent virtual circuit (PVC) bundles.

12.2(27)SBC

This command was integrated into Cisco IOS Release 12.2(27)SBC, and the dlci argument was added.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.4(9)T

The dlci argument was added.


Examples

The following is sample output from the show frame-relay ip tcp header-compression command: 

Router# show frame-relay ip tcp header-compression


DLCI 200          Link/Destination info: ip 10.108.177.200

Interface Serial0:

Rcvd:     40 total, 36 compressed, 0 errors

          0 dropped, 0 buffer copies, 0 buffer failures

Sent:     0 total, 0 compressed

          0 bytes saved, 0 bytes sent

Connect:  16 rx slots, 16 tx slots, 0 long searches, 0 misses, 0% hit ratio

          Five minute miss rate 0 misses/sec, 0 max misses/sec

The following sample output from the show frame-relay ip tcp header-compression command shows statistics for a PVC bundle called "MP-3-static": 

Router# show frame-relay ip tcp header-compression interface Serial1/4


 vc-bundle MP-3-static      Link/Destination info:ip 10.1.1.1

  Interface Serial1/4:

    Rcvd:   14 total, 13 compressed, 0 errors

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:   15 total, 14 compressed,

             474 bytes saved, 119 bytes sent

             4.98 efficiency improvement factor

    Connect:256 rx slots, 256 tx slots,

             1 long searches, 1 misses 0 collisions, 0 negative cache hits

             93% hit ratio, five minute miss rate 0 misses/sec, 0 max

In the following example, the show frame-relay ip tcp header-compression command displays information about DLCI 21: 

Router# show frame-relay ip tcp header-compression 21


DLCI 21         Link/Destination info: ip 10.1.2.1

  Interface POS2/0 DLCI 21 (compression on, VJ)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts


 DLCI 21         Link/Destination info: ip 10.1.4.1

  Interface Serial3/0 DLCI 21 (compression on, VJ)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts

The following is sample output from the show frame-relay ip tcp header-compression command for a specific DLCI on a specific interface: 

Router# show frame-relay ip tcp header-compression pos2/0 21


DLCI 21         Link/Destination info: ip 10.1.2.1

  Interface POS2/0 DLCI 21 (compression on, VJ)

    Rcvd:    0 total, 0 compressed, 0 errors, 0 status msgs

             0 dropped, 0 buffer copies, 0 buffer failures

    Sent:    0 total, 0 compressed, 0 status msgs, 0 not predicted

             0 bytes saved, 0 bytes sent

    Connect: 256 rx slots, 256 tx slots, 

             0 misses, 0 collisions, 0 negative cache hits, 256 free contexts

Table 2 describes the fields shown in the display.

Table 2 show frame-relay ip tcp header-compression Field Descriptions 

Field
Description

Rcvd:

Table of details concerning received packets.

total

Sum of compressed and uncompressed packets received.

compressed

Number of compressed packets received.

errors

Number of errors caused by errors in the header fields (version, total length, or IP checksum).

dropped

Number of packets discarded. Seen only after line errors.

buffer failures

Number of times that a new buffer was needed but was not obtained.

Sent:

Table of details concerning sent packets.

total

Sum of compressed and uncompressed packets sent.

compressed

Number of compressed packets sent.

bytes saved

Number of bytes reduced because of the compression.

bytes sent

Actual number of bytes transmitted.

Connect:

Table of details about the connections.

rx slots, tx slots

Number of states allowed over one TCP connection. A state is recognized by a source address, a destination address, and an IP header length.

long searches

Number of times that the connection ID in the incoming packet was not the same as the previous one that was processed.

misses

Number of times that a matching entry was not found within the connection table and a new entry had to be entered.

hit ratio

Percentage of times that a matching entry was found in the compression tables and the header was compressed.

Five minute miss rate

Miss rate computed over the most recent 5 minutes and the maximum per-second miss rate during that period.


show frame-relay map

To display current Frame Relay map entries and information about connections, use the show frame-relay map command in privileged EXEC mode.

show frame-relay map [interface type number] [dlci]

Syntax Description

interface type number

(Optional) Specifies an interface for which mapping information will be displayed. A space is optional between the type and number.

dlci

(Optional) Specifies a data-link connection identifier (DLCI) for which mapping information will be displayed. Range: 16 to 1022.


Command Modes

Privileged EXEC

Command History

Release
Modification

10.0

This command was introduced.

12.2(2)T

The display output for this command was modified to include the IPv6 address mappings of remote nodes to Frame Relay permanent virtual circuits (PVCs).

12.0(21)ST

This command was integrated into Cisco IOS Release 12.0(21)ST.

12.0(22)S

This command was integrated into Cisco IOS Release 12.0(22)S.

12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.2(13)T

The display output for this command was modified to include information about Frame Relay PVC bundle maps.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB, the interface keyword was added, and the dlci argument was added.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(9)T

The interface keyword was added, and the dlci argument was added.


Examples

This section contains the following examples:

• Sample Router Configuration

• Display All Maps: Example

• Display Maps for a Specific DLCI: Example

• Display Maps for a Specific Interface: Example

• Display Map for a Specific DLCI on a Specific Interface: Example

• Display Maps for a Specific Subinterface: Example

• Display Maps for a Specific DLCI on a Specific Subinterface: Example

• Maps with IPV6 Addresses: Example

• Maps for VC Bundles: Example

Sample Router Configuration

This configuration example corresponds to the following examples of output for the show frame-relay map command. 

interface POS2/0

 no ip address

 encapsulation frame-relay

 frame-relay map ip 10.1.1.1 20 tcp header-compression

 frame-relay map ip 10.1.2.1 21 tcp header-compression

 frame-relay map ip 10.1.3.1 22 tcp header-compression

 frame-relay map bridge 23

 frame-relay interface-dlci 25

 frame-relay interface-dlci 26

 bridge-group 1

interface POS2/0.1 point-to-point

 frame-relay interface-dlci 24 protocol ip 10.1.4.1


interface Serial3/0

 no ip address

 encapsulation frame-relay

 serial restart-delay 0

 frame-relay map ip 172.16.3.1 20

 frame-relay map ip 172.16.4.1 21 tcp header-compression active

 frame-relay map ip 172.16.1.1 100

 frame-relay map ip 172.16.2.1 101

interface Serial3/0.1 multipoint

 frame-relay map ip 192.168.11.11 24

 frame-relay map ip 192.168.11.22 105

Display All Maps: Example 

Router# show frame-relay map


POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

POS2/0 (up): ip 10.1.2.1 dlci 21(0x15,0x450), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

POS2/0 (up): ip 10.1.3.1 dlci 22(0x16,0x460), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

POS2/0 (up): bridge dlci 23(0x17,0x470), static,

              CISCO, status deleted

POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcast

          status deleted

Serial3/0 (down): ip 172.16.3.1 dlci 20(0x14,0x440), static,

              CISCO, status deleted

Serial3/0 (down): ip 172.16.4.1 dlci 21(0x15,0x450), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

Serial3/0.1 (down): ip 192.168.11.11 dlci 24(0x18,0x480), static,

              CISCO, status deleted

Serial3/0 (down): ip 172.16.1.1 dlci 100(0x64,0x1840), static,

              CISCO, status deleted

Serial3/0 (down): ip 172.16.2.1 dlci 101(0x65,0x1850), static,

              CISCO, status deleted

Serial3/0.1 (down): ip 192.168.11.22 dlci 105(0x69,0x1890), static,

              CISCO, status deleted

Serial4/0/1:0.1 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast, CISCO

          status defined, active,

              RTP Header Compression (enabled), connections: 256

Display Maps for a Specific DLCI: Example 

Router# show frame-relay map 20


POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

Serial3/0 (down): ip 172.16.3.1 dlci 20(0x14,0x440), static,

              CISCO, status deleted

Display Maps for a Specific Interface: Example 

Router# show frame-relay map interface pos2/0


POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

POS2/0 (up): ip 10.1.2.1 dlci 21(0x15,0x450), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

POS2/0 (up): ip 10.1.3.1 dlci 22(0x16,0x460), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

POS2/0 (up): bridge dlci 23(0x17,0x470), static,

              CISCO, status deleted

POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcast

          status deleted

Display Map for a Specific DLCI on a Specific Interface: Example 

Router# show frame-relay map interface pos2/0 20


POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,

              CISCO, status deleted

              TCP/IP Header Compression (enabled), connections: 256

Display Maps for a Specific Subinterface: Example 

Router# show frame-relay map interface pos2/0.1


POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcast

          status deleted

Display Maps for a Specific DLCI on a Specific Subinterface: Example 

Router# show frame-relay map interface pos2/0.1 24


POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcast

          status deleted

Maps with IPV6 Addresses: Example

The following sample output from the show frame-relay map command shows that the link-local and global IPv6 addresses (FE80::E0:F727:E400:A and 3ffe:1111:2222:1044::73; FE80::60:3E47:AC8:8 and 3ffe:1111:2222:1044::72) of two remote nodes are explicitly mapped to data-link connection identifier (DLCI) 17 and DLCI 19, respectively. Both DLCI 17 and DLCI 19 are terminated on interface serial 3 of this node; therefore, interface serial 3 of this node is a point-to-multipoint interface. 

Router# show frame-relay map 


Serial3 (up): ipv6 FE80::E0:F727:E400:A dlci 17(0x11,0x410), static, 

              broadcast, CISCO, status defined, active 

Serial3 (up): ipv6 3ffe:1111:2222:1044::72 dlci 19(0x13,0x430), static, 

              CISCO, status defined, active 

Serial3 (up): ipv6 3ffe:1111:2222:1044::73 dlci 17(0x11,0x410), static, 

              CISCO, status defined, active 

Serial3 (up): ipv6 FE80::60:3E47:AC8:8 dlci 19(0x13,0x430), static, 

              broadcast, CISCO, status defined, active

Maps for VC Bundles: Example

The following sample output displays mapping information for two PVC bundles. The PVC bundle "MAIN-1-static" is configured with a static map. The map for PVC bundle "MAIN-2-dynamic" is created dynamically using Inverse Address Resolution Protocol (ARP). 

Router# show frame-relay map 


Serial1/4 (up): ip 10.1.1.1 vc-bundle MAIN-1-static, static, 

          CISCO, status up

Serial1/4 (up): ip 10.1.1.2 vc-bundle MAIN-2-dynamic, dynamic, 

          broadcast, status up

Table 3 describes the significant fields shown in the displays.

 

Table 3 show frame-relay map Field Descriptions  

Field
Description

Serial 1 (administratively down)

Identifies a Frame Relay interface and its status (up or down).

ip 10.108.177.177

Destination IP address.

dlci 177 (0xB1,0x2C10)

DLCI that identifies the logical connection being used to reach this interface. This value is displayed in three ways: its decimal value (177), its hexadecimal value (0xB1), and its value as it would appear on the wire (0x2C10).

vc-bundle

PVC bundle that serves as the logical connection being used to reach the interface.

static/dynamic

Indicates whether this is a static or dynamic entry.

broadcast

Indicates pseudo broadcasting.

CISCO

Indicates the encapsulation type for this map: either CISCO or IETF.

TCP/IP Header Compression (inherited), passive (inherited)

Indicates whether the TCP/IP header compression characteristics were inherited from the interface or were explicitly configured for the IP map.

status defined, active

Indicates that the mapping between the destination address and the data-link connection identifier (DLCI) used to connect to the destination address is active.


Related Commands

Command
Description

show frame-relay pvc

Displays statistics about PVCs for Frame Relay interfaces.

show frame-relay vc-bundle

Displays attributes and other information about a Frame Relay PVC bundle.


show frame-relay pvc

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

show frame-relay pvc [[interface interface] [dlci] [64-bit] | summary [all]]

Syntax Description

interface

(Optional) 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.

summary

(Optional) Displays a summary of all PVCs on the system.

all

(Optional) Displays a summary of all PVCs on each interface.


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 PVC interface priority queueing.

•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 network-to-network PVCs.

12.0(17)S

This command was modified to display the number of outgoing packets dropped and the number of outgoing bytes dropped because of QoS policy.

12.2 T

This command was modified to show that when payload compression is configured for a PVC, the throughput rate reported by the PVC is equal to the rate reported by the interface.

12.2(4)T

The 64-bit keyword was added.

12.2(11)T

This command was modified to display the number of outgoing packets dropped and the number of outgoing bytes dropped because of QoS policy.

12.2(13)T

This command was modified to support display of Frame Relay PVC bundle information.

12.2(15)T

This command was modified to support display of Frame Relay voice-adaptive fragmentation information.

12.2(27)SBC

This command was integrated into Cisco IOS Release 12.2(27)SBC, and the summary and all keywords were added.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB, and support was added for hierarchical queueing framework (HQF).

12.4(9)T

The summary and all keywords were added, and support was added for hierarchical queueing framework (HQF).


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.

To display a summary of all PVCs on the system, use the show frame-relay pvc command with the summary keyword. To display a summary of all PVCs per interface, use the summary all keywords.

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.

You can change the period of time over which a set of data is used for computing load statistics. If you decrease the load interval, the average statistics are computed over a shorter period of time and are more responsive to bursts of traffic. To change the length of time for which a set of data is used to compute load statistics for a PVC, use the load-interval command in Frame-Relay DLCI configuration mode.

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 points 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. This section contains the following examples:

• Summary of Frame Relay PVCs: Example

• Frame Relay Generic Configuration: Example

• Frame Relay Voice-Adaptive Fragmentation: Example

• Frame Relay PVC Bundle: Example

• Frame Relay 64-Bit Counter: Example

• Frame Relay Fragmentation and Hardware Compression: Example

• Switched PVC: Example

• Frame Relay Congestion Management on a Switched PVC: Example

• Frame Relay Policing on a Switched PVC: Example

• Frame Relay PVC Priority Queueing: Example

• Low Latency Queueing for Frame Relay: Example

• PPP over Frame Relay: Example

• Voice over Frame Relay: Example

• FRF.12 Fragmentation: Example

• Multipoint Subinterfaces Transporting Data: Example

• PVC Shaping When HQF is Enabled: Example

• PVC Transporting Voice and Data: Example

Summary of Frame Relay PVCs: Example

The following example shows sample output of the show frame-relay pvc command with the summary keyword. The summary keyword displays all PVCs on the system. 

Router# show frame-relay pvc summary          


Frame-Relay VC Summary


              Active     Inactive      Deleted       Static

  Local          0           12            0            0

  Switched       0            0            0            0

  Unused         0            0            0            0

The following example shows sample output for the show frame-relay pvc command with the summary and all keywords. The summary and all keywords display all PVCs per interface. 

Router# show frame-relay pvc summary all


VC Summary for interface Serial3/0 (Frame Relay DTE)


              Active     Inactive      Deleted       Static

  Local          0            7            0            0

  Switched       0            0            0            0

  Unused         0            0            0            0


VC Summary for interface Serial3/1 (Frame Relay DTE)


              Active     Inactive      Deleted       Static

  Local          0            5            0            0

  Switched       0            0            0            0

  Unused         0            0            0            0

Frame Relay Generic Configuration: Example

The following sample output shows a generic Frame Relay configuration on DLCI 100: 

Router# show frame-relay pvc 100


PVC Statistics for interface Serial4/0/1:0 (Frame Relay DTE)


DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE (EEK UP), INTERFACE = Serial4/0/1:0.1


  input pkts 4360          output pkts 4361         in bytes 146364    

  out bytes 130252         dropped pkts 3735        in pkts dropped 0         

  out pkts dropped 3735             out bytes dropped 1919790

  late-dropped out pkts 3735        late-dropped out bytes 1919790

  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 337       out bcast bytes 102084    

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

  pvc create time 05:34:06, last time pvc status changed 05:33:38

Frame Relay Voice-Adaptive Fragmentation: Example

The following sample output indicates that Frame Relay voice-adaptive fragmentation is active on DLCI 202 and there are 29 seconds left on the deactivation timer. If no voice packets are detected in the next 29 seconds, Frame Relay voice-adaptive fragmentation will become inactive. 

Router# show frame-relay pvc 202

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

DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial3/1.2

  input pkts 0             output pkts 479          in bytes 0

  out bytes 51226          dropped pkts 0           in pkts dropped 0

  out pkts dropped 0                out bytes dropped 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

  5 minute input rate 0 bits/sec, 0 packets/sec 

  5 minute output rate 5000 bits/sec, 5 packets/sec

  pvc create time 00:23:36, last time pvc status changed 00:23:31     

  fragment type end-to-end fragment size 80 adaptive active, time left 29 secs

Frame Relay PVC Bundle: Example

The following sample output indicates that PVC 202 is a member of VC bundle MAIN-1-static: 

Router# show frame-relay pvc 202


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


DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1/4


  input pkts 0             output pkts 45           in bytes 0

  out bytes 45000          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

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 2000 bits/sec, 2 packets/sec

  pvc create time 00:01:25, last time pvc status changed 00:01:11

  VC-Bundle MAIN-1-static

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 Network-to-Network Interface (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 64000 bps 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 type employed is proprietary to Cisco.

A sample configuration for this situation 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 situation 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: Example

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 Shaping When HQF is Enabled: Example

The following is sample output from the show frame-relay pvc command for a PVC when HQF is enabled: 

Router# show frame-relay pvc 16


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


DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial4/1


  input pkts 1             output pkts 1            in bytes 34

  out bytes 34             dropped pkts 0           in pkts dropped 0

  out pkts dropped 0                out bytes dropped 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 1         out bcast bytes 34

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

  shaping inactive

PVC Transporting Voice and Data: Example

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 4 describes the significant fields shown in the displays.

Table 4 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 pkts dropped

Number of incoming packets dropped. Incoming packets may be dropped for a number of reasons, including the following:

•Inactive PVC

•Policing

•Packets received above DE discard level

•Dropped fragments

•Memory allocation failures

•Configuration problems

out pkts dropped

Number of outgoing packets dropped, including shaping drops and late drops.

out bytes dropped

Number of outgoing bytes dropped.

late-dropped out pkts

Number of outgoing packets dropped because of QoS policy (such as with VC queuing or Frame Relay traffic shaping). This field is not displayed when the value is zero.

late-dropped out bytes

Number of outgoing bytes dropped because of QoS policy (such with as VC queuing or Frame Relay traffic shaping). This field is not displayed when the value is zero.

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.

VC-Bundle

PVC bundle of which the PVC is a member.

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.

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 as follows:

•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.

adaptive active/inactive

Indicates whether Frame Relay voice-adaptive fragmentation is active or inactive.

time left

Number of seconds left on the Frame Relay voice-adaptive fragmentation deactivation timer. When this timer expires, Frame Relay fragmentation turns off.

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.

Queueing strategy

Per-VC queueing strategy.

Output queue

48/100

0 drop

300 dequeued

State of the per-VC queue.

•Number of packets enqueued/size of the queue

•Number of packets dropped

•Number of packets dequeued

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 accounting adjust

Enables byte count adjustment at the PVC level so that the number of bytes sent and received at the PVC corresponds to the actual number of bytes sent and received on the physical interface.

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.

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 map

Displays the current Frame Relay map entries and information about the connections

show frame-relay vc-bundle

Displays attributes and other information about a Frame Relay PVC bundle.


Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2005-2006 Cisco Systems, Inc. All rights reserved.