3 Installation Integration



This section describes how the software and hardware, which was installed according to the instructions in Chapter 1 and Chapter 2, can be integrated into the system.

The system integration phase has 2 segments.

    1. Complete the installation
    2. Verify the software installation
    3. Set up the network topology.

3.1 Complete the Installation

This section integrates the SNC software and hardware and brings the server on-line. You must have completed all of the steps described in Chapter 1 and Chapter 2 of this manual.

    1. Boot the system with the SNC kernel.

3.2 Verify the Software Installation

This section of the integration process verifies that the SNC software has been properly installed, that the files needed to run the SNC are in the correct locations, and that the kernel has been built and installed properly.

    1. Run the SNC verification script to ensure that all software components are properly installed. The verification script will issue warnings if any programs or files are missing or improperly installed.

3.3 Set Up New Network Topology

This section of the integration process is particularly important if you are modifying the topology of your network. Please refer to Appendix F for a full discussion of this issue.

    1. If you have modified your network topology or changed your server's host name, you will need to edit the /etc/hosts and /etc/bootparams files.

Note - If the local network is using NIS, you must also update the NIS maps.

    2. Edit /etc/hosts to add the new hostnames of your server.
    3. If the server is to be used as a boot server for diskless clients, edit the /etc/bootparams file to use a new host name from which the diskless clients will boot.

    The server host name that should be used by the diskless client for booting is the host name of the server associated with the interface through which the client is connected.

    If NIS is being used on the network, this update can be performed in the NIS server.

    4. Modify the fstab file for each client installed on the new network that has NFS mounts from the server.

    The server name used by each client must be the name associated with the server interface that connects the client to the server. For example:

    5. Modify the files in the server's /tftpboot directory if necessary.

    If a client's network address has changed, the boot file in /tftpboot named by the hexadecimal representation of the client's Internet address must be renamed.

    6. Reboot each client whose fstab file has been modified.

You are finished with the Sun Network CoProcessor installation!

The following sections are appendixes. You only need to consult them under special circumstances; if your installation has been successful, you may ignore them.