|
|
OpenBoot DiagnosticsYou can run various hardware diagnostics in OpenBoot to troubleshoot hardware and network problems. The diagnostic commands are listed in Table 3.13.
The following examples use some of the diagnostic features of OpenBoot. To identify peripheral devices currently connected to the system, such as disks, tape drives, or CD-ROMs, you use OpenBoot probe commands. To identify the various probe commands and their syntax, you use the OpenBoot sifting command, as follows: sifting probe The system responds with this: (f006c444) probe-all (f006bf14) probe-pci-slot (f006baa4) probe-scsi-all (f0060de8) probe-pci . . . <output has been truncated> The OpenBoot sifting command, also called a sifting dump, searches OpenBoot commands to find every command name that contains the specified string. This first example uses the OpenBoot probe command, probe-scsi, to identify all the SCSI devices attached to a particular SCSI bus: ok probe-scsi This command is useful for identifying SCSI target IDs that are already in use or to make sure that all devices are connected and identified by the system. The system responds with this: Target 1 Unit 0 Disk IBM DDRS34560SUN4.2GS98E Target 3 Unit 0 Disk IBM DDRS34560SUN4.2GS98E Note OpenBoot probe Commands The most common OpenBoot probe commands are probe-scsi and probe-scsi-all, which are used to obtain a free open SCSI target ID number before adding a tape unit, a CD-ROM drive, a disk drive, or any other SCSI peripheral. Only devices that are powered on will be located, so you need to make sure everything is turned on. You can use this command after installing a SCSI device to ensure that it has been connected properly and that the system can see it. You can also use this command if you suspect a faulty cable or connection. If you have more than one SCSI bus, you use the probe-scsi-all command, but only after a reset-all has been issued; otherwise the system is likely to lock up. This example uses the probe-ide command to identify all IDE devices connected to the PCI bus: ok probe-ide
Device 0 ( Primary Master )
ATA Model: ST34321A
Device 1 ( Primary Slave )
Not Present
Device 2 ( Secondary Master )
Removable ATAPI Model: CRD-8322B
Device 3 ( Secondary Slave )
Not PresentThis example tests many of the system components, such as video, the network interface, and the floppy disk: ok test all To test the disk drive to determine whether it is functioning properly, you put a formatted, high-density disk into the drive and type the following: ok test floppy The system responds with this: Testing floppy disk system. A formatted disk should be in the drive. Test succeeded. You type eject-floppy to remove the disk. Table 3.14 describes other OpenBoot commands you can use to gather information about the system.
The following example uses the banner command to display the CPU type, the installed RAM, the Ethernet address, the host ID, and the version and date of the startup PROM: ok banner The system responds with this: Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 270MHz), No Keyboard OpenBoot 3.31, 128 MB (60 ns) memory installed, Serial #10642306. Ethernet address 8:0:20:a2:63:82, Host ID: 80a26382. This example uses the .version command to display the OpenBoot version and the date of the startup PROM: ok .version The system responds with this: Release 3.31 Version 0 created 2001/07/25 20:36 OBP 3.31.0 2001/07/25 20:36 POST 3.1.0 2000/06/27 13:56 Note Checking the OpenBoot Version from a Shell Prompt You can display the OpenBoot version from a shell prompt by typing this: /usr/sbin/prtdiag -v The system displays the following system diagnostic information and the OpenBoot version is displayed at the end of the output: System Configuration: Sun Microsystems sun4u Sun Ultra 5/10 UPA/PCI
(UltraSPARC-IIi 270MHz)
System clock frequency: 90 MHz
Memory size: 128 Megabytes
========================= CPUs =========================
Run Ecache CPU CPU
Brd CPU Module MHz MB Impl. Mask
--- --- ------- ----- ------ ------ ----
0 0 0 270 0.2 12 1.3
========================= IO Cards =========================
Bus# Freq
Brd Type MHz Slot Name Model
--- ---- ---- ---- -------------------------------- ----------------------
0 PCI-1 33 1 ebus
0 PCI-1 33 1 network-SUNW,hme
0 PCI-1 33 2 SUNW,m64B ATY,GT-C
0 PCI-1 33 3 ide-pci1095,646.1095.646.3
0 PCI-2 33 1 pci-pci1011,25.4
No failures found in System
===========================
========================= HW Revisions =========================
ASIC Revisions:
---------------
Cheerio: ebus Rev 1
System PROM revisions:
----------------------
OBP 3.31.0 2001/07/25 20:36 POST 3.1.0 2000/06/27 13:56This example shows how to use the .enet-addr command to display the Ethernet address: ok .enet-addr The system responds with this: 8:0:20:1a:c7:e3 To display the CPU information, type the following: .speed The system responds with this: CPU Speed : 270.00MHz UPA Speed : 090.00MHz PCI Bus A : 33MHz PCI Bus B : 33MHz Input and Output ControlThe console is used as the primary means of communication between OpenBoot and the user. The console consists of an input device that is used for receiving information supplied by the user and an output device that is used for sending information to the user. Typically, the console is either the combination of a text/graphics display device and a keyboard, or an ASCII terminal connected to a serial port. The configuration variables that are related to the control of the console are listed in Table 3.15.
You can use the variables in Table 3.15 to assign the console's power-on defaults. These values do not take effect until after the next power cycle or system reset. If you select keyboard for input-device and the device is not plugged in, input is accepted from the ttya port as a fallback device. If the system is powered on and the keyboard is not detected, the system looks to ttyathe serial portfor the system console and uses that port for all input and output. You can define the communication parameters on the serial port by setting the configuration variables for that port. These variables are shown in Table 3.16.
The value for each field of the ttya-mode variable is formatted as follows: <baud-rate>,<data-bits>,<parity>,<stop-bits>,<handshake> The values for these fields are shown in Table 3.17.
 |
|
|