Update to the LightStream 1010 ATM Switch Software Configuration Guide

The following is an update to the LightStream 1010 ATM Switch Software Configuration Guide. The information in this update reflects information added after printing the software configuration guide.

In Chapter 8, "Configuring Interfaces," on page 8-13, add the following sections as part of the "Configure a Public Network Tunnel Interface" section before the section "Delete Virtual Path Tunnels."

Configure Signalling VPCI for PVP Tunnels

To specify the value of the virtual path connection identifier (VPCI) that is to be carried in the signalling messages with in a VP tunnel, use the atm signalling vpci subinterface configuration command.

Note By default, the VPCI is the same as the VPI on the ATM switch.

The connection identifier information element (IE) is used in signalling messages to identify the corresponding user information flow. The connection identifier IE contains the VPCI and VCI.

For example, if you want to configure a PVP tunnel connection from a LightStream 1010 ATM switch on VPI 2, VCI X, to a router with a virtual path switch in between, the signalling message would contain connection ID, VPI 2, VCI X. Since the PVP tunnel at the router end is on VPI 3, VCI X, the connection is refused. By configuring VPCI to 3, you can configure the signalling message explicitly to contain connection ID VPI 3, VCI X, instead of containing VPI 2, VCI X.

This command can also be used to support virtual User-Network Interface (UNI) connections.

To configure a VP tunnel connection signalling VPCI, use the following EXEC commands. Use the no form of the atm signalling vpci command to disable VPCI configuration:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
interface atm card/subcard/port.vpt #

Select the subinterface.

4
atm signalling vpci vpci_number

Configure the atm signalling VPCI number 0 to 255.

5
exit

Exit subinterface configuration mode.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	interface atm card/subcard/port.vpt #	Select the subinterface.
4	atm signalling vpci vpci_number	Configure the atm signalling VPCI number 0 to 255.
5	exit	Exit subinterface configuration mode.

Example

The following example configures a PVP tunnel on ATM interface 0/0/0, PVP 99, and then configures the connection ID VCPI as 0 in subinterface configuration mode.

Switch(config)# config terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# interface atm 1/0/0
Switch(config-if)# atm pvp 99
Switch(config-if)# exit
Switch(config)# interface atm 1/0/0.99


 
  Switch(config-subif)# atm signalling vpci 0
Switch(config-subif)# end
Switch#

Display the PVP Tunnel VPCI Configuration

To confirm the PVP tunnel VPCI configuration, use the show running-config command:.

Command Task

show running-config

Show the PVP tunnel subinterface configuration.

Command	Task
show running-config	Show the PVP tunnel subinterface configuration.

In Chapter 10, "Configuring ILMI," replace the first part of the section "Configure an ILMI Interface," on page 10-6 and 10-7 with the following new information:

Configure an ILMI Interface

To configure an ILMI interface on a per-interface basis, perform the following tasks:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
interface atm card/subcard/port [.vpt#]

Select interface port.

3
atm auto-configuration

Enable ILMI auto configuration, including determination of interface protocol, version and side.

4
atm address-registration

Configure ILMI address registration for a specified interface.

5
auto-link-determination

Enable ILMI link determination feature.

6
atm ilmi-keepalive [seconds [retry retry_number]]

Configure ILMI keepalive.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	interface atm card/subcard/port [.vpt#]	Select interface port.
3	atm auto-configuration	Enable ILMI auto configuration, including determination of interface protocol, version and side.
4	atm address-registration	Configure ILMI address registration for a specified interface.
5	auto-link-determination	Enable ILMI link determination feature.
6	atm ilmi-keepalive [seconds [retry retry_number]]	Configure ILMI keepalive.

Note If the ILMI VC (by default VCI = 16) is disabled, then the ILMI is disabled.

Examples

The following example shows how to enable ILMI autoconfiguration on ATM interface 3/0/3:

Switch(config)# interface atm 3/0/3
Switch(config-if)# atm-autoconfiguration
Switch(config-if)#

The following example shows how to enable ATM address registration on ATM interface 3/0/3:

Switch(config)# interface atm 3/0/3
Switch(config-if)# atm address-registration
Switch(config-if)#

Note If you use the no atm address-registration command to disable ILMI on this interface, the keepalives and responses to incoming ILMI queries continue to function. If you want ILMI to be completely disabled at this interface, use the no atm ilmi-enable command.

The following example shows how to configure the ILMI ATM interface 3/0/3 with a keepalive time of 20 seconds and retry count of 3:

Switch(config)# interface atm 3/0/3
Switch(config-if)# atm ilmi-keepalive 20 retry 3
Switch(config-if)#

In this example, the peer network element is polled every 20 seconds.

Proceed to the following section to confirm the ILMI interface configuration.

In Chapter 13, "Configuring IP-Over-ATM and LAN Emulation," replace all sections beginning with "Configuration of LANE" to the end of the chapter with the following revised sections.

Configuration of LANE

This section describes how to configure LAN emulation (LANE) on the LightStream 1010 ATM switch.

What is LANE on ATM?

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.

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

LANE emulates a broadcast environment like 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 LANE server 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. The LANE protocol defines the operation of an emulated LAN.

The ATM LANE system has three servers that are single points of failure. These are the LANE configuration server, the LANE server, and the broadcast-and-unknown server.

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.

Note LANE on the LightStream 1010 ATM switch supports only the IP protocol.

LANE Servers and Components

A single emulated LAN consists of the following entities: A LANE configuration server, a broadcast-and-unknown server, a LANE server, and LANE clients.

LANE configuration server --- A server that assigns individual clients to particular emulated LANs by directing them to the LANE server that corresponds to the emulated LAN. The LANE configuration server maintains a database of LANE client ATM or MAC addresses and their emulated LANs. A LANE configuration server can serve multiple emulated LANs.
Broadcast-and-unknown server---A multicast server that floods unknown destination traffic and forwards multicast and broadcast traffic to clients within an emulated LAN. One Cisco broadcast-and-unknown server exists per emulated LAN.
LANE server ---A server that provides a registration facility for clients to join the emulated LAN. Each emulated LAN has one Cisco LANE server, which handles LAN Emulation Address Resolution Protocol (LE ARP) requests and maintains a list of LAN destination MAC addresses. In Token Ring LANE environments, the LANE server maintains a list of route descriptors.
LANE client---An entity in an endpoint such as a router that performs data forwarding, 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 LANE server. In Token Ring environments, a LANE client configured for source-route bridging may register a route descriptor with the LANE server.

Emulated LAN entities coexist on one or more Cisco routers. On Cisco routers, each LANE server and broadcast-and-unknown server is always a single entity. Other LANE components include ATM switches---those that supports the ILMI and signaling. Multiple emulated LANs can coexist on a single ATM network.

Implementation Considerations

The following sections contain information relevant to implementation:

Network Support
Addressing
Rules for Assigning Components to Interfaces and Subinterfaces

Network Support

In this release, Cisco supports the following LANE features:

Ethernet-emulated LANs.
Token Ring-emulated LANs.
Simple server redundancy for fault tolerance of all LANE servers

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 (server, client, broadcast-and-unknown server, and configuration server) must have an ATM address that is different from that of all the other components.

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 end-system identifier (ESI)
A 1-byte selector field

See the section "Configure the ATM Address" in the chapter "Initially Configuring the LightStream 1010 ATM Switch."

Cisco's Method of Automatically Assigning ATM Addresses for LANE

Cisco provides the following standard method of constructing and assigning ATM and MAC addresses for use in a LANE configuration server'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 switch. The prefix value must be configured on the switch.
The ESI field value assigned to every client on the interface is the first of the pool of MAC addresses assigned to the interface.
The ESI field value assigned to every server on the interface is the second of the pool of MAC addresses.
The ESI field value assigned to the broadcast-and-unknown server on the interface is the third of the pool of MAC addresses.
The ESI field value assigned to the configuration server is the fourth of the pool of MAC addresses.
The selector field value is set to the subinterface number of the LANE component---except for the LANE configuration server, 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 the ESI 0800.200c.1000.
Any server gets the ESI 0800.200c.1001.
The broadcast-and-unknown server gets the ESI 0800.200c.1002.
The LANE configuration server gets the ESI 0800.200c.1003.

Using ATM Address Templates

ATM address templates can be used 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. The use of 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 those for address templates of 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. Table 13-1 indicates 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 13-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 of 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 LANE configuration server 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, LAN components can be configured only on the ASP interface or on one of its subinterfaces.

LANE Configuration Task List

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. Bridged emulated LANs are configured just like any other LAN, in terms of commands and outputs.

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

Note For fault tolerance, multiple servers can be assigned to the emulated LAN.

Enable the Configuration Server

: An ATM cloud can contain multiple configuration servers.

Set Up LANE Servers and Clients

: You can configure multiple servers on an emulated LAN and multiple servers (LANE server/broadcast-and-unknown server) in an ATM cloud.

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 in the participating routers by completing the tasks in the following section:

Monitor and Maintain the LANE Components

See the "LANE Configuration Examples" section at the end of this chapter.

Create a LANE Plan and Worksheet

Draw up a plan and a worksheet for your own LANE scenario, showing the following information and leaving space for noting the ATM address of each of the LANE components on each subinterface of each participating router or switch:

The router and interface where the LANE configuration server will be located
The router, interface, and subinterface where the LANE server and broadcast-and-unknown server for each emulated LAN will be located; each emulated LAN, has multiple servers for fault-tolerant operation.
The routers, interfaces, and subinterfaces where the clients for each emulated LAN will be located
The name of the default emulated LAN (optional)
The names of the emulated LANs that will have unrestricted membership
The names of the emulated LANs that will 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's database.

Display LANE Default Addresses

You can display the LANE default addresses to make configuration easier. Complete this task for each router or switch that participates in LANE. This command displays default addresses for all ATM interfaces present on the router. 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.

Command	Task
show lane default-atm-addresses	Display the LANE default addresses.

Example

The following example displays the default LANE addresses:

Switch# show lane default-atm-addresses
interface ATM2/0/0:
LANE Client:        47.00918100000000400B0A2B81.0002F6900801.**
LANE Server:        47.00918100000000400B0A2B81.0002F6900802.**
LANE Bus:           47.00918100000000400B0A2B81.0002F6900803.**
LANE Config Server: 47.00918100000000400B0A2B81.0002F6900804.00
note: ** is the subinterface number byte in hex
 
Switch#

Enter the ATM Address of the Configuration Server

You must enter the configuration server's ATM address(es) into the Lightstream 1010 ATM switch and save it permanently, so that the value is not lost when the switch is reset or powered off.

On the LightStream 1010 ATM switch, the configuration server address can be specified for the entire switch, or per port.

To enter the configuration server addresses on the LightStream 1010 for the entire switch:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
atm lecs-address-default address

Specify the LANE configuration server's ATM address for the entire switch.

3
copy running-config

Save the configuration value permanently.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	atm lecs-address-default address	Specify the LANE configuration server's ATM address for the entire switch.
3	copy running-config	Save the configuration value permanently.

To enter the configuration server addresses on the LightStream 1010 per port:

Step Command Task

1
interface atm card/subcard/port [.sub_inter #]

Ensure you are in interface configuration mode.

2
atm lecs-address address

Specify the LANE configuration server's ATM address for a port.

3
copy running-config

Save the configuration value permanently.

Step	Command	Task
1	interface atm card/subcard/port [.sub_inter #]	Ensure you are in interface configuration mode.
2	atm lecs-address address	Specify the LANE configuration server's ATM address for a port.
3	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.

Set Up the Configuration Server's Database

After you have set up all servers, broadcast-and-unknown servers, and clients 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 database, complete the tasks in the following sections as appropriate for your emulated LAN plan and scenario:

Set Up the Database for the Default Emulated LAN Only
Set Up the Database for Unrestricted-Membership Emulated LANs
Set Up the Database for Restricted-Membership LANs

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

Set Up the Database for the Default Emulated LAN Only

When you configure a router as the configuration server for one default emulated LAN, you provide 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), and 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 server's 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 configuration server for the default emulated LAN, complete the following steps:

Step Commands Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
lane database database-name

Create a named database for the LANE configuration server.

3
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 LANE server.

4
name elan-name local-seg-id seg-num

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

5
default-name elan-name

In the configuration database, provide a default name for the emulated LAN.

6
exit

Exit from database configuration mode and return to global configuration mode.

Step	Commands	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	lane database database-name	Create a named database for the LANE configuration server.
3	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 LANE server.
4	name elan-name local-seg-id seg-num	(Token Ring only) In the configuration database, specify the ring number for the emulated LAN.
5	default-name elan-name	In the configuration database, provide a default name for the emulated LAN.
6	exit	Exit from database configuration mode and return to global configuration mode.

In Step 3, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet and obtained in the "Display 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 3 is the same as the default emulated LAN name you provide in Step 5.

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

For examples of these commands, see the section "LANE Configuration Examples" at the end of 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 LANE clients locations. 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 configuration server for multiple emulated LANs with unrestricted membership, complete the following steps:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
lane database database-name

Create a named database for the LANE configuration server.

3
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 LANE server for that emulated LAN.

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

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

5
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 LANE server.

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

6
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.

7
default name elan-name1

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

8
exit

Exit from database configuration mode and return to global configuration mode.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	lane database database-name	Create a named database for the LANE configuration server.
3	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 LANE server for that emulated LAN.
4	name elan-name1 local-seg-id seg-num	(Token Ring only) In the configuration database, specify the ring number for the first emulated LAN.
5	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 LANE server. Repeat this step, providing a different emulated LAN name and an ATM address, for each additional emulated LAN in this switch cloud.
6	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.
7	default name elan-name1	(Optional) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN.
8	exit	Exit from database configuration mode and return to global configuration mode.

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

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

For examples of these commands, see the section "LANE Configuration Examples" at the end of 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 6, in 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, perform the following steps:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
lane database database-name

Create a named database for the LANE configuration server.

3
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 LANE server for that emulated LAN.

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

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

5
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 LANE server.

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

6
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.

7
d efault name elan-name1

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

8
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.

9
exit

Exit from database configuration mode and return to global configuration mode.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	lane database database-name	Create a named database for the LANE configuration server.
3	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 LANE server for that emulated LAN.
4	name elan-name1 local-seg-id seg-num	(Token Ring only) In the configuration database, specify the ring number for the first emulated LAN.
5	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 LANE server. Repeat this step, providing a different name and a different ATM address, for each additional emulated LAN.
6	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.
7	d efault name elan-name1	(Optional) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN.
8	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.
9	exit	Exit from database configuration mode and return to global configuration mode.

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

Enable the Configuration Server

Once you have created the database entries appropriate to the type and 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, perform the following steps:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
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.

3
lane config database database-name

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

4
lane config auto-config-atm-address

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

5
exit

Exit interface configuration mode.

6
Ctrl-Z

Return to EXEC mode.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	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.
3	lane config database database-name	Link the configuration server's database name to the specified major interface, and enable the configuration server.
4	lane config auto-config-atm-address	Specify that the configuration server's ATM address will be computed by Cisco's automatic method.
5	exit	Exit interface configuration mode.
6	Ctrl-Z	Return to EXEC mode.

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

Set Up LANE Servers and Clients

For each router 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 LANE configuration server will be located.

For one default emulated LAN, you will have one set of servers to set up: 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 broadcast-and-unknown server 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 LS1010, multiring must be configured to enable 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, Broadcast-and-Unknown Server, and a Client on a Subinterface

To set up the server, broadcast-and-unknown server, and (optionally) clients for an emulated LAN, perform the following steps:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

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

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

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

Enable a LANE server and a LANE broadcast-and-unknown server for the first emulated LAN.

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

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

5
ip address address

Provide a protocol address for the client.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	interface atm 2/0/0[.sub_inter #]	Specify the subinterface for the first emulated LAN on this router.
3	lane server-bus {ethernet \| tokenring} elan-name1	Enable a LANE server and a LANE broadcast-and-unknown server for the first emulated LAN.
4	lane client {ethernet \| tokenring} [elan-name1]	(Optional) Enable a LANE client for the first emulated LAN.
5	ip address address	Provide a protocol address for the client.

If the emulated LAN in Step 4 is intended to have restricted membership, consider carefully whether you want to specify its name here. You will specify the name in the LANE configuration server's database when it is set up. However, if you link the client to an emulated LAN , and through 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 emulated LAN or any other.

If you do decide to include the name of the emulated LAN linked to the client in Step 4 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 5 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:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

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

Specify the subinterface for an emulated LAN on this router.

3
ip address address

Provide a protocol address for the client on this subinterface.

4
lane client {ethernet | tokenring} elan-name1

Enable a LANE client for the first emulated LAN.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	interface atm 2/0/0[.sub_inter #]	Specify the subinterface for an emulated LAN on this router.
3	ip address address	Provide a protocol address for the client on this subinterface.
4	lane client {ethernet \| tokenring} elan-name1	Enable a LANE client for the first emulated LAN.

Each emulated LAN is a separate subnetwork. In Step 3, 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.

Configure a LAN Emulation Client on the Switch

This section describes configuring a LAN Emulation (LANE) client connection from the LightStream 1010 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.

To configure interface 2/0/0 as a LANE client on the LightStream 1010 switch requires configuring the LANE client as described in the following section.

Configure an Ethernet LANE Client

To configure the interface 2/0/0 as an Ethernet LANE client on the LightStream 1010 switch, use the following EXEC commands:

Step Command Task

1
configure
[terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2
atm lecs-address lecs-address

Specify the address to the LECS.

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

Select the interface to be configured.

4
lane client-atm-address atm-address-template

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

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

Configure a LANE client on the specified subinterface.

Step	Command	Task
1	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
2	atm lecs-address lecs-address	Specify the address to the LECS.
3	interface atm 2/0/0[.sub_inter #]	Select the interface to be configured.
4	lane client-atm-address atm-address-template	Specify an ATM address, and override the automatic ATM address assignment for the LANE client.
5	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:

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-atm-address...0800.200C.1001.**
Switch(config-if)# lane client ethernet mis

In order, the commands in this example:

1. Set the LANE configuration server (LECS) ATM address = 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.

Configure Fault-Tolerant Operation

The LANE simple server redundancy feature creates fault tolerance using standard LANE protocols and mechanisms. If a failure occurs on the LANE configuration server or on the LANE server/broadcast-and-unknown server, the emulated LAN can continue to operate using the services of a backup LANE server. 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.

Understand Simple Server Redundancy

You can define redundant LANE configuration servers by configuring one or more server addresses---obtained through the Interim Local Management Interface (ILMI)---on the ATM switch. The LANE configuration server 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 LANE server addresses. This mechanism is specified in the LANE standard. The LANE servers 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 LANE configuration servers.

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.

The LANE protocol does not specify the location of any emulated LAN server entities. However, Cisco implements these server components on its routers for reliability and performance,.

With the earlier implementation of LANE, only one LANE configuration server, capable of serving multiple emulated LANS, and only one LANE server/broadcast-and-unknown server per emulated LAN could exist for an ATM switch cloud. The earlier LANE protocol did not allow for multiple LANE servers within an emulated LAN. Therefore, these components represented both single points of failure and potential bottlenecks for LANE service.

LANE simple server redundancy corrects these limitations by allowing backup LANE configuration servers and LANE server/broadcast-and-unknown servers 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 LANE configuration servers and LANE server/broadcast-and-unknown server combinations. Third-party LANE components continue to interoperate with the LANE configuration server and LANE server/broadcast-and-unknown server function of Cisco routers, but cannot take advantage of the redundancy features.

Enable Redundant LANE Configuration Servers

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

To enable fault tolerance, you enable multiple, redundant, and standby LANE configuration servers and multiple, redundant, and standby LANE server/broadcast-and-unknown servers. Cisco LANE continues to operate seamlessly with other vendors' LANE components, but fault tolerance is not effective in this situation.

To configure multiple LANE server/broadcast-and-unknown servers for emulated LANs on the routers or switches, perform the following steps:

Step Command Task

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

Specify redundant LANE server/broadcast-and-unknown servers, or simple server replication. Enter the command for each LANE server address for the same emulated LAN. The index determines the priority. 0 is the highest priority.

2
lane client {ethernet | tokenring} elan-name1

Enable a LANE client for the first emulated LAN.

Step	Command	Task
1	name elan-name server-atm-address address index n	Specify redundant LANE server/broadcast-and-unknown servers, or simple server replication. Enter the command for each LANE server address for the same emulated LAN. The index determines the priority. 0 is the highest priority.
2	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 LANE server components are running. This includes all the ATM interface cards in Cisco routers and Catalyst switches. Fault tolerance is not effective for ATM network or switch failures.

For server redundancy to work correctly:

All the ATM switches must have identical lists of the global LANE configuration server addresses, in the identical priority order.
The operating LANE configuration servers must use exactly the same configuration database. Load the configuration table data using the config net 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

Up to 16 LANE configuration server addresses can be handled by the LANE subsystem.
No limit exists on the number of LANE servers that can be defined per emulated LAN.
When a LANE configuration server switchover occurs, no previously joined clients are affected.
When a LANE server/broadcast-and-unknown server switches over, momentary loss of clients occurs until they are all transferred to the new LANE server/broadcast-and-unknown server.
LANE configuration servers come up automatically as masters until a higher-level LANE configuration server tells them otherwise.
If a higher-priority LANE server comes online, it bumps the current LANE server off on the same emulated LAN. Therefore, there might be some changing of clients from one LANE server to another after a powerup, depending on the order of the LANE servers coming up. Changing should settle after the last highest-priority LANE server comes up.
If none of the specified LANE servers are up or connected to the master LANE configuration server and more than one LANE server is defined for an emulated LAN, a configuration request for that specific emulated LAN is rejected by the LANE configuration server.
Changes made to the list of LANE configuration server addresses on ATM switches can take up to a minute to propagate through the network. Changes made to the configuration database regarding LANE server addresses take effect almost immediately.
If none of the designated LANE configuration servers are operational or reachable, the ATM Forum-defined well-known LANE configuration server address is used.
You can override the LANE configuration server 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 an override like this is performed, fault-tolerant operation cannot be guaranteed. To avoid affecting the fault-tolerant operation, do not override any LANE configuration server, LANE server or broadcast-and-unknown server addresses.

If an underlying ATM network failure occurs, there might be multiple master LANE configuration servers and multiple active LANE servers 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.

Monitor and Maintain 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, perform the following tasks in EXEC mode:

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 broadcast-and-unknown server 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 LANE configuration server'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 LANE server 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 broadcast-and-unknown server 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 LANE configuration server'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 LANE server 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 LANE configuration server and LANE server 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 "Cisco's 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 two Cisco 4500 routers and one LightStream 1010 ATM switch for a single emulated LAN. Configurations for both Ethernet and Token Ring emulated LANs are shown.

Router 1 contains the configuration server, the server, the broadcast-and-unknown server, and a client. The remaining router and ATM switch each contain a client 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 13-1).

Figure 13-1: Single Emulated LAN Example Network

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# 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 example1
router1(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.01
router1(lane-config-database)# default-name eng
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 example1
router1(config-if)#
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm0.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
router1(config-subif)#
%LANE-5-UPDOWN: ATM0.1 elan eng: LE Client changed state to up
router1(config-subif)# end
router1#

Router 2

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

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 ethernet
Switch(config-subif)#
%LANE-5-UPDOWN: ATM2/0/0.1 elan : LE Client changed state to up
Switch(config-subif)# end
Switch#

Token Ring 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# 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 example1
router1(lane-config-database)# name eng server-atm-address 47.00918100000000603E7B2001.00000C407573.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 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 example1
router1(config-if)#
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm0.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
router1(config-subif)#
%LANE-5-UPDOWN: ATM0.1 elan eng: LE Client changed state to up
router1(config-subif)# end
router1#

Router 2

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

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
Switch(config-subif)#
%LANE-5-UPDOWN: ATM2/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:

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

Switch# show lane client
LE Client ATM2/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:

Switch# show lane client
LE Client ATM2/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
Ring:100    Bridge:2        ELAN Segment ID: 2048
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#

Default Configuration for a Single Emulated LAN with a Backup LANE Configuration Server and LANE Server 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 configuration server, the server, the broadcast-and-unknown server, and a client. Router 2 contains only a client. The ATM switch contains the backup LANE configuration server and the backup LANE server for this emulated LAN and another client (see Figure 13-2).

Figure 13-2: 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 colocated 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 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 example1
router1(config-if)#
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm0.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
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
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 atm0
router2(config-if)# atm pvc 1 0 5 qsaal
router2(config-if)# atm pvc 2 0 16 ilmi
router2(config-if)# interface atm0.2
router2(config-subif)# ip address 172.16.0.3 255.255.0.0
router2(config-subif)# lane client ethernet
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 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)# name eng local-seg-id 2048
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 example1
router1(config-if)#
%LANE-5-UPDOWN: ATM0 database example1: LE Config Server (LECS) changed state to up
router1(config-if)# interface atm0.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
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 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
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 atm0
router2(config-if)# atm pvc 1 0 5 qsaal
router2(config-if)# atm pvc 2 0 16 ilmi
router2(config-if)# interface atm0.2
router2(config-subif)# ip address 172.16.0.3 255.255.0.0
router2(config-subif)# lane client tokenring
router2(config-subif)#
%LANE-5-UPDOWN: ATM0.2 elan : LE Client changed state to up
router2(config-subif)# end
router2#

Displaying the LANE Configuration Server Configuration on the ATM Switch

The following example shows the show lane config command display for the LANE configuration server (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 LANE Server Configuration on the ATM Switch

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

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 Ethernet 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 includes two physical rings, which are source-route bridged over a Token Ring switch.

The router contains the configuration server, the server, the broadcast-and-unknown server, and a client. The ATM switch and Token Ring switch each contain a client 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 13-3).

Figure 13-3: 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 atm0
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 atm0.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
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
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#

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

Table of Contents

Update to the LightStream 1010 ATM Switch Software Configuration Guide

Example

Examples

Example

Example

Router 1

ATM Switch

Router 1

Router 2

ATM Switch

Router 1

ATM Switch

Router 1

Router 2

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