User`s guide

System Troubleshooting and Diagnostics
5.6 Interpreting User Environmental Test Package (UETP) OpenVMS Failures
delete these log files yourself or rerun the entire UETP, which checks for old
UETP.LOG files and deletes them.
5.6.1.2 Possible UETP Errors
This section is intended to help you identify problems you might encounter
running UETP.
The following are the most common failures encountered while running UETP:
• Wrong quotas, privileges, or account
• UETINIT01 failure
• Ethernet device allocated or in use by another application
• Insufficient disk space
• Incorrect VAXcluster setup
• Problems during the load test
• DECnet–VAX error
• Lack of default access for the FAL object
• Errors logged but not displayed
• No PCB or swap slots
• Hangs
• Bug checks and machine checks
For more information refer to the VAX 3520, 3540 OpenVMS Installation and
Operations (ZKS166) manual.
5.7 Using Loopback Tests to Isolate Failures
You can use external loopback tests to isolate problems with the console port,
DSSI adapters (SHAC chips), Ethernet controller (SGEC chip), and many
common Q–bus options.
5.7.1 Testing the Console Port
To test the console port at power-up, set the Power-Up Mode switch on the
console module to the Loop Back Test Mode position (bottom) and install an
H3103 loopback connector into the MMJ. The H3103 connects the console port
transmit and receive lines. At power-up, the SLU_EXT_LOOPBACK test then
runs a continuous loopback test.
System Troubleshooting and Diagnostics 5–61