How to Configure and Troubleshoot an AIX ATMLE (ATM LAN Emulated Network)


About this document
    Related documentation
ATM LANE filesets
Adding and configuring ATM LANE clients
Using the SMIT fastpath
Configuring TCP/IP interfaces (enx or etx or trx) over LANE clients
Troubleshooting ATM LANE clients

About this document

This document covers the software requirements and configuration of ATM LAN Emulation on AIX Versions 4.1.5, 4.2.1, and 4.3. The IBM ATM LAN Emulation device driver is available for systems running these versions of AIX.

The Forum-Compliant ATM LAN Emulation (LANE) device driver provides a method for non-IP protocols to communicate over ATM such as IPX, Netbios, and SNA. LANE also allows the vast base of applications written for traditional LANs to be run over ATM. This ATM LANE function supports the LAN emulation Client (LEC) as specified in the ATM Forum Technical Committee LAN Emulation Over ATM Version 1.0.

The ATM LANE device driver emulates the operation of Standard Ethernet, IEEE 802.3 Ethernet, and IEEE 802.5 Token-Ring LANs. It encapsulates each LAN packet and transfers over an ATM network. This data can also be bridged transparently to a traditional LAN with ATM/LAN bridges such as the IBM 8281.

Related documentation

The product documentation library is also available:

ATM LANE filesets

The fileset bos.atm.atmle implements the AIX ATM LAN Emulation (LANE) device driver for AIX Versions 4.1.5, 4.2.x and 4.3.x. The fileset is contained on the base install media in AIX Versions 4.2.1 and 4.3. For AIX 4.1.5, it must be purchased separately from your IBM representative as PRPQ P91164.

In order to verify the presence of the fileset in AIX, run the following command:

lslpp -l bos.atm.atmle
If it is installed, the following output displays:
Path: /usr/lib/objrepos
  bos.atm.atmle	APPLIED	ATM LAN Emulation Client Support
Path: /etc/objrepos
  bos.atm.atmle	APPLIED	ATM LAN Emulation Client Support
If your system is at AIX Version 4.1.5, as mentioned above, contact your local IBM representative and request PRPQ P91164. The ATMLE is not supported for versions of AIX prior to 4.1.5. The ATMLE at 4.1.5 is not available on any 4.1.5 install media.

If your system is at AIX Version 4.2.0, contact IBM to obtain refresh or replacement media. A 4.2.1 maintenance upgrade exists which is used to upgrade AIX from to However, this upgrade will not contain the ATMLE filesets.

Adding and configuring ATM LANE clients

An ATM LAN emulation client can be added to the system to communicate over an ATM network using the ATM Forum LANE protocol. A user with root authority can add ethernet or token-ring clients using the smit atmle_panel fastpath (see the following section).

Entries are required for the Local LE Client's LAN MAC Address field and the LES ATM Address or LECS ATM Address fields, depending on the support provided at the LAN emulation server. The MAC address of the atm0 adapter in the client can be used for the local LE client's LAN MAC address.

Configuration help text is also available within the SMIT LE Client add and change menus.

Using the SMIT fastpath

Access the relevant SMIT menu:
	smit atmle_panel
The following menu choices will display:
  List All Defined ATM LE Clients
  Add an ATM LE Client
  Change / Show an ATM LE Client
  Remove an ATM LE Client
  Configure a Defined LE Client
  Generate an Error Report
  Trace an ATM LE Client
Select Add an ATM LE Client and then select an ethernet or token-ring client. The menu fields for ethernet and token-ring are identical except for the Emulated LAN Type. Shown below for discussion is the ethernet ATMLE setup.
                         Add an Ethernet ATM LE Client
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
                                                        [Entry Fields]
  Local LE Client's LAN MAC Address (dotted hex)     []
  Automatic Configuration via LECS                    No                      +
    If No, enter the LES ATM Address (dotted hex)    []
    If Yes, enter the LECS ATM Address (dotted hex)  []
  Local ATM Device Name                              [atm0]                   +
  Emulated LAN Type                                   Ethernet/IEEE 802.3     +
  Maximum Frame Size                                  Unspecified             +
  Emulated LAN Name                                  []
The MAC address of atm0 can be used in the first field. To obtain the address, use the command lscfg -vl atm0 -v. The address is listed as the network address. It consists of 12 digits which must be entered as six octets separated by a period (.). Here is an example of the 12-digit address:

network address = 02608C2CD2DC

The preceding address is entered in the SMIT field as the six octets 2.60.8c.2c.d2.dc. The leading zero can be dropped. To configure additional ATMLE adapters, use a different MAC address. Any MAC address can be used; however, it must be unique in the ELAN for the ARP function to work.

Mandatory entries are required for the Local LE Client's LAN MAC Address and possibly the LES ATM Address or LECS ATM Address, depending on the support provided at the server. If the server accepts the "well-known ATM address" for LECS or well-known PVC, or ILMI at 4.3.2, Automatic Configuration via LECS can be set to yes and the LES and LECS ATM Address fields left blank.

If the server does not support the well-known ATM address for LECS, an ATM address must be entered for either LES (manual configuration) or LECS (automatic configuration). All other configuration attribute values are set to defaults for ease of use, and may additionally be specified by the operator for specific needs. The well-known ATM address was defined by the ATM forum to simplify the ATMLE configuration process at the ATMLE client and provide automatic configuration for ATMLE clients. The address is: Usage of the well-known-address or the well-known pvc, or the ILMI allows the ATM address fields in the above SMIT menus to remain blank. Consult your ATM switch or network support personnel for directions as to the Automatic Configuration via LECS and which ATM address, if any, to use.

The ATM address is inserted in the SMIT field as a 20-byte hexadecimal address using a period (.) to separate the bytes, as in the MAC address field. In addition, leading zeroes in each octet can be dropped. For example:

The default values can be left in the next three fields. The ELAN name is optional unless the LECS has more than one ELAN defined and the LECS is not configured to automatically assign the LEC to the correct ELAN. It must be entered exactly as it is defined at the LECS. Consult your ATM support personnel if you are unsure as to its value. If the name is incorrect, the LANE will not work correctly.

Run SMIT and it should configure the entx or tokx.

Exit SMIT and run the following command:

	 lsdev -Cc adapter
The output follows:
tok1    Available          ATM LAN Emulation Client (token-ring)
ent1    Available          ATM LAN Emulation Client (ethernet)
Configuring Netbios, IPX, AIX connections, or SNA will involve essentially the same process. The PPA (physical point of attachment or adapter number) must be carefully specified in the configuration for these applications if you have additional adapters of the same type as the LAN emulation client. For example, tok0 is a real token-ring adapter and tok1 is the LAN emulation client. The PPA for the LAN emulation client would be 1 (from tok1).

Configuring TCP/IP interfaces (enx or etx or trx) over LANE clients

Before starting, entstat/tokstat should be run to make sure the adapter joins successfully. TCP/IP interfaces can now be configured on these LANE clients via the following SMIT fastpath:
	smit inet
The display will show (this is a partial list of possible LANE interfaces):
  Add a Network Interface
  Add a Standard Ethernet Network Interface
  Add an IEEE 802.3 Network Interface
  Add a Token-Ring Network Interface
Choose one of the above. A small window appears, displaying the interface as available and highlighting the interface designator:
  enx or etx or trx

If an error occurs, check to see if the data entered is correct or contact the IBM AIX Support Center.

Troubleshooting ATM LANE Clients

  1. If pinging to the ATM switch or another client fails, check the tokstat -d tokx or the entstat -d entx output. Look for the ATM address of the ATM LANE client and those of the LECS and the LES servers. If any of these addresses are blank, the ATM address initially entered may be incorrect, the ATM switch is configured incorrectly, or the connection to the ATM switch is bad. The following is an example from the entstat or tokstat command output:
    ATM LAN Emulation Specific Statistics:
    Emulated LAN Name: elan102
    Local ATM Device Name: atm0 
    Local LAN MAC Address: 08.00.5a.99.9e.9d
    Local ATM Address: 
    Auto Configuration With LECS: Yes 
    LECS ATM Address: 
    LES ATM Address:
    In the command output, check the driver flags for correct operation. The flags should be similar to the following:
    Driver Flags:
       Up Broadcast Running
       Simplex Alternate Address
    If Up or Running is missing, there is no contact to the ATM switch. If the Limbo flag is present, that means the client lost contact with one or more LAN emulation servers and is attempting to recover.

    If the Dead flag is present, a hard failure has occurred. Check the system errorlog for additional error messages. If the entstat or tokstat command runs very slowly, use the atmstat command.

  2. Check to make sure there is a proper connection to the ATM switch. This is usually indicated by a port light on the ATM switch. Look for wire fault errors in the error log by using the errpt |grep atm command to identify cable problems. If the connectors on your fiber cables are not keyed or connected with a plastic cover, try reversing the connectors on one end.

  3. Use the following command:
    	atmstat -d atm0
    Assuming there is a good physical connection to the ATM switch, the following command sequence will indicate if the ATM adapter and device driver are working.
    1. Execute the following:
      	atmstat -d atm0 > /tmp/atmstat.out
    2. Wait 10 seconds and then run it again, appending it to the same file (use >>).
      	atmstat -d atm0 >> /tmp/atmstat.out
    3. Edit the file in a text editor and check the following parameters under the Receive Statistics column: Packets and Cells Received. These two parameters should show an increase in the second atmstat, which means the adapter and device driver are working.

    No increase in either parameter means the adapter is not able to receive ATM cells or there may be a problem with the atmsvcd-ATM call manager daemon.

    If either number is not increasing, use the following command to see if the atmsvcd daemons are running:

    ps -ef |grep atm
    The output follows:
    root 2816    1   0 12:08:57      -  0:00 /usr/sbin/atmsvcd
    root 3844 2816   0 12:08:57      -  0:02 /usr/sbin/atmsvcd
    For a single ATM adapter, two atmsvcd processes should exist. If no process exists, restart the daemon /usr/sbin/atmsvcd. If only one process is running, run the following command (the child pid in the preceding example is 3844):
    kill -9 [child pid]
    Then restart the daemons. The addition of a second or additional ATM adapter only adds one atmsvcd per adapter. Only the atm0 has two atmsvcd processes.

    If the atmsvcd daemons exist, then try rebooting if possible. The adapter or the device driver may be hung. If the reboot fails to free up the ATM, contact the IBM AIX Support Center if necessary.

  4. The UNI version is defined at both the switch and AIX system clients. The UNI version can be either 3.0 or 3.1. In addition, the AIX system will set the UNI version to auto-detect. In some cases problems have occurred such that the ATM switch does not recognize or is incompatible with the auto-detect function. Check the UNI version of the ATM adapter with lsattr -El atmx or via the smit fastpath with smit chg_atm. Try changing the UNI version to the fixed value of that of the ATM switch.

  5. Many problems occur when the switch is incorrectly configured. If no one can ping on the switch and you have double-checked the configuration on AIX, please contact the switch administrator to verify the configuration.

  6. Ensure that the latest atm and atmle fileset PTFs are installed on your client. Many of the switch ping problems are defects and can be solved by upgrading the filesets to their latest PTF levels. The filesets consist of the atm device driver, the atmle LAN device driver, and the common atm filesets. Contact the IBM AIX Support Center to obtain these filesets.

[ Doc Ref: 91185999914814     Publish Date: Nov. 14, 2000     4FAX Ref: 7684 ]