Table Of Contents
encapsulation (Layer 2 local switching)
encapsulation untagged dot1q second-dot1q
ima differential-delay-maximum
dbs enable
To apply Dynamic Subscriber Bandwidth Selection (DBS) QoS parameters, use the dbs enable command in the appropriate configuration mode. To remove DBS QoS parameters, use the no form of this command.
dbs enable
no dbs enable
Syntax Description
This command has no arguments or keywords.
Command Default
DBS QoS parameters are not applied.
Command Modes
ATM VC class configuration
ATM VC configuration
ATM PVC range configuration
ATM PVC-in-range configurationCommand History
Usage Guidelines
The no dbs enable command configured in any configuration mode overrides the dbs enable command configured in any configuration mode. Both the dbs enable and no dbs enable commands are saved in the running configuration and appear, when configured, in the output of the show running-config command. The default dbs enable command does not appear in the output of the show running-config command when configured.
When you enter the dbs enable or no dbs enable command, existing sessions are not disconnected. If you have a session that has been configured for DBS and you configure the no dbs enable command on a VC, additional sessions that are configured will display DBS-configured QoS values until the first new session is up. After the first session is brought up, the VC has default and locally configured values. If you configure the dbs enable command after multiple sessions are already up on the VC, all sessions on that VC have DBS QoS parameters.
RADIUS QoS attributes are applied to PVCs when a new PPP over Ethernet (PPPoE) session has peak cell rate (PCR) and sustainable cell rate (SCR) values that are higher than existing PPPoE sessions. If a new PPPoE session with lower PCR and SCR values is added to a PVC, the RADIUS QoS attributes are not applied to the new session. If the user of the PPPoE session that has the higher PCR and SCR values logs out, the QoS attributes are set to those of the lower bandwidth user.
RADIUS QoS attributes override attributes on a PVC configured in ATM PVC-in-range or ATM PVC range configuration mode. If the RADIUS QoS attributes cannot be applied to a PVC, PPPoE and PPPoA sessions cannot be established.
When DBS is configured, normal ATM precedences apply. PVC configurations take precedence over VC class configurations. Thus, if DBS QoS parameters are applied on a VC class and disabled on one PVC in that VC class, DBS QoS parameters are not applied on the PVC. ATM PVC-in-range configurations take precedence over PVC range configurations.
When you configure DBS on a PVC, existing sessions on that PVC remain connected.
Examples
The following example configures DBS in ATM VC class configuration mode:
vc-class atm pppoedbs enableThe following example configures DBS in ATM VC configuration mode:
interface atm0/0/0.5 point-to-pointip address 10.0.0.0 255.255.255.0pvc 0/100dbs enableprotocol pppoeThe following example configures DBS in ATM PVC range configuration mode:
interface atm0/0/0.1 multipointip address 10.0.0.0 255.255.255.0range pvc 0/50 0/70dbs enableThe following example configures DBS in ATM PVC-in-range configuration mode:
interface atm0/0/0.1 multipointrange pvc 0/50 0/70pvc-in-range 60dbs enableRelated Commands
default-name
To provide an emulated LAN name in the configuration server's database for those client MAC addresses and client ATM addresses that do not have explicit emulated LAN name bindings, use the default-name command in database configuration mode. To remove the default name, use the no form of this command.
default-name elan-name
no default-name
Syntax Description
elan-name
Default emulated LAN name for any LAN emulation (LANE) client MAC address or LANE client ATM address not explicitly bound to any emulated LAN name. Maximum length is 32 characters.
Command Default
No name is provided.
Command Modes
Database configuration
Command History
Usage Guidelines
This command affects only the bindings in the configuration server's database. It has no effect on the LANE components themselves.
The named emulated LAN must already exist in the configuration server's database before this command is used. If the default name-to-emulated LAN name binding already exists, the new binding replaces it.
The default-name command is a subcommand of the global lane database global configuration command.
Examples
The following example shows how to specify the emulated Token Ring LAN named man as the default emulated LAN. Because none of the emulated LANs are restricted, clients are assigned to whichever emulated LAN they request. Clients that do not request a particular emulated LAN will be assigned to the named man emulated LAN.
lane database example2name eng server-atm-address 39.000001415555121101020304.0800.200c.1001.02name eng local-seg-id 1000name man server-atm-address 39.000001415555121101020304.0800.200c.1001.01name man local-seg-id 2000name mkt server-atm-address 39.000001415555121101020304.0800.200c.4001.01name mkt local-seg-id 3000default-name manRelated Commands
dxi map
To map a protocol address to a given virtual path identifier (VPI) and virtual channel identifier (VCI), use the dxi map command in interface configuration mode. To remove the mapping for that protocol and protocol address, use the no form of this command.
dxi map protocol protocol-address vpi vci [broadcast]
no dxi map protocol protocol-address
Syntax Description
Command Default
No map definition is established.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used in configurations where the router is intended to communicate with an ATM network through an ATM data service unit (ADSU). Given the circuit identifier parameters (VPI and VCI) for the ATM permanent virtual circuit (PVC), the router computes and uses the DXI frame address (DFA) that is used for communication between the router and the ADSU.
The dxi map command can be used only on a serial interface or HSSI configured for ATM-DXI encapsulation.
Examples
The following example converts all IP packets intended for the host with IP address 172.21.170.49 into ATM cells identified with a VPI of 2 (binary 0000 0010) and a VCI of 46 (binary 0000 0000 0010 1110) by the ADSU:
interface serial 0dxi map ip 172.21.170.49 2 46 broadcastUsing the mapping defined in Annex A of the ATM DXI Specification, the router uses the VPI and VCI information in this example to compute a DFA of 558 (binary 1000101110). The ADSU will use the DFA of the incoming frame to extract the VPI and VCI information when formulating ATM cells.
Related Commands
dxi pvc
Configures multiprotocol or single-protocol ATM-DXI encapsulation.
encapsulation atm-dxi
Enables ATM-DXI encapsulation.
dxi pvc
To configure multiprotocol or single protocol ATM-Data Exchange Interface (DXI) encapsulation, use the dxi pvc command in interface configuration mode. To disable multiprotocol ATM-DXI encapsulation, use the no form of this command.
dxi pvc vpi vci [snap | nlpid | mux]
no dxi pvc vpi vci [snap | nlpid | mux]
Syntax Description
Defaults
LLC/SNAP encapsulation
Command Modes
Interface configuration
Command History
Usage Guidelines
This command can be used only on a serial interface or HSSI that is configured with ATM-DXI encapsulation.
Select the nlpid option if you are using the default encapsulation for software releases earlier than Cisco IOS Release 10.3.
Examples
The following example configures ATM-DXI MUX encapsulation on serial interface 1. The PVC identified by a VPI of 10 and a VCI of 10 can carry a single protocol. Then the protocol to be carried on this PVC is defined by the dxi map command.
interface serial 1dxi pvc 10 10 muxdxi map ip 172.21.176.45 10 10 broadcastThe following example configures ATM-DXI NLPID encapsulation on serial interface 1. The PVC identified by a VPI of 11 and a VCI of 12 can carry multiprotocol traffic that is encapsulated with a header described in RFC 1294/1490.
interface serial 1dxi pvc 11 12 nlpidRelated Commands
class-int
Maps a protocol address to a given VPI and VCI.
encapsulation atm-dxi
Enables ATM-DXI encapsulation.
show dxi pvc
Displays the PVC statistics for a serial interface.
encapsulation (ATM)
To configure the ATM adaptation layer (AAL) and encapsulation type for an ATM virtual circuit (VC), VC class, VC, bundle, or permanent virtual circuit (PVC) range, use the encapsulation command in the appropriate mode. To remove an encapsulation type, use the no form of this command.
encapsulation {aal2 | aal5auto | aal5autoppp virtual-template template-number | aal5ciscoppp virtual-template template-number | aal5mux protocol | aal5nlpid | aal5snap} [group group-name]
no encapsulation {aal2 | aal5auto | aal5autoppp virtual-template template-number | aal5ciscoppp virtual-template template-number | aal5mux protocol | aal5nlpid | aal5snap} [group group-name]
Syntax Description
Defaults
The global default encapsulation option is aal5snap. See the "Usage Guidelines" section for other default characteristics.
Command Modes
ATM VC configuration (for an ATM PVC or SVC)
Bundle configuration (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
VC-class configuration (for a VC class)Command History
Usage Guidelines
Note
To configure Integrated Local Management Interface (ILMI), QSAAL, or Switched Multimegabit Data Service (SMDS) encapsulations for an ATM PVC, use the pvc command.
Use the aal5mux encapsulation option to dedicate the specified PVC to a single protocol; use the aal5snap encapsulation option to multiplex two or more protocols over the same PVC. Whether you select aal5mux or aal5snap encapsulation might depend on practical considerations, such as the type of network and the pricing offered by the network. If the pricing of the network depends on the number of PVCs set up, aal5snap might be the appropriate choice. If pricing depends on the number of bytes transmitted, aal5mux might be the appropriate choice because it has slightly less overhead. Use the aal5mux pppoe option to reduce SNAP encapsulation overhead associated with carrying PPPoE frames. Use the aal5mux bridge ieee8023 option to reduce SNAP encapsulation overhead associated with carrying bridged frames.
Encapsulation for PPPoA
When configuring Cisco PPP over ATM, use the aal5ciscoppp keyword and specify the virtual template number.
It is possible to implicitly create a virtual template when configuring Cisco PPP over ATM. In other words, if the parameters of the virtual template are not explicitly defined before you configure the ATM PVC, the PPP interface will be brought up using default values from the virtual template identified. However, some parameters (such as an IP address) take effect only if they are specified before the PPP interface comes up. Therefore, we recommend that you explicitly create and configure the virtual template before configuring the ATM PVC to ensure that such parameters take effect.
If you specify virtual template parameters after the ATM PVC is configured, you should enter a shutdown command followed by a no shutdown command on the ATM subinterface to restart the interface, causing the newly configured parameters (such as an IP address) to take effect.
Configuring PPPoA/PPPoE Autosense
Use the encapsulation aal5autoppp virtual-template template-number command to configure PPPoA/PPPoE autosense. PPPoA/PPPoE autosense enables a router to distinguish between incoming PPPoA and PPPoE sessions and create virtual access for both PPP types based on demand.
If a PPPoE profile is not specified by using the group group-name option, PPPoE sessions will be established using parameters from the global PPPoE profile. PPPoE profiles must be configured using the bba-group pppoe command.
Note
Entering the no encapsulation aal5autoppp virtual-template command will terminate the PPPoA or PPPoE session and detach the virtual-access interface from the PVC.
Configuring Encapsulation for VC Bundles
Before using this command to configure a VC bundle, enter the bundle subinterface configuration command to create a new bundle or modify an existing one and to enter bundle configuration mode.
A VC bundle can have only one encapsulation keyword configured for it: either aal5snap or aal5mux.
Encapsulation Rules of Precedence
If the encapsulation command is not explicitly configured on an ATM PVC, SVC, or VC bundle, the VC inherits the following default configuration (listed in order of precedence from lowest to highest):
•
•
•
•
Note
Configuring Encapsulation for a PVC Range
When a PVC range or an individual PVC within a PVC range is being configured, the following options are available:
•
•
•
Examples
MUX-Type Encapsulation on a VC Example
The following example configures an ATM PVC with VPI 0 and VCI 33 for a MUX-type encapsulation using IP:
interface atm 1/0pvc 0/33encapsulation aal5mux ipSNAP Encapsulation Example
The following example configures a bundle called "bundle1" for aal5snap encapsulation:
bundle bundle1encapsulation aal5snapPPP over ATM SVCs Example
The following example configures an ATM SVC called "bundle1" with the encapsulation type aal5auto. Encapsulation type aal5auto enables the SVC to use PPP and either aal5snap or aal5mux encapsulation.
interface ATM 2/0/0svc bundle1encapsulation aal5autoPPPoA/PPPoE Autosense Example
The following example enables PPPoA/PPPoE autosense on PVC 30/33. PPPoA sessions will use virtual template 1, and PPPoE sessions will use the global PPPoE profile.
interface ATM 0/0/0.33 multipointpvc 30/33encapsulation aal5autoppp virtual-template 1!bba-group pppoe globalvirtual-template 1sessions max limit 8000sessions per-vc limit 8sessions per-mac limit 2AAL2 Voice over ATM Example
The following example configures a PVC to support AAL2 encapsulation for Voice over ATM:
interface ATM0.2 point-to-pointpvc 2/200vbr-rt 760 760 100encapsulation aal2Related Commands
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 3 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 atm-dxi
To enable ATM-Data Exchange Interface (DXI) encapsulation, use the encapsulation atm-dxi command in interface configuration mode. To disable ATM-DXI, use the no form of this command.
encapsulation atm-dxi
no encapsulation atm-dxi
Syntax Description
This command has no arguments or keywords.
Command Default
When ATM-DXI encapsulation is not configured, HDLC is the default encapsulation.
Command Modes
Interface configuration
Command History
Examples
The following example configures ATM-DXI encapsulation on serial interface 1:
interface serial 1encapsulation atm-dxiRelated Commands
encapsulation untagged dot1q second-dot1q
To define the matching criteria to map untagged dot1q ingress Ethernet frames on an interface to the appropriate service instance, use the encapsulation untagged dot1q second-dot1q command in the service instance mode. To delete the matching criteria to map untagged dot1q ingress Ethernet frames on an interface to the appropriate service instance, use the no form of this command.
encapsulation untagged dot1q {any | vlan-id[vlan-id[vlan-id]} second-dot1q {any | vlan-id[vlan-id[vlan-id]]}
no encapsulation untagged dot1q
Syntax Description
Command Default
No matching criteria are defined.
Command Modes
Service instance mode (config-if-srv) #
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 dot1q ingress Ethernet frames to a service instance. The example contains VLAN IDs 40 and 42.
Router(config-if-srv)# encapsulation untagged dot1q 40 second-dot1q 42Related Commands
framer-type
To set the framer type of supported circuit emulation service (CES) multiservice interchange (MIX) connections to T1 or E1, use the framer-type command in CES configuration mode.
framer-type {t1 | e1}
Syntax Description
t1
Sets the framer type of supported CES connections to T1.
e1
Sets the framer type of supported CES connections to E1.
Defaults
T1
Command Modes
CES configuration
Command History
Usage Guidelines
This command is needed only with CES-enabled network modules (ATM OC-3 CES network modules) that do not contain Cisco T1/E1 multiflex voice/WAN interface cards (VWICs) on the Cisco 3660. Other network modules set their framer type automatically and therefore do not require use of this command. It is also not necessary to use this command for T1 connections, because t1 is the default argument.
To reach CES configuration mode for a particular slot, enter ces and the slot number and port number while in global configuration mode. Note that the port value is always 0, as the interface configuration applies to all ports in the slot.
Examples
The following example sets the framer type of the CES card in slot 1 to E1:
Router(config)# ces 1/0
Router(config-ces)# framer-type e1
Related Commands
holding-time
To specify the holding time value for the MPS-p7 variable of a Multiprotocol over ATM server (MPS), use the holding-time command in MPS configuration mode. To revert to the default value, use the no form of this command.
holding-time seconds
no holding-time seconds
Syntax Description
Defaults
The default holding time is 1200 seconds (20 minutes).
Command Modes
MPS configuration
Command History
Examples
The following example shows how to set the holding time to 600 seconds (10 minutes):
holding-time 600idle-timeout
To configure the idle timeout parameter for tearing down an ATM switched virtual circuit (SVC) connection, use the idle-timeout command in the VC-class configuration mode or interface-ATM-VC configuration mode. To disable the timeout parameter, use the no form of this command.
idle-timeout seconds [minimum-traffic]
no idle-timeout seconds [minimum-traffic]
Syntax Description
Command Default
For PVCs, the default timeout value is infinity.
For SVCs, the default timeout value is 300 seconds.Command Modes
Interface-ATM-VC configuration (config-if-atm-range-pvc)
VC-class configuration (config-vc-class)Command History
Usage Guidelines
If within the idle timeout period, both the input and output traffic rates are below the minimum-rate, the SVC connection is torn down. The input and output traffic rates are set using the ubr, ubr+, or vbr-nrt command.
If the idle-timeout command is not explicitly configured on an ATM SVC, the SVC inherits the following default configuration (listed in order of next highest precedence):
•
•
•
•
Examples
The following example configures an idle period of 300 seconds for an ATM SVC connection. The SVC connection is also configured so that it is considered inactive if the traffic rate is less than 5 kbps.
Router> enableRouter# configure terminalRouter(config)# interface atm 2/0Router(config-if)# range ran1 pvc 32/45 45/56Router(config-if-atm-range)# idle-timeout 300 5Related Commands
ilmi manage
To enable Integrated Local Management Interface (ILMI) management on an ATM permanent virtual circuit (PVC), use the ilmi manage command in the appropriate command mode. To disable ILMI management, use the no form of this command.
ilmi manage
no ilmi manage
Syntax Description
This command has no arguments or keywords.
Command Default
ILMI management is disabled.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC)
VC-class configuration (for a virtual circuit [VC] class)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)Command History
Usage Guidelines
If the ilmi manage command is not explicitly configured on an ATM PVC, the PVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Examples
The following example enables ILMI management on the ATM PVC with VPI 0 and VCI 60. The ILMI PVC is assigned the name routerA and the VPI and VCI are 0 and 16, respectively.
interface atm 0/0pvc routerA 0/16 ilmiexitinterface atm 0/0.1 multipointpvc 0/60ilmi manageima active-links-minimum
To set the minimum number of links that must be operating in order for an ATM inverse multiplexing over ATM (IMA) group to remain in service, use the ima active-links-minimum interface configuration command. To remove the current configuration and set the value to the default, use the no form of this command.
ima active-links-minimum number
no ima active-links-minimum number
Syntax Description
number
Number of links; a value from 1 to 8.
On Cisco 7600 series routers, number is a value from 1 to 16.
Defaults
Links: 1
Command Modes
Interface configuration
Command History
Usage Guidelines
The minimum number of links that should be active for continued group operation depends upon the applications you are using and the speeds they require. ATM frame size and the number of links in a group affect the overhead required by ATM.
Examples
Cisco 2600, 3600, 7100, 7200, and 7500 series routers
The following example specifies that two links in IMA group 2 must be operational in order for the group to remain in service:
interface atm 0/ima2ima active-links-minimum 2Cisco 7600 series routers
The following example shows how to specify that three links in IMA group 0 (on the SPA in chassis slot 2, SIP subslot 1) must be operational in order for the group to remain in service:
interface atm2/1/ima0ima active-links-minimum 3Related Commands
ima autorestart
To enable the auto restart feature for an inverse multiplexing over ATM (IMA) group, use the ima autorestart command in interface configuration mode. Use the no form of the command to disable auto restart if it is enabled.
ima autorestart {near-end-id near-end-group-id [far-end-id far-end-group-id]}
no ima autorestart {near-end-id near-end-group-id [far-end-id far-end-group-id]}
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration (IMA interface)
Command History
Usage Guidelines
The IMA auto restart feature controls how IMA groups are to sync up after a restart. When an IMA group stops operating correctly (for example, due to a failure with the CEoP SPA, an IMA link, or the router), the group must be restarted. When it is restarted, the local IMA group must synchronize with an IMA group at the remote end:
•
•
Include IMA group IDs in the command line to specify how IMA groups are to synchronize:
•
•
To see the current settings for auto restart, issue the show ima interface command and view the Auto-Restart section of the command output.
Examples
The following example shows how to enable IMA auto restart for local IMA group 0 and specify that the group should synchronize with IMA group 5 on the remote end:
interface atm2/1/ima0ima autorestart far-end-id 5The following example shows how to enable IMA auto restart for local IMA group 3 and specify that the group should synchronize with IMA group 3 on the remote end:
interface atm2/1/ima3ima autorestart near-end-id 3 far-end-id 3Related Commands
ima clock-mode
To set the transmit clock mode for an ATM inverse multiplexing over ATM (IMA) group, use the ima clock-mode command in interface configuration mode. To remove the current configuration, use the no form of this command.
ima clock-mode {common port | independent}
no ima clock-mode
Syntax Description
Defaults
The default value is common. If no port is specified, the system automatically chooses an active link to provide clocking.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command controls the clock for the IMA group as a whole. If all the links in the group share a clock source, use the common keyword. If all the links use different clock sources, use the independent clock source keyword.
When the common keyword is set, the clock source ATM interface configuration command for the common link determines clocking for all the links in the group.When the independent keyword is set, the clock source ATM interface configuration command is used under each interface to determine clocking individually.
Because the system automatically chooses a replacement for the common link when it fails, any link in an IMA group potentially can provide the recovered transmit clock. For this reason, even when the common keyword is set with a specific link stipulated by the port value, you should use the ATM interface configuration clock source command to make sure that the clock source is configured correctly on each interface in the IMA group.
Examples
Cisco 2600, 3600, 7100, 7200, and 7500 series routers
The following example specifies that the links in IMA group 2 use a common clock source on link 0:
interface atm0/ima2ima clock-mode common 0Cisco 7600 series routers
The following example shows how to configure the links in IMA group 0 (on the SPA in slot 2, subslot 1) to use independent clock mode:
interface atm2/1/ima0ima clock-mode independentRelated Commands
ima differential-delay-maximum
To specify the maximum differential delay among the active links in an inverse multiplexing over ATM (IMA) group, use the ima differential-delay-maximum command in interface configuration mode. To restore the default setting, use the no form of this command.
ima differential-delay-maximum milliseconds
no ima differential-delay-maximum milliseconds
Syntax Description
Defaults
25 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command helps control latency in ATM-layer traffic by setting a limit on how much latency the slowest link in the group is allowed to introduce (a slower link has a longer propagation delay—for example, due to a longer path through the network or less accurate physical layer clocking—than other links). Setting a high value allows a slow link to continue operating as part of the group, although such a setting means there is added delay to links across the group. A low setting may result in less latency for traffic across the group than a high setting, but it can mean that the system takes a slow link out of operation, reducing total bandwidth.
When a link has been removed from service, it is automatically placed back in service when it meets the delay differential standard. If a link delay exceeds the specified maximum, the link is dropped; otherwise, the IMA feature adjusts for differences in delays so that all links in a group are aligned and carry ATM-layer traffic.
Examples
Cisco 2600, 3600, 7100, 7200, and 7500 series routers
The following example specifies that the links in IMA group 2 have a maximum differential delay of 50 ms:
interface atm0/ima2ima differential-delay-maximum 50Cisco 7600 series routers
The following example shows how to set the differential delay to 50 milliseconds for the links in IMA group 0 (on the SPA in chassis slot 2, SIP subslot 1):
interface atm2/1/ima0ima differential-delay-maximum 50Related Commands
show ima interface atm
Provides information about all configured IMA groups or a specific IMA group.
ima frame-length
To specify the number of cells in inverse multiplexing over ATM (IMA) frames, use the ima frame-length command in interface configuration mode. To remove the current setting and restore the default value, use the no form of this command.
ima frame-length {32 | 64 | 128 | 256}
no ima frame-length {32 | 64 | 128 | 256}
Syntax Description
32
Specifies a value of 32 cells.
64
Specifies a value of 64 cells.
128
Specifies a value of 128 cells.
256
Specifies a value of 256 cells.
Defaults
The default value is 128 cells in a frame.
Command Modes
Interface configuration
Command History
Usage Guidelines
IMA frames are numbered sequentially, and each contains an IMA Control Protocol (ICP) cell at a specific position. This command controls how often ICP cells are sent over the links in an IMA group. For example, with a frame length of 64, 1 out of every 64 cells on the link is an ICP cell.
Frame length can affect performance because the greater the total number of frames required to communicate a given number of cells, the greater the overhead for header and other control cells. In addition, shorter frame lengths might diminish performance when translated ATM-Frame Relay interworking occurs.
Examples
Cisco 7100 and 7200 series routers
The following example specifies that the links in IMA group 2 have a frame length of 64 cells:
interface atm 1/ima2ima frame-length 64Cisco 7600 series routers
The following example shows how to specify that the links in IMA group 0 on the SPA in slot 2, subslot 1, use a frame length of 256 cells:
interface atm2/1/ima0ima frame-length 256ima-group
To define inverse multiplexing over ATM (IMA) groups, use the ima-group command in interface configuration mode (Cisco 7100, 7200, and 7500 series routers), controller configuration mode (Cisco 7600 router), or config controller mode (Cisco HWIC-4SHDSL). To remove the group, use the no form of this command.
Cisco HWIC-4SHDSL
ima-group [shutdown | minimum-links number | clock-mode]
Cisco 7100, 7200, 7500, and 7600 series routers
ima-group group-number
no ima-group group-number
Syntax Description
Command Defaults
No IMA groups are defined.
Command Modes
Cisco HWIC-4SHDSL
Config controller
Config controller DSL group
Cisco 7100, 7200, and 7500 series routers
Interface configuration
Cisco 7600 series routers
Controller configuration
Command History
Usage Guidelines
For usage guidelines for using the clock-mode keyword, see the command reference page for the ima group clock-mode command.
Cisco HWIC-4SHDSL
Use the dsl-group command with the optional keyword ima to create an IMA DSL group and to enter config-controller-dsl-group mode. Use the ima group command to define the links as IMA group members.
Cisco 7100, 7200, and 7500 series routers
When the configuration is first performed or when the group number is changed, the interface is automatically disabled, moved to the new group, and then enabled.
Examples
Cisco HWIC-4SHDSL
The following example uses the dsl-group command to create an IMA group and enter config-controller-dsl-group mode on the Cisco HWIC-4SHDSL in a Cisco access router:
Router(config-controller)# dsl-group 1 pairs 0-1 imaRouter(config-controller-dsl-group)#Sep 26 11:43:55.798: %HWIC_SHDSL-5-DSLGROUP_UPDOWN: SHDSL 0/2/0 dsl-group(1) state changed to down.Sep 26 11:43:57.798: %LINK-3-UPDOWN: Interface ATM0/2/IMA1, changed state to downSep 26 11:43:58.798: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/2/IMA1, changed state to downRouter (config-controller-dsl-group)# ?dsl-group configuration sub commands:default Set a command to its defaultsexit Exit dsl-group sub commandsima IMA sub commandsno Negate a command or set its defaultsshdsl Symmetric g.shdsl configurationshutdown Shutdown this dsl-groupRouter (config-controller-dsl-group)# ima ?group IMA group configurationlink IMA link configurationRouter (config-controller-dsl-group)# ima group ?clock-mode IMA group clock mode configurationminimum-links Minimum number of active links for group UPshutdown IMA group shutdownCisco 7100, 7200, and 7500 series routers
The following example assigns interface 1 on the ATM module in slot 0 to a member of IMA group 2:
interface atm0/1ima-group 2Cisco 7600 series routers
The following example shows how to create IMA group 0 and add T1 interfaces 2/1/0, 2/1/1, and 2/1/2 to the group. These interfaces represent the T1 links attached to ports 0, 1, and 2 of the SPA in subslot 1 of the SPA interface processor (SIP) in chassis slot 2.
controller t1 2/1/0ima-group 0exitcontroller t1 2/1/1ima-group 0exitcontroller t1 2/1/2ima-group 0exitRelated Commands
ima restart
To manually restart an IMA group, issue the ima restart command in interface configuration mode on the IMA interface that represents the IMA group you want to restart.
ima restart
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration (IMA interface)
Command History
Usage Guidelines
If an IMA group stops operating correctly (for example, due to a link or configuration failure), you must restart the group once the problem has been corrected. This command provides a way to manually restart an IMA group. Issue the command on the IMA interface that represents the group you want to restart.
When you issue this command, the IMA group attempts to re-establish the IMA protocol (synchronize) with the remote end.
Examples
The following example shows how to restart IMA for group 0 on the SPA installed in slot 2, subslot 1:
interface atm2/1/ima0ima restartRelated Commands
ima autorestart
Specifies how IMA groups should sync up with remote groups after a restart.
ima test
To specify an interface and test pattern for verifying connectivity of all links in an inverse multiplexing over ATM (IMA) group, use the ima test command in interface configuration mode. To stop the test, use the no form of this command.
Cisco 2600, 3600, 7100, 7200, and 7500 series router
ima test [link port] [pattern pattern-id]
no ima test [link port] [pattern pattern-id]
Cisco 7600 series router
ima test [link link number] [pattern pattern]
no ima test [link link number] [pattern pattern]
Syntax Description
Defaults
There is no default for the port value. The default value for pattern-id is 106 (0x6A).
Command Modes
Interface configuration
Command History
Usage Guidelines
To verify link and group connectivity, the pattern is sent from the specified link and looped back from the receiving end across all links belonging to the group as defined at the remote end. Verifying link and group connectivity can help you to troubleshoot physical link connectivity or configuration problems at the remote end. The local end verifies that the pattern is returned on all links belonging to the group at the local end, and testing is continuous. An IMA control protocol (ICP) cell in each frame identifies the pattern.
When a link is not transmitting or receiving a pattern correctly, the command reports the link number where the problem exists.
Examples
Cisco 2600, 3600, 7100, 7200, and 7500 series routers
The following example configures link 4 to send test pattern 56:
interface atm 0/ima 2ima test link 2 pattern 56Cisco 7600 series routers
The following example shows how to configure IMA to send the test pattern 255 (0xFE) over link 4 in IMA group 0:
interface atm2/1/ima0ima test link 4 pattern 0xFERelated Commands
show ima interface atm
Provides information about all configured IMA groups or a specific IMA group.
ima version
To specify which version of inverse multiplexing over ATM (IMA) to use, issue the ima version command in interface configuration mode. Use the no form of the command to revert to the default value.
ima version {1.0 | 1.1}
no ima version
Syntax Description
Defaults
The default is version 1.1.
Command Modes
Interface configuration (IMA interface)
Command History
Usage Guidelines
Use this command in interface configuration mode on the IMA interface that represents the IMA group that you are configuring for operation.
Examples
The following example shows how to select IMA version 1.0 for IMA group 0 on the SPA installed in chassis slot 2, SIP subslot 1:
interface atm2/1/ima0ima version 1.0Related Commands
show ima interface atm
Provides information about all configured IMA groups or a specific IMA group.
inarp
To configure the Inverse Address Resolution Protocol (ARP) time period for an ATM permanent virtual circuit (PVC), virtual circuit (VC) class, or VC bundle, use the inarp command in the appropriate command mode. To restore the default Inverse ARP time period behavior, use the no form of this command.
inarp minutes
no inarp minutes
Syntax Description
Defaults
15 minutes
Command Modes
Interface-ATM-VC configuration (for an ATM PVC)
VC-class configuration (for a VC class)
Bundle configuration (for a VC bundle)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)Command History
Usage Guidelines
This command is supported for aal5snap encapsulation only when Inverse ARP is enabled. Refer to the encapsulation command for configuring aal5snap encapsulation and the protocol command for enabling Inverse ARP.
If the inarp command is not explicitly configured on an ATM PVC, the PVC inherits the following default configuration (listed in order of precedence):
•
•
•
•
Note
For ATM VC bundle management, the Inverse ARP parameter can only be enabled at the bundle level and applied to all VC members of the bundle—that is, it cannot be enabled in bundle-vc configuration mode for individual VC bundle members. To use this command in bundle configuration mode, first enter the bundle command to create the bundle and enter bundle configuration mode.
Examples
The following example sets the Inverse ARP time period to 10 minutes:
inarp 10Related Commands
inarp-vc
To enable Inverse Address Resolution Protocol (InARP) for a permanent virtual circuit (PVC) bundle member, use the inarp-vc command in ATM VC bundle-member configuration mode. To disable InARP for a PVC bundle member, use the no form of this command.
inarp-vc
no inarp-vc
Syntax Description
This command has no arguments or keywords.
Command Default
InARP is disabled for the PVC bundle member.
Command Modes
ATM VC bundle-member configuration
Command History
12.4(4)T
This command was introduced.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
Usage Guidelines
You can use this command only when using the quality of service (QoS) groups method for selecting the PVC bundle members. When InARP is enabled for a PVC bundle member, InARP requests are sent and are expected to be received on the PVC bundle member, and InARP replies are expected to be received on the PVC bundle member.
Examples
The following example associates QoS group 1 with a PVC bundle member and enables InARP on the PVC bundle member:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 2/0Router(config-subif)# bundle ciscoRouter(config-if-atm-bundle)# selection-method qos-groupRouter(config-if-atm-bundle)# pvc 1/32Router(config-if-atm-member)# qos-group 1Router(config-if-atm-member)# inarp-vcRouter(config-if-atm-member)# endRelated Commands
qos-group (ATM VC bundle member)
Associates a QoS group or groups with a PVC bundle member.
selection-method
Specifies the method for selection of the PVC bundle member.
interface atm
To configure an ATM interface and enter interface configuration mode, use the interface atm command in global configuration mode.
interface atm interface-number[.subinterface-number {mpls | multipoint | point-to-point}]
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
The interface atm command enables you to define a subinterface for a specified type of ATM interface. The subinterface for the ATM interface is created the first time this command is issued with a specified subinterface number.
For the Cisco 7600 series routers, you must specify the interface ATM slot, bay, and port for the SIP400 or SIP200.
Examples
For physical ATM interface 3/0, the following command creates an ATM MPLS subinterface having subinterface number 1:
Router# interface atm 3/0.1 mplsFor a Cisco 7600 series router where the slot is 4, the bay is 3, and the port is 0, the command is:
Router# interface atm 4/3/0 mplsRelated Commands
interface atm ima
To configure an inverse multiplexing over ATM (IMA) group, use the interface atm ima global configuration command.
interface atm slot/imagroup-number
Syntax Description
Command Default
There are no IMA groups (only individual ATM links).
Command Modes
Global configuration
Command History
Usage Guidelines
If the group does not exist when the command is issued, the command automatically creates the group.
When a port is configured for IMA functionality, it no longer operates as an individual ATM link.
Specifying ATM links as members of a group by using the ima group interface command does not enable the group. You must use the interface atm ima command to create the group.
Examples
The following example configures IMA group 0 on the module in slot 1:
interface atm 1/ima0 ip address 10.18.16.121 255.255.255.192Related Commands
interface cbr
To specify the T1 or E1 constant bit rate interface on an ATM-CES port adapter, and to enter interface configuration mode, use the interface cbr command in global configuration mode.
interface cbr slot/port
Syntax Description
Command Default
None
Command Modes
Global configuration
Command History
Usage Guidelines
The ATM-CES port adapter has four T1 (1.544 Mbps) or four E1 (2.048 Mbps) ports (75- or 120-ohm) that can support both structured (N x 64 kbps) and unstructured ATM Forum-compliant circuit emulation services (CES), and one port that supports an OC-3 (155 Mbps) single-mode intermediate reach interface or a T3 (45 Mbps) or E3 (34 Mbps) standards-based ATM interface.
Examples
The following example specifies the first T1 or E1 port on the ATM-CES port adapter in slot 1:
interface cbr 1/0Related Commands
show ces interface cbr
Displays detailed CBR port information.
show interface cbr
Displays the information about the CBR interface on the ATM-CES port adapter.
keepalive-lifetime
To specify the duration that a keepalive message from a Multiprotocol over ATM server (MPS) is considered valid by the Multiprotocol over ATM client (MPC), use the keepalive-lifetime command in global configuration mode.
keepalive-lifetime seconds
Syntax Description
Defaults
The default is 35 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
The keepalive lifetime (MPS-p2) must be greater than or equal to three times the value of the keepalive time (MPS-p1). MPS-p1 specifies the frequency with which a keepalive message is sent from the MPS to the MPC.
Examples
The following example shows how to specify a keepalive lifetime of 60 seconds:
Router(config)# keepalive-lifetime 60Related Commands
keepalive-time
Specifies the keepalive time value for the MPS-p1 variable of an MPS.
keepalive-time
To specify the keepalive time value for the Multiprotocol over ATM (MPOA) server (MPS)-p1variable of an MPS, use the keepalive-time command in MPS configuration mode. To revert to the default value, use the no form of this command.
keepalive-time seconds
no keepalive-time seconds
Syntax Description
Defaults
The default keepalive time is 10 seconds.
Command Modes
MPS configuration
Command History
Examples
The following example shows how to set the keepalive time to 25 seconds:
Router(mpoa-server-config)# keepalive-time 25lane auto-config-atm-address
Note
To specify that the configuration server ATM address is computed by the Cisco automatic method, use the lane auto-config-atm-address command in interface configuration mode. To remove the previously assigned ATM address, use the no form of this command.
lane [config] auto-config-atm-address
no lane [config] auto-config-atm-address
Syntax Description
Defaults
No specific ATM address is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the config keyword is not present, this command causes the LANE server and LANE client on the subinterface to use the automatically assigned ATM address for the configuration server.
When the config keyword is present, this command assigns the automatically generated ATM address to the configuration server (LECS) configured on the interface. Multiple commands that assign ATM addresses to the LANE configuration server can be issued on the same interface to assign different ATM addresses to the configuration server. Commands that assign ATM addresses to the LANE configuration server include lane auto-config-atm-address, lane config-atm-address, and lane fixed-config-atm-address.
For a discussion of Cisco's method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to associate the LANE configuration server with the database named network1 and specifies that the configuration server's ATM address will be assigned by the Cisco automatic method:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config auto-config-atm-addressThe following example shows how to cause the LANE server and LANE client on the subinterface to use the automatically assigned ATM address to communicate with the configuration server:
Router(config)# interface atm 2/0.1Router(config-if)# ip address 172.16.0.4 255.255.255.0Router(config-if)# lane client ethernetRouter(config-if)# lane server-bus ethernet engRouter(config-if)# lane auto-config-atm-addressRelated Commands
lane bus-atm-address
Note
To specify an ATM address—and thus override the automatic ATM address assignment—for the broadcast and unknown server on the specified subinterface, use the lane bus-atm-address command in interface configuration mode. To remove the ATM address previously specified for the broadcast and unknown server on the specified subinterface and thus revert to the automatic address assignment, use the no form of this command.
lane bus-atm-address atm-address-template
no lane bus-atm-address [atm-address-template]
Syntax Description
Defaults
For the broadcast and unknown server, the default is automatic ATM address assignment.
Command Modes
Interface configuration
Command History
Usage Guidelines
When applied to a broadcast and unknown server, this command overrides automatic ATM address assignment for the broadcast and unknown server. When applied to a LANE client, this command gives the client the ATM address of the broadcast and unknown server. The client will use this address rather than sending LAN Emulation Address Resolution Protocol (LE ARP) requests for the broadcast address.
When applied to a selected interface, but with a different ATM address from what was used previously, this command replaces the broadcast and unknown server's ATM address.
ATM Addresses
A LANE ATM address has the same syntax as a network service access point (NSAP) (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
The values of the digits that are replaced by wildcards come from the automatic ATM assignment method.
In LANE, a prefix template explicitly matches the prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
In the Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
Examples
The following example shows how to use an ESI template to specify the part of the ATM address corresponding to the interface; the remaining values in the ATM address come from automatic assignment:
Router(config-if)# lane bus-atm-address ...0800.200C.1001.**The following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch; the remaining values in the ATM address come from automatic assignment:
Router(config-if)# lane bus-atm-address 45.000014155551212f.00.00...Related Commands
lane server-bus
Enables a LANE server and a broadcast and unknown server on the specified subinterface with the ELAN ID.
lane client
Note
To activate a LAN Emulation (LANE) client on the specified subinterface, use the lane client command in interface configuration mode. To remove a previously activated LANE client on the subinterface, use the no form of this command.
lane client {ethernet} [elan-name]
no lane client {ethernet} [elan-name]
Syntax Description
Defaults
No LANE clients are enabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
If a lane client command has already been used on the subinterface for a different ELAN, then the client initiates termination procedures for that ELAN and joins the new ELAN.
If you do not provide an elan-name value, the client contacts the server to find which ELAN to join. If you do provide an ELAN name, the client consults the configuration server to ensure that no conflicting bindings exist.
Examples
The following example shows how to enable an Ethernet LANE client on an interface:
Router(config-if)# lane client ethernetRelated Commands
lane client-atm-address
Specifies an ATM address—and thus overrides the automatic ATM address assignment—for the LANE client on the specified subinterface.
lane client flush
Note
To enable the flush mechanism of a LAN Emulation Client (LEC), use the lane client flush command in global configuration mode. To disable the flush mechanism of a LEC, use the no form of this command.
lane client flush
no lane client flush
Syntax Description
This command contains no arguments or keywords.
Defaults
All the LECs perform the LANE LE_FLUSH process by default.
Command Modes
Global configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.1(3)T and later releases, the lane client flush command will be hidden and will not be visible in the configuration.
Configuring the no lane client flush command on a Cisco networking device is recommended to prevent the initial packet drops during the establishment of LANE data direct virtual connection (VCC).
Use the no lane client flush command to keep LANE clients from sending LE_FLUSH messages to the remote LANE client. This configuration also allows the LANE clients to process the LE_FLUSH messages from the remote LANE clients.
Note
Examples
The following example shows how to disable the flush mechanism of a LEC:
Router(config)# no lane client flushRelated Commands
lane client mpoa client name
Note
To bind a LAN Emulation Client (LEC) to the named Multiprotocol over ATM client (MPC), use the lane client mpoa client name command in interface configuration mode. To unbind the named MPC from a LEC, use the no form of this command.
lane client mpoa client name mpc-name
no lane client mpoa client name mpc-name
Syntax Description
Defaults
No LEC is bound to a named MPC.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enter this command, the named MPC is bound to a LEC. The named MPC must exist before this command is accepted. If you enter this command before a LEC is configured (not necessarily running), a warning message is issued.
Examples
The following example shows how to bind a LEC on a subinterface to the MPC:
Router(config-if)# lane client mpoa client name ip_mpclane client mpoa server name
Note
To bind a LAN Emulation Client (LEC) with the named Multiprotocol over ATM server (MPS), use the lane client mpoa server name command in interface configuration mode. To unbind the server, use the no form of this command.
lane client mpoa server name mps-name
no lane client mpoa server name mps-name
Syntax Description
Defaults
No LEC is bound to a named MPS.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command binds a LEC to the named MPS. The specified MPS must exist before this command is accepted. If this command is entered when a LEC is not already configured (not necessarily running), a warning message will be issued.
Examples
The following example shows how to bind a LANE client with the MPS named MYMPS:
Router(config-if)# lane client mpoa server name MYMPS
lane client-atm-address
Note
To specify an ATM address—and thus override the automatic ATM address assignment—for the LAN Emulation (LANE) client on the specified subinterface, use the lane client-atm-address command in interface configuration mode. To remove the ATM address previously specified for the LANE client on the specified subinterface and thus revert to the automatic address assignment, use the no form of this command.
lane client-atm-address atm-address-template
no lane client-atm-address [atm-address-template]
Syntax Description
Defaults
Automatic ATM address assignment
Command Modes
Interface configuration
Command History
Usage Guidelines
Use of this command on a selected subinterface, but with a different ATM address from what was used previously, replaces the ATM address of the LANE client.
ATM Addresses
A LANE ATM address has the same syntax as a network service access point (NSAP) (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the ATM address prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
The Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
For a discussion of Cisco's method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to use an ESI template to specify the part of the ATM address corresponding to the interface; the remaining parts of the ATM address come from automatic assignment:
Router(config-if)# lane client-atm-address...0800.200C.1001.**The following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch; the remaining parts of the ATM address come from automatic assignment:
Router(config-if)# lane client-atm-address 47.000014155551212f.00.00...Related Commands
lane config database
Note
To associate a named configuration table (database) with the configuration server on the selected ATM interface, use the lane config database command in interface configuration mode. To remove the association between a named database and the configuration server on the specified interface, use the no form of this command.
lane config database database-name
no lane config database
Syntax Description
Defaults
No configuration server is defined, and no database name is provided.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid only on a major interface, not a subinterface, because only one LANE Configuration Server (LECS) can exist per interface.
The named database must exist before the lane config database command is used. Refer to the lane database command for more information.
Multiple lane config database commands cannot be used multiple times on the same interface. You must delete an existing association by using the no form of this command before you can create a new association on the specified interface.
Activating a LANE configuration server requires the lane config database command and one of the following commands: lane fixed-config-atm-address, lane auto-config-atm-address, or lane config-atm-address.
Examples
The following example shows how to associate the LECS with the database named network1 and to specify that the configuration server's ATM address will be assigned by the Cisco automatic method:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config auto-config-atm-addressRelated Commands
lane config-atm-address
Note
To specify a configuration server's ATM address explicitly, use the lane config-atm-address command in interface configuration mode. To remove an assigned ATM address, use the no form of this command.
lane [config] config-atm-address atm-address-template
no lane [config] config-atm-address atm-address-template
Syntax Description
Defaults
No specific ATM address or method is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
If the config keyword is not present, this command causes the LAN Emulation (LANE) server and LANE client on the subinterface to use the specified ATM address for the configuration server.
When the config keyword is present, this command adds an ATM address to the configuration server configured on the interface. A LECS can listen on multiple ATM addresses. Multiple commands that assign ATM addresses to the LECS can be issued on the same interface to assign different ATM addresses to the LECS.
ATM Addresses
A LANE ATM address has the same syntax as an NSAP (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the ATM address prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
In our implementation of LANE, the prefix corresponds to the switch prefix, the ESI corresponds to a function of the ATM interface's MAC address, and the selector field corresponds to the specific subinterface of the interface.
For a discussion of the Cisco method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to associate the LANE configuration server with the database named network1 and to explicitly specify the configuration server's ATM address:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config config-atm-address 39.020304050607080910111213.0800.AA00.3000.00The following example shows how to cause the LANE server and LANE client on the subinterface to use the explicitly specified ATM address to communicate with the configuration server:
Router(config)# interface atm 2/0.1Router(config-if)# ip address 172.16.0.4 255.255.255.0Router(config-if)# lane client ethernetRouter(config-if)# lane server-bus ethernet engRouter(config-if)# lane config-atm-address 39.020304050607080910111213.0800.AA00.3000.00Related Commands
lane database
Note
To create a named configuration database that can be associated with a configuration server, use the lane database command in global configuration mode. To delete the database, use the no form of this command.
lane database database-name
no lane database database-name
Syntax Description
Defaults
No name is provided.
Command Modes
Global configuration
Command History
Usage Guidelines
Use of the lane database command places you in database configuration mode, in which you can use the client-atm-address name, default name, mac-address name, name restricted, name unrestricted, name new-name, and name server-atm-address commands to create entries in the specified database. When you are finished creating entries, type ^Z or exit to return to global configuration mode.
Examples
The following example shows how to create the database named network1 and associates it with the configuration server on interface ATM 1/0:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(lane-config-dat)# default-name engRouter(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config auto-config-atm-addressRelated Commands
lane fixed-config-atm-address
Note
To specify that the fixed configuration server ATM address assigned by the ATM Forum will be used, use the lane fixed-config-atm-address command in interface configuration mode. To specify that the fixed ATM address will not be used, use the no form of this command.
lane [config] fixed-config-atm-address
no lane [config] fixed-config-atm-address
Syntax Description
Defaults
No specific ATM address or method is set.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the config keyword is not present, this command causes the LAN emulation (LANE) server and LANE client on the subinterface to use that ATM address, rather than the ATM address provided by the ILMI, to locate the configuration server.
When the config keyword is present, and the LECS is already up and running, be aware of the following scenarios:
•
•
•
•
•
When you use this command with the config keyword, and the LECS is a master, the master will listen on the fixed address. If you use this command when an LECS is not a master, the LECS will listen on this address when it becomes a master. If you do not use this command, the LECS will not listen on the fixed address.
Multiple commands that assign ATM addresses to the LECS can be issued on the same interface in order to assign different ATM addresses to the LECS. Commands that assign ATM addresses to the LECS include lane auto-config-atm-address, lane config-atm-address, and lane fixed-config-atm-address. The lane config database command and at least one command that assigns an ATM address to the LECS are required to activate a LECS.
Examples
The following example shows how to associate the LECS with the database named network1 and how to specify that the configuration server's ATM address is the fixed address:
Router(config)# lane database network1Router(lane-config-dat)# name eng server-atm-address 39.020304050607080910111213.0800.AA00.1001.02Router(lane-config-dat)# name mkt server-atm-address 39.020304050607080910111213.0800.AA00.4001.01Router(config)# interface atm 1/0Router(config-if)# lane config database network1Router(config-if)# lane config fixed-config-atm-addressThe following example shows how to cause the LANE server and LANE client on the subinterface to use the fixed ATM address to communicate with the configuration server:
Router(config)# interface atm 2/0.1Router(config-if)# ip address 172.16.0.4 255.255.255.0Router(config-if)# lane client ethernetRouter(config-if)# lane server-bus ethernet engRouter(config-if)# lane fixed-config-atm-addressRelated Commands
lane fssrp
Note
To enable the special LANE features such that LANE components (such as the LANE Configuration Server, the LANE client, the LANE server, and the BUS) become aware of the Fast Simple Server Redundancy Protocol (FSSRP), use the lane fssrp command in interface configuration mode. To disable the LANE FSSRP configuration, use the no form of this command.
lane fssrp
no lane fssrp
Syntax Description
This command contains no arguments or keywords.
Defaults
FSSRP is not enabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must execute this command on all ATM interfaces to enable FSSRP capability for all LANE components on that interface and hence all its subinterfaces.
Examples
The following example shows how to enable FSSRP on an ATM interface:
Router(config-if)# lane fssrpRelated Commands
lane global-lecs-address
Note
To specify a list of LAN Emulation Configuration Server (LECS) addresses to use when the addresses cannot be obtained from the Interim Local Management Interface (ILMI), use the lane global-lecs-address command in interface configuration mode. To remove a LECS address from the list, use the no form of this command.
lane global-lecs-address address
no lane global-lecs-address address
Syntax Description
Defaults
No addresses are configured. The router obtains LECS addresses from the ILMI.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command when your ATM switches do not support the ILMI list of LECS addresses and you want to configure Simple Server Redundancy. This command will simulate the list of LECS addresses, as if they had been obtained from the ILMI. Use this command with a different address for each LECS. The order they are used determines their priority. You should enter the addresses in the same order as you would on the ATM switch.
Note
If your switches do support ILMI, this command forces the router to use the addresses specified and will not use the ILMI to obtain the LECS addresses. Because the well-known LECS address is always used as a last resort LECS address, you cannot use the address in this command.
lane le-arp
Note
To add a static entry to the LAN Emulation Address Resolution Protocol (LE ARP) table of the LANE client configured on the specified subinterface, use the lane le-arp command in interface configuration mode. To remove a static entry from the LE ARP table of the LANE client on the specified subinterface, use the no form of this command.
lane le-arp {mac-address | route-desc segment segment-number bridge bridge-number} atm-address
no lane le-arp {mac-address | route-desc segment segment-number bridge bridge-number} atm-address
Syntax Description
Defaults
No static address bindings are provided.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command adds or removes a static entry binding a MAC address or segment number and bridge number to an ATM address. It does not add or remove dynamic entries. Removing the static entry for a specified ATM address from a LE ARP table does not release data direct VCCs established to that ATM address. However, clearing a static entry clears any fast-cache entries that were created from the MAC address-to-ATM address binding.
Static LE ARP entries are neither aged nor removed automatically.
To remove dynamic entries from the LE ARP table of the LANE client on the specified subinterface, use the clear lane le-arp command.
Examples
The following example shows how to add a static entry to the LE ARP table:
Router(config-if)# lane le-arp 0800.aa00.0101 47.000014155551212f.00.00.0800.200C.1001.01The following example shows how to add a static entry to the LE ARP table binding segment number 1, bridge number 1 to the ATM address:
Router(config-if)# lane le-arp route-desc segment 1 bridge 1 39.020304050607080910111213.00000CA05B41.01Related Commands
clear lane le-arp
Forces a LANE server to drop a client and allow the LANE configuration server to assign the client to another ELAN.
lane server-atm-address
Note
To specify an ATM address—and thus override the automatic ATM address assignment—for the LAN emulation (LANE) server on the specified subinterface, use the lane server-atm-address command in interface configuration mode. To remove the ATM address previously specified for the LANE server on the specified subinterface and thus revert to the automatic address assignment, use the no form of this command.
lane server-atm-address atm-address-template
no lane server-atm-address [atm-address-template]
Syntax Description
Defaults
For the LANE server, the default is automatic address assignment; the LANE client finds the LANE server by consulting the configuration server.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command also instructs the LANE client configured on this subinterface to reach the LANE server by using the specified ATM address instead of the ATM address provided by the configuration server.
When used on a selected subinterface, but with a different ATM address than was used previously, this command replaces the ATM address of the LANE server.
ATM Addresses
A LANE ATM address has the same syntax as an network service access point (NSAP) (but it is not a network-level address). It consists of the following:
•
–
–
–
–
–
–
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the prefix, but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field, but uses wildcards for the prefix and selector.
In the Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
For a discussion of the Cisco method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter of the Cisco IOS Switching Services Configuration Guide.
Examples
The following example shows how to used an ESI template to specify the part of the ATM address corresponding to the interface; the remaining parts of the ATM address come from automatic assignment:
Router(config-if)# lane server-atm-address ...0800.200C.1001.**The following example shows how to use a prefix template to specify the part of the ATM address corresponding to the switch; the remaining part of the ATM address come from automatic assignment:
Router(config-if)# lane server-atm-address 45.000014155551212f.00.00...Related Commands
lane server-bus
Enables a LANE server and a BUS on the specified subinterface with the ELAN ID.
lane server-bus
Note
To enable a LAN emulation (LANE) server and a broadcast and unknown server (BUS) on the specified subinterface with the emulated LAN (ELAN) ID, use the lane server-bus command in interface configuration mode. To disable a LANE server and BUS on the specified subinterface, use the no form of this command.
lane server-bus {ethernet} elan-name [elan-id id]
no lane server-bus {ethernet} elan-name [elan-id id]
Syntax Description
Defaults
No LAN type or ELAN name is provided.
Command Modes
Interface configuration
Command History
Usage Guidelines
The LANE server and the BUS are located on the same router.
If a lane server-bus command has already been used on the subinterface for a different ELAN, the server initiates termination procedures with all clients and comes up as the server for the new ELAN.
To participate in MPOA, a LEC must have an ELAN ID. This command enables the LEC to get the ELAN ID from the LES when the LEC bypasses the LECS phase.
Caution
specified in the LECS for the same ELAN.
The LEC can also obtain the ELAN ID from the LECS by using the name elan-id command.
Examples
The following example shows how to enable a LANE server and BUS for an Ethernet ELAN named MYELAN:
Router(config-if)# lane server-bus ethernet myelanRelated Commands
logging event atm pvc state
To enable notification of ATM permanent virtual circuit (PVC) state changes, use the logging event atm pvc state command in interface configuration mode. To disable notification, use the no form of this command.
logging event atm pvc state
no logging event atm pvc state
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
For monitoring purposes, this command can be used to log the state changes for all PVCs associated with an ATM interface.
Examples
The following example shows how to enable notification of ATM PVC state changes:
Router(config-if)# logging event atm pvc stateRelated Commands
loopback
To loop packets back to the interface for testing, use the loopback interface configuration command with or without an optional keyword. To remove the loopback, use the no form of this command.
Cisco 2600 and 3600 Series
loopback [line | local | payload | remote]
no loopback [line | local | payload | remote]
Cisco 7100, 7200, and 7500 Series
For T1 lines:
loopback {diagnostic | local {payload | line} | remote {iboc | esf {payload | line}}}
For E1 lines:
loopback {diagnostic | local {payload | line}}
no loopback
Syntax Description
Defaults
The interface is placed into external loopback mode at the line, and loopback is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can use a loopback test on lines to detect and distinguish equipment malfunctions caused either by line and channel service unit/digital service unit (CSU/DSU) or by the interface. If correct data transmission is not possible when an interface is in loopback mode, the interface is the source of the problem.
The local loopback does not generate any packets automatically. Instead, the ping command is used.
Examples
The following example sets up local loopback diagnostics:
interface atm 1/0 loopback localloopback (ATM)
To configure the ATM interface into loopback mode, use the loopback interface configuration command. To remove the loopback, use the no form of this command.
loopback [cell | line | payload]
no loopback [cell | line | payload]
Syntax Description
Defaults
The interface is placed into external loopback at the line.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is useful for testing because it loops all packets from the ATM interface back to the interface as well as directing the packets to the network.
Use the loopback line command to check that the PA-A3 port adapter is working by looping the receive data back to the transmit data.
Examples
The following example loops all packets back to the ATM interface:
interface atm 4/0loopbackRelated Commands
