The document will ask a series of questions that will help you determine the boot configuration that best suits your network and system configuration. The document is comprised of modules that contain specific configuration steps. The modules have been arranged from general to specific configuration issues. Since this document contains modules for four different configurations, you will not use all of the modules presented in this document.
If you are unsure of which boot configuration to use, the default configuration is marked with a double asterisk, (**). If you already have a specific boot configuration in mind, it may be more efficient to use other documents that have been specifically written for that boot configuration. Specific boot configuration documents available are:
The 7318 was originally designed to boot and operate locally to a RS/6000 (i.e. the RS/6000 and 7318 are on the same LAN). Frequently the 7318's functionality is needed in a remote network (i.e. the RS/6000 and 7318 are on separate networks, linked by a gateway or router). The 7318 is capable of booting while remote from the RS/6000, but special care needs to be taken for the communication channel. REMOTE BOOTING tips will be listed throughout this document when a remote configuration is different from the normal configuration.
The 7318 model S20 can load from a non-AIX computer using TCP/IP. This document does not cover this boot configuration. Please call an AIX Technical Specialist for configuring a 7318 S20 to load from a non-AIX host.
Before using this document, it is assumed that:
AIX Connections use an IPX protocol stack (indicating IPXd) that is slightly different than the IPX (indicating IPX) software that is used for NetWare and the 7318 Terminal Server. Both IPX software (IPX and IPXd) CANNOT be active on a host at the same time. To configure IPX for NetWare or the 7318, verify that AIX CONNECTIONS are not active on the host at the same time.
NOTE: Other hosts running AIX CONNECTIONS can reside on the same physical network without any incompatibility problems.
ps -ef | grep nw
Sample output is as follows:
root 11676 1 0 Oct 11 - 0:00 /usr/tn/nw/NWfile root 23948 1 0 Oct 11 - 0:00 /usr/tn/nw/NWbinderyd root 33958 1 0 Oct 11 - 0:00 /usr/tn/nw/NWprint user 34264 47824 2 16:30:01 pts/22 0:00 grep nw root 43820 11676 0 Oct 11 - 0:00 /usr/tn/nw/NWfile root 46740 1 0 Oct 11 - 0:00 /usr/tn/nw/NWlockd root 48002 1 0 Oct 11 pts/0 0:15 /usr/tn/nw/IPXd root 48558 1 0 Oct 11 - 0:00 /usr/tn/nw/NWdiagd
If any AIX CONNECTIONS processes are active, you cannot configure an IPX network for NetWare or the 7318 on this host.
If AIX CONNECTIONS are NOT active, please continue with the next section, "Checking The Interface."
The host communicates with the network through an interface (tr0, en0, et0, fi0). To configure an interface for IPX, the interface must be active (the words <UP, RUNNING> appear in the flags when the ifconfig command is run).
NOTE:
ent0 Available 00-02 Ethernet High-Performance LAN Adapter (8ef5) fddi0 Available 00-03 FDDI Primary Card, Single Ring Fiber tok0 Available 00-04 Token-Ring High-Performance Adapter (8fc8)
For a Standard Ethernet Interface configured on ent0, execute:
ifconfig en0
Sample output is as follows:
en0: flags=8080863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> inet 9.3.6.32 netmask 0xffffffc0 broadcast 9.3.6.63
For a Standard Token Ring Interface on tok0, execute:
ifconfig tr0
Sample output is as follows:
tr0: flags=80a0043<UP,BROADCAST,RUNNING,ALLCAST,MULTICAST> inet 9.3.6.68 netmask 0xffffffc0 broadcast 9.3.6.127
If the interface is active (the words <UP, RUNNING> appear in the flags list), then continue to the next section. If the words <UP, RUNNING> do not appear in the flags list, then configure the interface through SMIT, execute:
smit inet
The 7318 model P10 and S20 can use either the SPX/IPX or TCP/IP protocol to boot. For the SPX/IPX boot configuration, continue to "Check the IPX and cnsview Daemons." For the TCP/IP boot configuration, continue to, "Check the tftp Daemon" section.
The Terminal Server depends on many daemons for operation. The sapd and npsd daemons (Novell Protocol Suite) manage the IPX channel for communication and the cnsview daemon manages all Terminal Server devices and processes on the host. All three daemons must be active for a successful IPX boot and normal Terminal Server operation.
ps -ef | grep npsd
Sample output when active is as follows:
root 5150 1 0 06:45:54 - 0:00 ./npsd root 16170 15336 2 15:47:33 pts/1 0:00 grep npsd
ps -ef | grep sapd
Sample output when active is as follows:
root 5404 1 0 06:45:52 - 0:09 ./sapd root 16178 15336 5 15:47:39 pts/1 0:00 grep sapd
ps -ef | grep cnsview
Sample output when active is as follows:
root 3370 1 0 06:46:03 - 0:03 /usr/bin/cnsview -c daemon start root 18978 15336 6 15:47:25 pts/1 0:00 grep cnsview
If the cnsview daemon was active but the sapd and/or npsd daemons are not active, stop the cnsview daemon and restart all three daemons using the sequence in the step below.
To stop the cnsview daemon, execute:
cnsview -c "daemon stop"
If all three processes were NOT listed in the output from the above ps commands, then continue with the steps below, to start the daemons.
/usr/lpp/netware/bin/startnps
cnsview -c "daemon start"
NOTE: The cnsview daemon cannot be active until both the sapd and npsd daemons are active. If you are stopping daemons and yet they are still listed as an active system process, execute a kill -1 on the process id and restart all three daemons starting with step 4 above. If still unsuccessful, please contact an IBM AIX Technical Specialist.
The host's IPX routing table can be viewed by executing the following program:
/usr/lpp/netware/bin/drouter
If the IPX network is configured properly, it will be listed in the IPX routing table.
All remote IPX networks will appear in the hosts IPX routing table if there is an active IPX communication channel between the two IPX networks (i.e. a router or gateway is configured for IPX and passes IPX packets).
/usr/lpp/netware/bin/drouter
Sample output is as follows:
NETWORK HOPS TIME NODE NETWORK HOPS TIME NODE -------- ---- ---- ------------ -------- ---- ---- ------ 00000001 0000 0001 000000000001 00000002 0000 0001 02608C2F7119 00000003 0000 0001 02608C2F1591 00000004 0001 0002 00406E0002F5 00000005 0001 0002 00406E0002DB
NETWORK is the network number, internal or external. There should be one entry in this table for each network segment in the overall network.
HOPS is the number of routers which must be passed through to get to this network.
NODE is the Ethernet address of the station used to get to the network.
If the IPX network on which the 7318 resides is shown in the host's IPX network table, continue to the next section.
If an IPX network is not shown and must be configured, refer to documentation on configuring IPX networks or call an IBM AIX Technical Specialist.
To boot the 7318 using the SPX/IPX broadcast configuration, the 7318's device and network definitions must be added to the ODM using SMIT.
smitty ts7318_cs_add_hdr
New ComNetServer Number
The New ComNetServer Number is the number of the 7318 you are adding. The first 7318 is typically 01, then 02, 03, 04 . . . NN as more are added.
Autogenerated TTY Devices
With the arrow key, move down to the Autogenerated TTY Devices field. Press the Tab key until the selection reads "none". Many times it is more convenient to add the ttys later. However, if all 16 serial ports on the 7318 will be used as ttys, it is easier to auto-generate the tty's now.
Interface Type
Select the desired interface type for the ttys. The default type is RS-232.
ComNetServer Network Address
The ComNetServer Network Address is the IPX network on which the 7318 resides. The Network Address must match an IPX network address listed in the host's IPX network table.
NOTE: When the 7318 is local to the host (on the same physical LAN), the IPX network address is listed as the lan_X_network number in the /etc/netware/NPSConfig file. If the 7318 is remote from the host (on a different LAN), an IPX communication channel must be active between the two IPX networks. Execute the following command:
/usr/lpp/netware/bin/drouter
to see if the IPX communication channel is active between the RS/6000 and the remote IPX network. The IPX network on which the 7318 resides should be listed.
ComNetServer Ethernet Address
The ComNetServer Ethernet Address [00406eXXXXXX] is the hardware address of the 7318, where XXXXXX refers to the last six digits of the 7318's hardware address. This address can be found on the white label on the back of the 7318.
ComNetServer Bootfile
The ComNetServer Bootfile is the boot image sent to the 7318. For P10's, the default image is /usr/lib/cns/cns-p10 and for S20's, it is /usr/lib/cns/cns-s20 or /usr/lib/cns/cns-s20e depending on the version of the software you are using. A sample entry looks similar to the following:
New ComNetServer Number [01] Autogenerated TTY Devices none Interface Type RS-232 ComNetServer Network Address [00000300] ComNetServer Ethernet Address [00406ee00155] ComNetServer Bootfile [/usr/lib/cns/cns-p10]
tftp is the daemon that services file requests from the 7318 using UDP/IP. This service must be active on the host to send the load image and configuration file to the 7318.
lssrc -ls inetd | grep tftp
Sample output is as follows:
tftp /usr/sbin/tftpd tftpd -n active
If the process is active, proceed to the next section. If the process is inactive or is not listed, continue to start the process.
tftp dgram udp wait nobody /usr/sbin/tftpd tftpd -n
tftp 69/udp
refresh -s inetd
NOTE: For AIX 3.2.5 systems, first run the command inetimp.
tftp must have permission to access the directories in which the boot image and configuration file reside. The /etc/tftpaccess.ctl file contains the directories tftp is allowed to access. If /etc/tftpaccess.ctl does not exist, then tftp can access any directory.
NOTE: If the /etc/tftpaccess.ctl file does not exist, either create the file (and allow tftp access to the directories in which the files reside) or continue to "Choosing the Boot Method for the 7318" section. If the /etc/tftpaccess.ctl file does not exist, then tftp is allowed access to all directories.
The following is a sample /etc/tftpaccess.ctl file entry with tftp allowed access to the /usr/lib/cns directory.
##########################################################
# The following example, when uncommented, only #
# allows access to the Diskless Client boot files. #
##########################################################
allow:/tftpboot allow:/usr/lib/cns
ls -l | more
Correct sample file permissions are as follows:
-r--r--r-- 1 root system 442532 Jul 24 01:56 cns-p10 -r--r--r-- 1 root system 1240228 Jul 24 01:56 cns-s20e -rw-r--r-- 1 root system 17539 Sep 09 1995 p10.cfg -rw-r--r-- 1 root system 43120 Jul 24 01:56 s20.cfg
chmod 444
The 7318 model P10 and S20 can use two different boot methods with either TCP/IP or SPX/IPX, that is a directed load or a broadcast load.
With a broadcast load configuration, the 7318 broadcasts a boot request to every host on the network. Hosts that are configured to send the 7318 a load image and configuration file reply to the broadcast.
To configure the 7318 to boot using a broadcast load configuration, proceed to "Boot the 7318 Using a Broadcast Configuration," section.
A directed load involves more configuration than a broadcast load but ensures the 7318 queries only one host for its load image and configuration file. Configuring the 7318 to boot using the directed load method requires saving load parameters in the 7318's NVRAM (Non-Volatile RAM).
The NVRAM can be edited through a BIOS Console session.
NOTE: Since boot parameters are specified in the NVRAM, the 7318 boots faster (compared to a broadcast configuration) because it does not have to search for the correct boot settings.
To configure the 7318 to boot using a directed load configuration, proceed to "Boot the 7318 Using a Directed Load Configuration," section.
To configure the 7318 to boot using the IPX protocol for a broadcast load, continue to "Boot the 7318," section.
To boot using a TCP/IP broadcast configuration, the router or gateway connecting the two LANs must be able to pass BOOTP broadcast packets. If the router cannot pass these broadcast packets, then use the TCP/IP directed load configuration instead.
To configure the 7318 to boot using the TCP/IP protocol for a broadcast load, continue to section 11, 7318 Entry in the /etc/bootptab File.
To boot the P10 or S20 using a TCP/IP Broadcast Load, the 7318 must be added to the /etc/bootptab file. The /etc/bootptab file lists the devices on the network to which the bootp server should reply. A bootp server listens for boot requests from the devices listed in the /etc/bootptab file and then begins boot services.
NOTE: Device parameters are listed at the beginning of the file. All entries must be on one line (lines may wrap to the next line), with no spaces, and separated by a colon. The entry must end with a colon.
Sample entry looks like the following:
cns01.ibm.com:ht=ethernet:bf=/usr/lib/cns/cns-s20:ha=00406 e000999:ip=1.1.1.2:
NOTE: The "ht=ethernet" is mandatory and indicates the format of the hardware address, which will always be Ethernet. This can be an issue for those who are booting across a bridge to token ring.
Bootp is the daemon that listens for the 7318's file requests and replies with its IP address and the name of its boot file. To boot the 7318 using a broadcast configuration, bootp must be active.
lssrc -ls inetd | grep bootps
Sample Output looks like the following:
bootps /usr/sbin/bootpd bootpd /etc/bootptab active
If bootp is active, continue to "Boot the 7318" section. If the process is inactive or is not listed, continue to start the process.
An uncommented, sample entry from the /etc/inetd.conf file looks like the following:
bootps dgram udp wait root /usr/sbin/bootpd bootpd /etc/bootptab
An uncommented, sample entry from the /etc/services looks like the following:
bootps 67/udp # bootp server port
refresh -s inetd
NOTE: For AIX 3.2.5 systems, first run the command inetimp.
Configure the 7318 model P10 or S20 to request its boot files from a specific host. These boot parameters are saved in the 7318's NVRAM (Non-Volatile RAM), which can be modified through a BIOS Console session. A BIOS Console session can be accessed by connecting a terminal (IBM3151) to one of the ports on the front of the 7318 with a RJ-45 cable and a null-modem adapter.
9600 baud 8 data bits no parity 1 stop bit
NOTE: You can access a BIOS Console between the time the 7318 is first powered on and the ready light (second light) starts blinking. If the ready light begins blinking, you have missed the window to enter the BIOS Console and must recycle the power and try again. Once four # signs scroll across the screen, the 7318 will begin a BIOS Console session.
admin
show
Specify the loadimage. Set the loadimage for the 7318. Default loadimages (in the /usr/lib/cns directory) are as follows:
Sample command to set the loadimage for a P10 is as follows:
set loadimage /usr/lib/cns/cns-p10
Specify the configuration file. Set the configuration file for the 7318. Sample command to set the configuration file for 00406ef000f0 is as follows:
set config /usr/lib/cns/00406ef000f0.cfg
NOTE: If the 7318's configuration file has not been created, copy the 7318's default configuration file and name it 00406eXXXXXX.cfg (where XXXXXX refers to the last six digits of the 7318's hardware address). The default configuration files (in the /usr/lib/cns directory) are s20.cfg and p10.cfg. You can use the default configuration to boot the 7318 but DO NOT MODIFY THE DEFAULT CONFIGURATION FILE.
Specify the Load Interface. Use the set command to specify the load interface. The 7318 can be forced to use either the AUI or 10BaseT Ethernet interface instead of searching for the attached interface. If unsure, leave the default value.
Sample command to set the load interface is as follows:
set interface 1
NOTE: This may be needed if the HA feature is being used and the system to load from is on the AUI port (the 10BaseT is checked first). Otherwise, leave the default value.
Specify the Frametype. Use the set command to specify the packet type. The 7318 can be forced to use a packet type by setting the frametype parameter. If unsure, leave the default value.
Sample command to set the frametype is as follows:
set frametype 1
NOTE: This feature is most useful for speeding up the boot process. If the frametype is specified, the 7318 will not search for the frametype needed.
Specify the Protocol. Use the set command to specify the protocol. The 7318 can be forced to use either IPX (1) or UDP (2) to load. If unsure, leave the default value.
Sample command to set the protocol is as follows:
set protocol 1
NOTE: Since IPX is tried first, specifying this parameter speeds up the boot process for a 7318 using TCP/IP (UDP). No time will be wasted looking for an IPX boot host when one doesn't exist.
To force the 7318 to download files from a specific SPX/IPX host:
Sample command to set an IPX load host (hosts internal_network number is 8ae46c31):
set host1 8ae46c31:000000000001
Since the 7318 is using TCP/IP, the 7318 must have an IP address.
Sample command to set the IP address (7318s IP address is 9.3.6.7):
set inet 9.3.6.7
Sample command to set a TCP/IP load host (hosts IP address is 9.3.6.42):
set host1 9.3.6.42
NOTE: If you have a name server or a non-standard netmask, configure them with the set command as well (as shown above for other NVRAM boot parameters). If you enter a name server IP address and DNS domain, you can enter a hostname for the host1 parameter instead of an IP address.
Sample command to set a TCP/IP gateway (gateway IP address is 9.3.6.2):
set gateway 9.3.6.2
save
Now that we have made the necessary configuration changes, boot the 7318. The 7318 can be rebooted in two ways. Choose the most convenient method from the following.
After approximately 20 seconds, the light sequence on the front of the 7318 should be either 1110 or 1101. If the sequence is (1 Flash 1 0) or (1 Flash 0 1), verify the boot configuration methods used above. If booting the 7318 is unsuccessful, please contact an IBM AIX Technical Specialist.