7318 IPX Broadcast Boot Configuration


Contents

About this document
Prerequisite information
Checking for conflicting software
Checking the interface
Checking the IPX and cnsview daemons
Verify the IPX network
Adding the 7318 as a device using SMIT
Boot the 7318

About this document

This document discusses how to configure an IBM 7318 model P10 or model S20 to boot using an IPX broadcast load configuration. This document applies to AIX Versions 4.x.

This document was designed for AIX System Administrators with a knowledge of AIX administration and the 7318. Using this document, an IPX broadcast boot configuration takes about 20 minutes.

Remote booting

The 7318 was originally designed to boot and operate locally to an IBM eServer pSeries or RS/6000 (for example, the pSeries or RS/6000 and 7318 are on the same LAN). Frequently the 7318's functionality is needed in a remote network (for example, the pSeries or RS/6000 and 7318 are on separate networks, linked by a gateway or router). The 7318 is capable of booting while remote from the computer, 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.


Prerequisite information

Assumptions

Before using this document, it is assumed that:

Terms used in this document:


Requirements

To use this document effectively, you must:


Checking for conflicting software

You need to check for both AIX Connections and Novell Network Services (NNS).

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.

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

Now check for NNS. This also uses its own IPX stack and cannot be run with 7318s. This can be seen by running the command lslpp -l ipx.base.rte and lslpp -l ncps.*. If nothing is returned, continue with the next section, otherwise 7318s cannot be run on that machine unless the software is deinstalled and the machine rebooted.


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:

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

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 

Checking the IPX and cnsview daemons

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 preceding ps commands, 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 preceding ps commands, 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 you are still encountering difficulties, please contact an IBM AIX Technical Specialist.

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

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 (such as, 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.


Adding the 7318 as a device using SMIT

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 fast path 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 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 pSeries or 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] 
    
  3. After finishing the configuration, press Enter to add the device definition. Continue to the next section.

Boot the 7318

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 re-plugging 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.




[ Doc Ref: 90605192614778     Publish Date: Jan. 03, 2001     4FAX Ref: 7452 ]