The purpose of this document is to assist with trouble shooting an IPX directed boot for an IBM 7318 model P10 or model S20. This document was designed for AIX System Administrators with a knowledge of AIX administration and the 7318. Using this document, IPX directed boot trouble shooting takes about 25 minutes. In a directed load configuration, the 7318 requests its boot image and configuration file from a specific host. The boot configuration is primarily on the 7318 but the host must have active daemons that will respond to the 7318 file requests. This document contains modules that troubleshoot the directed load configuration on the 7318 and the host.
This document applies to AIX levels 3.2.5 to 4.3.2.
The 7318 was originally designed to boot and operate local to an 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 troubleshooting tips will be listed throughout this document when troubleshooting a remote 7318 varies from troubleshooting one local to the RS/6000.
Before using this document, the following is assumed:
To use this document effectively, you must:
The lights on the front of the 7318 show its status. From left to right, the lights correspond to Power, Ready, AUI interface in use, and 10Base-T interface in use. Different light sequences will be shown during the 7318's power-on and hardware check, booting, and normal operation. For more information on the light sequences, refer to page 2-5 in the 7318 Serial Communications Network Server Guide and Reference (SC23-2542-00).
Legend:
Light Sequence Condition and Resolution, if applicable:
0 0 0 0 The 7318 is not powered ON.The 7318 does not have a power on/off switch. You must use the AC plug to power on and off the 7318.
1 0 0 0 The 7318 has a hardware problem, if this sequence persists for more than 1 minute. In that case, the 7318 needs to be serviced or replaced.
1 B 0 0 The 7318 is trying to boot but cannot communicate with the network. Check all cabling connecting the 7318 to the LAN. Replace cabling if necessary. Continue Troubleshooting once the 7318 is able to transmit onto the LAN.
1 B 1 0 The 7318 is trying to boot and can transmit onto the LAN.
1 B 0 1 The 7318 is trying to boot and can transmit onto the LAN. The 7318 is trying to boot but cannot find a load host. Proceed to the next section to continue troubleshooting.
1 1 1 0 The 7318 is booted and can transmit onto the LAN.
1 1 0 1 The 7318 is booted and can transmit onto the LAN. The 7318 has booted and is operating as designed. If you are unable to communicate with the 7318, the problem is beyond booting and the scope of this document.
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)
Verify that the communications interface is active using the ifconfig command and the adapter name.
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
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.
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 all three processes were listed in the output from the preceding 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 step 4 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 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 you are still encountering difficulties, 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 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).
/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.
If any two IPX hosts on the same inter-network have the same internal network number, the SPX link between the 7318 and the host will be unstable and the 7318 may not boot. Therefore, no two hosts can have the same IPX internal network number.
NOTE: The default internal network number is 00000001 but it can be any eight digit hexadecimal number (it is usually the last eight digits of the host's mac address). The internal network number must also be different from the LAN network numbers in the environment.
Below is a sample internal network number from the /etc/netware/NPSConfig file.
internal_network = "00000001"
If all the internal_network numbers are unique, continue to the next section.
If any internal network numbers are the same, make each host's internal network number unique and continue with step 4.
WARNING: Recycling these daemons will disconnect any device communicating with the host via IPX (includes P10 Style Ports)!
cnsview -c "daemon stop" /usr/lpp/netware/bin/stopnps /usr/lpp/netware/bin/startnps cnsview -c "daemon start"
Verify that the 7318's device information, specified download image, and IPX network address are correct in its SMIT configuration.
smitty ts7318_cs_mnu
[Entry Fields] ComNetServer Number 01 ComNetServer Network Address [00000002] ComNetServer Ethernet Address [00406ee00155] ComNetServer Bootfile [/usr/lib/cns/cns-p10]
It should match an IPX network address listed in the host's IPX routing table. If the network address is incorrect, change it. If the network address is not listed in the host's IPX routing table, either change the 7318's network address in the ComNetServer configuration stanza or check with your network administrator to verify the correct IPX network configuration.
This number is the 7318's hardware address and is labeled on the back of the 7318.
The default boot image and path for the model P10 and S20 are /usr/lib/cns/cns-p10 and /usr/lib/cns/cns-s20 (or /usr/lib/cns/cns-s20e) respectively.
NOTE: SMIT automatically refreshes the cnsview daemons. Reboot the 7318. This can be done in two ways.
cnsview -c reboot /dev/cnsXX
(where cnsXX is the 7318 cns number).
If the 7318 still does not boot, continue with the next section.
NOTE: It is possible that the device data in the ODM is corrupt and a complete reconfiguration solves the problem. If the 7318 still fails to boot, continue to the next section.
In a broadcast load configuration, the 7318 requests its boot image and configuration from the host. The boot image and configuration file must have permissions that allow the 7318 to download them.
The default is /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
Now that we have verified that an IPX network exists, it is time to check IPX communication between the host and the 7318. To verify IPX communication between the 7318 and host machine, send a broadcast IPX ping to every 7318 on the network.
cnsview -c "ipxping -b"
To IPX ping a specific 7318, execute:
cnsview -c "ipxping external_ipx_network_number:7318's_Ethernet_address"
for example,
cnsview -c "ipxping 00000002:00406ee00155"
Sample output is as follows:
[root@ivorye] / # cnsview -c "ipxping -b" 00000002:00406ee00175 is responding but not online 00000002:00406ee00155 is responding but not online 00000002:00406ef000f0 is responding and online
NOTE: The success of an IPX ping implies the 7318 is powered on. There is an IPX path to the 7318. The routers, if any, are routing the packets correctly.
NOTE: The success of an IPX ping does NOT imply that the 7318 has booted, the 7318 is configured so that the SPX link is present.
If the 7318 is not listed and is local to the host (on the same LAN, including hubs) check if the IPX network on which the 7318 resides is listed in the host's IPX routing tables.
In this section, we will verify the boot parameters specified in the NVRAM. For a directed load configuration, all booting parameters (load host and boot files) are specified 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.
9600 baud 8 data bits no parity 1 stop bit
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.
admin
show
Default load images (in the /usr/lib/cns directory) are as follows:
Sample command to set the load image for a P10 is as follows:
set loadimage /usr/lib/cns/cns-p10
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.
To modify the load interface, use the set command to specify the correct 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
where:
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.
show
NOTE: The latest BIOS level as of 03/25/99 is 5.23. If you are unsure whether the 7318 is at the latest BIOS level, please contact an IBM AIX Technical Specialist.
To modify the frametype, use the set command to specify the correct 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
where:
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.
To modify the protocol, use the set command to specify the correct protocol. The 7318 can be forced to use either IPX (1) or TCP/IP (2) to load. If unsure, leave the default value.
Sample command to set the protocol is as follows:
set protocol 1
where:
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 does not exist.
To force the 7318 to download files from a specific SPX/IPX host, set the host1 parameter with the internal IPX network number of the host (this is done in the 7318's BIOS Console).
Sample command to set an IPX load host (host's internal_network number is 8ae46c31) is as follows:
set host1 8ae46c31:000000000001
If any boot parameters were changed, save the modifications, execute:
save
Continue to the next section.
Now that we have verified the 7318's NVRAM configuration:
Many times error reporting can show why the Terminal Server is not booting properly. When configured, these errors and their codes can be logged to a file. This section sets up error reporting for cns, the software that manages the Terminal Server.
config svclts 2sess periodic method vpd boot stats
cnsview -c "daemon stop"# cnsview -c "daemon start"
WARNING: All other Terminal Server communication (IPX) will be stopped on the host when these daemons are recycled.
cnsview -c "reboot" /dev/cnsXX
where cnsXX is the 7318 cns number.
NOTE: The resource names used in the AIX error log are as follows:
cnsdd - Events logged by the CNS device driver
cnsview - Events logged by the CNSVIEW daemon for the 7318 units
cnld - Events logged by the CNSVIEW daemon associated with downloading/
booting
errpt -aNcnsdd | more
NOTE: Every 3-4 minutes, the cnsview daemon checks the status of the SPX links to those 7318 devices which were configured. When the SPX links are not present, an error log entry is made, similar to the following:
ERROR LABEL: CNS_DISCONNECT ERROR ID: 5EBD0D06 Date/Time: Fri Jun 9 22:34:41 Sequence Number: 9987 Machine Id: 000001871800 Node Id: levesconte Error Class: S Error Type: PERM Resource Name: cnsdd Error Description Driver for ComServer Probable Causes REMOTE NODE Failure Causes COMMUNICATIONS/REMOTE NODE SOFTWARE PROGRAM Recommended Actions RUN STANDALONE DIAGNOSTICS Detail Data ERROR CODE 0000 0000 Comm Probable Cause REMOTE NODE Failure Causes COMMUNICATIONS/REMOTE NODE SOFTWARE PROGRAM Recommended Actions RUN STANDALONE DIAGNOSTICS Detail Data ERROR CODE 0000 0000 Communications Device Name: 00406e0002db
If the 7318 still fails to boot, there may be a problem with the cns software on the RS/6000. If you suspect a software bug, run the following command to determine the level of the cns software on the RS/6000.
lslpp -h *cns* | pg
lslpp -h *7318* |pg
Contact AIX SupportLine or use the Fixdist application for a listing of the latest PTFs for the 7318 software.