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.

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.

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.

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.

Usage Guidelines

Note	To configure Integrated Local Management Interface (ILMI), Quasi Signaling Application Adaptation Layer (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 configured, aal5snap might be the appropriate choice. If pricing depends on the number of bytes transmitted, aal5mux might be the appropriate choice because it has a slightly lower transmission rate. Use the aal5mux pppoe option to reduce SNAP encapsulation bandwidth usage associated with carrying PPPoE frames. Use the aal5mux bridge ieee8023 option to reduce SNAP encapsulation bandwidth usage associated with carrying bridged frames.

Encapsulation for PPPoA

When you configure 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 with 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	Do not use this command on a router that initiates PPPoA sessions.

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):

• Configuration of the encapsulation command in a VC class assigned to the PVC, PVC bundle, or SVC itself.

• Configuration of the encapsulation command in a VC class assigned to the ATM subinterface of the PVC, SVC, or VC bundle.

• Configuration of the encapsulation command in a VC class assigned to the ATM main interface of the PVC, SVC, or VC bundle.

• Global encapsulation option default: aal5snap.

Note	When a VC is a member of a VC bundle, bundle configuration takes precedence over configuration using the encapsulation command in VC-class mode.

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:

• encapsulation aal5ciscoppp

• encapsulation aal5mux

• encapsulation aal5snap

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:

• For Layer 2 local switching, you must add the l2transport keyword to the pvc command. The l2transport keyword enables the PVC to transport Layer 2 packets.

• The Layer 2 local switching encapsulation command works only with the pvc command. You cannot create switched virtual circuits or VC bundles to transport Layer 2 packets. You can use only PVCs to transport Layer 2 packets.

The table below shows the encapsulation types supported for each transport type:

Usage Guidelines

Use the encapsulation priority-tagged command to set the VLAN identifier (VLAN ID) of an 802.1Q Ethernet frame to zero to enable the frame to be processed as per the 802.1P priority bits configured in the 802.1Q Ethernet frame header. Use the encapsulation priority-tagged native command to configure the subinterface with the VLAN ID set to zero as a native VLAN, which can receive both tagged and untagged frames but transmit only untagged frames. Use the encapsulation priority-tagged native tx-tagged command to enable the VLAN 0 native subinterface to transmit only priority tagged frames.

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.

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.

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):

• Configuration of the idle-timeout command in a VC class assigned to the SVC.

• Configuration of the idle-timeout command in a VC class assigned to the SVC’s ATM subinterface.

• Configuration of the idle-timeout command in a VC class assigned to the SVC’s ATM main interface.

• Global default--The global idle timeout default is the value set using the idle-timeout command. If the idle-timeout command is not configured, the default idle timeout is 300 seconds, and the minimum-rate is 0 kbps.

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):

• Configuration of the ilmi manage command in a VC class assigned to the PVC itself.

• Configuration of the ilmi manage command in a VC class assigned to the PVC’s ATM subinterface.

• Configuration of the ilmi manage command in a VC class assigned to the PVC’s ATM main interface.

• Global default: ILMI management is disabled.

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.

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:

• If auto restart is disabled (the default), IMA learns the ID of the remote group each time a restart occurs. In this case, the remote IMA group ID might change between restarts.

• If auto restart is enabled, you can specify which remote IMA group the local group should synchronize with. This allows you to keep an IMA group from synchronize with any group ID.

Include IMA group IDs in the command line to specify how IMA groups are to synchronize:

• If you specify near-end-id only, the local IMA group learns the ID of the remote group to synchronize with (which will be the first remote IMA group to become active). This learned remote group ID remains active until the SPA is reloaded.

• If you specify both near-end-id and far-end-id , the local IMA group will only synchronize with this remote IMA group. Both the near-end and far-end IDs must be the same.

To see the current settings for auto restart, issue the show ima interface command and view the Auto-Restart section of the command output.

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.

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.

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.

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.

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.

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.

Usage Guidelines

Use this command in interface configuration mode on the IMA interface that represents the IMA group that you are configuring for operation.

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):

• Configuration of the inarp command in a VC class assigned to the PVC itself.

• Configuration of the inarp command in a VC class assigned to the PVC’s ATM subinterface.

• Configuration of the inarp command in a VC class assigned to the PVC’s ATM main interface.

• Global default for the minutes argument is 15 minutes; this default assumes that Inverse ARP is enabled.

Note	As the inheritance rules imply, when a VC is a member of a VC bundle, configuration using the inarp command in VC-class configuration mode no longer applies to that VC. Bundle configuration takes precedence.

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.

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.

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.

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.

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.

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.

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:

• A 13-byte prefix that includes the following fields defined by the ATM Forum:

  • AFI (Authority and Format Identifier) field (1 byte)
  • DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)
  • DFI field (Domain Specific Part Format Identifier) (1 byte)
  • Administrative Authority field (3 bytes)
  • Reserved field (2 bytes)
  • Routing Domain field (2 bytes)
  • Area field (2 bytes)

• A 6-byte ESI

• A 1-byte selector field

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.

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.

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	Configuring the no lane client flush command on a Cisco networking device does not guarantee the orderly delivery of incoming packets. There is a chance of receiving out-of-order packets at the destination during the establishment of a LANE data direct VCC.

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.

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.

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:

• A 13-byte prefix that includes the following fields defined by the ATM Forum:

  • AFI (Authority and Format Identifier) field (1 byte)
  • DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)
  • DFI field (Domain Specific Part Format Identifier) (1 byte)
  • Administrative Authority field (3 bytes)
  • Reserved field (2 bytes)
  • Routing Domain field (2 bytes)
  • Area field (2 bytes)

• A 6-byte ESI

• A 1-byte selector field

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 .

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 .

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:

• A 13-byte prefix that includes the following fields defined by the ATM Forum:

  • AFI (Authority and Format Identifier) field (1 byte)
  • DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)
  • DFI field (Domain Specific Part Format Identifier) (1 byte)
  • Administrative Authority field (3 bytes)
  • Reserved field (2 bytes)
  • Routing Domain field (2 bytes)
  • Area field (2 bytes)

• A 6-byte ESI

• A 1-byte selector field

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 .

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.

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:

• If you configure the LECS with only the well-known address, the LECS will not participate in the SSRP, will act as a standalone primary, and will listen only on the well-known LECS address. This scenario is ideal if you want a standalone LECS that does not participate in SSRP, and you would like to listen to only the well-known address.

• If only the well-known address is already assigned, and you assign at least one other address to the LECS (additional addresses are assigned using the lane auto-config-atm-address command or the lane config-atm-address command ), the LECS will participate in the SSRP and act as the primary or subordinate based on the normal SSRP rules. This scenario is ideal if you would like the LECS to participate in SSRP, and you would like to make the primary LECS listen on the well-known address.

• If the LECS is participating in SSRP, has more than one address (one of which is the well-known address), and all the addresses but the well-known address are removed, the LECS will declare itself the primary and stop participating in SSRP completely.

• If the LECS is operating as an SSRP subordinate, and it has the well-known address configured, it will not listen on the well-known address unless it becomes the primary.

• If you want the LECS to assume the well-known address only when it becomes the primary, configure the LECS with the well-known address and at least one other address.

When you use this command with the config keyword, and the LECS is primary, the primary will listen on the fixed address. If you use this command when an LECS is not a primary, the LECS will listen on this address when it becomes a primary. 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.

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.

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	You must configure the same list of addresses on each interface that contains a LAN emulation (LANE) entity.

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.

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.

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:

• A 13-byte prefix that includes the following fields defined by the ATM Forum:

  • AFI (Authority and Format Identifier) field (1 byte)
  • DCC (Data Country Code) or ICD (International Code Designator) field (2 bytes)
  • DFI field (Domain Specific Part Format Identifier) (1 byte)
  • Administrative Authority field (3 bytes)
  • Reserved field (2 bytes)
  • Routing Domain field (2 bytes)
  • Area field (2 bytes)

• A 6-byte ESI

• A 1-byte selector field

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 .

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

If an ELAN ID is supplied, make sure that it corresponds to the same ELAN ID value 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.

Usage Guidelines

For monitoring purposes, this command can be used to log the state changes for all PVCs associated with an ATM interface.