1 read vpd image from last system boot
displays manufacturer’s vital product data (vpd), such as serial numbers, part numbers, and so on, that was stored from the system boot prior to the one in progress now. vpd from all devices in the system is displayed.
2 read progress indicators from last system boot
displays a number of the boot progress indicators, which may include service processor checkpoints, ipl checkpoints, or aix configuration codes, from the previous system boot. this information can be useful in diagnosing system faults.
if you are running from a partitioned system, enter the partition id (0-15) to display progress indicators for that partition since the last system boot. in a full system partition, this option automatically displays details from partition 0.
the progress indicator codes are listed from top (latest) to bottom (oldest).
this information is not stored in nonvolatile storage. if the system is powered off using the power-on button on the operator panel, this information is retained. if the ac power is disconnected from the system, this information will be lost. for an example, refer to “lcd progress indicator log” on page 63.
3 read service processor error logs
displays error conditions detected by the service processor. refer to “service processor error logs” on page 62 for an example of this error log.
4 read system post errors
this option should only be used by service personnel to obtain additional debug information.
5 read nvram
displays non volatile random access memory (nvram) content.
6 read service processor configuration
displays current service processor configuration.
7 processor configuration/deconfiguration menu
enable/disable cpu repeat gard
cpu repeat gard will automatically deconfigure a cpu during a system boot if a processor has failed bist (power-on self-test), caused a machine check or check stop, or has reached a threshold of recoverable errors. the processor will remain deconfigured until repeat gard is disabled or the processor is replaced.
the default is enabled.
for more information, see “configuring and deconfiguring processors or memory” on page 58.
processor hot sparing
this option is not available on this system.
this menu allows the user to change the system processor configuration. if it is necessary to take one of the processors offline, use this menu to deconfigure a processor, and then reconfigure the processor at a later time. an example of this menu follows:
this table is built from vital product data collected during the last boot sequence. the first time the system is powered on, or after the system’s nonvolatile ram (nvram) has been erased, this table may be empty. the table is rebuilt during the next boot into the operating system.
the fields of the previous table represent the following:
column 1
(1.) menu selection index.
column 2
(0) logical processor device number assigned by aix. if the system is running aix, you can display these logical device numbers by issuing the following command on the aix command line:
lsdev -c | grep proc
column 3
(3.0) processor address list used by the service processor.
column 4
(00) error status of the processors.
the error status of each processor is indicated by ab, where b indicates the number of errors and a
indicates the type of error according to the following:
1. bring-up failure
2. run-time non-recoverable failure
3. run-time recoverable failure
4. group integrity failure
5. non-repeat-gardable error. the resource may be reconfigured on the next boot.
a status of 00 indicates that the cpu has not had any errors logged against it by the service processor.
to enable or disable cpu repeat gard, use menu option 77. cpu repeat gard is enabled by default.
if cpu repeat gard is disabled, processors that are in the 2deconfigured by system2 state will be reconfigured. these reconfigured processors are then tested during the boot process, and if they pass, they remain online. if they fail the boot testing, they are deconfigured even though cpu repeat gard is disabled.
the failure history of each cpu is retained. if a processor with a history of failures is brought back online by disabling repeat gard, it remains online if it passes testing during the boot process. however, if repeat gard is enabled, the processor is taken offline again because of its history of failures.
1. the processor numbering scheme used by the service processor is different from the numbering scheme used by the operating system. consult the operating system documentation before configuring or deconfiguring a processor to ensure that the correct processor is selected.
2. to determine the number of processors available to aix, run the following command on the aix command line: bindprocessor -q
the number of processor available to linux can be determined by issuing the following command on the linux command line: cat /proc/cpuinfo | grep power
memory configuration/deconfiguration menu
enable/disable memory repeat gard
memory repeat gard will automatically deconfigure a quad of memory during a system boot if a memory dimm has failed bist (power-on self-test), caused a machine check or check stop, or has reached a threshold of recoverable errors. the quad will remain deconfigured until repeat gard is disabled or the memory is replaced.
the default is enabled.
for more information, see “configuring and deconfiguring processors or memory” on page 58.
runtime recoverable error repeat gard
the runtime recoverable error repeat gard flag controls the deallocation of the memory if a recoverable error occurs during runtime. if a recoverable memory error occurs, and runtime recoverable error repeat gard is disabled, the system will continue running with no change in the memory configuration. if a recoverable memory error occurs, and runtime recoverable error repeat gard is enabled, the memory quad in which the error occurred will be garded out (taken offline).
the default is disabled.
these menus allow the user to change the system memory configuration. if it is necessary to take one of the memory dimms offline, this menu allows you to deconfigure a dimm, and then reconfigure the dimm at a later time.
when this option is selected, a menu displays. the following is an example of this menu:
after you select the memory card option by entering 1, a menu displays, allowing the selection of a memory dimm. the following is an example of this menu.
this table is built from vital product data collected during the last boot sequence. the first time the system is powered on, or after the system’s nonvolatile ram (nvram) has been erased, this table may be empty. the table is rebuilt during the next boot into the operating system.
the fields in the previous table represent the following:
column 1
1. menu selection index/dimm number
column 2
xx.xx : dimm address used by service processor
column 3
(00) error status
the error status of the each memory dimm is indicated by ab, where b indicates the number of errors and a indicates the type of error according to the following table:
1. bring-up failure
2. run-time non-recoverable failure
3. run-time recoverable failure
4. group integrity failure
5. non-repeat-gardable error. the resource may be reconfigured on the next boot.
an error status of 00 (for example, 3.16(00)) indicates that the memory dimm has not had any errors logged against it by the service processor.
to change the memory configuration, select the number of the memory dimm. the memory dimm state will change from configured to deconfigured or from deconfigured to configured.
in the previous example menu, each line shows two dimms and indicates whether they are configured.
to enable or disable memory repeat gard, use menu option 77 of the memory configuration/deconfiguration menu.
to enable or disable runtime recoverable error repeat gard, use option 78 of the memory configuration/deconfiguration menu.
the failure history of each dimm is retained. if a dimm with a history of failures is brought back online by disabling repeat gard, it remains online if it passes testing during the boot process. however, if repeat gard is enabled, the dimm is taken offline again because of its history of failures.
2 power control network utilities menu
1 lamp test for all operator panels
selecting this option tests the media drawer operator panel’s indicators by causing them to blink on and off for approximately 30 seconds.
2 display i/o type
this option is not available on this system.
3 change i/o type
use this option to change the i/o type after a service action or configuration change, if the i/o type is incorrect. if this option is chosen, you will be asked to make the following entries:
1. for the i/o drawer address, type 1.
2. if a 4-slot pci riser has been replaced, or is present in the system, type a6 for the i/o type. if a 6-slot pci riser has been replaced, or is present in the system, type a3 for the i/o type.
if either value is not valid, a failure message displays on the console. press enter to return to the power control network utilities menu.
3 led indicator menu
this menu displays the state of the processor subsystem disturbance/system attention led and the fault/identify led on the i/o subsystem(s). use this menu to toggle the attention/fault leds between identify (blinking) and off. option 1 is only available when the system is in the error state (the cec is powered on and the service processor menus are available). it is not available when the system is in standby. an example of this menu follows:
if option 1 is selected, a list of location codes of the i/o subsystems and the system unit drawer is shown. the screen is similar to the following:
if one of the devices is selected using the index number, the present state of its led is displayed, and you are given the option to toggle it as shown in the following example screen. the final state of the led is then displayed whether or not its state was changed.
option 2, clear system attention indicator, clears the attention indicator on the operator panel.
the processor subsystem disturbance/led is on the operator panel. the i/o drawer fault/identify led is located on the front of each i/o subsystem.
4 mcm/l3 interposer plug count menu
this option is not available on this system.
5 performance mode setup menu
if certain types of processor cards are installed in the system, this menu is not available. for other types of processor cards, this menu is active after the first boot.
the first time the system is booted after nvram is cleared, not applicable displays under performance mode setup menu on the screen. this might also happen if the service processor is replaced, or the processor cards are upgraded.
if performance mode setup menu is selected when not applicable displays the screen, the system responds with not applicable and redisplays the system information menu. the setup menu can be displayed after the performance mode is set, which occurs when the system is rebooted for the first time.
the default performance mode is set by the firmware during ipl. the default mode provides the optimum performance for the hardware configuration of the system. the performance mode is systemwide; it cannot be set on a per-partition basis.
you can override the default setting by using the default performance mode menu, which will be similar to the following:
selecting option 1 displays the following performance modes:
1. some processor card changes cause the default performance mode to change. this new setting is not reflected in the menu until after the system is rebooted with the new configuration.
2. if the nvram has been cleared, the default performance mode and the current performance mode will indicate uninitialized.
if you want to override the default setting, a brief description of each performance mode follows:
large commercial system optimization
is the setting for systems that do not fall into the other two categories, standard operation and turbo database mode. this setting provides the optimum performance for most applications.
standard operation
optimizes the system for large memory bandwidth applications where minimal sharing of data occurs and the likelihood of significant hardware data-prefetching exists.
turbo database mode
optimizes system operation for environments where there is a large amount of data sharing among processes running concurrently on the system.