| Dynamic Reconfiguration User's Guide 2.5.1 |
|
Contents
|
| Chapter 2 DR Environment and Administration | > 2.3 DR Configuration and Administration Issues | > 2.3.2 DR configuration and OBP (Open Boot PROM) |
When the system boots up, OBP will always choose the lowest numbered system board as a target where OBP program is loaded. The OS system program is loaded on the same board as well. The board where these programs are loaded at boot time is called "boot board". Since these programs are treated as kernel memory, the boot board cannot be detached on GP7000F model 1000/2000 and PRIMEPOWER 800/1000/2000. This policy can be overridden by using the following OBP property. The system boards listed on the kernel memory allocation option will not be chosen as the "boot board" and are chosen as the least candidates for a kernel memory board as well.
# eeprom no-obp-sb-cX=Y
# eeprom no-obp-sb="XY"
# eeprom no-obp-sb="XY-N"
where X is the cabinet number , Y is a concatenation of board numbers within the cabinet and N is logical number in the system board.
# eeprom no-obp-sb-c0=134
In the above example, the boards numbered 1, 3 and 4 on cabinet #0 are specified. On the next reset, OBP and system startup memory will not be allocated on these boards as the OBP home board.
# eeprom no-obp-sb="01 03 04 10"
In the above example, the boards numbered 1, 3 and 4 on cabinet #0 are specified, and the board numbered 0 on cabinet#1 is specified. On the next reset, OBP and system startup memory will not be allocated on these boards as the OBP home board.
If all the system boards on a partition are set as no-obp-sb-cX or no-obp-sb , OBP ignores the setting and behaves as if no board is specified.
OBP chooses the lowest numbered system board as the boot board among system boards not specified by the above option.
This feature is used to manage the system board pool. Please refer to "2.4 System board pool management" for details.
|
Contents
|