Model Features: LANE
Some of the important features that the model incorporates are:
- The LANE Client, including an interface process that allows interfacing with higher layer protocols for Ethernet and Token Ring stations, and an LEC process that executes the LANE protocol for data transfer.
- The LANE Service, including a LAN Emulation Server (LES) and the Broadcast and Unknown Server (BUS).
- LANE clients may be end stations, servers, or intermediate devices such as bridges and routers. Clients can be grouped into Emulated Local Area Networks (ELANs) irrespective of their physical location, and a client containing more than one ATM interface can be a member of more than one ELAN.
- During initialization, all LECs issue a setup request with the LES for a control direct Virtual Channel Connection (VCC). The LES receives the request and returns an establish indication. Once the control direct VCC is established, the LECs join the emulated LAN by issuing a join request. LECs that successfully join the emulated LAN will locate the BUS and set up the multicast send VCC. The BUS in turn sets up the multicast forward VCC with the client. The multicast forward VCC is implemented as many point-to-point connections.
- Once an LEC joins an emulated LAN, it can set up data direct VCCs with other ELAN members in order to transfer data traffic. The LEC maintains an Address Resolution Protocol (ARP) cache where addresses of ELAN members are stored.
- Bridge entities that have a LANE interface will register addresses in the LES filtering database for the emulated LAN the interface belongs to. Then, when an LEC attempts to locate a remote address, it issues an address resolution request to the LES, which locates the address in its registered address database.
- When a client is physically added to or removed from a bridge (a topology change), the change is noted in the bridge’s filtering database. This triggers the release of a bridge protocol data unit (BPDU), which carries a flag that indicates a change of topology to all the bridge’s clients. Upon receipt of the BPDU, each client notes the topology change in its ARP database and ages its entries faster using the bridge forward delay timer value.
- When an LEC has a data packet to send, it checks the ARP cache. If an entry exists and a connection to the destination is available, the packet is transferred. If there is no connection available, a connection setup request is issued. If there is no entry in the ARP cache, the data packet is queued and an ARP request is issued to the LES. If the LES does not respond within a given time interval, the packet is sent to the BUS, which broadcasts it to all the LANE clients.