|
|
This release note describes the features, modifications, and caveats for the Cisco ATM SBus adapter Release software 1.1.
The Cisco ATM SBus Adapter User Guide is available in printed form and in electronic form on UniverCD.
This section describes warnings and cautions about using the Cisco ATM SBus adapter software Release 1.1.
Before you implement and use the Cisco ATM SBus adapter on a Solaris or SunOS system, consider the following information:
BEGIN_LINK_GLOBAL
SONET_FRAMING_TYPE:STS-3c
END_LINK_GLOBALS
Before you implement and use the Cisco ATM SBus adapter on a SunOS system, consider the following information:
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:
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 Make sure you remove any previously installed software by using the pkgrm command (Solaris only).
Step 7 Make sure the software was successfully installed using the pkgadd command (Solaris) or the extract_unbundled default command for installation from diskettes or install_unbundled for installation from a network directory (SunOS).
Step 8 Make sure all files were installed. Refer to the "On the CIO server, the SunOS package image will be kept in a tar format. You need to copy the image from the CIO server into a directory with approximately 20MB of available space. The contents of this tar image can be extracted under the current directory using the following command" 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 Set up /etc/catmilmi.db with the correct network prefix on both SunOS and Solaris if the switch does not support ILMI functions. Also, insure that the correct steps for static registration are followed per the Section "ILMI Registration on the Switch" found on page three of this release note.
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.
| 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.* | Kill process | Kill process | -- |
| PVC
Switch
|
Set configuration the same for both ARP client and ARP server. | Configure the file for the appropriate operating system.* | Kill process | Kill process | Set PVC |
| PVC
Switch
|
Configure for either ARP client or ARP server. | -- | Normal boot | Normal boot | Set PVC |
| PVC
Switch
|
Configure for either ARP client or ARP server. | -- | Normal boot | Normal boot | Set PVC |
SVC
|
Configure for either ARP client or ARP server. | -- | Set switch prefix in /etc/catmilmi.db. | Normal boot | Add route using route add command. |
SVC
|
Configure for either ARP client or ARP server. | -- | -- | Normal boot | Automatic |
*NOTE: 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.
For configurations with no support for signalling, such as the back-to-back connection of two adapters on the end systems or an AIP to an adapter on an end system without going through a switch, the following sequence is required on the end station. The same setup is required when the switch to which these end stations are connected does not support signalling.
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 catm.o
zipc_svc?W 0 (0 to turn SVC off; 1 to turn SVC on)
^D
# reboot
For configurations with no support for signalling, such as the back-to-back connection of two adapters on the end systems or an AIP to an adapter on an end system without going through a switch, the following sequence is required on the end station. The same setup is required when the switch to which these end stations are connected does not support signalling.
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)
You configure the catmlancfg.db file depending on the type of configuration, as follows:
Refer to the appropriate section in the user guide for information on configuring the catmlancfg.db file.
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_LINKTo 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_LINKTo set up an ATM client without an ARP server, modify the catmlancfg.db 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_LINKTo 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
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_LINKThe /etc/atms file contains the ATM addresses for clients and servers. An ATM address is 20 bytes in length and is constructed using the following values:
The following is a sample from the /etc/atms file showing ATM addresses for various clients:
#
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
#
The following is a sample from the /etc/atms file showing ATM addresses for various servers:
#
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
#
The /etc/catmilmi.db file contains the network prefix (the first 13 bytes of the ATM address). The following is a sample from the /etc/catmilmi.db file showing the network prefix (NET_PREFIX):
#
BEGIN_LINK 0
NET_PREFIX : 39:00:00:00:00:00:00:00:00:00:00:00:00
END_LINK
#
The /etc/hosts file contains IP addresses of clients. The following is a sample from the /etc/hosts file showing IP addresses for clients:
#
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)
#
To add the Cisco ATM SBus adapter software, enter the following command:
root@SYS1% add_drv -i 'ZATMSBUS' catm
To remove the Cisco ATM SBus adapter software, enter the following command:
root@SYS1% rem_drv catm
The procedure for installing the Cisco ATM SBus adapter software for SunOS in the Cisco ATM SBus Adapter User Guide is for local installation. The following procedure is for network installation:
Step 1 Issue the following command to create and extract files into the directory called "+install":
When prompted, remove the inserted diskette and insert the next one. The +install directory can then be exported and mounted on the client system.
Step 2 On the client system, enter the following commands:
The script is executed, as follows:
Step 3 Edit the system network configuration files and ATM adapter configuration files as described in the "Configure the Adapter" section of the Cisco ATM SBus Adapter User Guide.
Step 4 Reboot the system log using the /usr/etc/reboot command.
On the CIO server, the SunOS package image will be kept in a tar format. You need to copy the image from the CIO server into a directory with approximately 20MB of available space. The contents of this tar image can be extracted under the current directory using the following command:
tar xvf <tarimagename>
From the same directory, execute the ./install_unbundled command to install the SunOS package.
On the CIO server the Solaris package image will be kept in tar format. You must copy the image from the CIO server in to a directory with approximately 4MB of available disk space. The contents of the tar image can be extracted under the current directory using the following command:
tar xvf <tarimagename>
From the same directory, execute pkgadd -d. to install the Solaris package.
Following is a list of files contained in the Cisco ATM SBus adapter software:
/bin/atmstat
/bin/catmilmid
/bin/catmlancfg
/bin/catmsig
/etc/Atmstat
/etc/atmgui.dat
/etc/catmilmi.db.sample
/etc/catmlancfg.db.sample
/etc/catmmib.txt
/etc/rc.local (SunOS Only - Modified by install script)
/etc/rc2.d/S69catm (Solaris Only)
/etc/catmstartup (SunOS Only)
/sys/catm/catm.o (SunOS Only)
/kernel/drv/catm (Solaris Only)
/usr/man/man1/catmilmid.1
/usr/man/man1/catmlancfg.1
/usr/man/man1/catmsig.1
/usr/man/man4/atms.4
Cisco Information Online (CIO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CIO to obtain additional content and services.
Available 24 hours a day, 7 days a week, CIO provides a wealth of standard and value-added services to Cisco's customers and business partners. CIO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CIO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously--a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CIO (called "CIO Classic") supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CIO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CIO in the following ways:
.
.
For a copy of CIO's Frequently Asked Questions (FAQ), contact cio-help@cisco.com. For additional information, contact cio-team@cisco.com.
|
|