System Startup, Configuration, and Shutdown Reference Manual (32650-90907)

Appendix E
Verifying Attached Devices
Overview
203
E Verifying Attached Devices
This section discusses using the initial system loader’s ODE utility to verify which devices are attached and
configured to a HP e3000 computer system.
Overview
SYSGEN provides utilities for listing the configured paths and associated devices of a system. It does not,
however, provide a utility for listing the devices actually attached to the system. (A valid configured path does
not require an associated device.) The initial system loader (ISL) provides the ODE utility for locating the
devices attached to a system.
A list of attached peripherals aids the system manager in assessing a system's needs, deciding where (on
which I/O paths) to add or remove peripheral devices, resolving I/O path conflicts (as with SYSGEN and NMMGR),
and restoring or copying a system’s configuration.
Displaying Configured Devices
ODE is a utility that is located in the ISL boot directory of an HP e3000 computer system. It can be launched
only from ISL, which indicates that the system is down.
When running with default options, ODE running mapper or mapper2 performs the following operations:
• Displays the current configuration of the processor, including the presence of coprocessor boards, analyzer
cards, memory sizes of cache and translation look-aside buffer (TLB) cards, the processor model number,
and the processor-dependent code (PDC) firmware revision.
• Checks all possible I/O paths to determine if a component is present, and identifies every component
(such as a module, bus converter, adapter, device, or unit.)
• Displays a table showing all configured components.
• Performs self-test and/or loopback tests on all components with self-test and/or loopback capabilities.
• Does not test any devices (terminals, data communication lines, or other serial devices) connected to
external ports of the terminal multiplexer.
The loopback test performs component-dependent loopback tests where feasible. The result of this test is
reported as pass, fail, unimplemented, or untestable.
The self-test initiates the internal self-test of each component that has a self-test routine. The result of this
test is reported as pass, fail, unimplemented, or untestable.
Running ODE
To run ODE :