-
Cisco IOS Wide-Area Networking Command Reference
-
Introduction
-
A through C
-
D through E
-
fdl through frame-relay lapf n200
-
frame-relay lapf n201 through fr-atm connect dlci
-
H through L
-
M through R
-
sequencing through show mpls l2transport vc
-
show smds addresses through vpls-id
-
x25 accept-reverse through x25 pvc (XOT)
-
x25 pvc rbp local through xot access-group
-
Table Of Contents
show ethernet service instance
show ethernet service interface
show frame-relay end-to-end keepalive
show frame-relay ip tcp header-compression
show frame-relay qos-autosense
show l2tun counters tunnel l2tp
show mpls l2transport checkpoint
sequencing
To configure the direction in which sequencing is enabled for data packets in a Layer 2 pseudowire, use the sequencing command in pseudowire class configuration mode. To remove the sequencing configuration from the pseudowire class, use the no form of this command.
sequencing {transmit | receive | both | resync number}
no sequencing {transmit | receive | both | resync number}
Syntax Description
Command Default
Sequencing is disabled.
Command Modes
Pseudowire class configuration
Command History
Usage Guidelines
When you enable sequencing using any of the available options, the sending of sequence numbers is automatically enabled and the remote provider edge (PE) peer is requested to send sequence numbers. Out-of-order packets received on the pseudowire are dropped only if you use the sequencing receive or sequencing both command.
If you enable sequencing for Layer 2 pseudowires on the Cisco 7500 series routers and you issue the ip cef distributed command, all traffic on the pseudowires is switched through the line cards.
It is useful to specify the resync keyword for situations when the disposition router receives many out-of-order packets. It allows the router to recover from situations where too many out-of-order packets are dropped.
Examples
The following example shows how to enable sequencing in data packets in Layer 2 pseudowires that were created from the pseudowire class named "ether-pw" so that the Sequence Number field is updated in tunneled packet headers for data packets that are both sent and received over the pseudowire:
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation mplsRouter(config-pw)# sequencing bothThe following example shows how to enable the disposition router to reset packet sequencing after it receives 1000 out-of-order packets:
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation mplsRouter(config-pw)# sequencing bothRouter(config-pw)# sequencing resync 1000Related Commands
service pad
To enable all packet assembler/disassembler (PAD) commands and connections between PAD devices and access servers, use the service pad command in global configuration mode. To disable this service, use the no form of this command.
service pad [cmns] [from-xot] [to-xot]
no service pad [cmns] [from-xot] [to-xot]
Syntax Description
cmns
(Optional) Specifies sending and receiving PAD calls over CMNS.
from-xot
(Optional) Accepts XOT to PAD connections.
to-xot
(Optional) Allows outgoing PAD calls over XOT.
Command Default
All PAD commands and associated connections are enabled. PAD services over XOT or CMNS are not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The keywords from-xot and to-xot enable PAD calls to destinations that are not reachable over physical X.25 interfaces, but instead over TCP tunnels. This feature is known as PAD over XOT (X.25 over TCP).
Examples
If the service pad command is disabled, the pad EXEC command and all PAD related configurations, such as X.29, are unrecognized, as shown in the following example:
Router(config)# no service padRouter(config)# x29 ?% Unrecognized commandRouter(config)# exitRouter# pad ?% Unrecognized commandIf the service pad command is enabled, the pad EXEC command and access to an X.29 configuration are granted as shown in the following example:
Router# config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# service padRouter(config)# x29 ?access-list Define an X.29 access listinviteclear-time Wait for response to X.29 Invite Clear messageprofile Create an X.3 profileRouter# pad ?WORD X121 address or name of a remote systemIn the following example, PAD services over CMNS are enabled:
! Enable CMNS on a nonserial interfaceinterface ethernet0cmns enable!!Enable inbound and outbound PAD over CMNS serviceservice pad cmns!! Specify an X.25 route entry pointing to an interface's CMNS destination MAC addressx25 route ^2193330 interface Ethernet0 mac 00e0.b0e3.0d62Router# show x25 vcSVC 1, State: D1, Interface: Ethernet0Started 00:00:08, last input 00:00:08, output 00:00:08Line: 0 con 0 Location: console Host: 2193330connected to 2193330 PAD <--> CMNS Ethernet0 00e0.b0e3.0d62Window size input: 2, output: 2Packet size input: 128, output: 128PS: 2 PR: 3 ACK: 3 Remote PR: 2 RCNT: 0 RNR: noP/D state timeouts: 0 timer (secs): 0data bytes 54/19 packets 2/3 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0Related Commands
service pad from-xot
To permit incoming X.25 over TCP (XOT) calls to be accepted as a packet assembler/disassembler (PAD) session, use the service pad from-xot command in global configuration mode. To disable this service, use the no form of this command.
service pad from-xot
no service pad from-xot
Syntax Description
This command has no arguments or keywords.
Defaults
Incoming XOT connections are ignored.
Command Modes
Global configuration
Command History
Usage Guidelines
If the service pad from-xot command is enabled, the calls received using the XOT service may be accepted for processing a PAD session.
Examples
The following example prevents incoming XOT calls from being accepted as a PAD session:
no service pad from-xotRelated Commands
service pad to-xot
To permit outgoing PAD sessions to use routes to an XOT destination, use the service pad to-xot command in global configuration mode. To disable this service, use the no form of this command.
service pad to-xot
no service pad to-xot
Syntax Description
This command has no arguments or keywords.
Defaults
XOT routes pointing to XOT are not considered.
Command Modes
Global configuration
Command History
Examples
If the service pad to-xot command is enabled, the configured routes to XOT destinations may be used when the router determines where to send a PAD Call, as shown in the following example:
service pad to-xotRelated Commands
service translation
To enable upper layer user protocol encapsulation for Frame Relay-to-ATM Service Interworking (FRF.8) feature, which allows mapping between encapsulated ATM protocol data units (PDUs) and encapsulated Frame Relay PDUs, use the service translation command in FRF.8 connect configuration mode. To disable upper layer user protocol encapsulation, use the no form of this command.
service translation
no service translation
Syntax Description
This command has no arguments or keywords.
Defaults
The default state is service translation.
Command Modes
FRF.8 connect configuration
Command History
Usage Guidelines
The no service translation command disables mapping between encapsulated ATM PDUs and encapsulated Frame Relay PDUs.
Examples
The following example shows an FRF.8 configuration with service translation disabled:
Router# show running-configBuilding configuration...Current configuration:connect service-1 Serial1/0 16 ATM3/0 1/32 service-interworkingno service translationefci-bit map-fecnThe following example shows how to configure service translation on the connection named service-1:
Router(config)# connect service-1 serial1/0 16 ATM3/0 1/32 service-interworkingRouter(config-frf8)# service translationRelated Commands
set fr-fecn-becn
To enable forward explicit congestion notification (FECN) and backward explicit congestion notification (BECN) with Frame Relay over MPLS, use the set fr-fecn-becn command in policy map class configuration mode. To disable the configuration notification, use the no form of this command.
set fr-fecn-becn percent
no set fr-fecn-becn percent
Syntax Description
Defaults
Frame Relay does not perform FECN and BECN marking.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
This command works only with Frame Relay over MPLS.
If you configure FECN and BECN bit marking, you cannot configure bandwidth or priority.
Examples
The following example enables marking the FECN and BECN bits when 20 percent of the queue is used:
Router(config)# policy-map policy1Router(config-pmap)# class class1Router(config-pmap-c)# shape 80000Router(config-pmap-c)# set fr-fecn-becn 20Related Commands
shape fr-voice-adapt
To enable Frame Relay voice-adaptive traffic shaping, use the shape fr-voice-adapt command in policy-map class configuration mode. To disable Frame Relay voice-adaptive traffic shaping, use the no form of this command.
shape fr-voice-adapt [deactivation seconds]
no shape fr-voice-adapt
Syntax Description
Defaults
Frame Relay voice-adaptive traffic shaping is not enabled.
Seconds: 30Command Modes
Policy-map class configuration
Command History
Usage Guidelines
Frame Relay voice-adaptive traffic shaping enables a router to reduce the permanent virtual circuit (PVC) sending rate to the minimum CIR (minCIR) whenever packets (usually voice) are detected in the low latency queueing priority queue or H.323 call setup signaling packets are present. When there are no packets in priority queue and signaling packets are not present for a configured period of time, the router increases the PVC sending rate from minCIR to CIR to maximize throughput.
The shape fr-voice-adapt command can be configured only in the class-default class. If you configure the shape fr-voice-adapt command in another class, the associated Frame Relay map class will be rejected when you attach it to the interface.
Frame Relay voice-adaptive traffic shaping can be used with other types of adaptive traffic shaping. For example, when both voice-adaptive traffic shaping and adaptive shaping based on interface congestion are configured, the sending rate will change to minCIR if there are packets in the priority queue or the interface queue size exceeds the configured threshold.
Note
Although the priority queue is generally used for voice traffic, Frame Relay voice-adaptive traffic shaping will respond to any packets (voice or data) in the priority queue.
In order to use Frame Relay voice-adaptive traffic shaping, you must have low latency queueing and traffic shaping configured using the Modular QoS CLI.
Examples
The following example shows the configuration of Frame Relay voice-adaptive traffic shaping and fragmentation. With this configuration, priority-queue packets or H.323 call setup signaling packets destined for PVC 100 will result in the reduction of the sending rate from CIR to minCIR and the activation of FRF.12 end-to-end fragmentation. If signaling packets and priority-queue packets are not detected for 50 seconds, the sending rate will increase to CIR and fragmentation will be turned off.
interface serial0encapsulation frame-relayframe-relay fragmentation voice-adaptive deactivation 50frame-relay fragment 80 end-to-endframe-relay interface-dlci 100class voice_adaptive_class!map-class frame-relay voice_adaptive_classframe-relay fair-queueservice-policy output shapeclass-map match-all voicematch access-group 102class-map match-all datamatch access-group 101policy-map vatsclass voicepriority 10class databandwidth 10policy-map shapeclass class-defaultshape average 60000shape adaptive 30000shape fr-voice-adapt deactivation 50service-policy vatsRelated Commands
show acircuit checkpoint
To display checkpointing information for each attachment circuit (AC), use the show acircuit checkpoint command in privileged EXEC mode.
show acircuit checkpoint
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used for interface-based attachment circuits. For Frame Relay and ATM circuits, use the following commands to show redundancy information:
•
•
•
•
•
Examples
The following show acircuit checkpoint command displays information about the ACs that have been check-pointed. The output varies, depending on whether the command output is for the active or standby Route Processor (RP).
On the active RP, the command displays the following output:
Router# show acircuit checkpointAC HA Checkpoint info:Last Bulk Sync: 1 ACsAC IW XC Id VCId Switch Segment St Chkpt---- ---- ---- --- ---- -------- -------- -- -----HDLC LIKE ATOM 3 100 1000 1000 0 NVLAN LIKE ATOM 2 1002 2001 2001 3 YOn the standby RP, the command displays the following output::
Router# show acircuit checkpointAC HA Checkpoint info:AC IW XC Id VCId Switch Segment St F-SLP---- ---- ---- --- ---- -------- -------- -- -----HDLC LIKE ATOM 3 100 0 0 0 001VLAN LIKE ATOM 2 1002 2001 2001 2 000Table 20 describes the significant fields shown in the display.
Related Commands
show connect (FR-ATM)
To display statistics and other information about Frame-Relay-to-ATM Network Interworking (FRF.5) and Frame Relay-to-ATM Service Interworking (FRF.8) connections, use the show connect command in privileged EXEC mode.
show connect [all | element | id ID | name | port port]
Syntax Description
Defaults
Default state is show connect all.
Command Modes
Privileged EXEC
Command History
Examples
FRF.5: Examples
The following example displays information about all FRF.5 connections:
C3640# show connect allID Name Segment 1 Segment 2 State========================================================================5 network-1 VC-Group network-1 ATM3/0 1/34 UPThe following example displays information about the specified FRF.5 connection identifier:
Router# show connect id 5FR/ATM Network Interworking Connection: network-1Status - UPSegment 1 - VC-Group network-1Segment 2 - ATM3/0 VPI 1 VCI 34Interworking Parameters -de-bit map-clpclp-bit map-deFRF.8: Examples
The following example displays information about the specified FRF.8 connection identifier:
Router# show connect id 10FR/ATM Service Interworking Connection: service-1Status - UPSegment 1 - Serial1/0 DLCI 16Segment 2 - ATM3/0 VPI 1 VCI 32Interworking Parameters -service translationefci-bit 0de-bit map-clpclp-bit map-deThe following example displays information about the FRF.8 connection on an interface:
Router# show connect port atm3/0ID Name Segment 1 Segment 2 State========================================================================10 service-1 Serial1/0 16 ATM3/0 1/32 UPTable 21 describes the fields seen in these displays.
Related Commands
show connection
To display the status of interworking connections, use the show connection command in privileged EXEC mode.
show connection [all | element | id ID | name name | port port]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the local interworking connections on a router:
Router# show connectionID Name Segment 1 Segment 2 State========================================================================1 conn1 ATM 1/0/0 AAL5 0/100 ATM 2/0/0 AAL5 0/100 UP2 conn2 ATM 2/0/0 AAL5 0/300 Serial0/1 16 UP3 conn3 ATM 2/0/0 AAL5 0/400 FA 0/0.1 10 UP4 conn4 ATM 1/0/0 CELL 0/500 ATM 2/0/0 CELL 0/500 UP5 conn5 ATM 1/0/0 CELL 100 ATM 2/0/0 CELL 100 UPTable 22 describes the significant fields shown in the display.
Related Commands
show ethernet service evc
To display information about Ethernet virtual connections (EVCs), use the show ethernet service evc command in privileged EXEC mode.
show ethernet service evc [detail | id evc-id [detail] | interface type number [detail]]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
This command is useful for system monitoring and troubleshooting.
Examples
Following is sample output from the show ethernet service evc command:
Router# show ethernet service evcIdentifier Type Act-UNI-cnt StatusBLUE P-P 2 ActivePINK MP-MP 2 PartiallyActivePURPLE P-P 2 ActiveBROWN MP-MP 2 ActiveGREEN P-P 3 ActiveYELLOW MP-MP 2 PartiallyActiveBANANAS P-P 0 InActiveTEST2 P-P 0 NotDefinedORANGE P-P 2 ActiveTEAL P-P 0 InActiveTable 23 describes the significant fields in the output.
Related Commands
show ethernet service instance
To display information about Ethernet customer service instances, use the show ethernet service instance command in privileged EXEC mode.
show ethernet service instance [detail | id id | interface type number | policy-map | stats]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
This command is useful for system monitoring and troubleshooting.
Examples
Following is an example of output from the show ethernet service instance command:
Router# show ethernet service instanceIdentifier Interface CE-Vlans222 FastEthernet0/1 untagged,1-409410 FastEthernet0/2222 FastEthernet0/2 200333 FastEthernet0/2 default10 FastEthernet0/3 30011 FastEthernet0/310 FastEthernet0/4 30010 FastEthernet0/6 untagged,1-409410 FastEthernet0/7 untagged,1-409410 FastEthernet0/8 untagged,1-409410 FastEthernet0/9 untagged20 FastEthernet0/9222 FastEthernet0/11 300-350,900-999333 FastEthernet0/11 100-200,1000,1999-4094222 FastEthernet0/12 20333 FastEthernet0/12 1010 FastEthernet0/13 1020 FastEthernet0/13 2030 FastEthernet0/13 30200 FastEthernet0/13 222200 FastEthernet0/14 200,222300 FastEthernet0/14 333555 FastEthernet0/14 555Table 24 describes the significant fields in the output.
Related Commands
show ethernet service interface
To display interface-only information about Ethernet customer service instances for all interfaces or for a specified interface, use the show ethernet service interface privileged EXEC mode.
show ethernet service interface [type number] [detail]
Syntax Description
type
(Optional) Type of interface.
number
(Optional) Number of the interface.
detail
(Optional) Displays detailed information about interfaces or a specified service instance ID or interface.
Command Modes
Privileged EXEC
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain "Output" are displayed.
Examples
Following are examples of output from the show ethernet service interface command:
Router# show ethernet service interface gigabitethernet0/1Interface IdentifierGigabitEthernet0/1 PE2-G101Router# show ethernet service interface detailInterface: FastEthernet0/1ID:CE-VLANS:EVC Map Type: Bundling-MultiplexingInterface: FastEthernet0/2ID:CE-VLANS:EVC Map Type: Bundling-MultiplexingInterface: FastEthernet0/3ID:CE-VLANS:EVC Map Type: Bundling-Multiplexing<output truncated>Interface: GigabitEthernet0/1ID: PE2-G101CE-VLANS: 10,20,30EVC Map Type: Bundling-MultiplexingAssociated EVCs:EVC-ID CE-VLANWHITE 30RED 20BLUE 10Associated Service Instances:Service-Instance-ID CE-VLAN10 1020 2030 30Table 25 describes the significant fields in the output.
Related Commands
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] | failures]
Syntax Description
interface
(Optional) Interface to display.
dlci
(Optional) DLCI to display.
failures
(Optional) Displays the number of times keepalive has failed and the elapsed time since the last failure occurred.
Defaults
If no interface is specified, show all interfaces.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the keepalive status of an interface.
Examples
The following examples show output from the show frame-relay end-to-end keepalive command:
Displaying Statistics About Frame Relay End-to-End Keepalive: Example
Router# show frame-relay end-to-end keepalive interface s1End-to-end Keepalive Statistics for Interface Serial1 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, VC STATUS = STATIC (EEK UP)SEND SIDE STATISTICSSend Sequence Number: 86, Receive Sequence Number: 87Configured Event Window: 3, Configured Error Threshold: 2Total Observed Events: 90, Total Observed Errors: 34Monitored Events: 3, Monitored Errors: 0Successive Successes: 3, End-to-end VC Status: UPRECEIVE SIDE STATISTICSSend Sequence Number: 88, Receive Sequence Number: 87Configured Event Window: 3, Configured Error Threshold: 2Total Observed Events: 90, Total Observed Errors: 33Monitored Events: 3, Monitored Errors: 0Successive Successes: 3, End-to-end VC Status: UPDisplaying Failure Statistics About Frame Relay End-to-End Keepalive: Example
Router# show frame-relay end-to-end keepalive interface s1 failuresEnd-to-end Keepalive Statistics for Interface Serial1 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, VC STATUS = STATIC (EEK UP)SEND SIDE STATISTICSSend Sequence Number: 86, Receive Sequence Number: 87Configured Event Window: 3, Configured Error Threshold: 2Total Observed Events: 90, Total Observed Errors: 34Monitored Events: 3, Monitored Errors: 0Successive Successes: 3, End-to-end VC Status: UPRECEIVE SIDE STATISTICSSend Sequence Number: 88, Receive Sequence Number: 87Configured Event Window: 3, Configured Error Threshold: 2Total Observed Events: 90, Total Observed Errors: 33Monitored Events: 3, Monitored Errors: 0Successive Successes: 3, End-to-end VC Status: UPFailures Since Started: 1, Last Failure: 00:01:31Table 26 describes the fields shown in the display.
Related Commands
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
Command Modes
Privileged EXEC
Command History
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 fragmentinterface dlci frag-type frag-size in-frag out-frag dropped-fragSerial0 108 VoFR-cisco 100 1261 1298 0Serial0 109 VoFR 100 0 243 0Serial0 110 end-to-end 100 0 0 0The 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 16fragment-size 45 fragment type end-to-endin fragmented pkts 0 out fragmented pkts 0in fragmented bytes 0 out fragmented bytes 0in un-fragmented pkts 0 out un-fragmented pkts 0in un-fragmented bytes 0 out un-fragmented bytes 0in assembled pkts 0 out pre-fragmented pkts 0in assembled bytes 0 out pre-fragmented bytesin dropped reassembling pkts 0 out dropped fragmenting pkts 0in timeouts 0in out-of-sequence fragments 0in fragments with unexpected B bit set 0out interleaved packets 0Table 27 describes the fields shown in the display.
Related Commands
show frame-relay iphc
To display Frame Relay IP Header Compression Implementation Agreement (FRF.20) negotiation parameters for each PVC, use the show frame-relay iphc command in user EXEC or privileged EXEC mode.
show frame-relay iphc [interface interface] [dlci]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Examples
The following is sample output for the show frame-relay iphc command without any parameters specified:
Router# show frame-relay iphcFRF.20 Statistics for Interface Serial2/0DLCI 16 :Parameters: TCP space 16 non TCP space 16F_MAX period 256 F_MAX time 5 MAX header 168CP: State - req sent CP drops 0Reqs txed 2 Req rxed 0 Acks txed 0 Acks rxed 0Table 28 describes the significant fields shown in the display.
Related Commands
show frame-relay ip tcp header-compression
To display Frame Relay Transmission Control Protocol (TCP)/IP header compression statistics, use the show frame-relay ip tcp header-compression command in user EXEC or privileged EXEC mode.
show frame-relay ip tcp header-compression [interface type number] [dlci]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show frame-relay ip tcp header-compression command:
Router# show frame-relay ip tcp header-compressionDLCI 200 Link/Destination info: ip 10.108.177.200Interface Serial0:Rcvd: 40 total, 36 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed0 bytes saved, 0 bytes sentConnect: 16 rx slots, 16 tx slots, 0 long searches, 0 misses, 0% hit ratioFive minute miss rate 0 misses/sec, 0 max misses/secThe following sample output from the show frame-relay ip tcp header-compression command shows statistics for a PVC bundle called "MP-3-static":
Router# show frame-relay ip tcp header-compression interface Serial1/4vc-bundle MP-3-static Link/Destination info:ip 10.1.1.1Interface Serial1/4:Rcvd: 14 total, 13 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 15 total, 14 compressed,474 bytes saved, 119 bytes sent4.98 efficiency improvement factorConnect:256 rx slots, 256 tx slots,1 long searches, 1 misses 0 collisions, 0 negative cache hits93% hit ratio, five minute miss rate 0 misses/sec, 0 maxIn the following example, the show frame-relay ip tcp header-compression command displays information about DLCI 21:
Router# show frame-relay ip tcp header-compression 21DLCI 21 Link/Destination info: ip 10.1.2.1Interface POS2/0 DLCI 21 (compression on, VJ)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 21 Link/Destination info: ip 10.1.4.1Interface Serial3/0 DLCI 21 (compression on, VJ)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsThe following is sample output from the show frame-relay ip tcp header-compression command for a specific DLCI on a specific interface:
Router# show frame-relay ip tcp header-compression pos2/0 21DLCI 21 Link/Destination info: ip 10.1.2.1Interface POS2/0 DLCI 21 (compression on, VJ)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsTable 29 describes the fields shown in the display.
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 command in user EXEC or privileged EXEC mode.
show frame-relay lapf
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show frame-relay lapf command.
Router# show frame-relay lapfInterface = Serial1 (up), LAPF state = TEI_ASSIGNED (down)SVC disabled, link down cause = LMI down, #link-reset = 0T200 = 1.5 sec., T203 = 30 sec., N200 = 3, k = 7, N201 = 260I xmt = 0, I rcv = 0, I reXmt = 0, I queued = 0I xmt dropped = 0, I rcv dropped = 0, Rcv pak dropped = 0RR xmt = 0, RR rcv = 0, RNR xmt = 0, RNR rcv = 0REJ xmt = 0, REJ rcv = 0, FRMR xmt = 0, FRMR rcv = 0DM xmt = 0, DM rcv = 0, DISC xmt = 0, DISC rcv = 0SABME xmt = 0, SABME rcv = 0, UA xmt = 0, UA rcv = 0V(S) = 0, V(A) = 0, V(R) = 0, N(S) = 0, N(R) = 0Xmt FRMR at Frame RejectTable 30 describes significant fields in this output.
show frame-relay lmi
To display statistics about the Local Management Interface (LMI), use the show frame-relay lmi command in user EXEC or privileged EXEC mode.
show frame-relay lmi [type number]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 lmiLMI Statistics for interface Serial1 (Frame Relay DTE) LMI TYPE = ANSIInvalid Unnumbered info 0 Invalid Prot Disc 0Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0Num Status Enq. Sent 9 Num Status msgs Rcvd 0Num Update Status Rcvd 0 Num Status Timeouts 9The 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 lmiLMI Statistics for interface Serial3 (Frame Relay NNI) LMI TYPE = CISCOInvalid Unnumbered info 0 Invalid Prot Disc 0Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0Num Status Enq. Rcvd 11 Num Status msgs Sent 11Num Update Status Rcvd 0 Num St Enq. Timeouts 0Num Status Enq. Sent 10 Num Status msgs Rcvd 10Num Update Status Sent 0 Num Status Timeouts 0Table 31 describes significant fields shown in the output.
show frame-relay map
To display current Frame Relay map entries and information about connections, use the show frame-relay map command in privileged EXEC mode.
show frame-relay map [interface type number] [dlci]
Syntax Description
Command Default
Static and dynamic Frame Relay map entries and information about connections for all DLCIs on all interfaces are displayed.
Command Modes
Privileged EXEC
Command History
Examples
This section contains the following examples:
•
•
•
Display All Maps or Maps for Specific DLCIs on Specific Interfaces or Subinterfaces: Example
The sample output in these examples uses the following configuration:
interface POS2/0no ip addressencapsulation frame-relayframe-relay map ip 10.1.1.1 20 tcp header-compressionframe-relay map ip 10.1.2.1 21 tcp header-compressionframe-relay map ip 10.1.3.1 22 tcp header-compressionframe-relay map bridge 23frame-relay interface-dlci 25frame-relay interface-dlci 26bridge-group 1interface POS2/0.1 point-to-pointframe-relay interface-dlci 24 protocol ip 10.1.4.1interface Serial3/0no ip addressencapsulation frame-relayserial restart-delay 0frame-relay map ip 172.16.3.1 20frame-relay map ip 172.16.4.1 21 tcp header-compression activeframe-relay map ip 172.16.1.1 100frame-relay map ip 172.16.2.1 101interface Serial3/0.1 multipointframe-relay map ip 192.168.11.11 24frame-relay map ip 192.168.11.22 105The following example shows how to display all maps:
Router# show frame-relay mapPOS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.2.1 dlci 21(0x15,0x450), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.3.1 dlci 22(0x16,0x460), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): bridge dlci 23(0x17,0x470), static,CISCO, status deletedPOS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedSerial3/0 (downup): ip 172.16.3.1 dlci 20(0x14,0x440), static,CISCO, status deletedSerial3/0 (downup): ip 172.16.4.1 dlci 21(0x15,0x450), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256Serial3/0.1 (downup): ip 192.168.11.11 dlci 24(0x18,0x480), static,CISCO, status deletedSerial3/0 (downup): ip 172.16.1.1 dlci 100(0x64,0x1840), static,CISCO, status deletedSerial3/0 (downup): ip 172.16.2.1 dlci 101(0x65,0x1850), static,, CISCO,CISCO, status deletedECRTP Header Compression (enabled, IETF), connections 16TCP/IP Header Compression (enabled, IETF), connections 16Serial3/0.1 (downup): ip 192.168.11.22 dlci 105(0x69,0x1890), static,CISCO, status deletedSerial4/0/1:0.1 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast, CISCOstatus defined, active,RTP Header Compression (enabled), connections: 256The following example shows how to display maps for a specific DLCI:
Router# show frame-relay map 20POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256Serial3/0 (down): ip 172.16.3.1 dlci 20(0x14,0x440), static,CISCO, status deletedThe following example shows how to display maps for a specific interface:
Router# show frame-relay map interface pos2/0POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.2.1 dlci 21(0x15,0x450), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.3.1 dlci 22(0x16,0x460), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): bridge dlci 23(0x17,0x470), static,CISCO, status deletedPOS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedThe following example shows how to display maps for a specific DLCI on a specific interface:
Router# show frame-relay map interface pos2/0 20POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256The following example shows how to display maps for a specific subinterface:
Router# show frame-relay map interface pos2/0.1POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedThe following example shows how to display maps for a specific DLCI on a specific subinterface:
Router# show frame-relay map interface pos2/0.1 24POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedDisplay Maps for PVC Bundles: Example
The sample output in this example uses the following router configuration:
hostname router1!interface Serial2/0ip address 30.0.0.2 255.255.255.0encapsulation frame-relayframe-relay vc-bundle vcb1pvc 100 vcb1-classAprecedence 1-7class vcb1-classApvc 109 vcb1-othersprecedence otherclass othersframe-relay intf-type dce!map-class frame-relay vcb1-classAframe-relay cir 128000!map-class frame-relay othersframe-relay cir 64000hostname router2!interface Serial3/3ip address 30.0.0.1 255.255.255.0encapsulation frame-relayframe-relay vc-bundle vcb1pvc 100 vcb1-classAprecedence 1-7class vcb1-classApvc 109 vcb1-othersprecedence otherclass others!map-class frame-relay vcb1-classAframe-relay cir 128000!map-class frame-relay othersframe-relay cir 64000The following sample output displays mapping information for two PVC bundles. The PVC bundle MAIN-1-static is configured with a static map. The map for PVC bundle MAIN-2-dynamic is created dynamically using Inverse Address Resolution Protocol (ARP).
Router# show frame-relay map
Serial1/4 (up): ip 10.1.1.1 vc-bundle MAIN-1-static, static,CISCO, status upSerial1/4 (up): ip 10.1.1.2 vc-bundle MAIN-2-dynamic, dynamic,broadcast, status upDisplay Maps for IPv6 Addresses: Example
The sample output in this example uses the following router configuration:
hostname router1!interface Serial2/0no ip addressencapsulation frame-relay!interface Serial2/0.1 point-to-pointipv6 address 1::1/64frame-relay interface-dlci 101!interface Serial2/0.2 multipointipv6 address 2::1/64frame-relay map ipv6 2::2 201frame-relay interface-dlci 201!hostname router2!interface Serial3/3no ip addressencapsulation frame-relayframe-relay intf-type dce!interface Serial3/3.1 point-to-pointipv6 address 1::2/64frame-relay interface-dlci 101!interface Serial3/3.2 multipointipv6 address 2::2/64frame-relay map ipv6 3::1 201frame-relay interface-dlci 201!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 2001:0DB8:2222:1044::32; FE80::60:3E47:AC8:8 and 2001:0DB8:2222:1044::32) of two remote nodes are explicitly mapped to 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, activeSerial3 (up): ipv6 2001:0DB8:2222:1044::32 dlci 19(0x13,0x430), static,CISCO, status defined, activeSerial3 (up): ipv6 2001:0DB8:2222:1044::32 dlci 17(0x11,0x410), static,CISCO, status defined, activeSerial3 (up): ipv6 FE80::60:3E47:AC8:8 dlci 19(0x13,0x430), static,broadcast, CISCO, status defined, activeTable 32 describes the significant fields shown in the displays.
Related Commands
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
Command Default
Information for all bundles and bundle links is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify a bundle or bundle link, information for all bundles and bundle links is displayed.
Examples
All Bundles and Bundle Links: Example
The following example shows output for the show frame-relay multilink command (see Table 33 for descriptions of the fields). Because a specific bundle or bundle link is not specified, information for all bundles and bundle links is displayed:
Router# show frame-relay multilinkBundle:MFR0, State = up, class = A, fragmentation disabledBID = MFR0Bundle links :Serial2/1:3, HW state :up, Protocol state :Idle, LID :Serial2/1:3Serial2/1:2, HW state :up, Protocol state :Idle, LID :Serial2/1:2Serial2/1:1, HW state :up, Protocol state :Idle, LID :Serial2/1:1The following example shows output for the show frame-relay multilink command when a Frame Relay bundle is configured as bandwidth class C (threshold) (see Table 33 for descriptions of the fields):
Router# show frame-relay multilinkBundle: MFR0, state down, class C (threshold 2), no fragmentationID: Bundle-DallasSerial5/1, state up/up, ID: BL-Dallas-1Serial5/3, state up/add-sent, ID: BL-Dallas-3Bundle Link: Example
The following example shows output for the show frame-relay multilink command when it is issued with the serial number option (see Table 33 for descriptions of the fields). It displays information about the specified bundle link:
Router# show frame-relay multilink serial 3/2Bundle links :Serial3/2, HW state : down, Protocol state :Down_idle, LID :Serial3/2Bundle interface = MFR0, BID = MFR0Detailed Bundle Links: Examples
The following example shows output for the show frame-relay multilink command when it is issued with the serial number and detailed options (see Table 33 for descriptions of the fields). The example shows a bundle link in the "idle" state:
Router# show frame-relay multilink serial 3 detailedBundle links:Serial3, HW state = up, link state = Idle, LID = Serial3Bundle interface = MFR0, BID = MFR0Cause code = none, Ack timer = 4, Hello timer = 10,Max retry count = 2, Current count = 0,Peer LID = Serial5/3, RTT = 0 msStatistics: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 = 0The following example shows output for the show frame-relay multilink command when it is issued with the serial number and detailed options (see Table 33 for descriptions of the fields). The example shows a bundle link in the "up" state:
Router# show frame-relay multilink serial 3 detailedBundle links:Serial3, HW state = up, link state = Up, LID = Serial3Bundle interface = MFR0, BID = MFR0Cause code = none, Ack timer = 4, Hello timer = 10,Max retry count = 2, Current count = 0,Peer LID = Serial5/3, RTT = 4 msStatistics: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 = 0Table 33 describes significant fields shown in the displays.
Related Commands
debug frame-relay multilink
Displays debug messages for multilink Frame Relay bundles and bundle links.
show frame-relay pvc
To display statistics about Frame Relay permanent virtual circuits (PVCs), use the show frame-relay pvc command in privileged EXEC mode.
show frame-relay pvc [[interface interface] [dlci] [64-bit] | summary [all]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor the PPP link control protocol (LCP) state as being open with an up state or closed with a down state.
When "vofr" or "vofr cisco" has been configured on the PVC, and a voice bandwidth has been allocated to the class associated with this PVC, configured voice bandwidth and used voice bandwidth are also displayed.
Statistics Reporting
To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.
To obtain statistics about a PVC that include policy-map configuration or the priority configured for that PVC, use this command with the dlci argument.
To display a summary of all PVCs on the system, use the show frame-relay pvc command with the summary keyword. To display a summary of all PVCs per interface, use the summary all keywords.
Per-VC counters are not incremented at all when either autonomous or silicon switching engine (SSE) switching is configured; therefore, PVC values will be inaccurate if either switching method is used.
You can change the period of time over which a set of data is used for computing load statistics. If you decrease the load interval, the average statistics are computed over a shorter period of time and are more responsive to bursts of traffic. To change the length of time for which a set of data is used to compute load statistics for a PVC, use the load-interval command in Frame-Relay DLCI configuration mode.
Traffic Shaping
Congestion control mechanisms are currently not supported on terminated PVCs nor on PVCs over ISDN. Where congestion control mechanisms are supported, the switch passes forward explicit congestion notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligible (DE) bits unchanged from entry points to exit points in the network.
Examples
The various displays in this section show sample output for a variety of PVCs. Some of the PVCs carry data only; some carry a combination of voice and data. This section contains the following examples:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Summary of Frame Relay PVCs: Example
The following example shows sample output of the show frame-relay pvc command with the summary keyword. The summary keyword displays all PVCs on the system.
Router# show frame-relay pvc summaryFrame-Relay VC SummaryActive Inactive Deleted StaticLocal 0 12 0 0Switched 0 0 0 0Unused 0 0 0 0The following example shows sample output for the show frame-relay pvc command with the summary and all keywords. The summary and all keywords display all PVCs per interface.
Router# show frame-relay pvc summary allVC Summary for interface Serial3/0 (Frame Relay DTE)Active Inactive Deleted StaticLocal 0 7 0 0Switched 0 0 0 0Unused 0 0 0 0VC Summary for interface Serial3/1 (Frame Relay DTE)Active Inactive Deleted StaticLocal 0 5 0 0Switched 0 0 0 0Unused 0 0 0 0Frame Relay Generic Configuration: Example
The following sample output shows a generic Frame Relay configuration on DLCI 100:
Router# show frame-relay pvc 100PVC 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.1input pkts 4360 output pkts 4361 in bytes 146364out bytes 130252 dropped pkts 3735 in pkts dropped 0out pkts dropped 3735 out bytes dropped 1919790late-dropped out pkts 3735 late-dropped out bytes 1919790in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 337 out bcast bytes 1020845 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/secpvc create time 05:34:06, last time pvc status changed 05:33:38Frame 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 202PVC Statistics for interface Serial3/1 (Frame Relay DTE)DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial3/1.2input pkts 0 output pkts 479 in bytes 0out bytes 51226 dropped pkts 0 in pkts dropped 0out pkts dropped 0 out bytes dropped 0in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 5000 bits/sec, 5 packets/secpvc create time 00:23:36, last time pvc status changed 00:23:31fragment type end-to-end fragment size 80 adaptive active, time left 29 secsFrame 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 202PVC Statistics for interface Serial1/4 (Frame Relay DTE)DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1/4input pkts 0 output pkts 45 in bytes 0out bytes 45000 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 2000 bits/sec, 2 packets/secpvc create time 00:01:25, last time pvc status changed 00:01:11VC-Bundle MAIN-1-staticFrame Relay 64-Bit Counter: Example
The following sample output displays the Frame Relay 64-bit counters:
Router# show frame-relay pvc 35 64-bitDLCI = 35, INTERFACE = Serial0/0input pkts 0 output pkts 0in bytes 0 out bytes 0Frame 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 110PVC Statistics for interface Serial0/0 (Frame Relay DTE)DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0/0input pkts 409 output pkts 409 in bytes 3752out bytes 4560 dropped pkts 1 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 3d00h, last time pvc status changed 2d22hService type VoFR-ciscoVoice Queueing Stats: 0/100/0 (size/max/dropped)Post h/w compression queue: 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0configured voice bandwidth 16000, used voice bandwidth 0fragment type VoFR-cisco fragment size 100cir 64000 bc 640 be 0 limit 80 interval 10mincir 32000 byte increment 80 BECN response nofrags 428 bytes 4810 frags delayed 24 bytes delayed 770shaping inactivetraffic shaping drops 0ip rtp priority parameters 16000 32000 20000Switched 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 pvcPVC Statistics for interface Serial2/2 (Frame Relay NNI)DLCI = 16, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE = Serial2/2LOCAL PVC STATUS = INACTIVE, NNI PVC STATUS = INACTIVEinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0switched pkts0Detailed packet drop counters:no out intf 0 out intf down 0 no out PVC 0in PVC down 0 out PVC down 0 pkt too big 0shaping Q full 0 pkt above DE 0 policing drop 0pvc create time 00:00:07, last time pvc status changed 00:00:07Frame 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 200PVC Statistics for interface Serial3/0 (Frame Relay DTE)DLCI = 200, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial3/0input pkts 341 output pkts 390 in bytes 341000out bytes 390000 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 390out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 341pvc create time 00:10:35, last time pvc status changed 00:10:06Congestion DE threshold 50shaping activecir 56000 bc 7000 be 0 byte limit 875 interval 125mincir 28000 byte increment 875 BECN response nopkts 346 bytes 346000 pkts delayed 339 bytes delayed 339000traffic shaping drops 0Queueing strategy:fifoOutput queue 48/100, 0 drop, 339 dequeuedFrame 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 100PVC Statistics for interface Serial1/0 (Frame Relay DCE)DLCI = 100, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial1/0input pkts 1260 output pkts 0 in bytes 1260000out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 1260pvc create time 00:03:57, last time pvc status changed 00:03:19policing enabled, 180 pkts marked DEpolicing Bc 6000 policing Be 6000 policing Tc 125 (msec)in Bc pkts 1080 in Be pkts 180 in xs pkts 0in Bc bytes 1080000 in Be bytes 180000 in xs bytes 0Frame Relay PVC Priority Queueing: Example
The following is sample output for a PVC that has been assigned high priority:
Router# show frame-relay pvc 100PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0input pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:00:59, last time pvc status changed 00:00:33priority highLow 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 100PVC Statistics for interface Serial1/0 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial1/0.1input pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:00:42, last time pvc status changed 00:00:42service policy mypolicyClass voiceWeighted Fair QueueingStrict PriorityOutput Queue: Conversation 72Bandwidth 16 (kbps) Packets Matched 0(pkts discards/bytes discards) 0/0Class immediate-dataWeighted Fair QueueingOutput Queue: Conversation 73Bandwidth 60 (%) Packets Matched 0(pkts discards/bytes discards/tail drops) 0/0/0mean queue depth: 0drops: class random tail min-th max-th mark-prob0 0 0 64 128 1/101 0 0 71 128 1/102 0 0 78 128 1/103 0 0 85 128 1/104 0 0 92 128 1/105 0 0 99 128 1/106 0 0 106 128 1/107 0 0 113 128 1/10rsvp 0 0 120 128 1/10Class priority-dataWeighted Fair QueueingOutput Queue: Conversation 74Bandwidth 40 (%) Packets Matched 0 Max Threshold 64 (packets)(pkts discards/bytes discards/tail drops) 0/0/0Class class-defaultWeighted Fair QueueingFlow Based Fair QueueingMaximum Number of Hashed Queues 64 Max Threshold 20 (packets)Output queue size 0/max total 600/drops 0fragment type end-to-end fragment size 50cir 64000 bc 640 be 0 limit 80 interval 10mincir 64000 byte increment 80 BECN response nofrags 0 bytes 0 frags delayed 0 bytes delayed 0shaping inactivetraffic shaping drops 0PPP 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 55PVC Statistics for interface Serial5/1 (Frame Relay DTE)DLCI = 55, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial5/1.1input pkts 9 output pkts 16 in bytes 154out bytes 338 dropped pkts 6 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:35:11, last time pvc status changed 00:00:22Bound 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 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 108vofr ciscoclass vofr-classmap-class frame-relay vofr-classframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000frame-relay voice bandwidth 25000Router# show frame-relay pvc 108PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 108, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 1260 output pkts 1271 in bytes 95671out bytes 98604 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 1271 out bcast bytes 98604pvc create time 09:43:17, last time pvc status changed 09:43:17Service type VoFR-ciscoconfigured voice bandwidth 25000, used voice bandwidth 0voice reserved queues 24, 25fragment type VoFR-cisco fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 2592 bytes 205140 pkts delayed 1296 bytes delayed 102570shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0FRF.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 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 110class fragmap-class frame-relay fragframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000Router# show frame-relay pvc 110PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 0 output pkts 243 in bytes 0out bytes 7290 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 243 out bcast bytes 7290pvc create time 04:03:17, last time pvc status changed 04:03:18fragment type end-to-end fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 486 bytes 14580 pkts delayed 243 bytes delayed 7290shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Note that when voice is not configured, voice bandwidth output is not displayed.
Multipoint Subinterfaces Transporting Data: Example
The following is sample output from the show frame-relay pvc command for multipoint subinterfaces carrying data only. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing. Note that neither fragmentation nor voice is configured on this PVC.
Router# show frame-relay pvcDLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103input pkts 10 output pkts 7 in bytes 6222out bytes 6034 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:13:11 last time pvc status changed 0:11:46DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104input pkts 20 output pkts 8 in bytes 5624out bytes 5222 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:03:57 last time pvc status changed 0:03:48PVC Shaping When HQF is Enabled: Example
The following is sample output from the show frame-relay pvc command for a PVC when HQF is enabled:
Router# show frame-relay pvc 16PVC Statistics for interface Serial4/1 (Frame Relay DTE)DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial4/1input pkts 1 output pkts 1 in bytes 34out bytes 34 dropped pkts 0 in pkts dropped 0out pkts dropped 0 out bytes dropped 0in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 1 out bcast bytes 34pvc create time 00:09:07, last time pvc status changed 00:09:07shaping inactivePVC Transporting Voice and Data: Example
The following is sample output from the show frame-relay pvc command for a PVC carrying voice and data traffic, with a special queue specifically for voice traffic created using the frame-relay voice bandwidth command queue keyword:
Router# show frame-relay pvc interface serial 1 45PVC Statistics for interface Serial1 (Frame Relay DTE)DLCI = 45, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1input pkts 85 output pkts 289 in bytes 1730out bytes 6580 dropped pkts 11 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:02:09, last time pvc status changed 00:02:09Service type VoFRconfigured voice bandwidth 25000, used voice bandwidth 22000fragment type VoFR fragment size 100cir 20000 bc 1000 be 0 limit 125 interval 50mincir 20000 byte increment 125 BECN response nofragments 290 bytes 6613 fragments delayed 1 bytes delayed 33shaping inactivetraffic shaping drops 0Voice Queueing Stats: 0/100/0 (size/max/dropped)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Table 34 describes the significant fields shown in the displays.
Table 34 show frame-relay pvc Field Descriptions
DLCI
One of the DLCI numbers for the PVC.
DLCI USAGE
Lists SWITCHED when the router or access server is used as a switch, or LOCAL when the router or access server is used as a DTE device.
PVC STATUS
Status of the PVC: ACTIVE, INACTIVE, or DELETED.
INTERFACE
Specific subinterface associated with this DLCI.
LOCAL PVC STATUS1
Status of PVC configured locally on the NNI interface.
NNI PVC STATUS1
Status of PVC learned over the NNI link.
input pkts
Number of packets received on this PVC.
output pkts
Number of packets sent on this PVC.
in bytes
Number of bytes received on this PVC.
out bytes
Number of bytes sent on this PVC.
dropped pkts
Number of incoming and outgoing packets dropped by the router at the Frame Relay level.
in pkts dropped
Number of incoming packets dropped. Incoming packets may be dropped for a number of reasons, including the following:
•
•
•
•
•
•
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:
•
•
•
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.
•
•
•
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
show frame-relay qos-autosense
To display the quality of service (QoS) values sensed from the switch, use the show frame-relay qos-autosense command in privileged EXEC mode.
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
Privileged EXEC
Command History
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-autosenseELMI information for interface Serial1IP Address used for Address Registration:9.2.7.9 My Ifindex:4ELMI AR status : Enabled.Connected to switch:hgw1 Platform:2611 Vendor:ciscoSw side ELMI AR status: EnabledIP Address used by switch for address registration :9.2.6.9 Ifindex:5ELMI 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-autosenseELMI information for interface Serial1Connected to switch:FRSM-4T1 Platform:AXIS Vendor:cisco(Time elapsed since last update 00:00:30)DLCI = 100OUT: CIR 64000 BC 50000 BE 25000 FMIF 4497IN: CIR 32000 BC 25000 BE 12500 FMIF 4497Priority 0 (Time elapsed since last update 00:00:12)DLCI = 200OUT: CIR 128000 BC 50000 BE 5100 FMIF 4497IN: CIR Unknown BC Unknown BE Unknown FMIF 4497Priority 0 (Time elapsed since last update 00:00:13)Table 35 describes the significant fields in the output display.
Related Commands
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 command in privileged EXEC mode.
show frame-relay route
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show frame-relay route command:
Router# show frame-relay routeInput Intf Input Dlci Output Intf Output Dlci StatusSerial1 100 Serial2 200 activeSerial1 101 Serial2 201 activeSerial1 102 Serial2 202 activeSerial1 103 Serial3 203 inactiveSerial2 200 Serial1 100 activeSerial2 201 Serial1 101 activeSerial2 202 Serial1 102 activeSerial3 203 Serial1 103 inactiveTable 36 describes significant fields shown in the output.
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 command in user EXEC or privileged EXEC mode.
show frame-relay svc maplist name
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example shows, first, the configuration of the map list "fish" and, second, the corresponding output of the show frame-relay svc maplist command. The following lines show the configuration:
map-list fish local-addr X121 87654321 dest-addr X121 12345678ip 172.21.177.26 class fish ietfipx 123.0000.0c07.d530 class fish ietf!map-class frame-relay fishframe-relay incir 192000frame-relay min-incir 19200frame-relay outcir 192000frame-relay min-outcir 19200frame-relay incbr(bytes) 15000frame-relay outcbr(bytes) 15000The following lines show the output of the show frame-relay svc maplist command for the preceding configuration:
Router# show frame-relay svc maplist fishMap List : fishLocal Address : 87654321 Type: X121Destination Address: 12345678 Type: X121Protocol : ip 172.21.177.26Protocol : ipx 123.0000.0c07.d530Encapsulation : IETFCall Reference : 1 DLCI : 501Configured Frame Mode Information Field Size :Incoming : 1500 Outgoing : 1500Frame Mode Information Field Size :Incoming : 1500 Outgoing : 1500Configured 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 : 15000Committed Burst Rate (bytes) :Incoming : 15000 Outgoing : 15000Configured Excess Burst Rate (bytes) :Incoming : 16000 Outgoing : 1200Excess Burst Rate (bytes) :Incoming : 16000 Outgoing : 1200Table 37 describes significant fields in the output.
Related Commands
show frame-relay traffic
To display the global Frame Relay statistics since the last reload, use the show frame-relay traffic command in privileged EXEC mode.
show frame-relay traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show frame-relay traffic command:
Router# show frame-relay trafficFrame Relay statistics:ARP requests sent 14, ARP replies sent 0ARP request recvd 0, ARP replies recvd 10show 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
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
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
Displaying General Information: 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: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps*4a 400 0-9 0-9 40/Yes pg up4b 401 10-19 10-19 9/Yes pg up4c 402 20-29 20-29 19/Yes pg up4d 403 30-39 30-39 29/Yes - up4e 404 40-49 40-49 39/Yes - up4f 405 50-59 50-59 49/Yes - up4g 406 60-62 60-62 59/Yes pv up4h 407 63 63 62/Yes pv upPackets 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: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps3a 300 0-9 0-9 -/Yes - up3b 301 10-19 10-19 9/Yes - up3c 302 20-29 20-29 19/Yes - up3d 303 30-39 40/Yes - deleted3e 304 40-49 30-59,63 39/Yes - up3f 305 50-59 49/Yes - deleted3g 306 60-62 60-62 59/No - up3h 307 63 62/Yes - deletedPackets sent out on vc-bundle MP-3-static : 335Router#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:PRECEDENCEName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/ accept PV kbps521 0,2,4 0,2,4 -/Yes - 20 up522 1,3,5-6 1,3,5-6 0/Yes - 26 up523 7 7 6/Yes - 20 upPackets sent out on vc-bundle 26k :0Router#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: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps410 50-62 49/Yes - down411 30,32,34,36,3.. 29/Yes - downPackets sent out on vc-bundle x41 : 0Active configuration and statistics for each member PVCDLCI Output pkts Active level410 0 50-62411 0 30,32,34,36,38-40Router#Table 38 describes the significant fields shown in the show frame-relay vc-bundle displays.
Related Commands
show l2tun
To display general information about Layer 2 tunnels and sessions, use the show l2tun command in privileged EXEC mode.
show l2tun
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show l2tun command displays general information about all active Layer 2 tunnels and sessions. Use the show l2tun tunnel command or the show l2tun session command to display more detailed information about Layer 2 tunnels or sessions.
Examples
The following example shows the display of information about all currently active Layer 2 tunnels and sessions:
Router# show l2tunL2TP Tunnel and Session Information Total tunnels 1 sessions 1LocID RemID Remote Name State Remote Address Port Sessions L2TP Class/VPDN Group45795 43092 PE1 est 10.1.1.1 0 1 genericLocID RemID TunID Username, Intf/ State Last Chg Uniq IDVcid, Circuit42410 0 45795 123456789, Fa4/1/1 idle 00:00:24 1Table 39 describes the significant fields shown in the display.
Related Commands
show l2tun counters tunnel l2tp
To display global or per-tunnel control message statistics for Layer 2 Tunnel Protocol (L2TP) tunnels, use the show l2tun counters tunnel l2tp command in privileged EXEC mode.
show l2tun counters tunnel l2tp [all | authentication | id local-id]
Syntax Description
Command Default
Global control message statistics are always enabled.
Per-tunnel control message statistics are disabled by default.Command Modes
Privileged EXEC
Command History
12.2(28)SB
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB, and
EXP ACK and CiscoACK were added to the command output.
Usage Guidelines
Use the show l2tun counters tunnel l2tp command to display global L2TP control message statistics.
Use the show l2tun counters tunnel l2tp authentication command to display global L2TP authentication control message statistics.
The show l2tun counters tunnel l2tp command can display per-tunnel statistics, but per-tunnel statistics must first be enabled. Per-tunnel statistics are controlled on a tunnel by tunnel basis using the monitor l2tun counters tunnel l2tp command.
Use the show l2tun counters tunnel l2tp id local-id command to display per-tunnel statistics for a specific tunnel.
Use the show l2tun counters tunnel l2tp all command to display control message statistics for all tunnels that have per-tunnel statistics enabled.
Examples
The following example displays global L2TP control message counter information. In this example, the Number of unknown control messages received: displays only if the unknown message count is nonzero.
Router# show l2tun counters tunnel l2tpGlobal L2TP tunnel control message statistics:Number of unknown control messages received: 10XMIT RE-XMIT RCVD DROP========== ========== ========== ==========Total 32 25 22 15ZLB 0 0 0 0SCCRQ 6 10 0 0SCCRP 0 0 1 0SCCCN 1 0 0 0StopCCN 5 5 0 0Hello 0 0 0 0OCRQ 0 0 0 0OCRP 0 0 0 0OCCN 0 0 0 0ICRQ 2 0 0 0ICRP 0 0 2 0ICCN 2 0 0 0CDN 0 0 0 0WEN 0 0 0 0SLI 2 0 4 0EXP ACK 0 0 0 0SRRQ 0 0 0 0SRRP 0 0 0 0CiscoACK 4 0 5 5Table 40 describes the significant fields shown in the display.
The following example shows the display of all possible L2TP control channel authentication AV pair statistics. AV pair statistic fields are displayed only if they are nonzero. For the purposes of this example, all possible output fields are displayed in the sample output.
Router# show l2tun counters tunnel l2tp authenticationL2TPv3 Tunnel Authentication Statistics:Nonce AVP Statistics:Ignored 0Missing 0All Digests Statistics:Unexpected 0Unexpected ZLB 0Primary Digest AVP Statistics:Validate fail 0Hash invalid 0Length invalid 0Missing 0Ignored 0Passed 0Failed 0Secondary Digest AVP Statistics:Validate fail 0Hash invalid 0Length invalid 0Missing 0Ignored 0Passed 0Failed 0Integrity Check Statistics:Validate fail 0Length invalid 0Passed 0Failed 0Local Secret Statistics:Missing 0Challenge AVP Statistics:Generate response fail 0Ignored 0Challenge/Response AVP Statistics:Generate response fail 0Missing 0Ignored 0Passed 0Failed 0Overall Statistics:Passed 0Skipped 0Ignored 0Failed 0Table 41 describes the significant fields shown in the display.
The following example displays L2TP control message statistics for all L2TP tunnels with per-tunnel statistics enabled:
Router# show l2tun counters tunnel l2tp allSummary listing of per-tunnel statistics:LocID RemID Remote IP Total Total Total TotalXMIT RE-XMIT RCVD DROP15587 39984 10.0.1.1 40 0 40 017981 42598 10.0.0.1 34 0 34 022380 14031 10.0.0.0 38 0 38 031567 56228 10.0.1.0 32 0 32 038360 30275 10.1.1.1 30 0 30 042759 1708 10.1.0.1 36 0 36 0Number of tunnels with per-tunnel stats: 6Table 42 describes the significant fields shown in the display.
The following example enables per-tunnel L2TP control message statistics for the L2TP tunnel with the local ID 38360:
Router# monitor l2tun counters tunnel l2tp id 38360 startRouter#The following example displays L2TP control message statistics for the L2TP tunnel with the local ID 38360:
Router# show l2tun counters tunnel l2tp id 38360L2TP tunnel control message statistics:Tunnel LocID: 38360 RemID: 30275Remote Address: 10.1.1.1XMIT RE-XMIT RCVD DROP========== ========== ========== ==========Total 32 25 22 15ZLB 0 0 0 0SCCRQ 6 10 0 0SCCRP 0 0 1 0SCCCN 1 0 0 0StopCCN 5 5 0 0Hello 0 0 0 0OCRQ 0 0 0 0OCRP 0 0 0 0OCCN 0 0 0 0ICRQ 2 0 0 0ICRP 0 0 2 0ICCN 2 0 0 0CDN 0 0 0 0WEN 0 0 0 0SLI 2 0 4 0EXP ACK 0 0 0 0SRRQ 0 0 0 0SRRP 0 0 0 0CiscoACK 4 0 5 5Related CommandsCiscoACK 4 0 5 5
show l2tun session
To display the current state of Layer 2 sessions and protocol information about Layer 2 Tunnel Protocol (L2TP) control channels, use the show l2tun session command in privileged EXEC mode.
show l2tun session [all [filter] | brief [filter] [hostname] | circuit [filter] [hostname] | interworking [filter] [hostname] | packets [filter] | sequence [filter] | state [filter]]
Syntax Description
all
(Optional) Displays information about all current L2TP sessions on the router.
filter
(Optional) One of the filter parameters defined in Table 43.
brief
(Optional) Displays information about all current L2TP sessions, including peer ID address and circuit status of the L2TP sessions.
hostname
(Optional) Specifies that the peer hostname will be displayed in the output.
circuit
(Optional) Displays information about all current L2TP sessions, including circuit status (up or down).
interworking
(Optional) Displays information about Layer 2 Virtual Private Network (L2VPN) interworking.
packets
(Optional) Displays information about the packet counters (in and out) associated with current L2TP sessions.
sequence
(Optional) Displays sequencing information about each L2TP session, including number of out-of-order and returned packets.
state
(Optional) Displays information about all current L2TP sessions and their protocol state, including remote Virtual Connection Identifier (VCIDs).
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show l2tun session command to display information about current L2TP sessions on the router.
Table 43 defines the filter parameters available to refine the output of the show l2tun session command.
Examples
The following example shows how to display detailed information about all current L2TP sessions:
Router# show l2tun session allSession Information Total tunnels 0 sessions 1Session id 42438 is down, tunnel id n/aRemote session id is 0, remote tunnel id n/aSession Layer 2 circuit, type is Ethernet, name is FastEthernet4/1/1Session vcid is 123456789Circuit state is DOWNLocal circuit state is DOWNRemote circuit state is DOWNCall serial number is 1463700128Remote tunnel name is PE1Internet address is 10.1.1.1Local tunnel name is PE1Internet address is 10.1.1.2IP protocol 115Session is L2TP signalledSession state is idle, time since change 00:00:260 Packets sent, 0 received0 Bytes sent, 0 receivedLast clearing of "show vpdn" counters neverReceive packets dropped:out-of-order: 0total: 0Send packets dropped:exceeded session MTU: 0total: 0DF bit off, ToS reflect disabled, ToS value 0, TTL value 255No session cookie information availableUDP checksums are disabledL2-L2 switching enabledNo FS cached header information availableSequencing is offUnique ID is 1The following example shows how to display information only about the L2TP session set up on a peer router with an IP address of 172.16.184.142 and a VCID of 300:
Router# show l2tun session all ip-addr 172.16.184.142 vcid 300L2TP SessionSession id 32518 is up, tunnel id n/aCall serial number is 2074900020Remote tunnel name is tun1Internet address is 172.16.184.142Session is L2TP signalledSession state is established, time since change 03:06:399932 Packets sent, 9932 received1171954 Bytes sent, 1171918 receivedSession vcid is 300Session Layer 2 circuit, type is Ethernet Vlan, name is FastEthernet0/1/0.3:3Circuit state is UPRemote session id is 18819, remote tunnel id n/aSet DF bit to 0Session cookie information:local cookie, size 4 bytes, value CF DC 5B F3remote cookie, size 4 bytes, value FE 33 56 C4SSS switching enabledSequencing is onNs 9932, Nr 10001, 0 out of order packets discardedTable 44 describes the significant fields shown in the displays.
The following example shows how to display information about the circuit status of L2TP sessions on a router:
Router# show l2tun session circuitSession Information Total tunnels 3 sessions 3LocID TunID Peer-address Type Stat Username, Intf/Vcid, Circuit32517 n/a 172.16.184.142 VLAN UP 100, Fa0/1/0.1:132519 n/a 172.16.184.142 VLAN UP 200, Fa0/1/0.2:232518 n/a 172.16.184.142 VLAN UP 300, Fa0/1/0.3:3The following example shows how to display information about the circuit status of L2TP sessions and the hostnames of remote peers:
Router# show l2tun session circuit hostnameSession Information Total tunnels 3 sessions 3LocID TunID Peer-hostname Type Stat Username, Intf/Vcid, Circuit32517 n/a <unknown> VLAN UP 100, Fa0/1/0.1:132519 n/a router32 VLAN UP 200, Fa0/1/0.2:232518 n/a access3 VLAN UP 300, Fa0/1/0.3:3Table 45 describes the significant fields shown in the displays.
