-
Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide
-
Preface
-
Overview of the Cisco 3825 Mobile Wireless Edge Router
-
Cisco IOS Software Basics
-
First-Time Configuration
-
Configuring the Cisco 3825 Mobile Wireless Edge Router in a RAN-O Solution with the Command-Line Interface
-
Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference
-
Configuration Examples
-
Feedback
Table Of Contents
Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference
clear ip rtp header-compression
ipran-mib backhaul-notify-interval
ipran-mib threshold-acceptable
ipran-mib threshold-overloaded
show ip rtp header-compression
snmp-server enable traps ipran
snmp-server enable traps ipran alarm-gsm
snmp-server enable traps ipran alarm-umts
snmp-server enable traps ipran util
Cisco 3825 Mobile Wireless Edge Router RAN-O Command Reference
This appendix contains an alphabetical listing of new and revised commands specific to the Cisco 3825 router in a Radio-Access Network-Optimization (RAN-O) solution.
The following commands have been introduced:
•
snmp-server enable traps ipran
•
•
•
•
•
The following commands were not changed but are included for your convenience:
•
•
•
•
•
atm umts
To select an ATM interface for Universal Mobile Telecommunications System (UMTS) Iub traffic for the atm subinterfaces, use the atm umts Sub-Interface configuration command. This command is used when you want to off load one or more permanent virtual circuit (PVC) traffic packets from a physical ATM shorthaul so as to go over an alternate backhaul. For each alternate backhaul, you need to create a logical shorthaul by creating an atm subinterface. Traffic for the PVCs configured under this logical shorthaul will go through the corresponding alternate backhaul.
atm umts
Syntax Description
This command has no arguments or keywords.
Command Modes
Sub-Interface configuration
Command History
Examples
The following example illustrates the use of atm umts command.
Router(config)# interface ATM0/2/0Router(config-if)# atm umts-iubRouter(config-subif)# atm umts
Note
Related Commands
atm umts-iub
To select an ATM interface for UMTS Iub traffic, use the atm umts-iub Interface configuration command.
atm umts-iub
Syntax Description
This command has no arguments or keywords.
Command Modes
Sub-Interface configuration
Command History
Examples
The following example illustrates the use of atm umts command.
Router(config)# interface ATM0/2/0Router(config-if)# atm umts-iubbackup delay
To specify how long a backup pseudowire (PW) virtual circuit (VC) should wait before resuming operation after the primary PW VC goes down, use the backup delay command in the interface configuration mode or xconnect configuration mode.
backup delay enable-delay {disable-delay | never}
Syntax Description
Defaults
If a failover occurs, the xconnect redundancy algorithm immediately switches over or falls back to the backup or primary member in the redundancy group.
Command Modes
Interface configuration
Xconnect configuration
Command History
Examples
The following example shows a Multiprotocol Label Switching (MPLS) xconnect with one redundant peer. Once a switchover to the secondary VC occurs, there is no fallback to the primary VC unless the secondary VC fails.
Router# config tRouter(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# exitRouter(config)# interface atm1/0/0Router(config-if)# xconnect 10.0.0.1 50 pw-class mplsRouter(config-if-xconn)# backup peer 10.0.0.2 50Router(config-if-xconn)# backup delay 0 neverRouter(config-if-xconn)# exitRouter(config-if)# exitRouter(config)# exitThe following example shows an MPLS xconnect with one redundant peer. The switchover does not begin unless the Layer 2 Tunnel Protocol (L2TP) PW has been down for three seconds. After a switchover to the secondary VC occurs, there is no fallback to the primary until the primary VC has been reestablished and is up for ten seconds.
Router# config tRouter(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# exitRouter(config)# interface atm1/0/0Router(config-if)# xconnect 10.0.0.1 50 pw-class mplsRouter(config-if-xconn)# backup peer 10.0.0.2 50Router(config-if-xconn)# backup delay 3 10Router(config-if-xconn)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
backup peer
To specify a redundant peer for a PW VC, use the backup peer command in the interface configuration mode or xconnect configuration mode. To remove the redundant peer, use the no form of this command.
backup peer peer-router-ip-addr vcid [pw-class pw-class-name]
no backup peer peer-router-ip-addr vcid
Syntax Description
Defaults
No redundant peer is established.
Command Modes
Interface configuration
Xconnect configuration
Command History
Usage Guidelines
The combination of the peer-router-ip-addr and vcid arguments must be unique on the router.
Examples
The following example shows an MPLS xconnect with one redundant peer:
Router# config tRouter(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# exitRouter(config)# interface atm1/0/0Router(config-if)# xconnect 10.0.0.1 100 pw-class mplsRouter(config-if-xconn)# backup peer 10.0.0.2 200Router(config-if-xconn)# exitRouter(config-if)# exitRouter(config)# exitThe following example shows a backup peer configuration for an ATM interface:
Router# config tRouter(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# exitRouter(config)# interface atm0/0/1Router(config-if)# xconnect 10.0.0.2 1 pw-class mplsRouter(config-if-xconn)# backup peer 10.0.0.2 100 pw-class mplsRouter(config-if-xconn)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
backup delay
Specifies how long the backup PW VC should wait before resuming operation after the primary PW VC goes down.
cdp enable
To enable Cisco Discovery Protocol (CDP) on an interface, use the cdp enable command in interface configuration mode. To disable CDP on an interface, use the no form of this command.
cdp enable
Syntax Description
This command has no arguments or keywords.
Command Modes
Interface configuration
Command History
Usage Guidelines
CDP is enabled by default at the global level and on each supported interface in order to send or receive CDP information. However, some interfaces, such as ATM interfaces, do not support CDP.
Note
Examples
In the following example, CDP is disabled on the Ethernet 0 interface only.
Router# show cdpGlobal CDP informationSending CDP packets every 60 secondsSending a holdtime value of 180 secondsSending CDPv2 advertisements is enabledRouter# config terminalRouter(config)# interface ethernet 0Router(config-if)# no cdp enableRelated Commands
cdp run
Re-enables CDP on a Cisco device.
cdp timer
Specifies how often the Cisco IOS software sends CDP updates.
router odr
Enables on-demand routing on a hub router
cem-group
To create a circuit emulation (CEM) channel from one or more time slots of a T1 or E1 line, use the cem-group command in controller configuration mode. To remove a CEM group and release the associated time slots, use the no form of this command.
cem-group group-number {unframed | timeslots time-slot-range}
no cem-group group-number
Syntax Description
Defaults
No CEM groups are defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to create CEM channels on the T1 or E1 port.
Examples
The following example illustrates the use of the cem group command:
SATOP
Router# config tRouter(config)# controller el 0/0/0Router(config-controller)# cem-group 0 unframedRouter(config-controller)# exitRouter(config)# interface cem 0/0/0Router(config-if)# cem 0Router(config-if-cem)# xconnect 10.10.10.10 200 encapsulation mplsRouter(config-if-cem-xconn)# exitRouter(config-if-cem)# exitRouter(config-if)# exitRouter(config)# exitCESoPSN
Router# config tRouter(config)# controller el 0/0/1Router(config-controller)# cem-group 0 timeslots 1-31Router(config-controller)# exitRouter(config)# interface cem 0/0/1Router(config-if)# cem 0Router(config-if-cem)# xconnect 10.10.10.10 200 encapsulation mplsRouter(config-if-cem-xconn)# exitRouter(config-if-cem)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
class cem
Use the class cem command in the global configuration mode to configure CEM interface parameters in a class that's applied to CEM interfaces together. This command works in the same manner for CEM interfaces as pseudowire-class does for xconnect.
class cem class-name
Syntax Description
Command Modes
Global configuration
Command History
Usage Guidelines
The class cem command allows you to configure CEM interface parameters in a class that's applied to CEM interfaces together. A class cem command includes the following configuration settings:
•
•
•
Examples
The following example illustrates the use of the class cem command:
Router# config tRouter(config)# class cem mycemclassRouter(config-cem-class)# dejitter-buffer 10Router(config-cem-class)# sample-rate 2Router(config-cem-class)# exitRouter(config)# interface cem 0/0/0Router(config-if)# no ip addressRouter(config-if)# cem 0Router(config-if-cem)# xconnect 10.10.10.10 200 encapsulation mplsRouter(config-if-cem-xconn)# cem class mycemclassRouter(config-if-cem)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
clear gsm-abis
To clear the statistics displayed by the show gsm-abis commands, use the clear gsm-abis command in privileged EXEC mode.
clear gsm-abis [serial serial-number interface-number]
Syntax Description
serial
serial-number
(Optional) The serial number range is from 0 to6.
interface number
(Optional) The serial number range is from 0 to6.
Command Modes
Interface configuration
Command History
12.4(2)MR
This command was introduced.
12.4(9)MR
This command was modified to include serial option.
Examples
The following example illustrates the use of the clear gsm-abis command.
Router# clear gsm-abis serial 0/0/0:0Related Commands
clear ip rtp header-compression
To clear Real-Time Transport Protocol (RTP) header compression structures and statistics, use the clear ip rtp header-compression privileged EXEC command.
clear ip rtp header-compression [type number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If this command is used without an interface type and number, the command clears all RTP header compression structures and statistics.
Examples
The following example clears the RTP header compression structures and statistics for multilink interface 1:
Router# clear ip rtp header-compression multilink1Related Commands
clear umts-iub
To clear the statistics displayed by the show umts-iub commands, use the clear umts-iub command in privileged EXEC mode.
clear umts-iub [atm atm interface interface number]
Syntax Description
atm
atm interface
(Optional) The interface number range is from 0 to 1.
interface number
(Optional) The serial number range is from 0/0/0 to 1/0/1.
Command Modes
Interface configuration
Command History
12.4(2)MR
This command was introduced.
12.4(9)MR
This command was modified to include atm option.
Examples
The following example illustrates the use of the clear umts-iub command.
Router# clear umts-iub atm 0/0/1Related Commands
dejitter-buffer
To specify the size of the dejitter-buffer used to compensate for the network jitter, use the dejitter-buffer command in the CEM configuration mode. To restore the dejitter-buffer to its default size, use the no form of this command.
dejitter-buffer size
no dejitter-buffer
Syntax Description
size
Use the size argument to specify the size of the buffer in milliseconds. Size can vary from 4 to 500 ms; default is 4 ms.
Defaults
The dejitter buffer defaults to 4 milliseconds.
Command Modes
CEM circuit configuration
Command History
Examples
The following example illustrates the use of the dejitter-buffer command:
Router# config tRouter(config)# interface cem 0/0/0Router(config-if)# no ip addressRouter(config-if)# cem 0Router(config-if-cem)# dejitter-buffer 10Router(config-if-cem)# xconnect 10.10.10.10 200 encapsulation mplsRouter(config-if-cem-xconn)# exitRouter(config-if-cem)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
encapsulation l2tpv3
To specify that Layer 2 Tunnel Protocol version 3 (L2TPv3) is used as the data encapsulation method for tunneling IP traffic over the PW, use the encapsulation l2tpv3 command in pseudowire-class configuration mode. To remove L2TPv3 as the encapsulation method, use the no pseudowire-class command (see the Usage Guidelines for more information).
encapsulation l2tpv3
no pseudowire-class
Syntax Description
This command has no arguments or keywords.
Defaults
No encapsulation method is specified.
Command Modes
Pseudowire-class configuration
Command History
Usage Guidelines
This command must be configured if the pseudowire-class is referenced from an xconnect configured to forward L2TPv3 traffic.
Once you specify the encapsulation l2tpv3 command, you cannot remove it using the no encapsulation l2tpv3 command. Nor can you change the command's setting using the encapsulation mpls command. Those methods result in the following error message:
Encapsulation changes are not allowed on an existing pw-class.To remove the l2tpv3 command, you must delete the PW with the no pseudowire-class command. To change the type of encapsulation, remove the PW with the no pseudowire-class command to re-establish the PW and to specify the new encapsulation type.
Examples
The following example illustrates the use of the encapsulation l2tpv3 command:
Router# config tRouter(config)# pseudowire-class l2tpRouter(config-pw-class)# encapsulation l2tpv3Router(config-pw-class)# exitRouter(config)# exitThe following example configures ATM AAL5 over L2TPv3 PW:
Router# config tRouter(config)# interface atm 0/0/1Router(config-if)# pvc 0/10 l2transportRouter(config-if-atm-l2trans-pvc)# encapsulation aal5Router(config-if-atm-l2trans-pvc)# xconnect 1.1.1.1 10 pw-class l2tpRouter(config-if-atm-l2trans-pvc-xconn)# exitRouter(config-if-atm-l2trans-pvc)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
gsm-abis congestion abate
Sets the congestion abatement detection level at which the remote router will stop suppressing timeslots because congestion has been alleviated.
The abate detection level is defined as x milliseconds of continuous congestion abatement (that is, no congestion indications). To set the abate detection, use the gsm-abis congestion abate Interface configuration command.
gsm-abis congestion abate [ms]
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to the gsm-abis abate command is set at 250 ms:
Router(config)# interface Serial10/1/0:0Router(config-if)# no ip addressRouter(config-if)# encapsulation gsm-abisRouter(config-if)# load-interval 30Router(config-if)# gsm-abis local 10.10.10.2 6661Router(config-if)# gsm-abis remote 10.10.10.1 5553Router(config-if)# gsm-abis congestion enableRouter(config-if)# gsm-abis congestion abate 250Router(config-if)# no keepaliveRelated Commands
gsm-abis congestion critical
Defines the critical timeslots that are exempt from suppression during congestion onset.
These are the timeslots that contain signalling and control information exchanged between the BSC and Base Transceiver Station (BTS). To define the critical timeslots that are exempt from suppression during congestion onset, use the gsm-abis congestion critical Interface configuration command.
gsm-abis congestion critical [timeslot-range]
Syntax Description
timeslot-range
Specifies a value or range of values for time slots that are exempt from suppression during congestion onset. Use a hyphen to indicate a range.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to set the timeslots range:
Router(config)# interface Serial10/1/0:0Router(config-if)# no ip addressRouter(config-if)# encapsulation gsm-abisRouter(config-if)# load-interval 30Router(config-if)# gsm-abis local 10.10.10.2 6661Router(config-if)# gsm-abis remote 10.10.10.1 5553Router(config-if)# gsm-abis congestion enableRouter(config-if)# gsm-abis congestion critical 2-3Router(config-if)# no keepaliveRelated Commands
gsm-abis congestion enable
The congestion detection algorithm monitors the transmit jitter buffer and sends congestion indicator signals to the remote when congestion is detected. The remote will suppress all timeslots that are not defined as critical in an effort to alleviate the congestion. The goal of the congestion detection algorithm is to save the critical timeslots from loss of data. To enable the congestion detection algorithm, use the gsm-abis congestion enable Interface configuration command.
gsm-abis congestion enable
Syntax Description
This command has no arguments or keywords.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to enable the gsm-abis congestion:
Router(config)# interface Serial10/1/0:0Router(config-if)# no ip addressRouter(config-if)# encapsulation gsm-abisRouter(config-if)# load-interval 30Router(config-if)# gsm-abis local 10.10.10.2 6661Router(config-if)# gsm-abis remote 10.10.10.1 5553Router(config-if)# gsm-abis congestion enableRouter(config-if)# no keepaliveRelated Commands
gsm-abis congestion onset
Sets the congestion onset detection level at which the remote router will start suppressing all timeslots that are not defined as critical in an effort to alleviate the congestion.
The onset detection level is defined as x milliseconds of continuous congestion detected. To set the congestion onset, use the gsm-abis congestion onset Interface configuration command.
gsm-abis congestion onset [ms]
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to set the onset detection level at 50 ms:
Router(config)# interface Serial10/1/0:0Router(config-if)# no ip addressRouter(config-if)# encapsulation gsm-abisRouter(config-if)# load-interval 30Router(config-if)# gsm-abis local 10.10.10.2 6661Router(config-if)# gsm-abis remote 10.10.10.1 5553Router(config-if)# gsm-abis congestion enableRouter(config-if)# gsm-abis congestion onset 100Router(config-if)# no keepaliveRelated Commands
gsm-abis jitter
Sets the amount of transmit jitter delay for the GSM-Abis interface.If the transmit jitter is set to 4 ms, data received on the backhaul with a time equal to 0 milliseconds will be stored in the jitter buffer and transmitted with a time equal to 4 milliseconds. The transmit jitter buffer allows some amount of jitter in the arrival of data on the backhaul to be tolerated without introducing errors into the stream of data.
To set the jitter, use the gsm-abis jitter Interface configuration command.
gsm-abis jitter ms
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to set the jitter level to 8 ms:
Router(config)# interface Serial10/1/0:0Router(config-if)# no ip addressRouter(config-if)# encapsulation gsm-abisRouter(config-if)# load-interval 30Router(config-if)# gsm-abis local 10.10.10.2 6661Router(config-if)# gsm-abis remote 10.10.10.1 5553Router(config-if)# gsm-abis jitter 8Router(config-if)# no keepaliveRelated Commands
gsm-abis local
To configure the local parameters required to establish an Internet Protocol/User Datagram Protocol (IP/UDP) backhaul connection, use the gsm-abis local Interface configuration command.
gsm-abis local [ip-address] [port]
Syntax Description
ip-address
(Optional) The IP address for the entry you wish to establish.
port
(Optional) The port you want to use for the entry you wish to establish.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the local parameters:
Router(config)# interface Serial10/1/0.0Router(config-if)# encapsulation gsm-abisRouter(config-if)# gsm-abis local 10.10.10.2 5502Related Commands
gsm-abis remote
Configures the remote parameters for an IP/UDP backhaul connection.
gsm-abis remote
To configure the remote parameters required to establish an Internet Protocol/User Datagram Protocol (IP/UDP) backhaul connection, use the gsm-abis remote Interface configuration command.
gsm-abis remote [ip-address] [port]
Syntax Description
ip-address
(Optional) The IP address for the entry you wish to establish.
port
(Optional) The port you want to use for the entry you wish to establish.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the remote parameters:
Router(config)# interface Serial10/1/0.0Router(config-if)# encapsulation gsm-abisRouter(config-if)# gsm-abis remote 10.10.10.1 5504Related Commands
gsm-abis local
Configures the local parameters for an IP/UDP backhaul connection.
gsm-abis retransmit
To enable retransmission of repetitive subrate sample, use the gsm-abis retransmit Interface configuration command. This command is useful when the latency introduced by the characteristics of the backhaul network is excessive. Examples are the use of satellite transmission facilities or multiple router hops on the backhaul network.
gsm-abis retransmit [sample-delay]
Syntax Description
sample-delay
The number of duplicate samples that must be observed before the duplicate sample will be retransmitted. The sample-delay in a range of 5 to 255 or 100 to 5100 ms at 20 ms intervals.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how a retransmit delay of 100 ms:
Router(config)# interface Serial10/1/0.0Router(config-if)# encapsulation gsm-abisRouter(config-if)# gsm-abis local 10.10.10.1 5504Router(config-if)# gsm-abis remote 10.10.10.2 5504Router(config-if)# gsm-abis retransmit 5Related Commands
gsm-abis set dscp
To mark a packet by setting the differential services code point (DSCP) for GSM-Abis, use the gsm-abis set dscp Interface configuration command.
gsm-abis set dscp value
Note
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to set a retransmit delay of 100 ms:
Router(config)# interface Serial10/1/0.0Router(config-if)# encapsulation gsm-abisRouter(config-if)# gsm-abis local 10.10.10.1 5504Router(config-if)# gsm-abis remote 10.10.10.2 5504Router(config-if)# gsm-abis set dscp cs2idle-pattern
To specify the data pattern transmitted on the T1/E1 when missing packets are detected on the PWE3 circuit, use the idle-pattern command in CEM configuration mode.
idle-pattern [pattern]
no idle-pattern
Syntax Description
Defaults
Default idle-pattern is 0xFF.
Command Modes
CEM circuit configuration
Command History
Usage Guidelines
The idle-pattern data is sent to replace the data from missing packets.
Examples
The following example illustrates the use of the idle-pattern command:
Router# config tRouter(config)# interface cem 0/0/0Router(config-if)# no ip addressRouter(config-if)# cem 0Router(config-if-cem)# idle-pattern 0x55Router(config-if-cem)# xconnect 10.10.10.10 200 encapsulation mplsRouter(config-if-cem-xconn)# exitRouter(config-if-cem)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
ima-group
To define physical links as inverse multiplexing over ATM (IMA) group members, use the ima-group Interface configuration command. When you first perform the configuration or when you change the group number, the interface is automatically disabled, moved to the new group, and then enabled. To remove the port from the group, use the no form of this command.
ima-group group-number
Syntax Description
group-number
Specifies an IMA group number from 0 to 3. IMA groups can span multiple ports on a port adapter but cannot span port adapters.
Defaults
Physical links are not included in IMA groups.
Command Modes
Interface configuration
Command History
12.0(5)XK
This command was introduced.
12.4(4)MR
This command was incorporated.
Usage Guidelines
Use the ima-group interface command to configure a T1/E1 IMA port adapter interface as part of an IMA group.
Examples
The following example shows how to define an IMA group:
Router(config)# interface ATM0/0/0Router(config-if)# no ip addressRouter(config-if)# no atm ilmi-keepaliveRouter(config-if)# ima-group 0Related Commands
interface atm ima
To configure an ATM IMA group and enter interface configurations mode, use the interface atm ima global configuration command. If the group does not exist when the command is issued, the command automatically creates the group.
interface atm slot/ima<group-number>
Syntax Description
slot
Specifies the slot location of the ATM IMA port adapter.
group-number
Specifies an IMA group number from 0 to 3. You can create up to four groups.
Defaults
By default there are no IMA groups, only individual ATM links.
Command Modes
Global configuration
Command History
12.0(5)XE
This command was introduced.
12.4(4)MR
This command was incorporated.
Usage Guidelines
When a port is configured for IMA functionality, it no longer operates as an individual ATM link. Specifying ATM links as members of a group using the ima-group interface command does not enable the group. You must use the interface atm slot/ima<group-number> command to create the group.
Examples
The following example shows the how to create the IMA group:
Router(config)# interface ATM0/IMA0Router(config-if)# no ip addressRelated Commands
ip local interface
To configure the IP address of the provider edge (PE) router interface to be used as the source IP address for sending tunneled packets, use the ip local interface command in the pseudowire-class configuration mode. To remove the IP address, use the no form of this command.
ip local interface interface-name
no ip local interface interface-name
Syntax Description
interface-name
Name of the PE interface whose IP address is used as the source IP address for sending tunneled packets over a Layer 2 PW.
Defaults
No IP address is configured.
Command Modes
Pseudowire-class configuration
Command History
Usage Guidelines
Use the same local interface name for all pseudowire-classes configured between a pair of PE routers. It is highly recommended that you configure a loopback interface with this command. If you do not, the router chooses the "best available local address," which could be any IP address configured on a core-facing interface. This configuration could prevent a control channel from being established.
Note
Examples
The following example shows how to configure the IP address of the local loopback 0 as the source IP address for sending packets through an L2TPv3 session:
Router# config tRouter(config)# pseudowire-class l2tpRouter(config-pw-class)# ip local interface loopback 0Router(config-pw-class)# exitRouter(config)# exitRelated Commands
ip protocol
To configure the Layer 2 Tunnel Protocol (L2TP) or Universal Tunnel Interface (UTI) as the IP protocol used for tunneling packets in a Layer 2 PW, use the ip protocol command in the pseudowire-class configuration mode. To remove the IP protocol configuration, use the no form of this command.
ip protocol {l2tp | uti | udp}
no ip protocol {l2tp | uti | udp}
Syntax Description
Defaults
The default IP protocol is L2TP.
Command Modes
Pseudowire-class configuration
Command History
Usage Guidelines
The ip protocol uti command is not supported on the Cisco 3825 router. You can use the ip protocol command only if you have already entered the encapsulation l2tpv3 command.
Examples
The following example shows how to configure l2tp as the IP protocol used to tunnel packets in an L2TPv3 PW created from the pseudowire-class named "l2tp":
Router# config tRouter(config)# pseudowire-class l2tpRouter(config-pw-class)# encapsulation l2tpv3Router(config-pw-class)# ip protocol l2tpRouter(config-pw-class)# exitRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
pseudowire-class
Specifies the name of an L2TP pseudowire-class and enters pseudowire-class configuration mode.
ip rtp header-compression
To enable Real-Time Transport Protocol (RTP) header compression, use the ip rtp header-compression command in interface configuration mode. To disable RTP header compression, use the no form of this command.
ip rtp header-compression [passive | iphc-format | ietf-format] [periodic-refresh]
no ip rtp header-compression [passive | iphc-format | ietf-format] [periodic-refresh]
Syntax Description
Defaults
Disabled
For PPP interfaces, the default format for header compression is the IPHC format.
For High-Level Data Link Control (HDLC) and Frame Relay interfaces, the default format for header compression is the original proprietary Cisco format. The maximum number of compression connections for the proprietary Cisco format is 256.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can compress IP/UDP/RTP headers to reduce the size of your packets. Compressing headers is especially useful for RTP because RTP payload size can be as small as 20 bytes, and the uncompressed header is 40 bytes.
The passive Keyword
By default, the ip rtp header-compression command compresses outgoing RTP traffic. If you specify the passive keyword, outgoing RTP traffic is compressed only if incoming RTP traffic on the same interface is compressed. If you do not specify the passive keyword, all outgoing RTP traffic is compressed.
The passive keyword is ignored on PPP interfaces. PPP interfaces negotiate the use of header-compression, regardless of whether the passive keyword is specified. Therefore, on PPP interfaces, the passive keyword is replaced by the IPHC format, the default format for PPP interfaces.
The iphc-format Keyword
The iphc-format keyword indicates that the IPHC format of header compression that will be used. For PPP and HDLC interfaces, when the iphc-format keyword is specified, TCP header compression is also enabled. For this reason, the ip tcp header-compression command appears in the output of the show running-config command. Since both RTP header compression and TCP header compression are enabled, both UDP packets and TCP packets are compressed.
The iphc-format keyword includes checking whether the destination port number is even and is in the ranges of 16,385 to 32,767 (for Cisco audio) or 49,152 to 65,535 (for Cisco video). Valid RTP packets that meet the criteria (that is, the port number is even and is within the specified range) are compressed using the compressed RTP packet format. Otherwise, packets are compressed using the less-efficient compressed non-TCP packet format.
The iphc-format keyword is not available for interfaces that use Frame Relay encapsulation.
Note
The ietf-format Keyword
The ietf-format keyword indicates that the IETF format of header compression will be used. For HDLC interfaces, the ietf-format keyword compresses only UDP packets. For PPP interfaces, when the ietf-format keyword is specified, TCP header compression is also enabled. For this reason, the ip tcp header-compression command appears in the output of the show running-config command. Since both RTP header compression and TCP header compression are enabled, both UDP packets and TCP packets are compressed.
With the ietf-format keyword, any even destination port number higher than 1024 can be used. Valid RTP packets that meet the criteria (that is, the port number is even and is higher than 1024) are compressed using the compressed RTP packet format. Otherwise, packets are compressed using the less-efficient compressed non-TCP packet format.
The ietf-format keyword is not available for interfaces that use Frame Relay encapsulation.
Note
Support for Serial Lines
RTP header compression is supported on serial lines using Frame Relay, HDLC, or PPP encapsulation. You must enable compression on both ends of a serial connection.
Unicast or Multicast RTP Packets
This command can compress unicast or multicast RTP packets, and, hence, multicast backbone (MBONE) traffic can also be compressed over slow links. The compression scheme is beneficial only when you have small payload sizes, as in audio traffic.
Examples
The following example enables RTP header compression on the Serial1/0/0 interface and limits the number of RTP header compression connections to 10. In this example, the optional iphc-format keyword of the ip rtp header-compression command is specified.
Router> enableRouter# configure terminalRouter(config)# interface Serial1/0/0Router(config-if)# encapsulation pppRouter(config-if)# ip rtp header-compression iphc-formatRouter(config-if)# ip rtp compression-connections 10Router(config-if)# exitThe following example enables RTP header compression on the Serial1/0/0 interface and limits the number of RTP header compression connections to 20. In this example, the optional iphc-format keyword of the ip rtp header-compression command is specified.
Router> enableRouter# configure terminalRouter(config)# interface Serial1/0/0Router(config-if)# encapsulation pppRouter(config-if)# ip rtp header-compression iphc-formatRouter(config-if)# ip rtp compression-connections 20Router(config-if)# exitIn the following example, RTP header compression is enabled on the Serial1/0/0 interface and the optional periodic-refresh keyword of the ip rtp header-compression command is specified:
Router> enableRouter# configure terminalRouter(config)# interface Serial1/0/0Router(config-if)# encapsulation pppRouter(config-if)# ip rtp header-compression iphc-format periodic-refreshRouter(config-if)# ip rtp compression-connections 10Router(config-if)# exitRelated Commands
ip tcp header-compression
To enable TCP header compression, use the ip tcp header-compression command in interface configuration mode. To disable compression, use the no form of this command.
ip tcp header-compression [passive] [iphc-format] [ietf-format]
no ip tcp header-compression [passive] [iphc-format] [ietf-format]
Syntax Description
Defaults
Disabled
For PPP interfaces, default format for header compression is the IPHC format.
For High-Level Data Link Control (HDLC) and Frame Relay interfaces, the default format is as described in RFC 1144, Compressing TCP/IP Headers for Low-Speed Serial Links.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can compress the headers of your TCP/IP packets in order to reduce the size of your packets. TCP header compression is supported on serial lines using Frame Relay, HDLC, or PPP encapsulation. You must enable compression on both ends of a serial connection. Compressing the TCP header can speed up Telnet connections dramatically.
In general, TCP header compression is advantageous when your traffic consists of many small packets, not for traffic that consists of large packets. Transaction processing (usually using terminals) tends to use small packets and file transfers use large packets. This feature only compresses the TCP header, so it has no effect on User Datagram Protocol (UDP) packets or other headers.
Header Compression passive Keyword
By default, the ip tcp header-compression command compresses outgoing TCP traffic. This command includes an optional passive keyword. If you specify the passive keyword, outgoing TCP traffic is compressed only if incoming TCP traffic on the same interface is compressed. If you do not specify the passive keyword, all TCP traffic is compressed.
For PPP interfaces, the passive keyword is ignored. PPP interfaces negotiate the use of header-compression, regardless of whether the passive keyword is specified. Therefore, on PPP interfaces, the passive keyword is replaced by IPHC format, the default format for PPP interfaces.
Header Compression iphc-format Keyword
This command includes the iphc-format keyword. The iphc-format keyword indicates the type of header compression that will be used. For PPP and HDLC interfaces, when the iphc-format keyword is specified, Rapid Transport Protocol (RTP) header-compression is also enabled. For this reason, the ip rtp header-compression command appears in the output of the show running-config command. Because both TCP and RTP header compression are enabled, both TCP and UDP packets are compressed.
Note
Header Compression ietf-format Keyword
This command includes the ietf-format keyword. The ietf-format keyword indicates the type of header compression that will be used. For HDLC interfaces, the ietf-format compresses only TCP packets. For PPP interfaces, when the ietf-format keyword is specified, RTP header-compression is also enabled. For this reason, the ip rtp header-compression command appears in the output of the show running-config command. Because both TCP and RTP header compression are enabled, both TCP and UDP packets are compressed.
Note
Examples
The following example sets the first serial interface for header compression with a maximum of ten cache entries:
Router(config)# interface serial 0Router(config-if)# ip tcp header-compressionRouter(config-if)# ip tcp compression-connections 10The following example enables RTP header compression on the Serial1/0/0.0 subinterface and limits the number of RTP header compression connections to 10. In this example, the optional iphc-format keyword of the ip tcp header-compression command is specified:
Router(config)# interface serial1/0/0.0Router(config-if)# encapsulation pppRouter(config-if)# ip tcp header-compression iphc-formatRouter(config-if)# ip tcp compression-connections 10The following example enables RTP header compression on the Serial1/0/0.0 subinterface and limits the number of RTP header compression connections to 20. In this example, the optional ietf-format keyword of the ip tcp header-compression command is specified:
Router(config)# interface serial1/0/0.0Router(config-if)# ip tcp header-compression ietf-formatRouter(config-if)# ip tcp compression-connections 20Related Commands
ip tos (l2tp)
To configure the Type of Service (ToS) byte in the header of Layer 2 tunneled packets, use the ip tos command in the pseudowire-class configuration mode. To disable a configured ToS value or IP ToS reflection, use the no form of this command.
ip tos {value value | reflect}
no tos {value value | reflect}
Syntax Description
Defaults
The default ToS value is 0.
Command Modes
Pseudowire-class configuration
Command History
Usage Guidelines
The ip tos command allows you to manually configure the value of the ToS byte used in the headers of Layer 2 tunneled packets or to have the ToS value reflected from the IP header of the encapsulated packet.
Note
In addition, you can configure both IP ToS reflection and a ToS priority level (from 0 to 255) for a pseudowire-class. In this case, the ToS value in the tunnel header defaults to the value you specify with the ip tos value value command. IP packets received on the Layer 2 interface and encapsulated into the L2TPv3 session have their ToS byte reflected into the outer IP session, overriding the default value configured with the ip tos value value command.
Examples
In the following example, the ToS byte in the headers of tunneled packets in Layer 2 tunnels created from the pseudowire-class named "l2tp" is set as 5:
Router# config tRouter(config)# pseudowire-class l2tpRouter(config-pw-class)# ip tos 5Router(config-pw-class)# exitRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
pseudowire-class
Specifies the name of an L2TP pseudowire-class and enters pseudowire-class configuration mode.
ipran-mib backhaul-notify-interval
Use the ipran-mib backhaul-notify-interval command in the global configuration mode to specify the interval used to suppress the generation of the ciscoIpRanBackHaulRcvdUtil and the ciscoIpRanBackHaulSentUtil notifications from the CISCO-IP-RAN-BACKHAUL-MIB.
To set the interval used to suppress notifications, use the following configuration command or the no form of this command to remove the interval:
ipran-mib backhaul-notify-interval 60-900 seconds
Notifications are suppressed for the number of seconds specified. Notifications are not suppressed when this keyword is set to zero. The minimum interval is one minute and the maximum is fifteen minutes. When suppression is enabled, notifications are generated when a worse state is encountered. For example, the following transitions generate notifications:
•
•
Later transitions to lesser states are suppressed. For example, the following transitions do not generate notifications:
•
•
•
At the end of the specified interval, a notification is generated if the current state is different from the state reported by the last notification.
Syntax Description
Defaults
Defaults to 0 (notifications are not suppressed).
Command Modes
Interface configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification was removed. This command is supported to maintain compatibility.
Examples
Router# config tRouter(config)# ipran-mib backhaul-notify-interval 60Router(config)# ipran-mib backhaul-notify-interval 900Router(config)# no ipran-mib backhaul-notify-intervalRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
ipran-mib location
Use the ipran-mib location command in the global configuration mode to define the location of the device. It is also used to assist the network management system in properly displaying the topology of the system.
ipran-mib location location
Syntax Description
ipran-mib location ?
•
•
•
Defaults
cellSite.
Command Modes
Interface configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification was removed. This command is supported to maintain compatibility.
Examples
Router# config tRouter(config)# ipran-mib location aggSiteRouter(config)# ipran-mib location cellSiteRouter(config)# ipran-mib location undefinedRouter(config)# no ipran-mib locationRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
ipran-mib snmp-access
Defines the type of connectivity between the device and the network management system.
ipran-mib snmp-access
Use the ipran-mib snmp-access command in the global configuration mode to define the type of connectivity between the device and the network management system. It is used to limit the amount of traffic when in band polling.
ipran-mib snmp-access access
Syntax Description
ipran-mib snmp-access ?
•
•
•
Defaults
inBand.
Command Modes
Interface configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification was removed. This command is supported to maintain compatibility.
Examples
Router# config tRouter(config)# ipran-mib snmp-access inBandRouter(config)# ipran-mib snmp-access outOfBandRouter(config)# ipran-mib snmp-access undefinedRouter(config)# no ipran-mib snmp-accessRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
ipran-mib location
Defines the location of the device. It is also used to assist the network management system in properly displaying the topology of the system.
ipran-mib threshold-acceptable
Use the ipran-mib threshold-acceptable command in the global configuration mode to specify a level of traffic below which the instances of the cirbhBackHaulRcvdUtilState and cirbhBackHaulSentUtilState objects are marked as "acceptable." All changes to this threshold takes affect at the end of the current interval. The value for this object must be less than the values specified by ipran-mib threshold-warning and ipran-mib threshold-overloaded command keywords. This parameter corresponds to the cirbhBackHaulAcceptableThreshold object.
ipran-mib threshold-acceptable [20-100 Utilization (percent)]
Syntax Description
Defaults
60 percent.
Command Modes
Interface configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification was removed. This command is supported to maintain compatibility.
Examples
Router# config tRouter(config)# ipran-mib threshold-acceptable 50Router(config)# ipran-mib threshold-acceptable 70Router(config)# no ipran-mib threshold-acceptableRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
ipran-mib threshold-overloaded
Use the ipran-mib threshold-overloaded command in the global configuration mode to specify a level of traffic where the instances of the cirbhBackHaulRcvdUtilState and cirbhBackHaulSentUtilState objects are marked as "overloaded." Changes to this threshold take affect at the end of the current interval. The value for this object must be greater than the value specified for the cirbhBackHaulAcceptableThreshold object. Also, the value for this object must be greater than or equal to value of the cirbhBackHaulWarningThreshold object.
ipran-mib threshold-overloaded [40-100 Utilization default (percent)]
Syntax Description
Defaults
80 percent.
Command Modes
Interface configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification was removed. This command is supported to maintain compatibility.
Examples
Router# config tRouter(config)# ipran-mib threshold-overloaded 60Router(config)# ipran-mib threshold-overloaded 80Router(config)# no ipran-mib threshold-warningRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
ipran-mib threshold-warning
Use the ipran-mib threshold-warning command in the global configuration mode to specify a level of traffic where the instances of the cirbhBackHaulRcvdUtilState and cirbhBackHaulSentUtilState objects are marked as "warning."
All changes to this threshold take affect at the end of the current interval. The value for this object must be greater than the value specified for the ipran-mib threshold-acceptable command keyword.
Also, the value for this object must be less than or equal to value of the cirbhBackHaulOverloadedThreshold object. This parameter corresponds to the cirbhBackHaulWarningThreshold object.
ipran-mib threshold-warning [30-100 Utilization default (percent)]
Syntax Description
Defaults
70 percent.
Command Modes
Interface configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification was removed. This command is supported to maintain compatibility.
Examples
Router# config tRouter(config)# ipran-mib threshold-warning 60Router(config)# ipran-mib threshold-warning 80Router(config)# no ipran-mib threshold-warningRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
keepalive
To enable keepalive packets and to specify the number of times that the Cisco IOS software tries to send keepalive packets without a response before bringing down the interface or before bringing the tunnel protocol down for a specific interface, use the keepalive command in interface configuration mode. When the keepalive function is enabled, a keepalive packet is sent at the specified time interval to keep the interface active. To turn off keepalive packets entirely, use the no form of this command.
keepalive [period [retries]]
no keepalive [period [retries]]
Syntax Description
Defaults
period: 10 seconds
retries: 5
If you enter only the keepalive command with no arguments, the defaults for both arguments are used.
If you enter only the keepalive command and the timeout (period) parameter, the default number of retries (5) is used.
If you enter the no keepalive command, keepalive packets are disabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Keepalive Time Interval
You can configure the keepalive time interval, which is the frequency at which the Cisco IOS software sends messages to itself (Ethernet and Token Ring) or to the other end (serial and tunnel), to ensure that a network interface is alive. The interval is adjustable in 1-second increments, down to a minimum of 1 second. An interface is declared down after three update intervals have passed without receiving a keepalive packet unless the retry value is set higher.
Setting the keepalive timer to a low value is very useful for rapidly detecting Ethernet interface failures (such as a transceiver cable disconnecting, or cable that is not terminated).
Line Failure
A typical serial line failure involves losing the Carrier Detect (CD) signal. Because this sort of failure is typically noticed within a few milliseconds, adjusting the keepalive timer for quicker routing recovery is generally not useful.
Keepalive Packets with Tunnel Interfaces
GRE keepalive packets may be sent either from both sides of a tunnel or from just one side. If they are sent from both sides, the period and retry parameters can be different at each side of the link. If you configure keepalives on only one side of the tunnel, the tunnel interface on the sending side might perceive the tunnel interface on the receiving side to be down because the sending interface is not receiving keepalives. From the receiving side of the tunnel, the link appears normal because no keepalives were enabled on the second side of the link.
Dropped Packets
Because keepalive packets are treated as ordinary packets, it is possible that they will be dropped. To reduce the possibility that dropped keepalive packets will cause the tunnel interface to be taken down, increase the number of retries.
Note
Examples
The following example shows how to set the keepalive interval to 3 seconds:
Router(config)# interface ethernet 0Router(config-if)# keepalive 3The following example shows how to set the keepalive interval to 3 seconds and the retry value to 7:
Router(config)# interface tunnel 1Router(config-if)# keepalive 3 7load-interval
To change the length of time for which data is used to compute load statistics, use the load-interval interface configuration command. Use the no form of this command to revert to the default setting.
load-interval seconds
no load-interval seconds
Syntax Description
seconds
Length of time for which data is used to compute load statistics. A value that is a multiple of 30, from 30 to 600 (30, 60, 90, 120, and so forth).
Defaults
300 seconds (or 5 minutes)
Command Modes
Interface configuration
Command History
Usage Guidelines
If you want load computations to be more reactive to short bursts of traffic, rather than averaged over 5-minute periods, you can shorten the length of time over which load averages are computed.
If the load interval is set to 30 seconds, new data is used for load calculations over a 30-second period. This data is used to compute load statistics, including input rate in bits and packets per second, output rate in bits and packets per second, load, and reliability.
Load data is gathered every 5 seconds. This data is used for a weighted average calculation in which more-recent load data has more weight in the computation than older load data. If the load interval is set to 30 seconds, the average is computed for the last 30 seconds of load data.
The load-interval command allows you to change the default interval of 5 minutes to a shorter or longer period of time. if you change it to a shorter period of time, the input and output statistics that are displayed when you use the show interface command will be more current, and based on more instantaneous data, rather than reflecting a more average load over a longer period of time.
This command is often used for dial backup purposes, to increase or decrease the likelihood of a backup interface being implemented, but it can be used on any interface.
Examples
In the following example, the default 5-minute average is set to a 30-second average. A burst in traffic that would not trigger a dial backup for an interface configured with the default 5-minute interval might trigger a dial backup for this interface that is set for a shorter, 30-second interval.
Router(config)# interface serial 0Router(config-if)# load-interval 30Related Commands
match ip dscp
To identify a specific IP differential service code point (DSCP) value as a match criterion, use the match ip dscp class-map configuration command. To remove a specific IP DSCP value from a class map, use the no form of this command.
match ip dscp ip-dscp-value [ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value]
no match ip dscp ip-dscp-value [ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value ip-dscp-value]
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Class-map configuration
Command History
12.0(5)XE
This command was introduced.
12.0(9)S
This command was incorporated.
12.1(2)T
This command was incorporated.
12.4(4)MR
This command was incorporated.
Usage Guidelines
Up to eight IP DSCP values can be matched in one match statement. For example, if you wanted the IP DSCP values of 0, 1, 2, 3, 4, 5, 6, or 7 (note that only one of the IP DSCP values must be a successful match criterion, not all of the specified IP DSCP values), enter the match ip dscp 0 1 2 3 4 5 6 7 command.
This command is used by the class map to identify a specific IP DSCP value marking on a packet. The ip-dscp-value arguments are used as markings only. The IP DSCP values have no mathematical significance. For instance, the ip-dscp-value of 2 is not greater than 1. The value simply indicates that a packet marked with the ip-dscp-value of 2 is different than a packet marked with the ip-dscp-value of 1. The treatment of these marked packets is defined by the user through the setting of QoS policies in policy-map class configuration mode.
Examples
The following example shows how to configure the service policy called priority50 and attach service policy priority50 to an interface. In this example, the class map called ipdscp15 will evaluate all packets entering interface Gigabit Ethernet 0/0 for an IP DSCP value of 15. If the incoming packet has been marked with the IP DSCP value of 15, the packet will be treated with a priority level of 55.
Router(config)# class-map ipdscp15Router(config-cmap)# match ip dscp 15Router(config-cmap)# exitRouter(config)# policy-map priority55Router(config-pmap)# class ipdscp15Router(config-pmap-c)# priority55Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface GigabitEthernet0/0Router(config-if)# service-policy input priority55Related Commands
mode y-cable
To access the command mode that allows you to manually control the relays on the voice/WAN interface card (VWIC) or high-speed WAN interface card (HWIC), use the mode y-cable command in redundancy configuration mode.
mode y-cable
Syntax Description
This command has no parameters, it invokes the y-cable mode.
Defaults
There are no default settings or behaviors.
Command Modes
Redundancy configuration
Command History
12.2(8)MC2
This command was introduced.
12.2(15)MC1
This command was incorporated.
12.3(11)T
This command was incorporated.
12.4(2)MR
This command was incorporated.
Examples
The following example enables y-cable mode:
Router(config)# redundancyRouter(config-r)# mode y-cableRelated Commands
mpls ip
To enable MPLS forwarding of IPv4 packets along normally routed paths for a specified interface, use the mpls ip command in the interface configuration mode. To disable this feature, use the no form of this command.
mpls ip
no mpls ip
Syntax Description
This command has no arguments or keywords.
Defaults
MPLS forwarding of IPv4 packets along normally routed paths for the interface is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
MPLS forwarding of IPv4 packets along normally routed paths is sometimes called dynamic label switching. If dynamic label switching has been enabled for the platform when this command is issued on an interface, label distribution for the interface begins with the periodic transmission of neighbor discovery Hello messages on the interface. When the outgoing label for a destination routed through the interface is known, packets for the destination are labeled with that outgoing label and forwarded through the interface.
The no form of this command causes packets routed out through the interface to be sent unlabeled; this form of the command also terminates label distribution for the interface. However, the no form of the command does not affect the sending of labeled packets through any Label Switched Path (LSP) tunnels that might use the interface.
For an LC-ATM interface, the no form of this command prevents the establishment of label virtual circuits (LVCs) beginning at, terminating at, or passing through the interface.
Examples
The following example shows that label switching is enabled on the specified Ethernet interface:
Router# config tRouter(config)# configure terminalRouter(config-if)# interface Ethernet 0/1/0Router(config-if)# mpls ipRouter(config-if)# exitRouter(config)# exitRelated Commands
pseudowire-class
To specify the name of a Layer 2 pseudowire-class and enter pseudowire-class configuration mode, use the pseudowire-class command in the global configuration mode.
pseudowire-class [pw-class-name]
Syntax Description
Defaults
No pseudowire-class is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
The pseudowire-class command configures a pseudowire-class template that consists of configuration settings used by all attachment circuits bound to the class. A pseudowire-class includes the following configuration settings:
•
•
•
•
•
After entering the pseudowire-class command, the router switches to pseudowire-class configuration mode where PW settings can be configured.
Examples
The following example shows how to enter pseudowire-class configuration mode to configure a PW configuration template named "ether-pw":
Router# config tRouter(config)# pseudowire-class l2tpRouter(config-pw-class)# encapsulation l2tpv3Router(config-pw-class)# exitRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
pw-pvc
To configure permanent virtual circuit (PVC) mapping or rewrite the PW configured for a PVC, use the pw-pvc command. This command specifies the PW-side vpi/vci value to be used inside PW packet payload in sending and receiving PW packets for a specified PVC.
pw-pvc [pw-vpi]/[pw-vci]
Syntax Description
Defaults
By default, PW-side vpi/vci value is the same as the attachment circuit-side vpi/vci value.
Command Modes
l2transport VC mode
Command History
Examples
The following example illustrates the use of the pw-pvc command.
Router# config tRouter(config-if)# pvc 0/40 l2transportRouter(config-if-atm-l2trans-pvc)# encapsulation aal0Router(config-if-atm-l2trans-pvc)# pw-pvc 1/40Router(config-if-atm-l2trans-pvc)# xconnect 1.1.1.1 40 encapsulation mplsRouter(config-if-atm-l2trans-pvc-xconn)# exitRouter(config-if-atm-l2trans-pvc)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
xconnect
The xconnect command is used to bind an attachment circuit to a PW in one of the supported configuration modes.
redundancy
To access the command mode that allows you to configure aspects of redundancy, use the redundancy command in global configuration mode.
redundancy
Syntax Description
This command has no parameters; it invokes the redundancy mode.
Defaults
There are no default settings or behaviors.
Command Modes
Global configuration
Command History
12.2(8)MC2
This command was introduced.
12.2(15)MC1
This command was incorporated.
12.3(11)T
This command was incorporated.
12.4(2)MR
This command was incorporated.
Examples
The following example enables redundancy mode:
Router(config)# redundancyRouter(config-r)Related Commands
sample-rate
To specify in milliseconds the rate hardware samples the data on the attached circuit, use the sample-rate command in the circuit emulation (CEM) circuit configuration mode.
sample-rate [sample-rate]
Syntax Description
Command Modes
CEM circuit configuration
Command History
Examples
The following example illustrates the use of the sample-rate command:
Router# config tRouter(config)# interface cem 0/0/0Router(config-if)# no ip addressRouter(config-if)# cem 0Router(config-if-cem)# sample-rate 2Router(config-if-cem)# xconnect 10.10.10.10 200 encapsulation mplsRouter(config-if-cem-xconn)# exitRouter(config-if-cem)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands xconnect 10.10.10.10 200 encapsulation mpls
scrambling-payload
To improve data reliability, randomize the ATM cell payload frames. This avoids continuous non-variable bit patterns and improves the efficiency of the ATM's cell delineation algorithms. To do this, use the scrambling-payload command in interface configuration mode. The no form disables scrambling.
scrambling-payload
Syntax Description
This command has no arguments or keywords.
Defaults
By default, payload scrambling is on for E1 links and off for T1 1inks.
Command Modes
Interface configuration
Command History
12.0(5)XE
This command was introduced.
12.4(4)MR
This command was incorporated.
Usage Guidelines
Normally, you do not issue the scrambling-payload command explicitly, because the default value is sufficient. On T1 links, the default B8ZS line encoding normally assures sufficient reliability. The scrambling setting must match that of the far end.
Examples
The following example shows scrambling-payload on ATM configuration:
Router(config)# interface ATM0/0/0Router(config-if)# no ip addressRouter(config-if)# no atm ilmi-keepaliveRouter(config-if)# ima-group 0Router(config-if)# scrambling-payloadsequencing
To configure the direction in which sequencing is enabled for data packets in a Layer 2 PW, use the sequencing command in the 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
Defaults
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 PW are dropped only if you use the sequencing receive or sequencing both command.
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.
Set the sequence number to 0 in the slow path before packets are punted to the local CPU, because packets may become out of order.
Note
Examples
The following example shows how to enable sequencing in data packets in Layer 2 PWs 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 PW:
Router# config tRouter(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# sequencing bothRouter(config-pw-class)# exitRouter(config)# exitThe following example shows how to enable the disposition router to reset packet sequencing after it receives 1,000 out-of-order packets:
Router# config tRouter(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config-pw-class)# sequencing bothRouter(config-pw-class)# sequencing resync 1000Router(config-pw-class)# exitRouter(config)# exitRelated Commands
Related Commandspvc 0/40 l2transport
Related Commands encapsulation aal0
Related Commands pw-pvc 1/40
Related Commands xconnect 1.1.1.1 40 encapsulation mpls
show atm cell-packing
To display cell packing information for the Layer 2 attachment circuits (ACs) configured on your system, use the show atm cell-packing command in the EXEC mode.
show atm cell-packing
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release 3.4.1
This command was introduced on the Cisco XR 12000 Series Router.
12.4(12)MR2
This command was integrated into Cisco IOS Release 12.4(12)MR2.
Examples
The following sample output is from the show atm cell-packing command:
Router# show atm cell-packingavg # avg #Circuit local cells/pkt negotiated cells/pkt MCPTType MNCP rcvd MNCP sent (us)ATM0/2/0/1.200 vc 1/200 1 0 1 0 50ATM0/2/0/1.300 vc 1/300 1 0 1 0 50Related Commands
cell-packing
Packs multiple ATM cells into each MPLS or L2TPv3 packet.
atm cell-packing
Packs multiple ATM cells into each MPLS or L2TPv3 packet.
show cem circuit
To display a summary of circuit emulation (CEM) circuits, use the show cem circuit command in the privileged EXEC mode.
show cem circuit [cem-id]
Syntax Description
Command Modes
Privileged EXEC
Command HistoryGlobal configuration
Examples
The following is an example of the output generated by this command.
Router# show cem circuitCEM Int. ID Ctrlr Admin Circuit AC--------------------------------------------------------------CEM0/0/0 0 UP UP Enabled UPCEM0/0/1 1 UP UP Enabled UPCEM0/1/0 2 UP UP Enabled UPCEM0/1/1 3 UP UP Enabled UPCEM0/2/0 4 UP UP Enabled UPCEM0/2/1 5 UP UP Enabled UPRouter# show cem circuit 5CEM0/2/1, ID: 5, Line: UP, Admin: UP, Ckt: EnabledController state: upIdle Pattern: 0xFF, Idle cas: 0x8Dejitter: 4, Sample Rate: 1, Payload Size: 192Framing: Framed, (DS0 channels: 1-24)CEM Defects SetNoneSignalling: No CASRTP: No RTPIngress Pkts: 527521938 Dropped: 0Egress Pkts: 527521938 Dropped: 0CEM Counter DetailsInput Errors: 0 Output Errors: 0Pkts Missing: 0 Pkts Reordered: 0Misorder Drops: 0 JitterBuf Underrun: 0Error Sec: 0 Severly Errored Sec: 0Unavailable Sec: 0 Failure Counts: 0Pkts Malformed: 0Related Commands
show cem platform
To display platform-specific error counters for all circuit emulation (CEM) circuits, use the show cem platform command in the privileged EXEC mode.
show cem platform [interface]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command:
Router# show cem platformCEM0/0/0 errors:net2cem_drops =============== 50/527658758net2cem_drops_underflow === 26net2cem_drops_overflow ==== 24Last cleared 6d02hCEM0/0/1 errors:net2cem_drops =============== 50/527658759net2cem_drops_underflow === 25net2cem_drops_overflow ==== 25Last cleared 6d02hCEM0/1/0 errors:net2cem_drops =============== 2/526990836net2cem_drops_overflow ==== 2Last cleared neverCEM0/1/1 errors:net2cem_drops =============== 1/526982274net2cem_drops_overflow ==== 1Last cleared neverCEM0/2/0 errors:net2cem_drops =============== 51/527658758net2cem_drops_underflow === 26net2cem_drops_overflow ==== 25Last cleared 6d02hCEM0/2/1 errors:net2cem_drops =============== 48/527660498net2cem_drops_underflow === 24net2cem_drops_overflow ==== 24Last cleared 6d02hRouter# show cem platform cem0/0/1CEM0/0/1 errors:net2cem_drops =============== 50/527678398net2cem_drops_underflow === 25net2cem_drops_overflow ==== 25Last cleared 6d02hRelated Commands
show connection
To display the status of interworking connections, use the show connection command in the 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 1 describes the significant fields shown in the display.
Related Commands
show gsm-abis efficiency
To display history of the GSM compression/decompression efficiency averages at 1 second, 5 seconds, 1 minute, 5 minutes, and 1 hour intervals, use the show gsm-abis efficiency command in privileged EXEC mode. Efficiency is defined as the percentage of bandwidth savings obtained by using the compression/decompression algorithm to suppress GSM data.
show gsm-abis efficiency [history]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show gsm-abis efficiency ser0/1/0:0GSM-Abis(Serial0/2:0): efficiency (1sec/5sec/1min/5min/1hr) units(%%)compression efficiency (091/091/091/091/---) estimatedecompression efficiency (091/091/091/091/---)Router# sh gsm eff history ser0/1/0:0mwr1 04:00:00 PM Tuesday Apr 5 2005 est9999999999999999999999999999999999999999999999999999999999111111111111111111111111111111111111111111111111111111111110090 ************************************************************80 ************************************************************70 ************************************************************60 ************************************************************50 ************************************************************40 ************************************************************30 ************************************************************20 ************************************************************10 ************************************************************0....5....1....1....2....2....3....3....4....4....5....5....0 5 0 5 0 5 0 5 0 5GSM-Abis(Serial0/1/0:0) compression efficiency%/sec (last 60 secs)99999999911111111110090 ########*80 #########70 #########60 #########50 #########40 #########30 #########20 #########10 #########0....5....1....1....2....2....3....3....4....4....5....5....0 5 0 5 0 5 0 5 0 5GSM-Abis(Serial0/1/0:0) compression efficiency%/min (last 60 mins)* = maximum eff% # = average eff%1009080706050403020100....5....1....1....2....2....3....3....4....4....5....5....6....6....7.0 5 0 5 0 5 0 5 0 5 0 5 0GSM-Abis(Serial0/1/0:0) compression efficiency%/hr (last 72 hrs)* = maximum eff% # = average eff%mwr1 04:00:03 PM Tuesday Apr 5 2005 est9999999999999999999999999999999999999999999999999999999999111111111111111111111111111111111111111111111111111111111110090 ************************************************************80 ************************************************************70 ************************************************************60 ************************************************************50 ************************************************************40 ************************************************************30 ************************************************************20 ************************************************************10 ************************************************************0....5....1....1....2....2....3....3....4....4....5....5....0 5 0 5 0 5 0 5 0 5GSM-Abis(Serial0/1/0:0) decompression efficiency%/sec (last 60 secs)99999999911111111110090 ########*80 #########70 #########60 #########50 #########40 #########30 #########20 #########10 #########0....5....1....1....2....2....3....3....4....4....5....5....0 5 0 5 0 5 0 5 0 5GSM-Abis(Serial0/1/0:0) decompression efficiency%/min (last 60 mins)* = maximum eff% # = average eff%1009080706050403020100....5....1....1....2....2....3....3....4....4....5....5....6....6....7.0 5 0 5 0 5 0 5 0 5 0 5 0GSM-Abis(Serial0/1/0:0) decompression efficiency%/hr (last 72 hrs)* = maximum eff% # = average eff%Related Commands
show gsm-abis errors
To display error statistics counters of the GSM compression/decompression, use the show gsm-abis errors command in privileged EXEC mode.
show gsm-abis errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.4(2)MR
This command was introduced.
12.4(9)MR
The output response of this command was modified.
Examples
The following is an example of the output generated by this command.
Router# show gsm-abis errorsGSM-Abis(Serial0/1/0:0): backhaul_rxLostPakInd =========== 1/431956GSM-Abis(Serial0/1/0:0): backhaul_txLostPakInd =========== 1/432539GSM-Abis(Serial0/1/0:0): backhaul_missedPaks ============= 654/431956GSM-Abis(Serial0/1/0:0): backhaul_latePaks =============== 591GSM-Abis(Serial0/1/0:0): backhaul_lostPaks =============== 1GSM-Abis(Serial0/1/0:0): backhaul_txRset ================= 33GSM-Abis(Serial0/1/0:0): backhaul_overun ================= 29GSM-Abis(Serial0/1/0:0): compression_failures ============ 39661GSM-Abis(Serial0/1/0:0): backhaul_congestion_drops ======= 39661GSM-Abis(Serial0/1/0:0): backhaul_congestion_events ====== 1GSM-Abis(Serial0/1/0:0): backhaul_congestion_duration(sec) == 80GSM-Abis(Serial0/1/0:0): backhaul_congestion_bytes ========== 16498976Last cleared 00:14:24
Table A-3 describes the significant fields shown in the display.
Related Commands
show gsm-abis packets
To display packet statistics counters of the GSM compression/decompression, use the show gsm-abis packets command in privileged EXEC mode. Add the include retransmit to see the repetitive sub-rate samples at a specific configuration level (100 ms to 5100 ms).
show gsm-abis packets
show gsm-abis packets | include retransmit
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.4(2)MR
This command was introduced.
12.4(9)MR
The output response for the is command was modified.
Examples
The following is a show gsm-abis packets example of the output generated by this command.
Router# show gsm-abis packetsGSM-Abis(Serial0/1/0:0): packets:rxGSM_count =================== 164011txGSM_count ================= 164011rxBackhaul_packets ========== 163428txBackhaul_packets ========== 164011rxBackhaul_bytes ============ 7649833txBackhaul_bytes ============ 7638262rx_sampleCount ============== 40674728rx_suppressedCount ======== 36629047rx_retransmittedCount ===== 0rx_all_presentCount ======= 29tx_sampleCount ============== 4053144tx_presentCount =========== 66522tx_all_presentCount ======= 8backhaul_forced_inclusions == 1Last cleared 00:05:27The following is a show gsm-abis packets | include retransmit example of the output generated by this command.
Router# show gsm-abis packet | include retransmitrx-retransmittedCount ====== 71405Related Commands
show gsm-abis peering
To display peering status, statistics, and history of the GSM compression/decompression, use the show gsm-abis peering command in privileged EXEC mode.
show gsm-abis peering [details]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show gsm-abis peering ser0/1/0:0GSM-Abis(Serial0/1/0:0): Peering InformationGSM-Abis(Serial0/1/0:0): Local (10.10.10.1:5555) States:GSM-Abis(Serial0/1/0:0): Connect State Is: CONNECTEDGSM-Abis(Serial0/1/0:0): Local Alarm Is: CLEAR (NO ALARM)GSM-Abis(Serial0/1/0:0): Redundancy State: ACTIVEGSM-Abis(Serial0/1/0:0): Local Peer Version: 1.0GSM-Abis(Serial0/1/0:0): Remote (10.10.10.2:5555) States:GSM-Abis(Serial0/1/0:0): Remote Alarm Is: CLEAR (NO ALARM)GSM-Abis(Serial0/1/0:0): Remote Peer Version: 1.0Router# show gsm-abis peering detail ser0/1/0:0GSM-Abis(Serial0/1/0:0): Peering Information (Version 1.0) History with current state at the bottom GSM Peering History:Connect State Is: System Time------------------ -------------------DISCONNECT *Apr 26 19:00:20.303SND_CONNECT *Apr 26 15:48:30.568ACK_CONNECT *Apr 26 15:48:31.572**CONNECTED *Apr 26 15:50:57.113Local Peer Is: Conn Info System Time---------------------- ---------- -------------------CLEAR (NO ALARM) DISCONNECT *Mar 1 19:00:20.303SENDING AIS DISCONNECT *Apr 24 15:48:31.980**CLEAR (NO ALARM) CONNECTED *Apr 26 15:51:04.113Remote Peer Is: Conn Info Local Redundancy System Time---------------------- ---------- ---------------- -------------------UNAVAILABLE DISCONNECT STANDBV *Mar 1 19:00:20.303UNAVAILABLE DISCONNECT ACTIVE *Mar 1 15:50:57.113RX LOF RED) ALARM CONNECTED ACTIVE *Apr 26 15:50:57.117**CLEAR (NO ALARM) CONNECTED ACTIVE *Apr 26 15:50:57.117Current System Time: *Apr 26 16:00:33.133 estPeer Pak Info:No Backhaul Interface ======= 0 packetsBackhaul Encap Failures ===== 0 packetsGet CtrlPak Failures ======== 0 packetsRX Ctrl Paks ================ 7 packetsTX Ctrl Paks ================ 11 packetsOut Of Sequence Paks ======== 1 packetsOut Of Sequence Paks ====== 0 packetsUnsolicited Connect Paks ==== 1 (times)Unsolicited Connect Paks == 0 (times)Remove Retransmit Errors ==== 8 (error)Backhaul QOS classify drops = 0 packetsPeer Ctrl Type Info:Unknown Ctrl Types ========== 0 (times)Invalid Ctrl Lens =========== 0 (times)Missed Keepalives =========== 0 (times)Extra Keepalives ============ 0 (times)Peer Restarts =============== 5 (times)Due to Cfg Change ========= 2(times)Due to Internal Err ======= 1(times)Due to Lost Keepalive ===== 0 (times)Due to Interface Down ===== 0 (times)Due to Critical Pak Lost == 0 (times)Due to Interface Cleanup == 0 (times)Due to Excess Seq No Err == 0 (times)Peer Ctrl Variable Info:peer_enable ================= 1 (on/off)peer_ready ================== 1 (on/off)connecting ================== 0 (on/off)detectAlmErr ================ 1 (on/off)Peer Queue/Memory Info:Retransmition Contexts Used = 1 (in use)Data Buffers Used =========== 0 (in use)Seq Num: tx_fsn/tx_bsn ====== 4/4Seq Num: rx_fsn/rx_bsn ====== 4/4Adjacent serial number: `FTX1021A44Q'Related Commands
show gsm-abis traffic
To display traffic rates, in bits per second, at 1 second, 5 seconds, 1 minute, 5 minutes, and 1 hour intervals for GSM data transmitted and received over the backhaul, use the show gsm-abis traffic command in privileged EXEC mode.
show gsm-abis traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show gsm-abis trafficGSM-Abis(Serial1/1/0:0): traffic (1sec/5sec/1min/5min/1hr) units(bps)compression traffic( 964000/ 966758/ 965928/ 965937/ 48831)decompression traffic( 132000/ 136774/ 134428/ 134430/ 6799)Related Commands
show ip rtp header-compression
To show Real-Time Transport Protocol (RTP) header compression statistics, use the show ip rtp header-compression privileged EXEC command.
show ip rtp header-compression [type number] [detail]
Syntax Description
type number
(Optional) Interface type and number.
detail
(Optional) Displays details of each connection.
Note
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The detail keyword is not available with the show ip rtp header-compression command on a Route Switch Processor (RSP). However, the detail keyword is available with the show ip rtp header-compression command on a Versatile Interface Processor (VIP). Enter the show ip rtp header-compression type number detail command on a VIP to retrieve detailed information about RTP header compression on a specific interface.
Examples
The following is sample output from the show ip rtp header-compression command:
Router# show ip rtp header-compressionRTP/UDP/IP header compression statistics:Interface Multilink1 (compression off, IETF, RTP)Rcvd: 0 total, 0 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 430 total 429 compressed15122 bytes saved, 0 bytes sent0 efficiency improvement factorConnect: 16 rx slots, 16 tx slots, 0 long searches, 1 misses99% hit ratio, five minute miss rate 0 misses/sec, 0 max.Table A-3 describes the significant fields shown in the display.
Related Commands
show l2tp session
To display basic information about all active L2TP sessions, use the show l2tp session command in the user EXEC mode.
show l2tp session
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Command History
Usage Guidelines
Use the show l2tp session command to display information about all active sessions using L2TP.
Examples
The following is sample output from the show l2tp session command on a device with active L2TP sessions:
Router# show l2tp sessionL2TP Session Information Total tunnels 1 sessions 4LocID RemID TunID Username, Intf/ State Last Chg Uniq IDVcid, Circuit9547 61932 2220 100, AT0/0: est 2w6d 19580 61966 2220 1100, AT0/1:0/100 est 2w6d 219584 61970 2220 1200, AT0/1.1: est 2w6d 299595 61981 2220 1101, AT0/1:0/101 est 1w0d 37Router#Related Commands
show l2tp tunnel
To display basic information about all L2TP tunnels, use the show l2tp tunnel command in the user EXEC mode.
show l2tp tunnel
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Command History
Usage Guidelines
Use the show l2tp tunnel command to display information about all active tunnels using L2TP.
Examples
The following is sample output from the show l2tp tunnel command on a device with active L2F and L2TP tunnels:
Router# show l2tp tunnelL2TP Tunnel Information Total tunnels 1 sessions 4LocID RemID Remote Name State Remote Address Port Sessions L2TP Class/VPDN Group2220 55756 mwr2 est 99.99.99.99 0 4 l2tp_default_clRouter#Router#Router#Router#Related Commands
show mpls l2transport vc
To display information about Any Transport over MPLS (AToM) virtual connections (VCs) that have been enabled to route Layer 2 packets on a router, use the show mpls l2transport vc command in the privileged EXEC mode.
show mpls l2transport vc {[vcid vc-id] | [vcid vc-id-min vc-id-max]} [interface name [local-circuit-id]] [destination ip-address | name] [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify any keywords or arguments, the command displays a summary of all the VCs.
Examples
The output of the commands varies, depending on the type of Layer 2 packets being transported over the AToM VCs.
The following sample output shows information about the interfaces and VCs that have been configured to transport various Layer 2 packets on the router:
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- ------------------ --------------- ---------- ----------AT4/0 ATM AAL5 0/100 10.0.0.1 100 UPAT4/0 ATM AAL5 0/200 10.0.0.1 200 UPAT4/0.300 ATM AAL5 0/300 10.0.0.1 300 UPTable A-4 describes the significant fields shown in the display.
The following example shows information about the NSF/SSO and graceful restart capability. The SSO portion indicates when checkpointing data has either been sent (on active) or received (on standby). When SSO data has not been successfully sent or has been released, the SSO information is not shown.
Router# show mpls l2transport vc detailLocal interface: Fa0/1.1 down, line protocol down, Eth VLAN 2 upDestination address: 10.55.55.2, VC ID: 1002, VC status: downOutput interface: Fa0/0, imposed label stack {16}Preferred path: not configuredDefault path: activeTunnel label: imp-null, next hop point2pointCreate time: 02:03:29, last status change time: 02:03:26Signaling protocol: LDP, peer 10.55.55.2:0 downMPLS VC labels: local 16, remote unassignedGroup ID: local 0, remote unknownMTU: local 1500, remote unknownRemote interface description:Sequencing: receive disabled, send disabledSSO Descriptor: 10.55.55.2/1002, local label: 16SSM segment/switch IDs: 12290/8193, PWID: 8193VC statistics:packet totals: receive 0, send 0byte totals: receive 0, send 0packet drops: receive 0, send 0Table A-5 describes the significant fields shown in the display.
Related Commands
show mpls l2transport summary
Displays summary information about VCs that have been enabled to route AToM Layer 2 packets on a router.
show redundancy
To display information about the current redundant configuration and recent changes in states, use the show redundancy command in privileged EXEC mode.
show redundancy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(8)MC2
This command was introduced.
12.2(15)MC1
This command was incorporated.
12.3(11)T
This command was incorporated.
12.4(2)MR
This command was incorporated.
Usage Guidelines
In the standby group name group-name command, if you omit the group-name or if you enter a group name that does not begin with 1 or 2, the configuration will fail and there will be a mismatch in the information displayed by the show redundancy and show standby commands.
Examples
The following is an example of the output generated by this command.
Router# show redundancyMWR3825 is the Active RouterPrevious States with most recent at bottomINITL_INITL Dec 31 19:00:00.000LISTN_INITL Feb 28 19:00:15.568LISTN_LISTN Feb 28 19:00:15.568SPEAK_LISTN Feb 28 19:00:18.568SPEAK_SPEAK Feb 28 19:00:18.568STDBY_SPEAK Mar 19 08:54:26.191ACTIV_SPEAK Mar 19 08:54:26.191ACTIV_STDBY Mar 19 08:54:26.191ACTIV_ACTIV Mar 19 08:54:26.191INITL_ACTIV Mar 19 08:56:22.700INITL_INITL Mar 19 08:56:22.700INITL_LISTN Mar 19 08:56:28.544LISTN_LISTN Mar 19 08:56:28.652LISTN_SPEAK Mar 19 08:56:31.544SPEAK_SPEAK Mar 19 08:56:31.652SPEAK_STDBY Mar 19 08:56:34.544SPEAK_ACTIV Mar 19 08:56:34.544STDBY_ACTIV Mar 19 08:56:34.652ACTIV_ACTIV Mar 19 08:56:34.652INITL_ACTIV Mar 19 10:20:41.455INITL_INITL Mar 19 10:20:41.455INITL_LISTN Mar 19 10:20:49.243LISTN_LISTN Mar 19 10:20:49.299LISTN_SPEAK Mar 19 10:20:52.244SPEAK_SPEAK Mar 19 10:20:52.300SPEAK_STDBY Mar 19 10:20:55.244STDBY_STDBY Mar 19 10:20:55.300ACTIV_STDBY Mar 19 10:21:01.692ACTIV_ACTIV Mar 19 10:21:01.692Related Commands
show umts-iub congestion
To display history of the UMTS congestion, use the show umts-iub congestion command in privileged EXEC mode.
show umts-iub congestion
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show umts congestion atm 0/0/1UMTS(ATM0/0/1):Congestion: ONThrottled ATM cells: 415801Last congestion time: Dec 13 18:09.858 duration: 0h 0m 53sRelated Commands
show umts-iub efficiency
To display history of the UMTS interface efficiency averages at 1 second, 5 seconds, 1 minute, 5 minutes, and 1 hour intervals, use the show umts-iub efficiency command in privileged EXEC mode. Efficiency is defined as the percentage of bandwidth savings obtained by using the compression/decompression algorithm to suppress GSM data.
show umts-iub efficiency [history]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show umts effRouter# show umts efficiency atm 0/0/1UMTS(ATM0/0/1): efficiency (1sec/5sec/1min/5min/1hr) units(%%)decompression efficiency (100/100/100/100/---)compression efficiency (100/100/100/100/---)Related Commands
show umts-iub errors
To display the error statistics of the UMTS Iub interface, use the show umts-iub errors command in privileged EXEC mode.
show umts-iub errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following are examples of the output generated by this command.
Example 1:
Receiving traffic from shorthaul when the peering connection is not connected with the remote router yet.
Router# show umts errors atm 0/0/1UMTS-Iub(ATM0/0/1): backhaul_peer_not_ready ========= 55 is the number of packets received from shorthaul.Example 2
The peering connection is up and shorthaul is receiving traffic from a pvc that's NOT configured on the remote peering router's shorthaul.
Router# show umts errors atm 0/0/1UMTS-Iub(ATM0/0/1): no_remote_pvc =============== 55 is also the number of packets.Example 3
Error statistics that the code keeps track of if the number is not zero.
Router# show umts errorsUMTS-Iub(ATM1/1/1): backhaul_peer_not_ready ===== 6UMTS-Iub(ATM1/1/1): no_remote_pvc =============== 6UMTS-Iub(ATM1/1/1): backhaul_invalid_pak ======== 1UMTS-Iub(ATM1/1/1): decompression_failures ====== 1UMTS-Iub(ATM1/1/1): no_shorthaul_pak_available == 1UMTS-Iub(ATM1/1/1): compression_failures ======== 1UMTS-Iub(ATM1/1/1): no_backhaul_pak_available === 1UMTS-Iub(ATM1/1/1): no_backhaul_interface ======= 1UMTS-Iub(ATM1/1/1): backhaul_interface_down ===== 1UMTS-Iub(ATM1/1/1): backhaul_encap_failures ===== 1UMTS-Iub(ATM1/1/1): umts_encap_failures ========= 1UMTS-Iub(ATM1/1/1): no_local_pvc ================ 1UMTS-Iub(ATM1/1/1): no_remote_pvc =============== 1Related Commands
show umts-iub packets
To display packet statistics of the UMTS-Iub interface, use the show umts-iub packets command in privileged EXEC mode.
show umts-iub packets
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show umts packets atm 0/1/0UMTS-Iub(ATM0/1/0): packets:rxUMTS_count ================ 288799txUMTS_count ================ 288799rxUMTS_bytes ================ 13862352txUMTS_bytes ================ 13862352rxBackhaul_packets ========== 238484txBackhaul_packets ========== 247328rxBackhaul_bytes ============ 156844691txBackhaul_bytes ============ 15736957txBackhaul_pak_overrun ====== 0
Note
show umts-iub peering
To display the peering status, statistics, and history of the UMTS Iub interface, use the show umts-iub peering command in privileged EXEC mode.
show umts-iub peering [details]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following are examples of the output generated by this command.
Example 1
Router# show umts peering atm 0/0/1UMTS-Iub(ATM0/0/1): Peering InformationUMTS-Iub(ATM0/0/1): Local (40.40.40.40:6666) States:UMTS-Iub(ATM0/0/1): Connect State: OPENUMTS-Iub(ATM0/0/1): Redundancy State: ACTIVEUMTS-Iub(ATM0/0/1): Alarm State: RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1): Version: 1UMTS-Iub(ATM0/0/1): Remote (40.40.40.41:6666) States:UMTS-Iub(ATM0/0/1): Alarm State: RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1): Version: 1Example 2
Router# show umts peering detail atm 0/0/1UMTS-Iub(ATM0/0/1): Peering Information (Version 1)05/15/02 02:35:50 AM: BACKHAUL UP INIT --> CLOSED05/15/02 02:35:50 AM: OPEN CLOSED --> CON_SENT05/15/02 02:35:50 AM: CLOSE CON_SENT --> CLOSING05/15/02 02:35:50 AM: OPEN CLOSING --> STOPPING05/15/02 02:35:59 AM: TIMEOUT- STOPPING --> STOPPED05/15/02 02:36:28 AM: OPEN STOPPED --> CON_SENT05/15/02 02:36:28 AM: RCR+ CON_SENT --> ACK_SENT05/15/02 02:36:28 AM: RCA ACK_SENT --> OPEN03/01/02 12:00:37 AM: Local RX(NOT AVAILABLE) TX(NOT AVAILABLE), Remote RX(NOT AVAILABLE) TX(NOT AVAILABLE)05/15/02 02:35:52 AM: Local RX(NO ALARM ) TX(NO ALARM ), Remote RX(NOT AVAILABLE) TX(NOT AVAILABLE)05/15/02 02:36:28 AM: Local RX(NO ALARM ) TX(NO ALARM ), Remote RX(NO ALARM ) TX(NO ALARM )Peer Info:No Backhaul Interface ======= 5 packetsBackhaul Encap Failures ===== 2 packetsRX Ctrl Paks ================ 62 packetsRX Ctrl Bytes =============== 2078 bytesTX Ctrl Paks ================ 62 packetsTX Ctrl Bytes =============== 1365 bytesOut Of Sequence Paks ======== 0 packetsBackhaul QOS classify drops = 0 packetsVersion Mismatch ============ 0 packetsShorthaul Mismatch ========== 0 timesPeer Errors:No Pak Mem ================== 0 (times)No Event Mem ================ 0 (times)No VC Mem =================== 0 (times)No Alarm Link Mem =========== 0 (times)No Print Buf ================ 0 (times)Unknown Msg Type ============ 0 (times)Unexpected Attrs ============ 0 (times)RX Msg Length Err =========== 0 (times)Retransmit Counter Err ====== 0 (times)NULL Retransmit Err ========= 0 (times)PVC Delete Mismatch ========= 0 (times)PVC Add Existing ============ 0 (times)Example 3 with IMA
Router# show umts peeringUMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Peering InformationUMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Local (20.20.20.21:6666) States:UMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Connect State: OPENUMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Redundancy State: ACTIVEUMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Version: 4UMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Alarm State:UMTS-Iub(ATM0/0/0 - ATM0/0/0): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1 - ATM0/0/1): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Remote (20.20.20.20:6666) States:UMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Version: 4UMTS-Iub(ATM0/IMA0 - ATM0/IMA0): Alarm State:UMTS-Iub(ATM0/0/0 - ATM0/0/0): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1 - ATM0/0/1): RX(NO ALARM) TX(NO ALARM)
Note
Example 4 with Alternate Backhaul (192.168.10.2 to 192.168.10.1)
Router# show umts peeringUMTS-Iub(ATM0/IMA0): Peering InformationUMTS-Iub(ATM0/IMA0): Local (20.20.20.21:6666) States:UMTS-Iub(ATM0/IMA0): Connect State: OPENUMTS-Iub(ATM0/IMA0): Redundancy State: ACTIVEUMTS-Iub(ATM0/IMA0): Version: 3UMTS-Iub(ATM0/IMA0): Alarm State:UMTS-Iub(ATM0/0/0) ID(1): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1) ID(2): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/IMA0): Remote (20.20.20.20:6666) States:UMTS-Iub(ATM0/IMA0): Version: 3UMTS-Iub(ATM0/IMA0): Alarm State:UMTS-Iub(ATM0/0/0) ID(1): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1) ID(2): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/IMA0.1): Peering InformationUMTS-Iub(ATM0/IMA0.1): Local (192.168.10.2:6666) States:UMTS-Iub(ATM0/IMA0.1): Connect State: OPENUMTS-Iub(ATM0/IMA0.1): Redundancy State: ACTIVEUMTS-Iub(ATM0/IMA0.1): Version: 3UMTS-Iub(ATM0/IMA0.1): Remote (192.168.10.1:6666) States:UMTS-Iub(ATM0/IMA0.1): Version: 3Example 5 with Alarms over Primary Backhaul
Router# show umts peeringUMTS-Iub(ATM0/IMA0): Peering InformationUMTS-Iub(ATM0/IMA0): Local (20.20.20.21:6666) States:UMTS-Iub(ATM0/IMA0): Connect State: OPENUMTS-Iub(ATM0/IMA0): Redundancy State: ACTIVEUMTS-Iub(ATM0/IMA0): Version: 3UMTS-Iub(ATM0/IMA0): Alarm State:UMTS-Iub(ATM0/0/0) ID(1): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1) ID(2): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/IMA0): Remote (20.20.20.20:6666) States:UMTS-Iub(ATM0/IMA0): Version: 3UMTS-Iub(ATM0/IMA0): Alarm State:UMTS-Iub(ATM0/0/0) ID(1): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1) ID(2): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/IMA0.1): Peering InformationUMTS-Iub(ATM0/IMA0.1): Local (192.168.10.2:6666) States:UMTS-Iub(ATM0/IMA0.1): Connect State: OPENUMTS-Iub(ATM0/IMA0.1): Redundancy State: ACTIVEUMTS-Iub(ATM0/IMA0.1): Version: 3UMTS-Iub(ATM0/IMA0.1): Remote (192.168.10.1:6666) States:UMTS-Iub(ATM0/IMA0.1): Version: 3Example 6 with Congestion Control Status
Router# show umts-iub peering atm 0/ima0UMTS-Iub(ATM0/IMA0): Peering InformationUMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Local (20.20.20.21:6666) States:UMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Connect State: OPENUMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Redundancy State: ACTIVEUMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Congestion Control: ONUMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Version: 4UMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Alarm State:UMTS-Iub(ATM0/0/0 - ATM0/2): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1 - ATM0/3): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Remote (20.20.20.20:6666) States:UMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Version: 4UMTS-Iub(ATM0/IMA0 - ATM0/IMA1): Alarm State:UMTS-Iub(ATM0/0/0 - ATM0/2): RX(NO ALARM) TX(NO ALARM)UMTS-Iub(ATM0/0/1 - ATM0/3): RX(NO ALARM) TX(NO ALARM)Related Commands
show umts-iub pvc
To display the pvc mapping of the UMTS Iub interface, use the show umts-iub pvc command in privileged EXEC mode.
show umts-iub pvc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show umts pvcUMTS(ATM0/0/1): VCD infoVCD Mapping:Local Index(1) <--> Local VCD(1) <--> Remote Index(1)Local VCDs (not sent):Local VCDs (sent):Index(1), VPI/VCI(2/100), Encap(6), SC(0), Peak(1920), Avg/Min(0), Burst Cells(0)Remote VCDs:Index(1), VPI/VCI(2/100), Encap(6), SC(0), Peak(1920), Avg/Min(0), Burst Cells(0)show umts-iub traffic
To display traffic rates, in bits per second, at 1 second, 5 seconds, 1 minute, 5 minutes, and 1 hour intervals for UMTS data transmitted and received over the backhaul, use the show umts-iub traffic command in privileged EXEC mode.
show umts-iub traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of the output generated by this command.
Router# show umts-iub trafficUMTS-Iub(ATM1/0/0.1): traffic (1sec/5sec/1min/5min/1hr) units(bps)compression traffic( 2400/ 2496/ 2495/ 2496/ 203)decompression traffic( 81120/ 81120/ 80989/ 81006/ 6287)UMTS-Iub(ATM1/0/0.2): traffic (1sec/5sec/1min/5min/1hr) units(bps)compression traffic( 0/ 0/ 4/ 4/ 1)decompression traffic( 0/ 0/ 19/ 19/ 2)Related Commands
show xconnect all
To display information about xconnect attachment circuits and pseudowires (PWs), use the show xconnect all command in the privileged EXEC mode.
show xconnect {all | interface interface | peer ip-address {all | vcid vcid}} [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show xconnect all command can be used to display, sort, and filter basic information about all xconnect attachment circuits and PWs.
You can use the show xconnect all command output to help determine the appropriate steps to troubleshoot an xconnect configuration problem. More specific information about a particular type of xconnect can be displayed using the commands listed in the Related Commands table.
Examples
The following example shows show xconnect all command output in the brief (default) display format.
The sample output shows information about the interfaces and VCs that have been configured to transport various Layer 2 packets on the router:
Router# show xconnect allLegend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 StateUP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UPUP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UPIA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UPUP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UPTable A-6 describes the significant fields shown in the display.
The following example shows show xconnect all command output in the detailed display format:
Router# show xconnect all detailLegend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 StateUP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No HardwareXCST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UPInterworking: ip Local VC label 16Remote VC label 16pw-class: mpls-ipUP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UPInterworking: ip Local VC label 17Remote VC label 20pw-class: mpls-ipIA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UPInterworking: none Interworking: noneUP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UPInterworking: none Local VC label 23Remote VC label 17pw-class: mplsThe additional fields displayed in the detailed output are self-explanatory.
Related Commands
snmp-server enable traps ipran
To enable all ipran notifications via Simple Network Management Protocol (SNMP) notifications (traps) available on your system, use the snmp-server enable traps ipran command in global configuration mode. To disable ipran alarm-gsm notifications, use the no form of this command.
snmp-server enable traps ipran
no snmp-server enable traps ipran
Related Commands
This command has no arguments or keywords.
Defaults
This command is disabled by default. No notifications are sent.
Command Modes
Global configuration
Command History
Examples
The following is an example of the output generated by this command.
Router(config)# snmp-server enable traps ipranRelated Commands
snmp-server enable traps ipran alarm-gsm
To provide information alarms associated with GSM-Abis interfaces via Simple Network Management Protocol (SNMP) notifications (traps) available on your system, use the snmp-server enable traps ipran alarm-gsm command in global configuration mode. To disable ipran alarm-gsm notifications, use the no form of this command.
snmp-server enable traps ipran alarm-gsm
no snmp-server enable traps ipran alarm-gsm
This statement controls the generation of the cisco IpRanBackHaulGsmAlarm notification from the CISCO-IP-RAN-BACKHAUL-MIB.
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default. No notifications are sent.
Command Modes
Global configuration
Command History
Examples
The following is an example of the output generated by this command.
Router(config)# snmp-server enable traps ipran alarm-gsmRelated Commands
snmp-server enable traps ipran alarm-umts
To provide information alarms associated with UMTS-Iub interfaces via Simple Network Management Protocol (SNMP) notifications (traps) available on your system, use the snmp-server enable traps ipran alarm-umts command in global configuration mode. To disable ipran alarm-umts notifications, use the no form of this command.
snmp-server enable traps ipran alarm-umts
no snmp-server enable traps ipran alarm-umts
This statement controls the generation of the cisco IpRanBackHaulUmtsAlarm notification from the CISCO-IP-RAN-BACKHAUL-MIB.
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default. No notifications are sent.
Command Modes
Global configuration
Command History
Examples
The following is an example of the output generated by this command.
Router(config)# snmp-server enable traps ipran alarm-umtsRelated Commands
snmp-server enable traps ipran util
To provide information alarms associated with backhaul utilization via Simple Network Management Protocol (SNMP) notifications (traps) available on your system, use the snmp-server enable traps ipran util command in global configuration mode. To disable ipran alarm-gsm notifications, use the no form of this command.
snmp-server enable traps ipran util
no snmp-server enable traps ipran util
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default. No notifications are sent.
Command Modes
Global configuration
Command History
12.4(2)MR1
This command was introduced.
12.4(9)MR
Support for utilization notification has been removed and the command is provided only to maintain compatibility.
Examples
The following is an example of the output generated by this command.
Router(config)# snmp-server enable traps ipran utilRelated Commands
standalone
To specify that the Cisco 3825 router is being used in a standalone configuration (which impacts the relays on the VWIC/HWIC), use the standalone command in y-cable configuration mode. To use the router in a redundant configuration, use the no form of this command.
[no] standalone
Syntax Description
This command has no arguments or keywords.
Defaults
By default, the Cisco 3825 router is configured to be used in a redundant configuration (no standalone) and the relays are open.
Command Modes
Y-cable configuration
Command History
12.2(8)MC2
This command was introduced.
12.2(15)MC1
This command was incorporated.
12.3(11)T
This command was incorporated.
12.4(2)MR
This command was incorporated.
Usage Guidelines
Issuing the standalone command closes the relays on the VWICs/HWICs installed in the Cisco 3825 router.
Examples
The following example closes the relays so that the router can be used as a standalone device.
Router# standaloneRelated Commands
mode y-cable
Invokes y-cable mode.
standby use-interface
Specifies the interfaces to be used for health and revertive interfaces.
standby use-interface
To designate a loopback interface as a health or revertive interface, use the standby use-interface command in y-cable configuration mode.
standby use-interface interface {health | revertive | backhaul}
Syntax Description
Defaults
By default, the Cisco 3825 is configured to be used in a redundant configuration (no standalone) and the relays are open.
Command Modes
Y-cable configuration
Command History
Usage Guidelines
The loopback interfaces that you specify for the health and revertive interfaces must be the same loopback interfaces that you specified in the standby track command. In the standby track command, the decrement value for the revertive interface should always be less than that for other interfaces. We recommend that you use loopback101 for health and loopback102 for revertive.
The interface that you specify for the backhaul must be an MLPPP interface. If you want to use a serial interface as the backhaul, you must first configure that interface to be part of an MLPPP bundle. We recommend you that use multilink1 for the backhaul interface.
Examples
The following example specifies loopback101 as the health interface and loopback102 as the revertive interface:
Router# standby use-interface loopback101 healthRouter# standby use-interface loopback102 revertiveRouter# standby use-interface multilink1 backhaulRelated Commands
umts-iub backhaul-oam
To configure the local parameters required to provide OAM cells received on the UMTS ATM interface to be sent across the backhaul, use the umts-iub backhaul-oam Interface configuration command. To not transport the OAM cells across the backhaul, use the no form of this command.
Note
Additionally, the pvc-oam manage Interface configuration for ATM-VC commands at the PVC configuration level should be enabled for UMTS PVCs on the Cisco 3825 router. These PVCs will respond to OAM cells if the no version of the umts-iub backhaul-oam command is used.umts-iub backhaul-oam
Syntax Description
This command has no arguments or keywords.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the local parameters:
Router(config)# interface ATM0/2/0Router(config-if) atm umts-iubRouter(config-if) umts-iub local 10.10.10.2 5504Router(config-if) umts-iub backhaul-oamumts-iub backhaul-timer
To determine how often backhaul packets are sent for UMTS, use the umts-iub backhaul-timer Interface configuration command. This option is commonly used for High Speed Downlink Data Packet Access (HSDPA) offload environments. HSDPA traffic requires much more bandwidth than voice/signaling traffic on UMTS. Customers can offload the HSDPA traffic to an alternate backhaul media, such as metro-Ethernet while still maintaining low latency traffic (voice/signaling) on the existing T1/E1s. By configuring a separate UMTS peer for the HSPDA interface(s) and a timer value in the 3 ms to 8 ms range, customers can reduce CPU utilization on the Cisco 3825 router and save backhaul costs by sending HSDPA across the lower cost metro-Ethernet.
Note
umts-iub backhaul-timer ? [1-8] timer value(in ms)
Syntax Description
This command has no arguments or keywords.
Defaults
Timer value of 1 ms.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to determine how often the backhaul packets are sent for UMTS:
Router(config)# interface a0/3/0Router(config-if) umts-iub backhaul-timer ?<1-8> timer value(in msec)Router(config-if)#umts-iub congestion-control
To enable control under the UMTS shorthaul interface, use the umts-iub congestion-control Interface configuration command.
umts-iub congestion-control
Syntax Description
This command has no arguments or keywords.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to enable congestion control under UMTS shorthaul interface:
Router(config-if) umts-iub congestion-controlRelated Commands
umts-iub congestion control priority
Configures the congestion control priority under UMTS.
umts-iub congestion priority
To configure the congestion control priority for UMTS, use the umts-iub congestion priority PVC configuration command.
umts-iub congestion priority [protected] [2-9]
Syntax Description
Defaults
The default setting is 9.
Command Modes
PVC configuration
Command History
Examples
The following example shows how to configure the UMTS congestion priority:
Router(config-if) pvc 2/1 qsaalRouter(config-if-atm-vc) umts-iub congestion priority protectedRelated Commands
umts-iub congestion-control
Enables the congestion control under the UMTS shorthaul interface.
umts-iub local
To configure the local parameters required to establish an Internet Protocol/User Datagram Protocol (IP/UDP) backhaul connection for use with the ATM path on the UMTS Iub interface, use the umts-iub local Interface configuration command.
umts-iub local [ip-address] [port]
Syntax Description
ip-address
(Optional) The IP address for the entry you wish to establish.
port
(Optional) The port you want to use for the entry you wish to establish.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the local parameters:
Router(config)# interface ATM0/2/0Router(config-if) atm umts-iubRouter(config-if) umts-iub local 10.10.10.2 5504Related Commands
umts-iub remote
Configures the remote parameters for an IP/UDP backhaul connection.
umts-iub remote
To configure the remote parameters required to establish an Internet Protocol/User Datagram Protocol (IP/UDP) backhaul connection for use with the ATM path on the UMTS Iub interface, use the umts-iub local Interface configuration command.
umts-iub remote [ip-address] [port]
Syntax Description
ip-address
(Optional) The IP address for the entry you wish to establish.
port
(Optional) The port you want to use for the entry you wish to establish.
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the remote parameters:
Router(config)# interface ATM0/2/0Router(config-if) atm umts-iubRouter(config-if) umts-iub remote 10.10.10.1 5502Related Commands
umts-iub local
Configures the local parameters for an IP/UDP backhaul connection.
umts-iub set dscp
To mark a packet by setting the differential services code point (DSCP) for UMTS-Iub value for the backhaul packet including the peering and data generated from the shorthaul, use the umts-iub set dscp Interface configuration command.
umts-iub set dscp value
Note
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the parameters:
Router(config)# interface ATM0/2/0Router(config-if) atm umts-iubRouter(config-if) umts-iub set dscp [value]Related Commands
umts-iub set peering dscp
This command overwrites the interface default value defined in the umts-iub set dscp value and is used to tag peering backhaul packet.
umts-iub set dscp
To overwrite the interface default value defined in the umts-iub set dscp value for UMTS shorthaul interfaces and is used to tag the backhaul packet generated from traffic from a PVC, use the umts-iub set dscp ATM-VC configuration command.
umts-iub set dscp value
Note
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
ATM-VC configuration
Command History
Examples
The following example shows how to configure the remote parameters:
Router(config)# interface ATM0/2/0Router(config-if)# atm umts-iubRouter(config-if)# umts-iub set dscp valueRouter(config-if-atm-vc)# umts-iub set dscp valueRelated Commands
umts-iub set peering dscp
To overwrite the interface default value defined in the umts-iub set dscp value and is used to tag the peering backhaul packet, use the umts-iub set peering dscp Interface configuration command.
umts-iub set peering dscp value
Note
Syntax Description
Defaults
There are no default settings or behaviors.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the parameters:
Router(config)# interface ATM0/2/0Router(config-if) atm umts-iubRouter(config-if) umts-iub set dscp valueRelated Commands
umts local
To configure local ip address for the atm subinterfaces, use the umts local Sub-Interface configuration command. This command is used when you want to off load PVC traffic from a physical ATM shorthaul to an alternate backhaul. For each alternate backhaul, you need to create a logical shorthaul by creating an atm subinterface. Traffic for the PVCs configured under this logical shorthaul will go through the corresponding alternate backhaul.
umts local [ip-address]
Syntax Description
Command Modes
Sub-Interface configuration
Command History
Examples
The following example illustrates the use of the umts local command in Sub-Interface command mode.
Router(config)# interface ATM0/2/0Router(config-if)# atm umts-iubRouter(config-subif)# atm umtsRouter(config-subif)# umts local 10.10.10.2 5504
Note
Related Commands
atm umts
This command enables the UMTS mode for alternate backhaul.
umts remote [ip-address]
This command configures remote IP address for alternate backhaul.
umts remote
To configure local ip address for the atm subinterfaces, use the umts remote Sub-Interface configuration command. This command is used when you want to off load one or more PVC's traffic from a physical ATM shorthaul to go over alternate backhaul. For each alternate backhaul, you need to create a logical shorthaul by creating an atm subinterface. Traffic for the PVCs configured under this logical shorthaul will go through the corresponding alternate backhaul.
umts remote [ip-address]
Syntax Description
Command Modes
Sub-Interface configuration
Command History
Examples
The following example illustrates the use umts remote command.
Router(config)# interface ATM0/2/0Router(config-if)# atm umts-iubRouter(config-subif)# atm umtsRouter(config-subif)# umts remote 10.10.10.1 5502
Note
Related Commands
atm umts
This command enables the UMTS mode for alternate backhaul.
umts local [ip-address]
This command configures the remote IP address for alternate backhaul.
xconnect
To bind an attachment circuit to a pseudowire (PW), use the xconnect command in one of the supported configuration modes. To restore the default values, use the no form of this command.
xconnect peer-ip-address | vcid | pseudowire-parameters [sequencing {transmit | receive | both | one-to-one}] [ignore-vpi-vci]
Syntax Description
Defaults
The attachment circuit is not bound to the PW.
Command Modes
CEM circuit configuration
Interface configuration
Subinterface configuration
l2transport configuration (for ATM)
Connect configuration mode Global configuration
Command History
Usage Guidelines
The combination of the peer-ip-address and vcid arguments must be unique on the router. Each xconnect configuration must have a unique combination of peer-ip-address and vcid configuration.
Note
The same vcid value that identifies the attachment circuit must be configured using the xconnect command on the local and remote PE router. The vcid creates the binding between a PW and an attachment circuit.
The pw-class pw-class-name value binds the xconnect configuration of an attachment circuit to a specific pseudowire-class. In this way, the pseudowire-class configuration serves as a template that contains settings used by all attachment circuits bound to it with the xconnect command.
Note
Keyword ignore-vpi-vci
Using the xconnect command with keyword ignore-vpi-vci provides benefits over using the pw-pvc command for PVC mapping.
Originally, PVC mapping was done through the pw-pvc pw-vpi/pw-vci command. When the MWR received the MPLS PW packet, it decoded the PW payload and looked up the PW VPI/VCI value to see if it matched any local configured PVC values. If a match was made, the PW-VPI/PW-VCI was translated to the AC-side VPI/VCI and the cell was sent to the local PVC. Without a match, the MWR dropped the received PW packet. When the MWR generated the PW packet, it used configured pw-vpi/pw-vci values. In this case, the PVC mapping was done completely on the MWR and was transparent to the remote end.
The scenario differs when keyword ignore-vpi-vci is configured. For N:1 with N=1 special case, when the PW packet is received from the MWR, the receiving router ignores the VPI/VCI value contained in the PW payload. It does a blind rewrite to use the AC-side VPI/VCI and sends the cell to the AC side PVC.
The xconnect command with keyword ignore-vpi-vci results in the PVC mapping being done in a cooperative way if the MWR works the same way as the receiving router. Without this command, the MWR checks the VPI/VCI value inside PW packet for matches against the local configured PVC or PVC-mapping. With the ignore-vpi-vci keyword configured, the MWR ignores the VPI/VCI header inside the received PW packet and does a blind rewrite with the local configured AC-side PVC's VPI/VCI value.
Note
Examples
The following example illustrates the configured xconnect service for an ATM interface by binding the ATM circuit to the PW named 123 with a remote peer 10.0.3.201. The configuration settings in the pseudowire-class named ATM-xconnect are used.
Router# config tRouter(config)# interface ATM 0/0/0Router(config-if)# xconnect 10.0.3.201 123 pw-class ATM-xconnectRouter(config-if-xconn)# exitRouter(config-if)# exitRouter(config)# exitThe following example illustrates PVC mapping using the keyword ignore-vpi-vci with the xconnect command. The example shows both the MWR and remote end (7600) routers.
MWR:
Router# config tRouter(config)# interface ATM 0/0Router(config-if)# pvc 0/10 12transportRouter(config-if-atm-12trans-pvc)# encapsulation aa10Router(config-if-atm-12trans-pvc)# xconnect 10.10.10.10 100 encapsulation mpls ignore-vpi-vciRouter(config-if-atm-12trans-pvc-xconn)# exitRouter(config-if-atm-12trans-pvc)# exitRouter(config-if)# exitRouter(config)# exit7600:
Router# config tRouter(config)# interface ATM 0/0Router(config-if)# pvc 2/20 12transportRouter(config-if-atm-12trans-pvc)# encapsulation aa10Router(config-if-atm-12trans-pvc)# xconnect 20.20.20.20 100 encapsulation mplsRouter(config-if-atm-12trans-pvc-xconn)# exitRouter(config-if-atm-12trans-pvc)# exitRouter(config-if)# exitRouter(config)# exitRelated Commands
xconnect logging redundancy
To enable system message log (syslog) reporting of the status of the xconnect redundancy group, use the xconnect logging redundancy command in global configuration mode. To disable syslog reporting of the status of the xconnect redundancy group, use the no form of this command.
xconnect logging redundancy
no xconnect logging redundancy
Syntax Description
This command has no arguments or keywords.
Defaults
Syslog reporting of the status of the xconnect redundancy group is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable syslog reporting of the status of the xconnect redundancy group.
Examples
The following example enables syslog reporting of the status of the xconnect redundancy group and shows the messages that are generated during switchover events:
Router# config tRouter(config)# xconnect logging redundancyRouter(config)# exitActivating the Primary Member
00:01:07: %XCONNECT-5-REDUNDANCY: Activating primary member 10.55.55.2:1000Activating the Backup Member:
00:01:05: %XCONNECT-5-REDUNDANCY: Activating secondary member 10.55.55.3:1001Related Commands
xconnect
Binds an Ethernet, 802.1q VLAN, or Frame Relay attachment circuit to an L2TPv3 PW for xconnect service and enters xconnect configuration mode.
