-
Cisco IOS Wide-Area Networking Command Reference
-
Introduction
-
A through C
-
D through E
-
fdl through frame-relay lapf n200
-
frame-relay lapf n201 through fr-atm connect dlci
-
H through L
-
M through R
-
sequencing through show mpls l2transport vc
-
show smds addresses through vpls-id
-
x25 accept-reverse through x25 pvc (XOT)
-
x25 pvc rbp local through xot access-group
-
Table Of Contents
dscp (Frame Relay VC-bundle-member)
encapsulation (Any Transport over MPLS)
encapsulation (Frame Relay VC-bundle)
encapsulation (Layer 2 local switching)
encapsulation dot1q (service instance)
encapsulation dot1q second-dot1q
de-bit
To set Frame Relay discard-eligible (DE) bit mapping for FRF.5 and FRF.8 network interworking, use the de-bit command in FRF.5 connect configuration mode or FRF.8 connect configuration mode. To disable or reset Frame Relay DE bit mapping, use the no form of this command.
de-bit {0 | 1 | map-clp}
no de-bit {0 | 1 | map-clp}
Syntax Description
Defaults
map-clp
Command Modes
FRF.5 connect configuration
FRF.8 connect configurationCommand History
Usage Guidelines
In the default state, the DE bit in the Frame Relay header is set to 1 when one or more ATM cells that belong to a frame have their cell loss priority (CLP) field set to 1 or when the DE field of the Frame Relay service-specific convergence sublayer (FR-SSCS) protocol data unit (PDU) is set to 1.
When the no de-bit command and map-clp keyword are entered, the FR-SSCS PDU DE field is copied unchanged to the Q.922 core frame DE field, independently of CLP indications received at the ATM layer.
Examples
The following example creates a connection between the virtual circuit (VC) group named "friends" and ATM PVC 0/32 and configures FR DE field mapping to match the ATM CLP field:
Router(config)# vc-group friendsRouter(config-vc-group)# serial1/0 16 16Router(config-vc-group)# serial1/0 17 17Router(config-vc-group)# serial1/0 18 18Router(config-vc-group)# serial1/0 19 19Router(config)# interface atm3/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter (config-if-atm-vc)# exitRouter (config-if)# exitRouter(config)# connect vc-group friends atm3/0 0/32Router(config-frf5)# de-bit map-clpRelated Commands
de-bit map-clp
To set Frame Relay discard eligible (DE) bit mapping for FRF.5 network interworking, use the de-bit map-clp command in FRF.5 connect mode. To disable or reset Frame Relay DE bit mapping, use the no form of this command.
de-bit map-clp
no de-bit map-clp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
FRF.5 connect configuration
Command History
Usage Guidelines
In the default state, the DE bit in the Frame Relay header is set to 1 when one or more ATM cells belonging to a frame have their cell loss priority (CLP) field set to 1, or when the DE field of the Frame Relay service specific convergence sublayer (FR-SSCS) protocol data unit (PDU) is set to 1.
When the no de-bit map-clp command is entered, the FR-SSCS PDU DE field is copied unchanged to the Q.922 core frame DE field, independent of CLP indications received at the ATM layer.
Examples
The following example creates a connection that connects the virtual circuit (VC) group named friends to ATM PVC 0/32 and configures FR DE field mapping to match the ATM CLP field:
Router(config)# vc-group friendsRouter(config-vc-group)# serial0 16 16Router(config-vc-group)# serial0 17 17Router(config-vc-group)# serial0 18 18Router(config-vc-group)# serial0 19 19Router(config)# interface atm3/0Router(config-if)# pvc 0/32Router(config-if-atm-vc)# encapsulation aal5mux frame-relayRouter(config)# connect vc-group friends atm3/0 0/32Router(config-frf5)# de-bit map-clpRelated Commands
digest
To enable Layer 2 Tunneling Protocol Version 3 (L2TPv3) control channel authentication or integrity checking, use the digest command in L2TP class configuration mode. To disable control channel authentication or integrity checking, use the no form of this command.
digest [secret [0 | 7] password] [hash {md5 | sha}]
no digest [secret password] [hash {md5 | sha}]
Syntax Description
Command Default
L2TPv3 control channel authentication and integrity checking are disabled by default.
Command Modes
L2TP class configuration
Command History
Usage Guidelines
Beginning in Cisco IOS Release 12.0(29)S, two methods of control channel authentication are available. The L2TPv3 Control Message Hashing feature (enabled with the digest command) introduces a more robust authentication method than the older Challenge Handshake Authentication Protocol (CHAP) style method of authentication enabled with the authentication command. You may choose to enable both methods of authentication to ensure interoperability with peers that support only one of these methods of authentication, but this configuration will yield control of which authentication method is used to the peer PE router. Enabling both methods of authentication should be considered an interim solution to solve backward-compatibility issues during software upgrades.
Table 9 shows a compatibility matrix for the different L2TPv3 authentication methods. PE1 is running a Cisco IOS software release that supports the L2TPv3 Control Message Hashing feature, and the different possible authentication configurations for PE1 are shown in the first column. Each remaining column represents PE2 running software with different available authentication options, and the intersections indicate the different compatible configuration options for PE2. If any PE1/PE2 authentication configuration poses ambiguity on which method of authentication will be used, the winning authentication method is indicated in bold. If both the old and new authentication methods are enabled on PE1 and PE2, both types of authentication will occur.
Table 9 Compatibility Matrix for L2TPv3 Authentication Methods
None
None
None
New integrity check
None
New integrity check
Old authentication
Old authentication
—
Old authentication
Old authentication and new authentication
Old authentication and new integrity check
New authentication
—
New authentication
New authentication
Old authentication and new authentication
New integrity check
None
None
New integrity check
None
New integrity check
Old and new authentication
Old authentication
New authentication
Old authentication
New authentication
Old and new authentication
Old authentication and new integrity check
Old authentication and new integrity check
Old authentication
—
Old authentication
Old authentication and new authentication
Old authentication and new integrity check
1 Any PE software that supports only the old CHAP-like authentication system.
2 Any PE software that supports only the new message digest authentication and integrity checking authentication system, but does not understand the old CHAP-like authentication system. This type of software may be implemented by other vendors based on the latest L2TPv3 draft.
3 Any PE software that supports both the old CHAP-like authentication and the new message digest authentication and integrity checking authentication system, such as Cisco IOS 12.0(29)S or later releases.
In Cisco IOS Release 12.0(30)S, this command was enhanced to allow two L2TPv3 control channel authentication passwords to be configured simultaneously. This enhancement allows the transition from using an old authentication password to using a new authentication password without interrupting L2TPv3 services. No more than two passwords may be configured at a time. In order to configure a new password when two passwords are already configured, you must remove one of the existing passwords using the no digest secret password command. The number of configured passwords can be verified using the show l2tun tunnel command.
Examples
The following example configures control channel authentication and a control channel authentication password for tunnels belonging to the L2TP class named class1:
l2tp-class class1digest secret cisco hash shahiddenThe following example configures a second control channel authentication password for tunnels belonging to the L2TP class named class1:
l2tp-class class1digest secret cisco2 hash shaThe following example removes the old control channel authentication password for tunnels belonging to the L2TP class named class1. The old password should be removed only after all peer routers have been configured with the new password.
l2tp-class class1no digest secret cisco hash shaThe following example configures control channel integrity checking and disables validation of the message digest for L2TPv3 tunnels belonging to the L2TP class named class2:
l2tp-class class2digest hash shano digest checkThe following example disables validation of the message digest for L2TPv3 tunnels belonging to the L2TP class named class3. Control channel authentication and control channel integrity checking are both disabled.
l2tp-class class3no digest checkRelated Commands
dscp (Frame Relay VC-bundle-member)
To configure the differentiated services code point (DSCP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the dscp command in Frame Relay VC-bundle-member configuration mode. To remove the DSCP level configuration from the PVC, use the no form of this command.
dscp {level | other}
no dscp level
Syntax Description
Command Default
DSCP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
Usage Guidelines
Assignment of DSCP levels to PVC bundle members lets you create differentiated service, because you can distribute the DSCP levels over the various PVC bundle members. You can map a single DSCP level or range of levels to each discrete PVC in the bundle, which enables PVCs in the bundle to carry packets marked with different DSCP levels.
Use the dscp other command to configure a PVC to carry traffic marked with DSCP levels not specifically configured on other PVCs. Only one PVC in the bundle can be configured with the dscp other command.
This command is available only when the match type for the PVC bundle is set to dscp by using the match dscp command in Frame Relay VC-bundle configuration mode.
You can overwrite the DSCP level configuration on a PVC by reentering the dscp command with a new level value.
There is no default value for this command. When the PVC bundle is set to dscp using the match dscp command, all PVCs in the bundle are reset to remove any existing DSCP values. If one or more DSCP values are not specifically configured, the bundle will not come up.
However, a PVC may exist in a bundle but have no DSCP value associated with the bundle. As long as all valid DSCP values are handled by one or more of the other PVCs in the bundle, the bundle can come up, but the PVC that has no DSCP value configured will not participate in the bundle.
A DSCP level can be configured on one PVC bundle member per bundle. If you configure the same DSCP level on more than one PVC within a bundle, the following error warning appears on the console:
%Overlapping diff-serv code pointsExamples
The following example assigns DSCP levels 0 through 9 to PVC bundle member 300 in a Frame Relay PVC bundle named MP-3-static:
interface Serial4/0
encapsulation frame-relay
frame-relay vc-bundle MP-3-static
match dscp
pvc 300
dscp 0-9
frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticThe following example changes the DSCP levels in the above example from 0 through 9 to 0, 9, and 20 through 29:
interface serial 1/4frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticmatch dscppvc 300dscp 0,9,20-29Related Commands
efci-bit
To set the explicit forward congestion indication (EFCI) bit field in the ATM cell header for FRF.8 service interworking, use the efci-bit command in FRF.8 connect mode. To disable or reset this bit, use the no form of this command.
efci-bit {0 | map-fecn}
no efci-bit {0 | map-fecn}
Syntax Description
Defaults
The default is 0.
Command Modes
FRF.8 connect configuration
Command History
Usage Guidelines
This command maps from Frame Relay to ATM.
Examples
The following example creates a connection that connects Frame Relay DLCI 100 to ATM PVC 0/32, and sets the EFCI field in the ATM cell header to 1 when the FECN field in the Frame Relay header is set:
Router(config)# interface atm1/0Router(config-if)# pvc 0/32Router(config-if)# encapsulation aal5mux fr-atm-srvRouter(config)# connect serial0 100 atm1/0 0/32 service-interworkingRouter(config-frf8)# efci-bit map-fecnRelated Commands
encapsulation (Any Transport over MPLS)
To configure the ATM adaptation layer (AAL) encapsulation for an Any Transport over MPLS (AToM), use the encapsulation command in the appropriate configuration mode. To remove the ATM encapsulation, use the no form of this command.
encapsulation layer-type
no encapsulation layer-type
Syntax Description
layer-type
The adaptation layer type, which is one of the following:
•
aal5—ATM adaptation layer 5
•
Command Default
The default encapsulation is AAL5.
Command Modes
L2transport VC configuration—for ATM PVCs
VC class configuration—for VC classCommand History
Usage Guidelines
In L2transport VC configuration mode, the pvc command and the encapsulation command work together. Use the commands for AToM differently than for all other applications. Table 10 shows the differences in how the commands are used.
The following list highlights the differences:
•
•
•
When you use the aal5 keyword, incoming cells (except Operation, Administration, and Maintenance [OAM] cells) on that PVC are treated as AAL5 encapsulated packets. The router reassembles the packet from the incoming cells. The router does not check the contents of the packet, so it does not need to know the encapsulation type (such as aal5snap and aal5mux). After imposing the Multiprotocol Label Switching (MPLS) label stack, the router sends the reassembled packet over the MPLS core network.
When you use the aal0 keyword, the router strips the header error control (HEC) byte from the cell header and adds the MPLS label stack. The router sends the cell over the MPLS core network.
Examples
The following example shows how to configure a PVC to transport ATM cell relay packets for AToM:
Router> enableRouter# configure terminalRouter(config)# interface atm1/0Router(config-if)# pvc 1/100 l2transportRouter(config-if-atm-l2trans-pvc)# encapsulation aal0Router(config-if-atm-l2trans-pvc)# xconnect 10.13.13.13 100 encapsulation mplsThe following example shows how to configure ATM AAL5 over MPLS in VC class configuration mode. The VC class is applied to a PVC.
Router> enableRouter# configure terminalRouter(config)# vc-class atm aal5classRouter(config-vc-class)# encapsulation aal5Router(config)# interface atm1/0Router(config-if)# pvc 1/200 l2transportRouter(config-if-atm-l2trans-pvc)# class-vc aal5classRouter(config-if-atm-l2trans-pvc)# xconnect 10.13.13.13 100 encapsulation mplsRelated Commands
encapsulation (Frame Relay VC-bundle)
To override the encapsulation for a point-to-point subinterface and configure Frame Relay encapsulation for an individual Frame Relay permanent virtual circuit (PVC) bundle, use the encapsulation command in Frame Relay VC-bundle configuration mode. To disable the encapsulation for the individual PVC bundle and revert to the encapsulation for the point-to-point subinterface, use the no form of this command.
encapsulation [cisco | ietf]
no encapsulation [cisco | ietf]
Syntax Description
Defaults
Encapsulation type that is configured on the main interface.
Command Modes
Frame Relay VC-bundle configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to override the encapsulation at a point-to-point subinterface for an individual Frame Relay PVC bundle. This command is available for point-to-point subinterfaces only; it cannot be used on multipoint interfaces.
Examples
The following example configures RFC 1490 encapsulation for the Frame Relay PVC bundle named "P2P-5":
interface serial 1/4.2 point-to-pointip address 10.1.1.1 255.0.0.0frame-relay vc-bundle P2P-5encapsulation ietfRelated Commands
encapsulation (L2TP)
To specify the Layer 2 data encapsulation method to be used for tunneling IP traffic over a pseudowire, use the encapsulation (L2TP) command in pseudowire class configuration mode. To remove the specified Layer 2 encapsulation method, use the no form of this command.
encapsulation {l2tpv2 | l2tpv3 [manual] | mpls}
no encapsulation {l2tpv2 | l2tpv3 [manual] | mpls}
Syntax Description
Defaults
No encapsulation method is specified.
Command Modes
Pseudowire class configuration
Command History
Usage Guidelines
This command must be configured if the pseudowire class will be referenced from an xconnect or pseudowire configured to forward Layer 2 traffic.
Examples
The following example shows how to configure L2TPv3 as the data encapsulation method for the pseudowire class named "ether-pw":
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation l2tpv3Related Commands
pseudowire-class
Specifies the name of an L2TP pseudowire class and enters pseudowire class configuration mode.
encapsulation (Layer 2 local switching)
To configure the ATM adaptation layer (AAL) for a Layer 2 local switching ATM permanent virtual circuit (PVC), use the encapsulation command in ATM PVC L2transport configuration mode. To remove an encapsulation from a PVC, use the no form of this command.
encapsulation layer-type
no encapsulation layer-type
Syntax Description
layer-type
Adaptation layer type. The values are:
•
•
•
•
•
Command Default
If you do not create a PVC, one is created for you. The default encapsulation types for autoprovisioned PVCs are as follows:
•
•
Command Modes
ATM PVC L2transport configuration
Command History
Usage Guidelines
The pvc command and the encapsulation command work together. The use of these commands with Layer 2 local switching is slightly different from the use of these commands with other applications. The following list highlights the differences:
•
•
Table 11 shows the encapsulation types supported for each transport type:
Examples
The following example shows how to configure a PVC to transport AAL0 packets for Layer 2 local switching:
pvc 1/100 l2transportencapsulation aal0Related Commands
encapsulation default
To configure the default service instance on a port, use the encapsulation default command in the service instance mode. To delete the default service instance on a port, use the no form of this command.
encapsulation default
no encapsulation default
Syntax Description
This command has no arguments or keywords.
Command Default
No default service instance is configured on the port.
Command Modes
Service instance
Command History
Usage Guidelines
If the default service instance is the only one configured on a port, the encapsulation default command matches all ingress frames on that port. If the default service instance is configured on a port that has other non-default service instances, the encapsulation default command matches frames that are unmatched by those non-default service instances (anything that does not meet the criteria of other services instances on the same physical interface falls into this service instance).
Only a single default service instance can be configured per interface. If you attempt to configure more than one default service instance per interface, the encapsulation default command is rejected.
Only one encapsulation command must be configured per service instance.
Examples
The following example shows how to configure a service instance on a port:
Router(config-if-srv)# encapsulation defaultRelated Commands
encapsulation dot1q (service instance)
To define the matching criteria to map 802.1Q frames ingress on an interface to the appropriate service instance, use the encapsulation dot1q command in the service instance mode. To delete the matching criteria to map 802.1Q frames ingress on an interface to the appropriate service instance, use the no form of this command.
encapsulation dot1q vlan-id[,vlan-id[-vlain-id]] [native]
no encapsulation dot1q vlan-id[,vlan-id[-vlain-id]] [native]
Syntax Description
.
Command Default
No matching criteria are defined.
Command Modes
Service instance
Command History
Usage Guidelines
The criteria for this command are: single VLAN, range of VLANs, and lists of the previous two.
A single 802.1Q service instance, allows one VLAN, multiple VLANs, or a range of VLANs. The native keyword can only be set if a single VLAN tag has been specified.
Only a single service instance per port is allowed to have the native keyword.
Only one encapsulation command may be configured per service instance.
Examples
The following example shows how to map 802.1Q frames ingress on an interface to the appropriate service instance:
Router(config-if-srv)# encapsulation dot1q 10Related Commands
encapsulation dot1q second-dot1q
To define the matching criteria to map Q-in-Q ingress frames on an interface to the appropriate service instance, use the encapsulation dot1q second-dot1q command in service instance mode. To delete the matching criteria to map Q-in-Q ingress frames on an interface to the appropriate service instance, use the no form of this command.
encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}
no encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}
Syntax Description
Command Default
No matching criteria are defined.
Command Modes
Service instance
Command History
Usage Guidelines
The criteria for this command are: the outer tag must be unique and the inner tag may be a single VLAN, a range of VLANs or lists of the previous two.
QinQ service instance, allows single, multiple or range on second-dot1q.
Only one encapsulation command must be configured per service instance.
Examples
The following example shows how to map ingress frames to a service instance:
Router(config-if-srv)# encapsulation dot1q second-dot1q 20Related Commands
encapsulation frame-relay
To enable Frame Relay encapsulation, use the encapsulation frame-relay command in interface configuration mode. To disable Frame Relay encapsulation, use the no form of this command.
encapsulation frame-relay [cisco | ietf]
no encapsulation frame-relay [ietf]
Syntax Description
Defaults
The default is Cisco's own encapsulation.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command with no keywords to restore the default Cisco encapsulation, which is a 4-byte header with 2 bytes for the DLCI and 2 bytes to identify the packet type.
You should shut down the interface prior to changing encapsulation types. Although this is not required, shutting down the interface ensures that the interface is reset for the new encapsulation.
Examples
The following example configures Cisco Frame Relay encapsulation on interface serial 1:
interface serial 1encapsulation frame-relayUse the ietf keyword if your router or access server is connected to another vendor's equipment across a Frame Relay network to conform with RFC 1490:
interface serial 1encapsulation frame-relay ietfencapsulation frame-relay mfr
To create a multilink Frame Relay bundle link and to associate the link with a bundle, use the encapsulation frame-relay mfr command in interface configuration mode. To remove the bundle link from the bundle, use the no form of this command.
encapsulation frame-relay mfr number [name]
no encapsulation frame-relay mfr number [name]
Syntax Description
Command Default
Frame Relay encapsulation is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the name argument to assign a LID name to a bundle link. This name will be used to identify the bundle link to peer devices and to enable the devices to determine which bundle links are associated with which bundles. The LID name can also be assigned or changed by using the frame-relay multilink lid command on the bundle link interface. If the LID name is not assigned, the default name is the name of the physical interface.
Tip
To remove a bundle link from a bundle, use the no encapsulation frame-relay mfr command or configure a new type of encapsulation on the interface by using the encapsulation command.
Examples
The following example shows serial interface 0 being associated as a bundle link with bundle interface "mfr0." The bundle link identification name is "BL1."
interface mfr0!interface serial 0encapsulation frame-relay mfr0 BL1Related Commands
encapsulation l2tpv3
To specify that Layer 2 Tunnel Protocol Version 3 (L2TPv3) is used as the data encapsulation method for tunneling IP traffic over the pseudowire, use the encapsulation l2tpv3 command in pseudowire class or VC class configuration mode. To remove L2TPv3 as the encapsulation method, use the no pseudowire-class command (see the Usage Guidelines for more information).
encapsulation l2tpv3
no pseudowire-class
Syntax Description
This command has no arguments or keywords.
Command Default
No encapsulation method is specified.
Command Modes
Pseudowire class configuration
VC class configurationCommand History
Usage Guidelines
This command must be configured if the pseudowire class will be referenced from an Xconnect configured to forward L2TPv3 traffic.
Once you specify the encapsulation l2tpv3 command, you cannot remove it using the no encapsulation l2tpv3 command. Nor can you change the command's setting using the encapsulation mpls command. Those methods result in the following error message:
Encapsulation changes are not allowed on an existing pw-class.To remove the command, you must delete the pseudowire with the no pseudowire-class command. To change the type of encapsulation, remove the pseudowire with the no pseudowire-class command and re-establish the pseudowire and specify the new encapsulation type.
Examples
The following example shows how to configure L2TPv3 as the data encapsulation method for the pseudowire class named ether-pw:
Router(config)# pseudowire-class ether-pwRouter(config-pw)# encapsulation l2tpv3The following example configures ATM AAL5 over L2TPv3 in VC class configuration mode:
vc-class atm aal5classencapsulation aal5Related Commands
encapsulation lapb
To exchange datagrams over a serial interface using Link Access Procedure, Balanced (LAPB) encapsulation, use the encapsulation lapb command in interface configuration mode.
encapsulation lapb [dte | dce] [multi | protocol]
Syntax Description
Defaults
The default serial encapsulation is High-Level Data Link Control (HDLC). You must explicitly configure a LAPB encapsulation method.
DTE operation is the default LAPB mode. IP is the default protocol.
Command Modes
Interface configuration
Command History
Usage Guidelines
LAPB encapsulations are appropriate only for private connections, where you have complete control over both ends of the link. Connections to X.25 networks should use an X.25 encapsulation configuration, which operates the X.25 Layer 3 protocol above a LAPB Layer 2.
One end of the link must be a logical DCE device, and the other end a logical DTE device. (This assignment is independent of the interface's hardware DTE or DCE identity.)
Both ends of the LAPB link must specify the same protocol encapsulation.
LAPB encapsulation is supported on serial lines configured for dial-on-demand routing (DDR). It can be configured on DDR synchronous serial and ISDN interfaces and on DDR dialer rotary groups. It is not supported on asynchronous dialer interfaces.
A single-protocol LAPB encapsulation exchanges datagrams of the given protocol, each in a separate LAPB information frame. You must configure the interface with the protocol-specific parameters needed—for example, a link that carries IP traffic will have an IP address defined for the interface.
A multiprotocol LAPB encapsulation can exchange any or all of the protocols allowed for a LAPB interface. It exchanges datagrams, each in a separate LAPB information frame. Two bytes of protocol identification data precede the protocol data. You need to configure the interface with all the protocol-specific parameters needed for each protocol carried.
Multiprotocol LAPB encapsulation supports transparent bridging. This feature requires use of the encapsulation lapb multi command followed by the bridge-group command, which identifies the bridge group associated with multiprotocol LAPB encapsulation. This feature does not support use of the encapsulation lapb protocol command with a bridge keyword.
LAPB encapsulation supports the priority and custom queueing features.
Examples
The following example sets the operating mode as DTE and specifies that AppleTalk protocol traffic will be carried on the LAPB line:
interface serial 1encapsulation lapb dte appletalkRelated Commands
encapsulation smds
To enable Switched Multimegabit Data Service (SMDS) on the desired interface, use the encapsulation smds interface configuration command.
encapsulation smds
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The interface to which this command applies must be a serial interface. All subsequent SMDS configuration commands apply only to an interface with encapsulation SMDS.
Note
Caution
Examples
The following example shows how to configure the SMDS service on serial interface 0:
interface serial 0encapsulation smdsRelated Commands
encapsulation untagged
To define the matching criteria to map untagged ingress Ethernet frames on an interface to the appropriate service instance, use the encapsulation untagged command in the service instance mode. To delete the matching criteria to map untagged ingress Ethernet frames on an interface to the appropriate service instance, use the no form of this command.
encapsulation untagged
no encapsulation untagged
Syntax Description
This command has no arguments or keywords.
Command Default
No matching criteria are defined.
Command Modes
Service instance mode
Command History
Usage Guidelines
Only one service instance per port is allowed to have untagged encapsulation. The reason is to be able to unambiguously map the incoming frames to the service instance. However, it is possible for a port that hosts an service instance matching untagged traffic to host other service instances that match tagged frames.
Only one encapsulation command may be configured per service instance.
Examples
The following example shows how to map untagged ingress Ethernet frames to a service instance:
Router(config-if-srv)# encapsulation untaggedRelated Commands
encapsulation x25
To specify a serial interface's operation as an X.25 device, use the encapsulation x25 command in interface configuration mode. To remove the specification, use the no form of this command.
encapsulation x25 [dte | dce] [ddn | bfe | ietf]
no encapsulation x25 [dte | dce] [ddn | bfe | ietf]
Syntax Description
Defaults
The default serial encapsulation is High-Level Data Link Control (HDLC). You must explicitly configure an X.25 encapsulation method.
DTE operation is the default X.25 mode. Cisco's traditional X.25 encapsulation method is the default.
Command Modes
Interface configuration
Command History
Usage Guidelines
One end of an X.25 link must be a logical DCE device and the other end a logical DTE device. (This assignment is independent of the interface's hardware DTE or DCE identity.) Typically, when connecting to a public data network (PDN), the customer equipment acts as the DTE device and the PDN attachment acts as the DCE.
Cisco has long supported the encapsulation of a number of datagram protocols, using a standard means when available and a proprietary means when necessary. The IETF adopted a standard, RFC 1356, for encapsulating most types of datagram traffic over X.25. X.25 interfaces use Cisco's traditional method unless explicitly configured for IETF operation; if the ietf keyword is specified, that standard is used unless Cisco's traditional method is explicitly configured. For details see the x25 map command.
You can configure a router attaching to the DDN or to a BFE device to use their respective algorithms to convert between IP and X.121 addresses by using the ddn or bfe option, respectively. An IP address must be assigned to the interface, from which the algorithm will generate the interface's X.121 address. For proper operation, this X.121 address must not be modified.
A router DDN attachment can operate as either a DTE or a DCE device. A BFE attachment can operate only as a DTE device. The ietf option is not available if either the ddn or bfe option is selected.
Examples
The following example configures the interface for connection to a BFE device:
interface serial 0encapsulation x25 bfeRelated Commands
ethernet evc
To define an Ethernet virtual connection (EVC) and to enter EVC configuration mode, use the ethernet evc command in global configuration mode. To delete the EVC, use the no form of this command.
ethernet evc evc-id
no ethernet evc evc-id
Syntax Description
Command Default
No EVCs are defined.
Command Modes
Global configuration
Command History
12.2(25)SEG
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
After you enter the ethernet evc command, the device enters EVC configuration mode and the following configuration commands are available:
•
•
•
•
•
Examples
The following example shows how to define an EVC named test1 and to enter EVC configuration mode:
Router(config)# ethernet evc test1Router(config-evc)#Related Commands
exp
To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the exp command in Frame Relay VC-bundle-member configuration mode. To remove the EXP level configuration from the PVC, use the no form of this command.
exp {level | other}
no exp
Syntax Description
Defaults
EXP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
Usage Guidelines
Assignment of MPLS EXP levels to Frame Relay PVC bundle members lets you create differentiated services, because you can distribute the levels over the various PVC bundle members. You can map a single 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 levels.
Use the exp other command to indicate that a PVC can carry traffic marked with EXP levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the exp other command.
All EXP 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 but have no EXP level associated with it. As long as all valid EXP levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no EXP level configured will not participate in it.
The exp command is available only when MPLS is configured on the interface with the mpls ip command.
You can overwrite the EXP level configuration on a PVC by reentering the exp command with a new value.
The MPLS experimental bits are a bit-by-bit copy of the IP precedence bits. When Frame Relay PVC bundles are configured for IP precedence and MPLS is enabled, the precedence command is replaced by the exp command. When MPLS is disabled, the exp command is replaced by the precedence command.
Examples
The following example shows the configuration of four Frame Relay PVC bundle members in PVC bundle bundle1 configured with MPLS EXP level support:
interface serial 0.1 point-to-pointencapsulation frame-relayip address 10.1.1.1mpls ipframe-relay vc-bundle bundle1pvc 100 ny-controlclass controlexp 7protect vcpvc 101 ny-premiumclass premiumexp 6-5protect groupno bump trafficbump explicit 7pvc 102 my-priorityclass priorityexp 4-2protect grouppvc 103 ny-basicclass basicexp otherprotect groupRelated Commands
