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 

  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

The following is sample output from the show frame-relay pvc command for multipoint subinterfaces carrying data only. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing. Note that neither fragmentation nor voice is configured on this PVC.

Router# show frame-relay pvc

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

input pkts 10  output pkts 7  in bytes 6222 

out bytes 6034  dropped pkts 0  in FECN pkts 0 

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

in DE pkts 0  out DE pkts 0         

outbcast pkts 0  outbcast bytes 0

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

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

input pkts 20  output pkts 8  in bytes 5624 

out bytes 5222  dropped pkts 0  in FECN pkts 0 

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

in DE pkts 0  out DE pkts 0         

outbcast pkts 0  outbcast bytes 0

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

PVC Transporting Voice and Data

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

Router# show frame-relay pvc interface serial 1 45

 PVC Statistics for interface Serial1 (Frame Relay DTE)

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

   input pkts 85            output pkts 289          in bytes 1730      

   out bytes 6580           dropped pkts 11          in FECN pkts 0         

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

   in DE pkts 0             out DE pkts 0         

   out bcast pkts 0          out bcast bytes 0         

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

   Service type VoFR

   configured voice bandwidth 25000, used voice bandwidth 22000

   fragment type VoFR         fragment size 100

   cir 20000     bc   1000      be 0         limit 125    interval 50  

   mincir 20000     byte increment 125   BECN response no 

   fragments 290       bytes 6613      fragments delayed 1         bytes delayed 33       

   shaping inactive    

   traffic shaping drops 0

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

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

   Current fair queue configuration:

    Discard     Dynamic      Reserved

    threshold   queue count  queue count

    64          16           2    

   Output queue size 0/max total 600/drops 0

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

Table 32 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. The DCE device reports the status, and the DTE device receives the status. When you disable the Local Management Interface (LMI) mechanism on the interface (by using the no keepalive command), the PVC status is STATIC. Otherwise, the PVC status is exchanged using the LMI protocol: •STATIC—LMI is disabled on the interface. •ACTIVE— The PVC is operational and can transmit packets. •INACTIVE—The PVC is configured, but down. •DELETED—The PVC is not present (DTE device only), which means that no status is received from the LMI protocol. If the frame-relay end-to-end keepalive command is used, the end-to-end keepalive (EEK) status is reported in addition to the LMI status. For example: •ACTIVE (EEK UP) —The PVC is operational according to LMI and end-to-end keepalives. •ACTIVE (EEK DOWN)—The PVC is operational according to LMI, but end-to-end keepalive has failed.
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 •pkts 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 (and unfragmented packets that are too small to be fragmented) 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 (and unfragmented packets that are too small to be fragmented) 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.

show frame-relay qos-autosense

To display the quality of service (QoS) values sensed from the switch, use the show frame-relay qos-autosense EXEC command.

show frame-relay qos-autosense [interface number]

Syntax Description

interface number

(Optional) Indicates the number of the physical interface for which you want to display QoS information.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.
12.1(3)T	This command was modified to display information about Enhanced Local Management Interface (ELMI) address registration.

Examples

The following is sample output from the show frame-relay qos-autosense command when ELMI and ELMI address registration are enabled.

Router# show frame-relay qos-autosense

ELMI information for interface Serial1

   IP Address used for Address Registration:9.2.7.9 My Ifindex:4

   ELMI AR status : Enabled.

   Connected to switch:hgw1 Platform:2611 Vendor:cisco 

   Sw side ELMI AR status: Enabled

   IP Address used by switch for address registration :9.2.6.9 Ifindex:5

   ELMI AR status : Enabled.

                (Time elapsed since last update 00:00:40)

The following is sample output from the show frame-relay qos-autosense command when ELMI and traffic shaping are enabled:

Router# show frame-relay qos-autosense 

ELMI information for interface Serial1 

 Connected to switch:FRSM-4T1   Platform:AXIS   Vendor:cisco

              (Time elapsed since last update 00:00:30)

 DLCI = 100

 OUT:   CIR  64000       BC 50000        BE 25000        FMIF 4497

 IN:    CIR  32000       BC 25000        BE 12500        FMIF 4497

 Priority 0     (Time elapsed since last update 00:00:12) 

 DLCI = 200

 OUT:   CIR 128000       BC 50000        BE 5100         FMIF 4497

 IN:    CIR Unknown      BC Unknown      BE Unknown      FMIF 4497

 Priority 0     (Time elapsed since last update 00:00:13) 

Table 33 describes the significant fields in the output display.

Table 33 show frame-relay qos-autosense Field Descriptions 

Field	Description
IP Address used for Address Registration	Management IP address of the data terminal equipment (DTE) interface.
My ifIndex	ifIndex of the DTE interface on which ELMI is running.
ELMI AR status	Indicates whether ELMI is enabled or disabled on the interface.
Connected to switch	Name of neighboring switch.
Platform	Platform information about neighboring switch.
Vendor	Vendor information about neighboring switch.
Sw side ELMI AR status	Indicates whether ELMI is enabled or disabled on the neighboring switch.
IP Address used by switch for address registration	IP address of DCE. If ELMI is not supported or is disabled, this value will be 0.0.0.0.
ifIndex	ifIndex of DCE.
DLCI	Value that indicates which PVC statistics are being reported.
Out:	Values reporting settings configured for the outgoing Committed Information Rate, Burst Size, Excess Burst Size, and FMIF.
In:	Values reporting settings configured for the incoming Committed Information Rate, Burst Size, Excess Burst Size, and FMIF.
Priority	Value indicating priority level (currently not used).

Related Commands

Command	Description
frame-relay qos-autosense	Enables ELMI on the Cisco router.
show frame-relay pvc	Displays statistics about PVCs for Frame Relay interfaces.

show frame-relay route

To display all configured Frame Relay routes, along with their status, use the show frame-relay route EXEC command.

show frame-relay route

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

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

Router# show frame-relay route

    Input Intf      Input Dlci      Output Intf     Output Dlci  Status

    Serial1         100             Serial2         200          active

    Serial1         101             Serial2         201          active

    Serial1         102             Serial2         202          active

    Serial1         103             Serial3         203          inactive

    Serial2         200             Serial1         100          active

    Serial2         201             Serial1         101          active

    Serial2         202             Serial1         102          active

    Serial3         203             Serial1         103          inactive

Table 34 describes significant fields shown in the output.

 

Table 34 show frame-relay route Field Descriptions

Field	Description
Input Intf	Input interface and unit.
Input Dlci	Input DLCI number.
Output Intf	Output interface and unit.
Output Dlci	Output DLCI number.
Status	Status of the connection: active or inactive.

show frame-relay svc maplist

To display all the switched virtual circuits (SVCs) under a specified map list, use the show frame-relay svc maplist EXEC command.

show frame-relay svc maplist name

Syntax Description

name	Name of the map list.

Command Modes

EXEC

Command History

Release	Modification
11.2	This command was introduced.

Examples

The following example shows, first, the configuration of the shank map list and, second, the corresponding output of the show frame-relay svc maplist command. The following lines show the configuration:

map-list shank local-addr X121 87654321 dest-addr X121 12345678

 ip 172.21.177.26 class shank ietf

 ipx 123.0000.0c07.d530 class shank ietf

!

map-class frame-relay shank

 frame-relay incir 192000

 frame-relay min-incir 19200

 frame-relay outcir 192000

 frame-relay min-outcir 19200

 frame-relay incbr(bytes) 15000

 frame-relay outcbr(bytes) 15000

The following lines show the output of the show frame-relay svc maplist command for the preceding configuration:

Router# show frame-relay svc maplist shank 

Map List : shank

Local Address : 87654321            Type: X121

Destination Address: 12345678       Type: X121

Protocol : ip 172.21.177.26

Protocol : ipx 123.0000.0c07.d530

Encapsulation : IETF

Call Reference : 1              DLCI : 501

Configured Frame Mode Information Field Size :

Incoming : 1500         Outgoing : 1500

Frame Mode Information Field Size :

Incoming : 1500         Outgoing : 1500

Configured Committed Information Rate (CIR) :

Incoming : 192 * (10**3)                Outgoing : 192 * (10**3)

Committed Information Rate (CIR) :

Incoming : 192 * (10**3)                Outgoing : 192 * (10**3)

Configured Minimum Acceptable CIR :

Incoming : 192 * (10**2)                Outgoing : 192 * (10**2)

Minimum Acceptable CIR :

Incoming : 0 * (10**0)          Outgoing : 0 * (10**0)

Configured Committed Burst Rate (bytes) :

Incoming : 15000                Outgoing : 15000

Committed Burst Rate (bytes) :

Incoming : 15000                Outgoing : 15000

Configured Excess Burst Rate (bytes) :

Incoming : 16000                Outgoing : 1200

Excess Burst Rate (bytes) :

Incoming : 16000                Outgoing : 1200

Table 35 describes significant fields in the output.

 

Table 35 show frame-relay svc maplist Field Descriptions 

Field	Description
Map List	Name of the configured map-list.
Local Address...Type	Configured source address type (E.164 or X.121) for the call.
Destination Address...Type	Configured destination address type (E.164 or X.121) for the call.
Protocol : ip ... Protocol: ipx ...	Destination protocol addresses configured for the map-list.
Encapsulation	Configured encapsulation type (CISCO or IETF) for the specified destination protocol address.
Call Reference	Call identifier.
DLCI: 501	Number assigned by the switch as the DLCI for the call.
Configured Frame Mode Information Field Size: Incoming:     Outgoing: Frame Mode Information Field Size: Incoming: 1500 Outgoing: 1500	Lines that contrast the configured and actual frame mode information field size settings used for the calls.
Configured Committed Information Rate (CIR): Incoming: 192 * (10**3) Outgoing: 192 * (10**3) Committed Information Rate (CIR): Incoming: 192 * (10**3) Outgoing: 192 * (10**3)	Lines that contrast the configured and actual committed information rate (CIR) settings used for the calls.
Configured Minimum Acceptable CIR: Incoming: 192 * (10**2) Outgoing: 192 * (10**2) Minimum Acceptable CIR: Incoming: 0 * (10**0) Outgoing: 0 * (10**0)	Lines that contrast the configured and actual minimum acceptable CIR settings used for the calls.
Configured Committed Burst Rate (bytes): Incoming: 15000 Outgoing: 15000 Committed Burst Rate (bytes): Incoming: 15000 Outgoing: 15000	Lines that contrast the configured and actual committed burst rate (bytes) settings used for the calls.
Configured Excess Burst Rate (bytes): Incoming: 16000 Outgoing: 1200 Excess Burst Rate (bytes): Incoming: 16000 Outgoing: 1200	Lines that contrast the configured and actual excess burst rate (bytes) settings used for the calls.

Related Commands

Command	Description
class (map-list)	Associates a map class with a protocol-and-address combination.
frame-relay bc	Specifies the incoming or outgoing Bc for a Frame Relay VC.
frame-relay cir	Specifies the incoming or outgoing CIR for a Frame Relay VC.
frame-relay mincir	Specifies the minimum acceptable incoming or outgoing CIR for a Frame Relay VC.
map-class frame-relay	Specifies a map class to define QoS values for an SVC.
map-list	Specifies a map group and link it to a local E.164 or X.121 source address and a remote E.164 or X.121 destination address for Frame Relay SVCs.

show frame-relay traffic

To display the global Frame Relay statistics since the last reload, use the show frame-relay traffic EXEC command.

show frame-relay traffic

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

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

Router# show frame-relay traffic

Frame Relay statistics:

ARP requests sent 14, ARP replies sent 0

ARP request recvd 0, ARP replies recvd 10

show frame-relay vc-bundle

To display attributes and other information about a Frame Relay permanent virtual circuit (PVC) bundle, use the show frame-relay vc-bundle command in privileged EXEC mode.

show frame-relay vc-bundle vc-bundle-name [detail]

Syntax Description

vc-bundle-name	Name of this Frame Relay PVC bundle.
detail	(Optional) Displays output packet count information in addition to the other bundle member attributes for each PVC in the bundle specified by vc-bundle-name.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(13)T	This command was introduced.

Usage Guidelines

Use this command to display packet service levels, bumping attributes, and other information about a specific Frame Relay PVC bundle. To view packet counts for each PVC in the bundle in addition to the other attributes, use the detail keyword.

Examples

General Example

The following example shows the Frame Relay PVC bundle named "MP-4-dynamic" with PVC protection applied. Note that in this PVC bundle, data-link connection identifier (DLCI) 400 is configured to explicitly bump traffic to the PVC that handles DSCP level 40, which is DLCI 404. All the other DLCIs are configured for implicit bumping. In addition, all the DLCIs are configured to accept bumped traffic.

The asterisk (*) before PVC 4a indicates that this PVC was configured with the precedence other command, which means the PVC will handle all levels that are not explicitly configured on other PVCs.

In this example all PVCs are up so, the values in the "Active leve"l fields match the values in the "Config level" fields. If a PVC goes down and its traffic is bumped, the "Active level" field value for the PVC that went down is cleared. The "Active level" field values for the PVC that the traffic bumped to will be updated to include the levels of the PVC that went down.

The first three PVCs in the following example make up a protected group. All three of these PVCs must go down before the bundle will go down. The last two PVCs are protected PVCs: if either of these PVCs goes down, the bundle will go down.

Router# show frame-relay vc-bundle MP-4-dynamic

MP-4-dynamic on Serial1/4.1 - Status: UP Match-type: DSCP

Name 		DLCI 		Config. 	Active 				Bumping 			PG/ 		CIR 		Status 

				level 		level 			to/accept 			PV 		kbps

*4a 		400 		0-9 		0-9 			40/Yes 			pg 				up 

4b 		401 		10-19 		10-19 			9/Yes 			pg 				up 

4c 		402 		20-29 		20-29 			19/Yes 			pg 				up 

4d 		403 		30-39 		30-39 			29/Yes 			- 				up 

4e 		404 		40-49 		40-49 			39/Yes 			- 				up 

4f 		405 		50-59 		50-59 			49/Yes 			- 				up 

4g 		406 		60-62 		60-62 			59/Yes 			pv 				up 

4h 		407 		63 		63 			62/Yes 			pv 				up

Packets sent out on vc-bundle MP-4-dynamic : 0:

Router# 

Bumping Example

The following example shows that although some DLCIs are down, the bumping rules and the remaining DLCIs keep the bundle up and running for all traffic types.

Note that DLCI 304 is handling the traffic being bumped from the three DLCIs that are down. The "Active level" field indicates the levels that the PVC is actually handling, not just which levels are configured.

Router# show frame-relay vc-bundle MP-3-static

MP-3-static on Serial1/4.1 - Status: UP Match-type: DSCP

Name 		DLCI 		Config. 	Active 				Bumping 			PG/ 		CIR 		Status 

				level 		level 			to/accept 			PV 		kbps

3a 		300 		0-9 		0-9 			-/Yes 			- 				up 

3b 		301 		10-19 		10-19 			9/Yes 			- 				up 

3c 		302 		20-29 		20-29 			19/Yes 			- 				up 

3d 		303 		30-39 					40/Yes 			- 				deleted 

3e 		304 		40-49 		30-59,63 			39/Yes 			- 				up 

3f 		305 		50-59 					49/Yes 			- 				deleted 

3g 		306 		60-62 		60-62 			59/No 			- 				up 

3h 		307 		63 					62/Yes 			- 				deleted

Packets sent out on vc-bundle MP-3-static : 335

Router#

Traffic-Shaping Example

The following example shows output for a PVC bundle configured with traffic shaping. The same rules of class inheritance apply to PVC-bundle members as to regular PVCs.

Router# show frame-relay vc-bundle 26k

26k on Serial1/4.1 - Status:UP  Match-type:PRECEDENCE

Name    DLCI  Config.         Active          Bumping     PG/ CIR   Status

              level           level           to/ accept  PV  kbps

        521   0,2,4           0,2,4           -/Yes       -   20    up

        522   1,3,5-6         1,3,5-6         0/Yes       -   26    up

        523   7               7               6/Yes       -   20    up

Packets sent out on vc-bundle 26k :0

Router#

Detail Example

The following example shows the detail output of a PVC bundle. Note in this example that because all packet service levels are not handled, and because the PVCs are currently down, this bundle can never come up.

Router# show frame-relay vc-bundle x41 detail

x41 on Serial1/1 - Status: DOWN Match-type: DSCP

Name 		DLCI 		Config. 		Active 			Bumping 			PG/ 		CIR 		Status 

				level 		level 			to/accept 			PV 		kbps

		410 		50-62 					49/Yes 			- 				down 

		411 		30,32,34,36,3.. 					29/Yes 			- 				down

Packets sent out on vc-bundle x41 : 0

Active configuration and statistics for each member PVC

DLCI 		Output pkts 				Active level

410 		0 				50-62 

411 		0 				30,32,34,36,38-40 

Router#

Table 36 describes the significant fields shown in the show frame-relay vc-bundle displays.

Table 36 show frame-relay vc-bundle Field Descriptions

Field	Description
Status:	PVC bundle status. Possible values are UP, DOWN, and INITIAL (no PVCs associated with the bundle).
Name	The user-defined, alphanumeric name of the PVC.
DLCI	The ID number of the PVC bundle member.
Config. level	The packet service levels configured for the PVC.
Active level	The packet service levels actually handled by the PVC. This may include packet service levels for bumped traffic accepted by the PVC.
Bumping to/accept	The packet service level that the PVC will bump to if it goes down/whether or not the PVC will accept bumped traffic from another PVC.
PG/PV	Indicates whether the PVC is a member of a protected group or is an individually protected PVC. A dash in this field indicates that the PVC is not protected.
CIR kbps	Committed information rate for the PVC, in kilobits per second.
Status	Indicates whether the PVC is up, down, or deleted.
Output pkts	Number of packets sent out on the PVC.

Related Commands

Command	Description
show frame-relay map	Displays the current Frame Relay map entries and information about the connections.
show frame-relay pvc	Displays statistics about PVCs for Frame Relay interfaces.

show ima interface atm

To display information about all configured inverse multiplexing over ATM (IMA) groups or a specific group, use the show ima interface atm privileged EXEC command.

Cisco 2600 and 3600 Series

show ima interface atm [slot/imagroup-number] [detail]

Cisco 7200 Series

show ima interface atm [slot/port] [detail]

or

show ima interface atm [slot/port-adapter/imagroup-number] [detail]

Cisco 7500 Series

show ima interface atm [slot/port-adapter/slot] [detail]

or

show ima interface atm [slot/port-adapter/imagroup-number] [detail]

Syntax Description

slot/	(Optional) ATM slot number.
ima	(Optional) This keyword indicates an IMA group specification rather than a port value for a UNI interface.
group-number	(Optional) Enter an IMA group number from 0 to 3. If you specify the group number, do not insert a space between ima and the number.
port	(Optional) ATM port number.
port-adapter/	(Optional) ATM port adapter.
detail	(Optional) To obtain detailed information, use this keyword.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XK	This command was introduced.
12.0(5)XE	Support for Cisco 7200 and 7500 series routers was added.
12.0(7)XE1	Support for Cisco 7100 series routers was added.
12.1(5)T	Support for Cisco 7100, 7200, and 7500 series routers was integrated in Cisco IOS Release 12.1(5)T.

Usage Guidelines

Use this command to monitor the status of IMA group links.

Examples

On Cisco 7100 or 7200 series routers, the following example displays detailed information about IMA group 0 on ATM interface 2. If you do not enter the detail keyword, you do not see the IMA MIB information or the "Detailed Link Information" output.

Router# show ima interface atm 5/ima0 detail

ATM5/ima0 is up

        ImaGroupState:NearEnd = operational, FarEnd = operational

        ImaGroupFailureStatus  = noFailure

IMA Group Current Configuration:

        ImaGroupMinNumTxLinks = 2    ImaGroupMinNumRxLinks = 2

        ImaGroupDiffDelayMax  = 250  ImaGroupNeTxClkMode   = common(ctc)

        ImaGroupFrameLength   = 128  ImaTestProcStatus     = disabled

        ImaGroupTestLink      = 0    ImaGroupTestPattern   = 0xFF

IMA MIB Information:

        ImaGroupSymmetry        = symmetricOperation

        ImaGroupFeTxClkMode     = common(ctc)

        ImaGroupRxFrameLength   = 128

        ImaGroupTxTimingRefLink = 0     ImaGroupRxTimingRefLink = 0

        ImaGroupTxImaId         = 0     ImaGroupRxImaId         = 0

        ImaGroupNumTxCfgLinks   = 2     ImaGroupNumRxCfgLinks   = 2

        ImaGroupNumTxActLinks   = 2     ImaGroupNumRxActLinks   = 2

        ImaGroupLeastDelayLink  = 0     ImaGroupDiffDelayMaxObs = 0

IMA group counters:

        ImaGroupNeNumFailures   = 1     ImaGroupFeNumFailures   = 2

        ImaGroupUnAvailSecs     = 18    ImaGroupRunningSecs     = 241

IMA Detailed Link Information:

ATM5/0 is up

        ImaLinkRowStatus = active

        ImaLinkIfIndex   = 1            ImaLinkGroupIndex = 47

        ImaLinkState:

                NeTx = active

                NeRx = active

                FeTx = active

                FeRx = active

        ImaLinkFailureStatus:

                NeRx = noFailure

                FeRx = noFailure

        ImaLinkTxLid           = 0      ImaLinkRxLid           = 0

        ImaLinkRxTestPattern   = 64     ImaLinkTestProcStatus  = disabled

        ImaLinkRelDelay        = 0

IMA Link counters :

        ImaLinkImaViolations   = 1

        ImaLinkNeSevErroredSec = 10     ImaLinkFeSevErroredSec = 10

        ImaLinkNeUnavailSec    = 7      ImaLinkFeUnAvailSec    = 8

        ImaLinkNeTxUnusableSec = 17     ImaLinkNeRxUnUsableSec = 16

        ImaLinkFeTxUnusableSec = 17     ImaLinkFeRxUnusableSec = 16

        ImaLinkNeTxNumFailures = 0      ImaLinkNeRxNumFailures = 2

        ImaLinkFeTxNumFailures = 1      ImaLinkFeRxNumFailures = 1

ATM5/1 is up

        ImaLinkRowStatus = active

        ImaLinkIfIndex   = 2            ImaLinkGroupIndex = 47

        ImaLinkState:

                NeTx = active

                NeRx = active

                FeTx = active

                FeRx = active

        ImaLinkFailureStatus:

                NeRx = noFailure

                FeRx = noFailure

        ImaLinkTxLid           = 1      ImaLinkRxLid           = 1

        ImaLinkRxTestPattern   = 64     ImaLinkTestProcStatus  = disabled

        ImaLinkRelDelay        = 0

IMA Link counters :

        ImaLinkImaViolations   = 1

        ImaLinkNeSevErroredSec = 10     ImaLinkFeSevErroredSec = 10

        ImaLinkNeUnavailSec    = 7      ImaLinkFeUnAvailSec    = 8

        ImaLinkNeTxUnusableSec = 16     ImaLinkNeRxUnUsableSec = 16

        ImaLinkFeTxUnusableSec = 16     ImaLinkFeRxUnusableSec = 16

        ImaLinkNeTxNumFailures = 0      ImaLinkNeRxNumFailures = 2

        ImaLinkFeTxNumFailures = 1      ImaLinkFeRxNumFailures = 1

On a Cisco 2600 or 3600 series router, the following example displays detailed information about IMA group 0 on ATM interface 2. Without the detail keyword, only the information up to "Detailed group Information:" appears.

Router# show ima interface atm 4/ima0 detail

Interface ATM2/IMA2 is up

        Group index is 2

        Ne state is operational, failure status is noFailure

        active links bitmap 0x30

    IMA Group Current Configuration:

        Tx/Rx configured links bitmap 0x30/0x30

        Tx/Rx minimum required links 1/1

        Maximum allowed diff delay is 25ms, Tx frame length 128

        Ne Tx clock mode CTC, configured timing reference link ATM2/4

        Test pattern procedure is disabled

    Detailed group Information:

        Tx/Rx Ima_id 0x22/0x40, symmetry symmetricOperation

        Number of Tx/Rx configured links 2/2

        Number of Tx/Rx active links 2/2

        Fe Tx clock mode ctc, Rx frame length 128

        Tx/Rx timing reference link 4/4

        Maximum observed diff delay 0ms, least delayed link 5

        Running seconds 32

        GTSM last changed 10:14:41 UTC Wed Jun 16 1999

    IMA Group Current Counters (time elapsed 33 seconds):

        3 Ne Failures, 3 Fe Failures, 4 Unavail Secs

    IMA Group Total Counters (last 0 15 minute intervals):

        0 Ne Failures, 0 Fe Failures, 0 Unavail Secs

    Detailed IMA link Information:

Interface ATM2/4 is up

        ifIndex 13, Group Index 2, Row Status is active

        Tx/Rx Lid 4/4, relative delay 0ms

        Ne Tx/Rx state active/active

        Fe Tx/Rx state active/active

        Ne Rx failure status is noFailure

        Fe Rx failure status is noFailure

        Rx test pattern 0x41, test procedure disabled

    IMA Link Current Counters (time elapsed 35 seconds):

        1 Ima Violations, 0 Oif Anomalies

        1 Ne Severely Err Secs, 2 Fe Severely Err Secs

        0 Ne Unavail Secs, 0 Fe Unavail Secs

        2 Ne Tx Unusable Secs, 2 Ne Rx Unusable Secs

        0 Fe Tx Unusable Secs, 2 Fe Rx Unusable Secs

        0 Ne Tx Failures, 0 Ne Rx Failures

        0 Fe Tx Failures, 0 Fe Rx Failures

    IMA Link Total Counters (last 0 15 minute intervals):

        0 Ima Violations, 0 Oif Anomalies

        0 Ne Severely Err Secs, 0 Fe Severely Err Secs

        0 Ne Unavail Secs, 0 Fe Unavail Secs

        0 Ne Tx Unusable Secs, 0 Ne Rx Unusable Secs

        0 Fe Tx Unusable Secs, 0 Fe Rx Unusable Secs

        0 Ne Tx Failures, 0 Ne Rx Failures

        0 Fe Tx Failures, 0 Fe Rx Failures

Interface ATM2/5 is up

        ifIndex 14, Group Index 2, Row Status is active

        Tx/Rx Lid 5/5, relative delay 0ms

        Ne Tx/Rx state active/active

        Fe Tx/Rx state active/active

        Ne Rx failure status is noFailure

        Fe Rx failure status is noFailure

        Rx test pattern 0x41, test procedure disabled

    IMA Link Current Counters (time elapsed 46 seconds):

        1 Ima Violations, 0 Oif Anomalies

        1 Ne Severely Err Secs, 2 Fe Severely Err Secs

        0 Ne Unavail Secs, 0 Fe Unavail Secs

        2 Ne Tx Unusable Secs, 2 Ne Rx Unusable Secs

        0 Fe Tx Unusable Secs, 2 Fe Rx Unusable Secs

        0 Ne Tx Failures, 0 Ne Rx Failures

        0 Fe Tx Failures, 0 Fe Rx Failures

    IMA Link Total Counters (last 0 15 minute intervals):

        0 Ima Violations, 0 Oif Anomalies

        0 Ne Severely Err Secs, 0 Fe Severely Err Secs

        0 Ne Unavail Secs, 0 Fe Unavail Secs

        0 Ne Tx Unusable Secs, 0 Ne Rx Unusable Secs

        0 Fe Tx Unusable Secs, 0 Fe Rx Unusable Secs

        0 Ne Tx Failures, 0 Ne Rx Failures

        0 Fe Tx Failures, 0 Fe Rx Failures

Related Commands

Command	Description
show controllers atm	Displays information about an IMA group.

show interface cbr

To display information about the constant bit rate (CBR) interface on the ATM-CES port adapter, use the show interface cbr privileged EXEC command.

show interface cbr interface-number

Syntax Description

interface-number

Interface number (eg. 2/0).

Command Modes

Privileged EXEC

Command History

Release	Modification
11.1	This command was introduced.

Examples

The following is sample output from the show interface cbr command.

Router# show interface cbr 6/0

CBR6/0 is up, line protocol is up 

  Hardware is DCU

  MTU 0 bytes, BW 1544 Kbit, DLY 0 usec, rely 255/255, load 248/255

  Encapsulation ET_ATMCES_T1, loopback not set

  Last input 00:00:00, output 00:00:00, output hang never

  Last clearing of "show interface" counters never

  Queueing strategy: fifo

  Output queue 0/0, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 1507000 bits/sec, 3957 packets/sec

  5 minute output rate 1507000 bits/sec, 3955 packets/sec

     3025960 packets input, 142220120 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     3030067 packets output, 142413149 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 output buffer failures, 0 output buffers swapped out

Table 37 describes the fields shown in the display.

Table 37 show interface cbr Field Descriptions 

Field	Description
CBR6/0 is...	Type, slot, and port number of the interface and indicates whether the interface hardware is currently active (whether carrier detect is present), down, or if it has been taken down by an administrator.
line protocol is...	Indicates whether the software processes that handle the line protocol think the line is usable (that is, whether keepalives are successful). Values are up, down, and administratively down.
Hardware is...	Hardware type.
MTU	Maximum transmission unit of the interface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface, in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
Encapsulation	Encapsulation method assigned to interface.
loopback not set	Indicates whether or not loopback is set.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	The time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates that the elapsed time is too large to be displayed. 0:00:00 indicates that the counters were cleared more than 231ms (and less than 232ms) ago.
Queueing strategy	First-in, first-out queuing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
Output queue, drops input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
5 minute input rate, 5 minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes.
packets input	Total number of error-free packets received by the system.
bytes input	Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
input errors	Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum may not balance with the other counts.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
abort	Illegal sequence of one bits on the interface. This usually indicates a clocking problem between the interface and the data link equipment.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	Because collisions do not occur on CBR interfaces, this statistic is always zero.
interface resets	Number of times an interface has been reset. The interface may be reset by the administrator or automatically when an internal error occurs.
output buffer failures	Number of no resource errors received on the output.
output buffers swapped out	Number of packets swapped to DRAM.

Related Commands

Command	Description
show ces interface cbr	Displays detailed CBR port information.

show interfaces atm

To display information about the ATM interface, use the show interfaces atm privileged EXEC command.

Cisco 7500 series with AIP; Cisco 7200 series with ATM, ATM-CES, and enhanced ATM port adapter; Cisco 2600 and 3600 series with 1-port ATM-25 network module

show interfaces atm [slot/port]

Cisco 7500 series routers with the ATM port adapter and enhanced ATM port adapter

show interfaces atm [slot/port-adapter/port]

Syntax Description

slot/port	(Optional) ATM slot number and port number. Use this format for the following platform configurations: •The AIP on Cisco 7500 series routers. •The ATM port adapter, ATM-CES port adapter, or enhanced ATM port adapter on Cisco 7200 series routers. •The 1-port ATM-25 network module on Cisco 2600 and 3600 series routers.
slot/port-adapter/port	(Optional) ATM slot, port adapter, and port numbers. Use this format for the ATM port adapter or enhanced ATM port adapter on Cisco 2600 and 3600 series routers.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show interfaces atm command:

Router# show interfaces atm 4/0

ATM4/0 is up, line protocol is up

 Hardware is cxBus ATM

 Internet address is 10.108.97.165, subnet mask is 255.255.255.0

 MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255

 ATM E164 Auto Conversion Interface

 Encapsulation ATM, loopback not set, keepalive set (10 sec)

 Encapsulation(s): AAL5, PVC mode

 256 TX buffers, 256 RX buffers, 1024 Maximum VCs, 1 Current VCs

 Signalling vc = 1, vpi = 0, vci = 5

 ATM NSAP address: BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.13

 Last input 0:00:05, output 0:00:05, output hang never

 Last clearing of "show interface" counters never

 Output queue 0/40, 0 drops; input queue 0/75, 0 drops

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

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

     144 packets input, 3148 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     154 packets output, 4228 bytes, 0 underruns

     0 output errors, 0 collisions, 1 interface resets, 0 restarts

The following is sample output from the show interfaces atm command for the ATM port adapter on a Cisco 7500 series router:

Router# show interfaces atm 0/0/0

ATM0/0/0 is up, line protocol is up 

 Hardware is cyBus ATM

 Internet address is 10.1.1.1/24

 MTU 4470 bytes, sub MTU 4470, BW 156250 Kbit, DLY 80 usec, rely 255/255, load 1/255

 Encapsulation ATM, loopback not set, keepalive set (10 sec)

 Encapsulation(s): AAL5, PVC mode

 256 TX buffers, 256 RX buffers,

 2048 maximum active VCs, 1024 VCs per VP, 1 current VCCs

 VC idle disconnect time: 300 seconds

 Last input never, output 00:00:05, output hang never

 Last clearing of "show interface" counters never

 Queueing strategy: fifo

 Output queue 0/40, 0 drops; input queue 0/75, 0 drops

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

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

     5 packets input, 560 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     5 packets output, 560 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 output buffer failures, 0 output buffers swapped out

Table 38 describes the fields shown in both the displays.

Table 38 show interfaces atm Field Descriptions 

Field	Description
ATM... is {up | down| administratively down}	Indicates whether the interface hardware is currently active (whether carrier detect is present) and if it has been taken down by an administrator.
line protocol is {up | down | administratively down}	Indicates whether the software processes that handle the line protocol think the line is usable (that is, whether keepalives are successful).
Hardware is	Hardware type.
Internet address is	Internet address and subnet mask.
MTU	Maximum Transmission Unit of the interface.
sub MTU	Maximum Transmission Unit of the subinterface.
BW	Bandwidth of the interface in kilobits per second.
DLY	Delay of the interface in microseconds.
rely	Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.
load	Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command.
ATM E164 Auto Conversion Interface	Indicates that ATM E164 auto conversion is enabled. When this field is not present, ATM E164 auto conversion is disabled.
Encapsulation	Encapsulation method assigned to interface.
loopback	Indicates whether the interface is configured for loopback testing.
keepalive	Indicates whether keepalives are set or not.
Encapsulation(s)	Type of encapsulation used on the interface (for example, AAL5, and either PVC or SVC mode).
TX buffers	Number of buffers configured with the atm txbuff command.
RX buffers	Number of buffers configured with the atm rxbuff command.
Maximum active VCs	Maximum number of virtual circuits.
VCs per VP	Number of virtual circuits per virtual path (the default is 1024).
Current VCs	Number of virtual circuit connections currently open.
VC idle disconnect time	Number of seconds the SVC must be idle before the SVC is disconnected.
Signalling vc	Number of the signaling PVC.
vpi	Virtual path identifier number.
vci	Virtual channel identifier number.
ATM NSAP address	NSAP address of the ATM interface.
Last input	Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Last output	Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
output hang	Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing	The time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates that the elapsed time is too large to be displayed. 0:00:00 indicates that the counters were cleared more than 231ms (and less than 232ms) ago.
Queueing strategy	First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
Output queue, drops input queue, drops	Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
5 minute input rate, 5 minute output rate	Average number of bits and packets transmitted per second in the last 5 minutes.
packets input	Total number of error-free packets received by the system.
bytes input	Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
no buffer	Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
Received broadcasts	Total number of broadcast or multicast packets received by the interface.
runts	Number of packets that are discarded because they are smaller than the medium's minimum packet size.
giants	Number of packets that are discarded because they exceed the medium's maximum packet size.
input errors	Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum may not balance with the other counts.
CRC	Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.
frame	Number of packets received incorrectly having a CRC error and a noninteger number of octets.
overrun	Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored	Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
abort	Illegal sequence of one bits the interface. This usually indicates a clocking problem between the interface and the data link equipment.
packets output	Total number of messages transmitted by the system.
bytes	Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns	Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
output errors	Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions	This feature is not applicable for ATM interfaces.
interface resets	Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
output buffer failures	Number of times that a packet was not output from the output hold queue because of a shortage of MEMD shared memory.
output buffers swapped out	Number of packets stored in main memory when the output queue is full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty.
restarts	Number of times the controller was restarted because of errors.

show network-clocks

To display the current configured and active network clock sources, use the show network-clocks privileged EXEC command.

show network-clocks

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.1	This command was introduced.

Usage Guidelines

This command applies to Voice over Frame Relay, Voice over ATM, and Voice over HDLC on the Cisco MC3810.

The Cisco MC3810 has a background task that verifies whether a valid clocking configuration exists every 120 seconds. If this task detects an error, you will be reminded every 120 seconds until the error is corrected. A clocking configuration error may be generated for various reasons. Using the show network-clocks command, you can display the clocking configuration status.

Examples

The following is sample output from the show network-clocks EXEC command.

Router# show network-clocks

Priority 1 clock source: ATM3/0/0

Priority 2 clock source: System clock

Priority 3 clock source: System clock

Priority 4 clock source: System clock

Current clock source:ATM3/0/0, priority:1

The following is sample output from the show network-clocks command on the Cisco MC3810:

Router# show network-clocks

Priority 1 clock source(inactive config): T1 0

Priority 1 clock source(active config) : T1 0

Clock switch delay: 10

Clock restore delay: 10

T1 0 is clocking system bus for 9319 seconds.

Run Priority Queue: controller0

In this display, inactive configuration is the new configuration that has been established. Active configuration is the run-time configuration. Should an error be made in the new configuration, the inactive and active configurations will be different. In the above example, the clock priority configuration is valid, and the system is being clocked as indicated.

The following is another sample output from the show network-clocks command:

Router# show network-clocks

Priority 1 clock source(inactive config) : T1 0

Priority 2 clock source(inactive config) : T1 1

Priority 1 clock source(active config) : T1 0

Clock switch delay: 10

Clock restore delay: 10

T1 0 is clocking system bus for 9319 seconds.

Run Priority Queue: controller0

In this display, the new clocking configuration has an error for controller T1 1. This is indicated by checking differences between the last valid configuration (active) and the new proposed configuration (inactive). The error may result from hardware (the system controller board or MFT) unable to support this mode, or controller T1 1 is currently configured as "clock source internal."

Since the active and inactive configurations are different, the system will periodically display the warning message about the wrong configuration.

Related Commands

Command	Description
network-clock-select (ATM)	Establishes the sources and priorities of the requisite clocking signals for an ATM-CES port adapter.

show pppatm summary

To display PPP over ATM (PPPoA) session counts, use the show pppatm summary command in EXEC mode.

show pppatm summary [interface atm interface-number[.subinterface-number]]

Syntax Description

interface atm interface-number.subinterface-number

(Optional) Specifies a particular ATM interface by interface number and possibly a subinterface number. A period (.) must precede the optional subinterface number.

Command Modes

EXEC

Command History

Release	Modification
12.2(13)T	This command was introduced.

Usage Guidelines

This command is useful for obtaining session counts, the state of the PPPoA sessions, and the interfaces they are running on.

This command gives a summary of the number of PPPoA sessions in each state and the session information of each individual session. If a subinterface number is given in the command, the output is a summary report of the PPPoA sessions in the subinterface. If a main interface number is given, the output will have the summary reports for each individual subinterface of that main interface as shown in the example that follows. If no interface is given, the output will contain the summary reports for each ATM interface on the router.

Examples

The following example displays PPPoA session counts and states for ATM interface 5/0:

Router# show pppatm summary interface atm 5/0

ATM5/0.3:

       0 sessions total

ATM5/0.6:

       1 in PTA (PTA) State

       1 sessions total

VPI     VCI     Conn ID         PPPoA ID        SSS ID          PPP ID        AAA ID   VT      VA/SID  State

  6     101       11            DA000009       BB000013       E5000017        C        1       1.1     PTA

Most of the messages displayed by the show pppatm summary command are self-explanatory. Table 39 describes the significant fields shown in the displays. Any data not described in Table 39 is used for internal debugging purposes.

Table 39 show pppatm summary Field Descriptions

Field	Description
VPI	Virtual path identifier of the permanent virtual circuit (PVC).
VCI	Virtual channel identifier of the PVC.
Conn ID	Unique connection identifier for the PPPoA session. This ID can be correlated with the unique ID in the show vpdn session command output for the forwarded sessions.
PPPoA ID	Internal identifier for the PPPoA session.
SSS ID	Internal identifier in the Subscriber Service Switch.
PPP ID	Internal identifier in PPP.
AAA ID	Authentication, authorization, and accounting (AAA) unique identifier for accounting records.
VT	Virtual template number used by the session.
VA/SID	PPPoA virtual access number for PPP Termination Aggregation (PTA) sessions, and switch identifier for forwarded sessions.
State	PPPoA state of the session.

Related Commands

Command	Description
clear pppatm interface atm	Clears PPP ATM sessions on an ATM interface.
debug pppatm	Enables reports for PPPoA events, errors, and states either globally or conditionally on an interface or VC.
show pppatm trace	Displays a sequence of PPPoA events, errors, and state changes when the debug pppatm command is enabled.

show pppatm trace

To display a sequence of PPP over ATM (PPPoA) events, errors, and state changes when the debug pppatm command is enabled, use the show pppatm trace command in privileged EXEC mode.

show pppatm trace [error | event | state] interface atm interface-number.[subinterface-number] vc {[vpi/]vci | virtual-circuit-name}

Syntax Description

error	(Optional) PPPoA events.
event	(Optional) PPPoA errors.
state	(Optional) PPPoA state.
interface atm interface-number	Specifies a particular ATM interface by interface number.
.subinterface-number	(Optional) Specifies a subinterface number preceded by a period.
vc [vpi/]vci	Virtual circuit (VC) keyword followed by a virtual path identifier (VPI), virtual channel identifier (VCI).. The absence of the "/" and a vpi value causes the vpi value to default to 0.
virtual-circuit-name	Name of the VC.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(13)T	This command was introduced.

Usage Guidelines

When the debug pppatm command has been enabled, this command displays messages from the specified permanent virtual circuit (PVC). If only one debug pppatm command keyword is supplied in the command, the report will display only the sequence of events for that particular debug type.

Examples

The following example traces the debugging messages supplied by the debug pppatm command on PVC 101. The report is used by Cisco technical personnel for diagnosing system problems.

Router# debug pppatm trace interface atm 1/0.10 vc 101

Router# debug pppatm state interface atm 1/0.10 vc 101

Router# debug pppatm event interface atm 1/0.10 vc 101

Router# show pppatm trace interface atm 1/0.10 vc 101

Event = Disconnecting

Event = AAA gets dynamic attrs

Event = AAA gets dynamic attrs

Event = SSS Cleanup

State = DOWN

Event = Up Pending

Event = Up Dequeued

Event = Processing Up

Event = Access IE allocated

Event = Set Pkts to SSS

Event = AAA gets retrieved attrs

Event = AAA gets nas port details

Event = AAA gets dynamic attrs

Event = AAA gets dynamic attrs

Event = AAA unique id allocated

Event = No AAA method list set

Event = SSS Request

State = NAS_PORT_POLICY_INQUIRY

Event = SSS Msg

State = PPP_START

Event = PPP Msg

State = LCP_NEGOTIATION

Event = PPP Msg

Event = Access IE get nas port

Event = AAA gets dynamic attrs

Event = AAA gets dynamic attrs

Event = PPP Msg

Event = Set Pkts to SSS

State = FORWARDED

Related Commands

Command	Description
clear pppatm interface atm	Clears PPP ATM sessions on an ATM interface.
debug pppatm	Enables reports for PPPoA events, errors, and states either globally or conditionally on an interface or VC.
show pppatm summary	Displays PPPoA session counts.

show smds addresses

To display the individual addresses and the interface they are associated with, use the show smds addresses privileged EXEC command.

show smds addresses

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show smds addresses command:

Router# show smds addresses

SMDS address - Serial0   c141.5555.1212.FFFF	

Table 40 describes the fields shown in the display.

Table 40 show smds addresses Field Descriptions 

Field	Description
Serial0	Interface to which this SMDS address has been assigned.
c141.5555.1212	SMDS address that has been assigned to the interface.

show smds map

To display all Switched Multimegabit Data Service (SMDS) addresses that are mapped to higher-level protocol addresses, use the show smds map privileged EXEC command.

show smds map

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show smds map command:

Router# show smds map

Serial0: ARP maps to e180.0999.9999.FFFF multicast

Serial0: IP maps to e180.0999.9999.FFFF	 172.16.42.112 255.255.255.0 multicast

Serial0: IPX 1ABC.000.0c00.d8db maps to c111.1111.1111.1111 -- dynamic, TTL: 4 min

Table 41 describes the fields shown in the output.

Table 41 show smds map Field Descriptions 

Field	Description
Serial0	Name of interface on which SMDS has been enabled.
ARP maps to	Higher-level protocol address that maps to this particular SMDS address.
e180.0999.9999.FFFF	SMDS address. Includes all SMDS addresses entered with either the smds static-map command (static) or smds multicast command (multicast).
172.16.42.112	IP address.
255.255.255.0	Subnet mask for the IP address.
static/dynamic	The address was obtained from a static map or dynamic map.
TTL	Time to live.

show smds traffic

To display statistics about Switched Multimegabit Data Service (SMDS) packets the router has received, use the show smds traffic privileged EXEC command.

show smds traffic

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show smds traffic command:

Router# show smds traffic

624363 Input packets

759695 Output packets

2 DXI heartbeat sent

0 DXI heartbeat received

0 DXI DSU polls received

0 DXI DSU polls sent

0 DXI invalid test frames

0 Bad BA size errors

0 Bad Header extension errors

65 Invalid address errors

1 Bad tag errors

Table 42 describes the fields shown in the output.

Table 42 show smds traffic Field Descriptions 

Field	Description
Input packets	Number of input packets.
Output packets	Number of output packets.
DXI heartbeat sent	Number of Data Exchange Interface (DXI) heartbeat polls transmitted.
DXI heartbeat received	Number of DXI heartbeat polls received.
DXI DSU polls sent	Number of DXI Data Service Unit (DSU) polls sent.
DXI DSU polls received	Number of DXI DSU polls received.
DXI invalid test frames	Number of invalid test frames seen.
Bad BA size errors	Number of packets that have a size less than 32 or greater than 9188 bytes.
DXI Header extension errors	Number of extended SMDS Interface Protocol (SIP) Layer 3 header errors.
DXI Invalid address errors	Number of address errors.
Bad tag errors	Status indicating the number of errors that occur when there is a mismatch between the Tag value in the header and the BeTag value in the trailer of an SMDS frame. This usually indicates that there is a misconfiguration (that is, a DXI is connected to a non-DXI) or that the SMDS data service unit (SDSU) is scrambling the Layer 2 protocol data units (PDUs).

show sscop

To show Service-Specific Connection-Oriented Protocol (SSCOP) details for all ATM interfaces, use the show sscop privileged EXEC command.

show sscop

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following is sample output from the show sscop command:

Router# show sscop

SSCOP details for interface ATM4/0

   Current State = Data Transfer Ready

   Send Sequence Number: Current = 2,  Maximum = 9

   Send Sequence Number Acked = 3

   Rcv Sequence Number: Lower Edge = 2, Upper Edge = 2, Max = 9

   Poll Sequence Number = 1876, Poll Ack Sequence Number = 2

   Vt(Pd) = 0

   Connection Control:  timer = 1000

   Timer currently Inactive

   Keep Alive Timer = 30000

   Current Retry Count = 0, Maximum Retry Count = 10

      Statistics -

      Pdu's Sent = 0, Pdu's Received = 0, Pdu's Ignored = 0

      Begin = 0/1, Begin Ack = 1/0, Begin Reject = 0/0

      End = 0/0, End Ack = 0/0

      Resync = 0/0, Resync Ack = 0/0

      Sequenced Data = 2/0, Sequenced Poll Data = 0/0

      Poll = 1591/1876, Stat = 0/1591, Unsolicited Stat = 0/0

      Unassured Data = 0/0, Mgmt Data = 0/0, Unknown Pdu's = 0

Table 43 describes the fields shown in the display. Interpreting this output requires a good understanding of the SSCOP; it is usually displayed by our technicians to help diagnose network problems.

Table 43 show sscop Field Descriptions 

Field	Description
SSCOP details for interface	Interface slot and port.
Current State	SSCOP state for the interface.
Send Sequence Number	Current and maximum send sequence number.
Send Sequence Number Acked	Sequence number of packets already acknowledged.
Rcv Sequence Number	Sequence number of packets received.
Poll Sequence Number	Current poll sequence number.
Poll Ack Sequence Number	Poll sequence number already acknowledged.
Vt(Pd)	Number of sequenced data (SD) frames sent, which triggers a sending of a Poll frame.
Connection Control	Timer used for establishing and terminating SSCOP.
Keep Alive Timer	Timer used to send keepalives on an idle link.
Current Retry Count	Current count of the retry counter.
Maximum Retry Count	Maximum value the retry counter can take.
Pdu's Sent	Total number of SSCOP frames sent.
Pdu's Received	Total number of SSCOP frames received.
Pdu's Ignored	Number of invalid SSCOP frames ignored.
Begin	Number of Begin frames sent/received.
Begin Ack	Number of Begin Ack frames sent/received.
Begin Reject	Number of Begin Reject frames sent/received.
End	Number of End frames sent/received.
End Ack	Number of End Ack frames sent/received.
Resync	Number of Resync frames sent/received.
Resync Ack	Number of Resync Ack frames sent/received.
Sequenced Data	Number of Sequenced Data frames sent/received.
Sequenced Poll Data	Number of Sequenced Poll Data frames sent/received.
Poll	Number of Poll frames sent/received.
Stat	Number of Stat frames sent/received.
Unsolicited Stat	Number of Unsolicited Stat frames sent/received.
Unassured Data	Number of Unassured Data frames sent/received.
Mgmt Data	Number of Mgmt Data frames sent/received.
Unknown Pdu's	Number of Unknown Pdu's frames sent/received.

show ssg auto-domain exclude-profile

To display the contents of an Autodomain exclude profile downloaded from the AAA server, use the show ssg auto-domain exclude-profile command in global configuration mode.

show ssg auto-domain exclude-profile

Syntax Description

This command has no arguments or keywords.

Command Modes

Global configuration

Command History

Release	Modification
12.2(4)B	This command was introduced.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

Use this command in global configuration mode to display the contents of an Autodomain exclude-profile downloaded from the AAA server. If any exclude entries downloaded from the AAA server are removed by the no exclude {apn | domain} name command, these entries will not be displayed by the show ssg auto-domain exclude-profile command.

Examples

The following sample displays the contents of an Autodomain exclude profile downloaded from the AAA server. The report is self-explanatory.

Router# show ssg auto-domain exclude-profile

Exclude APN Entries Downloaded:

apn1.gprs   apr2.com

Exclude Domain Entries Downloaded:

cisco.com   abcd.com

Related Commands

Command	Description
exclude	Configures the Autodomain exclusion list.
mode extended	Enables extended mode for SSG Autodomain.
nat user-address	Enables NAT on Autodomain tunnel service.
select	Configures the Autodomain selection mode.
show ssg auto-domain exclude-profile	Adds to the Autodomain download exclusion list.
ssg enable	Enables SSG functionality.

show ssg binding

To display service names that have been bound to interfaces and the IP addresses to which they have been bound, use the show ssg binding command in privileged EXEC mode.

show ssg binding [begin expression | exclude expression | include expression]

Syntax Description

begin	(Optional) Begin with the line that contains expression.
expression	(Optional) Word or phrase used to determine what lines will be shown.
exclude	(Optional) Exclude lines that contain expression.
include	(Optional) Include lines that contain expression.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to display services and the interfaces to which they have been bound.

Examples

The following example shows all service names that have been bound to interfaces:

Router# show ssg binding

WhipitNet            -> 192.168.1.1 (NHT)

Service1.com         -> 192.168.1.2 (NHT)

Service2.com         -> 192.168.1.3 (NHT)

Service3.com         -> 192.168.1.4 (NHT)

GoodNet              -> 192.168.2.1 

Perftest             -> 192.168.1.6 

Related Commands

Command	Description
clear ssg service	Removes a service.
show ssg service	Displays the information for a service.
ssg bind service	Specifies the interface for a service.

show ssg connection

To display the connections of a given host and a service name, use the show ssg connection command in privileged EXEC mode.

show ssg connection ip-address service-name [interface]

Syntax Description

ip-address	IP address of an active Service Selection Gateway (SSG) connection. This is always a subscribed host.
service-name	Name of an active SSG connection.
interface	(Optional) The IP address through which the host is connected.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(2)B	The interface argument was added for the SSG Host Key feature.
12.2(4)B	This command was modified to display information about SSG prepaid billing.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(13)T.
12.2(13)T	This command was modified for Cisco IOS Release 12.2(13)T.

Examples

Prepaid Service Based on Volume Example

The following example displays the SSG connection for a prepaid service that uses a volume-based quota:

Router# show ssg connection 19.1.1.19 InstMsg 

------------------------ConnectionObject Content ----------------------- 

User Name:

Owner Host:19.1.1.19 

Associated Service:InstMsg 

Connection State:0 (UP) 

Connection Started since:*00:25:58.000 UTC Tue Oct 23 2001 

User last activity at:*00:25:59.000 UTC Tue Oct 23 2001

Connection Traffic Statistics:

          Input Bytes = 0, Input packets = 0 

          Output Bytes = 0, Output packets = 0 

          Quota Type = 'VOLUME', Quota Value = 100 

Session policing disabled 

Prepaid Service Based on Time Example

The following example displays the SSG connection for a prepaid service that uses a time-based quota:

Router# show ssg connection 19.1.1.22 Prepaid-internet 

------------------------ConnectionObject Content ----------------------- 

User Name:Host 

Owner Host:19.1.1.22 

Associated Service:Prepaid-internet 

Connection State:0 (UP) 

Connection Started since:*00:34:06.000 UTC Tue Oct 23 2001 

User last activity at:*00:34:07.000 UTC Tue Oct 23 2001

Connection Traffic Statistics:

            Input Bytes = 0, Input packets = 0 

            Output Bytes = 0, Output packets = 0 

            Quota Type = 'TIME', Quota Value = 100 

Session policing disabled 

Autologin Service Example

The following example shows the service connection for the autologin service to host 10.3.6.1:

Router# show ssg connection 10.3.6.1 autologin

------------------------ ConnectionObject Content -----------------------

User Name:autologin

Owner Host:10.3.6.1

Associated Service:autologin

Connection State:0 (UP)

Connection Started since:

*20:41:26.000 UTC Fri Jul 27 2001

User last activity at:*20:41:26.000 UTC Fri Jul 27 2001

Connection Traffic Statistics:

        Input Bytes = 0 (HI = 0), Input packets = 0

        Output Bytes = 0 (HI = 0), Output packets = 0

Table 44 describes the significant fields shown in the displays.

Table 44 show ssg connection Field Descriptions 

Field	Description
User Name	Subscriber name supplied at authentication.
Owner Host	IP address of the subscribed host.
Associated Service	Service name of the connected service.
Connection State	State of activation (active or inactive).
Connection Started since	Time of host connection to the associated service.
User last activity at	Time of last data packet sent over this connection.
Input Bytes	Number of bytes received on this connection.
Input packets	Number of packets received on this connection.
Output Bytes	Number of bytes sent on this connection.
Output packets	Number of packets sent on this connection.
Quota Type	Form in which the quota value is expressed (time or volume).
Quota Value	Value of the quota (in bytes for volume or seconds for time).

Related Commands

Command	Description
clear ssg connection	Removes the connections of a given host and a service name.

show ssg direction

To display the direction of all interfaces for which a direction has been specified, use the show ssg direction command in privileged EXEC mode.

show ssg direction [begin expression | exclude expression | include expression]

Syntax Description

begin	(Optional) Begin with the line that contains expression.
expression	(Optional) Word or phrase used to determine what lines will be shown.
exclude	(Optional) Exclude lines that contain expression.
include	(Optional) Include lines that contain expression.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to show all interfaces that have been specified as uplinks or downlinks.

Examples

The following example shows the direction of all interfaces that have been specified as uplinks or downlinks.

Router# show ssg direction

ATM0/0/0.10: Uplink

BVI1: Downlink

FastEthernet0/0/0: Uplink

Related Commands

Command	Description
ssg bind direction	Specifies an interface as a downlink or uplink interface.

show ssg host

To display the information about a subscriber and current connections of the subscriber, use the show ssg host command in privileged EXEC mode.

show ssg host [ip-address [interface] | username]

Syntax Description

ip-address	(Optional) IP address of the host.
interface	(Optional) Interface through which the host is connected.
username	(Optional) Displays the usernames logged into the active hosts.

Defaults

If no argument is provided, all current connections are displayed.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(2)B	The interface argument was added.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Examples

The following example shows all active hosts:

Router# show ssg host

1:10.3.1.1         [Host-Key 70.13.60.3:64]

2:10.3.6.1         [Host-Key 70.13.60.3:65] 

### Active HostObject Count:2

The following example shows information about host 10.3.1.1:

Router# show ssg host 10.3.1.1

------------------------ HostObject Content -----------------------

Activated:TRUE

Interface:Virtual-Access1

User Name:pppoauser

Host IP:10.3.1.1

Msg IP:0.0.0.0 (0)

Host DNS IP:0.0.0.0

Maximum Session Timeout:0 seconds

Host Idle Timeout:0 seconds

Class Attr:NONE

User logged on since:*20:59:51.000 UTC Fri Jul 27 2001

User last activity at:*20:59:51.000 UTC Fri Jul 27 2001

Default Service:NONE

DNS Default Service:NONE

Active Services:autologon;

AutoService:autologon;

Subscribed Services:

The following example shows two host objects with the same IP address:

Router# show ssg host 10.3.1.1

SSG:Overlapping hosts for IP 10.3.1.1 at interfaces:FastEthernet0/0/0

Virtual-Access1

In this case, use the interface argument to uniquely identify the host:

Router# show ssg host 10.3.1.1 FastEthernet0/0/0

Note that the output produced by this command is the same as that produced by the command without the interface argument. The interface argument is used only to uniquely identify a host when there are overlapping host IP addresses.

The following example shows the usernames logged in to the active hosts:

RouterA# show ssg host username

   1:10.3.1.1        (active) Host name:pppoauser

   2:10.3.6.1        (active) Host name:ssguser2

### Total HostObject Count(including inactive hosts):2

Related Commands

Command	Description
clear ssg host	Removes or disables a given host or subscriber.

show ssg next-hop

To display the next-hop table, use the show ssg next-hop command in privileged EXEC mode.

show ssg next-hop [begin expression | exclude expression | include expression]

Syntax Description

begin	(Optional) Displays lines beginning with the line that contains expression.
expression	(Optional) Word or phrase used to determine what lines will be shown.
exclude	(Optional) Excludes lines that contain expression.
include	(Optional) Includes lines that contain expression.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to display all next-hop IP addresses.

Examples

The following example shows the next-hop table:

Router# show ssg next-hop

Next hop table loaded from profile prof-nhg:

        WhipitNet            -> 192.168.1.6

        Service1.com         -> 192.168.1.3

        Service2.com         -> 192.168.1.2

        Service3.com         -> 192.168.1.1

        GoodNet              -> 192.168.1.2

        Perftest             -> 192.168.1.5

End of next hop table.

Related Commands

Command	Description
clear ssg next-hop	Removes the next-hop table.
ssg next-hop download	Downloads the next-hop table from a RADIUS server.

show ssg open-garden

To display a list of all configured open garden services, use the show ssg open-garden command in privileged EXEC mode.

show ssg open-garden

Syntax Description

This command has no keywords or arguments.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(5)DC	This command was introduced on the Cisco 6400 series node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Examples

In the following example, all configured open garden services are displayed:

Router# show ssg open-garden

nrp1-nrp2_og1 

nrp1-nrp2_og2 

nrp1-nrp2_og3 

nrp1-nrp2_og4 

Related Commands

Command	Description
local-profile	Configures a local service profile.
ssg open-garden	Designates a service, defined in a local service profile, as an open garden service.
ssg service-search-order	Specifies the order in which SSG searches for a service profile.

show ssg pass-through-filter

To display the downloaded filter for transparent pass-through, use the show ssg pass-through-filter command in privileged EXEC mode.

show ssg pass-through-filter [begin expression | exclude expression | include expression]

Syntax Description

begin	(Optional) Begin with the line that contains expression.
expression	(Optional) Word or phrase used to determine what lines will be shown.
exclude	(Optional) Exclude lines that contain expression.
include	(Optional) Include lines that contain expression.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to display the downloaded transparent pass-through filter. The filter prevents pass-through traffic from accessing the specified IP address and subnet mask combinations. The filter is set using the ssg pass-through command.

To display a filter defined on the command line, use the show running-config command.

Examples

The following example shows the pass-through filter:

Router# show ssg pass-through-filter

        Service name:  filter01

        Password:      cisco

        Direction:     Uplink

Extended IP access list (SSG ACL)

    permit tcp 172.16.6.0 0.0.0.255 any eq telnet

    permit tcp 172.16.6.0 0.0.0.255 192.168.250.0 0.0.0.255 eq ftp

Related Commands

Command	Description
clear ssg pass-through-filter	Removes the downloaded filter for transparent pass-through.
ssg pass-through	Enables transparent pass-through.

show ssg pending-command

To display current pending commands, such as next-hop or filters, use the show ssg pending-command command in privileged EXEC mode.

show ssg pending-command

Syntax Description

This command has no keywords or arguments.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to display the current pending commands.

Examples

The following example shows the pending commands:

Router# show ssg pending-command

SSG pending command list:

    ssg bind service Service1.com 192.168.103.1

    ssg bind service Perftest206 192.168.104.5

Related Commands

Command	Description
clear ssg pending-command	Removes all pending commands.

show ssg port-map ip

To display information on a particular port bundle, use the show ssg port-map ip command in privileged EXEC mode.

show ssg port-map ip ip-address port port-number

Syntax Description

ip-address	IP address used to identify the port bundle.
port port-number	TCP port number used to identify the port bundle.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(2)B	This command was introduced on the Cisco 6400 series.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

This command displays the following information about a port bundle:

•Port maps in the port bundle

•IP address of the subscriber

•Interface through which the subscriber is connected

Examples

The following output shows the Virtual-Access2 interface connected to the subscriber:

Router# show ssg port-map ip 10.13.60.2 port 64

State = IN-USE

Subscriber Address = 10.10.3.1

Downlink Interface = Virtual-Access2

Port-mappings:-

Subscriber Port:   3271                Mapped Port:   1024

Subscriber Port:   3272                Mapped Port:   1025

Subscriber Port:   3273                Mapped Port:   1026

Subscriber Port:   3274                Mapped Port:   1027

Subscriber Port:   3275                Mapped Port:   1028

Table 45 describes the significant fields shown in the display.

Table 45 show ssg port-map ip Field Descriptions 

Field	Description
State	Port bundle status.
Subscriber Address	Subscriber IP address.
Downlink Interface	Interface through which the subscriber is connected.
Port-Mappings	Port maps in the port bundle.
Subscriber Port	Subscriber port number.
Mapped Port	Port assigned by SSG.

Related Commands

Command	Description
show ssg port-map status	Displays information on port bundles.

show ssg port-map status

To display information on port bundles, use the show ssg port-map status command in privileged EXEC mode.

show ssg port-map status [free | reserved | inuse]

Syntax Description

free	(Optional) Lists the port bundles that are in the "free" state for each bundle group.
reserved	(Optional) Lists the port bundles that are in the "reserved" state for each bundle group. Also displays the associated subscriber IP address and interface for each port bundle.
inuse	(Optional) Lists the port bundles that are in the "inuse" state for each bundle group. Also displays the associated subscriber IP address and interface for each port bundle.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(2)B	This command was introduced on the Cisco 6400 series.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

Entered without any keywords, the command displays a summary of all port-bundle groups, including the following information:

•A list of port-bundle groups

•Port-bundle length

•Number of free, reserved, and in-use port bundles in each group

Examples

Display All Bundles Example

The following example shows output for the show ssg port-map status command with no keywords:

Router# show ssg port-map status

Bundle-length = 4

Bundle-groups:-

IP Address              Free Bundles            Reserved Bundles         In-use Bundles

10.13.60.2                      4032                    0                      0

Table 46 describes the significant fields shown in the display.

Table 46 show ssg port-map status Field Descriptions 

Field	Description
Bundle-length	The bundle-length value indicates the number of ports per bundle and the number of bundles per bundle group.
Bundle-groups	List of bundle groups.
IP Address	IP address of a bundle group.
Free Bundles	Number of free bundles in the specified bundle group.
Reserved Bundles	Number of reserved bundles in the specified bundle group.
In-use Bundles	Number of in-use bundles in the specified bundle group.

Display In-Use Bundles Example

The following example shows output for the show ssg port-map status command with the inuse keyword:

Router# show ssg port-map status inuse

Bundle-group 70.13.60.2 has the following in-use port-bundles:-

Port-bundle             Subscriber Address              Interface

64                      10.10.3.1                       Virtual-Access2

Table 47 describes the significant fields shown in the display.

Table 47 show ssg port-map status inuse Field Descriptions 

Field	Description
Port-bundle	Port-bundle number.
Subscriber Address	Subscriber IP address of the subscriber.
Interface	Interface through which the subscriber is connected.

Related Commands

Command	Description
show ssg port-map ip	Displays information on a particular port bundle.

show ssg radius-proxy address-pool

To display the pool of IP addresses configured for a router or for a specific domain, use the show ssg radius-proxy address-pool command in privileged EXEC mode.

show ssg radius-proxy address-pool [domain domain-name] [free | inuse]

Syntax Description

domain	(Optional) IP addresses configured for a specific domain.
domain-name	(Optional) Name of the domain to display.
free	(Optional) IP addresses currently available in the free pool.
inuse	(Optional) IP addresses currently in use.

Defaults

If no domain name is provided, the command displays information for all IP addresses configured in an address pool.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(4)B	This command was introduced.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

Use this command to display the IP address pools configured for a router or for a specific domain. You can also display which IP addresses are available or are in use.

Examples

The following example shows how to display information for IP addresses in the IP address pool:

Router# show ssg radius-proxy address-pool

Global Pool:  Free Addresses= 10234   Inuse Addresses= 0

The following example shows how to display information about the IP addresses in the IP address pool in the domain called "ssg.com":

Router# show ssg radius-proxy address-pool domain ssg.com

Domain Pool(ssg.com):  Free Addresses= 20   Inuse Addresses= 10

The following example shows how to display information about the IP addresses in the IP address pool for the domain called "ssg.com" that are currently in use:

Router# show ssg radius-proxy address-pool domain cisco inuse

Inuse Addresses in Domain Pool(ssg.com):10

10.1.5.1

10.1.5.2

10.1.5.3

10.1.5.4

10.1.5.5

19.1.5.6

10.1.5.7

10.1.5.8

10.1.5.9

10.1.5.10

The following example shows how to display information about the IP addresses in the IP address pool for the domain called "ssg.com" that are currently available:

Router# show ssg radius-proxy address-pool domain ssg.com free 

Free Addresses in Domain Pool(ssg.com):20

10.1.5.11

10.1.5.12

10.1.5.13

10.1.5.14

10.1.5.15

10.1.5.16

10.1.5.17

10.1.5.18

10.1.5.19

10.1.5.20

10.1.5.21

10.1.5.22

10.1.5.23

10.1.5.24

19.1.5.25

10.1.5.26

10.1.5.27

10.1.5.28

10.1.5.29

10.1.5.30

Related Commands

Command	Description
address-pool	Defines local IP pools to be used by SSG to assign IP addresses to users for which SSG is acting as a RADIUS client.
clear ssg radius-proxy client-address	Clears all hosts connected to a specific RADIUS client.
clear ssg radius-proxy nas-address	Clears all hosts connected to a specific NAS.
clear ssg service	Removes a service.
forward accounting-start-stop	Proxies accounting start, stop, and update packets generated by any RADIUS clients to the AAA server.
idle-timeout (SSG)	Configures a host object timeout value.
server-port	Defines the ports for the SSG RADIUS proxy.
show ssg binding	Displays service names that have been bound to interfaces and the interfaces to which they have been bound.
ssg bind service	Specifies the interface for a service.
ssg enable	Enables SSG.
ssg radius-proxy	Enables SSG RADIUS Proxy.

show ssg service

To display the information for a service, use the show ssg service command in privileged EXEC mode.

show ssg service [service-name [begin expression | exclude expression | include expression]]

Syntax Description

service-name	(Optional) Name of an active Service Selection Gateway (SSG) service.
begin	(Optional) Begin with the line that contains expression.
expression	(Optional) Word or phrase used to determine what lines will be shown.
exclude	(Optional) Exclude lines that contain expression.
include	(Optional) Include lines that contain expression.

Defaults

If no service name is provided, the command displays information for all services.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(3) DC	This command was introduced on the Cisco 6400 node route processor.
12.1(1) DC1	The output of this command was modified on the Cisco 6400 node route processor to display the following Service-Info Attributes when they are present in the proxy RADIUS service profile: •Service-Defined Cookie •Full Username Attribute
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to display connection information for a service.

Examples

The following example shows the information for the service called "serv1-proxy":

Router# show ssg service serv1-proxy

------------------------ ServiceInfo Content -----------------------

Uplink IDB:

Name:serv1-proxy

Type:PROXY

Mode:CONCURRENT

Service Session Timeout:0 seconds

Service Idle Timeout:0 seconds

Class Attr:NONE

Authentication Type:CHAP

Reference Count:1

Next Hop Gateway Key:my-key

DNS Server(s):Primary:10.13.1.5

Radius Server:IP=10.13.1.2, authPort=1645, acctPort=1646, secret=my-secret

Included Network Segments:

         10.13.0.0/255.255.0.0

Excluded Network Segments:

Full User Name Used

Service Defined Cookie exist

Domain List:service1.com;

Active Connections:

         1   :Virtual=255.255.255.255, Subscriber=10.20.10.2

------------------------ End of ServiceInfo Content ----------------

Related Commands

Command	Description
clear ssg service	Removes a service.
show ssg binding	Displays service names that have been bound to interfaces and the interfaces to which they have been bound.
ssg bind service	Specifies the interface for a service.

show ssg tcp-redirect group

To display information about the captive portal groups and their networks associated with those portal groups, use the show ssg tcp-redirect group command in privileged EXEC mode.

show ssg tcp-redirect group [group-name]

Syntax Description

group-name

(Optional) The previously defined name for the captive portal group.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(4)B	This command was introduced. This command replaced the show ssg http-redirect group command.
12.2(13)T	This command was integrated into Cisco IOS Release 12.2(13)T.

Usage Guidelines

Use this command to display information about the captive portal groups and their associated networks defined in your system.

If you omit the optional group-name argument, this command displays a list of all defined captive portal groups and the networks associated with the captive portal groups. If you specify the group-name argument, this command displays information about that group and its associated networks.

Examples

The following example shows how to display a list of all of the defined captive portal groups:

Router# show ssg tcp-redirect group

Current TCP redirect groups:

RedirectServer

CaptivateServer

SMTPServer

SSD

Unauthenticated user redirect group:RedirectServer

Default service redirect group:SSD

SMTP forwarding group:SMTPServer, for all users

Default initial captivation group:CaptivateServer,

for 10 seconds

Default advertising  captivation group:CaptivateServer,

for 30 seconds approximately every 3600 seconds

Table 48 describes the significant fields shown in the display above.

Table 48 show ssg tcp-redirect group Field Descriptions 

Field	Description
Current TCP redirect groups:	List of all TCP-redirect groups.
Default service redirect group: SSD	Default service redirect group.
SMTP forwarding group: SMTPServer, for all users	SMTP redirection settings.
Default initial captivation group: CaptivateServer, for 10 seconds	Default initial captivation group, name of captivation, and duration of captivation.
Default advertising captivation group: CaptivateServer, for 30 seconds approximately every 3600 seconds	Default advertising captivation group, name of captivation group, duration, and frequency of advertising captivation.

The following example shows how to display a detailed description of the captive portal group called "RedirectServer":

Router# show ssg tcp-redirect group RedirectServer

TCP redirect group RedirectServer:

Showing all TCP servers (Address, Port):

  10.2.36.253, 8080, FastEthernet0/0

Networks to redirect to (network-list RedirectNw):

  172.16.10.0 /24

  172.20.0.0 /16

TCP port to redirect:

  80

Table 49 describes the significant fields shown in the display.

Table 49 show ssg tcp-redirect group group-name Field Descriptions 

Field	Description
Showing all TCP servers (Address, Port):	List of all servers.
10.2.36.253	Server IP address.
8080	Server port number.
FastEthernet0/0	Interface on which this server is reachable.
Networks to redirect to	List of networks.
(network-list RedirectNw):	Network list name.
TCP port to redirect:	Name of port-list (if port-list is used).

Related Commands

Command	Description
debug ssg tcp-redirect	Turns on debug information for the SSG TCP Redirect for Services feature.
network (ssg-redirect)	Adds an IP address to a named network list.
network-list	Defines a list of one or more IP networks that make up a named network list.
port (ssg-redirect)	Adds a TCP port to a named port list.
port-list	Defines a list of one or more TCP ports that make up a named port list and enters SSG-redirect-port configuration mode.
redirect captivate advertising default group	Configures the default captive portal group, duration, and frequency for advertising.
redirect captivate initial default group duration	Selects a default captive portal group and duration of the initial captivation of users on Account Logon.
redirect port to	Marks a TCP port or named TCP port list for SSG TCP redirection.
redirect smtp group	Selects a captive portal group for redirection of SMTP traffic.
redirect unauthorized-service to	Sets a list of destination IP networks that can be redirected by a specified named captive portal group.
redirect unauthenticated-user to	Redirects the traffic from authenticated users to a specified captive portal group.
server (SSG)	Adds a server to a captive portal group.
server-group	Defines the group of one or more servers that make up a named captive portal group and enters SSG-redirect-group configuration mode.
show tcp-redirect mappings	Displays information about the TCP redirect mappings for hosts within your system.
ssg enable	Enables SSG.
ssg tcp-redirect	Enables SSG TCP redirect and enters SSG-redirect mode.

show ssg vc-service-map

To display virtual circuit (VC)-to-service-name mappings, use the show ssg vc-service-map command in privileged EXEC mode.

show ssg vc-service-map [vpi/vci | service service-name]

Syntax Description

vpi/vci	(Optional) Virtual path identifier (VPI)/virtual channel identifier (VCI) value, including the slash; for example, 3/33.
service	(Optional) Displays the VCs mapped to a service name.
service-name	(Optional) Service name.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)DC	This command was introduced on the Cisco 6400 node route processor.
12.2(4)B	This command was integrated into Cisco IOS Release 12.2(4)B.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

Use this command to display VC-to-service-name mappings.

Examples

The following example shows the VCs mapped to the service name "Worldwide":

Router# show ssg vc-service-map service Worldwide

Interface  From       To         Service Name                Type

All        3  /33     None       Worldwide                   non-exclusive

Related Commands

Command	Description
ssg vc-service-map	Maps VCs to service names.

show sss session

To display Subscriber Service Switch session status, use the show sss session command in privileged EXEC mode.

show sss session [all]

Syntax Description

all	(Optional) Provides an extensive report about the Subscriber Service Switch sessions.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(13)T	This command was introduced.

Usage Guidelines

Use this command to verify correct operation of PPP connections in the Subscriber Service Switch environment.

Examples

The following sample output from the show sss session command provides a basic report of Subscriber Service Switch session activity:

Router# show sss session

Current SSS Information: Total sessions 9

Uniq ID Type       State         Service      Identifier           Last Chg

9       PPPoE/PPP  connected     VPDN         nobody3@cisco.com        00:02:36

10      PPPoE/PPP  connected     VPDN         nobody3@cisco.com        00:01:52

11      PPPoE/PPP  connected     VPDN         nobody3@cisco.com        00:01:52

3       PPPoE/PPP  connected     VPDN         user3@cisco.com          2d21h   

6       PPPoE/PPP  connected     Local Term   user1                  00:03:35

7       PPPoE/PPP  connected     Local Term   user2                  00:03:35

8       PPPoE/PPP  connected     VPDN         nobody3@cisco.com        00:02:36

2       PPP        connected     Local Term   johndoe                00:05:06

4       PPP        connected     VPDN         nobody2@cisco.com        00:06:52

The following sample output from the show sss session all command provides a more extensive report of Subscriber Service Switch session activity:

Router# show sss session all

Current SSS Information: Total sessions 9

SSS session handle is 40000013, state is connected, service is VPDN

Unique ID is 9

SIP subscriber access type(s) are PPPoE/PPP

Identifier is nobody3@cisco.com

Last Changed 00:02:49

Root SIP Handle is DF000010, PID is 49

AAA unique ID is 10

Current SIP options are Req Fwding/Req Fwded

SSS session handle is B0000017, state is connected, service is VPDN

Unique ID is 10

SIP subscriber access type(s) are PPPoE/PPP

Identifier is nobody3@cisco.com

Last Changed 00:02:05

Root SIP Handle is B9000015, PID is 49

AAA unique ID is 11

Current SIP options are Req Fwding/Req Fwded

SSS session handle is D6000019, state is connected, service is VPDN

Unique ID is 11

SIP subscriber access type(s) are PPPoE/PPP

Identifier is nobody3@cisco.com

Last Changed 00:02:13

Root SIP Handle is D0000016, PID is 49

AAA unique ID is 12

Current SIP options are Req Fwding/Req Fwded

SSS session handle is 8C000003, state is connected, service is VPDN

Unique ID is 3

SIP subscriber access type(s) are PPPoE/PPP

Identifier is user3@cisco.com

Last Changed 2d21h   

Root SIP Handle is D3000002, PID is 49

AAA unique ID is 3

Current SIP options are Req Fwding/Req Fwded

SSS session handle is BE00000B, state is connected, service is Local Term

Unique ID is 6

SIP subscriber access type(s) are PPPoE/PPP

Identifier is user1

Last Changed 00:03:56

Root SIP Handle is A9000009, PID is 49

AAA unique ID is 7

Current SIP options are Req Fwding/Req Fwded

SSS session handle is DC00000D, state is connected, service is Local Term

Unique ID is 7

SIP subscriber access type(s) are PPPoE/PPP

Identifier is user2

Last Changed 00:03:57

Root SIP Handle is 2C00000A, PID is 49

AAA unique ID is 8

Current SIP options are Req Fwding/Req Fwded

SSS session handle is DB000011, state is connected, service is VPDN

Unique ID is 8

SIP subscriber access type(s) are PPPoE/PPP

Identifier is nobody3@cisco.com

Last Changed 00:02:58

Root SIP Handle is 1000000F, PID is 49

AAA unique ID is 9

Current SIP options are Req Fwding/Req Fwded

SSS session handle is 3F000007, state is connected, service is Local Term

Unique ID is 2

SIP subscriber access type(s) are PPP

Identifier is johndoe

Last Changed 00:05:30

Root SIP Handle is 8A000009, PID is 92

AAA unique ID is 1

Current SIP options are Req Fwding/Req Fwded

SSS session handle is 97000005, state is connected, service is VPDN

Unique ID is 4

SIP subscriber access type(s) are PPP

Identifier is nobody2@cisco.com

Last Changed 00:07:16

Root SIP Handle is 32000000, PID is 92

AAA unique ID is 5

Current SIP options are Req Fwding/Req Fwded

Most of the messages displayed by the show sss session and show sss session all commands are self-explanatory. Table 50 describes the significant fields shown in the displays. Any data not described in Table 50 is used for internal debugging purposes.

Table 50 show sss session Field Descriptions

Field	Description
Unique ID (Uniq ID)	The unique identifier used to correlate this particular session with the sessions retrieved from other show commands or debug command traces.
Type	Access protocols relevant to this session.
State	Status of the connection, which can be one of the following states: •connected—The session has been established. •wait-for-req—Waiting for request. •wait-for-auth—Waiting for authorization. •wait-for-fwd—Waiting to be forwarded; for example, waiting for virtual private dialup network (VPDN) service.
Service	Type of service given to the user.
Identifier	A string identifying the user. This identifier may either be the username, or the name used to authorize the session.
Last Chg (Last Changed)	Time interval in in hh:mm:dd since the service for this session was last changed.

Related Commands

Command	Description
show vpd