1 Software Installation





1.1 Introduction

This section describes how to install the software for the Sun Network CoProcessor (SNC).

It will take about 20 minutes to complete the software installation. Please read through the full procedure before beginning to become familiar with the entire operation.

1.2 Before You Start

The installation process has several requirements that must be fulfilled to permit a successful completion.

1.2.1 Product Compatibility

The 1.2 Sun Network CoProcessor can be installed in the following Sun file servers:

1.2.2 Space Requirements

1.2.3 Software Requirements

1.2.4 Hardware Requirements

1.2.4.1 CPU Board Revision Level

The CPU board of SPARCserver 470 and 490 systems running SNC 1.2 software must be Rev 09 or higher. To find the revision level of these systems, look for the CPU board revision number on the back side of the plastic tab attached to the top extractor handle of the CPU board.

1.2.4.2 IPI Disk Controller Firmware

Here is how to determine if the IPI disk controller firmware is at revision 10 or later:

    1. During the system boot sequence, look for an IPI controller revision date of 2/10/93 or later:

    2. If you miss seeing the IPI controller's firmware revision date message, you can retrieve it for a short time after the boot process finishes by typing:

Upgrade the firmware of all IPI controllers whose firmware predates 2/10/93 (revision 10).

Contact Sun Customer Support if you require an IPI controller firmware upgrade.

1.2.5 Information Requirements

Note - Appendix F, "Multiple Network Configuration Issues,discusses issues that become important when adding new network segments to an existing network. Read Appendix F before installing SNC boards or otherwise changing the topology of your network.

Appendix A, "The SNC Distribution Software" lists files affected by the SNC installation script.

After executing the installation script, your can back out most of the changes with the deinstall_snc script included on the CD-ROM. Appendix A lists the files affected by the deinstall_snc script.

Caution - While you can install the SNC software while the server is running in multi-user mode, any users logged in to or receiving file service from the server may see inconsistencies. Sun recommends that you either perform the installation in single-user mode, or expel all users from the server and make sure no file systems are exported until installation is complete.

Note - It is a good idea to use the script(1) command before beginning the installation. The installation log recorded by script can be useful if you encounter problems during the installation process.

1.3 Overview of the Installation Process

Following is an outline of the steps involved in installing the SNC in a server:

    1. Load SNC driver software from the CD-ROM, and install the SNC software.
    2. Shut down the server and turn off its power.
    3. Install the SNC hardware.
    4. If you have changed the topology of your network by adding, moving, or removing SNC's or other boards in the server and so on, update the network configuration files.
    5. Boot the server SNC kernel and prepare the clients to use the new SNC host names.

1.4 Loading and Installing the SNC Software

1.4.1 Installation Example

The following example is of a typical installation, your input will necessarily be somewhat different.

User input is presented below in boldface

-------------------------------------------------------------------------------
fluffybunnies% su fluffybunnies% prompt: {password} fluffybunnies# fluffybunnies# mkdir /cdrom fluffybunnies# mount -r /dev/sr0 /cdrom fluffybunnies# cd /cdrom fluffybunnies# cdm cdm Initializing Done Current program environment: Application : none Category : all Directory : /cdrom/release_dir ----->> CDM <<<<<----- 1. Select Application 2. Show Current Application 3. Install Application 4. Display Application Text File 5. Print Application Text File 6. List Applications 7. List Categories 8. Change Current Category 9. Change Current Directory 10. Show Program Environment Please enter a number or q to quit:1 Applications available: 1. Sun Network CoProcessor Please enter a number or q for the main menu:1 "Sun Network CoProcessor" selected as new application. ----->> CDM <<<<<----- 1. Select Application 2. Show Current Application 3. Install Application 4. Display Application Text File 5. Print Application Text File 6. List Applications 7. List Categories 8. Change Current Category 9. Change Current Directory 10. Show Program Environment Please enter a number or q to quit: 3 Begin installation now? y Executing installation file ... The following product will be installed: 1.2 Sun Network CoProcessor SPARC(R) FCS Sun-4 SUNBIN CD-ROM (UFS file system format) 1 of 1 Part Number: 704-3039-10 Rev. A Compatible with SunOS(TM) Release 4.1.3 Copyright Interphase Corp. 1990-1993. Copyright 1988-1993, Sun Microsystems, Inc. All Rights Reserved. Based on the SunOS Release. Derived from UNIX and Berkeley 4.3 BSD licensed from AT&T Information Systems Inc. and the Regents of the University of California, respectively. Sun considers its source code as an unpublished, proprietary trade secret, and it is available only under strict license provisions. This copyright notice is placed here only to protect Sun in the event the source is deemed a published work. Disassembly, decompilation, or other means of reducing the object code to human readable form is prohibited by the license agreement under which this code is provided to the user or company in possession of this copy. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 (Oct. 1988) and FAR 52.227-19(c) (June 1987). Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043. Do you want to continue [y|n]? y This is the Sun Network CoProcessor installation script. Software Requirements for SNC 1.2: SunOS 4.1.3 must already be installed on your system. SNC 1.2 is not supported with earlier SunOS versions. The Sys category of SunOS must be installed in order to build custom kernels. Hardware Requirements for SNC 1.2 on the sun4 architecture: Max Supported NC boards SPARCserver 490 (4/490) 6 SPARCserver 470 (4/470) 4 SNC 1.2 consists of utilities, data files, and object files needed to build custom kernels. Continue SNC 1.2 installation? [yn] y Installing SNC 1.2 from cd-rom Installing files in / ... x etc/ne.dwnld, 312840 bytes, 612 tape blocks x etc/reload.ne0, 1178 bytes, 3 tape blocks x etc/reload.ne1, 1178 bytes, 3 tape blocks x etc/reload.ne2, 1178 bytes, 3 tape blocks x etc/reload.ne3, 1178 bytes, 3 tape blocks x etc/reload.ne4, 1178 bytes, 3 tape blocks x etc/reload.ne5, 1178 bytes, 3 tape blocks x sbin/neload, 98304 bytes, 192 tape blocks x sbin/sncnet, 147456 bytes, 288 tape blocks x sys/sun4/OBJ/if.o, 6520 bytes, 13 tape blocks x sys/sun4/OBJ/in.o, 5768 bytes, 12 tape blocks x sys/sun4/OBJ/ne.o, 77936 bytes, 153 tape blocks x sys/sun4/OBJ/nfs_sncsvr.o, 26616 bytes, 52 tape blocks x sys/sun4/OBJ/route.o, 4568 bytes, 9 tape blocks x sys/sun4/OBJ/sncnet_vers.o, 212 bytes, 1 tape blocks x sys/sundev/nereg.h, 29507 bytes, 58 tape blocks x sys/sundev/ne_conf.c, 2564 bytes, 6 tape blocks x sys/nfs/nfsagent.h, 6244 bytes, 13 tape blocks x dev/MAKEDEV.ne, 1257 bytes, 3 tape blocks Installing files in /usr ... x usr/etc/arp, 163840 bytes, 320 tape blocks x usr/etc/necons, 98304 bytes, 192 tape blocks x usr/etc/neload, 98304 bytes, 192 tape blocks x usr/etc/nestat, 106496 bytes, 208 tape blocks x usr/etc/nestop, 98304 bytes, 192 tape blocks x usr/etc/newatch, 106496 bytes, 208 tape blocks x usr/etc/nfsstat, 16384 bytes, 32 tape blocks x usr/etc/snc_nfsd, 16384 bytes, 32 tape blocks x usr/etc/sncnet, 147456 bytes, 288 tape blocks Installing man pages in /usr/man ... x ./man4/Intro.4, 9054 bytes, 18 tape blocks x ./man4/List.4, 6021 bytes, 12 tape blocks x ./man4/ne.4, 3696 bytes, 8 tape blocks x ./man4/nfs.4p, 5150 bytes, 11 tape blocks x ./man8/Intro.8, 6539 bytes, 13 tape blocks x ./man8/List.8, 21080 bytes, 42 tape blocks x ./man8/MAKEDEV.ne.8, 2371 bytes, 5 tape blocks x ./man8/neload.8, 2696 bytes, 6 tape blocks x ./man8/nestat.8, 3989 bytes, 8 tape blocks x ./man8/nestop.8, 2829 bytes, 6 tape blocks x ./man8/newatch.8, 3857 bytes, 8 tape blocks x ./man8/nfsstat.8c, 5968 bytes, 12 tape blocks x ./man8/snc_nfsd.8, 2091 bytes, 5 tape blocks x ./man8/sncnet.8, 8686 bytes, 17 tape blocks Several system files require modification. This can be done automatically now, or you may manually perform the edits later. Would you like the edits to be performed automatically now? [yn] y files.cmn has already been modified for SNC 1.2. /sys/sun/conf.c has already been modified for the SNC 1.2. Skipping the edit. rc.boot has already been modified for SNC 1.2. rc.local has already been modified for SNC 1.2. Current kernel is named "GENERIC_100623-03_SNC". Going to use kernel name "GENERIC_100623-03_SNC". Would you like to change the name [yn]? n New kernel will be named "GENERIC_100623-03_SNC". Editing /sys/sun4/conf/GENERIC_100623-03_SNC Editing /dev/MAKEDEV.ne SNC 1.2 edits were successful and complete. Created special file /dev/ne0 Created special file /dev/ne1 Created special file /dev/ne2 Created special file /dev/ne3 Created special file /dev/ne4 Created special file /dev/ne5 Would you like to update the /etc/hostname.* files now? [yn] y You will now be asked for a host name to be associated with each network interface on the server. If you wish to deactivate a network interface, enter "NONE" for its host name. For example, if you intend to use the "ne0" interface as a replacement for an old "ie0" interface, enter "NONE" as the host name for the ie0 interface and enter the real host name for the ne0 interface. (The word "NONE" should be entered in all upper-case and without the quote marks). The ie0 interface currently has a host name of fluffybunnies. Do you want to change (or deactivate) it? [yn] n The ne0 interface currently has a host name of s1. Do you want to change (or deactivate) it? [yn] n The ne1 interface currently has a host name of s2. Do you want to change (or deactivate) it? [yn] n The ne2 interface currently has a host name of s3. Do you want to change (or deactivate) it? [yn] n The ne3 interface currently has a host name of s4. Do you want to change (or deactivate) it? [yn] n The ne4 interface currently has a host name of s5. Do you want to change (or deactivate) it? [yn] n The ne5 interface currently has a host name of s6. Do you want to change (or deactivate) it? [yn] n Your /etc/hostname.* files are up to date. Don't forget to update the "hosts" and "ethers" NIS maps (or the /etc/hosts and /etc/ethers files) if necessary. Write down the Ethernet interfaces and their corresponding host names now for future reference: Interface Host Name ie0 fluffybunnies ne0 s1 ne1 s2 ne2 s3 ne3 s4 ne4 s5 ne5 s6 Would you like to make a new kernel for your system now? [yn] y We will now make a new kernel for your system, using the config file GENERIC_100623-03_SNC. - Config'ing /sys/sun4/conf/GENERIC_100623-03_SNC <- (cd /sys/sun4/conf; config GENERIC_100623-03_SNC) Doing a "make depend" - Making /sys/sun4/GENERIC_100623-03_SNC kernel <- { compiler output omitted } loading vmunix rearranging symbols text data bss dec hex 1458176 240928 216168 1915272 1d3988 Your new kernel has been successfully loaded. cp /sys/sun4/GENERIC_100623-03_SNC/vmunix /vmunix.GENERIC_100623-03_SNC Your kernel has been installed as /vmunix.GENERIC_100623-03_SNC You will need to symlink it to /vmunix and reboot. I.e., do rm /vmunix # OK because /vmunix is a symbolic link ln -s /vmunix.GENERIC_100623-03_SNC /vmunix /usr/etc/shutdown -fh +5 to install GENERIC_100623-03_SNC kernel Shut off the server. Install the Network CoProcessor hardware [if not already installed]. Connect Ethernet cables to the Network CoProcessors. Restart the server. Kernel configuration complete. Installation of SNC 1.2 files from cd-rom finished. Now please continue with the installation instructions in the Sun Network CoProcessor Installation Manual. ----->> CDM <<<<<----- 1. Select Application 2. Show Current Application 3. Install Application 4. Display Application Text File 5. Print Application Text File 6. List Applications 7. List Categories 8. Change Current Category 9. Change Current Directory 10. Show Program Environment Please enter a number or q to quit:q fluffybunnies# -------------------------------------------------------------------------------

1.4.2 Installation Procedures

To begin the installation:

    1. Perform the installation shown in the example at the beginning of this section.

Note - If you have hard-coded broadcast addresses and/or network masks in the ifconfig lines of your rc.local file, you may need to hand-edit that file to restore these addresses and masks after the install script has finished executing. Most network managers rely on Network Information Service (NIS) to furnish this information.

    2. Move the standard kernel and create a symbolic link to the SNC kernel.
    3. Rename the kernel, preserving it for future use if needed.
    4. Make /vmunix a symbolic link to the new SNC kernel:

    5. If you are not going to use the on-board Ethernet port (ie0 or le0), then you need to specify "none" for both ie0 and le0 when running the installation script, and remove the following files:

    /etc/hostname.ie0
    /etc/hostname.le0
    .

    6. Shutdown the system to install the SNC hardware:

See Chapter 2, "Hardware Installation" for instructions on installing the SNC hardware.