Table Of Contents

show frame-relay end-to-end keepalive

show frame-relay fragment

show frame-relay ip tcp header-compression

show frame-relay lapf

show frame-relay lmi

show frame-relay map

show frame-relay multilink

show frame-relay pvc

show frame-relay qos-autosense

show frame-relay route

show frame-relay svc maplist

show frame-relay traffic

show frame-relay vc-bundle

show ima interface atm

show interface cbr

show interfaces atm

show network-clocks

show pppatm summary

show pppatm trace

show smds addresses

show smds map

show smds traffic

show sscop

show ssg auto-domain exclude-profile

show ssg binding

show ssg connection

show ssg direction

show ssg host

show ssg next-hop

show ssg open-garden

show ssg pass-through-filter

show ssg pending-command

show ssg port-map ip

show ssg port-map status

show ssg radius-proxy address-pool

show ssg service

show ssg tcp-redirect group

show ssg vc-service-map

show sss session

show tcp-redirect mappings

show vc-group

show frame-relay end-to-end keepalive

To display statistics about Frame Relay end-to-end keepalive, use the show frame-relay end-to-end keepalive command in privileged EXEC mode.

show frame-relay end-to-end keepalive [interface [dlci]]

Syntax Description

interface	(Optional) Interface to display.
dlci	(Optional) DLCI to display.

Defaults

If no interface is specified, show all interfaces.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)T	This command was introduced.

Usage Guidelines

Use this command to display the keepalive status of an interface.

Examples

The following example shows output from the show frame-relay end-to-end keepalive command:

Router# show frame-relay end-to-end keepalive interface s1

End-to-end Keepalive Statistics for Interface Serial1 (Frame Relay DTE)

DLCI = 100, DLCI USAGE = LOCAL, VC STATUS = STATIC (EEK UP)

SEND SIDE STATISTICS

Send Sequence Number: 86,       Receive Sequence Number: 87

Configured Event Window: 3,     Configured Error Threshold: 2

Total Observed Events: 90,      Total Observed Errors: 34

Monitored Events: 3,            Monitored Errors: 0

Successive Successes: 3,        End-to-end VC Status: UP

RECEIVE SIDE STATISTICS

Send Sequence Number: 88,       Receive Sequence Number: 87

Configured Event Window: 3,     Configured Error Threshold: 2

Total Observed Events: 90,      Total Observed Errors: 33

Monitored Events: 3,            Monitored Errors: 0

Successive Successes: 3,        End-to-end VC Status: UP

Related Commands

Command	Description
frame-relay end-to-end keepalive error-threshold	Modifies the keepalive error threshold value.
frame-relay end-to-end keepalive event-window	Modifies the keepalive event window value.
frame-relay end-to-end keepalive mode	Enables Frame Relay end-to-end keepalives.
frame-relay end-to-end keepalive success-events	Modifies the keepalive success events value.
frame-relay end-to-end keepalive timer	Modifies the keepalive timer.
map-class frame-relay	Specifies a map class to define QoS values for an SVC.

show frame-relay fragment

To display information about the Frame Relay fragmentation, use the show frame-relay fragment command in privileged EXEC mode.

show frame-relay fragment [interface interface [dlci]]

Syntax Description

interface	(Optional) Indicates a specific interface for which Frame Relay fragmentation information will be displayed.
interface	(Optional) Interface number containing the DLCI(s) for which you wish to display fragmentation information.
dlci	(Optional) Specific DLCI for which you wish to display fragmentation information.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(4)T	This command was introduced.
12.1(2)E	Support was added for Cisco 7500 series routers with Versatile Interface Processors.
12.1(5)T	Support was added for Cisco 7500 series routers with Versatile Interface Processors running 12.1(5)T.

Usage Guidelines

When no parameters are specified with this command, the output displays a summary of each data-link connection identifier (DLCI) configured for fragmentation. The information displayed includes the fragmentation type, the configured fragment size, and the number of fragments transmitted, received, and dropped.

When a specific interface and DLCI are specified, additional details are displayed.

Examples

The following is sample output for the show frame-relay fragment command without any parameters specified:

Router# show frame-relay fragment

interface         dlci  frag-type    frag-size  in-frag    out-frag   dropped-frag

Serial0           108   VoFR-cisco   100        1261       1298       0         

Serial0           109   VoFR         100        0          243        0         

Serial0           110   end-to-end   100        0          0          0         

The following is sample output for the show frame-relay fragment command when an interface and DLCI are specified:

Router# show frame-relay fragment interface Serial1/0 16

  fragment-size 45                  fragment type end-to-end

  in fragmented pkts 0              out fragmented pkts 0

  in fragmented bytes 0             out fragmented bytes 0

  in un-fragmented pkts 0           out un-fragmented pkts 0

  in un-fragmented bytes 0          out un-fragmented bytes 0 

  in assembled pkts 0               out pre-fragmented pkts 0 

  in assembled bytes 0              out pre-fragmented bytes

  in dropped reassembling pkts 0    out dropped fragmenting pkts 0 

  in timeouts 0         

  in out-of-sequence fragments 0         

  in fragments with unexpected B bit set 0         

  out interleaved packets 0         

Table 37 describes the fields shown in the display.

Table 26 show frame-relay fragment Field Descriptions 

Field	Description
interface	Subinterface containing the DLCI for which the fragmentation information pertains.
dlci	Data-link connection identifier for which the displayed fragmentation information applies.
frag-type	Type of fragmentation configured on the designated DLCI. Supported types are end-to-end, VoFR, and VoFR-cisco.
frag-size	Configured fragment size in bytes.
in-frag	Total number of fragments received by the designated DLCI.
out-frag	Total number of fragments sent by the designated DLCI.
dropped-frag	Total number of fragments dropped by the designated DLCI.
in/out fragmented pkts	Total number of frames received/sent by this DLCI that have a fragmentation header.
in/out fragmented bytes	Total number of bytes, including those in the Frame Relay headers, that have been received/sent by this DLCI.
in/out un-fragmented pkts	Number of frames received/sent by this DLCI that do not require reassembly, and therefore do not contain the FRF.12 header. These counters can be incremented only when the end-to-end fragmentation type is set.
in/out un-fragmented bytes	Number of bytes received/sent by this DLCI that do not require reassembly, and therefore do not contain the FRF.12 header. These counters can be incremented only when the end-to-end fragmentation type is set.
in assembled pkts	Total number of fully reassembled frames received by this DLCI, including the frames received without a Frame Relay fragmentation header (in unfragmented packets). This counter corresponds to the frames viewed by the upper-layer protocols.
out pre-fragmented pkts	Total number of fully reassembled frames transmitted by this DLCI, including the frames transmitted without a Frame Relay fragmentation header (out un-fragmented pkts).
in assembled bytes	Number of bytes in the fully reassembled frames received by this DLCI, including the frames received without a Frame Relay fragmentation header (in un-fragmented bytes). This counter corresponds to the total number of bytes viewed by the upper-layer protocols.
out pre-fragmented bytes	Number of bytes in the fully reassembled frames transmitted by this DLCI, including the frames sent without a Frame Relay fragmentation header (out un-fragmented bytes). This counter corresponds to the total number of bytes viewed by the upper-layer protocols.
in dropped reassembling pkts	Number of fragments received by this DLCI that are dropped for reasons such as running out of memory, receiving segments out of sequence, receiving an unexpected frame with a B bit set, or timing out on a reassembling frame.
out dropped fragmenting pkts	Number of fragments that are dropped by this DLCI during transmission because of running out of memory.
in timeouts	Number of reassembly timeouts that have occurred on incoming frames to this DLCI. (A frame that does not fully reassemble within two minutes is dropped, and the timeout counter is incremented.)
in out-of-sequence fragments	Number of fragments received by this DLCI that have an unexpected sequence number.
in fragments with unexpected B bit set	Number of fragments received by this DLCI that have an unexpected B bit set. When this occurs, all fragments being reassembled are dropped and a new frame is begun with this fragment.
out interleaved packets	Number of packets leaving this DLCI that have been interleaved between segments.

Related Commands

Command	Description
frame-relay fragment	Enables fragmentation of Frame Relay frames for a Frame Relay map class.
show frame-relay pvc	Displays statistics about PVCs for Frame Relay interfaces.
show frame-relay vofr	Displays details about FRF.11 subchannels being used on Voice over Frame Relay DLCIs.
show interfaces serial	Displays information about a serial interface.
show traffic-shape queue	Displays information about the elements queued at a particular time at the VC level.

show frame-relay ip tcp header-compression

To display statistics and TCP/IP header compression information for an interface, use the show frame-relay ip tcp header-compression command in EXEC mode.

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

Syntax Description

interface type number

(Optional) Interface type and number.

Command Modes

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.

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 rtp 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

Table 27 describes the fields shown in the display.

Table 27 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 lapf

To display information about the status of the internals of Frame Relay Layer 2 (LAPF) if switched virtual circuits (SVCs) are configured, use the show frame-relay lapf EXEC command.

show frame-relay lapf

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Examples

The following is sample output from the show frame-relay lapf command.

Router# show frame-relay lapf

Interface = Serial1 (up),  LAPF state = TEI_ASSIGNED (down)

SVC disabled, link down cause = LMI down,  #link-reset = 0

T200 = 1.5 sec.,  T203 = 30 sec.,  N200 = 3,  k = 7,  N201 = 260

I xmt = 0, I rcv = 0, I reXmt = 0, I queued = 0

I xmt dropped = 0,  I rcv dropped = 0,  Rcv pak dropped = 0

RR xmt = 0,  RR rcv = 0,  RNR xmt = 0,  RNR rcv = 0

REJ xmt = 0,  REJ rcv = 0,  FRMR xmt = 0,  FRMR rcv = 0

DM xmt = 0,  DM rcv = 0,  DISC xmt = 0,  DISC rcv = 0

SABME xmt = 0,  SABME rcv = 0,  UA xmt = 0,  UA rcv = 0

V(S) = 0,  V(A) = 0,  V(R) = 0,  N(S) = 0,  N(R) = 0

Xmt FRMR at Frame Reject 

Table 28 describes significant fields in this output.

 

Table 28 show frame-relay lapf Field Descriptions 

Field	Description
Interface	Identifies the interface and indicates the line status (up, down, administratively down).
LAPF state	A LAPF state of MULTIPLE FRAME ESTABLISHED or RIMER_RECOVERY indicates that Layer 2 is functional. Others, including TEI_ASSIGNED, AWAITING_ESTABLISHMENT, and AWAITING_RELEASE, indicate that Layer 2 is not functional.
SVC disabled	Indicates whether SVCs are enabled or disabled.
link down cause	Indicates the reason that the link is down. For example, N200 error, memory out, peer disconnect, LMI down, line down, and SVC disabled. Many other causes are described in the Q.922 specification.
#link-reset	Number of times the Layer 2 link has been reset.
T200, T203, N200, k, N201	Values of Layer 2 parameters.
I xmt, I rcv, I reXmt, I queued	Number of I frames sent, received, retransmitted, and queued for transmission, respectively.
I xmt dropped	Number of sent I frames that were dropped.
I rcv dropped	Number of I frames received over DLCI 0 that were dropped.
Rcv pak dropped	Number of received packets that were dropped.
RR xmt, RR rcv	Number of RR frames sent; number of RR frames received.
RNR xmt, RNR rcv	Number of RNR frames sent; number of RNR frames received.
REJ xmt, REJ rcv	Number of REJ frames sent; number of REJ frames received.
FRMR xmt, FRMR rcv	Number of FRMR frames sent; number of FRMR frames received.
DM xmt, DM rcv	Number of DM frames sent; number of DM frames received.
DISC xmt, DISC rcv	Number of DISC frames sent; number of DISC frames received.
SABME xmt, SABME rcv	Number of SABME frames sent; number of SABME frames received.
UA xmt, UA rcv	Number of UA frames sent; number of UA frames received.
V(S) 0, V(A) 0, V(R) 0, N(S) 0, N(R) 0	Layer 2 sequence numbers.
Xmt FRMR at Frame Reject	Indicates whether the FRMR frame is sent at Frame Reject.

show frame-relay lmi

To display statistics about the Local Management Interface (LMI), use the show frame-relay lmi EXEC command.

show frame-relay lmi [type number]

Syntax Description

type	(Optional) Interface type; it must be serial.
number	(Optional) Interface number.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

Usage Guidelines

Enter the command without arguments to obtain statistics about all Frame Relay interfaces.

Examples

The following is sample output from the show frame-relay lmi command when the interface is a data terminal equipment (DTE) device:

Router# show frame-relay lmi

LMI Statistics for interface Serial1 (Frame Relay DTE) LMI TYPE = ANSI

  Invalid Unnumbered info 0             Invalid Prot Disc 0

  Invalid dummy Call Ref 0              Invalid Msg Type 0

  Invalid Status Message 0              Invalid Lock Shift 0

  Invalid Information ID 0              Invalid Report IE Len 0

  Invalid Report Request 0              Invalid Keep IE Len 0

  Num Status Enq. Sent 9                Num Status msgs Rcvd 0

  Num Update Status Rcvd 0              Num Status Timeouts 9 

The following is sample output from the show frame-relay lmi command when the interface is a Network-to-Network Interface (NNI):

Router# show frame-relay lmi

LMI Statistics for interface Serial3 (Frame Relay NNI) LMI TYPE = CISCO

  Invalid Unnumbered info 0             Invalid Prot Disc 0

  Invalid dummy Call Ref 0              Invalid Msg Type 0

  Invalid Status Message 0              Invalid Lock Shift 0

  Invalid Information ID 0              Invalid Report IE Len 0

  Invalid Report Request 0              Invalid Keep IE Len 0

  Num Status Enq. Rcvd 11               Num Status msgs Sent 11

  Num Update Status Rcvd 0              Num St Enq. Timeouts 0

  Num Status Enq. Sent 10               Num Status msgs Rcvd 10

  Num Update Status Sent 0              Num Status Timeouts 0

Table 29 describes significant fields shown in the output.

Table 29 show frame-relay lmi Field Descriptions

Field	Description
LMI Statistics	Signalling or LMI specification: CISCO, ANSI, or ITU-T.
Invalid Unnumbered info	Number of received LMI messages with invalid unnumbered information field.
Invalid Prot Disc	Number of received LMI messages with invalid protocol discriminator.
Invalid dummy Call Ref	Number of received LMI messages with invalid dummy call references.
Invalid Msg Type	Number of received LMI messages with invalid message type.
Invalid Status Message	Number of received LMI messages with invalid status message.
Invalid Lock Shift	Number of received LMI messages with invalid lock shift type.
Invalid Information ID	Number of received LMI messages with invalid information identifier.
Invalid Report IE Len	Number of received LMI messages with invalid Report IE Length.
Invalid Report Request	Number of received LMI messages with invalid Report Request.
Invalid Keep IE Len	Number of received LMI messages with invalid Keep IE Length.
Num Status Enq. Sent	Number of LMI status inquiry messages sent.
Num Status Msgs Rcvd	Number of LMI status messages received.
Num Update Status Rcvd	Number of LMI asynchronous update status messages received.
Num Status Timeouts	Number of times the status message was not received within the keepalive time value.
Num Status Enq. Rcvd	Number of LMI status enquiry messages received.
Num Status Msgs Sent	Number of LMI status messages sent.
Num Status Enq. Timeouts	Number of times the status enquiry message was not received within the T392 DCE timer value.
Num Update Status Sent	Number of LMI asynchronous update status messages sent.

show frame-relay map

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

show frame-relay map

Syntax Description

This command has no arguments or keywords.

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.2(13)T	The display output for this command was modified to include information about Frame Relay PVC bundle maps.

Examples

The following is sample output from the show frame-relay map command:

Router# show frame-relay map

Serial 1 (administratively down): ip 10.108.177.177 dlci 177 (0xB1,0x2C10), static,

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

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 

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

 

Table 30 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 pseudobroadcasting.
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 multilink

To display configuration information and statistics about multilink Frame Relay bundles and bundle links, use the show frame-relay multilink command in privileged EXEC mode.

show frame-relay multilink [mfr number | serial number] [detailed]

Syntax Description

mfr number	(Optional) Specific bundle interface for which information will be displayed.
serial number	(Optional) Specific bundle link interface for which information will be displayed.
detailed	(Optional) More detailed information will be displayed, including counters for the control messages sent to and from the peer device and the status of the bundle links.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(17)S	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

If you do not specify a bundle or bundle link, information for all bundles and bundle links will be displayed.

Examples

All Bundles and Bundle Links Example

The following example shows output for the show frame-relay multilink command. Because a particular bundle or bundle link is not specified, information for all bundles and bundle links is displayed.

Router# show frame-relay multilink 

Bundle:MFR0, State = Administratively down, class = A, fragmentation disabled  

 BID = MFR0

 Bundle links :

 Serial2/1:3, HW state :up, Protocol state :Idle, LID :Serial2/1:3

 Serial2/1:2, HW state :up, Protocol state :Idle, LID :Serial2/1:2

 Serial2/1:1, HW state :up, Protocol state :Idle, LID :Serial2/1:1

Bundle Link Example

The following example shows output for the show frame-relay multilink command with the serial number option. It displays information about the specified bundle link.

Router# show frame-relay multilink serial3/2

 Bundle links :

 Serial3/2, HW state :Administratively down, Protocol state :Down_idle, LID :Serial3/2

 Bundle interface = MFR0,  BID = MFR0

Detailed Bundle Link Examples

The following example shows output for the show frame-relay multilink command with the serial number and detailed options. The example shows a bundle link in the "idle" state.

Router# show frame-relay multilink serial3 detail

 Bundle links:

  Serial3, HW state = up, link state = Idle, LID = Serial3

  Bundle interface = MFR0,  BID = MFR0

    Cause code = none, Ack timer = 4, Hello timer = 10,

    Max retry count = 2, Current count = 0,

    Peer LID = Serial5/3, RTT = 0 ms

    Statistics:

    Add_link sent = 0, Add_link rcv'd = 10,

    Add_link ack sent = 0, Add_link ack rcv'd = 0,

    Add_link rej sent = 10, Add_link rej rcv'd = 0,

    Remove_link sent = 0, Remove_link rcv'd = 0,

    Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,

    Hello sent = 0, Hello rcv'd = 0,

    Hello_ack sent = 0, Hello_ack rcv'd = 0,

    outgoing pak dropped = 0, incoming pak dropped = 0

The following example shows output for the show frame-relay multilink command with the serial number and detailed options. The example shows a bundle link in the "up" state.

Router# show frame-relay multilink serial3 detail

 Bundle links:

  Serial3, HW state = up, link state = Up, LID = Serial3

  Bundle interface = MFR0,  BID = MFR0

    Cause code = none, Ack timer = 4, Hello timer = 10,

    Max retry count = 2, Current count = 0,

    Peer LID = Serial5/3, RTT = 4 ms

    Statistics:

    Add_link sent = 1, Add_link rcv'd = 20,

    Add_link ack sent = 1, Add_link ack rcv'd = 1,

    Add_link rej sent = 19, Add_link rej rcv'd = 0,

    Remove_link sent = 0, Remove_link rcv'd = 0,

    Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,

    Hello sent = 0, Hello rcv'd = 1,

    Hello_ack sent = 1, Hello_ack rcv'd = 0,

    outgoing pak dropped = 0, incoming pak dropped = 0

Table 31 describes the significant fields shown in the displays.

Table 31 show frame-relay multilink Field Descriptions 

Field	Description
Bundle	Bundle interface.
State	Operational state of the bundle interface.
class	Class A indicates that if one bundle link is up, the bundle is marked up; all bundle links must be down before the bundle is marked down.
BID	Bundle identification.
Bundle links	Bundle links for which information will be displayed.
HW state	Operational state of the physical link.
Protocol state	Operational state of the bundle link line protocol.
Link state	Operational state of the bundle link.
LID	Bundle link identification.
Bundle interface	Bundle interface with which the bundle link is associated.
Cause code	May be one of the following values: •ack timer expiry—add link synchronization process has been exhausted. •bundle link idle—peer's bundle link is idle. This usually occurs when the peer's bundle interface is shut. •inconsistent bundle—peer already has this bundle associated with a different bundle. •loopback detected—local bundle link's physical line is looped back. •other—indicates a LID mismatch, or that the ID length from the peer is too long, or that there has been a failure to allocate ID memory. •unexpected Add_link—Add_link message is received when the bundle link is already in the up state. This code may appear when the line protocol is being set up, but will disappear once the connection has stabilized.
Ack timer	Number of seconds the bundle link will wait for a hello acknowledgment before resending a hello message or resending an Add_link message used for initial synchronization.
Hello timer	Interval at which a bundle link sends out hello messages.
Max retry count	Maximum number of times a bundle link will resend a hello message before receiving an acknowledgment or resending an Add_link message.
Current count	Number of tries that have already been attempted.
Peer lid	Bundle link identification name of the peer end of the link.
RTT	Round trip time, as measured by using the Timestamp Information Element in the Hello and Hello_ack messages.
Statistics	Statistics for each bundle link will be displayed.
Add_link sent	Number of Add_link messages sent. Add_link messages notify the peer endpoint that the local endpoint is ready to process frames.
Add_link rcv'd	Number of Add_link messages received.
Add_link ack sent	Number of Add_link acknowledgments sent. Add_link acknowledgments notify the peer endpoint that an Add_link message was received.
Add_link ack rcv'd	Number of Add_link acknowledgments received.
Add_link rej sent	Number of Add_link_reject messages sent.
Add_link rej rcv'd	Number of Add_link_reject messages received.
Remove_link sent	Number of Remove_link messages sent. Remove_link messages notify the peer that on the local end a bundle link is being removed from the bundle.
Remove_link rcv'd	Number of Remove_link messages received.
Remove_link_ack sent	Number of Remove_link acknowledgments sent. Remove_link acknowledgments notify the peer that a Remove_link message has been received.
Remove_link_ack rcv'd	Number of Remove_link acknowledgments received.
Hello sent	Number of Hello messages sent. Hello messages notify the peer endpoint that the local endpoint remains in the up state.
Hello rcv'd	Number of Hello messages received.
Hello_ack sent	Number of Hello acknowledgments sent. Hello acknowledgments notify the peer that hello messages have been received.
Hello_ack rcv'd	Number of Hello acknowledgments received.
outgoing pak dropped	Number of outgoing packets dropped.
incoming pak dropped	Number of incoming packets dropped.

Related Commands

Command	Description
debug frame-relay multilink	Displays debug messages for multilink Frame Relay bundles and bundle links.

show frame-relay pvc

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

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

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.

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.

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.

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.

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