Configuring LAN Emulation

This chapter describes LAN Emulation (LANE) and how to configure it on the LightStream 1010 ATM switch. The LANE connection can only be used to manage the ATM switch.

For definitions of all commands discussed in this chapter, refer to the LightStream 1010 ATM Switch Command Reference publication.

Note Most examples in this chapter describe configuration of the ATM Switch Processor (ASP) in a LightStream 1010 ATM switch chassis. If the ASP is installed in the Catalyst 5500 switch chassis, the CPU Ethernet interface will be 13/0/0 instead of 2/0/0.

This chapter contains the following sections:

How it Works

The ATM Forum defined the LANE specification to allow legacy LAN users to take advantage of ATM's benefits without requiring modifications to end station hardware or software. LANE makes an ATM interface look like one or more separate Ethernet or Token Ring interfaces.

LANE uses ATM as a backbone to interconnect existing legacy LANs. Multiple emulated LANs (ELANs), which are logically separated, can share the same physical ATM network and the same physical ATM interface.

LANE services provide connectivity between ATM-attached devices and LAN-attached devices. Two primary applications that use the LANE protocol are:

Connectivity between LAN-attached stations across an ATM network, effectively extending LANs over a high-speed ATM transport backbone.
Connectivity between ATM-attached hosts and LAN-attached hosts. Centralized hosts with high-speed ATM port adapters provide services, such as Domain Name System (DNS), to traditional LAN-attached devices.

Figure 14-1: LANE Concept

ATM is a connection-oriented service, while LAN is a broadcast medium. ATM uses connection-oriented service with point-to-point signaling or multipoint signaling between source and destination devices. LAN-based protocol suites use connectionless service and broadcasts so yjsy source devices can find one or more destination devices.

Using LANE, LAN broadcasts are emulated as ATM unicasts. LANE emulates a broadcast environment such as IEEE 802.3 Ethernet or 802.5 Token Ring on top of an ATM network that is a point-to-point environment. Client devices, such as routers, ATM workstations, and LAN switches use LES functions to emulate a LAN across ATM.

LANE defines a service interface for network layer protocols that is identical to existing MAC layers. No changes are required to existing upper layer protocols and applications. Data sent across the ATM network is encapsulated in the appropriate LAN MAC packets. LANE essentially bridges LAN traffic across ATM and defines the operation of an emulated LAN.

LANE does not emulate every particular physical or data-link characteristic. For example, it does not support carrier sense multiple access collision detect (CSMA/CD) for either Ethernet or Token Ring. LANE on the LightStream 1010 ATM switch supports only the IP protocol.

LANE can be implemented on the following devices:

Directly attached ATM hosts
Layer 2 devices, such as the Catalyst switches or LightStream 1010 ATM switches
Layer 3 devices, such as routers

Figure 14-2 shows the LANE protocol stack used between these devices.

Figure 14-2: LANE Protocol Stack

The LANE version 1 standard defines separate ELANs for Ethernet and Token Ring, but does not explicitly define how to connect the two types directly. An ATM equipped router, such as the Cisco 7000 with an ATM interface processor (AIP), acting as an LEC on each ELAN, can provide this connectivity while allowing the administrator to construct firewalls or to filter traffic between ELANs.

LANE Servers and Components

A single emulated LAN consists of the following components:

LANE client (LEC)---An entity in an endpoint such as a workstation, LAN switch, or router that performs data forwarding and receiving, address resolution, and other control functions for a single endpoint in a single emulated LAN. The LANE client provides a standard LAN service to any higher layers that interface to it. A router or switch can have multiple resident LANE clients, each connecting with different emulated LANs. The LANE client registers its MAC and ATM address with the LES.

Note In Token Ring environments, a LANE client configured for source-route bridging may register a route descriptor with the LES.

LANE configuration server (LECS)---A server that assigns individual clients to particular emulated LANs by directing them to the LES that corresponds to the emulated LAN. The LECS maintains a database of LANE client ATM or MAC addresses and their emulated LANs. An LECS can serve multiple emulated LANs, but there must be one LECS configured for each LANE cloud. The LECS can also be used for security by restricting ELAN membership to certain LECs based on their MAC addresses.
LANE server (LES)---A server that provides a registration facility for clients to join the emulated LAN. Each emulated LAN has one Cisco LES, which handles LAN Emulation Address Resolution Protocol (LE_ARP) requests and maintains a list or look-up table of LAN destination MAC addresses.

Note In Token Ring LANE environments, the LES maintains a list of route descriptors.

Broadcast-and-unknown server (BUS)---A server that floods unknown destination traffic and forwards multicast and broadcast traffic to clients within an emulated LAN. One Cisco BUS exists per emulated LAN.

These servers could be single points of failure in a LANE, but Cisco has developed a fault tolerance mechanism known as simple server redundancy that eliminates these single points of failure. Although this scheme is proprietary, no new protocol additions have been made to the LANE subsystems, which are described in the section "Configuring Fault-Tolerant Operation" later in this chapter.

Emulated LAN entities can coexist on one or more Cisco routers or Catalyst switches such as the Catalyst 5000 series. On Cisco routers, each LES and BUS is always a single entity.

Comparing VLANs and ELANs

In the Catalyst family of switches, a virtual LAN (VLAN) is a logical group of end stations, independent of physical location, with a common set of requirements. Currently, the Catalyst switches support a port-centric VLAN configuration. The VLAN number is only significant to the Catalyst family of switches.

On an ATM network, an emulated LAN is called an ELAN and is designated by a name. You can configure some ELANs from a router and some from a Catalyst switch. You can also configure ELANs with unrestricted membership and some with restricted membership. You can also configure a default ELAN for LECs that do not specify an ELAN name during the join request.

To create a VLAN that spans multiple Catalyst switches on an ATM network, you must assign the VLAN on each Catalyst switch to the same ELAN. Use the lane client ethernet vlan_num elan_name command to link the VLAN number with the ELAN name. You must use a router to allow communication between two or more ELANs, whether they are on the same or different Catalyst switches.

LANE VCC Connection Types

Communication among LANE components is ordinarily handled by several types of switched virtual channel circuits (VCCs). Some VCCs are unidirectional; others are bidirectional. Some are point-to-point; others are point-to-multipoint. Figure 14-3 illustrates the various types of VCCs followed by a description of each.

Figure 14-3: LANE Virtual Circuit Types

Control direct VCC---The LEC, as part of its initialization, sets up a bi-directional point-to-point VCC to the LES for sending or receiving control traffic. The LEC is required to accept control traffic from the LES through this VCC and must maintain the VCC while participating as a member of the emulated LAN.

Control distribute VCC---The LES may optionally set up a unidirectional VCC back to the LEC for distributing control traffic. Whenever an LES cannot resolve an LE_ARP request from an LEC, it forwards the request out the control distribute VCC to all of the clients in the LAN. The control distribute VCC enables information from the LES to be received whenever a new MAC address joins the LAN or whenever the LES cannot resolve an LE_ARP request.

Data direct VCC---Once an ATM address has been resolved by a LEC, this bidirectional point-to-point VCC is set up between clients that want to exchange unicast data traffic. Most client traffic travels via these VCCs.

Multicast send VCC---The LEC sets up a unidirectional point-to-point VCC to a multicast server. This VCC is used by the LEC to sends multicast traffic to the BUS for forwarding out the multicast forward VCC. The LEC also sends out unicast data on this VCC until it resolves the ATM address of a destination.

Multicast forward VCC---The BUS sets up a unidirectional VCC to the LECs for distributing data from the BUS. This can either be a unidirectional point-to-point or unidirectional point-to-multipoint VCC. Data sent by an LEC over the multicast send VCC is forwarded to all LEC's via the multicast forward VCC.

Configure direct VCC---This is a transient VCC which is set up by the LEC to the LECS in order to obtain the LES ATM address which controls a particular LAN that the LEC wishes to join.

Joining an ELAN

The following process (see Figure 14-3) normally occurs after an LEC has been allowed to join an ELAN:

Step 1 The LEC requests to join an ELAN.

The LEC sets up a connection to the LECS (bidirectional, point-to-point configure direct VCC, link 1-7 in Figure 14-3) to find the ATM address of the LES for its ELAN.

The LEC finds the LECS by using the following interface and addresses in the listed order:

Locally configured ATM address
ILMI from directly attached ATM switch
The well-known address defined by the ATM Forum

Step 2 The LECS identifies the LES.

Using the same VCC, the LECS returns the ATM address and the name of the LES for the LEC ELAN.

Step 3 The LEC tears down configure direct VCC.

Step 4 The LEC contacts the LES for its ELAN.

The LEC sets up a connection to the LES for its ELAN (bidirectional, point-to-point control direct VCC, link 1-7 in Figure 14-3) to exchange control traffic.

When a control direct VCC is established between an LEC and an LES, it remains established.

Step 5 The LES verifies that the LEC is allowed to join the ELAN.

The LES for the ELAN sets up a connection to the LECS to verify that the LEC is allowed to join the ELAN (bidirectional, point-to-point server configure VCC, link 11-12 in Figure 14-3). The LES configuration request contains the LEC MAC address, its ATM address, and the name of the ELAN. The LECS checks its database to determine whether the LEC can join that ELAN; then it uses the same VCC to inform the LES whether or not the LEC is allowed to join.

Step 6 The LES allows or does not allow the LEC to join the ELAN.

If allowed, the LES adds the LEC to the unidirectional, point-to-multipoint control distribute VCC (link 2-8 in Figure 14-3) and confirms the join over the bidirectional, point-to-point control direct VCC (link 1-7 in Figure 14-3).

If not allowed, the LES rejects the join over the bidirectional, point-to-point control direct VCC (link 1-7 in Figure 14-3).

Step 7 The LEC sends LE_ARP packets for the broadcast address, which is all 1s.

Sending LE_ARP packets for the broadcast address returns the ATM address of the BUS. Then the LEC sets up the multicast send VCC (link 4-9 in Figure 14-3), and the BUS adds the LEC to the multicast forward VCC (link 5-10 in Figure 14-3) to and from the BUS.

Resolving ELAN Addressing

As communication occurs on the ELAN, each LEC dynamically builds an LE_ARP table. An LEC LE_ARP table can also have static, preconfigured entries. The LE_ARP table maps MAC addresses to ATM addresses.

Note LE_ARP is not the same as IP ARP. IP ARP maps IP addresses (Layer 3) to Ethernet MAC addresses (Layer 2); LE_ARP maps LECMAC addresses (Layer 2) to ATM addresses (also Layer 2).

When an LEC first joins an ELAN, its LE_ARP table has no dynamic entries, and the LEC has no information about destinations on or behind its ELAN. To learn about a destination when a packet is to be sent, the LEC begins the following process to find the ATM address corresponding to the known MAC address:

Step 1 The LEC sends an LE_ARP request to the LES for this ELAN (point-to-point control direct VCC, link 1-7 in Figure 14-3).

Step 2 If the MAC address is registered with the LES, it returns the corresponding ATM address. If not, the LES forwards the LE_ARP request to all LECs on the ELAN (point-to-multipoint control distribute VCC, link 2-8 in Figure 14-3).

Step 3 Any LEC that recognizes the MAC address responds with its ATM address (point-to-point control direct VCC, link 1-7 in Figure 14-3).

Step 4 The LES forwards the response back to the LEC (point-to-multipoint control distribute VCC, link 2-8 in Figure 14-3).

Step 5 The LEC adds the MAC address-ATM address pair to its LE_ARP cache.

Step 6 The LEC can establish a VCC to the desired destination and transmit packets to that ATM address (bidirectional, point-to-point data direct VCC, link 6-6 in Figure 14-3).

For unknown destinations and during address resolution, the LEC sends a packet to the BUS, which forwards the packet to all LECs. The BUS floods the packet because the destination might be behind a bridge that has not yet learned this particular address.

Sending Multicast Traffic

When an LEC sends broadcast, multicast, or unicast traffic with an unknown address, the following process occurs:

The LEC sends the packet to the BUS (unidirectional, point-to-point multicast send VCC, link 4-9 in Figure 14-3).
The BUS forwards (floods) the packet to all LECs (unidirectional, point-to-multipoint multicast forward VCC, link 5-10 in Figure 14-3).

: This VCC branches at each ATM switch. The ATM switch forwards such packets to multiple outputs. (The switch does not examine the MAC addresses; it simply forwards all packets it receives.)

Building a LANE Connection from a PC

To learn about a destination when a Transmission Control Protocol/Internet Protocol (TCP/IP) file transfer is to be sent, the PC and the LEC in the Catalyst 5000 switch begin the following process to associate a LAN destination MAC address with the ATM address of the ATM-attached file server (see Figure 14-4).

Figure 14-4: Steps in Resolving Addresses and Building a LANE Connection

To build a LANE connection from a PC to an ATM attached LEC, the LANE components take these steps:

Step 1 PC---Before starting the file transfer the PC must locate the file server on the network. To find the file server's MAC address, the PC broadcasts an ARP request with the file server's IP address.

Step 2 LEC on Catalyst 5000 switch---Receives ARP and broadcasts to the BUS configured on the ATM switch.

Step 3 BUS on ATM switch---Broadcasts the ARP request to all members of the ELAN using a point-to-multipoint VCC.

Step 4 LEC on file server---Receives the ARP request, recognizes its own IP address and responds with an ARP reply back to the BUS in the ATM switch.

Step 5 BUS on ATM switch---Forwards the ARP reply to the Catalyst 5000 switch.

Step 6 LEC on Catalyst 5000 switch---Forwards the ARP reply to the originating PC.

Step 7 PC---Starts sending the packets of the file transfer using the Catalyst 5000-to-ATM switch multicast send VCC connection to keep the data moving.

Step 8 LEC on file server---Starts to set up the direct VCC to the Catalyst 5000 switch using an LE_ARP request to the LES. This request asks for the ATM address that corresponds to the PC's MAC address.

Note The PC's MAC address was obtained from the original ARP request in Step 4.

Step 9 LES on ATM switch---Looks up the PC's MAC address in its look-up table and multicasts the LE_ARP request to all LECs.

Step 10 LEC on Catalyst 5000 switch---Receives the LE_ARP request and finds the PC's MAC address in its look-up table. (It learned the PC's MAC address in step 2.)

Step 11 LEC on Catalyst 5000 switch---Adds its own ATM address into the LE_ARP request and returns it to the LES in the ATM switch.

Step 12 LES on ATM switch---Multicasts the LE_ARP reply to all members of the ELAN, including the file server.

Step 13 LEC on File Server---Receives the LE_ARP as part of the ELAN and signals for a data direct VCC to the Catalyst 5000 using the ATM address.

Step 14 ATM switch---Sets up a data direct VCC between the Catalyst 5000 and the file server.

Step 15 PC---The file transfers directly from the PC using the direct data VCC from the Catalyst 5000 to the ATM-attached file server.

Implementation Considerations

The following sections describes specific information and considerations you might need to consider prior to LANE implementation:

Network Support
Addressing
Rules for Assigning Components to Interfaces and Subinterfaces

Network Support

The ATM switch supports the following LANE features:

Ethernet-emulated LANs
Token Ring-emulated LANs
Simple server redundancy for fault tolerant LESs and LECSs

Addressing

On a LAN, packets are addressed by the MAC-layer address of the destination and source stations. To provide similar functionality for LANE, MAC-layer addressing must be supported, and every LANE client must have a MAC address. In addition, every LANE component (LEC, LES/BUS, and LECS) must have a unique ATM address.

All LANE clients on the same interface have the same, automatically assigned MAC address which is also used as the end-system identifier (ESI) part of the ATM address (see the following section). Although client MAC addresses are not unique, all ATM addresses are unique.

LANE ATM Addresses

LANE uses NSAP-format ATM end system addresses, consisting of the following:

A 13-byte prefix that includes the fields defined by the ATM Forum
A 6-byte ESI
A 1-byte selector field

See the section "Configuring the ATM Address" in the chapter "Initially Configuring the LightStream 1010 ATM Switch" for more information.

Method of Automatically Assigning ATM Addresses for LANE

We provide the following standard method of constructing and assigning ATM and MAC addresses for use in an LECS's database. A pool of MAC addresses is assigned to each ATM interface on the router or switch. For constructing ATM addresses, the following assignments are made to the LANE components:

The prefix fields are the same for all LANE components on the ATM interface; the prefix indicates the identity of the directly attached ATM switch. The prefix value must be configured on the switch.
The ESI field value assigned to every client on the interface is the first in the pool of MAC addresses assigned to the interface.
The ESI field value assigned to every server on the interface is the second in the pool of MAC addresses.
The ESI field value assigned to the BUS on the interface is the third in the pool of MAC addresses.
The ESI field value assigned to the configuration server is the fourth in the pool of MAC addresses.
The selector field value is set to the subinterface number of the LANE component---except for the LECS, which has a selector field value of 0.

: Because the LANE components are defined on different subinterfaces of an ATM interface, the value of the selector field in an ATM address is different for each component. The result is a unique ATM address for each LANE component, even within the same router. For more information about assigning components to subinterfaces, see the "Rules for Assigning Components to Interfaces and Subinterfaces" section later in this chapter.

For example, if the MAC addresses assigned to an interface are 0800.200C.1000 through 0800.200C.1007, the ESI part of the ATM addresses is assigned to LANE components as follows:

Any client gets ESI 0800.200c.1000.
Any server gets ESI 0800.200c.1001.
The BUS gets ESI 0800.200c.1002.
The LECS gets ESI 0800.200c.1003.

Using ATM Address Templates

You can use ATM address templates in many LANE commands that assign ATM addresses to LANE components (thus overriding automatically assigned ATM addresses) or that link client ATM addresses to emulated LANs. Using templates can greatly simplify the use of these commands. The syntax of address templates, the use of address templates, and the use of wildcard characters within an address template for LANE are very similar to the address templates of International Organization for Standardization of Connectionless Network Service (ISO CLNS).

Note E.164-format ATM addresses do not support the use of LANE ATM address templates.

LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character, and an ellipsis (...) to match any number of leading or trailing characters.

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 fields. Table 14-1 shows how the values of unspecified digits are determined when an ATM address template is used:

Unspecified Digits In	Value Is
Prefix (first 13 bytes)	Obtained from ATM switch via Interim Local Management Interface (ILMI)
ESI (next 6 bytes)	Filled with the slot MAC address¹ plus 0---LANE client 1---LANE server 2---LANE broadcast-and-unknown server 3---Configuration server
Selector field (last 1 byte)	Subinterface number, in the range 0 through 255

Table 14-1: Values of Unspecified Digits in ATM Address Templates

Unspecified Digits In Value Is

Prefix (first 13 bytes)

Obtained from ATM switch via Interim Local Management Interface (ILMI)

ESI (next 6 bytes)

Filled with the slot MAC address¹ plus

0---LANE client

1---LANE server

2---LANE broadcast-and-unknown server

3---Configuration server

Selector field (last 1 byte)

Subinterface number, in the range 0 through 255

¹The lowest in the pool of MAC addresses assigned to the ATM interface plus a value that indicates the LANE component.

Rules for Assigning Components to Interfaces and Subinterfaces

The following rules apply to assigning LANE components to the major ATM interface and its subinterfaces:

The LECS always runs on the major interface.

: The assignment of any other component to the major interface is identical to assigning that component to the 0 subinterface.

The server and the client of the same emulated LAN can be configured on the same subinterface.
Clients of two different emulated LANs cannot be configured on the same subinterface.
Servers of two different emulated LANs cannot be configured on the same subinterface.

Note On the LightStream 1010 ATM switch, LANE components can be configured only on the ASP interface or on one of its subinterfaces.

LANE Router and Switch Requirements

You must manually configure QSAAL and ILMI signaling PVCs on routers and edge LAN switches to run LANE.

Note These signaling PVCs are automatically configured on the LightStream 1010 ATM switch.

At least one ATM switch is required to run LANE. For example, you cannot run LANE on routers connected back-to-back.

LANE Configuration Tasks

Before you begin to configure LANE, you must decide whether you want to set up one or multiple emulated LANs. If you set up multiple emulated LANs, you must also decide where the servers and clients will be located, and whether to restrict the clients that can belong to each emulated LAN. The procedure for configuring bridged emulated is the same as for any other LAN.

To configure LANE, complete the tasks in the following sections:

Note For fault tolerance, multiple LANE services and servers can be assigned to the emulated LAN. This requires the use of our ATM switches and our ATM edge devices end-to-end.

Enabling the Configuration Server

: An ATM cloud can contain multiple configuration servers.

Setting Up LESs and Clients

: Every ELAN must have at least a LES/BUS pair, the maximum is 10. Every LANE cloud (one or multiple ELANs) must have at least one LECS.

You can configure some emulated LANs with unrestricted membership and some emulated LANs with restricted membership. You can also configure a default emulated LAN, which must have unrestricted membership.

After LANE is configured, you can monitor and maintain the components, as described in the section, "Monitoring and Maintaining the LANE Components."

Creating a LANE Plan and Worksheet

Draw up a plan and a worksheet for your LANE scenario, containing the following information and leaving spaces for the ATM address of each LANE component on each subinterface of each participating router or switch:

The component and interface where the LECS will be located.
The component, interface, and subinterface where the LES and BUS for each emulated LAN will be located. Each emulated LAN has multiple servers for fault-tolerant operation.
The component, interfaces, and subinterfaces where the clients for each emulated LAN will be located.
The component and database name of the default database.
The name of the default emulated LAN (optional).
The names of the emulated LANs that have unrestricted membership.
The names of the emulated LANs that have restricted membership.

The last three items in this list are very important; they determine how you set up each emulated LAN in the configuration server database.

Example LANE Plan and Worksheet

This section is an example of the LANE plan and worksheet that would be created for the example network configuration described in the section "Default Configuration for a Single Emulated LAN" at the end of this chapter.

Figure 14-5 shows the single emulated LAN example network.

Figure 14-5: LANE Plan Example Network

The following information describes the LANE plan in Figure 14-5:

LECS:
---Location: ATM_Switch
---Interface: atm 13/0/0
---ATM address: 47.00918100000000E04FACB401.00E04FACB405.00
LES:
---Location: ATM_Switch
---Interface/Subinterface: atm 13/0/0.1
---Type: Ethernet
---ATM address: 47.00918100000000E04FACB401.00E04FACB403.01
BUS:
---Location: ATM_Switch
---Interface/Subinterface: atm 13/0/0.1
---Type: Ethernet
---ATM address: "use default"
Database:
---Location: ATM_Switch
---Name: eng_dbase
---ELAN name: eng_elan
---Default ELAN name: eng_elan
---ATM address: 47.00918100000000E04FACB401.00E04FACB403.01
LANE Client:
---Location: ATM _Switch
---Interface/Subinterface: atm 13/0/0.1
---Server/BUS name: eng_elan
---IP Address/Subnet mask: 172.16.0.4 255.255.0.0
---Type: Ethernet
LANE Client:
---Location: Switch1
---Interface/Subinterface: atm 0.1
---Server/BUS name: eng_elan
---Type: Ethernet
LANE Client:
---Location: Router1
---Interface/Subinterface: atm 3/0.1
---Server/BUS name: eng_elan
---IP Address/Subnet mask: 172.16.0.1 255.255.0.0
---Type: Ethernet

Note VLANs need to be configured on the LAN edge switches. These VLANs must be mapped to the appropriate ELANs.

Continue with the following sections to start configuring LANE on your ATM network.

Displaying LANE Default Addresses

To make configuration easier, you should display the LANE default addresses for each router or switch that is running any of the LESs or services and write down the displayed addresses on your worksheet.

To display the default LANE addresses, enter the following command:

Command Task

show lane default-atm-addresses

Display the LANE default addresses for all ATM interfaces present on the router or switch

Command	Task
show lane default-atm-addresses	Display the LANE default addresses for all ATM interfaces present on the router or switch

Example

The following example displays the default LANE addresses:

Switch# show lane default-atm-addresses
interface ATM13/0/0:
LANE Client:        47.00918100000000E04FACB401.00E04FACB402.**
LANE Server:        47.00918100000000E04FACB401.00E04FACB403.**
LANE Bus:           47.00918100000000E04FACB401.00E04FACB404.**
LANE Config Server: 47.00918100000000E04FACB401.00E04FACB405.00
note: ** is the subinterface number byte in hex

Entering the ATM Address of the Configuration Server

You must enter the configuration server's ATM address into the ATM switch and save it permanently, so that the value is not lost when the switch is reset or powered off. The configuration server address can be specified for the entire switch, or per port.

To enter the configuration server addresses on the ATM switch for the entire switch, perform the following steps in global configuration mode:

Step Command Task

1
atm lecs-address-default address

Specify the LECS's ATM address for the entire switch.

2
copy running-config

Save the configuration value permanently.

Step	Command	Task
1	atm lecs-address-default address	Specify the LECS's ATM address for the entire switch.
2	copy running-config	Save the configuration value permanently.

For examples of these commands, see the section "LANE Configuration Examples" at the end of this chapter.

Setting Up the Configuration Server's Database

After you have determined all LESs, BUSs, and LECs on all ATM subinterfaces on all routers and switches that will participate in LANE, and have displayed their ATM addresses, you can use the information to populate the configuration server's database.

You can set up a default emulated LAN, whether or not you set up any other emulated LANs. You can also set up some emulated LANs with restricted membership and others with unrestricted membership.

To set up the LANE database, complete the tasks in the following subsections as appropriate for your emulated LAN plan and scenario. To set up fault-tolerant operation, see "Configuring Fault-Tolerant Operation," later in this chapter.

Set Up the Database for the Default Emulated LAN Only

When you configure a router as the LECS for one default emulated LAN, you provide the following information:

A name for the database
The ATM address of the server for the emulated LAN
The ring number of the emulated LAN (for Token Ring)
A default name for the emulated LAN

When you set up a database of only a default unrestricted emulated LAN, you do not have to specify where the LANE clients are located. That is, when you set up the configuration servers database for a single default emulated LAN, you do not have to provide any database entries that link the ATM addresses of any clients with the emulated LAN name.

To set up the LECS for the default emulated LAN, perform the following steps, beginning in global configuration mode:

Step Command Task

1
lane database database-name

Create a named database for the LECS.

2
name elan-name server-atm-address atm-address [index n]

In the configuration database, bind the name of the emulated LAN to the ATM address of the LES.

3
name elan-name local-seg-id seg-num

(for Token Ring only.) In the configuration database, specify the ring number for the emulated LAN.

4
default-name elan-name

In the configuration database, assign an emulated LAN to the LECs trying to join without specifying an ELAN name.

Step	Command	Task
1	lane database database-name	Create a named database for the LECS.
2	name elan-name server-atm-address atm-address [index n]	In the configuration database, bind the name of the emulated LAN to the ATM address of the LES.
3	name elan-name local-seg-id seg-num	(for Token Ring only.) In the configuration database, specify the ring number for the emulated LAN.
4	default-name elan-name	In the configuration database, assign an emulated LAN to the LECs trying to join without specifying an ELAN name.

In Step 2, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet and obtained in the "Displaying LANE Default Addresses" section. You can have any number of servers per emulated LAN for fault tolerance. Entry order determines priority: the first entry has the highest priority unless you override it with the index option.

If you are setting up only a default emulated LAN, the elan-name value in Step 2is the same as the default emulated LAN name you provide in Step 4.

To set up fault-tolerant operation, see the section "Configuring Fault-Tolerant Operation," later in this chapter.

For examples of these commands, see the section "LANE Configuration Examples" later in this chapter.

Set Up the Database for Unrestricted-Membership Emulated LANs

When you set up a database for unrestricted emulated LANs, you create database entries that link the name of each emulated LAN to the ATM address of its server.

However, you can choose not to specify the locations of the LANE clients. That is, when you set up the configuration server's database, you do not have to provide any database entries that link the ATM addresses or MAC addresses of any clients with the emulated LAN name.

To configure a router or switch as the LECS for multiple emulated LANs with unrestricted membership, perform the following steps, beginning in global configuration mode:

Step Command Task

1
lane database database-name

Create a named database for the LECS.

2
name elan-name1 server-atm-address atm-address [index n]

In the configuration database, bind the name of the first emulated LAN to the ATM address of the LES for that emulated LAN.

3
name elan-name1 local-seg-id seg-num

(For Token Ring only.) In the configuration database, specify the ring number for the first emulated LAN.

4
name elan-name2 server-atm-address atm-address [index n]

In the configuration database, bind the name of the second emulated LAN to the ATM address of the LES.

Repeat this step, providing a different emulated LAN name and an ATM address, for each additional emulated LAN in this switch cloud.

5
name elan-name2 local-seg-id seg-num

(For Token Ring only.) In the configuration database, specify the ring number for the second emulated LAN.

Repeat this step for each additional Token Ring emulated LAN.

6
default name elan-name1

(Optional.) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN.

Step	Command	Task
1	lane database database-name	Create a named database for the LECS.
2	name elan-name1 server-atm-address atm-address [index n]	In the configuration database, bind the name of the first emulated LAN to the ATM address of the LES for that emulated LAN.
3	name elan-name1 local-seg-id seg-num	(For Token Ring only.) In the configuration database, specify the ring number for the first emulated LAN.
4	name elan-name2 server-atm-address atm-address [index n]	In the configuration database, bind the name of the second emulated LAN to the ATM address of the LES. Repeat this step, providing a different emulated LAN name and an ATM address, for each additional emulated LAN in this switch cloud.
5	name elan-name2 local-seg-id seg-num	(For Token Ring only.) In the configuration database, specify the ring number for the second emulated LAN. Repeat this step for each additional Token Ring emulated LAN.
6	default name elan-name1	(Optional.) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN.

In Steps 2and 4, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet and obtained in the "Displaying LANE Default Addresses" section.

To set up fault-tolerant operation, see the section "Configuring Fault-Tolerant Operation" later in this chapter.

For examples of these commands, see the section "LANE Configuration Examples" later in this chapter.

Set Up the Database for Restricted-Membership LANs

When you set up the database for restricted-membership emulated LANs, you create database entries that link the name of each emulated LAN to the ATM address of its server.

However, you also must specify where the LANE clients are located. That is, for each restricted-membership emulated LAN, you provide a database entry that explicitly links the ATM address or MAC address of each client of that emulated LAN with the name of that emulated LAN.

Those client database entries specify the clients that are allowed to join the emulated LAN. When a client requests that the configuration server indicate which emulated LAN it is to join, the configuration server consults its database and then responds as configured.

When clients for the same restricted-membership emulated LAN are located in multiple routers, each client's ATM address or MAC address must be linked explicitly with the name of the emulated LAN. As a result, you must configure as many client entries (Step 5in the following procedure) as you have clients for emulated LANs in all the routers. Each client will have a different ATM address in the database entries.

To set up the configuration server for emulated LANs with restricted membership, follow these steps, beginning in global configuration mode:

Step Command Task

1
lane database database-name

Create a named database for the LECS.

2
name elan-name1 server-atm-address atm-address [index n]

In the configuration database, bind the name of the first emulated LAN to the ATM address of the LES for that emulated LAN.

3
name elan-name1 local-seg-id seg-num

(Token Ring only.) In the configuration database, specify the ring number for the first emulated LAN.

4
name elan-name2 server-atm-address atm-address [index n]

In the configuration database, bind the name of the second emulated LAN to the ATM address of the LES.

Repeat this step, providing a different name and a different ATM address for each additional emulated LAN.

5
name elan-name2 local-seg-id seg-num

(Token Ring only.) In the configuration database, specify the ring number for the second emulated LAN.

Repeat this step for each additional Token Ring emulated LAN.

6
d efault name elan-name1

(Optional.) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN.

7
client-atm-address atm-address-template name elan-name

Add a database entry associating a specific client's ATM address with a specific restricted-membership emulated LAN.

Repeat this step for each client of each restricted-membership emulated LANs on this switch cloud, in each case specifying that client's ATM address and the name of the emulated LAN with which it is linked.

Step	Command	Task
1	lane database database-name	Create a named database for the LECS.
2	name elan-name1 server-atm-address atm-address [index n]	In the configuration database, bind the name of the first emulated LAN to the ATM address of the LES for that emulated LAN.
3	name elan-name1 local-seg-id seg-num	(Token Ring only.) In the configuration database, specify the ring number for the first emulated LAN.
4	name elan-name2 server-atm-address atm-address [index n]	In the configuration database, bind the name of the second emulated LAN to the ATM address of the LES. Repeat this step, providing a different name and a different ATM address for each additional emulated LAN.
5	name elan-name2 local-seg-id seg-num	(Token Ring only.) In the configuration database, specify the ring number for the second emulated LAN. Repeat this step for each additional Token Ring emulated LAN.
6	d efault name elan-name1	(Optional.) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN.
7	client-atm-address atm-address-template name elan-name	Add a database entry associating a specific client's ATM address with a specific restricted-membership emulated LAN. Repeat this step for each client of each restricted-membership emulated LANs on this switch cloud, in each case specifying that client's ATM address and the name of the emulated LAN with which it is linked.

To set up fault-tolerant operation, see the section "Configuring Fault-Tolerant Operation" later in this chapter.

Enabling the Configuration Server

After you create the database entries appropriate to the type and to the membership conditions of the emulated LANs, you enable the configuration server on the selected ATM interface, router, or switch and specify that the configuration server's ATM address is to be computed automatically.

To enable the configuration server, follow these steps, beginning in global configuration mode:

Step Command Task

1
interface atm 2/0/0[.sub_inter #]

If you are not currently configuring the interface, specify the major ATM interface where the configuration server is located.

2
lane config database database-name

Link the configuration server's database name to the specified major interface, and enable the configuration server.

3
lane config auto-config-atm-address

Specify that the configuration server's ATM address will be computed by our automatic method.

Step	Command	Task
1	interface atm 2/0/0[.sub_inter #]	If you are not currently configuring the interface, specify the major ATM interface where the configuration server is located.
2	lane config database database-name	Link the configuration server's database name to the specified major interface, and enable the configuration server.
3	lane config auto-config-atm-address	Specify that the configuration server's ATM address will be computed by our automatic method.

For examples of these commands, see the section "LANE Configuration Examples" later in this chapter.

Setting Up LESs and Clients

For each device that participates in LANE, set up the necessary servers and clients for each emulated LAN; then display and record the server and client ATM addresses. Be sure to keep track of the router or switch interface where the LECS will be located.

For one default emulated LAN, you must set up one set of servers: one as a primary server and the rest as backup servers for the same emulated LAN. For multiple emulated LANs, you can set up servers for another emulated LAN on a different subinterface or on the same interface of this router or switch, or you can place the servers on a different router.

When you set up a server and BUS on a router, you can combine them with a client on the same subinterface, a client on a different subinterface, or no client at all on the router.

Where you put the clients is important, because any router with clients for multiple emulated LANs can route frames between those emulated LANs.

Note For Token Ring LANE environments that source-route bridge IP traffic to the ATM switch, multiring must be configured to enable Routing Information Field (RIF) packets. For an example, see "Default Configuration for a Single Emulated Token Ring LAN with IP Source Routing Across a Source-Route Bridged Network."

Set Up the Server, BUS, and a Client on a Subinterface

To set up the server, BUS, and (optionally) clients for an emulated LAN, perform the following steps in global configuration mode:

Step Command Task

1
interface atm 2/0/0[.sub_inter #]

Specify the subinterface for the first emulated LAN on this router.

2
lane server-bus {ethernet | tokenring} elan-name1

Enable a LES and a LANE BUS for the first emulated LAN.

3
lane client {ethernet | tokenring} [elan-name1]

(Optional.) Enable a LANE client for the first emulated LAN.

4
ip address address

Provide a protocol address for the client.

Step	Command	Task
1	interface atm 2/0/0[.sub_inter #]	Specify the subinterface for the first emulated LAN on this router.
2	lane server-bus {ethernet \| tokenring} elan-name1	Enable a LES and a LANE BUS for the first emulated LAN.
3	lane client {ethernet \| tokenring} [elan-name1]	(Optional.) Enable a LANE client for the first emulated LAN.
4	ip address address	Provide a protocol address for the client.

If the emulated LAN in Step 2 will have restricted membership, consider carefully whether you want to specify its name here. You will specify the name in the LECS's database when it is set up. However, if you link the client to an emulated LAN , and by some mistake it does not match the database entry linking the client to an emulated LAN, this client will not be allowed to join this or any other emulated LAN.

If you do decide to include the name of the emulated LAN linked to the client in Step 3 and later want to associate that client with a different emulated LAN, make the change in the configuration server's database before you make the change for the client on this subinterface.

Each emulated LAN is a separate subnetwork. In Step 4, make sure that the clients of the same emulated LAN are assigned protocol addresses on the same subnetwork, and that clients of different emulated LANs are assigned protocol addresses on different subnetworks.

For examples of these commands, see the section "LANE Configuration Examples" at the end of this chapter.

Set Up Only a Client on a Subinterface

On any given router or switch, you can set up one client for one emulated LAN or multiple clients for multiple emulated LANs. You can set up a client for a given emulated LAN on any routers you select to participate in that emulated LAN. Any router with clients for multiple emulated LANs can route packets among those emulated LANs.

To set up only a client for an emulated LAN, perform the following steps in global configuration mode:

Step Command Task

1
interface atm 2/0/0[.sub_inter #]

Specify the subinterface for an emulated LAN on this router.

2
ip address address

Provide a protocol address for the client on this subinterface.

3
lane client {ethernet | tokenring} elan-name1

Enable a LANE client for the first emulated LAN.

Step	Command	Task
1	interface atm 2/0/0[.sub_inter #]	Specify the subinterface for an emulated LAN on this router.
2	ip address address	Provide a protocol address for the client on this subinterface.
3	lane client {ethernet \| tokenring} elan-name1	Enable a LANE client for the first emulated LAN.

Each emulated LAN is a separate subnetwork. In Step 2, make sure that the clients of the same emulated LAN are assigned protocol addresses on the same subnetwork, and that clients of different emulated LANs are assigned protocol addresses on different subnetworks.

For examples of these commands, see the section "LANE Configuration Examples" at the end of this chapter.

Configuring a LAN Emulation Client on the Switch

This section describes configuring a LANE client connection from the LightStream 1010 ATM switch in the headquarters building to the CPU port 2/0/0 of the switch.

Note This connection can be used for switch management only.

Interface 2/0/0 configured as a LANE client allows configuration of the switch from a remote host.

Configure an Ethernet LANE Client

To configure the interface 2/0/0 as an Ethernet LANE client on the ATM switch, perform the following steps in global configuration mode:

Step Command Task

1
atm lecs-address lecs-address

Specify the address to the LECS.

2
interface atm 2/0/0[.sub_inter #]

Select the interface to be configured.

3
lane client-atm-address atm-address-template

Specify an ATM address, and override the automatic ATM address assignment for the LANE client.

4
lane client {ethernet | tokenring} [elan-name]

Configure a LANE client on the specified subinterface.

Step	Command	Task
1	atm lecs-address lecs-address	Specify the address to the LECS.
2	interface atm 2/0/0[.sub_inter #]	Select the interface to be configured.
3	lane client-atm-address atm-address-template	Specify an ATM address, and override the automatic ATM address assignment for the LANE client.
4	lane client {ethernet \| tokenring} [elan-name]	Configure a LANE client on the specified subinterface.

Example

The following example shows how to configure the LANE client on the ASP ATM interface 2/0/0:

Switch(config)# atm lecs-address 47.0091.0000.0000.0000.0000.0000.0000.00
Switch(config)# interface atm 2/0/0
Switch(config-if)# lane client ethernet eng_elan

In order, the commands in this example:

1. Set the LANE configuration server (LECS) ATM address to 47.0091.0000...

2. Change to interface configuration mode to configure ATM CPU interface 2/0/0.

3. Configure the LANE client ATM address to 0800.200C.1001.**

4. Configure the LANE client as an Ethernet connection, with the name "mis."

For additional examples of these commands, see the section "LANE Configuration Examples" at the end of this chapter.

Configuring Fault-Tolerant Operation

The LANE simple server redundancy feature creates fault tolerance using standard LANE protocols and mechanisms. If a failure occurs on the LECS or on the LES/BUS, the emulated LAN can continue to operate using the services of a backup LES. This protocol is called the Simple Server Redundancy Protocol (SSRP).

This section describes how to configure simple server redundancy for fault tolerance on an emulated LAN.

Cisco Simple Server Redundancy

You can define redundant LECSs by configuring one or more server addresses---obtained through the Interim Local Management Interface (ILMI)---on the ATM switch. The LECS turns on server redundancy by adjusting its database to accommodate multiple server ATM addresses for a particular emulated LAN. The additional servers provide backup for that emulated LAN.

For simple LANE service replication or fault tolerance to work, the ATM switch must support multiple LES addresses. This mechanism is specified in the LANE standard. The LESs establish and maintain a standard control circuit that enables the server redundancy to operate.

LANE simple server redundancy comes ready to operate with Cisco IOS Release 11.2 software. To activate the feature, you add an entry for the hierarchical list of servers that will support the given emulated LAN. All database modifications for the emulated LAN must be identical on all LECSs.

Older LANE configuration files continue to work with this new software. LANE configurations that network with non-Cisco ATM equipment continue to work, but the non-Cisco ATM equipment cannot participate in the LANE simple server redundancy.

With the earlier LANE implementation, only one LECS, capable of serving multiple emulated LANS, and only one LES/BUS per emulated LAN was possible for an ATM switch cloud. The earlier LANE protocol did not allow for multiple LESs within an emulated LAN. Therefore, these components represented both single points of failure for LANE service.

LANE simple server redundancy corrects these limitations by allowing backup LECSs and LES/BUSs for an emulated LAN. Offered in Cisco IOS Release 11.2 or later, LANE simple server redundancy is enabled when you configure multiple servers for the same emulated LAN.

Note This server redundancy does not overcome other points of failure beyond the router ports. Additional redundancy on the LAN side or in the ATM switch cloud are not a part of the LANE simple server redundancy feature.

This redundancy feature works only with Cisco LECSs and LES/BUS combinations. Third-party LANE components continue to interoperate with the LECS and LES/BUS function of Cisco routers, but cannot take advantage of the redundancy features.

Enable Redundant LECSs

To enable redundant LECSs, enter the multiple LECS addresses into the end ATM switches, which are used as central locations where the list of LECS addresses can be obtained. This allows LANE components connected to the switches to obtain the global list of LECS addresses.

To enable fault tolerance, you enable multiple, redundant, and standby LECSs and multiple, redundant, and standby LES/BUSs. Our LANE continues to operate seamlessly with other vendors' LANE components, but fault tolerance is not effective in this situation.

To configure multiple LES/BUSs for emulated LANs on the routers or switches, perform the following steps in global configuration mode:

Step Command Task

1
lane database database-name

Create a named database for the LECS.

2
name elan-name server-atm-address address index n

Specify redundant LES/BUSs, or simple server replication. Enter the command for each LES address for the same emulated LAN. The index determines the priority. 0 is the highest priority.

3
lane client {ethernet | tokenring} elan-name1

Enable a LANE client for the first emulated LAN.

Step	Command	Task
1	lane database database-name	Create a named database for the LECS.
2	name elan-name server-atm-address address index n	Specify redundant LES/BUSs, or simple server replication. Enter the command for each LES address for the same emulated LAN. The index determines the priority. 0 is the highest priority.
3	lane client {ethernet \| tokenring} elan-name1	Enable a LANE client for the first emulated LAN.

Server redundancy guards against the failure of the hardware on which LES components are running. This includes all the ATM interface cards in our routers and Catalyst switches. Fault tolerance is not effective for ATM network or switch failures.

Caution
For server redundancy to work correctly, all ATM switches must have identical lists of the global LECS addresses, in the identical priority order. The operating LECSs must use exactly the same configuration database.

Load the configuration table data using the configure network command. This method minimizes errors and enables the database to be maintained centrally in one place.

For examples of these commands, see the section "LANE Configuration Examples" at the end of this chapter.

Implementation Considerations

The following stipulations and limitations should be considered when configuring redundancy:

Up to 16 LECS addresses can be handled by the LANE subsystem.
There is no limit to the number of LESs that can be defined per emulated LAN.
When a LECS switches over, no previously joined clients are affected.
When a LES/BUS switches over, momentary loss of clients occurs until they are all transferred to the new LES/BUS.
LECSs come up automatically as masters until a higher-level LECS tells them otherwise.
If a higher-priority LES comes online, it bumps the current LES off on the same emulated LAN. Therefore, there might be some changing of clients from one LES to another after a powerup, depending on the order of the LESs coming up. Changing should settle after the last highest priority LES comes up.
If none of the specified LESs is up or connected to the master LECS, and more than one LES is defined for an emulated LAN, a configuration request for that specific emulated LAN is rejected by the LECS.
Changes made to the list of LECS addresses on ATM switches can take up to a minute to propagate through the network. Changes made to the configuration database regarding LES addresses take effect almost immediately.
You can override the LECS address on any subinterface by using the following commands:
- lane auto-config-atm-address
- lane fixed-config-atm-address
- lane config-atm-address

Caution
When you perform an override using one of these commands, fault-tolerant operation cannot be guaranteed. To avoid affecting the fault-tolerant operation, do not override any LECS, LES, or BUS addresses.

If an underlying ATM network failure occurs, there might be multiple master LECSs and multiple active LESs for the same emulated LAN. This situation creates a "partitioned" network. The clients continue to operate normally, but transmission between different partitions of the network is not possible. When the network break is repaired, the system recovers.

Monitoring and Maintaining the LANE Components

After configuring LANE components on an interface or any of its subinterfaces, on a specified subinterface, or on an emulated LAN, you can display their status. To show LANE information, follow these steps:

Command Task

show lane card/subcard/port[.sub_inter #] | name elan-name] [brief]

Display the global and per-virtual channel connection LANE information for all the LANE components and emulated LANs configured on an interface or any of its subinterfaces.

show lane bus [interface atm
card/subcard/port[.sub_inter #] | name elan-name] [brief]

Display the global and per-VCC LANE information for the BUS configured on any subinterface or emulated LAN.

show lane client [interface atm card/subcard/port [.sub_inter #] | name elan-name] [brief]

Display the global and per-VCC LANE information for all LANE clients configured on any subinterface or emulated LAN.

show lane config [interface atm
card/subcard/port[.sub_inter #]]

Display the global and per-VCC LANE information for the configuration server configured on any interface.

show lane database [database-name]

Display the LECS's database.

show lane le-arp [interface atm
card/subcard/port[.sub_inter # | name elan-name]

Display the LANE ARP table of the LANE client configured on the specified subinterface or emulated LAN.

show lane server [interface atm
card/subcard/port [.sub_inter #] | name elan-name] [brief]

Display the global and per-VCC LANE information for the LES configured on a specified subinterface or emulated LAN.

Command	Task
show lane card/subcard/port[.sub_inter #] \| name elan-name] [brief]	Display the global and per-virtual channel connection LANE information for all the LANE components and emulated LANs configured on an interface or any of its subinterfaces.
show lane bus [interface atm card/subcard/port[.sub_inter #] \| name elan-name] [brief]	Display the global and per-VCC LANE information for the BUS configured on any subinterface or emulated LAN.
show lane client [interface atm card/subcard/port [.sub_inter #] \| name elan-name] [brief]	Display the global and per-VCC LANE information for all LANE clients configured on any subinterface or emulated LAN.
show lane config [interface atm card/subcard/port[.sub_inter #]]	Display the global and per-VCC LANE information for the configuration server configured on any interface.
show lane database [database-name]	Display the LECS's database.
show lane le-arp [interface atm card/subcard/port[.sub_inter # \| name elan-name]	Display the LANE ARP table of the LANE client configured on the specified subinterface or emulated LAN.
show lane server [interface atm card/subcard/port [.sub_inter #] \| name elan-name] [brief]	Display the global and per-VCC LANE information for the LES configured on a specified subinterface or emulated LAN.

LANE Configuration Examples

The examples in the following sections illustrate how to configure LANE for the following cases:

Default configuration for a single emulated LAN with a LANE client on the ATM switch
Default configuration for a single emulated LAN with a backup LECS and LES on the ATM switch
Default configuration for a single emulated Token Ring LAN using IP source routing across a source-route bridged network with a LANE client on the ATM switch

All examples use the automatic ATM address assignment method described in the "Method of Automatically Assigning ATM Addresses for LANE" section, earlier in this chapter.

These examples show the LANE configurations, not the process of determining the ATM addresses and entering them.

Default Configuration for a Single Emulated LAN

The following examples show how to configure one Cisco 7505 router, one LightStream 1010 ATM switch, and one Catalyst 5500 switch for a single emulated LAN. Configurations for both Ethernet and Token Ring emulated LANs are shown.

The ATM switch contains the LECS, LES, BUS, and an LEC. The router and Catalyst 5500 switch each contain an LEC for the emulated LAN. This example uses all LANE default settings. For example, it does not explicitly set ATM addresses for the different LANE components that are colocated on the ATM switch. Membership in this LAN is not restricted (see Figure 14-6).

Figure 14-6: Single Emulated LAN Example Network

Ethernet Example

ATM Switch

ATM_Switch# show lane default-atm-addresses
interface ATM13/0/0:
LANE Client:        47.00918100000000E04FACB401.00E04FACB402.**
LANE Server:        47.00918100000000E04FACB401.00E04FACB403.**
LANE Bus:           47.00918100000000E04FACB401.00E04FACB404.**
LANE Config Server: 47.00918100000000E04FACB401.00E04FACB405.00
note: ** is the subinterface number byte in hex
 
ATM_Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM_Switch(config)# atm lecs-address-default 47.00918100000000E04FACB401.00E04FACB405.00
ATM_Switch(config)# ^Z
ATM_Switch# 
ATM_Switch# copy running-config startup-config
Building configuration...
[OK]
ATM_Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM_Switch(config)# lane database eng_dbase
ATM_Switch(lane-config-database)# name eng_elan
ATM_Switch(lane-config-database)# name eng_elan server-atm-address 47.00918100000000E04FACB401.00E04FACB403.01 
ATM_Switch(lane-config-database)# default-name eng_elan
ATM_Switch(lane-config-database)# end
ATM_Switch# show lane database
 
LANE Config Server database table 'eng_dbase'
default elan: eng_elan
elan 'eng_elan': un-restricted
  server 47.00918100000000E04FACB401.00E04FACB403.01 (prio 0)
 
ATM_Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM_Switch(config)# interface atm 13/0/0
ATM_Switch(config-if)# lane config database eng_dbase
ATM_Switch(config-if)# lane config auto-config-atm-address
ATM_Switch(config-if)# exit
ATM_Switch(config)# end
ATM_Switch# show lane config
LE Config Server ATM13/0/0 config table: eng_dbase
Admin: up  State: operational
LECS Mastership State: active master
list of global LECS addresses (42 seconds to update):
47.00918100000000E04FACB401.00E04FACB405.00  <-------- me
ATM Address of this LECS: 47.00918100000000E04FACB401.00E04FACB405.00 (auto)
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 0
cumulative total number of config failures so far: 0
 
ATM_Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM_Switch(config)# interface atm 13/0/0.1
ATM_Switch(config-subif)# lane server-bus ethernet eng_elan
ATM_Switch(config-subif)# ip address 172.16.0.4 255.255.0.0
ATM_Switch(config-subif)# end
ATM_Switch# show lane
LE Config Server ATM13/0/0 config table: eng_dbase
Admin: up  State: operational
LECS Mastership State: active master
list of global LECS addresses (46 seconds to update):
47.00918100000000E04FACB401.00E04FACB405.00  <-------- me
ATM Address of this LECS: 47.00918100000000E04FACB401.00E04FACB405.00 (auto)
 vcd  rxCnt  txCnt  callingParty
  82      0      0  47.00918100000000E04FACB401.00E04FACB403.01 LES eng_elan 0 active
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 0
cumulative total number of config failures so far: 0
 
LE Server ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB403.01
LECS used: 47.00918100000000E04FACB401.00E04FACB405.00 connected, vcd 81
 
LE BUS ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB404.01
 
ATM_Switch# show lane
LE Config Server ATM13/0/0 config table: eng_dbase
Admin: up  State: operational
LECS Mastership State: active master
list of global LECS addresses (15 seconds to update):
47.00918100000000E04FACB401.00E04FACB405.00  <-------- me
ATM Address of this LECS: 47.00918100000000E04FACB401.00E04FACB405.00 (auto)
 vcd  rxCnt  txCnt  callingParty
  82      0      0  47.00918100000000E04FACB401.00E04FACB403.01 LES eng_elan 0 active
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 0
cumulative total number of config failures so far: 0
 
LE Server ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB403.01
LECS used: 47.00918100000000E04FACB401.00E04FACB405.00 connected, vcd 81
 
LE BUS ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB404.01
 
ATM_Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM_Switch(config)# interface atm 13/0/0.1
ATM_Switch(config-subif)# lane client ethernet eng_elan
ATM_Switch(config-subif)# end
ATM_Switch# show lane client
LE Client ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
Client ID: 1                 LEC up for 30 seconds 
ELAN ID: 0
Join Attempt: 1              
HW Address: 00e0.4fac.b402   Type: ethernet		Max Frame Size: 1516            
ATM Address: 47.00918100000000E04FACB401.00E04FACB402.01
 
 VCD  rxFrames  txFrames  Type       ATM Address
   0         0         0  configure  47.00918100000000E04FACB401.00E04FACB405.00
  87         1         2  direct     47.00918100000000E04FACB401.00E04FACB403.01
  90         1         0  distribute 47.00918100000000E04FACB401.00E04FACB403.01
  91         0         1  send       47.00918100000000E04FACB401.00E04FACB404.01
  94         0         0  forward    47.00918100000000E04FACB401.00E04FACB404.01
 
ATM_Switch# copy running-config startup-config
Building configuration...
[OK]
ATM_Switch#

Router 1

router1# config t
Enter configuration commands, one per line.  End with CNTL/Z.
router1(config)# interface atm 3/0
router1(config-if)# atm pvc 1 0 5 qsaal
router1(config-if)# atm pvc 2 0 16 ilmi
router1(config-if)# interface atm 3/0.1
router1(config-subif)# ip address 172.16.0.1 255.255.0.0
router1(config-subif)# lane client ethernet eng_elan
router1(config-subif)# end
router1# show running-config
Building configuration...
 
Current configuration:
!
version 11.1
 
<Informaiton deleted>
 
!
interface ATM3/0
 no ip address
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
!
interface ATM3/0.1 multipoint
 lane client ethernet eng_elan
!
 
<Information deleted>
 
!
end
 
router1# show interface atm 3/0.1
ATM3/0.1 is up, line protocol is up 
  Hardware is cxBus ATM
  MTU 1500 bytes, BW 156250 Kbit, DLY 80 usec, rely 255/255, load 1/255
  Encapsulation ATM-LANE
  ARP type: ARPA, ARP Timeout 04:00:00
router1#

Catalyst 5500 Switch 1

Switch1> session 4
Trying ATM-4...
Connected to ATM-4.
Escape character is '^]'.
ATM> enable
ATM# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM(config)# interface atm 0
ATM(config-if)# lane server-bus ethernet eng_elan
ATM(config-if)# end
ATM# write mem
Building configuration...
[OK]
ATM# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM(config)# interface atm 0
ATM(config-if)# atm pvc 1 0 5 qsaal
ATM(config-if)# atm pvc 2 0 16 ilmi
ATM(config-if)# end
ATM# 
ATM# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM(config)# interface atm 0.1
ATM(config-subif)# lane client ethernet 1 eng_elan
ATM(config-subif)# end
ATM# show lane client
LE Client ATM0.1  ELAN name: eng_elan  Admin: up  State: operational
Client ID: 3                 LEC up for 24 seconds 
Join Attempt: 11             
HW Address: 00e0.4fac.b030   Type: ethernet		Max Frame Size: 1516            VLANID: 1                    	
ATM Address: 47.00918100000000E04FACB401.00E04FACB030.01
 
 VCD  rxFrames  txFrames  Type       ATM Address
   0         0         0  configure  47.00918100000000E04FACB401.00E04FACB405.00
  27         1        14  direct     47.00918100000000E04FACB401.00E04FACB403.01
  29        13         0  distribute 47.00918100000000E04FACB401.00E04FACB403.01
  30         0        15  send       47.00918100000000E04FACB401.00E04FACB404.01
  31         0         0  forward    47.00918100000000E04FACB401.00E04FACB404.01
 
ATM# write mem
Building configuration...
[OK]
ATM#

Confirming Connectivity between the ATM Switch and Other LANE Members

The following example shows how to use the show lane and ping commands to confirm the connection between the ATM switch, routers, and LAN switches:

ATM Switch

Switch# show lane
LE Config Server ATM13/0/0 config table: eng_dbase
Admin: up  State: operational
LECS Mastership State: active master
list of global LECS addresses (31 seconds to update):
47.00918100000000E04FACB401.00E04FACB405.00  <-------- me
ATM Address of this LECS: 47.00918100000000E04FACB401.00E04FACB405.00 (auto)
 vcd  rxCnt  txCnt  callingParty
  82      2      2  47.00918100000000E04FACB401.00E04FACB403.01 LES eng_elan 0 active
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 4
cumulative total number of config failures so far: 0
 
LE Server ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB403.01
LECS used: 47.00918100000000E04FACB401.00E04FACB405.00 connected, vcd 81
control distribute: vcd 89, 2 members, 2 packets
 
proxy/ (ST: Init, Conn, Waiting, Adding, Joined, Operational, Reject, Term)
lecid ST vcd    pkts Hardware Addr  ATM Address
   1  O   88       2 00e0.4fac.b402 47.00918100000000E04FACB401.00E04FACB402.01
   2  O   96       2 0080.1c93.8060 47.00918100000000E04FACB401.00801C938060.01
 
LE BUS ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB404.01
data forward: vcd 93, 2 members, 95 packets, 0 unicasts
 
lecid  vcd     pkts   ATM Address
    1   92       95 47.00918100000000E04FACB401.00E04FACB402.01
    2   97       42 47.00918100000000E04FACB401.00801C938060.01
 
LE Client ATM13/0/0.1  ELAN name: eng_elan  Admin: up  State: operational
Client ID: 1                 LEC up for 1 hour 34 minutes 46 seconds 
ELAN ID: 0
Join Attempt: 1              
HW Address: 00e0.4fac.b402   Type: ethernet		Max Frame Size: 1516            
ATM Address: 47.00918100000000E04FACB401.00E04FACB402.01
 
 VCD  rxFrames  txFrames  Type       ATM Address
   0         0         0  configure  47.00918100000000E04FACB401.00E04FACB405.00
  87         1         2  direct     47.00918100000000E04FACB401.00E04FACB403.01
  90         2         0  distribute 47.00918100000000E04FACB401.00E04FACB403.01
  91         0        95  send       47.00918100000000E04FACB401.00E04FACB404.01
  94        42         0  forward    47.00918100000000E04FACB401.00E04FACB404.01
 
ATM_Switch# ping 172.16.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms
ATM_Switch# ping 172.16.0.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms
ATM_Switch#

Token Ring Example

In this Token Ring example, the Cisco 7505 router contains the LECS, LES, BUS, and an LEC. The ATM switch and Catalyst 5500 Fast Ethernet switch each contain an LEC for the emulated LAN. This example uses all LANE default settings. For example, it does not explicitly set ATM addresses for the different LANE components that are colocated on the router. Membership in this LAN is not restricted.

Router 1

router1# show lane default-atm-addresses
interface ATM3/0:
LANE Client:        47.00918100000000603E7B2001.00000C407572.**
LANE Server:        47.00918100000000603E7B2001.00000C407573.**
LANE Bus:           47.00918100000000603E7B2001.00000C407574.**
LANE Config Server: 47.00918100000000603E7B2001.00000C407575.00
note: ** is the subinterface number byte in hex
 
router1#

ATM Switch

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# atm lecs-address-default 47.00918100000000603E7B2001.00000C407575.00
Switch(config)# end
Switch#

Router 1

router1# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router1(config)# lane database eng_dbase
router1(lane-config-database)# name eng_elan server-atm-address 47.00918100000000603E7B2001.00000C407573.01
router1(lane-config-database)# name eng_elan local-seg-id 2048
router1(lane-config-database)# default-name eng_elan
router1(lane-config-database)# exit
router1(config)# interface atm0
router1(config-if)# atm pvc 1 0 5 qsaal
router1(config-if)# atm pvc 2 0 16 ilmi
router1(config-if)# lane config auto-config-atm-address
router1(config-if)# lane config database eng_dbase
router1(config-if)# 
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm3/0.1
router1(config-subif)# ip address 172.16.0.1 255.255.0.0
router1(config-subif)# lane server-bus tokenring eng_elan
router1(config-subif)# lane client tokenring eng_elan
router1(config-subif)# 
%LANE-5-UPDOWN: ATM0.1 elan eng: LE Client changed state to up
router1(config-subif)# end
router1#

Catalyst 5000 Switch 1

Switch1> session 4
Trying ATM-4...
Connected to ATM-4.
Escape character is '^]'.
ATM> enable
ATM# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM(config)# interface atm 0
ATM(config-if)# lane server-bus tokenring eng_elan
ATM(config-if)# end
ATM# write mem
Building configuration...
[OK]
config t
Enter configuration commands, one per line.  End with CNTL/Z.
ATM(config)# interface atm 0
ATM(config-if)# atm pvc 1 0 5 qsaal
ATM(config-if)# atm pvc 2 0 16 ilmi
ATM(config-if)# end
ATM# 
ATM# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ATM(config)# interface atm 0.1
ATM(config-subif)# lane client tokenring 1 eng_elan
ATM(config-subif)# end
ATM#

ATM Switch

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# interface atm13/0/0.1
Switch(config-subif)# ip address 172.16.0.4 255.255.0.0
Switch(config-subif)# lane client tokenring eng_elan
Switch(config-subif)# 
%LANE-5-UPDOWN: ATM13/0/0.1 elan : LE Client changed state to up
Switch(config-subif)# end
Switch#

Confirming Connectivity between the ATM Switch and the Routers

The following example shows how to use the ping command to confirm the connection between the ATM switch and routers:

ATM_Switch# ping 172.16.0.1
 
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms
ATM_Switch# ping 172.16.0.3
 
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms

Displaying the LANE Client Configuration on the ATM Switch

The following example shows the show lane client command display for the Ethernet LANE client in the ATM switch:

ATM_Switch# show lane client
LE Client ATM13/0/0.1  ELAN name: eng  Admin: up  State: operational
Client ID: 3                 LEC up for 4 minutes 58 seconds 
Join Attempt: 1              
HW Address: 0060.3e7b.2002   Type: ethernet             Max Frame Size: 1516            
ATM Address: 47.00918100000000603E7B2001.00603E7B2002.01
 
 VCD  rxFrames  txFrames  Type       ATM Address
   0         0         0  configure  47.00918100000000603E7B2001.00000C407575.00
  52         1         4  direct     47.00918100000000603E7B2001.00000C407573.01
  53         9         0  distribute 47.00918100000000603E7B2001.00000C407573.01
  54         0        13  send       47.00918100000000603E7B2001.00000C407574.01
  55        19         0  forward    47.00918100000000603E7B2001.00000C407574.01
  56        11        10  data       47.00918100000000603E7B2001.00000C407572.01
  57         6         5  data       47.00918100000000603E7B2001.00000C407C02.02
 
Switch#

The following example shows the show lane client command display for the Token Ring LANE client in the ATM switch:

ATM_Switch# show lane client
LE Client ATM13/0/0.1  ELAN name: eng  Admin: up  State: operational
Client ID: 3                 LEC up for 4 minutes 58 seconds 
Join Attempt: 1              
HW Address: 0060.3e7b.2002   Type: token ring           Max Frame Size: 4544
ATM Address: 47.00918100000000603E7B2001.00603E7B2002.01
 
 VCD  rxFrames  txFrames  Type       ATM Address
   0         0         0  configure  47.00918100000000603E7B2001.00000C407575.00
  52         1         4  direct     47.00918100000000603E7B2001.00000C407573.01
  53         9         0  distribute 47.00918100000000603E7B2001.00000C407573.01
  54         0        13  send       47.00918100000000603E7B2001.00000C407574.01
  55        19         0  forward    47.00918100000000603E7B2001.00000C407574.01
  56        11        10  data       47.00918100000000603E7B2001.00000C407572.01
  57         6         5  data       47.00918100000000603E7B2001.00000C407C02.02
 
ATM_Switch#

Default Configuration for a Single Emulated LAN with a Backup LECS and LES on the ATM Switch

The following examples show how to configure two Cisco 4500 routers and one LightStream 1010 ATM switch for one emulated LAN with fault tolerance. Configurations for both Ethernet and Token Ring emulated LANs are shown.

Router 1 contains the LECS, LES, BUS, and an LEC. Router 2 contains only an LEC. The ATM switch contains the backup LECS and the backup LES for this emulated LAN, along with another LEC (see Figure 14-7).

Figure 14-7: Single Emulated LAN with Backup LANE Example Network

This example shows how to accept all default settings provided. For example, it does not explicitly set ATM addresses for the different LANE components that are also on the router. Membership in this LAN is not restricted.

Ethernet Example

Router 1

router1# show lane default-atm-addresses
interface ATM0:
LANE Client:        47.00918100000000603E7B2001.00000C407572.**
LANE Server:        47.00918100000000603E7B2001.00000C407573.**
LANE Bus:           47.00918100000000603E7B2001.00000C407574.**
LANE Config Server: 47.00918100000000603E7B2001.00000C407575.00
note: ** is the subinterface number byte in hex
 
router1#

ATM Switch

Switch# show lane default-atm-address
interface ATM2/0/0:
LANE Client:        47.00918100000000603E7B2001.00603E7B2002.**
LANE Server:        47.00918100000000603E7B2001.00603E7B2003.**
LANE Bus:           47.00918100000000603E7B2001.00603E7B2004.**
LANE Config Server: 47.00918100000000603E7B2001.00603E7B2005.00
note: ** is the subinterface number byte in hex
 
Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# atm lecs-address-default 47.00918100000000603E7B2001.00000C407575.00
Switch(config)# atm lecs-address-default 47.00918100000000603E7B2001.00603E7B2005.00
Switch(config)# end
Switch#

Router 1

router1# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router1(config)# lane database example1
router1(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.01
router1(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00603E7B2003.01
router1(lane-config-database)# default-name eng
router1(lane-config-database)# exit
router1(config)# interface atm3/0
router1(config-if)# atm pvc 1 0 5 qsaal
router1(config-if)# atm pvc 2 0 16 ilmi
router1(config-if)# lane config auto-config-atm-address
router1(config-if)# lane config database example1
router1(config-if)# 
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm3/0.1
router1(config-subif)# ip address 172.16.0.1 255.255.0.0
router1(config-subif)# lane server-bus ethernet eng
router1(config-subif)# lane client ethernet eng
router1(config-subif)# 
%LANE-5-UPDOWN: ATM0.1 elan eng: LE Client changed state to up
router1(config-subif)# end
router1#

ATM Switch

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# lane database example1_backup
Switch(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.01
Switch(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00603E7B2003.01
Switch(lane-config-database)# default-name eng
Switch(lane-config-database)# exit
Switch(config)# interface atm2/0/0 
Switch(config-if)# lane config auto-config-atm-address
Switch(config-if)# lane config database example1_backup
Switch(config-if)# 
%LANE-5-UPDOWN: ATM2/0/0 database example1_backup: LE Config Server (LECS) changed state to up
%LANE-6-LECS_INFO: ATM2/0/0: started listening on the well known LECS address
%LANE-6-LECS_INFO: LECS on interface ATM2/0/0 became a BACKUP
%LANE-6-LECS_INFO: ATM2/0/0: stopped listening on the well known LECS address
Switch(config-if)# interface atm2/0/0.1
Switch(config-subif)# ip address 172.16.0.4 255.255.0.0
Switch(config-subif)# lane server-bus ethernet eng
Switch(config-subif)# 
%LANE-5-UPDOWN: ATM2/0/0.1 elan eng: LE Server/BUS changed state to up
Switch(config-subif)# lane client ethernet eng
Switch(config-subif)# 
%LANE-5-UPDOWN: ATM2/0/0.1 elan eng: LE Client changed state to up
Switch(config-subif)# end
Switch#

Router 2

router2# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router2(config)# interface atm3/0
router2(config-if)# atm pvc 1 0 5 qsaal
router2(config-if)# atm pvc 2 0 16 ilmi
router2(config-if)# interface atm3/0.2
router2(config-subif)# ip address 172.16.0.3 255.255.0.0
router2(config-subif)# lane client ethernet eng
router2(config-subif)# 
%LANE-5-UPDOWN: ATM0.2 elan : LE Client changed state to up
router2(config-subif)# end
router2#

Token Ring Example

Router 1

router1# show lane default-atm-addresses
interface ATM3/0:
LANE Client:        47.00918100000000603E7B2001.00000C407572.**
LANE Server:        47.00918100000000603E7B2001.00000C407573.**
LANE Bus:           47.00918100000000603E7B2001.00000C407574.**
LANE Config Server: 47.00918100000000603E7B2001.00000C407575.00
note: ** is the subinterface number byte in hex
 
router1#

ATM Switch

Switch# show lane default-atm-address
interface ATM2/0/0:
LANE Client:        47.00918100000000603E7B2001.00603E7B2002.**
LANE Server:        47.00918100000000603E7B2001.00603E7B2003.**
LANE Bus:           47.00918100000000603E7B2001.00603E7B2004.**
LANE Config Server: 47.00918100000000603E7B2001.00603E7B2005.00
note: ** is the subinterface number byte in hex
 
Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# atm lecs-address-default 47.00918100000000603E7B2001.00000C407575.00
Switch(config)# atm lecs-address-default 47.00918100000000603E7B2001.00603E7B2005.00
Switch(config)# end
Switch#

Router 1

router1# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router1(config)# lane database example1
router1(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.01
router1(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00603E7B2003.01
router1(lane-config-database)# name eng local-seg-id 2048
router1(lane-config-database)# default-name eng
router1(lane-config-database)# exit
router1(config)# interface atm3/0
router1(config-if)# atm pvc 1 0 5 qsaal
router1(config-if)# atm pvc 2 0 16 ilmi
router1(config-if)# lane config auto-config-atm-address
router1(config-if)# lane config database example1
router1(config-if)# 
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm3/0.1
router1(config-subif)# ip address 172.16.0.1 255.255.0.0
router1(config-subif)# lane server-bus tokenring eng
router1(config-subif)# lane client tokenring eng
router1(config-subif)# 
%LANE-5-UPDOWN: ATM0.1 elan eng: LE Client changed state to up
router1(config-subif)# end
router1#

ATM Switch

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# lane database example1_backup
Switch(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.01
Switch(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00603E7B2003.01
Switch(lane-config-database)# name eng local-seg-id 2048
Switch(lane-config-database)# default-name eng
Switch(lane-config-database)# exit
Switch(config)# interface atm2/0/0 
Switch(config-if)# lane config auto-config-atm-address
Switch(config-if)# lane config database example1_backup
Switch(config-if)# 
%LANE-5-UPDOWN: ATM2/0/0 database example1_backup: LE Config Server (LECS) changed state to up
%LANE-6-LECS_INFO: ATM2/0/0: started listening on the well known LECS address
%LANE-6-LECS_INFO: LECS on interface ATM2/0/0 became a BACKUP
%LANE-6-LECS_INFO: ATM2/0/0: stopped listening on the well known LECS address
Switch(config-if)# interface atm2/0/0.1
Switch(config-subif)# ip address 172.16.0.4 255.255.0.0
Switch(config-subif)# lane server-bus tokenring eng
Switch(config-subif)# 
%LANE-5-UPDOWN: ATM2/0/0.1 elan eng: LE Server/BUS changed state to up
Switch(config-subif)# lane client tokenring eng
Switch(config-subif)# 
%LANE-5-UPDOWN: ATM2/0/0.1 elan eng: LE Client changed state to up
Switch(config-subif)# end
Switch#

Router 2

router2# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router2(config)# interface atm3/0
router2(config-if)# atm pvc 1 0 5 qsaal
router2(config-if)# atm pvc 2 0 16 ilmi
router2(config-if)# interface atm3/0.2
router2(config-subif)# ip address 172.16.0.3 255.255.0.0
router2(config-subif)# lane client tokenring eng
router2(config-subif)# 
%LANE-5-UPDOWN: ATM0.2 elan : LE Client changed state to up
router2(config-subif)# end
router2#

Displaying the LECS Configuration on the ATM Switch

The following example shows the show lane config command display for the LECS (Ethernet and Token Ring):

Switch# show lane config
LE Config Server ATM2/0/0 config table: example1_backup
Admin: up  State: operational
LECS Mastership State: backup
list of global LECS addresses (45 seconds to update):
47.00918100000000603E7B2001.00000C407575.00 incoming call (vcd 88)
47.00918100000000603E7B2001.00603E7B2005.00  <-------- me
ATM Address of this LECS: 47.00918100000000603E7B2001.00603E7B2005.00 (auto)
 vcd  rxCnt  txCnt  callingParty
  88      0      0  47.00918100000000603E7B2001.00000C407575.00 LECS
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 0
cumulative total number of config failures so far: 0

Displaying the LES Configuration on the ATM Switch

The following example shows the show lane server command display for the Ethernet LES:

Switch# show lane server
LE Server ATM2/0/0.1  ELAN name: eng  Admin: up  State: operational
type: ethernet         Max Frame Size: 1516
ATM address: 47.00918100000000603E7B2001.00603E7B2003.01
LECS used: 47.00918100000000603E7B2001.00000C407575.00 connected, vcd 95

The following example shows the show lane server command display for the Token Ring LANE server:

Switch# show lane server
LE Server ATM2/0/0.1  ELAN name: eng  Admin: up  State: operational
type: token ring         Max Frame Size: 4544      Segment ID: 2048
ATM address: 47.00918100000000603E7B2001.00603E7B2003.01
LECS used: 47.00918100000000603E7B2001.00000C407575.00 connected, vcd 95

Default Configuration for a Single Emulated Token Ring LAN with IP Source Routing Across a Source-Route Bridged Network

The following example shows how to configure a single emulated Token Ring LAN using a Cisco 4500 router and a LightStream 1010 ATM switch with IP source routing across a source-route bridged network. In this example, the emulated Token Ring LAN is source-route bridged to two physical Token Rings.

The router contains the LECS, LES, BUS, and an LEC. The ATM switch and Token Ring switch each contain an LEC for the emulated LAN. This example uses all LANE default settings. For example, it does not explicitly set ATM addresses for the different LANE components that are colocated on the router. Membership in this LAN is not restricted (see Figure 14-8).

Figure 14-8: Single Emulated Token Ring LAN with Token Ring Switch

Router

router# show lane default-atm-addresses
interface ATM0:
LANE Client:        47.00918100000000603E7B2001.00000C407572.**
LANE Server:        47.00918100000000603E7B2001.00000C407573.**
LANE Bus:           47.00918100000000603E7B2001.00000C407574.**
LANE Config Server: 47.00918100000000603E7B2001.00000C407575.00
note: ** is the subinterface number byte in hex
 
router#

ATM Switch

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# atm lecs-address-default 47.00918100000000603E7B2001.00000C407575.00 
Switch(config)# end
Switch#

Router

router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)# lane database example1
router(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.01
router(lane-config-database)# name eng local-seg-id 2048
router(lane-config-database)# default-name eng
router(lane-config-database)# exit
router(config)# interface atm3/0
router(config-if)# atm pvc 1 0 5 qsaal
router(config-if)# atm pvc 2 0 16 ilmi
router(config-if)# lane config auto-config-atm-address
router(config-if)# lane config database example1
router(config-if)# 
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router(config-if)# interface atm3/0.1
router(config-subif)# ip address 172.16.0.1 255.255.0.0
router(config-subif)# lane server-bus tokenring eng
router(config-subif)# lane client tokenring eng
router(config-subif)# 
%LANE-5-UPDOWN: ATM0.1 elan eng: LE Client changed state to up
router(config-subif)# end
router#

ATM Switch

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# interface atm2/0/0.1
Switch(config-subif)# ip address 172.16.0.4 255.255.0.0
Switch(config-subif)# lane client tokenring eng
Switch(config-subif)# multiring ip
Switch(config-subif)# 
%LANE-5-UPDOWN: ATM2/0/0.1 elan : LE Client changed state to up
Switch(config-subif)# end
Switch#

Table of Contents

Configuring LAN Emulation

LANE ATM Addresses

Using ATM Address Templates

Example

Example

Enable Redundant LECSs

Implementation Considerations

ATM Switch

Router 1

Catalyst 5500 Switch 1

ATM Switch

Router 1

ATM Switch

Router 1

Catalyst 5000 Switch 1

ATM Switch

Router 1

ATM Switch

Router 1

ATM Switch

Router 2

Router 1

ATM Switch

Router 1

ATM Switch

Router 2

Router

ATM Switch

Router

ATM Switch