ASR User Override Capability
While the default settings will properly configure or deconfigure the server in most cases, it is useful to provide advanced users with a manual override capability. Because of the nature of "soft" versus "hard" deconfiguration, it is necessary to provide two related but different override mechanisms.
"Soft" Deconfigure Override
For any subsystem represented by a distinct device tree node, users may disable that function via the NVRAM variable asr-disable-list, which is simply a list of device tree paths separated by spaces.
ok setenv asr-disable-list /pci@1f,2000 /pci@1f,4000/scsi@3,1
The Enterprise 250 OBP will use this information to created disabled status properties for each node listed in the variable asr-disable-list.
"Hard" Deconfigure Override
For overriding those subsystems that require "hard" deconfiguration (CPU and memory), the OBP commands asr-enable and asr-disable are used to selectively enable or disable each subsystem.
Note -
There are duplications between the soft and hard overrides. If possible, the hard override commands asr-enable and asr-disable should be used.
You can generate a list of valid parameters for asr-disable and asr-enable by issuing either command without parameters.
ok asr-disable ? Invalid subsystem name: Known 'enable/disable' subsystem components are: bank* bank3 bank2 bank1 bank0 dimm15 dimm14 dimm13 dimm12 dimm11 dimm10 dimm9 dimm8 dimm7 dimm6 dimm5 dimm4 dimm3 dimm2 dimm1 dimm0 cpu* cpu1 cpu0 ok
To track the status of all manual overrides, a new user command, .asr, is provided to summarize the current settings.
ok asr-disable cpu1 bank3 ok .asr CPU0: Enabled CPU1: Disabled SC-MP: Enabled Psycho@1f: Enabled Cheerio: Enabled SCSI: Enabled Mem Bank0: Enabled Mem Bank1: Enabled Mem Bank2: Enabled Mem Bank3: Disabled PROM: Enabled NVRAM: Enabled TTY: Enabled SuperIO: Enabled PCI Slots: Enabled
- © 2010, Oracle Corporation and/or its affiliates