Eserver Management

8/2/2019 Eserver Management

1/50

Managing your server using the Advanced SystemManagement Interface

ERserver


2/50


3/50


ERserver


4/50

NoteBefore using this information and the product it supports, read the information in Notices, onpage 35 and the manual IBM eServer Safety Information, G229-9054.

Sixth Edition (August 2005)

Copyright International Business Machines Corporation 2004, 2005. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/50

Contents

Managing your server using theAdvanced System Management Interface 1

Printable PDF . . . . . . . . . . . . . . 1Viewing system information . . . . . . . . . 1

Viewing vital product data . . . . . . . . 2Viewing persistent storage . . . . . . . . . 2Viewing system power control network trace . . 2Viewing progress indicator from previousboot . . 3Viewing progress indicator history . . . . . . 3Viewing real-time progress indicator . . . . . 3

Controlling the system power . . . . . . . . 4Powering the system on and off . . . . . . . 4Setting auto-power restart . . . . . . . . . 5Performing an immediate power off . . . . . 6Performing a system reboot . . . . . . . . 6Setting wake-on LAN . . . . . . . . . . 6

Changing system configuration . . . . . . . . 7Changing system name . . . . . . . . . . 7Changing the processing unit identifier . . . . 7Configuring I/O enclosures . . . . . . . . 8Changing the time of day . . . . . . . . . 9Changing firmware update policy . . . . . . 9

Updating firmware on an IBM eServer p5server . . . . . . . . . . . . . . 10Updating firmware on an IBM eServer i5server . . . . . . . . . . . . . . 10

Enabling PCI error injection policy . . . . . 10Configuring monitoring . . . . . . . . . 10Disconnecting an HMC . . . . . . . . . 11Changing the interposer plug count . . . . . 11

Changing the number of HSL OpticonnectConnections . . . . . . . . . . . . . 12Enabling I/O adapter memory allocation . . . 12Deconfiguring hardware . . . . . . . . . 13

Setting deconfiguration policies. . . . . . 13Changing processor configuration . . . . . 13Changing memory configuration . . . . . 14Clearing all deconfiguration errors. . . . . 15

Programming vital product data . . . . . . 15Setting the systembrand . . . . . . . . 15Setting the system identifiers . . . . . . 16Setting the system enclosure type . . . . . 16

Changing service indicators . . . . . . . . 17Turning off system attention indicator . . . 17Enabling enclosure indicators . . . . . . 17

Changing indicatorsby location code. . . . 18Performing an LED test on the control panel 18

Setting performance options . . . . . . . . . 19Changing the logical memoryblock size. . . . 19Enabling cache locking mode . . . . . . . 19

Configuring network services . . . . . . . . 20Configuring network interfaces . . . . . . . 20Configuring network access . . . . . . . . 20Using extended services . . . . . . . . . 21Debugging virtual TTY . . . . . . . . . 21

Using on-demand utilities . . . . . . . . . 22Order Capacity on Demand . . . . . . . . 22Activate Capacity on Demand . . . . . . . 23Resume server firmware after CoD activation . . 23Use Capacity on Demand commands. . . . . 23

Using concurrent maintenance utilities . . . . . 24

Controlling power to IDE devices . . . . . . 24Preparing the control panel . . . . . . . . 24Troubleshooting the server using service aids . . . 25

Displaying error and event logs . . . . . . 25Enabling serial port snoop . . . . . . . . 26Initiating a system dump . . . . . . . . . 26Initiating a service processor dump . . . . . 28Initiating a partition dump . . . . . . . . 28Configuring a system port for call options . . . 29Configuring your modem . . . . . . . . 29Configuring the call-home and call-in policy . . 30Testing the call-home policy . . . . . . . . 31Rebooting the service processor. . . . . . . 32Restoring your server to factory settings. . . . 32

Entering service processor commands . . . . 32

Appendix. Notices . . . . . . . . . . 35Trademarks . . . . . . . . . . . . . . 36Communication statements . . . . . . . . . 36

Class A Notices - Federal CommunicationsCommission (FCC) statement . . . . . . . 36Class B Notices - Federal CommunicationsCommission (FCC) statement . . . . . . . 39

Terms and conditions . . . . . . . . . . . 41Product recycling and disposal . . . . . . . . 41Battery return program . . . . . . . . . . 42IBM Cryptographic Coprocessor Card ReturnProgram . . . . . . . . . . . . . . . 42

Copyright IBM Corp. 2004, 2005 iii


6/50

iv Managing your server using the Advanced System Management Interface


7/50


The Advanced System Management Interface (ASMI) is the interface to the service processor that allowsyou to set flags that affect the operation of the server, such as auto power restart, and to viewinformation about the server, such as the error log and vital product data.

This interface is accessible using a Webbrowser on a client system that is connected to the serviceprocessor on an Ethernet network. It can alsobe accessed using a terminal attached to a serial port on theserver. The service processor and the ASMI are standard on all IBM eServer i5 and eServer p5 servers.

You maybe able to use the service processors default settings. In that case, accessing the ASMI is notnecessary.

The following list contains ASMI concepts and tasks that canbe performed using the ASMI if you havesuccessfully logged in with the requisite authority level (for additional details, see ASMI authority levels):

Printable PDF

Print a PDF (Portable Document Format) version of this topic and save it to your workstation.

To view or download the PDF version of this document, select Managing your server using AdvancedSystem Management Interface (about 250 KB).

You can view or download the related topic Managing the Advanced System Management Interface(about 136 KB).

Saving PDF files

To save a PDF file on your workstation for viewing or printing:1. Right-click the PDF in yourbrowser (right-click the link to the topic).

2. Click Save Target As... if you are using Internet Explorer. Click Save Link As... if you are usingNetscape Communicator.

3. Navigate to the directory in which you want to save the PDF file.

4. Click Save.

Downloading Adobe Reader

You need Adobe Reader to view or print these PDFs. You can download a copy from the Adobe Web site

(http://www.adobe.com/products/acrobat/readstep.html) .

Viewing system information

View system power control network (SPCN) trace data, progress indicator history, and vital product data(VPD).

This ASMI option provides access to vital product data (VPD) and system power control network (SPCN)trace data:

Copyright IBM Corp. 2004, 2005 1
http://../iphby/asmiauthority.htmhttp://../iphby/asmiauthority.htmhttp://../iphby/asmiauthority.htmhttp://iphbp.pdf/http://iphbp.pdf/http://iphbp.pdf/http://iphbp.pdf/http://iphbp.pdf/http://iphbp.pdf/http://iphbp.pdf/http://iphbp.pdf/http://../iphby/iphby.pdfhttp://../iphby/iphby.pdfhttp://../iphby/iphby.pdfhttp://../iphby/iphby.pdfhttp://www.adobe.com/products/acrobat/readstep.htmlhttp://www.adobe.com/products/acrobat/readstep.htmlhttp://www.adobe.com/products/acrobat/readstep.htmlhttp://../iphby/iphby.pdfhttp://iphbp.pdf/http://iphbp.pdf/http://../iphby/asmiauthority.htm


8/50

Viewing vital product dataDisplays selected or all manufacturers VPD, such as serial numbers and part numbers.

You can view manufacturers vital product data (VPD) stored from the systemboot prior to the one inprogress now.

To perform this operation, your authority level must be one of the following:v General

v Administrator

v Authorized service provider

To view the VPD, do the following:

1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.

2. In the navigation area, expand System Information and select Vital Product Data.

3. A list of field replaceable units (FRUs) that exist on the system and their descriptions are displayed.Select a single FRU or multiple FRUs from this list that you would like to view.

4. Click Display Details to display the details for selected FRUs, or click Display all details to display

details for all VPD entries.

Viewing persistent storageDisplays the contents of the registry.

You can gather additional debug information from a failing systemby viewing the contents of theregistry. The term registry key can refer to either the key part of a registry entry or the entire registryentry, depending on the context. The registry key hierarchy and the contents of any key canbe viewed in

both ASCII and hexadecimal formats.

Each registry entry is identified by a two-part key. The first part is the component name, and the secondpart is the name of the key. For example, the TerminalSize key of the esw_menu component is identifiedas menu/TerminalSize. Each registry key also has a value, which is up to 255bytes of binary data.

To view persistent storage, your authority level must be authorized service provider.

To view the component names of the contents of the registry, do the following:


2. In the navigation area, expand System Information and select Persistent Storage.

3. Click the component names to view a list of registry entries.

4. Click the desired registry entry to view the contents of a registry entry.

Viewing system power control network traceDisplays SPCN trace data that was dumped from the processor subsystem or server drawer.

You can dump the system power control network (SPCN) trace data from the processor subsystem, orserver drawer, to gather additional debug information. Producing a trace may take an extended period oftime based on your system type and configuration. This delay is due to the amount of time the systemrequires to query the data.

Note: Due to the amount of time required to produce a trace, select this option only if it is recommendedby an authorized service provider.

To perform this operation, your authority level must be one of the following:

2 Managing your server using the Advanced System Management Interface


9/50

v Administrator


To view this trace data, do the following:


2. In the navigation area, expand System Information and select System Power Control Network Trace.

Trace data is displayed as a single contiguous image in two columns.3. View the rawbinary data on the left and an ASCII translation on the right.

Viewing progress indicator from previous bootDisplays the boot progress indicator from the previous systemboot.

You can view the progress indicator that displayed in the control panel during the previous failed boot.During a successful boot, the previous progress indicator is cleared. If this option is selected after asuccessful boot, nothing displays.


v General

v Administratorv Authorized service provider

The progress indicator information is stored in nonvolatile memory. If the system is powered off usingthe power-onbutton on the control panel, this information is retained. If the ac power is disconnectedfrom the system, this information is lost.

To view the progress indicator from the previousboot, do the following:


2. In the navigation area, expand System Information.

3. Select Previous Boot Progress Indicator. The results are displayed in the right pane.

Viewing progress indicator historyDisplays progress codes that were shown on the control panel display.

You can view progress codes that appeared in the control panel display during the last boot. The codesdisplay in reverse chronological order.


v General

v Administrator


To view the progress indicator history, do the following:1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.


3. Select Progress Indicator History.

4. Select the desired progress indicator to view additional details and click Show Details. The progressindicator codes are listed from top (latest) tobottom (earliest).

Viewing real-time progress indicatorDisplays progress codes that currently show on the control panel display.

Managing your server using the Advanced System Management Interface 3


10/50

You can view the progress and error codes that currently display on the control panel. Viewing progressand error codes is useful when diagnosingboot-related issues.


v General

v Administrator

v

Authorized service provider

To view the progress indicator, do the following:



3. Select Real-time Progress Indicator to display a small box that contains the current progress and errorcodes. If no value is currently on the control panel, the small box is displayed but remains empty.

Controlling the system power

Manually and automatically control the system power.

This topic provides information on how to use the ASMI to manually and automatically control thesystem power:

Powering the system on and offView and customize various initial program load (IPL) parameters.

You can start and shut down the system in addition to setting IPL options.

To perform these operations, your authority level must be one of the following:

v Administrator


Several IPL options that you can set pertain to the server firmware. Firmware is an integral part of theserver that is stored in flash memory, whose contents are preserved when the system is powered off. Thefirmware is code that automatically starts when the server is turned on. Its main purpose is to bring theserver to a state where it is ready to operate, which means the server is ready to install orboot anoperating system. Firmware also enables the handling of exception conditions in the hardware andprovides extensions to the functions of the server hardware platform. You can view the servers currentfirmware level on the ASMI Welcome pane.

This server has a permanent firmware boot side, or P side, and a temporary firmware boot side, or Tside. When updating the firmware, new levels of firmware should be installed on the temporary side firstto test the compatibility with your applications. When the new level of firmware hasbeen approved, itcanbe copied to the permanent side.

To view and change IPL settings, perform the following steps:1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.

2. In the navigation area, expand Power/Restart Control and select Power On/Off System.

3. Set the following desired boot settings.

System boot speedSelect the speed for the next boot: Fast or Slow. Fast boot results in skipped diagnostic testsand shorter memory tests during the boot.



11/50

Firmware boot side for next bootSelect the side from which the firmware boots the next time: Permanent or Temporary.Firmware updates should be tested bybooting from the temporary side before being copiedinto the permanent side.

System operating modeSelect the operating mode: Manual or Normal. Manual mode overrides various automatic

power-on functions, such as auto-power restart, and enables the powerbutton.AIX/Linux partition mode boot

Select the stopping point during the boot process. This option is applicable only to pSeries

servers, and is available only if the system is not managed by the HMC. Service mode bootfrom saved list is the preferred way to run online AIX diagnostics. Service mode boot fromdefault list is the preferred way to run stand-alone AIX diagnostics.

This option is applicable only when the managed system is using the manufacturing defaultconfiguration, which is the initial partition setup as received from your service provider.When the system is not using the manufacturing default configuration, any changes to thisoption do not take effect. However, when the system is using the manufacturing defaultconfiguration, you can change the setting for the next restart by changing this option.

Boot to server firmware

Select the state for the server firmware: Standby or Running. When the server is in the serverfirmware standby state, partitions canbe set up and activated.

System power off policySelect the system power off policy. The system power off policy flag is a system parameterthat controls the systemsbehavior when the last partition (or the only partition in the case ofa system that is not managed by an HMC) is powered off.

i5/OS partition mode bootSelect the i5/OS partition mode for next systemboot. This option is available only when thesystem is not managed by the HMC.

4. Perform one of the following steps:

v Click Save settings to save the selected options. The power state does not change.

v Click Save settings and power on/off. All selected options are saved and the system turns on oroff. The power-on option is available only if the system is powered off. The power-off option isavailable only if the system is powered on.

v Click Save settings and continue server firmware boot to save the selected options, and turn theserver firmware on or off. This option is available only if the server firmware is in standby mode.

Setting auto-power restartEnable or disable the function that automatically restarts the system.

You can set your system to automatically restart. This function is useful when power hasbeen restoredand anybackup power supply has recharged after a temporary power failure or after an unexpectedpower line disturbance that caused the system to shut down unexpectedly. Auto-power restart will only

work if the system operating mode is set to normal; this setting is made on the power on/off menuunder the power\restart control menu on the ASMI.


v Administrator


To set the auto-power restart function, do the following:




12/50

2. In the navigation area, expand Power/Restart Control and select Auto Power Restart.

3. Select either Enable or Disable from the selection list. By default, the state for auto-power restart isDisable.

4. Click Save settings to save the selected options.

Performing an immediate power off

Power the system off immediately.

You can power off your system fasterby using the immediate power off option. Typically, this option isused when an emergency power off is needed. The operating system is not notified before the system ispowered off.

Attention: To avoid experiencing data loss and a longer IPL the next time the system or logicalpartitions are booted, shut down the operating system prior to performing an immediate power off.


v Administrator


To perform an immediate power off, do the following:


2. In the navigation area, expand Power/Restart Control and select Immediate Power Off.

3. Click Continue to perform the operation.

Performing a system rebootReboot your system without a complete system shutdown.

You can reboot the system.

Attention: Rebooting the system immediately shuts down all partitions.


v Administrator


To perform a system reboot, do the following:


2. In the navigation area, expand Power/Restart Control and select System Reboot.

3. Click Continue to perform the operation.

Setting wake-on LAN

Enable or disable the function that powers the system on remotely through a local area network (LAN)connection.

You can power on the system remotely through a local area network (LAN) connection.

Note: Wake-on LAN is supported on Ethernet port 0. It is not supported on Ethernet port 1.


v Administrator




13/50

To enable or disable wake-on LAN, do the following:


2. In the navigation area, expand Power/Restart Control and select Wake-on LAN.

3. Select either Enable or Disable from the selection list. By default, the state for wake-on LAN isDisable.

4. Click Save settings to save the selected options.

Changing system configuration

View and perform custom system configurations, such as enabling PCI (Peripheral ComponentInterconnect) error injection policies, viewing system identification information, and changing memoryconfiguration.

This topic provides instructions that should be used to view and perform custom system configurations:

Changing system nameChange the name of the system.

You can change the name that is used to identify the system. This name helps your support team (forexample, your system administrator, network administrator, or authorized service provider) to morequickly identify the location, configuration, and history of your server.


v Administrator


The system name is initialized to the 31-character value Server-tttt-mmm-SNooooooo, where thesubstitution characters mean the following:

Characters Description

tttt Machine typemmm Model number

ooooooo Serial number

The system name canbe changed to any valid ASCII string. It does not have to follow the initializedformat.

To change the system name, do the following:

1. In the navigation area, expand System Configuration.

2. Select System Name.

3. Enter the desired system name using the previous naming convention.

4. Click Save settings to update the system name to the new value.

The new system name is displayed in the status frame, the area where the logout button is located. Ifanother method, such as the HMC, is used to change the system name, the status frame does not reflectthe change.

Changing the processing unit identifierChange the processing unit ID, also referred to as the processing unit system power control network(SPCN) ID.



14/50

You can change the processing unit identifier, also referred to as the processing unit SPCN (system powercontrol network) ID. The processing unit SPCN ID is used by the SPCN firmware to identify the systemtype. It is also used to identify the primary service processor if there are two service processors in thesystem.


v Administrator


Note: This feature is available only when the system is powered off. This operation resets the serviceprocessor.

To change the processing unit identifier, do the following:



3. Select Processing Unit Identifier.

4. Enter the desired information into the 2-character text area. Supported processing unit identifiers areshown in the following table:

Model or expansion unit Processing unit identifier

OpenPower 710 BA

285 C1

OpenPower 720 BB

510 BA

520 B4

550 B5

570 B2

570 (with one or more secondary units) B3

575 B9590 and 0595 B1

5074 and 5079 81

5088 and 0588 89

5094 and 5294 8A

0595 and 5095 8B

5790 88

7311-D10 88

7311-D11 88

7311-D20 8C

5. Click Save settings to complete the operation.

Configuring I/O enclosuresView and change various enclosure attributes.

After the server firmware has reached the standby state, you can configure I/O enclosure attributes asfollows:

v List the status, location code, rack address, unit address, power control network identifier, and themachine type and model of each enclosure in the system.



15/50

v Change the identification indicator state on each enclosure to identify or off.

v Update the power control network identifier, enclosure serial number, and the machine type and modelof each enclosure.

v Change the identification indicator state of the SPCN firmware in a enclosure to Enable or Disable.

v Remove rack and unit addresses for all inactive enclosures in the system.

To perform this operation, your authority level must be one of the following:v Administrator


To configure I/O enclosures, do the following:


2. In the navigation area, expand System Configuration and select Configure I/O Enclosures.

3. Select the enclosure and the desired operation. If you select Change settings, click Save setting tocomplete the operation.

Changing the time of day

Display and change the time and date stored by the system.

You can display and change the systems current date and time. The date and time can only be changedwhen the system is powered off. The time is stored as UTC (Coordinated Universal Time), formerlyexpressed as Greenwich mean time (GMT).


v Administrator


Note: You can change the time of day only when the system is powered off.

To change the time of day, do the following:1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.


3. Select Time of Day. If the system is powered off, the right pane displays a form that shows thecurrent date (month, day, and year) and time (hours, minutes, seconds).

4. Change either the date value or the time value or both, and click Update Time Of Day.

Changing firmware update policyConfigure your system to only allow firmware updates from the selected source.

Note: These options are only valid if your server is managed by an HMC, otherwise the default sourcefor installing firmware updates is the operating system and setting the source using this method is

ignored by the server.

You can change the source for firmware updates. For example, if you choose the Hardware ManagementConsole (HMC) as the source for a firmware update, the HMC must be used to perform the update. TheHMC performs all tasks to update the server firmware.

Firmware updates canbe initiated from the Hardware Management Console (HMC) or the operatingsystem on your IBM eServer i5 server.



16/50

Updating firmware on an IBM eServer p5 server

If your server has an HMC attached, the firmware update can only be performed from the HMC. Thefirmware update must be initiated from the HMC concurrently (while the system is running), but theupdate will not be applied until the server is rebooted. If your server does not have an HMC attached,the firmware update must be performed from the operating system. The system reboots immediately toapply the update.

Firmware updates for IBM eServer p5 servers are available on the Web. For more information, see Gettingfixes in the Service and support topic.

Updating firmware on an IBM eServer i5 server

On an IBM eServer i5 server, a firmware update canbe initiated from either the HMC or the operatingsystem. Firmware updates for IBM eServer i5 servers are delivered by the program temporary fix (PTF)process. For more information, see Getting fixes in the Service and support topic.


v Administrator

v

Authorized service providerTo change the firmware update policy, do the following:



3. Select Firmware Update Policy.

4. Select the appropriate source from the selection list.

5. Click Save settings to complete the operation.

Enabling PCI error injection policyChange the PCI error injection policy that forces errors tobe injected to PCI cards.

You can enable or disable the injection of errors on the PCIbus. For example, independent softwarevendors who develop device drivers can inject errors to test the error handling code in the device driver.


v Administrator


Note: To inject errors, you will need special hardware in addition to having advanced PCIbusknowledge.

To enable or disable the PCI error injection policy, do the following:



3. Select PCI Error Injection Policy.

4. In the right pane, select Enabled or Disabled.

5. Click Save settings.

Configuring monitoringConfigure the server firmware, HMC, and service processor connection monitoring.

http://../ipha5/fixes.htmhttp://../ipha5/fixes.htmhttp://../ipha5/fixes.htmhttp://../ipha5/fixes.htmhttp://../ipha5/fixes.htmhttp://../ipha5/fixes.htmhttp://../ipha5/fixes.htm


17/50

You can configure your service processor to monitor the system and the system to monitor the serviceprocessor. By enabling the various monitoring options, the service processor can ensure that criticalsystem components are functioning while the system is in the Power off, IPL, and Running states.

To configure monitoring, your authority level must be an authorized service provider.

Monitoring is accomplished by periodic samplings called heartbeats, which can detect a service processor,

HMC, or server firmware connection failure. For example, if the service processor connection monitoringis enabled, each service processor monitors redundant service processor communication to keep track ofthe status of the other service processor. When the service processor detects no heartbeat from the otherservice processor, the heartbeat-initiating service processor logs an error due to this communicationfailure. If this condition persists, the service processor leaves the machine powered on, logs an error, andperforms recovery.

To configure monitoring, do the following:



3. Select Monitoring.

4. Select Enabled or Disabled for the server firmware, service processor connection monitoring, andHMC. All connection monitoring fields are enabled by default.

5. Click Save settings. Monitoring does not take effect until the next time the operating system isstarted.

Disconnecting an HMCDisplay and disconnect HMCs connected to the managed system.

You can display and disconnect HMCs connected to the managed system. By default, HMC connectiondata expires on the managed system after 14 days of disconnection from the HMC. If you want toperform a task that requires all HMCs tobe disconnected from the managed system, you can remove theHMC connection data prior to the 14-day period.

To disconnect an HMC, your authority level must be an authorized service provider.

To disconnect an HMC, do the following:



3. Select HMC Connections.

4. Select the desired HMC.


Changing the interposer plug countView and change the multiple chip module (MCM) interposer plug count.

You can track the number of times that a multiple chip module (MCM) hasbeen replaced or reseated ona given interposer. This interposer plug count provides you with information needed to prevent fieldproblems due to damaged or overused interposers. You can use the ASMI to view and alter theinterposer plug count for all MCMs in the system. Whenever a service action is performed on a systemthat requires the replacement or reseating of an MCM, service personnel are responsible for updating theplug count for that interposer.



18/50

Note: The Interposer Plug Count option is supported only on certain system types and models. If yourserver does not support this option and you select this option from the menu, the firmware returnsa message indicating that this option is not applicable to your system.

To perform this operation, your authority level must be authorized service provider.

To view and modify the interposer plug count, do the following:

1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.2. In the navigation area, expand System Configuration.

3. Select Interposer Plug Count. The current plug count is displayed in the text edit field for each MCMinterposer. Each interposer is identified by location code.

4. Type a new value into the text field to change the plug count.

5. Click Save settings. A report page displays the new value.

Changing the number of HSL Opticonnect ConnectionsView and change the maximum number of Highspeed Link (HSL) Opticonnect Connections allowed foryour system.

Note: The HSL Opticonnect Connections option is supported only on iSeries

hardware.


v Administrator


To change the number of HSL Opticonnect Connections, do the following:



3. Select HSL Opticonnect Connections. The current number of HSL Opticonnect Connections for thesystem is displayed.

4. Type a new value into the Custom text field, or to permit the system to automatically determine themaximum number of HSL Opticonnect Connections allowed for the system, select Automatic.


Enabling I/O adapter memory allocationIncrease the amount of PCI memory space allocated to specified PCI slots.

You can increase the amount of I/O adapter memory for specified PCI slots. When the I/O AdapterEnlarged Capacity option is enabled, specific PCI slots receive the largest memory-mapped addressspaces that are available.


v Administratorv Authorized service provider

To enable or disable I/O adapter memory allocation, do the following:



3. Select I/O Adapter Enlarged Capacity.





19/50

Deconfiguring hardwareSet deconfiguration policies, change processor configuration, change memory configuration, and clear alldeconfiguration errors.

Setting deconfiguration policiesSet various processor and memory configuration and deconfiguration policies.

You can set various policies to deconfigure processors and memory in certain situations. You can enablepolicies that will deconfigure the processor when failures occur, such as a predictive failure (for example,correctable errors generated by a processor exceeding the threshold), floating point failure, functionalfailure, or systembus failure.


v General

v Administrator


To set deconfiguration policies, do the following:

1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.2. In the navigation area, expand System Configuration and Hardware Deconfiguration.

3. Select Deconfiguration Policies.

4. In the right pane, select Enabled or Disabled for each policy.


Changing processor configurationDisplay data for each processor. You can change the state of each processor.

All processor failures that stop the system, even if intermittent, are reported to the authorized serviceprovider as a diagnostic call out for service repair. To prevent the recurrence of intermittent problems andimprove the availability of the system until a scheduled maintenance window, processors with a failure

history are marked deconfigured to prevent them from being configured on subsequent boots.

A processor is marked deconfigured under the following circumstances:

v A processor fails abuilt-in self-test or power-on self-test testing duringboot (as determined by theservice processor).

v A processor causes a machine check or check stop during run time, and the failure canbe isolatedspecifically to that processor (as determined by the processor run-time diagnostics in the serviceprocessor firmware).

v A processor reaches a threshold of recovered failures that results in a predictive call to service (asdetermined by the processor run-time diagnostics in the service processor firmware).

During system start time, the service processor does not configure processors that are marked

deconfigured. The deconfigured processors are omitted from the hardware configuration. The processorremains offline for subsequent reboots until it is replaced or the deconfiguration policy is disabled. Thedeconfiguration policy also provides the user with the option of manually deconfiguring a processor orre-enabling a previously manually-deconfigured processor.


v Administrator




20/50

Note: The state of the processor canbe changed only if the system is powered off. At run time, users canviewbut not change the state of each processor. If the deconfiguration policy is disabled, the statesof the processors cannot be changed.

To view or change the processor configuration, do the following:


2.In the navigation area, expand System Configuration and Hardware Deconfiguration.3. Select Processor Deconfiguration.

4. In the right pane, select a node from the list of nodes displayed.

5. Click Continue to change the state of each processor to configured, or deconfigured if it is not alreadydeconfigured by the system.

6. Reboot the system for the changes to take effect.

Changing memory configurationDisplay data for each memory unit (DIMM) and bank. You can change the state of eachbank.

Each memorybank contains two DIMMs (dual inline memory module). If the firmware detects a failure,or predictive failure, of a DIMM, it deconfigures the DIMM with the failure, as well as the other DIMM,

in the memorybank. If memory DIMMs are being monitored for errors, each memorybank will be inone of the following states:

v Configured by system (cs)

v Manually configured (mc)

v Deconfigured by system (ds)

v Manually deconfigured (md)

With ASMI you can change the state of the memorybank from cs to md, from mc to md, and from md tomc for one or more DIMMs. If one DIMM is deconfigured, the other DIMM in the memorybankautomatically becomes deconfigured.

Note: You can change the state of the memorybank only if the deconfiguration policy is enabled for the

memory domain. If this policy is not enabled and you try to change the state, an error message isdisplayed.

The error type is the cause of memory deconfiguration and applies to the bank in the ds state. The errortype is displayed only when the bank is in the ds state.


v Administrator


To view or change the memory configuration, do the following:


2. In the navigation area, expand System Configuration and Hardware Deconfiguration.3. Select Memory Deconfiguration.

4. In the right pane, select a node from the list of nodes displayed.

5. Click Continue to change the state of memory to configured or deconfigured, if it is not alreadydeconfigured by the system.

Note: The state of the memory canbe changed only if the system is powered off. At run time, userscan view, but not change, the state of each processor. If the deconfiguration policy function isdisabled, the state of the memory cannot be changed.



21/50

6. Click Submit. A report page is displayed, which indicates success or failure when the state of thememorybank hasbeen changed.

Clearing all deconfiguration errorsClear error records for specific or all resources in the system.

The ASMI allows you to clear error records for all or individual system hardware resources that include

the processor, memory, L2 and L3 cache, I/O hubs, service processor card, and clock card.

To clear all deconfiguration errors, your authority level must be an authorized service provider.

Note: Before performing this operation, record error messages or ensure that the error record data is nolonger needed; otherwise, you will lose all error data from the hardware resources.

To clear all deconfiguration errors, do the following:


2. In the navigation area, expand System Configuration and Hardware Deconfiguration.

3. Select Clear All Deconfiguration Errors.

4. In the right pane, select the desired hardware resource from the drop-down menu. You may select Allhardware resources or an individual resource.

5. Click Clear errors for selected hardware resource.

Programming vital product dataProgram vital product data (VPD) such as systembrand, system identifiers, and system enclosure type.

The ASMI allows you to program the system vital product data (VPD). To access any of the VPD-relatedpanels, your authority level must be administrator or authorized service provider.

Note: You cannot boot the system until valid values are entered for the systembrand, system identifiers,and system enclosure type.

Setting the system brandSet and view the systembrand.

The systembrand identifies your system using a 1-character or 2-character systembrand as shown in thefollowing table, where x is a reserved character that is provided by your service provider if it is needed.For example, your systembrand might be D or P1.

System brand Description

Dx IBM Storage

Ix IBM eServer i5

Px IBM eServer p5 and IBM eServer OpenPower

Changing the systembrand is only allowed if the value has not been set, or if the current value is Px andthe new value willbe Dx. Additionally, for IBM Storage, each of the systems that constitutes the storagefacility must be set to Dx for storage tobe accessible online.

Note: You cannot boot the system until valid values are entered for all fields. Use this procedure onlyunder the direction of your service provider.


v Administrator



22/50


To change the systembrand, complete the following steps:


2. In the navigation area, expand System Configuration and Program Vital Product Data.

3. Select System Brand. In the right pane, the current systembrand is displayed. If the systembrand has

not been set, you will be prompted to enter the systembrand. Enter the values as specified by yourservice provider.

4. Click Continue. Your system brand setting and the following notice are displayed: Attention: Onceset, this value cannot be changed unless it is Px, and then only to Dx.

5. Click Save settings to update the systembrand and save it to the VPD.

Setting the system identifiersSet the system-unique ID, system serial number, machine type, and machine model.

You can set the system-unique ID, serial number, machine type, and machine model. If you do not knowthe system-unique ID, contact your next level of support.


v Administrator


Note: You cannot boot the system until valid values are entered for all fields. You can change theseentries only once.

To set the system keywords, do the following:



3. Select System Keywords.

4. In the right pane, enter the desired values for the system serial number, machine type, and machine

model using the naming convention shown in the ASMI help. Set the Reserved field toblank spacesunless directed otherwise by service and support.

5. Click Continue. The data validation panel is displayed, which includes your entered settings.

6. Click Save settings to update the system keywords and save them to the VPD.

Setting the system enclosure typeSet values that uniquely identify the type of enclosures attached to the system.


v Administrator


Note: You cannot boot the system until valid values are entered for all fields.

To change the system enclosure type, do the following:



3. Select System Enclosures. In the right pane, the current system enclosures are displayed.

4. Enter the desired settings for the Enclosure location, Feature Code/Sequence Number, and Enclosureserial number fields using the naming convention in the ASMI help.



23/50

The value of the Enclosure serial number field must be different from the serial number of thesystem. Set the Reserved field toblank spaces unless directed otherwise by Level 4 technical support.

5. Click Save settings to update the systembrand and save it to the VPD.

Changing service indicatorsTurn off system attention indicator, enable enclosure indicators, change indicatorsby location code, and

perform an LED test on the control panel.

The service indicators alert you that the system requires attention or service. It also provides a methodfor identifying a field-replaceable unit (FRU) or a specific enclosure within the system.

A hierarchical relationship exists between FRU indicators and enclosure indicators. If any FRU indicatoris in an identify state, then the corresponding enclosure indicator will change to an identify stateautomatically. You cannot turn off the enclosure indicator until all FRU indicators within that enclosureare in an offstate.

Turning off system attention indicatorRead about the system attention indicator and how to turn it off.

The system attention indicator provides a visual signal that the system as a whole requires attention orservice. Each system has a single system attention indicator. When an event occurs that either needs yourintervention or IBM service, the system attention indicator lights continuously. The system attentionindicator is turned on when an entry is made in the service processor error log. The error entry istransmitted to the system level and operating system error logs.


v Administrator


To turn off the system attention indicator, do the following:


2. In the navigation area, expand System Configuration and Service Indicators.3. Select System Attention Indicator.

4. In the right pane, click Turn off system attention indicator. If the attempt is unsuccessful, an errormessage is displayed.

Enabling enclosure indicatorsFind out how to display and change FRU indicators within each enclosure.

You can turn on or off the identify indicators in each enclosure. An enclosure is a group of indicators. Forexample, a processing unit enclosure represents all of the indicators within the processing unit and anI/O enclosure represents all of the indicators within that I/O enclosure. Enclosures are listed by theirlocation code.


v Administrator


To enable the enclosure indicator states, do the following:


2. In the navigation area, expand System Configuration and Service Indicators.

3. Select Enclosure Indicators.



24/50

4. Select the enclosure of choice and click Continue.

5. Make the necessary changes to the selection list located next to each location code.

6. To save the changes made to the state of one or more FRU indicators, click Save settings.

To turn off all of the indicators for this enclosure, click Turn off all. A report page is displayedindicating success or failure.

Changing indicators by location codeEnter FRU indicator location code to set its LED to the identify or offstate.

You can specify the location code of any indicator to view or modify its current state. If you provide thewrong location code, the advanced system manager attempts to go to the next higher level of the locationcode.

The next level is the base-level location code for that field replaceable unit (FRU). For example, a usertypes the location code for the FRU located on the second I/O slot of the third enclosure in the system. Ifthe location code for the second I/O slot is incorrect (the FRU does not exist at this location), an attemptto set the indicator for the third enclosure is initiated. This process continues until a FRU is located or noother level is available.

To perform this operation, your authority level must be one of the following:v Administrator


To change the current state of an indicator, do the following:


2. In the navigation area, expand System Configuration and Service Indicators.

3. Select Indicators by Location code.

4. In the right pane, enter the location code of the FRU and click Continue.

5. Select the preferred state from the list.


Performing an LED test on the control panelPerform an LED test on the control panel.

You can perform an LED test on the control panel in order to determine if one of the LEDs is notfunctioning properly.


v Administrator


To perform an LED test on the control panel, do the following:

1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.2. In the navigation area, expand System Configuration and Service Indicators.

3. Select Lamp Test.

4. On the Lamp Test pane, click Continue to perform the lamp test. The test changes all indicators to theIdentify state for a short time (approximately 4 minutes).



25/50

Setting performance options

Enhance the performance of your managed systemby changing the logical memoryblock size andenabling cache locking mode.

This information describes how to enhance the performance of your managed system.

Changing the logical memory blocksizeEnhance the managed system performance by manually or automatically changing the logical memory

block size.

The system kernel uses the memoryblock size to read and write files. By default, the logical memoryblock size is set to Automatic. This setting allows the system to set the logical block memory size basedon the physical memory available. You can also manually change the logical memoryblock size.

To select a reasonable logical block size for your system, consider both the performance desired and thephysical memory size. The following are guidelines to use when selecting logical block sizes:

v On systems with a small amount of memory installed (2 GB or less), a large logical memoryblock sizeresults in the firmware consuming an excessive amount of memory. Firmware must consume at least 1

logical memoryblock. As a general rule, select the logical memoryblock size tobe no greater than1/8th the size of the systems physical memory.

v On systems with a large amount of memory installed, small logical memoryblock sizes result in alarge number of logical memoryblocks. Because each logical memoryblock must be managed during

boot, a large number of logical memoryblocks can cause boot performance problems. It isrecommended to limit the number of logical memoryblocks to 8 K or less.

Note: The logical memoryblock size canbe changed at run time, but the change does not take effectuntil the system is restarted.


v Administrator


To configure logical memoryblock size, do the following:


2. In the navigation area, expand Performance Setup.

3. Select Logical Memory Block Size.

4. In the right pane, select the logical memoryblock size and click Save settings.

Enabling cache locking modeImprove your system performance by enabling cache locking mode.

You can improve your system performance by enabling the cache locking mode. Performanceimprovements vary depending on the applications running on your system. It is recommended that youchange this setting only if advised by your service provider.


To enable or disable cache locking mode, do the following:


2. In the navigation area, expand Performance Setup.

3. Select Cache Locking Mode.



26/50



Configuring networkservices

Configure network interfaces, configure network access, and debug the virtual TTY.

This information describes how to use the ASMI to view and configure network settings:

Configuring network interfacesConfigure the number and type of network interfaces according to the needs of your system.

You can configure network interfaces on the system. The number and type of interfaces vary according tothe specific needs of your system.

Attention: This operation canbe performed when the system is powered on as well as powered off.Since network configuration changes occur immediately, existing network sessions, such as HMCconnections, are stopped. This operation should not be performed when the firmware update is inprogress. The new settings must be used to re-establish any network connections. Additional errors may

alsobe logged if the system is powered on.

You can change the network configurations when the system is in any state. When the system is turnedon, you can only view the network configurations.


v Administrator


To configure network interfaces, do the following:


2. In the navigation area, expand Network Services.

3. Select Network Configuration.

4. In the right pane, locate the interface that you want to change. Select the box corresponding to theConfigure this interface? field of the identified interface. If this box is not selected, the correspondingfield changes are ignored.

5. Select the Type of IP address from the following options:

Static The IP address, subnet mask,broadcast address, default gateway and first DNS server addressmust be entered. The second and third DNS server addresses are optional.

DynamicNo additional input is required.

6. Click Save settings tobegin data validation.

Attention: If incorrect network configuration information is entered, you may not be able to use theASMI after the changes are made. To remedy this situation, you must reset the service processor tothe default settingsby removing the service processor assembly from the server and moving the reset

jumpers. Resetting the service processor also resets all user IDs and passwords to their default values.

The next screen allows you to verify the IP settings that have been entered. Click Continue to makethe changes.

Configuring networkaccessSpecify which IP addresses will be allowed to access the server.



27/50

When you configure network access, you specify which IP addresses can access the service processor. Youcan specify a list of allowed IP addresses and a list of denied IP addresses.


v Administrator


To configure network access, do the following:



3. Select Network Access. In the right pane, the IP address field displays the IP address of the serverthat yourbrowser is running on and that connects to the ASMI.

4. Specify up to 16 addresses each for the list of allowed addresses and the list of denied addresses. ALLis a valid IP address.

If a login is received from an IP address that matches a complete or partial IP address in the allowedlist, access to the service processor is granted. Access to the service processor is not allowed if a loginis received from an IP address that matches a complete or partial IP address from the denied list.

Note: The allowed list takes priority over the denied list, and an empty denied list is ignored. ALL isnot allowed in the denied list if the allowed list is empty.

5. Click Save settings to validate the data.

Using extended servicesSpecify the IP address and directory path for remote systems.

ASMI allows you to mount a directory at a fixed mounting point on the service processor in order toenable utilities, such as telnet, ftp, and rsh. You can also clear the current mount settings. To mount adirectory, the IP addresses of the remote system and path to the directory on the remote system must beprovided. The targeted directory will be mounted at a fixed location on the host service processor. Bydefault, the mount point is /nfs.

This option is beneficial for gathering additional debug information from a failing system. To enableutilities, such as telnet, the name and relative path to a shell script on the remote system along with theIP address and path to mount the directory on the remote system must be provided. This shell script,when executed on the host service processor, enables utilities such as telnet and ftp.

To access the extended services menu, your authority level must be an authorized service provider.

To configure extended services, do the following:


2. Select Extended Services.

3. In the right pane, specify the IP address of the remote machine, directory path to mount on the

remote machine, and relative path name of the shell script you desire to execute on the remotemachine. The relative path of the shell script field is optional.

4. Click Save settings to mount the remote directory using your entered data or click Clear mount tounmount the previously mounted remote directory.

Debugging virtual TTYDebug virtual TTY from the master service processor.

You can gather additional debug information from a failing systemby using the debug virtual server(DVS). The DVS enables communication with the server firmware and partition firmware. DVS allows a



28/50

maximum of eight open connections. External interfaces such as the ASMI and service processor remoteapplication can communicate with the server firmware and partition firmware through DVS. Thiscommunication is bidirectional. External interfaces can send a message to the server firmware andpartition firmware through DVS.

DVS uses the partition ID and session ID to distinguish between the server firmware and partitionfirmware. The range forboth the partition ID and session ID is 0 to 255. Clients, such as the ASMI,

interact with DVS using a TCP/IP socket. Port 30002 on the service processor is used for thiscommunication.

Two parameters, the partition ID and the session ID, must be specified to start communicating. Afterspecifyingboth parameters, a telnet session must be opened to send messages. The telnet session must bestarted and messages must be sent within the time-out period of 15 minutes. If both actions are not takenwithin the time-out period, the connection is closed.


To debug the virtual TTY, do the following:


2. In the navigation area, expand Network Services.3. Select Debug Virtual TTY.

4. In the right pane, enter the partition and session IDs.


Using on-demand utilities

Activate inactive processors or inactive system memory without restarting your server or interruptingyour business.

Capacity on Demand (CoD) allows you to permanently activate inactive processors or inactive systemmemory without requiring you to restart your server or interrupt yourbusiness.

Note: Use this topic if a hardware failure causes the system to lose its Capacity On Demand or FunctionOn Demand purchased capabilities, and if there has never been an HMC managing the system. Ifan HMC is managing the system, use the HMC to perform the following tasks instead of theASMI.

Order Capacity on DemandGenerate the system information that is required when ordering processor or memory activation features.

After you determine that you want to permanently activate some or all of your inactive processors ormemory, you must order one or more processor or memory activation features. You then enter theresulting processor or memory-activation key that is provided by your hardware provider to activate

your inactive processors or memory.To perform this operation, your authority level must be one of the following:

v Administrator


To order processor or memory activation features, do the following:


2. In the navigation area, expand Capacity On Demand.



29/50

3. Select CoD Order Information. The server firmware displays the information that is necessary toorder a Capacity on Demand activation feature.

4. Record the information that is displayed.

5. Click Continue.

Activate Capacity on Demand

Activate processors or memory permanently with Capacity on Demand.

When you obtain processor or memory activation features, you receive an activation key that you use toactivate your inactive processors or memory.


v Administrator


To permanently activate some or all of your inactive processors or memory, do the following:



3. Select CoD Activation.

4. Enter the activation key into the field.

5. Click Continue to perform the specified operation.

Resume server firmware after CoD activationResume the booting process of the server firmware after the CoD activation keys are entered.

You can resume the server firmware after the CoD activation keys are entered. Resuming the serverfirmware causes the CoD key tobecome recognized and the hardware tobecome activated. This optionallows the server to complete the startup process that has been delayed up to one hour in order to placethe server into the On Demand Recovery state that was needed to enter the CoD activation keys.


v Administrator


To resume the server firmware, do the following:



3. Select CoD Recovery.

4. Click Continue to perform the specified operation.

Use Capacity on Demand commandsRun a command that is sent to the server firmware.

As directed by your service provider, you can run a Capacity On Demand-related command that is sentto the server firmware.


v Administrator




30/50

To run a Capacity On Demand command, do the following:



3. Select CoD Command.

4. Enter the Capacity On Demand command into the field and click Continue. The response to thecommand from the server firmware is displayed.

Using concurrent maintenance utilities

Replace devices in your server without having to power off your server.

You can replace some devices in your server without having to power off your server.

Controlling power to IDE devicesControl power to your IDE devices.

You can control power to the integrated drive electronics (IDE) devices so that you can performconcurrent maintenance. Power to IDE devices, a pair at a time, canbe turned on and off without

affecting power to the rest of the devices in the server.

Attention: To avoid damaging the hardware, turn off the power to IDE devices before performingconcurrent maintenance.


v Administrator


Note: The IDE device control menu is available only when the system is powered on.

To control power to your IDE devices, do the following:

1. On the ASMI Welcome pane, specify your user ID and password, and click Log In.2. In the navigation area, expand Concurrent Maintenance.

3. Select IDE Device Control. The location code and current power state of each IDE device isdisplayed.

4. Click Power off to remove power from the IDE devices displayed in the list. To restore power to theIDE devices displayed in the list, click Power on.

Preparing the control panelPrepare the control panel for concurrent maintenance.

You can prepare the control panel for concurrent maintenance by logically isolating the control panel. As aresult, your firmware does not recognize the control panel asbeing active and you can remove it.Performing this operation prevents your hardware frombecoming damaged while replacing the controlpanel. After a new control panel is installed, you can change the settings so that the hardware recognizesthe new control panel.


v Administrator


Note: The control panel menu is available only when the system is turned on.



31/50

For control-panel removal and replacement procedures, see Installing features and replacing parts.

To prepare the control panel for concurrent maintenance, do the following:


2. In the navigation area, expand Concurrent Maintenance.

3. Select Control Panel. You are asked to specify whether you want to remove or install the control

panel.4. Click Continue to display a list of all possible control-panel location codes.

5. Click to select the appropriate location code of the control panel.

6. Click Save settings to perform the selected operation.

Troubleshooting the server using service aids

View and customize troubleshooting information with various service aids (such as viewing error logsand initiating service processor dumps).

This topic provides information about using the following ASMI service aids.

Note: The system ports are disabled when a Hardware Management Console (HMC) is attached to theserver, and the server is booted beyond FSP standby.

Displaying error and event logsDisplay a list of all of the error and event logs in the service processor.

You can view error and event logs that are generated by various service processor firmware components.The content of these logs canbe useful in solving hardware or server firmware problems.


v General

v Administrator


Informational and error logs canbe viewed by all authority levels. Hidden error logs canbe viewed byauthorized service providers.

The following table shows error log types that might be displayed, the conditions that make an error logspecific to that error log type, and the user authority level that will allow you to view specific types oferror logs:

Error log type

Conditions

User availabilitySeverity Action

Informational logs Informational Report to operating

system (OS)but nothidden

Available to all users

Error logs Not informational Report to OS but nothidden

Available to all users

Hidden logs Not informational andinformational

Report to OS, hidden, orboth

Available only to theauthorized serviceprovider and users withhigher authority.

To view error and event logs in summary or full detailed format, do the following:

http://../iphaj/installcifcio.htmhttp://../iphaj/installcifcio.htmhttp://../iphaj/installcifcio.htmhttp://../iphaj/installcifcio.htmhttp://../iphaj/installcifcio.htm


32/50


2. In the navigation area, expand System Service Aids and click Error/Event Logs. If log entries exist, alist of error and event log entries is displayed in a summary view.

3. To view the full detail format of any of the logs listed, select the logs corresponding checkbox andclick Show details. When multiple logs are selected, any action applies to each selected log. The fulldetail information might span several pages. The contents and layout of the full detail output is

defined by the event or error logging component.4. Click Mark as reported to mark platform error entries whose underlying causes have been resolved.By doing so, these entries are not reported to the operating system again when the system reboots.After they are marked, these errors canbe overwrittenby other errors logged in the service processorhistory log.

Note: The Mark as reportedbutton is available only when your authority level is an authorizedservice provider.

Enabling serial port snoopSpecify parameters (including the snoop string) for enabling a serial port (system port) snoop.

You can disable or enable a snoop operation on a system port. When enabled, data received on theselected port is examined, or snooped, as it arrives. You can also specify the snoop string, a particularsequence ofbytes that resets the service processor if detected. The system port S1 serves as a catchallreset device.



v General

v Administrator


To view and change the current Serial Port Snoop settings, complete the following steps:


2. In the navigation area, expand System Service Aids and select Serial Port Snoop.

3. Disable or enable snooping on system port S1. The default is Disabled.

4. Enter the desired snoop string, up to 32bytes, into the Snoop string field. The current valuedisplayed is the default. Ensure that the string is not a commonly used string. A mixed-case string isrecommended.

5. Click Update snoop parameters to update the service processor with the selected values.

Note: After the snoop operation is correctly configured, at any point after the system is booted toAIX, the system uses the service processor reboot policy to restart whenever the reset string is

typed on an ASCII terminal attached to system port S1.

Initiating a system dumpControl how frequently a system dump is performed and the amount of data collected from thehardware and server firmware.

You can initiate a system dump in order to capture overall system information, system processor state,hardware scan rings, caches, and other information. This information canbe used to resolve a hardwareor server firmware problem. A system dump can alsobe automatically initiated after a system malfunction,such as a checkstop or hang. It is typically 34 MB.



33/50

Note: Use this procedure only under the direction of your service provider.


v Administrator


To configure and initiate a system dump, do the following:1. Perform a controlled shutdown of the operating system if possible.


3. In the navigation area, expand System Service Aids and click System dump.

4. From the selection list labeled Dump policy, select the policy to determine when an automatic systemdump is collected.

The dump policy is used whenever a system error condition is automatically detected by the system.In addition to the dump policy, the platform firmware determines whether a dump is recommended,

based on the type of error that has occurred. This recommendation is combined with the dump policyto determine if a system dump will be initiated.

The dump policy choices are the following:

As neededCollects the dump data only for specific reasons. This is the default setting for the dumppolicy.

AlwaysCollects the dump data after the system locks up or after a checkstop. This setting overridesthe firmware recommendation and forces a system dump, even when it is not recommended.

Note: The dump policy only defines when a system dump is performed. It does not define what todump nor the size of the information tobe dumped. Those parameters are controlled by theHardware content settings.

5. Select the policy to determine how much data to dump from the selection list labeled Hardwarecontent.

The system firmware makes a recommendation for the dump content based on the type of error thathas occurred. This recommendation is combined with the hardware content to determine how muchdump data is actually collected.

The dump policy choices available are the following:

v Automatic Collects dump data automatically. The firmware decides which dump content isbest,depending on the type of failure. This is the default setting for the hardware content.

v Minimum Collects the minimum amount of dump data. Collection of hardware dump data canbetime-consuming. This selection allows the user to minimize the content of the hardware portion ofthe system dump. It also allows the system to reboot as quickly as possible.

Note: If this option is selected, the debug data collected for some errors maybe insufficient. Thecapturing of relevant error data for some errors maybe sacrificed for less system downtime.

v Medium Collects a moderate amount of hardware error data. More data is captured with thissetting than the minimum setting, and less time is needed for dump data collection in comparisonto the maximum setting.

v Maximum Collects the maximum amount of hardware error data. This setting gives the mostcomplete error coverage but requires more system downtime in relation to the other policies. It isexpected tobe used in rare casesby authorized service providers if you are willing to sacrificereboot speed for error capture on a first failure, or if difficult problems are being analyzed.

Note: If this option is selected, the collection of hardware dump data canbe quite time-consuming,especially for systems with a large number of processors.



34/50

6. In the Server firmware content field, select the content level that indicates the amount of data todump for the server firmware portion of the system dump.

7. Click Save settings to save the setting changes.

To save the setting changes and instruct the system to immediately process a dump with the currentsettings, click Save settings and initiate dump.

For information about copying, reporting, and deleting the dump, see Managing dumps in the

Troubleshooting topic.

Initiating a service processor dumpEnable or disable the service processor dump in addition to immediately initiating a service processordump.

Use this procedure only under the direction of your hardware service provider. With this function, youcan preserve error data after a service processor application failure, external reset, or user request for aservice processor dump. The existing service processor dump is considered valid if neither the serverfirmware nor Hardware Management Console (HMC) has collected the previous failure data.


To enable or disable the service processor dump and view the status of the existing service processordump, do the following:


2. In the navigation area, expand System Service Aids and click Service Processor Dump.

3. Select either Enable or Disable from the selection list. By default, the state is Enable. The currentsetting is displayed and the status of an existing service processor dump is displayed as valid orinvalid.

Note: You cannot perform a user-requested service processor dump when this setting is disabled.


To save the setting changes and instruct the system to immediately process a service processor dump

with the current settings, click Save settings and initiate dump.For information about copying, reporting, and deleting the dump, see Managing dumps in theTroubleshooting topic.

Initiating a partition dumpEnable or disable the service processor dump in addition to immediately initiating a partition dump.

Use this procedure only under the direction of your hardware service provider. By initiating a partitiondump, you can preserve error data that canbe used to diagnose server firmware or operating systemproblems. The state of the operating system is saved on the hard disk and the partition restarts. Thisfunction canbe used when the operating system is in an abnormal wait state, or endless loop, and theretry partition dump function is not available. The retry partition dump feature is present only on iSeries

systems.

Attention: You may experience data loss when using this operation. This feature is only available onnon-HMC managed systems that have the system server firmware in the Running state.


v Administrator


To perform a partition dump, do the following:

http://../ipha5/manage_dumps.htmhttp://../ipha5/manage_dumps.htmhttp://../ipha5/manage_dumps.htmhttp://../ipha5/manage_dumps.htmhttp://../ipha5/manage_dumps.htmhttp://../ipha5/manage_dumps.htm


35/50


2. In the navigation area, expand System Service Aids and click Partition Dump.

3. Select Partition Dump. If your system is an iSeries server and the initial partition dump attemptfailed, select Retry partition dump.

Configuring a system port for call options

Configure the system port for use with the call-home and call-in options.

You can configure the system ports used with the call-home and call-in features. You can also set thebaud rate for all system ports.

Note: The system ports are disabled when a Hardware Management Console (HMC) is attached to theserver, and the server is booted beyond FSP standby. Therefore, these menus are not present if thesystem is managed by an HMC, or if the system has no ports.


v Administrator


To configure the system ports, complete the following steps:

1. In the navigation area, expand System Service Aids and click Serial Port Setup. Two sections aredisplayed. The first section is labeled S1, which is the system port that is used with the call-homefeature. The second section is labeled S2, which is the system port that is used with the call-in feature.

2. Modify the appropriate fields in the S1 and S2 sections.

Baud rateSelect the baud rate for this system port. If a terminal is attached to this port, the settingsmust match. The speeds available are 50, 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, and115200bps.

Character size

Select the character size for this system port. If a terminal is attached to this port, the settingsmust match.

Stop bitsSelect the number of stopbits for thissystem port. If a terminal is attached to this port, thesettings must match.

Parity Select the parity for thissystem port. If a terminal is attached to this port, the settings mustmatch.


Configuring your modemConfigure your modem that is connected to the system port.



v Administrator


To configure the modem, complete the following steps:




36/50

2. In the navigation area, expand System Service Aids.

3. Select Modem Configuration. Two sections are displayed. The first section is labeled S1, which is thesystem port that is used with the call-home feature.

Documents

Eserver Management