What next, How to deconfigure a device manually, Before you begin – Sun Microsystems Sun Fire V490 User Manual
Page 190: What to do

162
Sun Fire V490 Server Administration Guide • August 2004
What Next
You can now issue commands and view system messages on the local console.
How to Deconfigure a Device Manually
Before You Begin
To support the ability to boot even when nonessential components fail, the
OpenBoot firmware provides the asr-disable command, which lets you manually
deconfigure system devices. This command “marks” a specified device as disabled,
by creating an appropriate “status” property in the corresponding device tree node.
By convention, UNIX will not activate a driver for any device so marked. For
background information, see
■
“About Manually Configuring Devices” on page 59
What to Do
1. At the system ok prompt, type:
where the device-identifier is one of the following:
■
Any full physical device path as reported by the OpenBoot show-devs command
■
Any valid device alias as reported by the OpenBoot devalias command
■
An identifier for a device given in “Reference for Device Identifiers” on page 61
Note –
Manually deconfiguring a single processor causes the entire CPU/Memory
board to be deconfigured, including all processors and all memory residing on the
board.
OpenBoot configuration variable changes take effect after the next system reset.
ok asr-disable
device-identifier