If the problem reappears on the device or if the hardw are failure appears to be associated with an in terface card or an in ternal component of the system module, you should refer the problem to y our HP service represen tative.
Proceed to Step 4 (\Rebooting Y our System").
Step 3b: Recovering from a File System Problem
If the panic message indicates a problem with one of y our le systems, y ou will need to run the le system c hecker fsck (1m) to check and correct the problem(s). This is normally done automatically at boot time (from the /etc/rc le) so you should proceed to step 4 (rebooting y our system). Follow all directions that fsck gives you especially if it is your root le system (the one with the \/" directory) that has the problem . It is important to use the \
Step 3c: Recovering from a LAN Communication Problem
If the panic messages indicates a problem with LAN comm unication (such as when a diskless cluster clien t node is prevented from communication for too long), check all LAN cable connections to be sure of the following:
6
All connectors are tigh tly fastened to the LAN cable and the media access units (MAU's).
LAN is assembled correctly and does not exceed recommended lengths. If you use an AUI, the LAN must be connected directly to the MAU with no intervening length of cable bet ween the MAU on your Model 742i to the LAN tee.
Your LAN is properly terminated. Proceed to step 4 (rebooting y our system).
Step 3d: Recovering from Other Situations
When you suspect the problem w as something other than the abo ve (or when you do not know where to classify it), proceed to step 4 \ Rebooting your system ." In this case, it is especially important that y ou write down the exact text of the panic message, just in case y ou need it for future troubleshooting or help from HP service personnel.
FINAL TRIM SIZE : 7.0 in x 8.5 in