Configuring ATM interface on SGI

First of all make sure you have IP addresses for the host you are configuring. Sixteen 'subnets' have been assigned to Classical IP, from 128.63.240.x through 128.63.255.x, so that a total of 4096 IP addresses are available for assignment to the Classical IP ATM network, within ARL's 128.63 Class B IPv4 address. This should provide sufficient address space to allow all ARL hosts to exist on a single ATM-based IP network.

For backwards compatability, hosts in the existing SPANS subnet of 128.63.155.zzz will also be given addresses in the first block of 128.63.240, e.g. their qaa0 IP address will be 128.63.240.zzz. However, to provide some administrative organization to the number space, new hosts will be registered in the 15 other chunks of the address space. It has not yet been determined whether the organization will be by physical location (e.g. building number or group of buildings), by directorate, or what. Ask Tom Kile for the current thinking.

SPANS addresses have been in the 128.63.155 subnet.

Make sure you are installing a release compatible with the switch to which you are connected. You can telnet to the switch and the login banner will print out the version of software running on the switch. The major revision numbers should match.

Tom Kendall has been maintaining local copies of install kits:
Acquire the latest version for your system that matches the switch.
Run ``su -'' to become root.
Don't just ``su'', or later on the kernel autoconf will fail.
Run the installation script from the install kit:
The script asks several questions:
Would you like to use FORE's SNMP agent? [y] y
You must answer ``yes'' here, as the alternative (running ilmid) doesn't actually work. The ilmid will die shortly after being started.
Will you be using ILMI for Address Registration? [y] y
Would you like to use ILMI for UNI auto-configuration? [y] y
This allows the host to auto-configure for uni3.0 or uni3.1, whichever is enabled and running on the switch.  A good idea as not all switches have 3.1 enabled
Would you like to configure Classical IP? [n] y
Would you like to configure qaa0? [y] y
Enter the ATM address for the ARP server on qaa0
47000580ffe1000000f21c095f0020481c095f00 (old address)
Would you like to configure qaa1? [y] n
Would you like to configure qab0? [y] n
Would you like to configure qac0? [y] n
Would you like to configure qad0? [y] n
Would you like to configure qae0? [y] n
Would you like to configure qaf0? [y] n
Would you like to configure LAN Emulation? [n] n
Ready to configure kernel ? [y] y
Working (this may take a few minutes)...
Kernel build successful. The new kernel is /unix.install
Please move the original kernel, /unix, to /unix.orig and then
Reboot your machine to begin running the new kernel.
Automatic installation has completed.
Move the kernel into place.
cd /
mv unix unix.orig
mv unix.install unix
Add the interfaces to the system configuration file:
Edit /etc/config/netif.options to add the interface(s). For a single ATM card, add both SPANS and UNI interfaces:
IMPORTANT NOTE: If you are configuring the ATM interface as the primary network interface, (if1 and if2 instead of if2 and if3) the SPANS interface (fa0) should be listed first, because the MBONE tools (like "sdr") die if the first interface isn't multicast-capable.
Create options files:
for the previous example of interfaces if2 and if3:
netmask -trailers up
netmask -trailers up
Fix the clip startup file
edit /etc/init.d/clip and remove the ``-n'' option from the snmpd startup line:
/usr/etc/fore/etc/snmpd -c /usr/etc/fore/etc/cdb.conf -n -p 161
should be:
/usr/etc/fore/etc/snmpd -c /usr/etc/fore/etc/cdb.conf -p 161
This causes the snmpd to perform the ilmi functions, in addition to snmp service.
Configure routes
If you are configuring the atm interface as your default route, know that the Fore SGI ATM software does not presently allow setting a broadcast address on the Classical IP interface, which means that there is no way to get RIP routing updates, which means that unless you add a static route to the Cisco router, no traffic will use qaa0.
The easiest way to establish the default route is to create /etc/rc2.d/S91static_routes such that it contains:

/usr/etc/route add default 1
/usr/etc/route add net 128.63.2 1 -mtu 4352
There is no need to run routed, although doing so (with the "-q" flag) is not harmful. routed will only pick up on routes being conveyed over broadcast on the SPANS interface.

As an alternative method for establishing the default route, edit /etc/init.d/network to read:

	if test $netstate = "ok" ; then

            # Start either gated (the fancy routing daemon) or routed.
            # Note: gated and mrouted use configuration files in /usr/etc.
            # See gated(1M) and mrouted(1M) for details on their setup.

            if $IS_ON gated && test -x /usr/etc/gated ; then

                /usr/etc/gated `cat $CONFIG/gated.options 2> /dev/null` &
                                                        $ECHO " gated\c"
|           elif $IS_ON routed && test -x /usr/etc/routed ; then

                # Useful option:
                #       -q = "quiet": don't act as router if > 1 interface.
                # See routed(1M) for other options.

                /usr/etc/routed `cat $CONFIG/routed.options 2> /dev/null` &
                                                        $ECHO " routed\c"
|           else
|               /usr/etc/route add net 0 2 &
|                                       $ECHO " default_route=gw328-2\c"
Or you can establish an /etc/rc2.d/S31network.local file. See Chuck for details.
Reboot the system.
Ping the SPANS and UNI interfaces of a remote host to verify that they work.
From a remote host, ping both the SPANS and UNI interfaces of the host you just configured.