system information menu
1. read vpd image from last system boot
2. read progress indicators from last system boot
3. read service processor error logs
4. read system post errors
5. read nvram
6. read service processor configuration
7. processor configuration/deconfiguration menu
8. memory configuration/deconfiguration menu
9. power control network utilities menu
10. led control menu
11. mcm/l3 interposer plug count menu
12. performance mode setup menu
98. return to previous menu
99. exit from menus 0]
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 61.
3 read service processor error logs
displays error conditions detected by the service processor. refer to “service
processor error logs” on page 60 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 automatically deconfigures a cpu during a system boot if a processor has failed bist post, 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.
repeat gard is enabled by default.
enable/disable dynamic processor sparing
this option is part of the capacity upgrade on demand (cuod) function.
dynamic processor sparing is the capability of the system to deconfigure a failing (or potentially failing) processor and then configure a replacement processor from the unlicensed cuod processor pool.
if the system is running logical partitions, the hot sparing operation takes place while the system is running. if the system is booted in a full system partition, the system must be rebooted for the processor sparing operation to take place.
processor hot sparing is enabled by default.
for more information, see “configuring and deconfiguring processors or memory” on page 55.
the memory affinity of the failing processor is not taken into account when the replacement processor is assigned; the replacement processor is the next processor that is available.
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 the processor, and then reconfigure the processor at a later time. an example of this menu follows:
processor configuration/deconfiguration menu
77. enable/disable cpu repeat gard: currently enabled
78. enable/disable processor hot sparing (if available): currently enabled
1. 0 3.0 (00) configured by system 2. 1 3.1 (00) deconfigured by system
3. 2 3.2 (00) configured by system 4. 3 3.3 (00) configured by system
5. 4 3.4 (00) configured by system 6. 5 3.5 (00) deconfigured by system
7. 6 3.6 (00) configured by system 8. 7 3.7 (00) configured by system
98. return to previous menu 0]
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. the default is enabled.
to enable or disable processor hot sparing, use option 78. the default is enabled.
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.
the processor numbering scheme used by the service processor is different from the numbering scheme used by aix. to ensure that the correct processor is selected, consult the aix documentation before configuring or deconfiguring a processor.
to determine the number of processors available to aix, run the following command on the aix command line: bindprocessor -q
8 memory configuration/deconfiguration menu
enable/disable memory repeat gard
memory repeat gard partially or fully deconfigures a memory book automatically during a system boot if a memory book has failed bist post, 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 book is replaced.
memory repeat gard is enabled by default.
for more information, see “configuring and deconfiguring processors or memory” on page 55.
runtime recoverable error repeat gard
runtime recoverable error repeat gard 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 half-book or book in which the error occurred will be taken offline.
runtime recoverabe error repeat gard is disabled by default.
these menus allow the user to change the system memory configuration. if it is necessary to take one of the memory books partially or completely offline, this menu allows you to deconfigure a book, and then reconfigure the book at a later time. this menu also allows you to see if the repeat gard function has partially or completely deconfigured a memory book.
when this option is selected, a menu displays. the following is an example of this menu:
memory configuration/deconfiguration menu
77. enable/disable memory repeat gard: currently enabled
78. runtime recoverable error repeat gard: currently enabled
1. memory card
98. return to previous menu
after you select the memory card option by entering 1, a menu displays, allowing the selection of a memory book. the following is an example of this menu.
memory configuration/deconfiguration menu
1: 16.16(00, -) configured by system 2: 17.17(00, -) configured by system
3: 18.18(00, -) configured by system 4: 19.19(00, 1) partially deconfigured by system
98. return to previous 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/book number
column 2
xx.xx : book address used by service processor
column 3
(00, -) error/deconfiguration status
the error status of the each memory book is indicated by (ab, -1) 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.
an error status of (00, -) (for example, 11.16(00, -)) indicates that the memory book 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 book is fully configured. a zero or a one indicates that memory repeat gard has deconfigured half of the memory book. if this occurs, the status of the book in the menu is shown as “partially deconfigured by system.”
to change the memory configuration, select the number of the memory book. the memory book state will change from configured to deconfigured or from deconfigured to configured.
this menu only allows the deconfiguration of an entire book; it does not allow the manual deconfiguration of half a book. if half a book has been configured by the sytem (“partially deconfigured”), it can be manually reconfigured using this menu.
in the previous example menu, each line shows two books and indicates whether they are configured, deconfigured, or partially deconfigured.
to enable or disable memory repeat gard, use menu option 77 of the memory configuration/deconfiguration menu. the default is enabled.
to enable or disable runtime recoverable error repeat gard, use option 78 of the memory configuration/deconfiguration menu. the default is enabled.
the failure history of each book is retained. if a book 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 book is taken offline again because of its history of failures.
the four inner memory books, if present, are listed first, followed by the four outer books, if present. the memory books are shown in the following order of physical location code:
1 u1.18-p1-m2
2 u1.18-p1-m3
3 u1.18-p1-m7
4 u1.18-p1-m6
5 u1.18-p1-m4
6 u1.18-p1-m8
7 u1.18-p1-m5
8 u1.18-p1-m1
9 power control network utilities menu power control network utilities menu
1. lamp test for all operator panels
2. display i/o type
not supported
3. change i/o type
98. return to previous menu
0]
– 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.
– change i/o type
use this option to change the i/o type of the primary i/o book 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:
- for the i/o drawer address, type 1.
- for the i/o type, type 98.
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 processor subsystem disturbance or 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 available only when the system is in the error state (the cec 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:
led control menu
1. set/reset identify led state
2. clear system attention indicator
98. return to previous menu 0 ]
the processor subsystem disturbance or system attention led is located on the operator panel in the media drawer. the i/o drawer fault/identify led is located on the front of each i/o subsystem.
if option 1 is selected, a list of location codes of the i/o subsystems and the cec drawer displays. the screen will be similar to the following:
1. u1.9-p1
2. u1.9-p2
3. u1.5-p1
4. u1.5-p2
5. u1.1-p1
6. u1.1-p2
7. u2.1-p1
8. u2.1-p2
9. u2.5-p1
10. u2.5-p2
enter number corresponding to the location code, or press return to continue, or ’x’ to return to the menu.
0]4
if one of the devices is selected using the index number, the present state of its led will be displayed, and you are given the option to toggle it, as shown in the following screen. the final state of the led will then be displayed, whether or not it was changed.
u1.5-p2 is currently in the off state
select from the following (1=identify on, 2=identify off) 0]2 please wait...
u1.5-p2 is currently in the off state (press return to continue)
option 2, clear system attention indicator, will clear the attention indicator on the operator panel in the media drawer.
11 mcm/l3 interposer plug count menu
attention: do not power on the system when in this menu. fully eixt this menu before powering on the system.
this menu tracks the number of times that the mcm(s) and l3 cache modules have been plugged into the system backplane.
if an mcm or l3 cache module is replaced the plug count for tha 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 an 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 inclueded with the new or replacement module, enter the default value of 7. if the plug count is not entered, a b1xx 4698 error code, with a detail value of e10b or e10c, will be posted in the service processor error log.
if the primary i/o book is replaced, the plug counts are retained. however the plug count menu must be accessed and option 50, 2commit the values and write to the vpd,2 must be executed so that the plug counts are revalidated if the counts are not revalidated, a b1xx 4698 error code, with a detail value of e10b or e10c, will be posted in the service processor error log.
1. the plug count will be zero for those positions in which l3 cache modules and mcms have never been installed.
2. if mcm and l3 modules are removed from the system and not replaced, those plug counts are retained until they are manually changed.
a screen similar to the following will be displayed. in this example, all four mcms and all 16 l3 modules are shown.
mcm/l3 interposer plug count menu
1. l3_13:7 2. l3_0:7 3. mcm_0:7 4. l3_1:7 5. l3_4:7
6. l3_14:7 7. l3_3:7 8. l3_2:7 9. l3_7:7
10. mcm_3:1 11. mcm_2:1
12. l3_15:7 13. l3_10:7 14. mcm_1:7 15. l3_11:7 16. l3_6:7
17. l3_12:7 18. l3_9:7 19. l3_8:7 20. l3_5:7
50. commit the values and write to the vpd
98. return to previous menu
the format of the preceding menu entries is the menu index number, followed by l3_xx, followed by the plug count after the colon. the following table correlates the preceding information with the physical location codes.
to change the plug count for a particular module, enter a menu index number. for example, to change the plug count of the l3 module that is physically in the upper-right corner (u1.18-p1-c8), type 5, 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 stores the new values in nvram.
12 performance mode setup menu
if certain types of processor cards are installed in the system, this menu is 2not applicable.2 for other types of processor cards, this menu will be active after the first boot as noted below.
the first time the system is booted after nvram is cleared, 2not applicable2 will display under 2performance mode setup menu2 on the screen. this may also happen if the service processor is replaced, or the processor mcms are upgraded.
if option 12 is selected when 2not applicable2 is on the screen, the system will respond with 2not applicable2 and redisplay the system information menu. the setup menu can be displayed after the performance mode is set, which happens the first time the system is booted.
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 performance mode setup menu. the performance mode setup menu will be similar to the following:
default performance mode: large commercial system optimization
1. current performance mode:
large commercial system optimization
98. return to previous menu 0]1
selecting option 1 displays the following performance modes:
select from the following options:
1. large commercial system optimization
2. standard operation
3. turbo database mode 0]
1. some mcm configuration changes, such as going from an 8-way to a 24-way system, will cause the default performance mode to change. this new setting will not be 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.
to override the default setting, a brief description of each performance mode follows:
1 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 best performance for most applications.
2 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.
3 turbo database mode optimizes system operation for environments where there is a large amount of data sharing among processes running concurrently on the system.