hp-support-head-portlet
Actions
- ${title}
Loading...
HP Support
hp-contact-secondary-navigation-portlet
Actions
- ${title}
Loading...
hp-hero-support-search
Actions
- ${title}
Loading...
hp-share-print-widget-portlet
Actions
- ${title}
Loading...
hp-concentra-wrapper-portlet
Actions
- ${title}
Loading...
OpenVMS - VXT 2000: Troubleshooting a Malfunctioning VXT 2000 which Boots from an Infoserver
Issue
The following article gives some suggestions on how to troubleshoot a malfunctioning VXT 2000 which boots from an Infoserver.
Solution
1. Halt the VXT 2000 terminal using the small button
on the back of the VXT right next to the thickwire Ethernet port. Press
and hold for three seconds.
2. Next, on the VXT screen, you will see the console prompt:
>>>
Type the following command:
>>> T/UTIL 1 <press return>
3. The VXT 2000 terminal will blink a couple of times,
and then start a memory self-test, and then tests the video card and
Ethernet ports. If there is an issue with the VXT terminal, you may see
one of the following error codes:
-
?? 002 3 QDZ 0080 - The keyboard failed the self-test. Check that the keyboard is plugged in correctly.
-
?? 001 9 VNI 0132 - The Ethernet failed the self-test. Check that your network cable is plugged in correctly. There may be a defective network controller or bad BNC connectors. Check to see if at the back of VXT terminal whether the device is correctly terminated.
-
?? 020 12 IMG 0016 - The image accelerator option board failed the self-test. Check that the board is installed correctly. For VXT 2000 system box models, see VXT 2000 Windowing Terminal Installation Information. For other models, see instructions supplied with the image accelerator board.
-
?MOP 1 Transmit error. - MOP was unable to transmit due to a system board error.
-
?MOP 255 - Not enough space in memory to load the image. There is a possibility of defective memory.
-
?IP 2 - An ICMP Protocol Unreachable message was received. The TFTP host listed in the BOOTP response does not understand the user datagram protocol (UDP) that TFTP runs over. The IP download stops.
-
?IP 3 - An ICMP Port Unreachable message was received. The remote TFTP daemon has either never been started or is not running on the load host. The IP download stops.
-
?TFTP 1 - A TFTP error message was received while sending a TFTP Read Request packet. The TFTP load stops. This error usually means a file was not found or you do not have access to the file.
-
?TFTP 3 - A TFTP error message was received while sending a TFTP Acknowledgment packet. The TFTP load stops.
-
?TFTP 5 - A TFTP error message was received while sending a TFTP Error packet. The TFTP load stops.
-
?TFTP 255 - Not enough space in memory to load the image. There is a possibility of defective memory.
4. During the sequence of booting, you will see the following:
Mopv3…Mopv4…Tftpboot…Mopv3…Mopv4…Etc...
5. If the VXT 2000 is broadcasting out on the network, shortly afterwards, you will see the word SERVER followed by an Ethernet address of the device that answered the mop request.
Log on to the Infoserver, and issue the command:
>show server
And see if the Infoserver’s address matches what was shown on the VXT terminal.
6. If the VXT boots, you may see something like this:
##*##*#
The pound-sign (#) indicates a successful load of a portion of the VXTLDR image, and the asterisk (*)
indicates a retransmit request. If you have more asterisks than
pound-signs, then you also could have a network connectivity issue. If
you have more pound-signs than asterisks, this is good, and shortly you
should get a successful boot of the VXT terminal.
hp-feedback-input-portlet
Actions
- ${title}
Loading...
hp-online-communities-portlet
Actions
- ${title}
Loading...
Prefer to troubleshoot on your own?
hp-feedback-banner-portlet
Actions
- ${title}
Loading...
hp-country-locator-portlet
Actions
- ${title}
Loading...
Country:
Indonesia
Indonesia
hp-detect-load-my-device-portlet
Actions
- ${title}
Loading...







