|
|
This chapter explains how to install the SBus adapter software, which includes an FDDI SBus driver and an SNMP agent. If the software needs to be removed from your system, see the appendix "Running the FDDI deinstall Script."
To install the SBus adapter software, you need a SPARCstation or SPARCserver with a floppy disk drive in your network. Separate procedures are included for SunOS 4.1.x (see the following section, "SunOS Installation") and Solaris 2.x and later operating systems (see the section "Installing the Solaris 2.x Driver Using the pkgadd Script" later in this chapter).
You should be familiar with the UNIX system and a UNIX text editor. You also need to know the following:
For the SunOS 4.1.x installation, you should have 2,700 kilobytes (KB) of disk space in the /usr directory. If you are installing a new kernel (linkable driver), make sure you have 1,600 KB available in your root directory for the new kernel. Use the df command to check available disk space.
The Solaris 2.x installation procedure automatically checks for enough disk space.
The SunOS driver floppy disk contains both loadable and kernel-resident drivers. If you use the loadable driver, you can load or unload the driver into the kernel at any time. The loadable driver is appropriate for systems that boot from a local disk. The kernel-resident driver is built into a new kernel.
The SBus adapter software disk contains an installation script called install.fddi that adds an SNMP agent and installs a loadable or kernel-resident driver.
Following is an overview of this section on how to install software packages on your SunOS 4.1.x system:
 | Caution If you are currently running a kernel-resident FDDI driver and want to install the loadable driver, you must remove the kernel-resident driver, then rebuild the kernel. The script will ask you if you want to do this. |
Perform the following tasks to load the new SunOS driver files:
Step 1 Log in to your system as root and change your directory to /usr/local.
Step 2 Insert the SunOS driver installation disk into the SPARCstation floppy disk drive.
Step 3 Use the tar command to copy files from the installation disk to the hard disk, for example:
tar -xvf /dev/rfd0
A cfddi subdirectory will be created in /usr/local.
rcp -r cfddi console:/usr/local
Step 4 Confirm that the cfddi directory contains the following files:
config.fddi dflash.4.1.x
if_fddi.o.sun4c deinstall.fddi
if_fddi.o.sun4m download_flash.README
fddi.INSTALL install.fddi
fddi.load.sun4c.o mibs/
fddi.load.sun4m.o snmpd
fddi_conf.c snmpd.cfddi
fddistat ttcp
README download_flash
Step 5 To remove the disk, enter eject at the prompt.
| Caution If an error disrupts the installation script, stop the installation immediately by pressing Ctrl-C. Review the installation instructions up to this point to make sure that the steps you took were accurate and complete. If you repeat the installation process and continue to see errors, stop the installation and contact the Cisco Systems Technical Assistance Center. |
Now you need to invoke the SBus adapter software installation script using the install.fddi command.
The script asks various questions about the kind of installation you want to perform, and about your system. Specifically, it asks for the following information:
Perform the following tasks to install the SunOS loadable driver:
Step 1 Change the directory to /usr/local/cfddi.
Step 2 At the prompt, enter ./install.fddi to run the install script:
console# ./install.fddi
You have invoked the ./install.fddi script, which is used to install software for FDDI SBus Adapters.
There are two steps to the installation:
1) Install SNMP agent (optional).
2) Install FDDI SBus driver.
Is this install for a diskless station (y/n) [n]
Step 3 At the prompt, enter n if this is a not a diskless station installation.
The following prompt appears:
Step 4 When the SNMP agent installation prompt appears, enter y. The following information appears:
Copying snmpd.cfddi to /etc
Updating /etc/rc.local to start SNMP agent at boot time.
Installation of SNMP agent done.
Do you wish to install the FDDI SBus driver (y/n) [y]
Step 5 When the FDDI SBus driver installation prompt appears, enter y. The following information appears:
Step 6 When the loadable driver prompt appears, enter y. The following prompt appears:
Normally, the Ethernet interface is enabled each time the workstation is booted. If the new CDDI/FDDI interface will be the only network interface on the system, you can stop the Ethernet interface from being enabled at boot time. The installation procedure renames the /etc/hostname.le0 file to /etc/hostname.xx0.
The /etc/rc.boot script still uses the name in this file as the host name for the workstation, but it no longer enables the Ethernet interface.
Step 7 At the Ethernet interface prompt, enter y to allow the Ethernet interface to be used. The FDDI interface prompt appears:
Step 8 Enter the number of FDDI interfaces installed in this workstation.
The FDDI interface host name prompt appears:
console-fddi]: Step 9 Enter the new host name of this workstation or use the default name assigned (the existing name with the -fddi modification). The IP address prompt appears:
You are using NIS, do you want to get ip address from NIS (y/n) [y] ?
Retrieved ipaddr 172.20.43.146 for host console-fddi
Enter IP address for FDDI interface fddi0 [172.20.43.146]:
Step 10 Enter the IP address for this workstation. The FDDI driver loading prompt appears:
Step 11 Most users should enter y to have the FDDI driver loaded after every reboot. After some system configuration information is displayed, the kernel rebuild prompt appears:
Step 12 At the kernel rebuild prompt, enter n because this was a loadable driver installation so the kernel does not need to be rebuilt. The installable configuration screen appears:
Step 13 If your workstation is a yp server and you want to allow it to receive its own yp broadcasts by binding to itself, you must enable fddimode0 using one of the following commands:
Sun4c architecture command:
adb -w fddi.load.sun4c.o
fddimode0?W 1
$q
Sun4m architecture command:
adb -w fddi.load.sun4m.o
fddimode0?W 1
$q
Driver built into kernel command:
adb -w /vmunix
fddimode0?W 1
$q
Step 14 Driver buffers take up input output page buffer (IOPB) space that is used to perform direct virtual memory access (DVMA). If the workstation runs out of IOPB space after installation of the SBus adapter driver, decrease the number of nfddimaxtbd and set the fddimaxcopysz command to 4500. The following command examples show the variables set for a single Sun4c workstation with multiple adapters installed.
Sun4c architecture linkable kernel command:
adb -w fddi.load.sun4c.o
nfddimaxtbd?W 8
fddimaxcopysz?W Ox1194
$q
Driver built into kernel command:
adb -w /vmunix
nfddimaxtbd?W 8
fddimaxcopysz?W Ox1194
$q
Step 15 Power down the system and install the FDDI SBus adapter, or if the adapter is already installed, log out and reboot to cause the system to read the modified rc.local file. Refer to the chapter "Installing the SBus Adapter Hardware."
| Caution If your system is running Network Information Service (NIS), you must also update the NIS databases with the host name and IP address. Refer to the Sun manual System and Network Administration for instructions on how to update NIS databases. You must have an NIS server on the newly created FDDI subnet. |
The installation of the loadable FDDI driver removes any existing /etc/hostname.fddix files to prevent the rc.boot script from bringing up the interfaces.
The installation also modifies the following files:
The installation procedure adds the following text to rc.local to load the loadable driver and bring up the interfaces. This must occur before NIS and other networking daemons are started.
In this example, console-fddi is the name of the fddi interface.
# Load loadable modules.
if [ -f /etc/loadable ]; then
/etc/loadable
fi
ifconfig fddi0 console-fddi netmask + -trailers up
The installation procedure adds the following text to /etc/loadable. If this file does not exist, the installation creates one.
#
# Load the fddi driver.
#
if [ -f /dev/fddi.LOAD ]; then
if [ -f /dev/fddi.AUTOLOAD ]; then
/dev/fddi.LOAD
fi
fi
The installation procedure creates the following files and links in /dev:
/dev/fddi.AUTOLOAD
/dev/fddi.INSTALL -> /usr/local/cfddi/fddi.INSTALL
/dev/fddi.LOAD -> /dev/fddi.INSTALL*
/dev/fddi.MKDEV -> /dev/fddi.INSTALL*
/dev/fddi.RMDEV -> /dev/fddi.INSTALL*
/dev/fddi.UNLOAD -> /dev/fddi.INSTALL*
/dev/fddi.load.sun4c.o -> /usr/local/cfddi/fddi.load.sun4c.o*
/usr/local/cfddi
The following steps describe how to install the SunOS linkable, kernel-resident driver:
Step 1 Change directory to /usr/local/cfddi.
Step 2 At the prompt, enter ./install.fddi to run the install script:
./install.fddi
n
Step 3 At the prompt, enter n if this is a not a diskless station installation.
The following prompt appears:
Step 4 When the SNMP installation prompt appears, enter y to install the cfddi SNMP agent. The following information appears:
Step 5 When the FDDI SBus installation prompt appears, enter y. The following information appears:
Step 6 When the loadable driver prompt appears, enter n to install the kernel-resident driver. The Ethernet interface prompt appears:
Normally, the Ethernet interface is enabled each time the workstation is booted. If the new CDDI/FDDI interface will be the only network interface on the system, you can stop the Ethernet interface from being enabled at boot time. The installation procedure renames the /etc/hostname.le0 file to /etc/hostname.xx0.
The /etc/rc.boot script still uses the name in this file as the host name for the workstation, but it no longer enables the Ethernet interface.
Step 7 Enter y to allow the Ethernet interface to be used. The FDDI interface prompt appears:
Step 8 Enter the number of FDDI interfaces installed on this workstation. The FDDI interface host name prompt appears:
Step 9 Enter the new name of this workstation or use the default name assigned (the existing name with the -fddi modification). The IP address prompt appears:
Step 10 Enter the IP address for this workstation or use the default address. The existing kernel prompt appears:
Step 11 Enter the name of the kernel being used. A prompt appears asking for a new name for the kernel to be built:
Step 12 Enter the new name for the kernel.
The following installation confirmation screen appears:
Step 13 Power down the system and install the FDDI SBus adapter, or if the adapter is already installed, reboot the system and log back in to read the modified kernel file. Refer to the chapter "Installing the SBus Adapter Hardware."
The installation of the linkable driver creates /etc/hostname.fddix files so that the rc.boot script brings up each interface when the system boots.
Software running on a Solaris 2.x system is installed in packages using the pkgadd command. Refer to the pkgadd(1m), pkgrm(1m), and pkginfo(1m) man pages for more information.
Following is an overview of this section on how to install software packages on your Solaris 2.x system:
Your Solaris driver floppy disk contains the following packages:
Perform the following steps to load the new software on to your local SPARCstation or SPARCserver running Solaris 2.x :
Step 1 Log in to your system as root and insert the Solaris driver floppy disk into the disk drive.
Step 2 If your Sun Volume Manager is disabled, enter the following commands (see the note below if your Sun Volume Manager is enabled) :
mount -r /dev/diskette /mnt
pkgadd -d /mnt
Step 3 Proceed to the section "Installing the Solaris 2.x Driver Using the pkgadd Script."
Perform the following steps to load the new software on your local SPARCstation or SPARCserver running Solaris 2.x from a remote workstation:
Step 1 Insert the Solaris driver disk into the disk drive on a remote Sun workstation on your network.
Step 2 If you are running Solaris 2.x on the remote workstation with the disk drive and the workstation is configured as a Network File System (NFS) server, enter the following commands:
mount -r /dev/diskette /mnt
share -F nfs /mnt
sh /etc/init.d/nfs.server start
Step 3 On the workstation where you are installing the driver, enter the following commands:
mount hostname:/mnt /mnt
pkgadd -d /mnt
where hostname is the host name of the remote workstation with the floppy disk drive and diskette.
Step 4 Proceed to the section "Installing the Solaris 2.x Driver Using the pkgadd Script."
You can load the Solaris driver on a SPARCstation or SPARCserver running Solaris 2.x if you cannot mount a remote floppy drive over the NFS network. You need another workstation with a floppy drive and a tape drive to perform the floppy-to-tape duplication.
Transfer the Solaris driver software to media (for example, 4-mm, 8-mm, or QIC cartridge tape) that is compatible with the workstation that requires the SBus driver by performing the following steps:
Step 1 Locate a workstation with a floppy drive and a tape device and insert the Solaris driver diskette.
Step 2 If you are running Solaris 2.x, enter the following command:
mount -r /dev/diskette /mnt
If you are running SunOS 4.1.x enter the following command:
mount -r /dev/fd0 /mnt
Step 3 Enter the following command to transfer the files from the diskette to the tape:
tar cvf tapedevice /mnt
The following steps are performed at the workstation requiring the SBus driver.
Step 4 Create a /usr/local/fddi directory.
Step 5 Change the directory name to /usr/local/fddi
Step 6 Copy the files from the tape to the /usr/local/fddi directory:
tar xvf tapedeviceStep 7 Enter the following command to execute the pkgadd command:
pkgadd -d /usr/local/fddi
Step 8 Proceed to the following section, "Installing the Solaris 2.x Driver Using the pkgadd Script."
This script asks various questions about the kind of installation you want to perform, and about your system. Specifically, it asks for the following information:
Perform the following tasks to use the Solaris pkgadd script:
Step 1 Select the method described in one of the preceding sections:
After information is displayed about the packages that are available, the prompt to select package(s) to process appears:
Step 2 Enter the number(s) corresponding to the package(s) you want to install. If you choose the default, the following information appears:
Step 3 Enter n for a non-diskless station. Is the FDDI Adapter currently installed in the machine [y] [y,n,?,q]
Step 4 When the FDDI adapter prompt appears, enter y if the adapter is installed. The Ethernet interface prompt appears:
Normally, the Ethernet interface is enabled each time the workstation is booted. If the new CDDI/FDDI interface will be the only network interface on the system, you can stop the Ethernet interface from being enabled at boot time. The installation procedure renames the /etc/hostname.le0 file to /etc/hostname.xx0.
The system still uses the name in this file as the host name for the workstation, but it no longer enables the Ethernet interface.
Step 5 Enter y to allow the Ethernet interface to be used. The FDDI interface prompt appears:
Step 6 Enter the number of SBus adapters installed on this workstation. The IP address prompt appears:
Step 7 Enter y. The FDDI interface host name prompt appears:
Step 8 Enter the new host name of this workstation or use the default name assigned (the existing name with the -fddi modification). The IP address prompt appears:
Step 9 Use the default IP address for this workstation. The following information appears:
Step 10 When the installation confirmation prompt appears, enter y if you want to continue with the installation. The following information appears indicating that the installation was successful:
Step 11 Power down the system and install the SBus adapter or, if the adapter is already installed, reboot the system and log back in to read the modified kernel. Refer to the chapter "Installing the SBus Adapter Hardware."
When you install an FDDI SBus adapter in a system with an existing Ethernet interface, it automatically becomes a router serving both the FDDI and Ethernet networks. The router is known to the Ethernet network by its Ethernet IP address and host name, and to the FDDI network by its FDDI IP address and host name.
Stations on an internetwork can be reached via multiple routes. When a standard SunOS system is booted, the route daemon (routed) sends out packets over both the Ethernet and the FDDI networks. The route daemon determines the optimal route between stations by relative hop count, not by the speed of the interface. Therefore, in cases where the hop counts are equal, the use of FDDI is not guaranteed. You can guarantee the use of FDDI for network commands by specifying the FDDI host name or IP address of the destination machine.
In Figure 3-1, two commands will each resolve the same physical file on the workstation called Aria.
If a user on Fredo mounts files on Delbert, then NFS traffic goes over the Ethernet to either Samson or Aria and from there over an FDDI network to Delbert. However, if a user on Samson mounts files on Aria, the NFS traffic can go over either the FDDI or Ethernet.
The user can specify which interface to use by including Aria's FDDI or Ethernet host name in the mount command, as follows:
fredo@samson => mount aria:/usr/etc/install
/usr/etc/install
fredo@samson => mount aria-FDDI:/usr/etc/install
/usr/etc/install
Both these commands mount to the same physical files on Aria. However, the first results in NFS traffic being routed over the Ethernet networks, while the second results in NFS traffic being routed over the FDDI network.
|
|