                  ****************************************
                  * Checklist to get the network working *
                  *      (assuming ethernet on ec0)      *
                  ****************************************

OVERVIEW:
=========

Proceed through directions and restart the network to check it
after each step.

Commands you should type at the shell begin "# ".  The "# " 
represents the root prompt.

To restart the network without rebooting, execute the following 
commands:

   # /etc/init.d/network stop
   # /etc/init.d/network start

If this is the first time the network is set up on this machine, do the
first six steps before trying anything else.


TROUBLESHOOTING:
================

  Symptom                                        Start at step
  -------                                        -------------
  Nothing works, no error messages               1
  Local machines are reachable, but remote
        machines are not                         8
  No apparent reason for the network to fail     9
  YP (NIS) doesn't work                          7
  Any other problem                              1
  

STEPS:
======
1 - Check to see that the ethernet cable is plugged in.
2 - # chkconfig
    network should be on
    yp may be on, off, or not there at all
    ypmaster and ypserv should be off unless the machine is a yp server
    If any options are incorrect, set them correctly.  For example:
    # chkconfig network on
3 - # cat /etc/sys_id
    It should display the system's name, spelled correctly.
4 - Set your hostname with the "hostname" command to fix environment
    variables and the likes.
    # hostname <hostname>
5 - # more /etc/hosts
    It should list all of the relevant local machines (at least a server)
    and their IP addresses.
    Check spelling and numbers!
6 - # nvram netaddr
    It should show your IP address.  If not, type:
    # nvram netaddr <IP address>
    # reboot
7 - If running yp (NIS),
    # cat /usr/etc/yp/ypdomain
    It should show the domain for yp (NIS)
8 - # cat /usr/etc/resolv.conf
    It should show something like this:

      domain  huntsville.sgi.com
      hostresorder yp local bind
      nameserver      192.48.152.2
      nameserver      192.26.51.194
      nameserver      192.26.51.11

    See the man page on resolv.conf for details.  Do NOT copy this data
    unless you're working on a machine in the Huntsville SGI office.  It's
    an example only.
9 - # ifconfig ec0
    This checks the ethernet card to get all manner of information.  It should
    look something like this:

      ec0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,FILTMULTI,MULTICAST>
              inet 192.102.114.65 netmask 0xffffff00 broadcast 192.102.114.255

    Inet should be followed by your machine's IP address.  Netmask should almost
    always be 0xffffff00.  Broadcast should be <IP domain>.255 under most 
    circumstances.
    If these numbers are wrong, edit the /etc/config/ifconfig-1.options file
    and set it up something like this:

      netmask 255.255.255.0
      broadcast 192.102.114.255

    Your "netmask" line should look the same.  Your "broadcast" line should
    contain the first 3 numbers of your IP address followed by .255.
    For example, if your IP address is 102.122.203.4, the "broadcast" line
    should read "broadcast 102.122.203.255".
    Restart the network and repeat this step.  If the network still doesn't
    work, see the man pages for ifconfig and network.
10- If the network STILL doesn't work, check /etc/config/network, 
    /etc/config/netif.options, and /etc/init.d/network against those on
    a working machine.  (5.2's files are slightly modified from 4.0.5's.)  
    Spot checks should be sufficient to reveal problems on a high level
    (and there's probably a high level problem at this point).
11- Verify that the hardware works by plugging in another system which is known
    to work on the network.  Plug the system in to the SAME place as you have
    the faulty system plugged in.  Try swapping out cables, connectors, and 
    transceivers.
12- Reload the operating system.
13- Try swapping the ethernet board.
14- Try a sledgehammer.


NOTES:
======
   This file is not intended to provide a fix for all network problems.  It
addresses the problems that appear at the Huntsville office most often.

If you have any comments, steps to add to the list, complaints that it's too 
cryptic, or whatever, send them to jims@sgi.com.

Last modification 4/13/94
