Table of Contents

Cisco ATM SBus Adapter Release Note for Release 1.1

Documentation
Important Notes
Solaris and SunOS Systems
SunOS Systems Only
ILMI Registration on the Switch
Troubleshooting the Adapter Installation and Configuration
Setting Systems for Connecting Adapters Back to Back (SunOS)
Setting Systems for Connecting Adapters Back to Back (Solaris)
Modifying the catmlancfg.db File
PVC Connection to ARP Server (Client)
PVC Connection to ARP Server (Server)
ATM Client Without ARP Server (All Systems)
SVC Connection to an ARP Server (Client)
SVC Connection to an ARP Server (Server)
Sample /etc/atms File
Sample /etc/catmilmi.db File
Sample /etc/hosts File
Adding the Cisco ATM SBus Adapter Software
Removing the Cisco ATM SBus Adapter Software
Network Installation for SunOS
Cisco ATM SBus Adapter Software Files
Cisco Information Online

Cisco ATM SBus Adapter Release Note for Release 1.1

These release notes describe the features, modifications, and caveats for the Cisco ATM SBus adapter Release software 1.1.

Documentation

The Cisco ATM SBus Adapter User Guide is available in printed form and in electronic form on UniverCD.

Important Notes

This section describes warnings and cautions about using the Cisco ATM SBus adapter software Release 1.1.

Solaris and SunOS Systems

Before you implement and use the Cisco ATM SBus adapter on a Solaris or SunOS system, consider the following information:

• This software has been tested with Solaris 2.3, Solaris with mandatory patch level 1, and Solaris 2.4. Make sure to apply any mandatory patches to your operating system. On a Solaris system, to display installed patches, enter the showrev -p command.
  

• Currently, only one Cisco ATM SBus adapter per host is supported.
  

• The Cisco ATM SBus adapter does not support early versions of the SPARCstation 10-model 40 with bus speeds less than 20MHz. These workstations will exhibit cell loss (reported as CRC errors) under some heavily-loaded conditions.
  

• The Cisco ATM SBus adapter utility does not save permanent ARP table entries. To save permanent ARP table entries, modify the catmlancfg.db file.
  

• When you use Cisco ATM SBus adapter utility to initialize and then delete a VLAN without starting it, the Cisco ATM SBus adapter driver does not recognize that the VLAN existed. A"no such interface" error message appears. This error message can be ignored.
  

• If you use the window manager menu (accessed by clicking on the icon at the top left corner of the window) instead of the OK or Close options to exit windows that are periodically updated, the Cisco ATM SBus Adapter utility will exit with a segmentation fault. This fault is recorded and stored in a core dump files.
  

• When you select menu options in the Cisco ATM SBus Adapter utility, the windows displayed are inactive until subwindows are closed.
  

• The Cisco ATM SBus Adapter Utility can be accessed from a remote system by setting the DISPLAY environment variable appropriately, just like for any other X application. You cannot access the Cisco ATM SBus Adapter utility remotely using Telnet.
  

• The default MTU size is 9180. In Solaris, if the MTU size for a VLAN is changed using atmstat or the catmlancfg utility, the MTU size must be set explicitly to the new value in the IP layer using the ifconfig command:
  

ifconfig <interface_name> mtu <mtu_size>

In SunOS, the MTU size cannot be changed.

• The Cisco ATM SBus adapter utility does not function as expected if the Numlock function on the keyboard has been activated.
  

• Some tables shown in the Cisco ATM SBus adapter utility are wider than the normal screen width. You can view the right portion of the table by scrolling to the right. Data in these tables is updated after a preset interval. When data is updated, the screen is returned to the left portion of the table. To ease this inconvenience, set the refresh interval to a longer period of time, so that the right side of the screen is visible for a longer period.
  

• The Timer value for the ARP table (shown in the Cisco ATM SBus adapter utility) is in minutes.
  

• Performance on the SPARCstation 5 is relatively poor.
  

• As of this release date, this release has not been tested on a SPARCserver 2000. Contact Cisco's Technical Assistance Center for details on the status of the supportability of this release on a SPARCserver 2000.
  

• You can set the physical transmission mode to SDH or SONET by modifying the catmlancfg.db file. The transmission mode can be specified after the line "BEGIN_LINK" and before the definition of VLANs.
  

The syntax is as follows:

SONET_FRAMING_TYPE: STS-3c|SDH

The following example shows how to set the transmission mode to SONET (STS-3c):

BEGIN_LINK_GLOBAL
  SONET_FRAMING_TYPE:STS-3c
END_LINK_GLOBALS

SunOS Systems Only

Before you implement and use the Cisco ATM SBus adapter on a SunOS system, consider the following information:

• The Cisco ATM SBus adapter software release 1.1 for SunOS might not be included in this package. If the diskettes for this release have not been included in this package, contact Cisco's Technical Assistance Center for current information about the availability of this release.
  

• Cisco ATM SBus adapter software release 1.1 has been tested with SunOS 4.1.3, patched level U1.
  

• The Cisco ATM SBus adapter driver for SunOS cannot be unloaded. However, you can remove the driver using the /etc/uninstall_Catm command.
  

• In SunOS, the IP layer supports packet sizes of up to 32K only. If you attempt to transmit or receive packets greater than this size, an error is reported.
  

ILMI Registration on the Switch

If you are using the adapter with a switch that does not support ILMI registration, you must set up manual ILMI registration on the switch. For example, the LightStream 100, Release 2.5 or lower does not support ILMI registration. To set up manual registration of the routes on the switch, use the route add command. For example, to add the route for an end station with IP address 99.1.1.145, connected to port 12, issue the following command:

route add 390000000000000000000000000000006301019100 nsap 12 5 0 0

where the values are as follows:

• 39000000000000000000000000000000 is the net prefix specified in the /etc/catmilmi.db file
  

• 63010191 is the end station identifier (ESI) address (the IP address in hexidecimal)
  

• 00 is the selector
  

• nsap is the type
  

• 12 is the primary line number
  

• 5 is the secondary line number
  

• 0 is the first tunneling VPI number
  

• 0 is the secondary tunneling VPI number
  

Troubleshooting the Adapter Installation and Configuration

For the adapter to function properly, it must be installed and set up correctly for your configuration. This section contains steps to follow for troubleshooting your configuration. It also contains sample files for specific configurations.

Use the following guidelines for setting up or troubleshooting your configuration:

Step 1 Make sure that the system memory is at least 32 MB.

Step 2 Make sure that the operating system has the most current patches installed for Solaris 2.3/2.4 or SunOS 4.1.3/4.1.4.

Step 3 Make sure the adapter is installed properly in the correct SBus slot.

Step 4 Make sure the green LED light on the adapter is on.

Step 5 Make sure the LED on the switch port to which the adapter is connected is steady green.

Step 6 If the adapter software was previously installed, did you remove it using the pkgrm (Solaris only)?

Step 7 Was the software successfully installed using the pkgadd command (Solaris) or the extract_unbundled command (SunOS).

Step 8 Make sure all files were installed. Refer to the "Cisco ATM SBus Adapter Software Files" section for a list of installed files.

Step 9 Make sure the /etc/catmlancfg.db file is configured for each workstation.

Step 10 Make sure the adapter driver is installed properly (/dev/catm,prtconf).

Step 11 Make sure the IP addresses are set up properly (/etc/hosts).

Step 12 Make sure the netmasks file is set up properly (/etc/netmasks).

Step 13 If the switch does not support ILMI functions, make sure the correct netprefix exists on SunOS workstations.

Step 14 Make sure the netprefix is set up for the switch.

Step 15 Make sure the catmsig and catmilmid files exist in the /etc/rc2.d/S69catm file (Solaris) or the /etc/catmstartup file (SunOS).

Step 16 Execute the ping command after the systems are booted.

Step 17 Make sure that the configuration is correct. Refer to Table 1 for configuration specifications for your particular configuration.

Table 1 : Configuration Matrix

Configuration	/etc/catmlancfg.db	/etc/system	/bin/catmilmid	/bin/catmsig	Switch
PVC back to back No switch	Set configuration the same for both ARP client and ARP server.	Configure the file for the appropriate operating system. Refer to the "Setting Systems for Connecting Adapters Back to Back (SunOS)" section or the "Setting Systems for Connecting Adapters Back to Back (Solaris)" section, as appropriate.	Kill process	Kill process	---
PVC Switch no signalling (UNI 3.0) no ILMI	Set configuration the same for both ARP client and ARP server.	Configure the file for the appropriate operating system. Refer to the "Setting Systems for Connecting Adapters Back to Back (SunOS)" section or the "Setting Systems for Connecting Adapters Back to Back (Solaris)" section, as appropriate.	Kill process	Kill process	Set PVC
PVC Switch signalling (UNI 3.0) no ILMI	Configure for either ARP client or ARP server.	---	Normal boot	Normal boot	Set PVC
PVC Switch signalling (UNI 3.0) ILMI	Configure for either ARP client or ARP server.	---	Normal boot	Normal boot	Set PVC
SVC signalling (UNI 3.0) no ILMI	Configure for either ARP client or ARP server.	---	Set switch prefix in /etc/catmilmi.db.	Normal boot	Add route using route add command.
SVC signalling ILMI	Configure for either ARP client or ARP server.	---	---	Normal boot	Automatic

Setting Systems for Connecting Adapters Back to Back (SunOS)

For SunOS systems, to connect adapters back to back, install the patch for the Cisco ATM SBus adapter driver binary as follows:

# cd /sys/catm
# adb -w zz.o
zipc_svc?W 0 (0 to turn SVC off; 1 to turn SVC on)
^D
# reboot

Setting Systems for Connecting Adapters Back to Back (Solaris)

For Solaris systems, to connect adapters back to back, add the following line to the /etc/system file:

set catm:zipc_svc = 0 (0 to turn signalling off)

Modifying the catmlancfg.db File

You configure the catmlancfg.db file depending on the type of configuration, as follows:

• PVC Connection to ARP Server (Client)
  

• PVC Connection to ARP Server (Server)
  

• ATM Client Without ARP Server (All Systems)
  

• SVC Connection to an ARP Server (Client)
  

• SVC Connection to an ARP Server (Server)
  

Refer to the appropriate section for guidelines on configuring the catmlancfg.db file.

PVC Connection to ARP Server (Client)

To set a PVC connection to a PVC ARP server, modify the catmlancfg.db file on the client as follows:

BEGIN_LINK 0
 
  BEGIN_VLAN 0
     PROTOCOL : IPATM
     MYIPADDR : qaclient-ip0 (Client host name in /etc/hosts file)
     IPARPSERVER_CONNECT_METHOD : PVC 
     IPARPSERVER_CONNECT : VPI=0, VCI=100 (PVC connection using VPI/VCI)
   END_VLAN
 
END_LINK

PVC Connection to ARP Server (Server)

To set a PVC connection to a PVC ARP server, you must modify the catmlancfg.db file on the server as follows:

BEGIN_LINK 0
 
  BEGIN_VLAN 0
     PROTOCOL : IPATM
     MYIPADDR : qaserver-ip0 (Server host name in /etc/hosts file)
     IPARPSERVER_CONNECT_METHOD : LOCAL 
     IPATM_ADD : IPADDR = qaclient-ip0, VPI = 0, VCI = 100 (PVC---Provide client IP, VPI, and VCI)
   END_VLAN

 END_LINK

ATM Client Without ARP Server (All Systems)

To set up an ATM client without an ARP server, modify the catmlancfg file on all systems as follows:

BEGIN_LINK 0
 
   BEGIN_VLAN 0
     PROTOCOL : IPATM
     MYIPADDR : qaclient-ip0 (Client host name in /etc/hosts file)
     IPARPSERVER_CONNECT_METHOD : NONE (No ARP server)
     IPATM_ADD : IPADDR = qatarget-ip0, ATMADDR=qatarget-atm0 C (SVC-Destination IP and ATM)
     IPATM_ADD : IPADDR = qatarget-ip0, VPI=0, VCI=100 (PVC - Destination IP, VPI and VCI)
     IPATM_ADD:   < 1 line for each target system>
   END_VLAN

END_LINK

SVC Connection to an ARP Server (Client)

To set an SVC connection with an ARP server configuration, modify the catmlancfg.db on the client as follows:

BEGIN_LINK 0
 
   BEGIN_VLAN 0
     PROTOCOL : IPATM
     MYIPADDR : qaclient-ip0 (Client host name in /etc/hosts file)
     IPARPSERVER_CONNECT_METHOD : SVC
     IPARPSERVER_CONNECT ATMADDR: qaserver-atm0 (Server host name in /etc/atms file)
   END_VLAN

END_LINK

SVC Connection to an ARP Server (Server)

To set an SVC connection with an ARP server configuration, modify the catmlancfg.db file on the server as follows:

BEGIN_LINK 0
 
   BEGIN_VLAN 0
     PROTOCOL : IPATM
     MYIPADDR : qaserver-ip0 (Server host name entry in /etc/hosts file)
     IPARPSERVER_CONNECT_METHOD : LOCAL
   END_VLAN

END_LINK

#
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:63:01:01:01:00   qaclient-atm0
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:62:01:01:01:00   qaclient-atm1
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:61:01:01:01:00   qaclient-atm2
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:60:01:01:01:00   qaclient-atm3
#

#
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:63:01:01:02:00   qaserver-atm0
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:62:01:01:02:00   qaserver-atm1
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:61:01:01:02:00   qaserver-atm2
39:00:00:00:00:00:00:00:00:00:00:00:00:00:00:60:01:01:02:00   qaserver-atm3
#

#
BEGIN_LINK 0

NET_PREFIX : 39:00:00:00:00:00:00:00:00:00:00:00:00

END_LINK
#

#
100.1.1.150  qaclient    # Ethernet connection (le0)
99.1.1.1  qaclient-ip0  # ATM connection (VLAN 0)
98.1.1.1  qaclient-ip1  # ATM connection (VLAN 1)
97.1.1.1    qaclient-ip2  # ATM connection (VLAN 2)
96.1.1.1    qaclient-ip3  # ATM connection (VLAN 3)
#

root@SYS1% add_drv -i `ZATMSBUS' catm

root@SYS1% rem_drv catm