Current adapters supported by IBM:
ATM support at AIX version 4.x is installed via the following filesets provided on the base operating system install media:
IMPORTANT: ATM is not supported from AIX Version 4.1.1 through Version 4.1.3.
NOTE: At AIX levels 4.1.4 and 4.1.5, common ATM device driver software is contained in the devices.mca.8f7f.com fileset. This fileset needs to be at the latest level regardless of which ATM adapter (MCA or PCI) you have installed.
NOTE: At AIX 4.2.x and later, common ATM device driver software is contained in
the fileset devices.common.IBM.atm.rte. As in AIX level 4.1.x, this fileset needs to be
at the latest level for either PCI or MCA ATM adapters.
Related documentation
The product documentation library is also available:
http://www.rs6000.ibm.com/resource/aix_resource/Pubs/index.html
An ATM address is 20 bytes (40 hex digits) in length and listed in dotted decimal format. Following is an ATM address example:
AC.3E.21.11.6F.3.AA.16.19.A0.3.D.12.33.D4.A2.CC.D.8.5The leading zero digit can be dropped.
When configuring the system as an ARP server-client, it is necessary to know the ATM address of the ARP server. Usually you obtain this address from your network support or your ATM switch support administrator. It must be correct and entered correctly through SMIT as described subsequently. Otherwise, the system ATM client will not register with the ATM switch and ARP server.
If you are configuring the system as an ARP server-client, set the
Connection Type field to svc_c.
If you are configuring the system as an ARP server, then set Connection Type
to svc_s.
Multiple interfaces may be configured on one ATM adapter (that is, at0,
at1, at2, and so on). Therefore, it is necessary to specify the interface
designator (at0, at1, and so on) in the Network Interface field.
A unique network address must be assigned to each interface; otherwise,
confusion in the routing table will exist. For example, you may not be able to ping
or telnet out on one of the duplicated networks.
AIX supports only network interfaces which have unique network addresses.
Due to the possibility of having multiple adapters in the system,
the ATM physical device on which the atx interface
is being created must be specified in the Alternate Device field.
When the system is an ARP server-client as stated above, the 20-byte
ARP server ATM address must be entered in the ATM Server Address field.
The ATM server address is blank when configuring the system as an
ATM ARP server.
No increase in either parameter means the adapter is not able to receive
ATM cells or there may be a problem with the atmsvcd--the ATM call manager
daemon.
If either number is not increasing, check to see if the atmsvcd daemons
are running with the following command:
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 your AIX support center
if necessary.
[ Doc Ref: 90605195514806 Publish Date: Jan. 31, 2001 4FAX Ref: 7467 ]
ATM ARP server-client configuration
Use the SMIT fastpath mkinetat. Confirm or input the following settings:
* INTERNET ADDRESS (dotted decimal) (1.1.1.1)
Network MASK (hexadecimal or dotted decimal) (255.255.255.0)
Network Interface (at0)
Connection Type svc_c
ATM Server Address (20 byte ARPserver ATM address)
Alternate Device (atm0)
Idle Timer ()
* ACTIVATE the Interface after Creating it? yes
NOTE: Do not begin the ARP server address with an 0x designation.
ATM ARP server configuration
To configure an AIX Version 4 system to be an ARP server, use the SMIT
fastpath mkinetat:
* INTERNET ADDRESS (dotted decimal) (1.1.1.1)
Network MASK (hexadecimal or dotted decimal) (255.255.255.0)
Network Interface (at0)
Connection Type svc_s
ATM Server Address ()
Alternate Device (atm0)
Idle Timer ()
* ACTIVATE the Interface after Creating it? yes
NOTES:
Determining the ATM address of an AIX ARP server client
After configuring the system as an ARP server-client, verify that
registration with the ARP server has occurred by checking the ARP table
for the presence of the local ATM address and the ARP server ATM address.
When you execute arp -t atm -a the first line will appear as:
at0(2.2.2.160) 47.0.5.80.ff.e1.0.0.0.f2.15.16.45.8.0.5a.99.a.cc.0
The second line will appear similar to the following:
(2.2.2.125) 47.0.5.80.ff.e1.0.0.0.f2.15.16.45.8.0.5a.89.0.33.0
Note that the first 13 bytes are the same in both lines. These bytes are the switch prefix.
The next six bytes in the first address (that is, 14 -19) should be the MAC address
of the ATM adapter. If either line is all or mostly zeroes, then contact
with the ARP server has failed. See the next section, "Troubleshooting SVCs",
for additional tips.
Troubleshooting SVCs
Assuming there is a good physical connection to the ATM switch, the following
command sequence will tell you if the ATM adapter and device driver
are working.
atmstat -d atm0 >> /tmp/atmstat.out
ps -ef |grep atm
The output should read:
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, execute kill -9 <child pid>
(the child pid in the example is 3844)
and then restart the daemons. The addition of the second or additional ATM
adapter in the system only adds one atmsvcd per adapter. Only the atm0 has two
atmsvcd processes.