|
|
LAN Emulation (LANE) essentially bridges LAN traffic across an Asychronous Transfer Mode (ATM) network. The Catalyst 5000 Series Token Ring LANE feature emulates an IEEE 802.5 Token Ring LAN using ATM technology. LANE is transparent to upper-layer protocols and applications. No changes are required to existing upper-layer protocols and applications. With Token Ring LANE, Token Ring packets are encapsulated in the appropriate ATM cells and sent across the ATM network. When the packets reach the other side of the ATM network, they are de-encapsulated.
This configuration note describes how to configure Token Ring LANE in Catalyst 5000 series switches that contain an ATM Line Card (ALC) and are connected to a LightStream 1010 ATM switch. For more information on LANE and Catalyst 5000 series switches, refer to the documentation for the Catalyst 5000 series switch.
This document contains the following sections:
This section contains the following information:
ATM is a cell-switching and multiplexing technology that combines the benefits of circuit switching (constant transmission delay and guaranteed capacity) with those of packet switching (flexibility and efficiency for intermittent traffic). Like X.25 and Frame Relay, ATM defines the interface between the user equipment (such as workstations and routers) and the network (referred to as the User-Network Interface [UNI]).
Token Ring LANE allows Token Ring LAN users to take advantage of ATM's benefits without modifying end-station hardware or software. ATM uses connection-oriented service with point-to-point signaling or multicast signaling between source and destination devices. However, Token Ring LANs use connectionless service. Messages are broadcast to all devices on the network. With Token Ring LANE, routers and switches emulate the connectionless service of a Token Ring LAN for the end stations.
By using Token Ring LANE, you can scale your networks to larger sizes while preserving your investment in LAN technology.
LANE defines emulated LANs (ELANs). An ELAN consists of the following components:
The Catalyst 5000 series switch must contain an ALC running ATM software release 70.1 or later. These ALCs provide an ATM network interface for the Catalyst 5000 series switch. Network interfaces reside on modular interface processors, which provide a direct connection between the high-speed synergy backplane and the external networks. The maximum number of ALCs that the switch supports depends on the bandwidth configured.
The Catalyst 5000 series Token Ring LANE software requires the 3.2(203) upgrade to the Catalyst 5000 series Network Management Processor (NMP) release 3.2(1b) software. For instructions on obtaining this upgrade, see the "Downloading the Catalyst 5000 NMP Interim Software from CCO" section.
The Catalyst 5000 series Token Ring LANE feature also requires one of the following switches:
The Catalyst 5000 series Token Ring LANE supports the following networking features:
The Cisco implementation of LAN emulation over 802.5 uses existing terminology and configuration options for Token Rings and provides for the 802.5 transport of Token Ring frames across an ATM switching fabric.
For additional information that may be helpful in using the Catalyst 5000 series Token Ring LANE feature, refer to the documentation for the Catalyst 5000 series switch. The documentation for the Catalyst 5000 series switch can be obtained through Cisco Connection Online (CCO). For information on CCO, see the "Cisco Connection Online" section.
This section describes possible unexpected behavior and other known problems for Catalyst 5000 series Token Ring LANE software release 70.1(1).
Problem Identifier: CSCdj38378
Problem Description: After modifying the configuration of an LEC, the show lane client command output displays the LECs in the wrong order. The functionality of the LEC is not affected in any way by this incorrect display.
Recommended Action: To view the LECs in the correct order, reset the ALC.
Problem Identifier: CSCdj69980
Problem Description: The ALC does not drop all-routes explorer (ARE) frames that have already traversed a ring. This increases broadcast traffic because AREs are being passed onto rings they have already traveled.
Recommended Action: Run the IBM Spanning-Tree Protocol and configure endstations to send spanning-tree explorer frames rather than ARE frames.
Problem Identifier: CSCdj84517
Problem Description: When in interface configuration mode (atm0), the clear counters command does not clear the MAC and port counters.
Recommended Action: To accurately monitor hardware counters, identify the counters values using the show counters command before executing tests and after executing tests and use those numbers to calculate the valid counters values.
Problem Identifier: CSCdk07590
Problem Description: Loops can occur when configuring parallel ELANs between Catalyst 5000 series switches.
Recommended Action: Do not configure parallel paths using only ATM modules. If you configure a parallel path via an ATM module and ISL, ensure that the port cost and priority for the ATM port are configured such that the ATM port will be the preferred path (the lowest port cost with the highest priority).
The Catalyst 5000 Token Ring LANE release 70.1(1) software requires the 3.2(203) interim image of the Catalyst 5000 NMP software. You can download this image via CCO Special File Access.
To download the NMP 3.2(203) interim image:
Step 1 Log into CCO and click on Software & Support.
Step 2 From the Software & Support page, click on Switching Products in the Software Center section.
Step 3 From the Switching Products page, click on Special File Access in the Tools & Info section. You are then prompted for a special access code. The special access code to obtain the NMP 3.2(203) interim image is NMPzabar.
Step 4 In the Special Access Code field, enter NMPzabar and click Execute.
Step 5 Click on cat5000-sup.3-2-203.bin and select a CCO Server to download the file.
Step 6 Continue the download process until you have placed the file in the desired directory on your system.
Step 7 Download the software to the supervisor module using the instructions provided in the "Catalyst 5000 Series Software Configuration Guide."
This section describes how to update the software on the Catalyst 5000 series switch ATM module for Token Ring LANE support by initiating the network download from the Catalyst 5000 series switch through a Trivial File Transfer Protocol (TFTP) server.
Perform the following steps to download software using TFTP:
Step 1 Make sure the computer acting as the download server is running the TFTP daemon.
Step 2 On Sun workstations, make sure the /etc/inetd.conf file contains the following line:
tftp dgram udp wait root /usr/etc/in.tftpd in.tftpd -p -s /tftpboot
Make sure the /etc/services file contains the following line:
tftp 69/udp
Step 3 Copy the new software from the floppy disks to the home directory specified for the TFTP daemon on the workstation (usually /tftpboot). If this directory does not exist, create it before continuing. The file you copy is cat5000-atm-trlane.70-1-xxx.bin, where xxx is the software revision number.
Step 4 Log in to the Catalyst 5000 series switch through the administrative interface or through a Telnet session.
Step 5 Enter the download command. Specify the IP address or host name of the workstation acting as the download server, the file to download, and the module number of the ATM module. If you do not specify a module number, the download command downloads an image based on the download header type. The following is the command syntax to download the image:
download host file module_num
In the following example, the download server is 190.180.122.40 and the ATM module is in slot number 5:
Console> (enable) download 190.180.122.40 cat5000-atm-trlane.70-1-xxx.bin 5
Step 6 When the following prompt appears, type y and press Enter:
Download image cat5000-atm-trlane.70-1-xxx from 190.180.122.40 to Module 5 FLASH (y/n) [n]? y
The Catalyst 5000 series switch erases the code and automatically resets the module with the downloaded code. As the module is reset, the following messages display:
Download done, Please wait for Module On Line message Finished network single module download. (2025756 bytes) Please do not reset module before module on line message appears! Console> (enable) 10/10/1997,07:42:49:SYS-5:Module 5 is online.
Step 7 Enter the show version command to check the file you have just downloaded. If the version number is the correct number for the new software, the download was successful. If the version number is not the correct number, the download failed, and you must repeat the download procedure. Refer to the troubleshooting procedures in the next section if the download failed.
Console> (enable) show version
WS-C5000 Software, Version McpSW: 3.2(101) NmpSW: 3.2(101)
Copyright (c) 1995-1998 by Cisco Systems
NMP S/W compiled on Feb 19 1998, 18:13:43
MCP S/W compiled on Feb 19 1998, 15:11:58
System Bootstrap Version: 2.2(181)
Hardware Version: 0.214 Model: WS-C5000 Serial #: 001905909
Module Ports Model Serial # Hw Fw Fw1 Sw
------ ----- ---------- --------- ------ ------- -------
--------------------
1 2 WS-X5509 001905909 0.214 2.2(181 2.2(181 3.2(101)
2 24 WS-X5010 003621378 2.4 1.1 3.2(101)
3 16 WS-X5030 009000032 0.34 3.1(305 2.2(4) 3.1(305)
5 1 WS-X5155 002748206 1.0 1.2 1.320 0.0
DRAM FLASH NVRAM
Module Total Used Free Total Used Free Total Used Free
------ ------- ------- ------- ------- ------- ------- ----- ----- -----
1 16384K 7805K 8579K 8192K 3840K 4352K 256K 104K 152K
Uptime is 1 day, 2 hours, 41 minutes
Console> (enable)
Follow these steps to troubleshoot a failed download procedure:
Step 1 Make certain that the Catalyst 5000 series switch has a route to the TFTP server, and enter the ping command to test this connectivity.
Step 2 Make certain that the software image to be downloaded is in the correct directory.
If the network download procedure fails because the power was interrupted during the download procedure, or for some other reason, you will be prompted to start the download procedure. If this occurs, restart the download procedure as described in the "Downloading the Software" section.
LANE provides connectivity between ATM-attached devices and LAN-attached devices, including the following:
Because LANE connectivity is defined at the MAC layer, upper-protocol layer functions of LAN applications can continue unchanged when the devices join ELANs. This feature protects corporate investments in legacy LAN applications.
An ATM network can support multiple independent ELANs. End-system membership in any of the ELANs is independent of the physical location of the end system. This characteristic simplifies hardware moves and changes. In addition, the end systems can move easily from one ELAN to another, whether or not the hardware moves. Figure 1 shows an ATM LANE configuration.
On the Catalyst 5000 series switch, a VLAN is a logical group of end stations, independent of physical location, with a common set of requirements. Currently, the Catalyst 5000 series switch supports a port-centric VLAN configuration. All end stations connected to ports belong to the same VLAN and are assigned to the same VLAN number. The VLAN number is only significant to the Catalyst 5000 series switch.
Within a Token Ring VLAN, logical rings can be formed by defining groups of ports that have the same ring number. These logical groupings of rings are called a Token Ring Concentrator Relay Function (TrCRF). A TrCRF is limited to the ports in a Catalyst 5000 series switch. Within the TrCRF, source-route switching is used for forwarding based on either MAC addresses or route descriptors. Frames can be switched between ports within a single TrCRF.
Multiple TrCRFs can be interconnected using a single Token Ring Bridge Relay Function (TrBRF). The connection between the TrCRF and the TrBRF is referred to as a logical port. For source routing, the switch appears as a single bridge between the logical rings. The TrBRF can function as an SRB or SRT bridge running either the IBM or IEEE Spanning-Tree Protocol. If SRB is used, duplicate MAC addresses can be defined on different logical rings.
On an ATM network, a VLAN or TrCRF is called an ELAN and is designated by a name. You can configure some ELANs from a router and some from a Catalyst 5000 series switch. You can configure some ELANs with unrestricted membership and some with restricted membership. You can also configure a default ELAN, which must have unrestricted membership.
To create a Token Ring VLAN that spans multiple Catalyst 5000 series switches over an ATM network, you must assign an LEC within each TrCRF on each Catalyst 5000 series switch to the same ELAN. To link the TrCRF number with the ELAN name, enter the lane client tokenring vlan_id elan_name command. You must use a router to allow communication between two or more ELANs, whether they are on the same or different Catalyst 5000 series switches.
Each VLAN corresponds to an ELAN. Each association between the ATM module and a VLAN creates an LEC which is a virtual port in the corresponding TrCRF.
Communication among LANE components is ordinarily handled by several types of switched virtual channel connections (VCCs). Some VCCs are unidirectional; others are bidirectional. Some are point-to-point, and others are point-to-multipoint. Figure 2 illustrates the various types of VCCs.
The following sections describe the various process that occur, starting with an LEC requesting to join an ELAN.
The following process normally occurs after an LEC has been enabled on the ATM module in a Catalyst 5000 series switch:
1. The LEC requests to join an ELAN. The LEC sets up a connection to the LECS to find the ATM address of the LES for its ELAN. See the bidirectional, point-to-point link (link1-7 in Figure 2).
The LEC sets up a connection to the LECS (bidirectional, point-to-point Configure Direct VCC, link 3-11 in Figure 2) to find the ATM address of the LES for its ELAN.
The LEC find the LECS by using the following interface and addresses in the listed order:
(a) Locally configured ATM address
(b) ILMI
(c) Fixed address defined by the ATM Forum
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's ELAN.
3. The LEC tears down the Configure Direct VCC.
4. The LEC contacts the LES for its LAN. The LEC sets up a connection to the LES for its ELAN (bidirectional, point-to-point Control Direct VCC, link 1-7 in Figure 2) to exchange control traffic. Once a Control Direct VCC is established between an LEC and an LES, it remains established.
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 2).
The LES configuration request contains the LEC's MAC address, its ATM address, and the name of the ELAN. The LECS checks its database to determine whether the LEC can join that LAN; then it uses the same VCC to inform the LES whether or not the LEC is allowed to join.
6. The LES determines whether the LEC is allowed 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 2) and confirms the join over the bidirectional, point-to-point Control Direct VCC (link 1-7 in Figure 2). If the LEC is not allowed, the LES rejects the join over the bidirectional, point-to-point Control Direct VCC (link 1-7 in Figure 2).
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 2) and the BUS adds the LEC to the multicast forward VCC (link 5-10 in Figure 2) to and from the BUS.
8. The LEC registers the ring numbers of all other TrCRFs within its TrBRF that contain active ports on the local switch.
On a LAN, packets are addressed by the MAC-layer addresses of the destination and source stations. To provide similar functionality for LANE, MAC-layer addressing must be supported. Every LEC must have a MAC address. In addition, every LANE component (LECS, LES, BUS, and LEC) must have a unique ATM address.
All LECs on the same interface have the same automatically assigned MAC address. That MAC address is also used as the end-system identifier part of the ATM address, as explained in the following section. Although LEC MAC addresses are not unique, all ATM addresses are unique.
A LANE ATM address has the same syntax as an network service access point (NSAP), but it is not a network-level address. It consists of the following:
The Catalyst 5000 series switch builds its ATM address by obtaining its ATM address prefix from the ATM switch. To build its ATM address, the module obtains its ATM address prefix from the ATM switch and then combines the ATM address prefix with its own MAC address and the LEC subinterface number. Once the Catalyst ATM module has determined its ATM address, it uses ILMI registration to register this address with the ATM switch.
Using the atm vc-per-vp command, you can configure the maximum number of virtual channel identifiers (VCIs) per virtual path identifier (VPI). If this value is configured when the Catalyst 5000 ATM module registers with the ATM switch, the maximum number of VCIs per VPI is passed to the ATM switch. In this way, the ATM switch assigns to the Catalyst 5000 series switch a VCI value for a switched virtual circuit (SVC) that is within the ATM switch range. The default is 10 VCI bits, and 2 VPI bits on the Catalyst 5000 ATM module. Any change from the default requires an ATM module reset.
As communication occurs on the ELAN, each LEC dynamically builds a local LE_ARP table. The LE_ARP table maps ELAN MAC addresses (Layer 2) to ATM addresses (also Layer 2). An LEC's LE_ARP table can also have static, preconfigured entries.
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 beyond 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:
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 2).
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 2).
3. Any LEC that recognizes the MAC address responds with its ATM address (point-to-point Control Direct VCC, link 1-7 in Figure 2).
4. The LES forwards the response (point-to-multipoint Control Distribute VCC, link 2-8 in Figure 2).
5. The LEC adds the MAC address-ATM address pair to its LE_ARP cache.
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 2).
For unknown destinations, 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.
Cisco provides the following method of constructing and assigning ATM and MAC addresses in an LECS database. A pool of MAC addresses is assigned to each ATM module. The pool contains 16 MAC addresses. For constructing ATM addresses, the following assignments are made to the LANE components:
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 Catalyst 5000 series switch. For more information about assigning components to subinterfaces, see the "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.100F, the end-system identifier part of the ATM addresses is assigned to LANE components as follows:
You can use ATM address templates in many LANE commands. These templates can assign ATM addresses to LANE components (thus overriding automatically assigned ATM addresses) or link LEC ATM addresses to ELANs, simplifying the use of LANE commands. ATM address templates are very similar to the address templates used by the International Standards Organization (ISO) Connectionless Network Service (CLNS).
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 end-system identifier and selector fields. An end-system identifier template explicitly matches the end-system identifier field but uses wildcards for the prefix and selector field. Table 1 indicates how the values of unspecified bytes are determined when an ATM address template is used.
| Unspecified Digits | Value Location |
|---|---|
Prefix (first 13 bytes) | Switch via ILMI, or configured locally if ILMI is not supported on the switch. |
End-system identifier (next 6 bytes) | Slot MAC address1 plus
|
Selector field (last byte) | Subinterface number, in the range 0 through 255. |
| 1The Catalyst 5000 series switch ATM module has a pool of 16 MAC addresses. |
When an LEC sends broadcast, multicast, or unicast traffic with an unknown address, the following process occurs:
The following rules apply to assigning LANE components on the major ATM interface and its subinterfaces:
You can open a session with the ATM module in the Catalyst 5000 series switch by entering the session command from the supervisor Console> prompt. After opening the session, you see the ATM> prompt. You the have direct access only to the ATM module with which you have established a session.
The ATM module uses a subset of the Cisco IOS software. Generally, the Cisco IOS software works the same on the ATM module as it does on routers.
After configuring the ATM module, you are ready to implement LANE.
The ATM LANE has the following default configuration:
The ATM module user interface provides access to several different command modes, including the following modes:
Each command mode provides a variety of available commands. For information about each of these modes, including how to access them, refer to the documentation for the Catalyst 5000 series switch.
To configure the ATM module, you must use the ATM configuration mode. To enter global configuration mode, enter the configure EXEC command at the privileged EXEC prompt (ATM#). You see the following message, which asks you to specify the terminal, the nonvolatile RAM (NVRAM), or a file stored on a network server as the source of configuration commands:
Configuring from terminal, memory, or network [terminal]?
If you specify terminal, the run-time configuration is used. You can then save the run-time configuration into the NVRAM. If you specify memory, the run-time configuration is updated from the NVRAM. If you specify network, the run-time configuration is updated from a file in a server on the network.
The ATM module accepts one configuration command per line. You can enter as many configuration commands as you want.
You can add comments to a configuration file describing the commands you have entered. Precede a comment with an exclamation point (!) or the pound sign (#). Comments are not stored in NVRAM or in the active copy of the configuration file. In other words, comments do not appear when you list the active configuration with the write terminal EXEC command or list the configuration in NVRAM with the show configuration EXEC command. Comments are stripped out of the configuration file when it is loaded to the ATM module.
To configure the ATM module from the terminal, complete the following steps in privileged EXEC mode:
| Task | Command |
|---|---|
Step 1 Enter global configuration mode, selecting the terminal option. | configure terminal |
Step 2 Enter the necessary configuration commands. | Refer to the Catalyst 5000 Series Command Reference and the "Command Reference" section for more information about specific commands. |
Step 3 Quit global configuration mode. | Ctrl-Z |
Step 4 Save the configuration file modifications to NVRAM. | write memory |
In the following example, the ATM module is configured from the terminal. The interface atm 0 command designates that the ATM interface 0 is to be configured. Then the lane client tokenring command links TrCRF 10 to the ELAN named trcrf-10. The Ctrl-Z command quits configuration mode. The write memory command loads the configuration changes into NVRAM on the ATM module.
ATM# configure terminal ATM (config)# interface atm 0 ATM (config)# lane client tokenring 10 trcrf-10 ATM (config)# Ctrl-Z ATM# write memory
NVRAM stores the current configuration information in text format as configuration commands, recording only nondefault settings. The ATM module software performs a memory checksum to guard against corrupted data.
As part of its startup sequence, the ATM module startup software always checks for configuration information in NVRAM. If NVRAM holds valid configuration commands, the ATM module executes the commands automatically at startup. If the ATM module detects a problem with its NVRAM or the configuration it contains, the module goes into default configuration. Problems can include a bad checksum for the information in NVRAM or the absence of critical configuration information.
You can configure the ATM module from NVRAM by reexecuting the configuration commands stored in NVRAM. To do so, complete this task in privileged EXEC mode:
| Task | Command |
|---|---|
Configure the ATM module from NVRAM. | configure memory |
Before you implement Token Ring LANE, be aware of the following:
Before you begin to configure Token Ring LANE, you must decide whether you want to set up one or multiple ELANs. If you set up multiple ELANs, you must also decide where the servers and LECs will be located, and whether to restrict the clients that can belong to each ELAN. Bridged ELANs are configured just like any other LAN, in terms of commands and outputs. Once you have made those decisions, you can proceed to configuring Token Ring LANE.
To configure Token Ring LANE, first complete the tasks in the following sections:
It might help you to begin by drawing 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 switch:
Before you configure LANE components on a Catalyst 5000 series switch ATM module, you must configure the Cisco LightStream 1010 switch with the ATM address prefix to be used by all LANE components in the switch cloud.
To set the ATM address prefix, complete the following tasks on the Cisco LightStream 1010 switch, beginning in global configuration mode:
| Task | Command |
|---|---|
Set the local node ID (prefix of the ATM address). | atm address {atm_address | prefix...} |
Exit global configuration mode. | exit |
Save the configuration values permanently. | copy running-config startup-config |
On the Cisco LightStream 1010 switch, you can display the current prefix by using the show network command.
You must ensure that the signaling PVC and the PVC that will communicate with the ILMI on the major ATM interface of any Catalyst 5000 series switch that participates in LANE are set up.
Complete this task only once for a major interface. You do not need to repeat this task on the same interface even though you might configure LESs and clients on several of its subinterfaces.
To set up these PVCs, complete the following steps, beginning in global configuration mode:
| Task | Command |
|---|---|
Step 1 Specify the major ATM interface and enter interface configuration mode. | interface atm slot/port |
Step 2 Set up the signaling PVC that sets up and tears down SVCs; the vpi and vci values are usually set to 0 and 5, respectively. | atm pvc vcd1 vpi vci qsaal |
Step 3 Set up a PVC to communicate with the ILMI; the vpi and vci values are usually set to 0 and 16, respectively. | atm pvc vcd vpi vci ilmi |
| 1VCD = virtual channel descriptor. |
You can display the LANE default addresses to make configuration easier. Complete this task for each Catalyst 5000 series switch ATM interface that participates in LANE. This command will display default addresses for all ATM interfaces present on the switch. Write down the displayed addresses on your worksheet.
To display the default LANE addresses, complete the following step, beginning in global configuration mode:
| Task | Command |
|---|---|
show lane default-atm-addresses [interface atm number[.subinterface-number]] |
You must enter the configuration server's ATM address into the LightStream 1010 ATM switch and save it permanently, so that the value will not be lost when the switch is reset or powered off.
To enter the configuration server's ATM address into the LightStream 1010 switch and save it there permanently, complete the following steps on the LightStream 1010 switch, beginning in global configuration mode:
| Task | Command |
|---|---|
Step 1 Specify the LECS's ATM address for the entire switch. If you are configuring SSRP, include the ATM address of all the LECSs. | atm lecs-address-default address1 [ address2... ] |
Step 2 Exit global configuration mode. | exit |
Step 3 Save the configuration value permanently. | copy running-config startup-config |
In Step 1, you must specify the full 40-digit ATM address. Use the addresses on your worksheet that you obtained from the previous task.
The LECS database contains information about each ELAN, including the ATM addresses of the LESs.
You can specify one default ELAN in the database. The LECS will assign any client that does not request a specific ELAN to the default ELAN.
ELANs are either restricted or unrestricted. The configuration server will assign a client to an unrestricted ELAN if the client specifies that particular ELAN in its configuration. However, the configuration server will only assign a client to a restricted ELAN if the client is specified in the configuration server's database as belonging to that ELAN. The default ELAN should have unrestricted membership.
If you are configuring fault tolerance, you can have any number of servers per ELAN. Priority is determined by entry order; the first entry has the highest priority, unless you override it with the index option.
When setting up the LECS database remember that when configuring LECs the:
To set up the database, complete the tasks in the following sections as appropriate for your ELAN plan and scenario:
When you configure a Catalyst 5000 series switch ATM module as the configuration server for one default ELAN, you provide a name for the database, the ATM address of the LES for the ELAN, and a default name for the ELAN. In addition, you indicate that the configuration server's ATM address is to be computed automatically.
When you configure a database with only a default unrestricted ELAN, you do not have to specify where the LECs are located. That is, when you set up the configuration server's database for a single default ELAN, you do not have to provide any database entries that link the ATM addresses of any clients with the ELAN name. All of the clients will be automatically assigned to a default ELAN.
To set up the configuration server for the default ELAN, complete the following steps beginning in global configuration mode:
| Task | Commands |
|---|---|
Step 1 Create a named database for the LECS. | |
Step 2 In the configuration database, bind the name of the ELAN to the ATM address of the LES. If you are configuring Simple Server Redundancy Protocol, repeat this step for each additional server for the same ELAN. The index determines the priority. The highest priority is 0. | |
Step 3 In the configuration database, assign a segment number to the emulated Token Ring LAN. | name elan-name local-seg-id segment-number |
Step 4 In the configuration database, provide a default name for the ELAN. | default-name elan-name |
Step 5 Exit from database configuration mode and return to global configuration mode. | exit |
In Step 2, enter the ATM address of the server for the specified ELAN, as noted in your worksheet and obtained in the "Displaying LANE Default Addresses" section. You can have any number of servers per ELAN for fault tolerance. Priority is determined by entry order. The first entry has the highest priority unless you override it with the index number.
If you are setting up only a default ELAN, the elan-name value in Step 2 and Step 3 is the same as the default ELAN name you provide in Step 4.
In Step 2, the segment number you specify for local-seg-id must remain the same for each entry you add and it must also be identical to the ring number of the TrCRF. The set vlan command assumes that any ring number you enter is in hexadecimal. The name elan-name local-seg-id segment-number command assumes that any value you enter for the local-seg-id is in decimal unless you enter it explicitly in hexadecimal.
When you set up a database for unrestricted-membership ELANs, you create database entries that link the name of each ELAN to the ATM address of its server.
However, you may choose not to specify where the LECs are located. 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 ELAN name. The configuration server will assign the clients to the ELANs specified in the client's configurations.
To configure a Catalyst 5000 series switch ATM module as the configuration server for multiple ELANs with unrestricted membership, perform the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
Step 1 Create a named database for the LECS. | |
Step 2 In the configuration database, bind the name of the first ELAN to the ATM address of the LES for that ELAN. If you are configuring Simple Server Redundancy Protocol, repeat this step with the same ELAN name but with different server ATM addresses for each additional server for the same ELAN. The index determines the priority. The highest priority is 0. | name elan-name1 server-atm-address atm-address [index n] |
Step 3 In the configuration database, bind the name of the second ELAN to the ATM address of the LES. If you are configuring Simple Server Redundancy Protocol, repeat this step with the same ELAN name but with different server ATM addresses for each additional server for the same ELAN. The index determines the priority. The highest priority is 0. Repeat this step, providing a different ELAN name and ATM address for each additional ELAN in this switch cloud. | name elan-name2 server-atm-address atm-address [index n] |
Step 4 In the configuration database, assign a segment number to the first emulated Token Ring LAN. | |
Step 5 In the configuration database, assign a segment number to the second emulated Token Ring LAN. Repeat this step, providing a different ELAN name and segment number for each additional source-route bridged ELAN in this switch cloud. | name elan-name2 local-seg-id segment-number |
Step 6 (Optional) Specify a default ELAN for LECs not explicitly bound to an ELAN. | default-name elan-name1 |
Step 7 Exit from database configuration mode and return to global configuration mode. | exit |
In the steps listed in the task table, enter the ATM address of the server for the specified ELAN, as noted in your worksheet and obtained in the "Displaying LANE Default Addresses" section.
In Steps 4 and 5, the segment number you specify for local-seg-id must be identical to the ring number of the TrCRF. The set vlan command assumes that any ring number you enter is in hexadecimal. The name elan-name local-seg-id segment-number command assumes that any value you enter for the local-seg-id is in decimal unless you enter it explicitly in hexadecimal.
When you set up the database for restricted-membership ELANs, you create database entries that link the name of each ELAN to the ATM address of its server.
However, you must also specify where the LECs are located. That is, for each restricted-membership ELAN, you provide a database entry that explicitly links the ATM address or MAC address of each client of that ELAN with the name of that ELAN.
Those client database entries specify which clients are allowed to join the ELAN. When a client requests to join an ELAN, the configuration server consults its database and then assigns the client to the ELAN specified in the configuration server's database.
When clients for the same restricted-membership ELAN are located in multiple switch ATM interfaces, each client's ATM address or MAC address must be linked explicitly with the name of the ELAN. As a result, you must configure as many client entries (at Step 6, in the following procedure) as you have clients for ELANs in all the switch ATM interfaces. Each client will have a different ATM address in the database entries.
To set up the configuration server for ELANs with restricted membership, perform the following tasks beginning in global configuration mode:
| Task | Command |
Step 1 Create a named database for the LECS. | |
Step 2 In the configuration database, bind the name of the first ELAN to the ATM address of the LES for that ELAN. If you are configuring Simple Server Redundancy Protocol, repeat this step with the same ELAN name but with different server ATM addresses for each additional server for the same ELAN. The index determines the priority. The highest priority is 0. | name elan-name1 server-atm-address atm-address restricted [index n] |
Step 3 In the configuration database, bind the name of the second ELAN to the ATM address of the LES. If you are configuring Simple Server Redundancy Protocol, repeat this step with the same ELAN name but with different server ATM addresses for each additional server for the same ELAN. The index determines the priority. The highest priority is 0. Repeat this step, providing a different name and a different ATM address, for each additional ELAN. | name elan-name2 server-atm-address atm-address restricted [index n] |
Step 4 In the configuration database, assign a segment number to the first emulated Token Ring LAN. | name elan-name1 local-seg-id segment-number |
Step 5 In the configuration database, assign a segment number to the second emulated Token Ring LAN. Repeat this step, providing a different ELAN name and segment number for each additional source-route bridged ELAN in this switch cloud. | name elan-name2 local-seg-id segment-number |
Step 6 Add a database entry associating a specific client's ATM address with a specific restricted-membership ELAN. Repeat this step for each of the clients of each of the restricted-membership ELANs on the switch cloud, in each case specifying that client's ATM address and the name of the ELAN with which it is linked. | client-atm-address atm-address-template name elan-name |
Step 7 Exit from database configuration mode and return to global configuration mode. | exit |
In Steps 4 and 5, the segment number you specify for local-seg-id must be identical to the ring number of the TrCRF. The set vlan command assumes that any ring number you enter is in hexadecimal. The name elan-name local-seg-id segment-number command assumes that any value you enter for the local-seg-id is in decimal unless you enter it explicitly in hexadecimal.
Once you have created the database entries as appropriate to the type and the membership conditions of the ELANs, you can enable the configuration server on the selected ATM interface and switch by completing the following tasks, beginning in global configuration mode:
| Task | Command |
|---|---|
Step 1 If you are not currently configuring the interface, specify the major ATM interface where the configuration server is located. | interface atm number[.subinterface-number] |
Step 2 Link the configuration server's database name to the specified major interface, and enable the configuration server. | lane config database database-name |
Step 3 Specify that the configuration server's ATM address will be computed by the automatic method. | lane config auto-config-atm-address |
Step 4 Exit interface configuration mode. | exit |
Step 5 Return to EXEC mode. | exit |
Step 6 Save the configuration. | copy running-config startup-config |
For each Catalyst 5000 series switch ATM module that will participate in LANE, set up the necessary servers and clients for each ELAN and then display and record the server and client ATM addresses. Be sure to keep track of the switch ATM interface where the LECS will eventually be located.
If you are going to have only one default ELAN, you will have only one server to set up. If you are going to have multiple ELANs, you can set up the server for another ELAN on a different subinterface on the same interface of this switch, or you can place it on a different switch.
You can set up servers for more than one ELAN on a different subinterfaces or on the same interface of a switch, or you can place the servers on different switches. When you set up a server and BUS on a switch, you can combine them with a client on the same subinterface, a client on a different subinterface, or no client at all on the switch.
Depending on where your clients and servers are located, perform one of the following tasks for each LANE subinterface.
To set up the server, BUS, and clients for an ELAN, perform the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
Step 1 Specify the subinterface for the first ELAN on this switch. | interface atm number[.subinterface-number] |
Step 2 Enable an LES and a LANE BUS for the first ELAN. | lane server-bus tokenring elan-name1 |
Step 3 (Optional) Enable an LEC for the first ELAN. | lane client tokenring vlan_id [elan-name1] |
Step 4 Return to EXEC mode. | exit |
Step 5 Save the configuration. | copy running-config startup-config |
If the ELAN specified in Step 3 is intended to have restricted membership, consider carefully whether or not you want to specify its name here. You will specify the name in the LECS database when it is set up. However, if you link the client to an ELAN in this step, and through some mistake it does not match the database entry linking the client to an ELAN, this client will not be allowed to join this ELAN or any other.
If you do decide to include the name of the ELAN linked to the client in Step 3 and later want to associate that client with a different ELAN, make the change in the configuration server's database before you make the change for the client on this subinterface.
When VLANs are added to a Catalyst 5000 series switch in a management domain, VLAN Trunking Protocol (VTP) automatically distributes information to other trunks of all of the devices in the domain. The VTP is transmitted on all trunk connections, including Inter-Switch Link (ISL), IEEE 802.10, and LANE.
VTP and the Catalyst 5000 series Token Ring LANE feature require the following software:
When you set up an LEC, follow these rules and recommendations:
| VLAN Number | VLAN Name |
|---|---|
1 | default |
2...1002 | VLAN0002 through VLAN1002 |
1003 | trcrf-default |
1004 | VLAN1004 |
1005 | trbrf-default |
If you currently have a different ELAN name for VLAN 1 or VLAN 1003, you must change the ELAN name to default (for VLAN 1) or trcrf-default (for VLAN 1003) in the LECS database.The following example shows an LECS database configuration that specifies marktng as the ELAN name for VLAN 1003:
lane database test name marktng server-atm-address 47.0091810000000061705B8301.00400B020011.01 ! interface ATM0 no ip address no ip route-cache atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi lane config auto-config-atm-address lane config database test ! interface ATM0.1 multipoint no ip route-cache lane server-bus tokenring marktng lane client tokenring 1003 marktng
You must change the ELAN name for VLAN 1003 from marktng to trcrf-default in the second and last lines of the display, as follows:
lane database test name default server-atm-address 47.0091810000000061705B8301.00400B020011.01 ! interface ATM0 no ip address no ip route-cache atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi lane config auto-config-atm-address lane config database test ! interface ATM0.1 multipoint no ip route-cache lane server-bus tokenring default lane client tokenring 1003 trcrf-default
With Token Ring, to successfully route packets between ELANs, you can only set up one LEC for each TrBRF on an ATM module. For multiple ELANs with the same TrBRF to route packets, they must be configured on either separate ATM modules or connected via an external device.
If the TrBRF and TrCRF for which you are creating an LEC do not already exist, create the Token Ring VLANs by performing the following tasks:
| Task | Command |
|---|---|
Step 1 From the supervisor module, define the TrBRF that you will associate to TrCRF as a parent. | set vlan vlan_num [name name] type trbrf [state {active | suspend}] [mtu mtu] bridge bridge_number [stp {ieee | ibm | auto}] |
Step 2 From the supervisor module, define the TrCRF for which you are creating an LEC. | set vlan vlan_num [name name] type trcrf [state {active | suspend}] [mtu mtu] ring ring_number parent vlan_num [mode {srt | srb}] [backupcrf {off | on}] [aremaxhop hopcount] [stemaxhop hopcount] |
To set up the LEC for the Token Ring VLAN and corresponding ELAN, perform the following tasks on the ATM module beginning in interface configuration mode:
Step 3 Specify the subinterface for an ELAN on this switch. | interface atm number[.subinterface-number] |
Step 4 Enable an LEC for the first ELAN. | lane client tokenring vlan_id [elan-name1] |
Step 5 Return to EXEC mode. | exit |
Step 6 Save the configuration | copy running-config startup-config |
The LANE protocol does not specify where any of the ELAN server entities should be located, but for the purpose of reliability and performance, Cisco implements these server components on its routers and LAN switches.
With Phase I LANE, only one LECS, capable of serving multiple ELANs, and only one LES per ELAN could exist for an ATM cloud. The Phase I LANE protocol did not allow for multiple LESs within an ELAN. Therefore, these components represented both single points of failure and potential bottlenecks for LANE service.
LANE LES/BUS and LECS redundancy corrects these limitations by allowing you to configure redundant LESs and BUSs so that the LECs in an ELAN can automatically switch to a backup LES if the primary LES fails. The priority of the LES/BUS pairs is established by the order in which they are entered in the LECS database. LANE LES/BUS and LECS redundancy is always enabled. You can use this redundancy feature by configuring multiple servers.
LES/BUS and LECS redundancy works only with Cisco LECS and LES combinations. Third party LANE server components continue to interoperate with the LECS and LES/BUS function of Cisco routers and switches, but cannot take advantage of the redundancy features.
The following three servers are single points of failure in the ATM LANE system:
LES/BUS and LECS redundancy eliminates these single points of failure. To configure LES/BUS and LECS redundancy, use the procedure in the following section.
To enable redundant LECSs, enter the multiple LECS addresses to the end ATM switches, which are used as central locations for the list of LECS addresses. After entering the LECS addresses, LANE components connected to the switches can obtain the global list of LECS addresses.
To enable LES/BUS and LEC redundancy, complete following tasks:
| Task | Command |
|---|---|
Step 1 On the ATM switch, enter the multiple LECS addresses. | atm lecs-address address |
Step 2 On the ATM module, specify redundant LES/BUSs. Enter the command for each LES address on the ELAN. | name elan-name server-atm-address les-address [index n] |
The index determines the priority; 0 is the highest priority.
If enabled, ILMI sends keepalive messages on an ongoing basis on the active physical (PHY) to the switch, and the switch responds. If the response is not obtained for the last four polls, the ILMI timer times out and the dual PHY switches from active PHY to backup PHY. This feature is useful only if the two PHYs are connected to two different switches.
By default, this feature is disabled. To enable it, session to the ATM module (enter the session command), and then enter these commands:
ATM> enable ATM# configure terminal Enter configuration commands, one per line. End with CNTL/Z. ATM(config)# int atm0 ATM(config-if)# atm ilmi-keepalive 4 ATM(config-if)# end ATM#
These commands enable the transmission of ILMI keepalive and set the time between two ILMI keepalive messages to 4 seconds.
The ATM LANE dual PHY module supports backward compatibility with ATM switches for UNI version 3.1. On startup, ILMI negotiates between UNI versions 3.0 and 3.1, requiring no configuration. If the ILMI link autodetermination is successfully enabled on the interface, the router or switch accepts the UNI version returned by ILMI. If the ILMI link autodetermination is unsuccessful or if ILMI is disabled, the UNI version defaults to 3.0. You can override the version number by entering the atm uni-version command. If ILMI is enabled when you enter the no value of the command, the UNI version is set to the version returned by ILMI and the link autodetermination is successful. Otherwise, the version reverts to 3.0. Enter the no atm uni-version command to override the UNI version.
Once you have set up the LECs on the subinterfaces of an ATM module, you can display their ATM addresses by completing the following task in EXEC mode:
| Task | Command |
|---|---|
Display the LES, BUS, and LEC ATM addresses. | show lane |
The command output shows all the subinterfaces configured for LANE. For each subinterface, the command displays and labels the ATM addresses that belong to the LES, BUS, and the LEC.
When you look at each ATM address, note the following items:
Enter the show lane command on each Catalyst 5000 series switch to verify the LANE setup before you set up the LECs on the next Catalyst 5000 series switch. Print the display or make a note of these ATM addresses so that you can use it when you set up the LECS database. At this point in the configuration process, the LECs are normally not operational.
After configuring LANE components on an interface or any of its subinterfaces, you can display their status on a specified subinterface or on an ELAN. To show LANE information, perform these steps in EXEC mode:
| Task | Command |
|---|---|
Step 1 Display the global and per-VCC LANE information for all the LANE components and ELANs configured on an interface or any of its subinterfaces. | show lane [interface atm 0 [subinterface-number | name elan-name]] [brief] |
Step 2 Display the global and per-VCC LANE information for the BUS configured on any subinterface or ELAN. | show lane bus [interface atm 0 [subinterface-number] | name elan-name] [brief] |
Step 3 Display the global and per-VCC LANE information for all LECs configured on any subinterface or ELAN. | show lane client [interface atm 0 [subinterface-number] | name elan-name] [brief] |
Step 4 Display the global and per-VCC LANE information for the LECS configured on any interface. | show lane config [interface atm 0] |
Step 5 Display the LECS database. | show lane database [database-name] |
Step 6 Display the LANE Address Resolution Protocol (ARP) table of the LECs configured on the specified subinterface or ELAN. | show lane le-arp [interface atm 0 [subinterface-number] | name elan-name] |
Step 7 Display the global and per-VCC LANE information for the LES configured on a specified subinterface or ELAN. | show lane server [interface atm 0 [subinterface-number] | name elan-name] [brief] |
Figure 3 shows a configuration composed of two Catalyst 5000 series switches and a LightStream 1010 ATM switch.
For the example in Figure 3 the following assumptions apply:
To define the TrCRF, complete the following steps:
Step 1 At the enable prompt, enter:
set vlan 112 name crf112 type trcrf ring 112 parent 400 mode srb
Step 2 To verify the configuration of the new VLAN, enter the show vlan command.
The output indicates that crf112 has been added and that brf400 is its parent.
Console> (enable) show vlan 112 VLAN Name Status Mod/Ports, Vlans ---- -------------------------------- --------- ---------------------------- 112 crf112 active VLAN Type SAID MTU Parent RingNo BrdgNo Stp BrdgMode Trans1 Trans2 ---- ----- ---------- ----- ------ ------ ------ ---- -------- ------ ------ 112 trcrf 100112 4472 400 0x112 - - srb 0 0 VLAN AREHops STEHops Backup CRF ---- ------- ------- ---------- 112 7 7 off Console> (enable)
To configure the LES, BUS, and LEC, complete the following steps:
Step 1 Set up the prefix of the ATM NSAP address for the switch.
Step 2 Start a session to the ATM module by entering the session 4 command. You see the following display:
Console> session 4 Trying ATM-4... Connected to ATM-4. Escape character is '^]'. ATM>
Step 3 Obtain the addresses of the LES and LES/BUS for later use by entering the enable command (to enable configuration mode) and the show lane default-atm-addresses command at the ATM prompt. You see the following display:
ATM> enable ATM# ATM# show lane default-atm-addresses interface atm0 interface ATM0: LANE Client: 47.0091810000000061705b7701.00400BFF0010.** LANE Server: 47.0091810000000061705b7701.00400BFF0011.** LANE Bus: 47.0091810000000061705b7701.00400BFF0012.** LANE Config Server: 47.0091810000000061705b7701.00400BFF0013.00 ATM#
Step 4 Using the LECS address obtained in Step 3, set the address of the default LECS in the LightStream 1010 switch by entering the configure terminal and atm lecs-address-default commands on the console of the LightStream 1010 switch. You see the following display:
Switch> enable Switch# Switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# atm lecs-address-default 47.0091810000000061705b7701.00400BFF0013.00 1 Switch(config)# end Switch#
The commands shown in this step configure the address of the LECS in the switch. The LECS ATM NSAP address is 47.0091810000000061705b7701.00400BFF0013.00. The sequence number of this LECS address, which is 1, means it is the first LECS in this switch.
Step 5 Save the configuration to NVRAM by entering the write memory command, as follows:
ATM# write memory
Step 6 Start up an LES/BUS pair on Catalyst 5000 series switch 1 by entering the interface atm0 and the lane server-bus tokenring commands in global configuration mode. On the console of Catalyst 5000 series switch 1, enter the following commands:
ATM# config terminal Enter configuration commands, one per line. End with CNTL/Z. ATM(config)# interface atm0 ATM(config-subif)# lane server-bus tokenring crf112 ATM(config-subif)# end ATM#
The commands shown in this step start an LES/BUS pair and assign the ATM 0 interface to crf112. The ELAN name is crf112, and the interface on which this LES/BUS pair is configured is atm0. The ELAN name must be the same as the VLAN name assigned to the TrCRF.
Step 7 Save the configuration in NVRAM entering the write memory command, as follows:
ATM# write memory
Step 8 Set up the LECS database on the Catalyst 5000 series switch 1.
Enter the LES address obtained in Step 3 and replace the ** with the subinterface number of the interface on which the LES/BUS is to be configured. In this example, that number is 00. Enter the lane database database_name command, the name elan_name server-atm-address atm_address command, the name elan_name local-seg-id segment_number, and the default-name elan_name commands at the ATM prompt. You see the following display:
ATM# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
ATM(config)# lane database test
ATM(lane-config-database)# name trcf-default server-atm-address
47.0091810000000061705b7701.00400BFF0011.00
ATM (lane-config-database) name crf112 local-seg-id 0x112
ATM(lane-config-database)# default-name crf112
ATM(lane-config-database)# exit
ATM#
The commands shown in this step create the LECS database. The database name is test. The ELAN name is crf112. The ELAN segment number is 112. The LES ATM NSAP address is 47.0091810000000061705b7701.00400BFF0011.00.
Step 9 Save the configuration in NVRAM by entering the write memory command, as follows:
ATM# write memory
Step 10 Start and bind the LECS on the Catalyst 5000 series switch 1 by entering the interface atm0 command, the lane config database database_name command, and the lane config auto-config-atm-address command at the ATM prompt. You see the following display:
ATM# config terminal Enter configuration commands, one per line. End with CNTL/Z. ATM(config)# interface atm0 ATM(config-if)# lane config database test ATM(config-if)# lane config auto-config-atm-address ATM(config-if)# end ATM#
The commands shown in this step start the LECS. The database to use is test. The interface on which the LECS is configured is atm0.
Step 11 Save the configuration in NVRAM by entering the write memory command, as follows:
ATM# write memory
Step 12 Start the LEC on the Catalyst 5000 series switches 1 and 2 by entering the interface atm0.1 command and the lane client tokenring 112 crf112 command in configuration mode on the consoles of switches 1 and 2. The interface on which the LEC is configured is atm0.1. The ELAN name is default, and it is configured to emulate Token Ring. You see the following display:
ATM# configure terminal Enter configuration commands, one per line. End with CNTL/Z. ATM(config)# interface atm0.1 ATM(config-subif)# lane client tokenring 112 crf112 ATM(config-subif)# end ATM#
Step 13 Save the configuration in NVRAM by entering the write memory command, as follows:
ATM# write memory
This section documents new and modified commands. All other commands used with this feature are documented in the Catalyst 5000 Series Command Reference.
To clear the dynamic LE_ARP table or a single LE_ARP entry of the LEC configured on the specified subinterface or ELAN, use the clear lane le-arp privileged EXEC command.
clear lane le-arp [{interface number [.subinterface-number] | name elan-name} [mac-address
interface number[.subinterface-number] | (Optional) Interface or subinterface for the LEC whose LE_ARP table or entry is to be cleared. |
name elan-name | (Optional) Name of the ELAN for the LEC whose LE_ARP table or entry is to be cleared. Maximum length is 32 characters. |
mac-address mac-address | (Optional) MAC address of the entry to be cleared from the LE ARP table. |
route-desc segment segment-number bridge bridge-number | (Optional) Keywords to specify the segment and bridge numbers. The segment number ranges from 1 to 4095, and the bridge number ranges from 1 to 15. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
This command removes dynamic LE_ARP table entries only. It does not remove static LE_ARP table entries.
If you do not specify an interface or an ELAN, this command clears all the LE_ARP tables of any LEC in the switch.
If you specify a major interface (not a subinterface), this command clears all the LE_ARP tables of every LEC on all the subinterfaces of that interface.
This command also removes the fast-cache entries built from the LE_ARP entries.
The following example clears all the LE_ARP tables for all clients on the router or switch:
clear lane le-arp
The following example clears all the LE_ARP tables for all LECs on all the subinterfaces of interface 1/0:
clear lane le-arp interface 1/0
The following example clears the entry corresponding to MAC address 0800.AA00.0101 from the LE_ARP table for the LEC on the ELAN red:
clear lane le-arp name red 0800.aa00.0101
The following example clears all dynamic entries from the LE_ARP table for the LEC on the ELAN red:
clear lane le-arp name red
The following example clears the dynamic entry from the LE_ARP table for the LEC on segment number 1, bridge number 1 in the ELAN red:
clear lane le-arp name red route-desc segment 1 bridge 1
lane le-arp
To force an LES to drop a client and allow the LECS to assign the client to another ELAN, use the clear lane server privileged EXEC command.
clear lane server {interface number [.subinterface-number] | name elan-name}
interface number[.subinterface-number] | Interface or subinterface where the LES is configured. |
name elan-name | Name of the ELAN on which the LES is configured. Maximum length is 32 characters. |
mac-address mac-address | (Optional) Keyword and LEC MAC address. |
client-atm-address atm-address | (Optional) Keyword and LEC ATM address. |
lecid lecid | (Optional) Keyword and LEC ID. The LEC ID is a value between 1 and 4096. |
route-desc segment segment-number bridge bridge-number | (Optional) Keywords and LANE segment number and bridge number. The segment number ranges from 1 to 4095, and the bridge number ranges from 1 to 15. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.0.
After changing the bindings on the configuration server, enter this command on the LES to force the client to leave one ELAN. The LES will drop the Control Direct and Control Distribute VCCs to the LEC. The client will then ask the LECS for the location of the LES of the ELAN it should join.
If no LEC is specified, all LECs attached to the LES are dropped.
The following example forces all the LECs on the ELAN red to be dropped. The next time they try to join, they will be forced to join a different ELAN.
clear lane server red
client-atm-address name
lane database
mac-address name
show lane server
To activate an LEC on the specified subinterface, use the lane client interface configuration command. To remove a previously activated LEC on the subinterface, use the no form of this command.
lane client {ethernet | tokenring} vlan_id [elan-name]
ethernet | Identifies the ELAN attached to this subinterface as an Ethernet ELAN. |
tokenring | Identifies the ELAN attached to this subinterface as a Token Ring ELAN. |
vlan_id | Number of the VLAN to which this ELAN corresponds. |
elan-name | (Optional) Name of the ELAN. This argument is optional because the client obtains its ELAN name from the configuration server. The maximum length of the name is 32 characters. |
No LECs are enabled on the interface.
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
This command is ordinarily used when configuring a switch or router.
If a lane client command has already been entered on the subinterface for a different ELAN, then the client initiates termination procedures for that ELAN and joins the new ELAN.
If you do not provide an elan-name value, the client contacts the server to find which ELAN to join. If you do provide an ELAN name, the client consults the configuration server to ensure that no conflicting bindings exist.
The following example enables a Token Ring LEC on an interface:
lane client tokenring 2 VLAN002
lane client-atm-address
To enable an LES and a BUS on the specified subinterface, use the lane server-bus interface configuration command. To disable an LES and BUS on the specified subinterface, use the no form of this command.
lane server-bus {ethernet | tokenring} elan-name
ethernet | Identifies the ELAN attached to this subinterface as an Ethernet ELAN. |
tokenring | Identifies the ELAN attached to this subinterface as a Token Ring ELAN. |
elan-name | Name of the ELAN. The maximum length of the name is 32 characters. |
No LAN type or ELAN name is provided.
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
This command is ordinarily used when configuring a switch or router.
The LES and the BUS are located on the same router.
If a lane server-bus command has already been entered on the subinterface for a different ELAN, then the server initiates termination procedures with all clients and comes up as the server for the new ELAN.
The no form of this command removes a previously configured LES and BUS on the subinterface.
The following example enables an LES and BUS for a Token Ring ELAN:
lane server-bus tokenring
lane server-atm-address
To specify or replace the ring number of the ELAN in the configuration server's configuration database, use the name local-seg-id database configuration command. To remove the ring number from the database, use the no form of this command.
name elan-name local-seg-id segment-number
elan-name | Name of the ELAN. The maximum length of the name is 32 characters. |
segment-number | Segment number to be assigned to the ELAN. The number ranges from 1 to 4095. |
No ELAN name or segment number is provided.
Database configuration
This command first appeared in Cisco IOS Release 11.2 F.
This command is ordinarily used for Token Ring LANE.
The same LANE ring number cannot be assigned to more than one ELAN.
The no form of this command deletes the relationships.
The segment number you specify for local-seg-id must be identical to the ring number of the TrCRF. The set vlan command assumes that any ring number you enter is in hexadecimal. The name elan-name local-seg-id segment-number command assumes that any value you enter for the local-seg-id is in decimal unless you enter it explicitly in hexadecimal.
The following example specifies a ring number of 1024 for the ELAN red:
name red local-seg-id 1024
default-name
lane database
mac-address name
To display global and per-VCC LANE information for all the LANE clients configured on an interface, a subinterface, or an ELAN, use the show lane EXEC command.
show lane [interface atm number[.subinterface-number] | name elan-name] [brief]
interface atm number | (Optional) ATM interface number. |
.subinterface-number | (Optional) Subinterface number. |
name elan-name | (Optional) Name of ELAN. The maximum length of the name is 32 characters. |
brief | (Optional) Keyword used to display the brief subset of available information. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
Entering the show lane command is equivalent to entering the show lane config, show lane server, show lane bus, and show lane client commands. The show lane command shows all LANE-related information except the show lane database command information.
The following is sample output of the show lane command for a Token Ring LANE network:
ATM# show lane
LE Config Server ATM4/0 config table: eng
Admin: up State: operational
LECS Mastership State: active master
list of global LECS addresses (35 seconds to update):
39.020304050607080910111213.006047704183.00 <-------- me
ATM Address of this LECS: 39.020304050607080910111213.006047704183.00 (auto)
vcd rxCnt txCnt callingParty
7 1 1 39.020304050607080910111213.006047704181.01 LES elan1 0 active
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 2
cumulative total number of config failures so far: 0
LE Server ATM4/0.1 ELAN name: elan1 Admin: up State: operational
type: token ring Max Frame Size: 4544 Segment ID: 2048
ATM address: 39.020304050607080910111213.006047704181.01
LECS used: 39.020304050607080910111213.006047704183.00 connected, vcd 9
control distribute: vcd 12, 1 members, 2 packets
proxy/ (ST: Init, Conn, Waiting, Adding, Joined, Operational, Reject, Term)
lecid ST vcd pkts Hardware Addr ATM Address
1 O 8 3 100.2 39.020304050607080910111213.006047704180.01
0060.4770.4180 39.020304050607080910111213.006047704180.01
LE BUS ATM4/0.1 ELAN name: elan1 Admin: up State: operational
type: token ring Max Frame Size: 4544 Segment ID: 2048
ATM address: 39.020304050607080910111213.006047704182.01
data forward: vcd 16, 1 members, 0 packets, 0 unicasts
lecid vcd pkts ATM Address
1 13 0 39.020304050607080910111213.006047704180.01
LE Client ATM4/0.1 ELAN name: elan1 Admin: up State: operational
Client ID: 1 LEC up for 2 hours 25 minutes 39 seconds
Join Attempt: 3
HW Address: 0060.4770.4180 Type: token ring Max Frame Size: 4544
Ring:100 Bridge:2 ELAN Segment ID: 2048
ATM Address: 39.020304050607080910111213.006047704180.01
VCD rxFrames txFrames Type ATM Address
0 0 0 configure 39.020304050607080910111213.006047704183.00
10 1 3 direct 39.020304050607080910111213.006047704181.01
11 2 0 distribute 39.020304050607080910111213.006047704181.01
14 0 0 send 39.020304050607080910111213.006047704182.01
15 0 0 forward 39.020304050607080910111213.006047704182.01
Table 3 describes significant fields in the sample display.
| Field | Description |
|---|---|
LE Config Server | Identifies the following lines as applying to the LECS. These lines are also displayed in output from the show lane config command. See the show lane config command for explanations of the output. |
LE Server | Identifies the following lines as applying to the LES. These lines are also displayed in output from the show lane server command. See the show lane server command for explanations of the output. |
LE BUS | Identifies the following lines as applying to the LANE BUS. These lines are also displayed in output from the show lane bus command. See the show lane bus command for explanations of the output. |
LE Client | Identifies the following lines as applying to an LEC. These lines are also displayed in output from the show lane client command. See the show lane bus command for explanations of the output. |
To display detailed LANE information for the BUS configured on an interface or any of its subinterfaces, on a specified subinterface, or on an ELAN, use the show lane bus EXEC command:
show lane bus [interface atm number[.subinterface-number] | name elan-name] [brief]
interface atm number | (Optional) ATM interface number. |
.subinterface-number | (Optional) Subinterface number. |
name elan-name | (Optional) Name of the ELAN. Maximum length is 32 characters. |
brief | (Optional) Keyword used to display the brief subset of available information. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output of the show lane bus command for a Token Ring LANE:
ATM# show lane bus
LE BUS ATM3/0.1 ELAN name: anubis Admin: up State: operational
type: token ring Max Frame Size: 4544 Segment ID: 2500
ATM address: 47.009181000000000000000000.00000CA01662.01
data forward: vcd 14, 2 members, 0 packets, 0 unicasts
lecid vcd pkts ATM Address
1 11 0 47.009181000000000000000000.00000CA01660.01
2 17 0 47.009181000000000000000000.00000CA04960.01
Table 4 describes significant fields in the sample display.
| Field | Description |
|---|---|
LE BUS ATM3/0.1 | Interface and subinterface for which information is displayed. |
ELAN name | Name of the ELAN for this BUS. |
Admin | Administrative state (either up or down). |
State | Status of this LANE BUS. Possible states include down and operational. |
type | Type of ELAN. |
Max Frame Size | Maximum frame size (in bytes) on the ELAN. |
Segment ID | The ELAN's ring number. This field appears only for Token Ring LANE. |
ATM Address | ATM address of this LANE BUS. |
data forward | Virtual channel descriptor of the Data Forward VCC, the number of LECs attached to the VCC, and the number of packets transmitted on the VCC. |
lecid | Identifier assigned to each LEC on the Data Forward VCC. |
vcd | Virtual channel descriptor used to reach the LEC. |
pkts | Number of packets sent by the BUS to the LEC. |
ATM Address | ATM address of the LEC. |
To display global and per-VCC LANE information for all the LECs configured on an interface, subinterface, or on an ELAN, use the show lane client EXEC command.
show lane client [interface atm number[.subinterface-number] | name elan-name] [brief]
interface atm number | (Optional) ATM interface number. |
.subinterface-number | (Optional) Subinterface number. |
name elan-name | (Optional) Name of the ELAN. The maximum length of the name is 32 characters. |
brief | (Optional) Keyword used to display the brief subset of available information. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output from the show lane client command for a Token Ring LANE:
ATM# show lane client LE Client ATM4/0.1 ELAN name: elan1 Admin: up State: operational Client ID: 1 LEC up for 2 hours 26 minutes 3 seconds Join Attempt: 3 HW Address: 0060.4770.4180 Type: token ring Max Frame Size: 4544 Ring:100 Bridge:2 ELAN Segment ID: 2048 ATM Address: 39.020304050607080910111213.006047704180.01 VCD rxFrames txFrames Type ATM Address 0 0 0 configure 39.020304050607080910111213.006047704183.00 10 1 3 direct 39.020304050607080910111213.006047704181.01 11 2 0 distribute 39.020304050607080910111213.006047704181.01 14 0 0 send 39.020304050607080910111213.006047704182.01 15 0 0 forward 39.020304050607080910111213.006047704182.01
Table 5 describes significant fields in the sample display.
| Field | Description |
|---|---|
LE Client ATM4/0.1 | Interface and subinterface of this client. |
ELAN name | Name of the ELAN. |
Admin | Administrative state; either up or down. |
State | Status of this LEC. Possible states include initialState, lecsConnect, configure, join, busConnect, and operational. |
Client ID | The LAN emulation 2-byte Client ID assigned by the LAN emulation server. |
Join Attempt | The number of attempts before successfully joining the ELAN. |
HW Address | MAC address of this LEC. |
Type | Type of ELAN. |
Max Frame Size | Maximum frame size (in bytes) on the ELAN. |
Ring | The ring number for the client. This field only appears for Token Ring LANE. |
Bridge | The bridge number for the client. This field only appears for Token Ring LANE. |
ELAN Segment ID | The ring number for the ELAN. This field only appears for Token Ring LANE. |
ATM Address | ATM address of this LEC. |
VCD | Virtual channel descriptor for each of the VCCs established for this LEC. |
rxFrames | Number of frames received. |
txFrames | Number of frames transmitted. |
Type | Type of VCC. The Configure Direct VCC is shown in this display as configure. The Control Direct VCC is shown as direct; the Control Distribute VCC is shown as distribute. The Multicast Send VCC and Multicast Forward VC are shown as send and forward, respectively. The Data Direct VCC is shown as data |
ATM Address | ATM address of the LANE component at the other end of this VCC. |
To display global LANE information about the LECS, use the show lane config EXEC command.
show lane config [interface atm number]
interface atm number | (Optional) ATM interface number. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following example shows sample show lane config output for Token Ring LANE:
ATM# show lane config LE Config Server ATM4/0 config table: eng Admin: up State: operational LECS Mastership State: active master list of global LECS addresses (40 seconds to update): 39.020304050607080910111213.006047704183.00 <-------- me ATM Address of this LECS: 39.020304050607080910111213.006047704183.00 (auto) vcd rxCnt txCnt callingParty 7 1 1 39.020304050607080910111213.006047704181.01 LES elan1 0 active cumulative total number of unrecognized packets received so far: 0 cumulative total number of config requests received so far: 2 cumulative total number of config failures so far: 0
Table 6 describes significant fields in the sample display.
| Field | Description |
|---|---|
LE Config Server | Major interface on which the LECS is configured. |
config-table | Name of the database associated with the LECS. |
Admin | Administrative state (either up or down). |
State | State of the configuration server (down or operational). If down, the reasons field indicates why it is down. The reasons include the following: NO-config-table, NO-nsap-address, and NO-interface-up. |
LECS Mastership State | Mastership state of the configuration server. If you have configured simple server redundancy, the configuration server with the lowest index is the active LECS. |
list of global LECS addresses | List of LECS addresses. |
40 seconds to update | Amount of time until the next update. |
<-------- me | ATM address of this configuration server. |
ATM Address of this LECS | ATM address of the active configuration server. |
auto | Method of ATM address assignment for the configuration server. In this example, the address is assigned by the automatic method. |
vcd | Virtual circuit descriptor that uniquely identifies the configure VCC. |
rxCnt | Number of packets received. |
txCnt | Number of packets transmitted. |
callingParty | ATM NSAP address of the LANE component that is connected to the LECS; "elan1" indicates the ELAN name, "0" indicates the priority number, and "active" indicates that the server is active. |
To display the configuration server's database, use the show lane database EXEC command.
show lane database [database-name]
database-name | (Optional) Specific database name. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
By default, this command displays the LECS information displayed by the show lane config command.
If no database name is specified, this command shows all databases.
The following is sample output of the show lane database command for a Token Ring LANE.
ATM# show lane database LANE Config Server database table 'eng' bound to interface/s: ATM4/0 default elan: elan1 elan 'elan1': un-restricted, local-segment-id 2048 server 39.020304050607080910111213.006047704181.01 (prio 0) active
Table 7 describes significant fields in the sample display.
| Field | Description |
|---|---|
LANE Config Server database | Name of this database and interfaces bound to it. |
default elan | Default name, if one is established. |
elan | Name of the ELAN whose data is reported in this line and the following indented lines. |
un-restricted | Indicates whether this ELAN is restricted or unrestricted. |
local-segment-id 2048 | Ring number of the ELAN. |
server | ATM address of the configuration server. |
(prio 0) active | Priority level and simple server redundancy state of this configuration server. If you have configured simple server redundancy, the configuration server with the lowest priority will be active. |
To display the LANE LE_ARP table of the LEC configured on an interface or any of its subinterfaces, on a specified subinterface, or on an ELAN, use the show lane le-arp EXEC command.
show lane le-arp [interface atm number[.subinterface-number] | name elan-name]
interface atm number | (Optional) ATM interface number. |
.subinterface-number | (Optional) Subinterface number. |
name elan-name | (Optional) Name of the ELAN. Maximum length is 32 characters. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output of the show lane le-arp command for a Token Ring LEC:
ATM# show lane le-arp Ring Bridge ATM Address VCD Interface 512 6 39.020304050607080910111213.00602F557940.01 47 ATM2/0.1
Table 8 describes significant fields shown in the display.
| Field | Description |
|---|---|
Ring | Route descriptor segment number for the LANE component. |
Bridge | Bridge number for the LANE component. |
ATM Address | ATM address of the LANE component at the other end of this virtual channel descriptor. |
VCD | Virtual circuit descriptor. |
Interface | Interface or subinterface used to reach the specified component. |
To display global information for the LES configured on an interface or any of its subinterfaces, on a specified subinterface, or on an ELAN, use the show lane server EXEC command.
show lane server [interface atm number[.subinterface-number] | name elan-name] [brief]
interface atm number | (Optional) ATM interface number. |
.subinterface-number | (Optional) Subinterface number. |
name elan-name | (Optional) Name of the ELAN. The maximum length of the name is 32 characters. |
brief | (Optional) Keyword used to display the brief subset of available information. |
EXEC
This command first appeared in Cisco IOS Release 11.0.
The following is sample output of the show lane server command for a Token Ring ELAN:
ATM# show lane server
LE Server ATM3/0.1 ELAN name: anubis Admin: up State: operational
type: token ring Max Frame Size: 4544 Segment ID: not set
ATM address: 47.009181000000000000000000.00000CA01661.01
LECS used: 47.009181000000000000000000.00000CA01663.00 connected, vcd 6
control distribute: vcd 10, 2 members, 4 packets
proxy/ (ST: Init, Conn, Waiting, Adding, Joined, Operational, Reject, Term)
lecid ST vcd pkts Hardware Addr ATM Address
1 O 7 3 400.1 47.009181000000000000000000.00000CA01660.01
0000.0ca0.1660 47.009181000000000000000000.00000CA01660.01
2 O 16 3 300.1 47.009181000000000000000000.00000CA04960.01
0000.0ca0.4960 47.009181000000000000000000.00000CA04960.01
Table 9 describes significant fields shown in the display.
| Field | Description |
|---|---|
LE Server ATM3/0.1 | Interface and subinterface of this server. |
ELAN name | Name of the ELAN. |
Admin | Administrative state (either up or down). |
State | Status of this LES. Possible states for an LES include down, waiting_ILMI, waiting_listen, up_not_registered, operational, and terminating. |
Type | Type of ELAN. |
Max Frame Size | Maximum frame size (in bytes) on this type of ELAN. |
Segment ID | The ELAN's ring number. This field appears only for Token Ring LANE. |
ATM Address | ATM address of this LES. |
LECs used | ATM address of the LECS being used. This line also shows the current state of the connection between the LES and the LECS and the virtual circuit descriptor of the circuit connecting them. |
control distribute | Virtual circuit descriptor of the Control Distribute VCC. |
proxy | Status of the LEC at the other end of the Control Distribute VCC. |
lecid | Identifier for the LEC at the other end of the Control Distribute VCC. |
ST | Status of the LEC at the other end of the Control Distribute VCC. Possible states are Init, Conn, Waiting, Adding, Joined, Operational, Reject, and Term |
vcd | Virtual channel descriptor used to reach the LEC. |
pkts | Number of packets sent by the LES on the Control Distribute VCC to the LEC. |
Hardware Addr | The top number in this column is the router-descriptor, while the second number is the MAC-layer address of the LEC. |
ATM Address | ATM address of the LEC. |
This section documents the modified debug lane client command.
Use the debug lane client privileged EXEC command to display information about an LEC. The no form of this command disables debugging output.
debug lane client [packet | state]
packet | (Optional) Displays debug information about each packet. |
state | (Optional) Displays debug information when the state changes. |
Privileged EXEC
Figure 4 shows sample output for the debug lane client packet and debug lane client state commands for an LEC joining an ELAN called elan1.
ATM# debug lane client packet ATM# debug lane client state
The LEC listens for signaling calls to its ATM address (initial state):
LEC ATM2/0.1: sending LISTEN LEC ATM2/0.1: listen on 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: received LISTEN
The LEC calls the LECS and attempts to set up the Configure Direct VC (LECS connect phase):
LEC ATM2/0.1: sending SETUP LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B43.00 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the LECS. The Configure Direct VC is established:
LEC ATM2/0.1: received CONNECT LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: vcd 148
The LEC sends a CONFIG REQUEST to the LECS on the Configure Direct VC (configuration phase):
LEC ATM2/0.1: sending LANE_CONFIG_REQ on VCD 148 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC receives a CONFIG RESPONSE from the LECS on the Configure Direct VC:
LEC ATM2/0.1: received LANE_CONFIG_RSP on VCD 148 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC releases the Configure Direct VC:
LEC ATM2/0.1: sending RELEASE LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: cause code 31
The LEC receives a RELEASE_COMPLETE from the LECS:
LEC ATM2/0.1: received RELEASE_COMPLETE LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: cause code 16
The LEC calls the LES and attempts to set up the Control Direct VC (join/registration phase):
LEC ATM2/0.1: sending SETUP LEC ATM2/0.1: callid 0x61167110 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B41.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the LES. The Control Direct VC is established:
LEC ATM2/0.1: received CONNECT LEC ATM2/0.1: callid 0x61167110 LEC ATM2/0.1: vcd 150
The LEC sends a JOIN REQUEST to the LES on the Control Direct VC:
LEC ATM2/0.1: sending LANE_JOIN_REQ on VCD 150 LEC ATM2/0.1: Status 0 LEC ATM2/0.1: LECID 0 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC receives a SETUP request from the LES to set up the Control Distribute VC:
LEC ATM2/0.1: received SETUP LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B41.01
The LEC responds to the LES call setup with a CONNECT:
LEC ATM2/0.1: sending CONNECT LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: vcd 151
A CONNECT_ACK is received from the ATM switch. The Control Distribute VC is established:
LEC ATM2/0.1: received CONNECT_ACK
The LEC receives a JOIN response from the LES on the Control Direct VC:
LEC ATM2/0.1: received LANE_JOIN_RSP on VCD 150 LEC ATM2/0.1: Status 0 LEC ATM2/0.1: LECID 1 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC sends and LE_ARP request to the LES to obtain the BUS ATM NSAP address (BUS connect):
LEC ATM2/0.1: sending LANE_ARP_REQ on VCD 150 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: TARGET MAC address ffff.ffff.ffff LEC ATM2/0.1: TARGET ATM address 00.000000000000000000000000.000000000000.00
The LEC receives its own LE_ARP request via the LES over the Control Distribute VC:
LEC ATM2/0.1: received LANE_ARP_RSP on VCD 151 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: TARGET MAC address ffff.ffff.ffff LEC ATM2/0.1: TARGET ATM address 39.020304050607080910111213.00000CA05B42.01
The LEC calls the BUS and attempts to set up the Multicast Send VC:
LEC ATM2/0.1: sending SETUP LEC ATM2/0.1: callid 0x6114D354 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B42.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the BUS. The Multicast Send VC is established:
LEC ATM2/0.1: received CONNECT LEC ATM2/0.1: callid 0x6114D354 LEC ATM2/0.1: vcd 153
The LEC receives a SETUP request from the BUS to set up the Multicast Forward VC:
LEC ATM2/0.1: received SETUP LEC ATM2/0.1: callid 0x610D4230 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B42.01
The LEC responds to the BUS call setup with a CONNECT:
LEC ATM2/0.1: sending CONNECT LEC ATM2/0.1: callid 0x610D4230 LEC ATM2/0.1: vcd 154
A CONNECT_ACK is received from the ATM switch. The Multicast Forward VC is established:
LEC ATM2/0.1: received CONNECT_ACK
The LEC moves into the OPERATIONAL state:
%LANE-5-UPDOWN: ATM2/0.1 elan elan1: LE Client changed state to up
The following output is from the show lane client command after the LEC joins the ELAN as shown in the debug lane client command output:
ATM# show lane client LE Client ATM2/0.1 ELAN name: elan1 Admin: up State: operational Client ID: 1 LEC up for 1 minute 2 seconds Join Attempt: 1 HW Address: 0000.0ca0.5b40 Type: token ring Max Frame Size: 4544 Ring:1 Bridge:1 ELAN Segment ID: 2048 ATM Address: 39.020304050607080910111213.00000CA05B40.01 VCD rxFrames txFrames Type ATM Address 0 0 0 configure 39.020304050607080910111213.00000CA05B43.00 142 1 2 direct 39.020304050607080910111213.00000CA05B41.01 143 1 0 distribute 39.020304050607080910111213.00000CA05B41.01 145 0 0 send 39.020304050607080910111213.00000CA05B42.01 146 1 0 forward 39.020304050607080910111213.00000CA05B42.01
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Posted: Fri Sep 17 06:45:51 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.