-
Cisco IOS Wide-Area Networking Command Reference
-
Introduction
-
accelerator through cpu-threshold
-
de-bit through exp
-
fdl through frame-relay lapf n200
-
frame-relay lapf n201 through fr-atm connect dlci
-
hello through lz entropy-check
-
mace enable through rtcp-regenerate
-
sequence-interval through show platform software otv fp
-
show smds addresses through waas export
-
x25 accept-reverse through x25 pvc XOT
-
x25 pvc rbp local through xot access-group
-
Index
-
Feedback
mace enable through rtcp-regenerate
- mace enable
- mace monitor waas
- map-class frame-relay
- map-group
- map-list
- match fr-de
- match protocol (L2TPv3)
- match tcp
- max-lsp-lifetime (OTV)
- metadatacache
- mls l2tpv3 reserve
- monitor l2tun counters tunnel l2tp
- neighbor (L2VPN Pseudowire Switching)
- neighbor (VPLS)
- nsf (OTV)
- oam-ac emulation-enable
- optimize tfo
- otv active-source
- otv adjacency-server unicast-only
- otv control-group
- otv data-group
- otv filter-fhrp
- otv fragmentation
- otv isis authentication
- otv isis csnp-interval
- otv isis hello-interval
- otv isis hello-multiplier
- otv isis hello padding
- otv isis lsp-interval
- otv isis metric
- otv isis overlay
- otv isis priority
- otv isis retransmit-interval
- otv isis retransmit-throttle-interval
- otv isis site
- otv join-interface
- otv mac flood
- otv site bridge-domain
- otv site-identifier
- otv suppress arp-nd
- otv use-adjacency-server unicast-only
- otv vpn-name
- packet drop during-authorization
- parameter-map type waas
- passthrough
- password
- password (L2TP)
- peer-cert-verify enable
- peer-cipherlist
- peer-ssl-version
- policy-map type mace
- policy-map type waas
- platform trace runtime process forwarding-manager module mfr
- prc-interval (OTV)
- precedence (Frame Relay VC-bundle-member)
- protect (Frame Relay VC-bundle-member)
- protocol (L2TP)
- pseudowire
- pseudowire-class
- pvc (Frame Relay VC-bundle)
- read-ahead
- receive-window
- retransmit
- rewrite ingress tag
- rd (VPLS)
- route-target (VPLS)
- rtcp-regenerate
mace enable
To apply the global Measurement, Aggregation, and Correlation Engine (MACE) policy on an interface, use the mace enable command in interface configuration mode. To disable the MACE policy on an interface, use the no form of this command.
Usage Guidelines
Use the mace enable command to apply the global MACE policy on an interface. This command applies the global MACE policy in both directions, ingress and egress, of the interface. The MACE runs on the traffic coming over this interface. MACE policy is limited to targets for which the Wide-Area Application Services (WAAS) policy can be enabled. MACE supports all the interfaces that are supported by WAAS.
NoteMACE does not interoperate with Network Address Translation (NAT) on the ingress (LAN) interface if the ip nat inside command is configured on the ingress interface. However, MACE interoperates with NAT on the egress (WAN) interface if the ip nat outside command is configured on the egress interface.
Before you enable MACE, you must configure the following:
- Flow record of type MACE
- Flow exporter
- Flow monitor of type MACE
- Class map of type WAAS
- Policy map of type MACE
When you configure the mace enable command, the metrics of the matching flows are collected and updated on every packet. When the export timer expires, these metrics are aggregated and exported to various collectors according to the defined configuration. On optimizing the flow by using WAAS, the metrics of both segments, pre-WAAS and post-WAAS, of the flow are exported.
Examples
The following example shows how to enable MACE on Ethernet interface 0/0:
Device(config)# interface ethernet0/0 Device(config-if)# mace enablemace monitor waas
To enable the Measurement, Aggregation, and Correlation Engine (MACE) monitoring on Wide Area Application Services (WAAS), use the mace monitor waascommand in global configuration mode. To disable MACE monitoring, use the no form of this command.
mace monitor waas [ all | optimized ] [name] monitor-name
no mace monitor waas [ all | optimized ] [name] monitor-name
Usage Guidelines
Usethe mace monitor waascommand to enable MACE for all WAAS instances that run on the router.
MACE monitors all the flows on which WAAS is active for optimization.
To enable MACE on WAAS, you must first configure the following:
- A flow record of type MACE
- A flow exporter
- A flow monitor of type MACE
When you use the mace monitor waas command along with the optimized keyword, MACE monitors all the flows on which WAAS is active for optimization.
When you use this command along with the all keyword, MACE monitors all the flows configured in a WAAS policy. This includes the flows that are subject to either WAAS optimization or pass-through actions.
When you use this command without the all or optimized keyword, MACE monitors all WAAS classes that have the optimize keyword configured in them. MACE also exports the flows that are tagged by WAAS as passthrough, even when they match the classes with optimize actions in them.
NoteIf you wish to choose a subset of WAAS classes, you must create a global MACE policy that includes the desired classes.
map-class frame-relay
To specify a map class to define quality of service (QoS) values for a virtual circuit (VC), use the map-class frame-relay command in global configuration mode. To remove a map class, use the no form of this command.
Command History
Release
Modification
11.2
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
After you specify the named map class, you can specify the QoS parameters--such as incoming and outgoing committed information rate (CIR), committed burst rate, excess burst rate, and the idle timer--for the map class.
To specify the protocol-and-address combination to which the QoS parameters are to be applied, associate this map class with the static maps under a map list.
Examples
The following example specifies a map class “hawaii” and defines three QoS parameters for it. The “hawaii” map class is associated with a protocol-and-address static map defined under the map-listcommand.
map-list bermuda source-addr E164 123456 dest-addr E164 654321 ip 10.108.177.100 class hawaii appletalk 1000.2 class hawaii map-class frame-relay hawaii frame-relay cir in 2000000 frame-relay cir out 56000 frame-relay be out 9000Related Commands
Command
Description
frame-relay bc
Specifies the incoming or outgoing Bc for a Frame Relay VC.
frame-relay be
Sets the incoming or outgoing Be for a Frame Relay VC.
frame-relay cir
Specifies the incoming or outgoing CIR for a Frame Relay VC.
frame-relay idle-timer
Specifies the idle timeout interval for an SVC.
map-group
To associate a map list with a specific interface, use the map-group command in interface configuration mode.
Command History
Release
Modification
11.2
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
A map-group association with an interface is required for switched virtual circuit (SVC) operation. In addition, a map list must be configured.
The map-group command applies to the interface or subinterface on which it is configured. The associated E.164 or X.121 address is defined by the map-list command, and the associated protocol addresses are defined by using the class command under the map-list command.
Examples
The following example configures a physical interface, applies a map group to the physical interface, and then defines the map group:
interface serial 0 ip address 172.10.8.6 encapsulation frame-relay map-group bermuda frame-relay lmi-type q933a frame-relay svc map-list bermuda source-addr E164 123456 dest-addr E164 654321 ip 10.1.1.1 class hawaii appletalk 1000.2 class rainbowmap-list
To specify a map group or map list and link it to a local E.164 or X.121 source address and a remote E.164 or X.121 destination address for Frame Relay switched virtual circuits (SVCs), use the map-list command in global configuration mode. To delete a previous map-group link, use the no form of this command.
map-list map-group-name source-addr { e164 | x121 } source-address dest-addr { e164 | x121 } destination-address clps number [ cdps number ]
no map-list map-group-name source-addr { e164 | x121 } source-address dest-addr { e164 | x121 } destination-address clps number [ cdps number ]
Syntax Description
map-group-name
Name of the map group or map list. This map group or list must be associated with a physical interface.
source-addr {e164 | x121}
Specifies the type of source address.
source-address
Address of the type specified (E.164 or X.121).
dest-addr {e164 | x121}
Specifies the type of destination address.
destination-address
Address of the type specified (E.164 or X.121).
clps number
Specifies the calling party subaddress. The subaddress range is from 1 to 9.
cdps number
(Optional) Specifies the called party subaddress. The subaddress range is from 1 to 9.
Command History
Release
Modification
11.2
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
15.0(1)M
This command was modified in a release earlier than Cisco IOS Release 15.0(1)M. The clps number and cdps numberkeyword and argument pairs were added.
Usage Guidelines
Use the map-class command to define quality of service (QoS) parameters--such as incoming and outgoing committed information rate (CIR), committed burst rate, excess burst rate, and the idle timer--for the static maps defined under a map list or map group.
Each SVC needs to use a source and destination number, in much the same way that a public telephone network needs to use source and destination numbers. These numbers allow the network to route calls from a specific source to a specific destination. This specification is done through map lists or map groups.
Depending on switch configuration, addressing can take either of two forms: E.164 or X.121.
An X.121 address number is 14 digits long and has the following form:
Z CC P NNNNNNNNNNThe table below describes the codes in an X.121 address number form.
Table 1 X.121 Address Numbers Code
Meaning
Value
Z
Zone code
3 for North America
C
Country code
10-16 for the United States
P
Public data network (PDN) code
Provided by the PDN
N
10-digit number
Set by the network for the specific destination
An E.164 number has a variable length; the maximum length is 15 digits. An E.164 number has the fields shown in the figure below and described in the table below.
Examples
In the following SVC example, if IP or AppleTalk triggers the call, the SVC is set up with the QoS parameters defined within the class “example”.
An SVC triggered by either protocol results in two SVC maps, one for IP and one for AppleTalk. Two maps are set up because these protocol-and-address combinations are heading for the same destination, as defined by the dest-addr keyword and the values following it in the map-list command.
map-list test source-addr e164 123456 dest-addr e164 654321 clps 2 cdps 4 ip 10.1.1.1 class example appletalk 1000.2 class examplematch fr-de
To match packets on the basis of the Frame Relay discard eligibility (DE) bit setting, use the match fr-decommand in class-map configuration or policy inline configuration mode. To remove the match criteria, use the no form of this command.
Command Modes
Class-map configuration (config-cmap)
Policy inline configuration (config-if-spolicy-inline)Command History
Release
Modification
12.0(25)S
This command was introduced for the Cisco 7500 series router.
12.0(26)S
This command was integrated into Cisco IOS Release 12.0(26)S and implemented on the Cisco 7200 series router.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
12.4(15)T2
This command was integrated into Cisco IOS Release 12.4(15)T2.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB and implemented on the Cisco 7300 series router.
15.1(3)T
This command was integrated into Cisco IOS Release 15.1(3)T for Cisco Performance Monitor. Support was added for policy inline configuration mode.
12.2(58)SE
This command was integrated into Cisco IOS Release 12.2(58)SE for Cisco Performance Monitor.
Usage Guidelines
This command can be used with both Flexible NetFlow and Performance Monitor. These products use different commands to enter the configuration mode in which you issue this command.
Cisco Performance Monitor in Cisco IOS Release 15.1(3)T and 12.2(58)SE
You must first enter the service-policy type performance-monitor inlinecommand.
Examples
The following example creates a class named match-fr-de and matches packets on the basis of the Frame Relay DE bit setting.
Router(config)# class-map match-fr-de Router(config-cmap)# match fr-deExamples
The following example shows how to use the policy inline configuration mode to configure a service policy for Performance Monitor. The policy specifies that packets traversing Ethernet interface 0/0 that match the Frame Relay DE bit setting will be monitored based on the parameters specified in the flow monitor configuration named fm-2:
Router(config)# interface ethernet 0/0 Router(config-if)# service-policy type performance-monitor inline input Router(config-if-spolicy-inline)# match fr-de Router(config-if-spolicy-inline)# flow monitor fm-2 Router(config-if-spolicy-inline)# exitRelated Commands
Command
Description
class-map
Creates a class map to be used for matching packets to a specified class.
service-policy type performance-monitor
Associates a Performance Monitor policy with an interface.
set fr-de
Changes the DE bit setting in the address field of a Frame Relay frame to 1 for all traffic leaving an interface.
match protocol (L2TPv3)
To configure protocol demultiplexing, use the match protocolcommand in xconnect configuration mode. To disable protocol demultiplexing, use the no form of this command.
Usage Guidelines
Protocol demultiplexing is supported only for Ethernet and terminated data-link connection identifier (DLCI) Frame Relay traffic in Cisco IOS Release 12.0(29)S and later releases.
Protocol demultiplexing requires supporting the combination of an IP address and an xconnectcommand configuration on the IPv4 provider edge (PE) interface. This combination of configurations is not allowed without enabling protocol demultiplexing, with the exception of switched Frame Relay permanent virtual circuits (PVCs). If no IP address is configured, the protocol demultiplexing configuration is rejected. If an IP address is configured, the xconnect command configuration is rejected unless protocol demultiplexing is enabled in xconnect configuration mode before exiting that mode. If an IP address is configured with an xconnect command configuration and protocol demultiplexing enabled, the IP address cannot be removed. To change or remove the configured IP address, the xconnect command configuration must first be disabled.
The table below shows the valid combinations of configurations.
match tcp
To match WAAS Express TCP traffic based on the IP address or port options, use the match tcp command in QoS class-map configuration mode. To remove the match, use the no form of this command.
match tcp { any | destination | source } { ip ip-address [ inverse mask ] | port start-port-number [end-port-number] }
match tcp { any | destination | source } { ip ip-address [ inverse mask ] | port start-port-number [end-port-number] }
Syntax Description
any
Matches based on any of TCP traffic.
destination
Matches the traffic based on the destination IP address or port number.
source
Matches the TCP traffic based on the source IP address or port number.
ip ip-address [inverse mask]
(Optional) Matches the TCP traffic based on the source or destination IP address and inverse mask.
port
Matches the TCP traffic based on the port number.
start-port-number
The starting port number.
end-port-number
(Optional) The ending port number.
Usage Guidelines
Use this command to match the TCP traffic based on the IP address or port number of the source or destination. If Network Address Translation (NAT) is used, the IP address refers to the inside local address and outside global address.
NoteThe class-map type of WAAS combines filters using the match-any logical operator. The match-all logical operator is not supported by the WAAS class map. This means that if one match criterion (filters) matches, the entire class map also matches.
Examples
The following example matches traffic having a destination TCP port number from 7000 to 7009:
Router(config)# class-map type waas waas_global Router(config-cmap)# match tcp destination port 7000 7009The following example matches traffic if the following conditions are matched:
- Destination IP address is in the range 209.165.200.225 and destination TCP port is 80.
- Destination IP address is in the range 209.165.200.225 and destination TCP port is 8080.
Router(config)# class-map type waas waas_global Router(config-cmap)# match tcp destination ip 209.165.200.225 0.0.0.31 port 80 80 Router(config-cmap)# match tcp destination ip 209.165.200.225 0.0.0.31 port 8080 8080max-lsp-lifetime (OTV)
To configure the maximum link-state packets (LSPs) lifetime, use the max-lsp-lifetime command in OTV IS-IS instance configuration mode. To return to the default setting, use the no form of this command.
metadatacache
To configure HTTP metadata caching, use the metadatacache command in WAAS HTTP configuration mode. To disable metadata caching, use the no form of this command.
metadatacache { filter-extension ext | max-age seconds | min-age seconds | { https | request-ignore-no-cache | response-ignore-no-cache | conditional-response | redirect-response | unauthorized-response } enable | enable }
no metadatacache { filter-extension ext | max-age seconds | min-age seconds | { https | request-ignore-no-cache | response-ignore-no-cache | conditional-response | redirect-response | unauthorized-response } enable | enable }
Syntax Description
filter-extension ext
Specifies file extensions, as a comma separated string, for which the metadata cache needs to be stored.
Filter extension is enabled by default. However, it is effective only after metadata caching is enabled. If no file extensions are configured, all file types are cached, which is the default state.
max-age seconds
Specifies the maximum time, in seconds, to retain cache entries in the metadata cache table.
Maximum age for metadata cache entries is enabled by default. However, it is effective only after metadata caching is enabled. The range is from 5 to 2592000. The default value is 86400.
min-age seconds
Specifies the minimum time, in seconds, to retain cache entries in the metadata cache table.
Minimum age for metadata cache entries is enabled by default. However, it is effective only after metadata caching is enabled. The range is from 5 to 86400. The default value is 60.
https
Enables HTTPS metadata caching. This keyword is enabled by default.
request-ignore-no-cache
Configures the metadata cache to ignore cache-control on requests. This keyword is disabled by default.
response-ignore-no-cache
Configures the metadata cache to ignore cache-control on response. This keyword is disabled by default.
conditional-response
Enables responses for the HTTP conditional requests feature. This keyword is enabled by default.
redirect-response
Enables the HTTP URL redirect feature. If this keyword is configured, the HTTP-Express accelerator responds with local HTTP 301 redirect messages. This keyword is enabled by default.
unauthorized-response
Enables the HTTP authentication-redirect feature. If this keyword is configured, the HTTP-Express accelerator responds with local HTTP 401 'authentication required' messages. This keyword is enabled by default.
enable
Enables HTTP metadata caching.
Usage Guidelines
Before you can enable the metadatacache command, use the following commands:
- Use the parameter-map type waas command in global configuration mode to enter parameter map configuration mode.
- Use the accelerator http-express command in parameter map configuration mode to enter WAAS HTTP configuration mode.
Use the metadatacache enable command to enable metadata caching for other metadata parameters to take effect.
Examples
The following example shows how to enable metadata caching and configure related parameters:
Device(config)# parameter-map type waas waas_global Device(config-profile)# accelerator http-express Device(config-waas-http)# enable Device(config-waas-http)# metadatacache enable Device(config-waas-http)# metadatacache max-age 10000 Device(config-waas-http)# metadatacache min-age 100 Device(config-waas-http)# metadatacache redirect-response enable Device(config-waas-http)# metadatacache conditional-response enable Device(config-waas-http)# metadatacache request-ignore-no-cache enableRelated Commands
Command
Description
accelerator
Enters a specific WAAS Express accelerator configuration mode based on the accelerator being configured.
parameter-map type waas
Configures WAAS Express global parameters.
show waas accelerator
Displays information about WAAS Express accelerators.
show waas cache http-express metadatacache
Displays WAAS Express HTTP metadata cache entries.
mls l2tpv3 reserve
To reserve a loopback interface to use as a source for the Layer 2 Tunnel Protocol version 3 (L2TPv3) tunnel for a specific line card and processor pair, use the mls l2tpv3 reserve command in interface configuration mode. To cancel the loopback interface reservation, use the no form of this command.
mls l2tpv3 reserve { slot slot-num | interface { TenGigabitEthernet slot_num/slot_unit | GigabitEthernet slot_num/slot_unit GigabitEthernet slot_num/slot_unit } }
no mls l2tpv3 reserve { slot slot-num | interface { TenGigabitEthernet slot_num/slot_unit | GigabitEthernet slot_num/slot_unit GigabitEthernet slot_num/slot_unit } }
Syntax Description
slot slot_num
Router slot number for a Cisco 7600 series SPA Interface Processor-400 (SIP-400) line card.
interface
Specifies that the interface is for a Cisco 7600 series ES Plus line card.
TenGigabitEthernet
Specifies a 2-Port 10 Gigabit Ethernet or a 4-Port 10 Gigabit Ethernet line card.
GigabitEthernet
Specifies 20-Port Gigabit Ethernet or 40-Port Gigabit Ethernet line cards.
slot_num/slot_unit
Slot number in which the line card is inserted and the slot unit (the line card port number).
When using two Gigabit Ethernet interfaces, the slot numbers of the two interfaces must match and can either be 1, 11, 21, or 31. The slot unit of the second Gigabit Ethernet interface must be ten plus the slot number of the first Gigabit Ethernet interface.
Usage Guidelines
This command also prevents the reserved loopback interface from being used across multiple line cards.
Examples
The following example reserves a loopback interface to use as a source for the L2TPv3 tunnel for a SIP-400 line card:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface Loopback1 Router(config-if)# mls l2tpv3 reserve slot 4 Router(config-if)# end Router# *Sep 11 04:03:26.770: %SYS-5-CONFIG_I: Configured from console by console Router# show running interface Loopback1 Building configuration... Current configuration : 69 bytes ! interface Loopback1 no ip address mls l2tpv3 reserve slot 4 endThe following example reserves a loopback interface to use as a source for the L2TPv3 tunnel for two 40-Port Gigabit Ethernet line cards:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface Loopback1 Router(config-if)# mls l2tpv3 reserve interface GigabitEthernet 3/11 GigabitEthernet 3/20 Router(config-if)# end Router# *Sep 10 10:46:01.671: %SYS-5-CONFIG_I: Configured from console by console Router# show running interface Loopback1 Building configuration... Current configuration : 112 bytes ! interface Loopback1 no ip address mls l2tpv3 reserve interface GigabitEthernet3/11 GigabitEthernet3/20 endThe following example reserves a loopback interface to use as a source for the L2TPv3 tunnel for a 2-Port 10 Gigabit Ethernet line card:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface Loopback2 Router(config-if)# mls l2tpv3 reserve interface TenGigabitEthernet 9/1 Router(config-if)# end Router# *Sep 10 10:49:31.451: %SYS-5-CONFIG_I: Configured from console by console Router# show running interface Loopback2 Building configuration... Current configuration : 112 bytes ! interface Loopback2 no ip address mls l2tpv3 reserve interface Tengigether 9/1 endmonitor l2tun counters tunnel l2tp
To enable or disable the collection of per-tunnel control message statistics for Layer 2 Tunnel Protocol (L2TP) tunnels, use the monitor l2tun counters tunnel l2tp command in privileged EXEC mode.
Syntax Description
Usage Guidelines
Use the monitor l2tun counters tunnel l2tpcommand to enable or disable the collection of per-tunnel control message statistics. Per-tunnel statistics must be enabled for each tunnel that you want to monitor.
Use the show l2tun counters tunnel l2tp id local-idcommand to display per-tunnel statistics for a specific tunnel. Use the show l2tun counters tunnel l2tp allcommand to display per-tunnel statistics for all tunnels that have per-tunnel statistics enabled.
Use the clear l2tun counters tunnel l2tp id local-idcommand to clear the per-tunnel statistics for a specific tunnel. Per-tunnel statistics are also cleared when the collection of per-tunnel statistics is disabled.
Examples
The following example enables the collection of per-tunnel control message statistics for the tunnel with the local tunnel ID 4230:
monitor l2tun counters tunnel l2tp id 4230 startThe following example disables the collection of per-tunnel control message statistics for the tunnel with the local tunnel ID 4230:
monitor l2tun counters tunnel l2tp id 4230 stopneighbor (L2VPN Pseudowire Switching)
To specify the routers that should form a point-to-point Layer 2 virtual forwarding interface (VFI) connection, use the neighbor command in L2 VFI point-to-point configuration mode. To disconnect the routers, use the no form of this command.
neighbor ip-address vc-id { encapsulation mpls | pw-class pw-class-name }
no neighbor ip-address vc-id { encapsulation mpls | pw-class pw-class-name }
Usage Guidelines
A maximum of two neighbor commands are allowed when you issue an l2 vfi point-to-pointcommand.
neighbor (VPLS)
To specify the type of tunnel signaling and encapsulation mechanism for each Virtual Private LAN Service (VPLS) peer, use the neighbor command in L2 VFI manual configuration mode. To disable a split horizon, use the no form of this command.
neighbor remote-router-id vc-id { encapsulation encapsulation-type | pw-class pw-name } [no-split-horizon]
no neighbor remote-router-id [vc-id]
Syntax Description
remote-router-id
Remote peer router identifier. The remote router ID can be any IP address, as long as it is reachable.
vc-id
32-bit identifier of the virtual circuit between the routers.
encapsulation
Specifies tunnel encapsulation.
encapsulation-type
Specifies the tunnel encapsulation type; valid values are l2tpv3 and mpls.
pw-class
Specifies the pseudowire class configuration from which the data encapsulation type is taken.
pw-name
Name of the pseudowire class.
no-split-horizon
(Optional) Disables the Layer 2 split horizon forwarding in the data path.
Command History
Release
Modification
12.2(18)SXF
This command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SRB
This command was modified. This command was updated so that the remote router ID need not be the LDP router ID of the peer.
Cisco IOS XE Release XE 3.7S
This command was integrated into Cisco IOS XE Release XE 3.7S.
Usage Guidelines
In a full-mesh VPLS network, keep split horizon enabled to avoid looping.
With the introduction of VPLS Autodiscovery, the remote router ID no longer needs to be the LDP router ID. The address that you specify can be any IP address on the peer, as long as it is reachable. When VPLS Autodiscovery discovers peer routers for the VPLS, the peer router addresses might be any routable address.
Examples
This example shows how to specify the tunnel encapsulation type:
Device(config-vfi)# l2 vfi vfi-1 manual Device(config-vfi)# vpn 1 Device(config-vfi)# neighbor 172.16.10.2 4 encapsulation mplsThis example shows how to disable the Layer 2 split horizon in the data path:
Device(config-vfi)# l2 vfi vfi-1 manual Device(config-vfi)# vpn 1 Device(config-vfi)# neighbor 172.16.10.2 4 encapsulation mpls no-split-horizonnsf (OTV)
To enable nonstop forwarding (NSF) operations for Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS), use the nsf command in OTV IS-IS instance configuration mode. To disable OTV IS-IS NSF and remove OTV IS-IS NSF configuration, use the no form of this command.
Command Default
NSF Cisco is enabled by default on a dual RP platform when an IS-IS overlay instance is created. The default NSF interval is 5 minutes.
oam-ac emulation-enable
To enable Operation, Administration, and Maintenance (OAM) cell emulation on ATM adaptation layer 5 (AAL5) over Multiprotocol Label Switching (MPLS) or Layer 2 Tunnel Protocol Version 3 (L2TPv3), use the oam-ac emulation-enable command in the appropriate configuration mode on both provider edge (PE) routers. To disable OAM cell emulation, use the no form of this command on both routers.
Command Modes
L2transport PVC configuration--for an ATM PVC
VC class configuration mode--for a VC classCommand History
Release
Modification
12.0(23)S
This command was introduced.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
12.0(30)S
This command was updated to enable OAM cell emulation as part of a virtual circuit (VC) class.
12.0(31)S
This command was integrated into Cisco IOS Release 12.0(31)S.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
15.0(1)S
This command was integrated into Cisco IOS Release 15.0(1)S.
Cisco IOS XE Release 3.1S
This command was integrated into Cisco IOS XE Release 3.1S.
Usage Guidelines
This command is used with AAL5 over MPLS or L2TPv3 and is not supported with ATM cell relay over MPLS or L2TPv3.
Examples
The following example shows how to enable OAM cell emulation on an ATM permanent virtual circuit (PVC):
Router# interface ATM 1/0/0 Router(config-if)# pvc ½00 l2transport Router(config-if-atm-l2trans-pvc)# oam-ac emulation-enableThe following example shows how to set the rate at which an AIS cell is sent every 30 seconds:
Router# interface ATM 1/0/0 Router(config-if)# pvc ½00 l2transport Router(config-if-atm-l2trans-pvc)# oam-ac emulation-enable 30The following example configures OAM cell emulation for ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to an interface.
Router> enable Router# configure terminal Router(config)# vc-class atm oamclass Router(config-vc-class)# encapsulation aal5 Router(config-vc-class)# oam-ac emulation-enable 30 Router(config-vc-class)# oam-pvc manage Router(config)# interface atm1/0 Router(config-if)# class-int oamclass Router(config-if)# pvc ½00 l2transport Router(config-if-atm-l2trans-pvc)# xconnect 10.13.13.13 100 encapsulation mplsoptimize tfo
To enable WAAS Express Transport Flow Optimization (TFO), use the optimize tfo command in QoS policy-map class configuration mode. To disable the WAAS Express TFO optimization, use the no form of this command.
optimize tfo [dre] [lz] application application-name [ accelerate { cifs-express | http-express } ]
no optimize tfo [dre] [lz] application application-name [ accelerate { cifs-express | http-express } ]
Syntax Description
dre
Enables Data Redundancy Elimination (DRE) and TFO.
lz
Enables Lempel-Ziv (LZ) and TFO.
application application-name
Specifies the class-map application name.
accelerate
(Optional) Enables the specified accelerator.
cifs-express
(Optional) Enables the Common Internet File System (CIFS)-Express accelerator.
http-express
(Optional) Enables the HTTP-Express accelerator.
Usage Guidelines
Use this command to apply optimizations for WAN traffic.
WAAS Express uses a variety of TFO features to optimize TCP traffic intercepted by WAAS devices. TFO protects communicating clients and servers from negative WAN conditions, such as bandwidth constraints, packet loss, congestion, and retransmission. In addition to TFO, WAAS Express provides acceleration benefits by supporting CIFS-Express, HTTP-Express, and Secure Sockets Layer (SSL)-Express accelerators.
WAAS Express uses the following optimization technologies based on the type of traffic it encounters:
- TFO—A collection of optimization technologies such as automatic windows scaling, increased buffering, and selective acknowledgment that optimize all TCP traffic over your network.
- DRE—A compression technology that reduces the size of transmitted data by removing redundant information before sending the shortened data stream over the WAN. DRE operates on significantly larger streams and maintains a much larger compression history than LZ compression.
- LZ—A compression technology that operates on smaller data streams and keeps limited compression history compared to DRE.
- Accelerator—A collection of individual accelerators for the following traffic types: CIFS, HTTP, and SSL.
NoteIf you do not use this command, pass-through optimization is applied on the WAN traffic.
You can also use the accelerator cifs-express command, the accelerator http-express command, and the accelerator ssl-express command in parameter map type configuration mode to enable CIFS-Express accelerator, HTTP-Express accelerator, and SSL-Express accelerator, respectively.
Examples
The following example shows how to enable TFO and LZ optimizations:
Device(config)# policy-map type waas_global Device(config-pmap)# class AFS Device(config-pmap-c)# optimize tfo lz application Filesystem Device(config-pmap-c)# exit Device(config-pmap)# exitThe following example shows how to enable TFO, DRE, and LZ optimizations on a Web application:
Device(config)# policy-map type waas_global Device(config-pmap)# class Http Device(config-pmap-c)# optimize tfo dre lz application Web Device(config-pmap-c)# exit Device(config-pmap)# exitThe following example shows how to enable TFO, DRE, and LZ optimizations on a Web application and also enable HTTP-Express accelerator:
Device(config)# policy-map type waas_global Device(config-pmap)# class Http Device(config-pmap-c)# optimize tfo dre lz application Web accelerate http-express Device(config-pmap-c)# exit Device(config-pmap)# exitRelated Commands
Command
Description
accelerator
Enters a specific WAAS Express accelerator configuration mode based on the accelerator being configured.
class
Associates a map class with a specified DLCI.
passthrough
Allows traffic without optimization.
policy-map type waas
Defines a WAAS Express policy map.
sequence-interval
Assigns sequential numbering to class maps.
otv active-source
To add a static active multicast source address for simulating a stream of multicast traffic emanating from an Overlay Transport Virtualization (OTV) site, use the otv active-source command in service instance configuration mode. To return to the default setting, use the no form of this command.
Usage Guidelines
This command preprovisions a mapping of the configured internal site multicast group to a multicast group in the core, even when no traffic is flowing for that multicast stream. Once the multicast traffic starts flowing, it will be sent over the overlay using the preprovisioned multicast mapping. As with all multicast mappings, a mapping is advertised by Intermediate System-to-Intermediate System (IS-IS) when the edge device is authoritative.
otv adjacency-server unicast-only
To configure a local edge device as an adjacency server in a unicast-core network, use the otv adjacency-server unicast-only command in interface configuration mode. To remove the adjacency server configuration from an edge device, use the no form of this command.
Usage Guidelines
To enable the OTV Adjacency Server feature, use the otv adjacency-server unicast-only command to configure an Overlay Transport Virtualization (OTV) edge device as a primary adjacency server and optionally configure another edge device as a secondary adjacency server as a backup. The remaining edge devices in the overlay network are configured to register to the primary and secondary adjacency servers by using the otv use-adjacency-server unicast-only command. Configure adjacency servers in a network where the provider core does not support multicast capability. The otv adjacency-server unicast-only command specifies that the device is not multicast-capable for the overlay network.
The configuration of multicast-core-specific commands and unicast-core-specific adjacency server commands is mutually exclusive. Therefore, if the otv control-group command or the otv data-group command is configured, the adjacency server commands are not allowed until the previous commands are disabled. Similarly, after an adjacency server command is configured, the otv control-group and otv data-group commands return errors until the adjacency server commands have been disabled.
Examples
The following example shows how to configure a local edge device as an adjacency server:
Device# configure terminal Device(config)# interface overlay 1 Device(config-if)# otv adjacency-server unicast-only Device(config-if)# endThe following example shows how to remove a local edge device from acting as an adjacency server:
Device# configure terminal Device(config)# interface overlay 1 Device(config-if)# no otv adjacency-server unicast-only Device(config-if)# endRelated Commands
Command
Description
otv control-group
Configures the IP multicast group address for the control and broadcast traffic for the specified OTV network. otv data-group
Configures one or more ranges of core provider multicast group prefixes for multicast data traffic for the specified OTV network.
otv use-adjacency-server unicast-only
Configures a local edge device to use a remote adjacency server in a unicast-core network.
show otv adjacency-server replication-list Displays the list of unicast destinations for which multicast traffic is replicated. otv control-group
To configure the IP multicast group address for the control and broadcast traffic for the specified Overlay Transport Virtualization (OTV) network, use the otv control-group command in interface configuration mode. To remove the multicast group address, use the no form of this command.
Usage Guidelines
Use the otv control-group command to configure the multicast group address for control traffic for the specified OTV overlay network and for customer broadcast traffic. Intermediate System-to-Intermediate System (IS-IS), broadcast, and other control packets sent toward the overlay are addressed to the specified multicast address to reach all other sites in the VPN.
Performing this command more than once on the same overlay interface will overwrite the existing addresses.
NoteThe OTV overlay interface cannot come up if you do not configure this command.
otv data-group
To configure one or more ranges of core provider multicast group prefixes for multicast data traffic for the specified Overlay Transport Virtualization (OTV) network, use the otv data-group command in interface configuration mode. To remove the multicast group address, use the no form of this command.Command Default
Range of multicast group prefixes for multicast data traffic for the specified OTV network
Usage Guidelines
Use the otv data-group command to configure a group of multicast addresses used to transmit multicast data across the overlay. Packets from the site that are destined to multicast addresses get mapped to one of these overlay multicast addresses. None of the data-group range addresses may overlap with addresses used by different overlays.
This command may be performed more than once for an overlay, in which case, the addresses will be added to the existing list of data-group addresses.
NoteThe OTV overlay interface cannot come up if you do not configure this command.
otv filter-fhrp
To enable filtering of First Hop Redundancy Protocol (FHRP) control packets, such as Hot Standby Router Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), and Gateway Load Balancing Protocol (GLBP), sent towards an Overlay Transport Virtualization (OTV) overlay network, use the otv filter-fhrp command in interface configuration mode. To disable the filtering of these packets, use the no form of this command.
Usage Guidelines
The HSRP/VRRP/GLBP packets being exchanged between routers in the same site are filtered from going over the overlay. This command enables filtering of FHRP control packets so that FHRP devices in different sites do not peer with each other. However, you can use the same virtual IP in multiple sites by performing additional configuration. Perform the following steps to use the same virtual IP in multiple sites:
- Enable the otv filter-fhrp command to filter HSRP/VRRP/GLBP protocol data units (PDUs).
- Create a Layer 2 access control list (L2ACL) to filter packets sourced from the FHRP device’s virtual MAC address.
- Apply the L2ACL to overlay Ethernet Flow Points (EFPs) in the out direction:
! HSRP L2ACL mac access-list extended filter_hsrp deny 0000.0c07.ac00 0000.0000.00ff any permit any any ! GLBP L2ACL mac access-list extended filter_glbp deny 0007.b400.0000 0000.00ff.ffff any permit any any ! VRRP L2ACL mac access-list extended filter_vrrp deny 0000.5e00.0100 0000.0000.00ff any permit any any interface Overlay1 service instance 120 ethernet encapsulation dot1q 120 mac access-group filter_hsrp out bridge-domain 120- Configure FHRP domains in different sites with different group numbers so that each site uses a unique virtual MAC address. Because the HSRP/VRRP/GLBP group number is included in the virtual MAC address, configuring a unique group in each site will ensure that the virtual MACs are also unique.
HSRP Usage: standby [group-number] ip [ip-address [secondary]] GLBP Usage: glbp group-number ip [ip-address [secondary]] VRRP Usage: vrrp group-number ip ip-addressotv fragmentation
To allow fragmentation of IP packets sent on an Overlay Transport Virtualization (OTV) overlay network using the specified join interface, use the otv fragmentation command in global configuration mode. To disable the fragmentation of IP packets, use the no form of this command.
Syntax Description
join-interface
Enables fragmentation of IP packets by using the specified join interface.
type
The type of interface to be configured.
number
Port, connector, or interface card number. The numbers are assigned at the factory at the time of installation or when added to a system; they can be displayed with the show interfaces command.
Usage Guidelines
The result of configuring the otv fragmentation command is that the Don’t Fragment (DF) bit in an IP header is set to zero. By default, all packets sent on an overlay are sent with the DF bit set to one.
This command should be used only if all edge devices in the overlay support reassembly in hardware.
otv isis authentication
To configure the Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) authentication on an overlay interface, use the otv isis authentication command in interface configuration mode or OTV site configuration mode. To remove the authentication, use the no form of this command.
otv isis authentication { key-chain key-chain-name | mode { md5 | text } | send-only }
no otv isis authentication { key-chain key-chain-name | mode { md5 | text } | send-only }
Syntax Description
key-chain
Configures the authentication key chain string.
keychain-name
Authentication key chain. The key-chain-name argument is case-sensitive and can be an alphanumeric string of up to 16 characters in length.
mode
Configures the authentication type.
md5
Specifies the message digest algorithm 5 (MD5) authentication method.
text
Specifies the cleartext authentication method.
send-only
Disables the authentication check on incoming hello protocol data units (PDUs) on an overlay interface and allows the sending of only authinfo.
Usage Guidelines
The otv isis authentication command is used to configure authentication for hello PDUs.
otv isis csnp-interval
To configure the interval in seconds between complete sequence number protocol data units (PDUs) (CSNPs) sent on the Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) interface, use the otv isis csnp-interval command in interface configuration mode. To return to the default setting, use the no form of this command.
Usage Guidelines
The otv isis csnp-interval command applies only for the designated router (DR) for a specified interface. The CSNP interval can be configured independently for Level 1. Configuring the CSNP interval does not apply to serial point-to-point interfaces.
otv isis hello-interval
To configure the interval between hello protocol data units (PDUs) sent on the Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) interface, use the otv isis hello-interval command in interface configuration mode or OTV site configuration mode. To return to the default setting, use the no form of this command.
otv isis hello-multiplier
To configure a multiplier used to calculate the interval within which hello protocol data units (PDUs) must be received on Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) instance to keep adjacency up, use the otv isis hello-multiplier command in interface configuration mode or OTV site configuration mode. To return to the default setting, use the no form of this command.
Usage Guidelines
Use the otv isis hello-multiplier command when hello packets are lost frequently and IS-IS adjacencies are failing. You can raise or lower the hello multiplier (otv isis hello-multiplier command) to make the hello protocol more reliable without increasing the time required to detect a link failure.
otv isis hello padding
To enable Overlay Transport Virtualization (OTV) Intermediate-System-to-Intermediate System (IS-IS) hello protocol data unit (PDU) padding, use the otv isis hello padding command in interface configuration mode or OTV site configuration mode. To disable IS-IS hello PDU padding, use the no form of this command.
Usage Guidelines
Padding adds extra characters to the hello packets so that all packets sent out by IS-IS have the maximum sized data payload.
IS-IS hello PDUs are padded to the full maximum transmission unit (MTU) size. Padding IS-IS hellos to the full MTU allows early detection of errors that may result either from transmission problems with large frames or from mismatched MTUs on adjacent interfaces.
You can disable hello padding to avoid wasting network bandwidth if the MTU of both interfaces is the same or for translational bridging. While hello padding is disabled, Cisco routers still send the first five IS-IS hellos padded to the full MTU size to maintain the benefits of discovering MTU mismatches.
otv isis lsp-interval
To configure the interval between Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) link-state packet (LSP) protocol data units (PDUs) sent on the interface during flooding, use the otv isis lsp-interval command in interface configuration mode. To return to the default setting, use the no form of this command.
otv isis metric
To configure the value of an Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) metric on an interface, use the otv isis metric command in interface configuration mode. To return to the default mteric value, use the no form of this command.
otv isis metric { metric | maximum } [ delay-metric | expense-metric | error-metric ]
no otv isis metric { metric | maximum } [ delay-metric | expense-metric | error-metric ]
Syntax Description
metric
Metric on the interface. The range is from 1 to 16777214.
maximum
Specifies the maximum metric value.
delay-metric
(Optional) Delay metric on the interface. The range is from 1 to 16777214.
expense-metric
(Optional) Expense metric on the interface. The range is from 1 to 16777214.
error-metric
(Optional) Error metric on the interface. The range is from 1 to 16777214.
otv isis overlay
To create an Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) instance, use the otv isis overlay command in global configuration mode. To return the OTV IS-IS instance to its default configuration, use the no form of this command.
Usage Guidelines
You can also create an overlay instance by using the interface overlay command. An IS-IS overlay instance is automatically created when you use either the interface overlay command or the otv isis overlay command.
The no otv isis overlay command does not remove the IS-IS overlay instance; it only returns the IS-IS overlay instance to its default configuration. The no interface overlay command removes the IS-IS overlay instance.
Use the otv isis overlay command to enter OTV IS-IS instance configuration mode.
otv isis priority
To configure the Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) priority for a Designated Intermediate System (DIS) election on the interface, use the otv isis priority command in interface configuration mode or OTV site configuration mode. To return to the default setting, use the no form of this command.
otv isis retransmit-interval
To configure the time interval between retransmission of each Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) link-state packet (LSP) on the interface, use the otv isis retransmit-interval command in interface configuration mode. To return to the default setting, use the no form of this command.
otv isis retransmit-throttle-interval
To configure the link-state packet (LSP) retransmission interval, use the otv isis retransmit-throttle-interval command in interface configuration mode. To remove the configuration, use the no form of this command.
otv isis site
To create an Overlay Transport Virtualization (OTV) Intermediate System-to-Intermediate System (IS-IS) site instance, use the otv isis site command in global configuration mode. To return the OTV IS-IS site instance to its default configuration, use the no form of this command.
Usage Guidelines
An IS-IS site instance is created automatically when one of the following configurations happen:
- An IS-IS overlay instance is created. You can create an overlay instance by using the interface overlay command or the otv isis overlay command.
- The otv site-identifier command is configured.
- The otv isis site command is configured.
An IS-IS site instance will be removed in the following scenarios:
- When there is no IS-IS overlay instance or site identifier, the no otv isis site command will remove the IS-IS site instance, irrespective of whether there is a site instance with default configuration. If there is at least one IS-IS overlay instance or a site identifier configured, the no otv isis site command will not remove the IS-IS site instance; instead, the command will return the IS-IS site instance to its default configuration.
The IS-IS site instance does not generate Link State Packets (LSPs) or run Shortest Path First (SPF) computations.
otv join-interface
To associate an Overlay Transport Virtualization (OTV) overlay interface to an external interface, use the otv join-interface command in interface configuration mode. To remove that interface from the overlay interface, use the no form of this command.
Usage Guidelines
This command configures the interface over which an overlay is formed. The IP of the specified interface is used as the source address of packets sourced from the edge device. Therefore, you must ensure that the IP address on the physical interface is configured. You can specify only one join interface per overlay.
NoteThe OTV overlay interface cannot come up if you do not configure this command.
NoteThe join interface must belong to the default VPN routing and forwarding (VRF) instance.
otv mac flood
To flood the specified destination MAC address to all other edge devices in the Overlay Transport Virtualization (OTV) overlay network and to all unblocked local ports in the bridge domain, use the otv mac flood command in service instance configuration mode. To disable the flooding of the specified MAC address, use the no form of this command.
Usage Guidelines
This command supports unidirectional MAC forwarding used by technologies such as Microsoft Network Load Balancing (NLB). The specified MAC is not advertised by Intermediate System-to-Intermediate System (IS-IS).
Examples
The following example shows how to flood the specified MAC address to all edge devices in the overlay and to all unblocked local ports in the bridge domain:
Router# configure terminal Router(config)# interface overlay 1 Router(config-if)# service instance 10 ethernet Router(config-if-srv)# otv mac flood 0005.9A3C.7810 Router(config-if-srv)# endotv site bridge-domain
To configure a bridge domain for sending Intermediate System-to-Intermediate System (IS-IS) hellos over site interfaces, use the otv site bridge-domain command in global configuration mode. To remove the bridge domain configuration, use the no form of this command.
Usage Guidelines
The same site bridge domain is used for all configured overlays. Interfaces facing the site network must be configured with this bridge domain for IS-IS hellos to reach other edge devices in the same site network. This command may be configured even if the specified bridge domain does not yet exist. IS-IS site hellos will not be sent until the specified bridge domain has been configured on one or more access port service instances.
This command needs to be configured before an edge device can become an authoritative edge device (AED).
otv site-identifier
To configure a site identifier for an Overlay Transport Virtualization (OTV) site, use the otv site-identifier command in global configuration mode. To remove the site-identifier configuration, use the no form of this command.
Usage Guidelines
All edge devices connected to the same site must have the same site identifier configured. The otv site-identifier command needs to be configured before an edge device can become an authoritative edge device (AED).
otv suppress arp-nd
To suppress sending IPv4 Address Resolution Protocol (ARP) requests over an overlay network, use the otv suppress-arp-nd command in interface configuration mode. To allow sending ARP requests over the overlay network, use the no form of this command.
Usage Guidelines
When sending of ARP requests is suppressed, this command performs caching of Layer 3-to-Layer 2 address mappings by snooping on ARP packets. Broadcast ARP requests received from the site for which a cache entry exists are then responded to by edge devices on the behalf of remote hosts. Because the edge devices respond to ARP requests, the number of broadcast and multicast packets sent on the overlay is significantly reduced.
otv use-adjacency-server unicast-only
To configure a local edge device to use a remote adjacency server in a unicast-core network, use the otv use-adjacency-server unicast-only command in interface configuration mode. To return to the default settings on the edge device, use the no form of this command.otv use-adjacency-server primary-address [ secondary-address ] unicast-only
no otv use-adjacency-server primary-address [ secondary-address ] unicast-only
Syntax Description
primary-address
IP address of the remote adjacency server. The IP address format must be in dotted decimal notation.
secondary-address
(Optional) IP address of the backup adjacency server. The IP address format must be in dotted decimal notation. This address is available only if a backup adjacency server has been configured.
Command Default
An edge device is not configured to use an adjacency server and is assumed to be multicast-capable.
Usage Guidelines
The primary and secondary IP addresses specified in the otv use-adjacency-server unicast-only command must match the IP addresses of previously configured adjacency servers. The otv use-adjacency-server unicast-only command specifies that the device is not multicast-capable for the overlay network.
otv vpn-name
To configure the name of the specified Overlay Transport Virtualization (OTV) VPN, use the otv vpn-name command in interface configuration mode. To return to the default setting, use the no form of this command.
Usage Guidelines
The OTV VPN name configured using this command is used as an alias to the overlay interface name in various OTV show commands. The VPN name for the specified overlay is locally significant only on the device. You must have different names for different overlay interfaces on the same device.
packet drop during-authorization
To specify that packets received from the user during authorization will be dropped, use the packet drop during-authorizationcommand in transparent auto-logon configuration mode. To remove the configuration, use the no form of this command.
Command Default
Packet drop during authorization is disabled, and packets from the authorizing user are forwarded.
Usage Guidelines
Use this command for configuring data traffic packet drop for users that are waiting for authorization (WA).
parameter-map type waas
To configure WAAS Express global parameters, use the parameter-map type waas command in global configuration mode. To remove global parameters, use the no form of this command.
Usage Guidelines
This command extends the parameter-map type command and enters parameter-map configuration mode. The parameter map type of WAAS can be deleted only if WAAS Express is not enabled on any interface.
Examples
The following example shows how to configure global parameters for WAAS Express:
Router> enable Router# configure terminal Router(config)# parameter-map type waas waas_globalRelated Commands
Command
Description
class-map type waas
Configures a WAAS Express class map.
cpu-threshold
Sets the CPU threshold limit.
lz entropy-check
Enables entropy checking to turn on LZ compression.
parameter-map type
Creates or modifies a parameter map.
policy-map type waas
Configures WAAS Express policy map.
tfo auto-discovery blacklist
Configures a blacklist with autodiscovery for WAAS Express.
tfo optimize
Configures compression for WAAS Express.
waas config
Restores or removes WAAS Express default configurations.
passthrough
To pass through match traffic and not apply the WAN optimization, use the passthrough command in QoS policy-map class configuration mode. To remove the default optimization, use the no form of this command.
Usage Guidelines
Use this command if you do not want to specify any optimizations such as Transport Flow Optimization (TFO), Data Redundancy Elimination (DRE), and Lempel-Ziv (LZ) for WAN traffic.
Examples
The following example shows how to specify pass-through optimization for Instant-Messaging:
Router(config)# policy-map type waas waas_global Router(config-pmap)# sequence-interval 111 Router(config-pmap-c)# optimize tfo dre lz application File-System Router(config-pmap-c)# passthrough application Instant-Messaging Router(config-pmap-c)# exitpassword
To configure the password used by a provider edge (PE) router for Challenge Handshake Authentication Protocol (CHAP) style Layer 2 Tunnel Protocol Version 3 (L2TPv3) authentication, use the passwordcommand in L2TP class configuration mode. To disable a configured password, use the no form of this command.
Command Default
If a password is not configured for the L2TP class with the password command, the password configured with the username password command in global configuration mode is used. The default input format of the shared secret is 0.
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
15.2(02)SA This command was implemented on the Cisco ME 2600X Series Ethernet Access Switches. Usage Guidelines
The password hierarchy sequence used for a local and remote peer PE for L2TPv3 authentication is as follows:
- The L2TPv3 password (configured with the password command) is used first.
- If no L2TPv3 password exists, the globally configured password (configured with the username password command) for the router is used.
NoteThe use of a special character such as '\'(backslash) and a three or more digit number for the character setting like password, results in incorrect translation.
Examples
The following example sets the password named tunnel2 to be used to authenticate an L2TPv3 session between the local and remote peers in L2TPv3 pseudowires configured with the L2TP class configuration named l2tp class1:
Router(config) # l2tp-class l2tp-class1 Router(config-l2tp-class) # authentication Router(config-l2tp-class) # password tunnel2password (L2TP)
To configure the password used by a provider edge (PE) router for Layer 2 authentication, use the passwordcommand in L2TP class configuration mode. To disable a configured password, use the no form of this command.
Syntax Description
encryption-type
(Optional) Specifies the type of encryption to use. The valid values are from 0 to 7. Currently defined encryption types are 0 (no encryption) and 7 (text is encrypted using an algorithm defined by Cisco). The default encryption type is 0.
password
Specifies the password used for L2TPv3 authentication.
Command Default
If a password is not configured for the L2TP class with the password command, the password configured with the usernamecommand in global configuration mode is used.
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
Usage Guidelines
The password that you define with the password command is also used for attribute-value pair (AVP) hiding.
The password hierarchy sequence used for a local and remote peer PE for L2TPv3 authentication is as follows:
- The L2TPv3 password (configured with the password command) is used first.
- If no L2TPv3 password exists, the globally configured password (configured with the username passwordcommand) for the router is used.
Examples
The following example sets the password named “tunnel2” to be used to authenticate an L2TPv3 session between the local and remote peers in L2TPv3 pseudowires that has been configured with the L2TP class configuration named “l2tp-class1”:
Router(config) # l2tp-class l2tp-class1 Router(config-l2tp-class) # authentication Router(config-l2tp-class) # password tunnel2peer-cert-verify enable
To enable the verification of the peer certificate, use the peer-cert-verify enable command in SSL peering service configuration mode. To disable the verification of the peer certificate, use the no form of this command.
Usage Guidelines
SSL peering service configuration parameters control secure communications established by the SSL accelerator between WAAS devices while optimizing SSL connections. If peer certificate verification is enabled, WAAS Express devices that use self-signed certificates will not be able to establish peering connections to each other and, therefore, will not be able to accelerate SSL traffic.
Before you can enable the peer-cert-verify enable command, use the following commands:
- Use the parameter-map type waas command in global configuration mode to enter parameter map configuration mode.
- Use the accelerator ssl-express command in parameter map configuration mode to enter WAAS SSL configuration mode.
- Use the services host-service peering command in WAAS SSL configuration mode to enter SSL peering service configuration mode.
Examples
The following example shows how to enable the verification of the peer certificate:
Device(config)# parameter-map type waas waas_global Device(config-profile)# accelerator ssl-express Device(config-waas-ssl)# enable Device(config-waas-ssl)# services host-service peering Device(config-waas-ssl-peering)# peer-cert-verify enableRelated Commands
Command
Description
accelerator
Enters a specific WAAS Express accelerator configuration mode based on the accelerator being configured.
parameter-map type waas
Configures WAAS Express global parameters.
peer-cipherlist
Creates a cipher list to be used for WAN-to-WAN sessions.
peer-ssl-version
Configures the SSL version to be used for WAAS-to-WAAS sessions.
services host-service peering
Configures the SSL-Express accelerator host peering service.
show waas accelerator
Displays information about WAAS Express accelerators.
show waas statistics accelerator
Displays statistical information about WAAS Express accelerators.
peer-cipherlist
To create a cipher list to be used for WAN-to-WAN sessions, use the peer-cipherlist command in SSL peering service configuration mode. To disable the use of a cipher list, use the no form of this command.
Usage Guidelines
A cipher list is customer list of cipher suites that you assign to an SSL connection.
Before you can enable the peer-cipherlist command, use the following commands:
- Use the parameter-map type waas command in global configuration mode to enter parameter map configuration mode.
- Use the accelerator ssl-express command in parameter map configuration mode to enter WAAS SSL configuration mode.
- Use the services host-service peering command in WAAS SSL configuration mode to enter SSL peering service configuration mode.
Examples
The following example shows how to create a cipher list for WAN-to-WAN sessions:
Device(config)# parameter-map type waas waas_global Device(config-profile)# accelerator ssl-express Device(config-waas-ssl)# enable Device(config-waas-ssl)# services host-service peering Device(config-waas-ssl-peering)# peer-cipherlist c-listRelated Commands
Command
Description
accelerator
Enters a specific WAAS Express accelerator configuration mode based on the accelerator being configured.
parameter-map type waas
Configures WAAS Express global parameters.
peer-cert-verify enable
Enables the verification of the peer certificate.
peer-ssl-version
Configures the SSL version to be used for WAAS-to-WAAS sessions.
services host-service peering
Configures the SSL-Express accelerator host peering service.
show waas accelerator
Displays information about WAAS Express accelerators.
show waas statistics accelerator
Displays statistical information about WAAS Express accelerators.
peer-ssl-version
To configure the Secure Sockets Layer (SSL) version to be used for Wide-Area Application Services (WAAS)-to-WAAS sessions, use the peer-ssl-version command in SSL peering service configuration mode. To toggle to the other SSL version value, use the no form of this command.
Usage Guidelines
Before you can enable the peer-ssl-version command, use the following commands:
- Use the parameter-map type waas command in global configuration mode to enter parameter map configuration mode.
- Use the accelerator ssl-express command in parameter map configuration mode to enter WAAS SSL configuration mode.
- Use the services host-service peering command in WAAS SSL configuration mode to enter SSL peering service configuration mode.
Examples
The following example shows how to configure SSL Version 3.0 to be used for WAAS-to-WAAS sessions:
Device(config)# parameter-map type waas waas_global Device(config-profile)# accelerator ssl-express Device(config-waas-ssl)# enable Device(config-waas-ssl)# services host-service peering Device(config-waas-ssl-peering)# peer-ssl-version ssl3Related Commands
Command
Description
accelerator
Enters a specific WAAS Express accelerator configuration mode based on the accelerator being configured.
parameter-map type waas
Configures WAAS Express global parameters.
peer-cert-verify enable
Enables the verification of the peer certificate.
peer-cipherlist
Creates a cipher list to be used for WAAS-to-WAAS sessions.
services host-service peering
Configures the SSL-Express accelerator host peering service.
show waas accelerator
Displays information about WAAS Express accelerators.
show waas statistics accelerator
Displays statistical information about WAAS Express accelerators.
policy-map type mace
To configure a Measurement, Aggregation, and Correlation Engine (MACE) policy map and enter policy map configuration mode, use the policy-map type mace command in global configuration mode. To remove a MACE policy map, use the no form of this command.
Usage Guidelines
Use the policy-map type mace command to classify session traffic and run MACE on that traffic. Two types of class maps are supported in a MACE policy map:
- A quality of service (QoS) class map (default type class map)
- A Wide Area Application Services (WAAS) class map
The usage of QoS and WAAS class maps in the MACE policy is independent of QoS or WAAS policies being configured on the routers.
Inside a MACE policy map, you can configure a flow monitor name using only the flow monitorcommand. The name of the flow monitor is used to collect the corresponding flow metrics and to export these flow metrics when the cache timeout is updated.
NoteOnly one flow monitor can be configured in a class map.
Examples
The following example shows how to configure the MACE policy map, mace_global:
Router(config)# policy-map type mace mace_global Router(config-pmap)# class class1 Router(config-pmap-c)# flow monitor name my-flow-monitorRelated Commands
Command
Description
class (policy-map)
Specifies the name of the class whose policy you want to create or change or specifies the default class (commonly known as the class-default class) before you configure its policy.
flow monitor
Creates or modifies a Flexible NetFlow flow monitor.
policy-map
Enters policy-map configuration mode, and creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.
policy-map type waas
To configure a WAAS Express policy map, use the policy-map type waas command in global configuration mode. To remove a WAAS Express policy-map, use the no form of this command.
Usage Guidelines
This command extends the policy-mapcommand and enters QoS policy-map configuration mode. The policy-map type of WAAS can be deleted only if WAAS Express is not enabled on any interface.
Examples
The following example shows how to configure a WAAS Express policy map:
Router> enable Router# configure terminal Router(config)# policy-map type waas waas_global Router(config-pmap)# class waas_globalRelated Commands
Command
Description
class
Associates a map class with a specified DLCI.
optimize
Applies optimization to WAN network traffic.
parameter-map type waas
Configures WAAS Express global parameters.
passthrough
Sends the network traffic without applying any optimization.
policy-map
Creates or modifies a policy map.
sequence-interval
Assigns sequential numbering to class maps.
waas config
Restores or removes WAAS Express default configurations.
platform trace runtime process forwarding-manager module mfr
To enable Forwarding Manager Route Processor and Embedded Service Processor trace messages for the multilink frame relay, use the platform trace runtime process forwarding-manager module mfrcommand in the global configuration mode. To disable the Forwarding Manager Route Processor and Embedded Service Processor debug messages, use the no form of this command.
platform trace runtime slot slot bay bay process forwarding-manager module mfr level level
no platform trace runtime slot slot bay bay process forwarding-manager module mfr level level
Syntax Description
slot
Shared Port Adapter (SPA) Interprocessor, Embedded Service Processor, or Route Processor slot.
Valid options are:
- F0—Embedded Service Processor slot 0
- R0—Route Processor slot 0
- F1—Embedded Service Processor slot 1
- R1—Route Processor slot 1
bay
Chassis bay to be configured.
Valid options are:
- 0
- 1
level level
Selects the trace level. The trace level determines the amount of information that should be stored about a module in the trace buffer or file.
Valid options are:
- debug —Provides debug-level output.
- emergency —Provides information about an issue that makes the system unusable.
- error —Provides information about a system error.
- info —Provides informational messages.
- noise —Provides all possible trace messages pertaining to the module. The noise level is always equal to the highest possible tracing level.
- notice —Provides information regarding a significant issue, that does not, however, affect the normal functioning of the router.
- verbose —Provides all possible tracing messages.
- warning —Provides information about a system warning.
Command Default
The default tracing level for every module on the Cisco ASR 1000 Series Routers is notice.
Usage Guidelines
Trace-level settings are leveled, that is, every setting contains all the messages from the lower setting plus the messages from its own setting. For instance, setting the trace level to 3 (error) ensures that the trace file contains all the output for the 0 (emergencies), 1 (alerts), 2 (critical), and 3 (error) settings. Setting the trace level to 4 (warning) ensures that all the trace output for a specific module is included in that trace file.
All trace levels cannot be configured by users. Specifically, the alert, critical, and notice tracing levels cannot be set by users. To trace these messages, set the trace level to a higher level, which collects these messages.
When setting the trace levels, it is also important to remember that the setting is not done in a configuration mode. As a result of this, trace level settings are returned to their defaults after every router reload.
Caution
Setting the tracing of a module to the debug level or higher can have a negative performance impact. Setting the tracing to the debug level or higher should be done with discretion.
Caution
Setting a large number of modules to high tracing levels can severely degrade performance. If a high level of tracing is needed in a specific context, it is almost always preferable to set a single module on a higher tracing level rather than setting multiple modules to high tracing levels.
Examples
In the following example, the trace level of the Forwarding Processor in the Forwarding Manager of the ESP processor in slot 0 is set to the informational tracing level (info):
Router(config)# platform trace runtime slot F0 bay 0 process forwarding-manager module mfr level infoIn the following example, the trace level for the Route Processor in the Forwarding Manager of the ESP processor in slot 0 is set to the informational tracing level (info):
Router(config)# platform trace runtime slot r0 bay 0 process forwarding-manager module mfr level infoprc-interval (OTV)
To configure the minimum interval between Partial Route Calculations (PRC), use the prc-interval command in OTV IS-IS instance configuration mode. To remove the configuration for the PRC interval, use the no form of this command.
Command Default
Layer 2 is configured, by default, with PRC generation intervals of 5 seconds, 50 milliseconds, and 200 milliseconds for the prc-max-wait, prc-initial-wait, and prc-second-wait arguments, respectively.
precedence (Frame Relay VC-bundle-member)
To configure the precedence levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the precedence command in Frame Relay VC-bundle-member configuration mode. To remove the precedence level configuration from a PVC, use the no form of this command.
Syntax Description
level
The precedence level or levels for the Frame Relay PVC bundle member. The range is from 0 to 7:
- 0--routine
- 1--priority
- 2--immediate
- 3--flash
- 4--flash override
- 5--critical
- 6--internetwork control
- 7--network control
A PVC bundle member can be configured with a single precedence level, multiple individual precedence levels, a range of precedence levels, multiple ranges of precedence levels, or a combination of individual precedence levels and ranges. Examples are as follows:
- 0
- 0,2,3
- 0-2,4-5
- 0,1,2-4,7
other
Specifies that this Frame Relay PVC bundle member will handle all of the remaining precedence levels that are not explicitly configured on any other bundle member PVCs.
Usage Guidelines
Assignment of precedence levels to PVC bundle members lets you create differentiated services, because you can distribute the IP precedence levels over the various PVC bundle members. You can map a single precedence level or a range of levels to each discrete PVC in the bundle, which enables PVCs in the bundle to carry packets marked with different precedence levels.
Use the precedence other command to indicate that a PVC can carry traffic marked with precedence levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the precedence other command.
This command is available only when the match type for the PVC bundle is set to precedence by using the match precedence command in Frame Relay VC-bundle configuration mode.
You can overwrite the precedence level configuration on a PVC by reentering the precedence command with a new level value.
All precedence levels must be accounted for in the PVC bundle configuration, or the bundle will not come up. However, a PVC can be a bundle member without a precedence level associated with it. As long as all valid precedence levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no precedence level configured will not participate in it.
A precedence level can be configured on one PVC bundle member per bundle. If you configure the same precedence level on more than one PVC within a bundle, the following error appears on the console:
%Overlapping precedence levelsWhen you use the mpls ip command to enable multiprotocol label switching (MPLS) on the interface, MPLS and IP packets can flow across the interface, and PVC bundles that are configured for IP precedence mapping are converted to MPLS EXP mapping. The PVC bundle functionality remains the same with respect to priority levels, bumping, and so on, but the match precedence command is replaced by the match exp command, and each precedencecommand is replaced by the exp command. The result is that a bundle-member PVC previously configured to carry precedence level 1 IP traffic now carries EXP level 1 MPLS traffic.
When MPLS is disabled, the match precedence and match dscp commands are restored, and the exp commands are replaced by precedence commands.
When MPLS is enabled or disabled, PVC bundles configured for IP precedence mapping or MPLS EXP mapping will stay up, and traffic will be transmitted over the appropriate bundle-member PVCs.
Examples
The following example shows how to configure Frame Relay PVC bundle member 101 to carry traffic with IP precedence level 5:
frame-relay vc-bundle bundle1 match precedence pvc 101 precedence 5Related Commands
Command
Description
bump
Configures the bumping rules for a specific PVC member of a bundle.
class
Associates a map class with a specified DLCI.
dscp (Frame Relay VC-bundle-member)
Configures the DSCP value or values for a Frame Relay PVC bundle member.
exp
Configures MPLS EXP levels for a Frame Relay PVC bundle member.
match
Specifies which bits of the IP header to use for mapping packet service levels to Frame Relay PVC bundle members.
match dscp
Configures a specific IP differentiated service code point (DSCP) value as a match criterion.
match precedence
Configures IP precedence values as match criteria.
protect (Frame Relay VC-bundle-member)
Configures a Frame Relay PVC bundle member with protected group or protected PVC status.
protect (Frame Relay VC-bundle-member)
Toconfigure a Frame Relay permanent virtual circuit (PVC) bundle member with protected group or protected PVC status, use the protect command in Frame Relay VC-bundle-member configuration mode. To remove the protected status from a PVC, use the noform of this command.
Usage Guidelines
When an individually-protected PVC goes down, it takes the bundle down. When all members of a protected group go down, the bundle goes down.
Despite any protection configurations, the PVC bundle will go down if a downed PVC has no PVC to which to bump its traffic or if the last PVC that is up in a PVC bundle goes down.
Examples
The following example configures Frame Relay PVC bundle member 101 as an individually protected PVC:
frame-relay vc-bundle new york pvc 101 protect vcRelated Commands
Command
Description
bump
Configures the bumping rules for a specific PVC member of a bundle.
bundle
Creates a bundle or modifies an existing bundle to enter bundle configuration mode.
dscp (Frame Relay VC-bundle-member)
Configures the DSCP value or values for a Frame Relay PVC bundle member.
exp
Configures MPLS EXP levels for a Frame Relay PVC bundle member.
precedence (Frame Relay VC-bundle-member)
Configures the precedence levels for a Frame Relay PVC bundle member.
protocol (L2TP)
To specify the signaling protocol to be used to manage the pseudowires created from a pseudowire class for a Layer 2 session and to cause control plane configuration settings to be taken from a specified L2TP class, use the protocolcommand in pseudowire class configuration mode. To remove the signaling protocol (and the control plane configuration to be used) from a pseudowire class, use the no form of this command.
protocol { l2tpv2 | l2tpv3 | none } [l2tp-class-name]
no protocol { l2tpv2 | l2tpv3 | none } [l2tp-class-name]
Syntax Description
l2tpv2
Specifies that the Layer 2 Tunnel Protocol (L2TP) signaling protocol will be used.
l2tpv3
Specifies that the L2TPv3 signaling protocol will be used. This is the default.
none
Specifies that no signaling protocol will be used in L2TPv3 sessions.
l2tp-class-name
(Optional) The name of the L2TP class whose control plane configuration is to be used for pseudowires set up from a specified pseudowire class. If you do not enter a value for the l2tp-class-nameargument, the default control plane configuration settings in the L2TP signaling protocol are used.
Usage Guidelines
Use the protocol(L2TP) command to configure the signaling protocol to use in sessions created from the specified pseudowire class. In addition, you can use this command to specify the L2TP class (see the “Configuring the Xconnect Attachment Circuit” section in the Layer 2 Tunnel Protocol Version 3 feature document) from which the control plane configuration settings are to be taken.
Use the protocol nonecommand to specify that no signaling will be used in L2TPv3 sessions created from the specified pseudowire class. This configuration is required for interoperability with a remote peer running the Universal Tunnel Interface (UTI).
Do not use this command if you want to configure a pseudowire class that will be used to create manual L2TPv3 sessions (see the “Static L2TPv3 Sessions” section in the Layer 2 Tunnel Protocol Version 3 feature document).
Examples
The following example shows how to enter pseudowire class configuration mode and how to configure L2TPv3 as the signaling protocol. The control plane configuration used in the L2TP class named “class1” will be used to create dynamic L2TPv3 sessions for a VLAN xconnect interface.
Router(config) # pseudowire-class vlan-xconnect Router(config-pw) # protocol l2tpv3 class1pseudowire
To bind a virtual circuit to a Layer 2 pseudowire for an xconnect service, use the pseudowire command in interface configuration mode. To remove the binding between a virtual circuit and a Layer 2 pseudowire, use the no form of this command.
pseudowire peer-ip-address vcid pw-class pw-class-name [ sequencing { transmit | receive | both } ]
no pseudowire
Syntax Description
peer-ip-address
IP address of the remote peer.
vcid
32-bit identifier of the virtual circuit between devices at each end of a Layer 2 control channel.
pw-class pw-class-name
Specifies the pseudowire class configuration from which the data encapsulation type is derived.
sequencing
(Optional) Configures sequencing options for xconnect.
transmit
(Optional) Transmits sequence numbers.
receive
(Optional) Receives sequence numbers.
both
(Optional) Transmits and receives sequence numbers.
Command History
Release
Modification
12.3(2)T
This command was introduced.
15.0(1)S
This command was integrated into Cisco IOS Release 15.0(1)S.
15.2(4)S
This command was modified. The behavior of the no form of this command was modified. A configured pseudowire must be disabled before disabling a virtual-ppp interface.
Usage Guidelines
The combination of the peer-ip-address and vcid arguments must be unique on a device.
The same vcid value that identifies a virtual circuit must be configured by using the pseudowire command on local and remote devices at each end of a Layer 2 session. The virtual circuit identifier creates a binding between a pseudowire and a virtual circuit.
The pw-class pw-class-name binds the pseudowire configuration of a virtual circuit to a specific pseudowire class. The pseudowire class configuration serves as a template that contains settings used by all virtual circuits bound to it by using the pseudowire command.
When removing a virtual-PPP interface that has a configured pseudowire, you must first remove the pseudowire by using the no pseudowire command.
Examples
The following example shows how to create a virtual-PPP interface, configure PPP on the virtual-PPP interface, and bind a virtual circuit to a Layer 2 pseudowire for an xconnect service for a pseudowire class named pwclass1:
interface virtual-ppp 1 ppp authentication chap ppp chap hostname peer1 pseudowire 172.24.13.196 10 pw-class pwclass1The following example shows how to remove a virtual-PPP interface that has a configured pseudowire. You must first remove the configured pseudowire or an error is generated. Note that you can remove the virtual-PPP interface in interface configuration mode as shown below:
no interface virtual-ppp 1 % Interface Virtual-PPP1 not removed - Remove the Pseudowire interface virtual-ppp 1 no pseudowire no interface virtual-ppp 1 endRelated Commands
Command
Description
interface virtual-ppp
Configures a virtual-PPP interface.
l2tp-class
Creates a template of L2TP control plane configuration settings that can be inherited by different pseudowire classes and enters L2TP class configuration mode.
ppp authentication
Enables at least one PPP authentication protocol and specifies the order in which protocols are selected on the interface.
ppp chap hostname
Creates a pool of dialup routers that all appear to be the same host when authenticating with CHAP.
pseudowire-class
Specifies the name of a Layer 2 pseudowire class and enters pseudowire class configuration mode.
pseudowire-class
To specify the name of a Layer 2 pseudowire class and enter pseudowire class configuration mode, use the pseudowire-class command in global configuration mode. To remove a pseudowire class configuration, use the no form of this command.
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
Cisco IOS XE Release 3.4S
This command was integrated into Cisco IOS XE Release 3.4S.
15.3(2)S
This command was implemented on the Cisco ASR 901 Series Aggregation Services Routers.
Command History
Usage Guidelines
The pseudowire-class command allows you to configure 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:
- Data encapsulation type
- Control protocol
- Sequencing
- IP address of the local Layer 2 interface
- Type of service (ToS) value in IP headers
The local interface name for each pseudowire class configured between a pair of PE routers can be the same or different.
After you enter the pseudowire-class command, the router switches to pseudowire class configuration mode, where pseudowire settings may be configured.
Examples
The following example shows how to enter pseudowire class configuration mode to configure a pseudowire configuration template named “ether-pw”:
Router(config) # pseudowire-class ether-pw Router(config-pw)#The following example shows how to enter pseudowire class configuration mode to configure a pseudowire configuration template named “mpls-ip”:
Router(config) # pseudowire-class mpls-ipRelated Commands
Command
Description
l2tp-class
Creates a template of L2TP control plane configuration settings that can be inherited by different pseudowire classes and enters L2TP class configuration mode.
pseudowire
Binds an attachment circuit to a Layer 2 pseudowire for xconnect service.
xconnect
Binds an attachment circuit to an L2TPv3 pseudowire for xconnect service and enters xconnect configuration mode.
pvc (Frame Relay VC-bundle)
To create a permanent virtual circuit (PVC) that is a Frame Relay PVC bundle member, and to enter Frame Relay VC-bundle-member configuration mode, use the pvc command in Frame Relay VC-bundle configuration mode. To delete a PVC from the Frame Relay PVC bundle, use the no form of this command.
Usage Guidelines
To use this command, you must first create a Frame Relay PVC bundle and enter Frame Relay VC-bundle configuration mode.
A PVC bundle must have at least one PVC for the bundle to come up. A PVC bundle cannot have more than eight PVCs. If you try to configure more than eight PVCs in a bundle, the following message appears on the console:
%FR vc-bundle contains 8 members. Cannot add another.Dynamic PVCs can be specified as PVC bundle members; however, if a PVC has already been created by using another configuration command, you cannot add it to a PVC bundle. If you try to do so, the following message appears on the console:
%DLCI 200 is not a dynamic PVC. Cannot add to VC-Bundle.If a PVC is already a member of a PVC bundle, any attempt to reuse that same PVC in a command that creates a PVC (for example, frame-relay interface-dlci or frame-relay local-dlci) causes the following error message:
%Command is inapplicable to vc-bundle PVCs.Examples
The following example creates a PVC that has a DLCI number of 101 and that belongs to a Frame Relay PVC bundle named new_york:
frame-relay vc-bundle new_york pvc 101Related Commands
Command
Description
dscp (frame-relay vc-bundle-member)
Configures the DSCP value or values for a Frame Relay PVC bundle member.
exp
Configures MPLS EXP levels for a Frame Relay PVC bundle member.
frame-relay vc-bundle
Creates a Frame Relay PVC bundle and enters Frame Relay VC-bundle configuration mode.
match
Specifies which bits of the IP header to use for mapping packet service levels to Frame Relay PVC bundle members
precedence (Frame Relay VC-bundle-member)
Configures the precedence levels for a Frame Relay PVC bundle member.
read-ahead
To configure the read ahead feature of Common Internet File System (CIFS)-Express accelerator, use the read-ahead command in WAAS CIFS configuration mode. To disable the read ahead feature, use the no form of this command.
Usage Guidelines
Before you can enable the read-ahead command, use the following commands:
- Use the parameter-map type waas command in global configuration mode to enter parameter map configuration mode.
- Use the accelerator cifs-express command in parameter map configuration mode to enter WAAS CIFS configuration mode.
To enable the read ahead feature, use the read-ahead enable command before configuring the read ahead size.
Examples
The following example shows how to enable read ahead and configure the read ahead size:
Device(config)# parameter-map type waas waas_global Device(config-profile)# accelerator cifs-express Device(config-waas-cifs)# enable Device(config-waas-cifs)# read-ahead enable Device(config-waas-cifs)# read-ahead size 300Related Commands
Command
Description
accelerator
Enters a specific WAAS Express accelerator configuration mode based on the accelerator being configured.
parameter-map type waas
Configures WAAS Express global parameters.
show waas accelerator
Displays information about WAAS Express accelerators.
show waas statistics accelerator
Displays statistical information about WAAS Express accelerators.
receive-window
To configure the packet size of the receive window on the remote provider edge router at the other end of a Layer 2 control channel, use the receive-windowcommand in L2TP class configuration mode. To disable the configured value, use the no form of this command.
Command Default
The default packet size of the receive window is the upper limit that the remote peer has for receiving packets.
Usage Guidelines
To determine the upper limit for the number argument, refer to the platform-specific documentation for the peer router.
retransmit
To configure the retransmission settings of control packets, use the retransmitcommand in L2TP class configuration mode. To disable the configured values, use the no form of this command.
retransmit { initial retries initial-retries | retries retries | timeout { max | min } seconds }
no retransmit { initial retries initial-retries | retries retries | timeout { max | min } seconds }
Syntax Description
initial retries initial-retries
Specifies how many start control channel requests (SCCRQs) are re-sent before giving up on the session. Valid values for the initial-retries argument range from 1 to 1000. The default value is 2
retries retries
Specifies how many retransmission cycles occur before determining that the peer provider edge (PE) router does not respond. Valid values for the retries argument range from 1 to 1000. The default value is 15.
timeout max | min } seconds
Specifies maximum and minimum retransmission intervals (in seconds) for resending control packets. Valid values for the timeout argument range from 1 to 8. The default maximum interval is 8; the default minimum interval is 1.
Usage Guidelines
Use this command to configure the amount of time spent trying to establish or maintain a control channel.
Examples
The following example configures ten retries for sending tunneled packets to a remote peer in Layer 2 pseudowires that have been configured with the Layer 2 Tunnel Protocol (L2TP) class named “l2tp-class1”:
Router(config) # l2tp-class l2tp-class1 Router(config-l2tp-class) # retransmit retries 10rewrite ingress tag
To specify the encapsulation adjustment to be performed on a frame ingressing a service instance, use the rewrite ingress tag command in Ethernet service configuration mode. To delete the encapsulation adjustment, use the no form of this command.
rewrite ingress tag { pop | { 1 | 2 } | [symmetric] | push { dot1ad vlan-id | [ dot1q vlan-id ] | [symmetric] | dot1q vlan-id | [ second-dot1q vlan-id ] | [symmetric] } | translate { 1-to-1 | { dot1ad vlan-id | dot1qvlan-id | [symmetric] } } | 1-to-2 { dot1ad vlan-iddot1q vlan-id } | dot1q vlan-idsecond-dot1q vlan-id | [symmetric] | 2-to-1 { dot1ad vlan-id | dot1q vlan-id | [symmetric] } | 2-to-2 { dot1q vlan-id | second-dot1q vlan-id | [symmetric] } }
no rewrite ingress tag
Syntax on the Cisco ASR 1000 Series Aggregation Router
Syntax Description
rewrite ingress tag {pop {1 | 2} [symmetric] | push {dot1ad vlan-id [dot1q vlan-id] [symmetric] | dot1q vlan-id [second-dot1q vlan-id] [symmetric] | vlan-type {0x88a8 | 0x9100 | 0x9200} [second-dot1q vlan-id] [symmetric]} | translate {1-to-1{dot1ad vlan-id| dot1q vlan-id[vlan-type {0x88a8 | 0x9100 | 0x9200}] [symmetric]} | 1-to-2 {dot1ad vlan-id dot1q vlan-id| dot1q vlan-id{second-dot1q vlan-id| vlan-type{0x88a8 | 0x9100 | 0x9200} second-dot1q vlan-id}} [symmetric] | 2-to-1{dot1ad vlan-id[symmetric] | dot1q vlan-id [vlan-type{0x88a8 | 0x9100 | 0x9200}] [symmetric]} | 2-to-2 {dot1ad vlan-id dot1q vlan-id[symmetric] | dot1q vlan-id{second-dot1q vlan-id| vlan-type {0x88a8 | 0x9100 | 0x9200} second-dot1q vlan-id} [symmetric]}}
no rewrite ingress tag
pop
Removes a tag from a packet.
{1 | 2}
Specifies either the outermost tag or the two outermost tags for removal from a packet.
symmetric
(Optional) Indicates a reciprocal adjustment to be done in the egress direction. For example, if the ingress pops a tag, the egress pushes a tag and if the ingress pushes a tag, the egress pops a tag.
push
Adds a tag.
dot1ad
Specifies an IEEE 802.1ad tag.
vlan-id
Integer in the range 1 to 4094 that identifies the VLAN.
dot1q
Specifies an IEEE 802.1Q tag.
second-dot1q
Specifies a different 802.1Q tag at the ingress service instance.
vlan-type
Specifies the type of VLAN protocol.
0x88a8
Specifies the protocol type 0x88a8.
0x9100
Specifies the protocol type 0x9100.
0x9200
Specifies the protocol type 0x9200.
translate
Translates, by VLAN ID, a tag or a pair of tags defined in the encapsulation command.
1-to-1
Translates a single tag defined by the encapsulation command to a single tag defined in the rewrite ingress tag command.
1-to-2
Translates a single tag defined by the encapsulation command to a pair of tags defined in the rewrite ingress tag command.
2-to-1
Translates, by VLAN ID, a pair of tags defined by the encapsulation command to a single tag defined in the rewrite ingress tag command.
2-to-2
Translates, by VLAN ID, a pair of tags defined by the encapsulation command to a pair of tags defined in the rewrite ingress tag command.
Command Default
The frame is left intact on ingress (the service instance is equivalent to a trunk port).
Command History
Release
Modification
12.2(33)SRB
This command was introduced.
Cisco IOS XE Release 3.2S
This command was integrated into Cisco IOS XE Release 3.2S.
Cisco IOS XE Release 3.5S
This command was implemented on the Cisco ASR 903 Router.
15.1(2)SNH
This command was implemented on the Cisco ASR 901 Series Aggregation Services Router.
Usage Guidelines
The symmetric keyword is accepted for all rewrite operations only when a single VLAN is configured in encapsulation. If a list of VLANs or a range of VLANs is configured in encapsulation, the symmetric keyword is accepted only for push rewrite operations.
The pop keyword assumes the elements being popped are defined by the encapsulation type. The exception case should be drop the packet.
The translate keyword assumes the tags being translated from are defined by the encapsulation type. In the 2-to-1 option, the “2” means 2 tags of a type defined by the encapsulation command. The translation operation requires at least one “from” tag in the original packet. If the original packet contains more tags than the ones defined in the “from,” the operation should be done beginning on the outer tag. Exception cases should be dropped.
Examples
The following example shows how to specify the encapsulation adjustment to be performed on the frame ingressing the service instance:
Device> enable Device# configure terminal Device(config) interface gigabitethernet 2/0/0 Device(config-if)# service instance 100 ethernet Device(config-if-srv)# encapsulation dot1q 100 Device(config-if-srv)# rewrite ingress tag push dot1q 200rd (VPLS)
To specify a route distinguisher (RD) to distribute endpoint information in a Virtual Private LAN Service (VPLS) configuration, use the rd command in L2 VFI configuration or VFI autodiscovery configuration mode. To remove the manually configured RD and return to the automatically generated RD, use the no form of this command.
rd { autonomous-system-number:nn | ip-address:nn }
no rd { autonomous-system-number:nn | ip-address:nn }
Command Default
VPLS autodiscovery automatically generates a RD using the Border Gateway Protocol (BGP) autonomous system number and the configured virtual forwarding instance (VFI) VPN ID.
Command Modes
L2 VFI configuration (config-vfi)
VFI autodiscovery configuration (config-vfi-autodiscovery)
Usage Guidelines
VPLS autodiscovery automatically generates an RD using the BGP autonomous system number and the configured VFI VPN ID. You can use this command to change the automatically generated RD.
The same RD value cannot be configured in multiple VFIs.
There are two formats for configuring the RD argument. It can be configured in the autonomous-system-number:network-number format, or it can be configured in the ip-address:network-number format.
An RD is either:
Examples
The following example shows a configuration using VPLS autodiscovery that sets the RD to an IP address of 10.4.4.4 and a network address of 70:
Device(config)# l2 vfi SP2 autodiscovery Device(config-vfi)# vpn id 200 Device(config-vfi)# vpls-id 10.4.4.4:70 Device(config-vfi)# rd 10.4.5.5:7The following example shows a configuration using VPLS Autodiscovery that sets the RD to an autonomous system number of 2 and a network address of 3:
Device(config)# l2 vfi SP2 autodiscovery Device(config-vfi)# vpn id 200 Device(config-vfi)# vpls-id 10.4.4.4:70 Device(config-vfi)# rd 2:3The following example shows a configuration using VPLS autodiscovery that sets the RD to an autonomous system number of 2 and a network address of 3 in VFI autodiscovery configuration mode:
Device(config)# l2vpn vfi context vfi1 Device(config-vfi)# vpn id 200 Device(config-vfi)# autodiscovery bgp signaling ldp Device(config-vfi-autodiscovery)# rd 2:3route-target (VPLS)
To specify a route target for a Virtual Private LAN Services (VPLS) virtual forwarding instance (VFI), use the route-target command in L2 VFI configuration or VFI auto discovery configuration mode. To revert to the automatically generated route target, use the no form of this command.
route-target [ import | export | both ] { autonomous-system-number:nn | ip-address:nn }
no route-target { import | export | both } { autonomous-system-number:nn | ip-address:nn }
Syntax Description
import
(Optional) Imports routing information from the target VPN extended community.
export
(Optional) Exports routing information to the target VPN extended community.
both
(Optional) Imports and exports routing information to the target VPN extended community.
autonomous-system-number:nn
Specifies the autonomous system number (ASN) and a 32-bit number.
ip-address:nn
Specifies the IP address and a 16-bit number.
Command Default
VPLS Autodiscovery automatically generates a route target using the lower six bytes of the route distinguisher (RD) and VPLS ID.
Command Modes
L2 VFI configuration (config-vfi)
VFI autodiscovery configuration (config-vfi-autodiscovery)
Usage Guidelines
The same route target cannot be configured in multiple VFIs.
Examples
The following example shows how to configure VPLS autodiscovery route-target extended community attributes for VFI SP1:
Device(config)# l2 vfi SP1 autodiscovery Device(config-vfi)# vpn id 100 Device(config-vfi)# vpls-id 5:300 Device(config-vfi)# rd 4:4 Device(config-vfi)# route-target 10.1.1.1:29The following example shows how to configure VPLS autodiscovery route-target extended community attributes for VFI vfi1:
Device(config)# l2vpn vfi context vfi1 Device(config-vfi)# vpn id 100 Device(config-vfi)# autodiscovery bgp signaling ldp Device(config-vfi-autodiscovery)# rd 4:4 Device(config-vfi-autodiscovery)# route-target 10.1.1.1:29Related Commands
Command
Description
autodiscovery (l2vpn vfi)
Designates VFI as having BGP autodiscovered pseudowire members.
auto-route-target
Automatically generates the route target in a VFI.
l2 vfi autodiscovery
Enables a VPLS PE router to automatically discover other PE routers that are part of the same VPLS domain.
rtcp-regenerate
To generate and terminate the RTCP packets on the SPA-DSP, use the rtcp-regeneratecommand in the SBC configuration mode (config-sbc) for the Unified Model, and from the SBC DBE configuration mode (config-sbc-dbe) for the Distributed Model.
Command Modes
SBC configuration (config-sbc) for the Unified Model
SBC DBE configuration (config-sbc-dbe) for the Distributed ModelUsage Guidelines
Use this command to generate and terminate the RTCP packets on the SPA-DSP on a Cisco ASR 1000 Series Router.
Examples
The following example shows how to generate and terminate the RTCP packets on the SPA-DSP on the Cisco Unified Border Element: Unified Model:
Router> enable Router# config terminal Router(config)# sbc mySBC Router(config-sbc)# rtcp-regenerateThe following example shows how to generate and terminate the RTCP packets on the SPA-DSP on the Cisco Unified Border Element: Distributed Model:
Router> enable Router# config terminal Router(config)# sbc mySBC dbe
