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.
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 hmc, 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 42.
3 read service processor error logs
displays error conditions detected by the service processor. refer to “service processor error logs” on page 40 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 39.
enable/disable processor hot sparing
this function 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 aix.
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. 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 ″deconfigured by system″ 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.
the processor numbering scheme used by the service processor is different from the numbering scheme used by aix. consult the aix documentation before configuring or deconfiguring a processor to ensure that the correct processor is selected.
the number of processors available to aix can be determined by issuing the following command on the aix command line: bindprocessor -q
8 memory configuration/deconfiguration menu
enable/disable memory repeat
memory repeat gard will automatically deconfigure a memory riser card during a system boot if a memory card has failed bist (power-on self-test), caused a machine check or checkstop, or has reached a threshold of recoverable errors. the memory will remain deconfigured until repeat gard is disabled or the memory card is replaced.
for more information, see “configuring and deconfiguring processors or memory” on page 39.
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 card on 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 cards offline, this menu allows you to deconfigure a memory card, and then reconfigure the card 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 card. 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 aix.
the fields in the previous table represent the following:
column 1
1. menu selection index/card number
column 2
xx.xx : card address used by service processor
column 3
(00.-) error/deconfiguration status
the error status of the each memory card 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, 11.16(00, -)) indicates that the memory card has not had any errors logged against it by the service processor, and it is fully configured.
the field after the error status will be a ″-″, ″0″, or ″1″. the dash indicates that the memory card is fully configured. a zero or a one indicates that memory repeat gard has deconfigured half of the memory
card. if this occurs, the status of the card in the menu is shown as ″partially deconfigured by system.″
to change the memory configuration, select the number of the memory card. the memory card state will change from configured to deconfigured or from deconfigured to configured.
this menu only allows the deconfiguration of an entire card; it does not allow the manual deconfiguration of half a card. if half a card has been configured by the system (″partially deconfigured″), it can be manually reconfigured using this menu.
in the previous example menu, each line shows two cards 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 card is retained. if a card 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 card is taken offline again because of its history of failures.
9 power control network utilities menu
1 lamp test for all operator panels
this option is not available on this system.
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 of the service processor 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. for the i/o type, type a5.
if either value is not valid, a failure message displays on the console. press enter to return to the power control network utilities menu.
10 led control menu
this menu displays the state of the i/o subsystem disturbance/system attention led. 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 processor subsystem is powered on and the service processor menus are available). option 1 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 is shown. the screen will be similar to the following:
if one of the devices is selected using the index number, the present state of its led will be displayed, and you will be given the option to toggle it as shown in these example screens. the final state of the led will then be displayed whether it was changed or not.
option 2 is not available on this system.
11 interposer plug count menu
do not power on the system when in this menu. fully exit from this menu before powering on the system.
this menu tracks the number of times that the mcm and l3 cache modules have been plugged into the system backplane.
if the mcm or l3 cache module is reseated or replugged, the plug count for that module must be incremented by 1. if the plug count exceeds the limit of 10 (reaches 11 or greater), a 450x yyyy or 4b2x yyyy error with a detail value of cff0 that calls out an mcm or l3 cache module will be posted in the service processor error log. the fru should be replaced during a deferred service call.
if the mcm or l3 cache module is replaced, or installed during an mes upgrade, the plug count must be set using the interposer plug count menu. if the plug count information is not included with the new or replacement module, enter the default value of 8 (7 for the manufacturing process and 1 for the installation of the module that was just done). if the plug count is not entered, a b1xx 4699 error code, with a detailed value of e10b or e10c, will be posted in the service processor error log.
if the service processor card is replaced, the plug counts are retained. however, the plug count menu must be accessed and option 50, commit the values and write to the vpd, must be executed, so that the plug counts are revalidated. if the counts are not revalidated, a b1xx 4699 error code, with a detail value of e10b or e10c, will be posted in the service processor error log.
a screen similar to the following will be displayed.
the mcm modules and l3 cache modules are shown in the same way that they are plugged into the processor subsystem planar; the layout shown in the menu represents the physical location as seen from the front of the subsystem.
the format of the menu entries shown above is the menu index number, followed by l3_xx, followed by the plug count after the colon. the following tables correlates the information shown above with the physical location codes.
enter a menu index number to change the plug count for a particular module. for example, to change the plug count of the l3 cache module that is physically in the upper-left corner (u1.9-p1-c1), type 1, then enter the new plug count.
when all of the new plug counts have been entered, select 50, commit the values and write to the vpd. this action will store the new values in nvram.