Filter
Top Products
SmartSwitch ATM User Guide 2-11
IP Over ATM and LANE Creating an Emulated LAN
6. Use the show client command on SW1 to see that the client has reached all the distributed LANE
services and has successfully joined ELAN
mis1.
SW1 # show client
ClientNumber(ALL) :
Client Type IP Address Server Type Server Conn Status
==============================================================================
1 LANE 90.1.1.22 LECS Established Operational
SW1 #
Notice in the example above that creating an ELAN with distributed services is a process of building from the bottom
up: First, the BUS is created so that its address can be specified to the LES. Next, the LES is created so that its address
can be specified to the LECS. Finally, the LECS is created.
If needed, all three ELAN services can exist on separate switches. For example, the BUS can exist on one switch (use
the
add buselan
command), the LES can exist on another switch (use the
add leselan
command), and the LECS can
exist on another switch (use the
add lecselan command).
Note If LNNI is enabled, each associated LES and BUS must reside on the same switch.
See Section 2.2.7, “Using LNNI” for details.
2.2.5 ELAN Join Policies
ATM SmartSwitches provide control over the assigning of clients to ELANs. Control is accomplished by ELAN join
policies. By default, ATM SmartSwitches have a single ELAN join policy defined —
Best Effort. When a client
attempts to join LANE services, the ATM SmartSwitch uses information provided by the client to performs the
Best
Effort ELAN join test.
Note Additional security can be achieved through the use of ATM address filtering. See
Section 8.1 for information regarding ATM address filtering.
Best Effort Elan Join Test
The following describe the Best Effort test.
1. Does the client specify the name of the ELAN it wants to join?
- If yes, check whether an ELAN exists by that name. If an ELAN exists by that name, assign the
client to the ELAN. If no ELAN exists by that name, assign the client to the default ELAN
(ELAN 0).
- If no, check the client against the configuration information stored by the add lecselanlec
command (see The LECSELANLEC Table, on page -13). If an entry exists that corresponds to
the client, assign the client to the ELAN indicated. If the client does not correspond to an entry,
assign it to the default ELAN (ELAN 0).