This fax will cover software requirements and configuration of ATM permanent
virtual circuits (PVC) on AIX 3.2.5, 4.1.4, and 4.2.
Current adapters supported by IBM are as follows:
MCA Turboways 100 ATM adapter - AIX 3.2.5, 4.1.4, and 4.2.0
MCA Turboways 155 ATM adapter - AIX 3.2.5, 4.1.4, and 4.2.0
MCA Turboways 155 ATM UTP/STP adapter - AIX 3.2.5, 4.1.5, 4.2.0
PCI Turboways 25 ATM UTP/STP adapter - AIX 4.2.1 (FC 2998)
PCI Turboways 155 ATM adapter - AIX 4.2.1 (FC 2988)
AIX Version 3.2.5: Drivers are installed via PTF U438028 for the Turboways
100 adapter and U443303 for the Turboways 155 and Turboways UTP/STP adapter.
ATM support at AIX version 4.x is installed via the following filesets:
MCA Turboways 155 ATM software:
devices.mca.8f67.com
devices.mca.8f67.rte
devices.mca.8f67.ucode
devices.mca.8f67.diag (4.1.5 and 4.2.x)
devices.common.IBM.atm.rte (4.2.x)
MCA Turboways 155 ATM UTP/STP software: (4.1.5, and 4.2.x)
devices.mca.8f64.diag
devices.mca.8f64.rte
devices.common.IBM.atm.rte (4.2.x)
MCA Turboways 100 ATM software:
devices.mca.8f7f.rte
devices.mca.8f7f.ucode
devices.mca.8f7f.com
devices.mca.8f7f.diag (4.1.5 and 4.2.x)
devices.common.IBM.atm.rte (4.2.x)
PCI Turboways 25 STM UTP/STP software:
devices.pci.14105300.rte
devices.pci.14105300.diag
PCI Turboways 155 ATM software:
devices.pci.14107c00.rte
devices.pci.14107c00.diag
devices.pci.14107c00.com
ATM is not supported from AIX Version 4.1.1 through 4.1.3
PVCs can be configured in a back-to-back ATM network between two systems, or
as a point-to-point connection to a switch.
It is EXTREMELY important in a back-to-back ATM 155 Mbs network that one
node provide sonet clocking. This is not an issue in an ATM 100 Mbs network.
To provide sonet clocking execute the following:
- smit fastpath chg_atm
- select the ATM adapter that is being configured in a back-to-back network.
- At the very bottom of the smit screen, set Provide SONET clock to 1.
Note: It is only necessary to do this on one node of the back to back
ATM 155 Mbs network.
If you get a "device busy" message, make sure all ATM IP interfaces are
detached and/or removed and ATM LAN emulation clients are defined and/or
removed.
The first step is to configure the IP interface for the PVC:
Execute the following commands:
- AIX Version 4.x IP Interface Configuration (smit mkinetat), execute as
follows:
* INTERNET ADDRESS (dotted decimal) (1.1.1.1)
Network MASK (hexadecimal or dotted decimal) (255.255.255.0)
Network Interface (at0)
Connection Type pvc
ATM Server Address ()
Alternate Device (atm0)
Idle Timer ()
Best Effort Bit Rate (UBR) in Kbits/sec ()
* ACTIVATE the Interface after Creating it? yes
- AIX Version 4.x PVC Configuration (smit mkatmpvc), execute as follows:
PVC Description (Optional) ()
* VPI:VCI (0:1000)
Network Interface (at0)
Destination IP Address ()
Automatically Discover Destination IP Address yes
LLC Encapsulation yes
Note: Alternatively, you may change Automatically Discover
Destination IP Adress to "no" and set the Destination IP address of the node
you are connecting to in a back-to-back network or the switch PVC.
- AIX Version 3.2.5 IP Interface Configuration (smit mkinetat), execute the
following:
Device Name atm1aio0
Network Interface at0
INTERNET ADDRESS (dotted decimal) (1.1.1.1)
Network MASK (hexadecimal or dotted decimal) (255.255.255.0)
ACTIVATE the Interface after Creating it? yes
Enable Hardware LOOPBACK Mode? no
Enable SVCs no
Is this an ARP server? no
If this is an ARP client
ARP Server ATM Address (dotted hexadecimal) ()
- AIX Version 3.2.5 PVC Configuration (smit mkpvcat), execute the following:
* ATM Network Interface at0
PVC Description (Optional) ()
* VPI:VCI (0:1000)
* LLC Encapsulation yes
If LLC Encapsulation
Automatically Discover Destination IP Address yes
If No Automatic Destination Discovery
Destination IP Address (dotted decimal) ()
Note: Alternatively, you may change Automatically Discover
Destination IP Adress to "no" and set the Destination IP address of the node
you are connecting to in a back-to-back network or the switch PVC.
- Verify you are using the correct VPI:VCI
- If this is a PVC to a switch, 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 with the "errpt |grep
atm" command to identify cable problems. If the SC connectors on your fiber
cables are not keyed or connected with a plastic cover, you may want to try to
reverse the connectors on one end of the connection. 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.
- A migration of an AIX Version 3.2.5 system with the ATM support PTF
installed to an AIX 4.1.4 system currently shows problems removing the old ATM
software. Please contact support for this solution.
- Problems of intermittent communications loss or inability to ping on reboot
are often caused by defects.
IX57795 Abstract: SNMP: doesn't return ifPhysAddr and
ifType for ATM and FCS
IX59407 Abstract: System hang/crash on 42T with GXT500
and ATM card
IX58475 Abstract: Flush for ATM HACMP/HANFS done too early
IX57531 Abstract: HACMP NFS process hung over ATM
IX56752 Abstract: HACMP 4.1.1 Support for TURBOWAYS 155 ATM
Adapter
IX57157 Abstract: HACMP over ATM problem
IX54527 Abstract: Information in ATM database is not consistent
IX61232 Abstract: SNMPD PROVIDES THE WRONG CODE FOR ATM
IX60278 Abstract: Flush for ATM HACMP/HANFS done too early
IX60125 Abstract: Default route on other interface is removed
when ATM is changed
IX64179 Abstract: Need to establish ifreqs betweem ATM filesets
IX62539 Abstract: detach/re-attach ATM interface has delay in
recovery
IX65933 Abstract: The default route thru ATM is removed after
chdev on ATMIF
IX66833 Abstract: ipreport doesn't work right for iptrace
over ATM
IX58650 Abstract: update the cdli_atmuser.h
IX56879 Abstract: atm_dmx_add_status fails if adapter
configured with support
IX64126 Abstract: chgatm does not allow enable alt mac addr
if addr not changed
IX65997 Abstract: CCET: Illegal Trap in muxatmd when fireball
is shutdown
IX66314 Abstract: atmsvcd taking a lot of CPU
IX58996 Abstract: ATM 155 stops transmitting on TCP Streaming
tests
IX64211 Abstract: PERF: Start DMAing data at 512 bytes vs
2048 on ATM
IX61479 Abstract: Delete PVC ATMARP crash system
IX61592 Abstract: Race condition in ATM CM
IX62203 Abstract: ATM address display
IX62488 Abstract: detach/re-attach ATM interface has delay
in recovery
IX64357 Abstract: accept()ed and NDD_ATM_ACCEPTed socket
returns ENOTCONN
IX64847 Abstract: accept()ed and NDD_ATM_ACCEPTed socket
returns ENOTCONN
IX62115 Abstract: SNMPD PROVIDES THE WRONG CODE FOR ATM
IX64108 Abstract: chgatm does not allow enable alt mac addr
if addr not chang
IX59558 Abstract: atm call manager fails to accept certain calls
IX61591 Abstract: atm signalling daemon fails to accept certain
calls
IX64980 Abstract: CCET: Illegal Trap in muxatmd when
fireball is shutdown
IX66288 Abstract: atmsock.c bug on bhli matching
How to Configure ATM Permanent Virtual Circuits: atm.pvc.325.414.42.tcp ITEM: FAX
Dated: 98/09/01~00:00 Category: tcp
This HTML file was generated 99/06/24~12:41:56
Comments or suggestions?
Contact us