Table Of Contents
Supported Standards, MIBs, and RFCs
Monitoring and Maintaining LANE Flush Process
Disabling LANE Flush Process Example
Disabling LANE Flush Process
This feature module describes the Disabling LAN Emulation (LANE) Flush Process feature and includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
The Disabling LANE Flush Process feature provides the ability to disable the LE_FLUSH process and make the transition from using the BUS to using a data direct virtual channel connection (VCC). With this feature configured, the LAN Emulation Clients (LECs) in the node will not send a flush request and will directly use a data direct VCC for data transfer. This feature disables the LE_FLUSH process for all the LECs in a Cisco networking device.
Benefits
Use of the Disabling LANE Flush Process feature is recommended to prevent the initial packet drops during the establishment of LANE Direct VC.
Supported Platforms
This feature is supported on the following platforms:
•
All router platforms with ATM interfaces that support LAN emulation
•
Catalyst 5000 ATM LANE modules
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
No new or modified MIBs are supported by this feature.
To obtain lists of MIBs supported by platform and Cisco IOS release and to download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Configuration Tasks
See the following section forrequired configuration tasks for the Disabling LANE Flush Process feature:
•
Disabling LANE Flush Process
Disabling LANE Flush Process
To keep LECs from sending LE_FLUSH messages to the remote LEC, use the following command in interface configuration mode:
Monitoring and Maintaining LANE Flush Process
To display the running configuration, use the following show command in EXEC mode:
Configuration Examples
This section provides the following configuration example:
•
Disabling LANE Flush Process Example
Disabling LANE Flush Process Example
The following example shows a running configuration and the LE_FLUSH process disabled for all LECs:
more system:running-configBuilding configuration...Current configuration :496 bytes!! Last configuration change at 11:36:21 UTC Thu Dec 20 2001!version 12.1service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname donner_b!no lane client flush!interface ATM0atm preferred phy Aatm pvc 1 0 5 qsaalatm pvc 2 0 16 ilmino atm ilmi-keepalive!interface ATM0.1 multipointlane config-atm-address 47.009181000000001007385101.0050A2FEBC43.00lane client ethernet 100 elan1!line con 0line vty 0 4no login!endCommand Reference
This section documents the new lane client flush command. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
lane client flush
To enable the flush mechanism of a LAN Emulation Client (LEC), use the lane client flush global configuration command. To disable the flush mechanism of a LEC, use the no form of this command.
lane client flush
no lane client flush
Syntax Description
This command contains no arguments or keywords.
Defaults
All the LECs perform the LANE LE_FLUSH process by default.
Command Modes
Global configuration
Command History
Usage Guidelines
In Cisco IOS releases 12.1(3)T and later releases, the lane client flush command will be hidden and will not be visible in the configuration.
Configuring the no lane client flush command on a Cisco networking device is recommended to prevent the initial packet drops during the establishment of LANE data direct virtual connection (VCC).
Use the no lane client flush command to keep LANE clients from sending LE_FLUSH messages to the remote LANE client. This will also allow the LANE clients to process the LE_FLUSH messages from the remote LANE clients.
Note
Configuring the no lane client flush command on a Cisco networking device does not guarantee the orderly delivery of incoming packets. There is a chance of receiving out of order packets at the destination during the establishment of LANE data direct VCC.
Examples
The following example disables the flush mechanism of a LEC:
no lane client flushRelated Commands
