7318 IPX Directed Boot Configuration

Contents

The purpose of this document is to assist with configuring an IBM 7318 model P10 or model S20 to boot using an IPX directed load configuration. This document was designed for AIX System Administrators with a knowledge of AIX administration and the 7318. Using this document, an IPX directed boot configuration takes about 25 minutes. The document applies to AIX versions 3.2.5 through 4.x.

In a directed load configuration, the 7318 requests its load image and configuration file from a specific host on the network. 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.

Remote Booting

Assumptions

• The RS/6000's communications interface is UP and RUNNING
• The SPX/IPX software is installed for IPX Configuration
• An IPX network has been configured and is active for IPX boots
• The 7318 is cabled correctly to the Ethernet Network
• A terminal can be connected to the 7318 for BIOS Console Configuration
• The 7318's configuration file has been specified or created

Terms Used in this Document:

• host - the computer (RS/6000)
• environment - computer network

Requirements

To use this document effectively, you must:

• Know the 7318 model type: P10 or S20
• Verify that the load images exist (either: /usr/lib/cns/cns-p10, cns-s20 or cns-s20e)
• Know the address of the IPX network on which the 7318 resides
• Know the hardware number (Ethernet address) of the 7318 being configured
• Know the internal IPX number of the load host

AIX Connections use an IPX protocol stack (indicating IPXd) that is slightly different than the IPX software (indicating IPX) 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.

1. Check if AIX CONNECTIONS are active, execute:

    
      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 
   

2. Verify that AIX CONNECTIONS are inactive (AIX Connections are inactive if none of the processes listed above are running).

   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:

• A communication INTERFACE is configured on a communication ADAPTER (i.e. the tr0 interface is configured on the tok0 adapter card, the en0 (or et0) interfaces are configured on the ent0 adapter card).
• A communication adapter can have multiple interfaces. IPX networks can be configured on the following adapters.

   
     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) 
  

Verify that the communications interface is active using the ifconfig command and the adapter name.

• 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 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.

1. Verify if the IPX npsd daemon is active, execute:

    
      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 
   

2. Verify if the IPX sapd daemon is active, execute:

    
      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 
   

3. Verify if the cnsview daemon is active, execute:

    
      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 
   

4. If all three processes were listed in the output from the above ps commands, then please continue to the section "Verify the IPX Network".

   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.

5. To start the sapd and npsd daemons, execute:

    
   /usr/lpp/netware/bin/startnps 
   

6. To start the cnsview daemon, execute:

    
      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 this is still unsuccessful, please contact an IBM AIX Technical Specialist.

7. Once these daemons are active, continue to the next section, "Verify the IPX Network."

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.

Remote Configurations

All remote IPX networks will appear in the host's 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).

1. To view the host's IPX routing table, execute:

    
      /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.

2. Verify that the IPX network is shown in the listing.

   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.

1. Start SMIT and use the fastpath ts7318_cs_add_hdr, execute:

    
      smitty ts7318_cs_add_hdr 
   

2. Enter the configuration information in the following fields:

   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 autogenerate the ttys 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 P10s, the default image is /usr/lib/cns/cns-p10 and for S20s, 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] 
   

3. After finishing the configuration, press Enter to add the device definition. Continue to the next section.

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 an RJ-45 cable and a null-modem adapter.

1. Verify the terminal connectivity and configuration. The terminal should be connected to any one of the 16 ports on the front of the 7318. The terminal should emulate an ASCII terminal with the following settings:

    
      9600 baud       8 data bits     no parity       1 stop bit 
   

2. To start a BIOS Console session, recycle the power on the 7318 by unplugging and replugging the power cord. When the 7318 is powered back on, hold the Shift key and press 3 (the # sign) repeatedly until four # signs scroll across the screen of the terminal.

   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.

3. To make changes to the NVRAM, change to the administrative user, execute:

    
      admin 
   

4. Display the current contents of the NVRAM, execute:

    
      show 
   

5. Specify the boot parameters using the set command.
   1. Specify the loadimage. Set the loadimage for the 7318. Default loadimages (in the /usr/lib/cns directory) are as follows:
      • cns-p10
      • cns-s20
      • cns-s20e

      Sample command to set the loadimage for a P10 is as follows:

       
         set loadimage /usr/lib/cns/cns-p10 
      

   2. 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.

   3. 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

      • 0 - auto (default)
      • 1 - 10BaseT Interface
      • 2 - AUI Interface

      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.

   4. 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

      • 0 - auto (default)
      • 1 - Ethernet Version 2
      • 2 - Ethernet SNAP
      • 3 - Ethernet 802.3
      • 4 - Ethernet 802.2

      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.

   5. 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

      • 0 - auto (default)
      • 1 - IPX, 2 - TCP/IP)

      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.

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.

1. Recycle the 7318's power by unplugging and replugging the power cord.
2. Execute the load command from the BIOS Console session on the 7318.

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.