Solving Bootup Problems

This section includes the following topics:

If a "BOOT FAILED" Error Message Appears

If a "Boot Failed" error message appears, identify the specific problem by following the steps outlined in the following sections:

Step 1: Review All Error Messages

Accompanying the above bootup error message are other error messages. Look them up in Messages and take the action suggested there.

Step 2: Use the Simplest Configuration

If you cannot solve the problem in Messages, verify that the network and essential host programs are operating normally by downloading the server using the simplest configuration.

In its simplest configuration the X station depends only on the TFTP software running on the host software.

To use the simplest configuration, connect the X station to the computer without an intervening gateway.

On the [General Network] configuration screen, click on [Factory Defaults], then set Network Parameters to [from Fields Below].
On the [Ethernet Network] configuration screen, set IP Address to the X station's IP address and File Server to the computer with the X station's base system file.

Step 3: Check the X Station Hardware

If the X station does not boot when using its simplest configuration, run the built-in selftests:

Access the configuration screens. Depending upon the type of X station you have, you may need to:
- Click on the [Setup] icon,
- Click on [To Config], or
- Press the space bar.
Click on [Diagnostics], then [Selftests].

For more details on the Selftests screen, refer to Using the Selftests Screen.

Step 4: Test the Network

Once it is given an IP address, the X station can respond to a ping.

Press and hold [F12] to access the configuration screens.
Click on [Network], then click on [Ethernet].
Click in the IP Address field and enter your X station's IP address.
Click on [OK].
Turn the X station off and on.
To ping the X station, log into the file server from another X station or console and type:
/etc/ping Xstation_ip_address
for example: /etc/ping 75.4.11.128
(For HP-UX 10.x systems, type:
/usr/sbin/ping Xstation_ip_address).

If the X station is correctly connected to the LAN, it echoes packets.

Step 5: Check TFTP

If the network is working, but the server code still does not download, check the operation of TFTP as follows;

Invoke the administration scripts, as described in Running the X Station Administration Scripts.
Choose Installation testing from the main menu.
Choose Check software installation from the installation testing menu.

This automatically verifies the operation of TFTP.

If TFTP passes, try increasing the File Timeout setting on the [General Network] configuration screen.

Step 6: Check the Software Installation

If TFTP and NFS fail but the LAN is working, configuration files may not be set up properly on the file server or the X station software may not be installed correctly:

If you have an inetd security file at /usr/adm/inetd.sec, ensure that you included the IP address of your X station.
If you have a large /etc/hosts table (with more than 200 entries), be sure that your X station is entered near the top of the table.

Solving BOOTP Problems

This section helps you solve some problems you may encounter with BOOTP. See:

If You Are Transferring Parameters through a Gateway

Using BOOTP to transfer parameters through a gateway may work, but it is not supported; the boot server should be on your immediate network subnet. If you cannot use BOOTP, on the [General Network] configuration screen set the configuration to "Network Parameters [from Fields Below]" and on the Ethernet Network screen type in the network values.

If You Have Edited bootptab Manually...

If an error is present in an entry, all entries below the erroneous entry are inaccessible. These errors are best diagnosed by turning on inetd loggin. Refer to the man page for inetd for details.

Note: We strongly recommend that you use the administration script (xtadm) to create bootptab entries instead of editing the file directly.

For more information about editing bootptab manually, refer to the following sections:

Including Vendor Information Tags

The BOOTP packet is divided into a standard portion and a vendor information portion. The tags that supply vendor information are terminalname.domain, ds, gw, sm, T144, and T145. T144 and T145 are specific to the X station:

Tag: Description
T144: Specifies the name of the remote configuration file, if any. The name of the file must be in double quotes, for example, "xterm1.cfg".
T145: Specifies the name or IP address of the file server, the computer where the base system code resides, if different from the computer that responds to the BOOTP request (the boot server). Two names or IP addresses separated by a blank are permitted; the first is stored in the File Server field and the second is stored in the Alt. File Server field. The names or IP addresses must be in double quotes, for example, "75.6.8.3 75.6.8.5". Leave this tag out if the file server is the same as the boot server.

Size Limitations on Vendor Information

The total size of the vendor information portion of a BOOTP packet cannot be larger than 64 bytes. Hence, it is important to minimize the length of all strings. It may also be advisable to omit the inclusion of an alternative name server unless it is deemed necessary.

The size of the vendor information portion of a BOOTP packet can be calculated as follows:

terminalname = 2 bytes + string
domain = 2 bytes + string
ds = 2 bytes + 4 bytes/name server
gw = 2 bytes + 4 bytes for the gateway
sm = 6 bytes
T144 = 2 bytes + string (excluding quotation marks)
T145 = 2 bytes + string (excluding quotation marks)

If There Is Not Enough Room for Your Vendor Information...

If there is not enough room for your information in the vendor information portion of the BOOTP packet, you can still download the information by using a remote configuration file. If you installed your X stations by using the administration script, it created the remote configuration files automatically and you need only to edit them. For details on using remote configuration, refer to Configuration Options.

Solving NFS Problems

If the X station boots using TFTP but not using NFS, NFS probably has not been set up properly:

Ensure that your X stations have entries in /etc/exports and /etc/hosts.
Ensure that the installation directory is NFS exported. Usually this happens automatically when you install the ENWARE software. However, if the installation script was unable to update the necessary file, you may need to do this manually as follows:
1. Edit the /etc/exports file (Note: on Solaris 1.x systems, this is /etc/hosts. On Solaris 2.x systems this is: /etc/dfs/dfstab)
2. Insert a line into this file to reference the installation directory, for example:
  /opt/hpxt/enware/xthome
Verify that the NFS mount daemon is running with the secure option switched off. If the secure mode is switched on, the X station cannot use NFS. Refer to your NFS documentation for information on the operation of the secure option.
Verify that NFS is actually running. Use the following commands to verify that the required daemons are running on your file server:
```
ps -ef | grep nfsd
ps -ef | grep mountd
```
Verify that the base system file, the X server file, and the fonts have read permission for other and that basepath/bin and your font directories have read and execute permissions for other.

If NFS works in general except for certain fonts, there must be something peculiar about these fonts. Look in /etc/checklist (/etc/fstab for HP-UX 10.x) and review the partitioning of your file systems.

If you use the administration script to add an X station while NFS is installed on your computer, your X station is assigned export permission for all installed ENWARE font directories. Additional font directories must be on the same physical drive or disk partition. If your font directories do not meet this condition, you need to edit /etc/exports.

If you are able to boot using TFTP but occasionally have problems with NFS, check the number of CRC errors on the Ethernet Statistics screen to see if you have a noisy LAN.

Note: NFS may not work over devices unable to accommodate an entire 8KB NFS read or write buffer sent in a burst. This includes HP Remote Bridges operating over serial links of less than 64 Kbps.

Solving Problems Related to Token Ring

With the addition of the Token Ring adapter card, the ENVIZEX station can boot using either the Token Ring or the Ethernet interface. When configured to use BOOTP, the X station first tries the Token Ring interface. If the attempt fails, the X station then tries to boot from the Ethernet interface.

Topics in this section include:

Normal Behavior

When you boot an ENVIZEX station that has a Token Ring adapter card installed, the boot screen displays a Token Ring icon:

If this icon is not present and you have installed an adapter card, open the chassis and ensure the card is seated properly (push down).

Changing Default Ring Speed

With the ENVIZEX Token Ring Adapter, you can connect your ENVIZEX station to a Token-Ring network with a speed of either 4 Mbps or 16 Mbps. The default speed is 16Mbps. If you have a Token Ring with a data speed of 4 Mbps, you MUST change the default speed as follows:

Press and hold [F12] to access the configuration screens.
Select the [Network] screen.
Select [Token Ring].
Change the TokenRing Ring Speed to 4Mbps.
Click on [OK].
Reboot the X station.

Running Token Ring Selftests

The first step towards diagnosing a problem involving the Token Ring connection is to run the selftests from the [Token Ring] Network screen. A message line below the selftest button displays state messages for 60 seconds, or until the selftest passes, whichever comes first. These messages are also logged to the log screen.

Selftest Messages and Conditions

If the selftest passes, the Token Ring adapter card inserts itself into the ring and functions normally. The message sequence for a normal selftest is:

Performing Token Ring Selftests...
Trying Bring Up Diagnostics
Bring Up Diagnostics Passed
Test Passed

If the selftest detects an error, the two most likely causes are:

The ring is beaconing (most likely due to a speed difference), or
The cable needs to be re-connected or replaced.

If the Ring Is Beaconing...

If the ring is beaconing, the usual message sequence is:

Performing Token Ring Selftests...
OPEN: Error During Insertion. Ring Beaconing (check speed)
Selftest Display Timer Expired

If the selftest determines beaconing on the ring (most likely due to a speed difference), the selftest terminates. After you have changed the Token Ring Speed (Default = 16Mbps), remember to reboot the X station to regain the connection to the Token Ring.

If the Cable Needs to Be Replaced...

If the cable has been disconnected or needs to be replaced, the usual message sequence is:

Performing Token Ring Selftests...
Ring Recovery
Wire Fault
Trying Bring Up Diagnostics
Bring Up Diagnostics Passed
Selftest Display Timer Expired
OPEN: Error During Lobe Test. Function Failure.

If you see these messages, examine both ends of the cable to ensure proper connection. If necessary, replace the cable and run the selftest again.

If the selftest fails for any other reason, contact your Hewlett-Packard support representative.

If the Problem Relates to BOOTP

Depending upon the version of BOOTP you are running, you may have to use the wire link level address instead of the option link level address in the bootptab entry.

Solving Problems Related to 100VG

Topics in this section include:

Normal Behavior

When you boot an ENVIZEX X station that has a 100VG adapter card installed, the boot screen displays a 100VG icon:

If this icon is not present and you have installed an adapter card, open the chassis and ensure the card is seated properly (push down):

If a red "X" appears over the icon, check the cable connection from the X station to the hub. Click on the [Start] icon to reboot.

When you attach an X station to a 100VG network, there is an initial training period (called "logging in a node") during which the hub becomes aware of the node and includes it in its polling cycle. During this period (up to 12 seconds), no data can be sent or received over the network.

Note: The 100VG card for ENVIZEX X stations supports Ethernet framing only: it does not support Token Ring framing.

Selftests

The first step towards diagnosing a problem involving the 100VG connection is to run the selftests from the [100VG] Network screen. A message below the selftest button displays diagnostic messages. These messages are also logged to the log screen.

Common messages and suggested actions include:

The cable may be bad or disconnected: Check the connections at the X station and the hub. Replace the cable to verify problem diagnosis.
The cable has too much noise: Replace the cable from the X station to the hub to ensure optimum transmission. Use a 4-pair, voice-grade or better (type 3) cable for 100VG connections.

Troubleshooting Hints

Run the selftests as described in Selftests. If an error occurs, take the appropriate action as indicated by the error message. Check the log screen (in the [Diagnostics] configuration screens) for all messages.
Monitor the 100VG network statistics. Choose [100VG Statistics] from the Diagnositics screen menus. These statistics measure the number of frames received and transmitted and may indicate errors occurring on the LAN or possible hardware problems.