User`s guide

System Troubleshooting and Diagnostics
5.5 Using MOP Ethernet Functions to Isolate Failures
***system 2***
$ MCR NCP
NCP>SET MODULE CONFIGURATOR CIRCUIT ISA-0 SURVEILLANCE ENABLED
NCP>SHOW MODULE CONFIGURATOR KNOWN CIRCUITS STATUS TO ETHER.LIS
NCP>EXIT
$ TYPE ETHER.LIS
Circuit name = ISA-0
Surveillance flag = enabled
Elapsed time = 00:09:37
Physical address = 08-00-2B-28-18-2C
Time of last report = 27-Feb 11:50:34
Maintenance version = V4.0.0
Function list = Loop, Multi-block loader, Boot, Data link counters
Hardware address = 08-00-2B-28-18-2C
Device type = ISA
Depending on your network, the file used to receive the output from the SHOW
MODULE CONFIGURATOR command may contain many entries, most of
which do not apply to the system you are testing. It is helpful to use an editor
to search the file for the Ethernet hardware address of the system under test.
Existence of the hardware address verifies that you are able to receive the
address from the system under test.
5.6 Interpreting User Environmental Test Package (UETP)
OpenVMS Failures
When UETP encounters an error, it reacts like a user program. It either
returns an error message and continues, or it reports a fatal error and
terminates the image or phase. In either case, UETP assumes the hardware is
operating properly and it does not attempt to diagnose the error.
If the cause of an error is not readily apparent, use the following methods to
diagnose the error:
• OpenVMS Error Log Utility—Run the Error Log Utility to obtain a
detailed report of hardware and system errors. Error log reports provide
information about the state of the hardware device and I/O request at the
time of each error. For information about running the Error Log Utility,
refer to the OpenVMS Error Log Utility Manual and Section 5.2 of this
manual.
• Diagnostic facilities—Use the diagnostic facilities to test exhaustively a
device or medium to isolate the source of the error.
System Troubleshooting and Diagnostics 5–59