Before using this information and the product it supports, read the information in Notices and the IBM Systems Safety Information manual, G229-9054.
Safety notices may be printed throughout this guide:
Several countries require the safety information contained in product publications to be presented in their national languages. If this requirement applies to your country, a safety information booklet is included in the publications package shipped with the product. The booklet contains the safety information in your national language with references to the U.S. English source. Before using a U.S. English publication to install, operate, or service this product, you must first become familiar with the related safety information in the booklet. You should also refer to the booklet any time you do not clearly understand any safety information in the U.S. English publications.
Das Produkt ist nicht für den Einsatz an Bildschirmarbeitsplätzen im Sinne § 2 der Bildschirmarbeitsverordnung geeignet.
IBM servers can use I/O cards or features that are fiber-optic based and that utilize lasers or LEDs.
All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information.
The following comments apply to the IBM servers that have been designated as conforming to NEBS (Network Equipment-Building System) GR-1089-CORE:
The equipment is suitable for installation in the following:
The intrabuilding ports of this equipment are suitable for connection to intrabuilding or unexposed wiring or cabling only. The intrabuilding ports of this equipment must not be metallically connected to the interfaces that connect to the OSP (outside plant) or its wiring. These interfaces are designed for use as intrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection to connect these interfaces metallically to OSP wiring.
The ac-powered system does not require the use of an external surge protection device (SPD).
The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return terminal shall not be connected to the chassis or frame ground.
This unit must be recycled or discarded according to applicable local and national regulations. IBM encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is no longer needed. IBM offers a variety of product return programs and services in several countries to assist equipment owners in recycling their IT products. Information on IBM product recycling offerings can be found on IBM's Internet site at http://www.ibm.com/ibm/environment/products/prp.shtml.
Esta unidad debe reciclarse o desecharse de acuerdo con lo establecido en la normativa nacional o local aplicable. IBM recomienda a los propietarios de equipos de tecnología de la información (TI) que reciclen responsablemente sus equipos cuando éstos ya no les sean útiles. IBM dispone de una serie de programas y servicios de devolución de productos en varios países, a fin de ayudar a los propietarios de equipos a reciclar sus productos de TI. Se puede encontrar información sobre las ofertas de reciclado de productos de IBM en el sitio web de IBM http://www.ibm.com/ibm/environment/products/prp.shtml.

Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste electrical and electronic equipment (WEEE). The Directive determines the framework for the return and recycling of used appliances as applicable throughout the European Union. This label is applied to various products to indicate that the product is not to be thrown away, but rather reclaimed upon end of life per this Directive.
In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is to be collected separately and to be reused, recycled, or recovered at end of life. Users of EEE with the WEEE marking per Annex IV of the WEEE Directive, as shown above, must not dispose of end of life EEE as unsorted municipal waste, but use the collection framework available to customers for the return, recycling, and recovery of WEEE. Customer participation is important to minimize any potential effects of EEE on the environment and human health due to the potential presence of hazardous substances in EEE. For proper collection and treatment, contact your local IBM representative.
This product may contain sealed lead acid, nickel cadmium, nickel metal hydride, lithium, or lithium ion battery. Consult your user manual or service manual for specific battery information. The battery must be recycled or disposed of properly. Recycling facilities may not be available in your area. For information on disposal of batteries outside the United States, go to http://www.ibm.com/ibm/environment/products/batteryrecycle.shtml or contact your local waste disposal facility.
In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM Equipment. For information on proper disposal of these batteries, contact IBM at 1-800-426-4333. Please have the IBM part number listed on the battery available prior to your call.
For Taiwan: Please recycle batteries.

For the European Union:

Batteries or packaging for batteries are labeled in accordance with European Directive 2006/66/EC concerning batteries and accumulators and waste batteries and accumulators. The Directive determines the framework for the return and recycling of used batteries and accumulators as applicable throughout the European Union. This label is applied to various batteries to indicate that the battery is not to be thrown away, but rather reclaimed upon end of life per this Directive.
In accordance with the European Directive 2006/66/EC, batteries and accumulators are labeled to indicate that they are to be collected separately and recycled at end of life. The label on the battery may also include a chemical symbol for the metal concerned in the battery (Pb for lead, Hg for mercury and Cd for cadmium). Users of batteries and accumulators must not dispose of batteries and accumulators as unsorted municipal waste, but use the collection framework available to customers for the return, recycling, and treatment of batteries and accumulators. Customer participation is important to minimize any potential effects of batteries and accumulators on the environment and human health due to the potential presence of hazardous substances. For proper collection and treatment, contact your local IBM representative.
For California:
Perchlorate Material - special handling may apply. See www.dtsc.ca.gov/hazardouswaste/perchlorate.
The foregoing notice is provided in accordance with California Code of Regulations Title 22, Division 4.5 Chapter 33. Best Management Practices for Perchlorate Materials. This product/part may include a lithium manganese dioxide battery which contains a perchlorate substance.
The following information applies only for systems originally sold prior to July 1, 2006:
This machine may contain an optional feature, the cryptographic coprocessor card, which includes a polyurethane material that contains mercury. Please follow local ordinances or regulations for disposal of this card. IBM has established a return program for certain IBM Cryptographic Coprocessor Cards. More information can be found at http://www.ibm.com/ibm/environment/products/prp.shtml.
This document describes the primary functions that eClipz provides within the operating system.
For information about the accessibility features of this product, for users who have a physical disability, see Appendix F. Accessibility features.
Your feedback is important in helping to provide the most accurate and highest quality information. If you have any comments about this publication, send your comments using Resource Link at http://www.ibm.com/servers/resourcelink. Click Feedback on the navigation pane. Be sure to include the name of the book, the form number of the book, and the specific location of the text you are commenting on (for example, a page number or table number).
This chapter briefly describes some of the concepts and functions of the Hardware Management Console (HMC) and introduces the user interface that is used for accessing those functions.
The HMC is a system that controls managed systems, logical partitions, Capacity on Demand (CoD), and updates. To provide flexibility and availability, you can implement HMCs as a local HMC or a redundant HMC.
The IBM® 7042-C06 Desktop Hardware Management Console and the IBM 7042-CR4 Rack-Mounted Hardware Management Console provide dedicated workstations designed to allow you to configure and manage POWER5, POWER5+, and POWER6 processor-based servers. One HMC can manage multiple servers, and dual HMCs can provide redundant support by managing the same system. To help ensure consistent function for all 7042-C06 and 7042-CR4 HMC models, each HMC is shipped preloaded with the Hardware Management Console Licensed Machine Code Version 7 (#0962).
The Hardware Management Console Licensed Machine Code Version 7 (#0962) may also be ordered via MES for 7310 HMCs for environments that may include POWER5, POWER5+, and POWER6 processor-based servers. Version 7 is not available for the 7315-C03 HMCs.
This HMC uses a Web-based user interface. This interface uses a tree style navigation model providing hierarchical views of system resources and tasks using drill-down and launch-in-context techniques to enable direct access to hardware resources and task management capabilities. It provides views of system resources and provides tasks for system administration.
See Using the Web-based user interface for detailed information on how to use this HMC interface.
You also have the option of using the HMC Command Line Interface (CLI). See the Command Line Support education module (http://www.ibm.com/servers/resourcelink/lib03030.nsf/page) for information on how to use the command line interface and see Appendix D. HMC commands for descriptions of all the commands you can use to perform the HMC and server tasks.
Predefined user IDs and passwords are included with the HMC. It is imperative to your system's security that you change the hscroot predefined password immediately.
The following predefined user IDs and passwords are included with the HMC:
| User ID | Password | Purpose |
|---|---|---|
| hscroot | abc123 | The hscroot user ID and password are used to log in to the HMC for the first time. They are case-sensitive and can only be used by a member of the super administrator role. |
| root | passw0rd | The root user ID and password are used by the service provider to perform maintenance procedures. They cannot be used to log in to the HMC. |
Each HMC user can be a member of a different role. Each of these roles allows the user to access different parts of the HMC and perform different tasks on the managed system. HMC roles are either predefined or customized.
The roles discussed in this section refer to HMC users; operating systems running on logical partitions have their own set of users and roles. When you create an HMC user, you must assign that user a task role. Each task role allows the user varying levels of access to tasks available on the HMC interface. For more information about the tasks each HMC user role can perform, see Appendix A. HMC tasks and user roles/IDs.
You can assign managed systems and logical partitions to individual HMC users. This allows you to create a user that has access to managed system A but not to managed system B. Each grouping of managed resource access is called a managed resource role. To learn more about managed resource roles and how to create them, see Manage Task and Resource Roles.
The predefined HMC roles, which are the default on the HMC, are as follows:
| hmcoperator | Operator | The operator is responsible for daily system operation. |
| hmcsuperadmin | Super Administrator | The super administrator acts as the root user, or manager, of the HMC system. The super administrator has unrestricted authority to access and modify most of the HMC system. |
| hmcpe | Product Engineer | A product engineer assists in support situations, but cannot access HMC user management functions. To provide support access for your system, you must create and administer user IDs with the product engineer role. |
| hmcservicerep | Service Representative | A service representative is an employee who is at your location to install, configure, or repair the system. |
| hmcviewer | Viewer | A viewer can view HMC information, but cannot change any configuration information. |
You can create customized HMC roles by modifying predefined HMC roles. Creating customized HMC roles is useful for restricting or granting specific task privileges to a certain user. For more information about creating customized HMC roles, see Manage Task and Resource Roles.
First, turn on the HMC by setting both the display and system unit to the On position. The initialization window, which includes the copyright information, is displayed.
When initialization is complete, the pre-login window is displayed as shown in Figure 1.

To log in to the HMC, click Log on and launch the Hardware Management Console web application. from the pre-login window.
The Logon window is displayed as shown in Figure 2.

To log in, enter the user ID and password combination assigned to you. Then click Logon.
After you log in, the HMC workplace window is displayed and, if enabled, the Tip of the Day window appears. For more information, see Tip of the Day.
The HMC workplace window allows you to work with tasks for your console and managed systems. Not all tasks are available for each user ID. The user role assigned to your user ID determines what tasks you are able to perform. For example, if you are assigned a user ID with the operator role, you will have access to all the tasks that have operator access. See Appendix A. HMC tasks and user roles/IDs for a listing of all tasks and the user roles for which the tasks are available.
If at any time you do not know or remember what user ID you are currently logged in to the HMC, look at the task bar on the top of the Welcome page or you can open the HMC Management node in the navigation pane, then select the Manage Users and Tasks task from the work pane (see Manage Users and Tasks for more information).
This section highlights some of the new features and functions that can be found on the Version 7.3.1. Hardware Management Console and the POWER6 platform. You can also click HMC Readme from the HMC workplace Welcome pane for more information.
The following new Interface features include:
The new UI also provides greater flexibility in how data is represented for managed systems and partitions through the sorting and filtering functions. In addition, custom groups can be created to provide essentially any structure the administrator wishes to construct over the managed objects (servers, frames, and partitions). For more information, see Using the Web-based user interface.
The following new POWER6 specific functions include:
This information is used to aid HMC Version 6 users in locating the equivalent WebSM HMC task in the new Web-based HMC UI. Each navigation node in the WebSM UI is broken out to a table listing the location of the WebSM task on the left hand side and then indicating the new location for the task in the Web UI on the right hand side. Where possible, a non-targeted task has been moved (no object is selected to perform the task on ) to a targeted task (a objected is selected first) to help make tasks readily available. These tasks are referred to as “Targeted” tasks and are denoted with a T[S-System, P-Partition, H-HMC, U-Updates, SP-System Plan], if a target is not listed then HMC is the assumed target.
The tasks for managed system and partitions have been grouped into consistent categories for each of the object types. Instead of one long list of tasks when you select an object, there is categories of tasks to choose from. The major change in the overall Server and Partition management approach is that System Profiles and Partition Profiles are now viewed and worked with in their own separate tasks. They are no longer displayed in the container underneath a system or partition, respectively. The new task used to manage System Profiles is found by selecting a server then Configuration > Manage System Profiles and the new task used to manage Partition Profiles is found by selecting a partition then Configuration > Manage Profiles. Each of those two tasks allows you to view and work with the profiles created on the system and contain the same tasks as the WebSM UI had provided when either one of those object types were selected.
| Task Name | Task Description | New Location |
|---|---|---|
| Properties | Display and edit managed system properties | Properties |
| Reset or Remove Connection | Remove or reset the HMC connection to the managed system | Connections > Reset or Remove Connection |
| Create | ||
|
Logical Partition |
Create a logical partition | Configuration > Create Logical Partition > |
|
System Profile |
Create a system profile | Configuration > Manage System Profiles > New |
|
System Plan |
Create a system plan | Configuration > System Plans > Create |
| Manage On Demand Activations (See Manage on demand activations) | See the section below | See Manage on demand activations |
| Adapters | ||
|
GX+ |
View the properties of the GX+ adapters installed | Removed for V7.3.1.0 |
| Power On | Power on the managed system | Operations > Power On |
| Power Off | Power off the managed system | Operations > Power Off |
| Disconnect Another HMC | Removes another HMC's lock on the managed system | Connections > Disconnect Another HMC |
| Profile Data | ||
|
Restore |
Restore a profile data backup file | Configuration > Manage Profile Data > Restore |
|
Initialize |
Clear the LPAR and profile configuration on the managed system | Configuration > Manage Profile Data > Initialize |
|
Backup |
Backup the LPAR and profile configuration on the managed system | Configuration > Manage Profile Data > Backup |
|
Remove |
Remove a configuration backup file | Configuration > Manage Profile Data > Remove |
| Rebuild Managed System | Rebuild the HMC's internal representation of the managed system | Operations > Rebuild |
| Recover Partition Data | Rebuild the HMC's internal representation of the managed system | Recover Partition Data |
| Update Managed System Password | Update the HMC passwords for the managed system | Operations > Change Password |
| Workload Management Groups | View the workload management groups | Configuration > View Workload Management Groups |
| Status | FSP connection status | Connections > Service Processor Status |
| Add Managed System | Add another managed system to the HMC | Connections > Add Managed System |
| Task Name | Task Description | New Location |
|---|---|---|
| Properties | View or edit the partition properties | Properties |
| Create Profile | Create a profile for the partition | Configuration > Manage Profiles > New |
|
Add |
Add physical adapters to the partition | Dynamic Logical Partitioning > Physical Adapters > Add |
| Dynamic Logical Partitioning | ||
|
Physical Adapter Resources: |
||
|
Remove |
Remove physical adapters from the partition | Dynamic Logical Partitioning > Physical Adapters > Move/Remove |
|
Move |
Move physical adapters to another partition | Dynamic Logical Partitioning > Physical Adapters > Move/Remove |
|
Processor Resources: |
||
|
Add |
Add processors to the partition | Dynamic Logical Partitioning > Processor > Add/Remove |
|
Remove |
Remove processors to the partition | Dynamic Logical Partitioning > Processor > Add/Remove |
|
Move |
Move processors to the partition | Dynamic Logical Partitioning > Processor > Move |
|
Memory Resources: |
||
|
Add |
Add memory to the partition | Dynamic Logical Partitioning > Memory > Add/Remove |
|
Remove |
Remove memory to the partition | Dynamic Logical Partitioning > Memory > Add/Remove |
|
Move |
Move memory to the partition | Dynamic Logical Partitioning > Memory > Move |
| Virtual I/O | ||
|
SCSI Adapters |
View the virtual SCSI adapter's connections configured for the partition | Hardware (Information) > Virtual I/O Adapters > SCSI |
|
Ethernet Adapters |
View the virtual Ethernet adapter's connections configured for the partition | Hardware (Information) > Virtual I/O Adapters > Ethernet |
| Restart Partition | Restart the partition | Operations > Restart |
| Shutdown Partition | Shutdown the partition | Operations > Shut Down |
| Save | Save the current LPAR configuration to a new profile | Configuration > Save Current Configuration |
| Activate | Activate the partition | Operations > Activate |
| Change Default Profile | Change the default profile for the partition | Change Default Profile |
| Virtual I/O Server Command | Issue a command to the Virtual I/O Server partition | Operations > Perform VIOS Command |
| Open Terminal Window | Open a virtual terminal to the partition | Console Window > Open Terminal Window |
| Open Shared 5250 Console | Open a shared 5250 console to the partition | Console Window > Open Shared 5250 Console |
| Open Dedicated 5250 Console | Open a dedicated 5250 console to the partition | Console Window > Open Dedicated 5250 Console |
| Close Terminal Window | Close the virtual terminal window connection to the partition | Console Window > Close Terminal Connection |
| Delete | Delete the partition | Operations > Delete |
| Task Name | Task Description | New Location |
|---|---|---|
| Profile Tasks | * All profile tasks are located in the Manage Profiles task which is available when a partition is selected in the main UI. | |
| Copy | Copy the profile | Configuration > Manage Profiles > Copy |
| Properties | View or edit the profile properties | Configuration > Manage Profiles > Edit |
| Delete | Delete the profile | Configuration > Manage Profiles > Delete |
| Activate | Activate the profile | Configuration > Manage Profiles > Activate |
| Task Name | Task Description | New Location |
|---|---|---|
| System Profile Tasks | * All profile tasks are located in the Manage System Profiles task which is available when a managed system is selected in the main UI. | |
| Validate | Validate the system profile configuration information | Configuration > Manage System Profiles > Validate |
| Copy | Copy the system profile | Configuration > Manage System Profiles > Copy |
| Properties | View or edit the system profile properties | Configuration > Manage System Profiles > Edit |
| Delete | Delete the system profile | Configuration > Manage System Profiles > Delete |
| Activate | Activate the system profile | Configuration > Manage System Profiles > Activate |
Manage On Demand Activations has more categorization of tasks and is located under Capacity On Demand (CoD). The different CoD types are separated out from each other and placed in their own category. For instance, instead of having one task called “Capacity Settings” that contained all of the information for the different CoD types (which retrieving all of that information to view one particular type is not the most efficient approach for performance), now each type of CoD has its own Capacity Settings task. This new categorization also allows you to easily see all of the tasks that are associated with each CoD type.
| Task Name | Task Description | New Location |
|---|---|---|
| Capacity On Demand | ||
| Enter CoD Code | Enter a CoD code | Capacity On Demand > Enter CoD Code |
| Processor | ||
| Capacity Settings | View overall system processor capacity settings | Capacity On Demand > Processor > View Capacity Settings |
|
On/Off CoD |
View On/Off CoD processor settings | Capacity On Demand > Processor > On/Off CoD > View Capacity Settings |
|
Reserve CoD |
View Reserve CoD processor settings | Capacity On Demand > Processor > Reserve CoD > View Capacity Settings |
|
Trial CoD |
View Trial CoD processor settings | Capacity On Demand > Processor > Trial CoD > View Capacity Settings |
| Manage On/Off CoD | Manage On/Off CoD processors | Capacity On Demand > Processor > On/Off CoD > Manage |
| Manage Reserve CoD | Manage Reserve CoD processors | Capacity On Demand > Processor > Reserve CoD > Manage |
| Stop Trial CoD | Stop Trial CoD processors | Capacity On Demand > Processor > Trial CoD > Stop |
| Shared Processor Utilization | View the shared processor utilization data for the system | Capacity On Demand > Processor > Reserve CoD > View Shared Processor Utilization |
| Memory | ||
| Capacity Settings | View overall system memory capacity settings | Capacity On Demand > Memory > View Capacity Settings |
|
On/Off CoD |
View On/Off CoD memory settings | Capacity On Demand > Memory > On/Off CoD > View Capacity Settings |
|
Trial CoD |
View Trial CoD memory settings | Capacity On Demand > Memory > Trial CoD > View Capacity Settings |
| Manage On/Off CoD | Manage On/Off CoD memory | Capacity On Demand > Memory > On/Off CoD > Manage |
| Stop Trial CoD | Stop Trial CoD memory | Capacity On Demand > Memory > Trial CoD > Stop |
| Show History Log | Displays the CoD history log | Capacity On Demand > View History Log |
| Show Code Information | Displays the information used to generate CoD codes by CoD type | Capacity On Demand > Processor > CUoD > View Code Information
Capacity On Demand > Processor > On/Off CoD > View Code Information Capacity On Demand > Processor > Trial CoD > View Code Information Capacity On Demand > Processor > Reserve CoD > View Code Information Capacity On Demand > Memory > CUoD > View Code Information Capacity On Demand > Memory > On/Off CoD > View Code Information Capacity On Demand > Memory > Trial CoD > View Code Information |
| Show Billing Information | Displays the billing information for On/Off CoD | Capacity On Demand > Processor > On/Off CoD > View Billing
Information
Capacity On Demand > Memory > On/Off CoD > View Billing Information |
| Task Name | Task Description | New Location |
|---|---|---|
| Virtualization Engine Technologies | Capacity On Demand > Advanced POWER Virtualization | |
| Enter Activation Code | Copy the profile | Capacity On Demand > Advanced POWER Virtualization > Enter Activation
Code
Capacity On Demand > Enterprise Enablement > Enter Activation Code |
| Show Code Information | View or edit the profile properties | Capacity On Demand > Advanced POWER Virtualization > View Code Information
Capacity On Demand > Enterprise Enablement > View Code Information |
| Show History Log | Delete the profile | Capacity On Demand > Advanced POWER Virtualization > View History
Log
Capacity On Demand > Enterprise Enablement > View History Log |
Frame Management has remained unchanged. Only a couple of the task names have changed and the tasks have been categorized not unlike the managed system and partition tasks.
| Task Name | Task Description | New Location |
|---|---|---|
| Initiate Frames | Perform genesis IPL for all of the frames attached to the HMC | Operations > Initialize Frames |
| Properties | View or edit the frame properties | Properties |
| Rebuild Managed Frame | Rebuild the HMC's internal representation of the frame | Operations > Rebuild |
| Reset or Remove Connection | Reset the HMC connection to the managed frame | Operations > Reset Connection |
| Update Managed Frame Password | Update the HMC password for the managed frame | Operations > Change Password |
| I/O Unit | Power off the I/O units that are not currently owned by a Service Processor | Operations > Power Off I/O Units |
| Status | View the frame connection status | Operations > Bulk Power Assembly (BPA) Status |
The Utilization Data Management node has been completely removed and the tasks are now strictly targeted on a managed system basis. You will find the utilization data tasks located in the “Operations” category of your managed systems.
| Task Name | Task Description | New Location |
|---|---|---|
| Change Settings for Utilization Data Collection | T[S] Enable or disable utilization data collection on the managed system | Operations > Utilization Data > Enable
Operations > Utilization Data > Disable |
| View Utilization Data | T[S] View the utilization data information that has been collected | Operations > Utilization Data > View |
System plan tasks have become, for the most, part targeted tasks. You can work with all of the system plans on the HMC in one view. There are also additional system plan tasks available at the server level. For example, in the server container you can select a managed system and create a system plan by selecting the Configuration > System Plans > Create task.
The newly implemented System Plans container replaces the Manage System Plans task found in the WebSM System Plans container. You can now manage all of your system plans and perform actions on them from one view.
| Task Name | Task Description | New Location |
|---|---|---|
| Import System Plan | Import system plans from media or remote site | System Plans > Import System Plan |
| Deploy System Plan | T[S,SP] Deploy system plan to the system | System Plans > Deploy System Plan
Servers > System Task - Configuration > System Plans > Deploy |
| Manage System Plans | Manage system plans (create, delete, import, export) | System Plans |
| Learn more about system planning | Information Center articles regarding system planning | Welcome Screen > Online Information > IBM System Support
Welcome Screen > Online Information > Education and Tutorials |
Licensed Internal Code Maintenance has been combined into one Updates node which not only allows you to update the HMC with one click, but also all of the systems and frames being managed are seen along with their current code levels in one view. An Update task category has been created for managed systems in the servers container that will also allow you to perform code update/upgrade type of tasks.
The Backup HMC Data, Save Upgrade Data, Format Media, types of tasks have been moved away from the LIC categories into the HMC Management node. Also, there are a number of places where you can view the entire HMC versioning information by simply pointing to HMC Version at the top of the Service Management, HMC Management, and Welcome work panes.
| Task Name | Task Description | New Location |
|---|---|---|
| HMC Code Update | ||
| Backup Critical Console Data | Backup HMC console data | HMC Management > Backup HMC Data |
| Save Upgrade Data | Save HMC upgrade data information | HMC Management > Save Upgrade Data |
| Install Corrective Service | Install corrective service fix packs/updates | Updates > HMC Code Level > * Click Update HMC |
| Format Removable Media | Format removable media sources on the HMC (USB flash, diskette, etc) | HMC Management > Format Media |
| Remote Restore of Critical Console Data | Restore console data from a remote site | HMC Management > Restore HMC Data |
| Display HMC Version | Display complete HMC Version information such as serial number, bios level | Welcome Screen > point to HMC Version
HMC Management > pint to HMC Version Updates > HMC Code Level |
| Licensed Internal Code Updates | ||
| Change Licensed Internal Code for the current release | T[S,U]Update the firmware code level on the managed system/frame | Updates > System Code Levels - Change Licensed Internal
Code for the current release
Servers > System Task – Updates > Change Licensed Internal Code for the current release |
| Flash Side Selection | T[S,U]Select flash side for update | Updates > System Code Levels > Flash Side Selection
Servers > System Task – Updates > Flash Side Selection |
| Upgrade Licensed Internal Code to a new release | T[S,U]Upgrade to a new firmware code level | Updates > System Code Levels > Upgrade Licensed Internal
Code to a new release
Servers > System Task - Updates > Upgrade Licensed Internal Code to a new release |
| Check system readiness | T[S,U]Check the system readiness for code update/upgrade | Updates > System Code Levels > Check system readiness
Servers > System Task – Updates >Check system readiness |
The HMC Management container, much like the Service Applications container, has been flattened out and all of the task are available with one click. One major change here is that the “Schedule Operations” task has been altered to become a targeted task so that you can simply select a managed system or partition in the work area and start working with scheduled operations for that object.
| Task Name | Task Description | New Location |
|---|---|---|
| HMC Users | ||
| Manage HMC Users and Access | Manage user and access | HMC Management > Manage User Profiles and Access |
| Manage Access Task Roles and Managed Resource Roles | Manage user roles | HMC Management > Manage Task and Resource Roles |
| Change User Password | Change password | HMC Management > Change User Password |
| HMC Configuration | ||
| Customize HMC Date and Time | Set date, time, and time zone | HMC Management > Change Date and Time |
| View HMC Events | View console events | HMC Management > View HMC Events |
| Customize Network Settings | Configure network, firewall, DNS, and routes | HMC Management > Change Network Settings |
| Test Network Connectivity | Ping utility | HMC Management > Test Network Connectivity |
| Schedule Operations | T[S,P,H] Configure scheduled operations | HMC Management > Schedule Operations
* System Task – Operations > Schedule Operations *Partition Task – Operations > Schedule Operations |
| Enable or Disable Remote Command Execution | Allow SSH | HMC Management > Remote Command Execution |
| Enable or Disable Remote Virtual Terminal | Allow virtual terminal | HMC Management > Remote Virtual Terminal |
| Change Current Language and Locale | Change language and locale | HMC Management > Change Language and Locale |
The Service Applications container has been renamed to Service Management and contains the majority of tasks that were found under the Service Applications nodes. The majority of tasks that are located in the Service Focal Point > Service Utilities dialogs have been moved to be targeted tasks located within the Serviceablity task category for managed systems and partitions. You can select a managed system or partition, then select Manage Serviceable Events or select a system and perform a Add FRU task.
| Task Name | Task Description | New Location |
|---|---|---|
| Service Agent | ||
| eService Registration | Registers system for use on the eService web site | Service Management > Manage eService Registration |
| Customer Notification | How the customer will be notified | Service Management > Manage Serviceable Event Notification |
| Transmit Service Information | Transmit HMC service information | Service Management > Transmit Service Information |
| Service Agent Connection Manager | Configure a connection manager for legacy SA clients | Service Management > Manage POWER4 Service Agent |
| Remote Support | ||
| Customize Customer Information | Configure customer information | Service Management > Manage Customer Information |
| Customize Outbound Connectivity | Configure call-home settings | Service Management > Manage Outbound Connectivity |
| Customize Inbound Connectivity | Configure remote serve settings | Service Management > Manage Inbound Connectivity |
| Manage Remote Support Requests | View active RSF requests | Service Management > Manage Remote Support Requests |
| Manage Remote Connections | View active RCS requests | Service Management > Manage Remote Connections |
| Customer Service Settings | Configure service settings | Service Management > Manage Systems Call-Home |
| Service Focal Point | ||
| Repair Serviceable Event | T[S,H,P] Repairs a problem.
** Manage and Repair have been combined into one task that is accessible from the System, Partition, and HMC level |
Service Management > Mange Serviceable Events
* Partition Task - Serviceability > Manage Serviceable Events * System Task - Serviceability > Manage Serviceable Events |
| Manage Serviceable Events | See Repair Service Event | |
| Install/Add/Remove Hardware | ||
| Add Enclosure | T[S] Add Enclosure. | System Task - Serviceability > Hardware |
| Add FRU | T[S] Add FRU | System Task - Serviceability > Hardware |
| Remove Enclosure | T[S] Remove Enclosure. | System Task - Serviceability > Hardware |
| Remove FRU | T[S] Remove FRU | System Task - Serviceability > Hardware |
| Exchange Parts | ||
| Replace Enclosure | T[S] Exchange Enclosure | System Task - Serviceability > Hardware |
| Replace FRU | T[S] Exchange FRU | System Task - Serviceability > Hardware |
| Service Utilities | ||
| Create Serviceable Event | Creates a problem for the HMC | Service Management > Create Serviceable Event |
| Connection Monitoring | Configures connection errors to be sent to service agent | Service Management > Manage Connection Monitoring |
| Load Problems From XML | Load problems from a local XML file | Service Management > Load Serviceable Events |
| View Network Topology | Ping broadcasting to discover managed system, HMCs, etc. | HMC Management > View Network Topology |
| Create Serviceable Event | T[S] Creates a problem for targeted system | System Task – Serviceability > Create Serviceable Event |
| Launch ASM Menu | T[S] Launch browser to connect to ASM | System Task – Operations > Advanced System Management ( ASM ) |
| Manage Dumps | T[S] Manage system dumps | System Task – Serviceability > Manage Dumps |
| Edit MTMS | T[S] Modify MTMS | System Task – Serviceability > Edit MTMS |
| System Attention LED | T[S] Turn System Attention LED on/off | System Task – Operations > LED Status |
| Identify LED processing | T[S] Turn Identify LED on/off | System Task – Operations > LED Status |
| Lamp Test | T[S] Blinks all LEDs on system | System Task – Operations > LED Status |
| Operator Panel Service Functions | T[S] Mimics Op Panel functionality | System Task – Serviceability > Control Panel Functions |
| Power On/Off Unit | T[S] Power system off/on | System Task – Serviceability > Hardware |
| View RIO Topology | T[S] View the RIO cable connections | System Task – Hardware > View Topology |
| Service Processor Failover | T[S] Configure FSP failover | System Task – Serviceability > FSP Failover |
| Collect VPD Information | T[S] Collect VPD Information | System Task – Serviceability > Collect VPD |
The following dynamic LPAR changes include:
Another change that has been implemented for DLPAR operations is that the task will display an indicator within the dialog for AIX and Linux partitions that alerts you that an RMC connection is missing. This is to let you know you are about to perform an RMC-less DLPAR operation before you start entering data into the fields in the dialog. If you would still like to move resources between two AIX or Linux partitions that do not have RMC connections the command line chhwres command can still be used to facilitate the move operation.
This chapter explains how to use the web-based user interface to perform tasks on the Hardware Management Console (HMC) or on your managed resources. This user interface comprises several major components as shown in Figure 3: the banner, the task bar, the navigation pane, the work pane, and the status bar.
The banner, across the top of the workplace window, identifies the product and logo. It is optionally displayed. Use the Change User Interface Settings task to change the setting.
The task bar, located below the banner, displays the names of any tasks that are running, the user ID you are logged in as, online help information, and the ability to logoff or disconnect from the console.
The navigation pane, in the left portion of the window, contains the primary navigation links for managing your system resources and the HMC. The items are referred to as nodes.
The work pane, in the right portion of the window, displays information based on the current selection from the navigation pane. For example, when Welcome is selected in the navigation pane, the Welcome window content is displayed in the work pane, as shown in Figure 3.
The status bar, in the bottom left portion of the window, provides visual indicators of current overall system status. It also contains a status overview icon which may be selected to display more detailed status information in the work pane.

You can resize the panes of the HMC workplace by moving the mouse pointer over the border that separates the navigation pane from the work pane until the mouse pointer changes to a double-pointed arrow. When the pointer changes shape, press and hold the left mouse button while dragging the mouse pointer to the left or right. Release the button and your navigation pane or work pane is now larger or smaller in size. You can also do this within the work pane border that separates the resources table from the tasks pad.
The task bar provides the capability of an active task switcher. The task bar can be used as a navigation aid to move between tasks that were launched and have not yet been closed. The task switcher does not pause or resume existing tasks. Clicking on a task in the task bar brings that task's window forward and gives it focus.
Note:Applet based tasks such as AIX terminal windows, 5250 console windows, or restricted shell windows do not support the task bar switching capabilities. Please use the window switching capabilities for local windows to switch to the windows for these tasks.
The right end of the task bar also contains the following information as shown in Figure 4:

The navigation pane, as shown in Figure 3, contains the primary navigation links for managing your system resources and the HMC. These include:
Welcome is the initial window that is displayed when you log on to the HMC. The Welcome work pane lists the nodes of the navigation pane and their descriptions. It also includes the following Additional Resources:
If you are accessing the HMC remotely, you can view the publication in PDF format or in HTML format (click View as HTML). If you are accessing the HMC locally, you can view the publication in HTML format.
To see what level of the HMC you are currently working with, point your mouse over HMC Version found at the top of the work pane.
Systems Management contains a tree view of managed resources. Resources may include:
The Servers node represents the servers that are managed by this HMC. To add servers you can use the Add Managed System task under the Connections category in the tasks pad.
When you click Servers from the navigation pane a listing of individually defined servers is displayed in table form in the work pane and under the Servers node in the navigation pane, as shown in Figure 5.

To work with a server, you can perform one of the following actions:
The Servers work pane table displays the following attributes by default.
The Servers work pane table can also display the following optional attributes in the table.
Optional attributes can be displayed when you select the Column configuration icon on the table toolbar. This function allows you to select additional attributes that you want displayed as columns in the table. It also allows you to reorder the columns, see Column configuration for more information.
You can also use Views from the table toolbar to display the Default server attributes in the table or to display the Capacity On Demand server attributes in the table. See Figure 6 for a sample of using the Capacity On Demand view and Views menu for more information.

To display details (properties) about a server you can select the server by clicking in the Select column in the work pane table. Then you can either, click Properties from the tasks pad or click on the double-arrow icon next to the server name and click Properties from the context menu. In both cases the Properties window is displayed.
After you have chosen the objects to work with you are ready to perform the appropriate tasks on them. The tasks the objects can perform include the following task groups. Task groups are simple "categorization nodes" and are not tasks themselves.
You can select a task from these task groups in a variety of ways. Some of these categories may also include sub categories before you get to the actual task you want to perform, see Figure 7. Appropriate tasks for a selected object are listed in the tasks pad, in context menus, and in the Tasks menu.
The tasks pad appears below the work pane when you have selected an object you want to work with (see Figure 7). This view contains available tasks for selected managed objects.

The tasks contained in this view meet the following characteristics:
An example of using the tasks pad method:
The Context menu is a pop-up menu that lists the task groups appropriate for the selected object. Context menus are only available for table selections. For example, in the Select column of the Servers Work pane table, select the object you want to work with (a check mark appears). The Context menu button (double right arrows) appears next to the object name you have selected. Click the button and the task groups menu appears for that particular object, as shown in Figure 8. Then select a task to launch for the object. If more than one object is selected, the tasks that appear in the Context menu(s) apply to all selections.
The tasks menu is displayed on the table toolbar, as shown in Figure 9. The tasks menu is only available for table selections. For example, in the Select column of the Servers work pane table, select the object you want to work with. Click Tasks for the list of the applicable task groups for the selected objects in the table. Select a task group, then select a task to open for the object. If more than one object is selected, the tasks that are displayed in the tasks menu apply to all selections.
When you select a managed server in the navigation pane, the work pane displays the list of partitions defined on the server as shown in Figure 10.

The Partitions work pane table displays the following attributes by default.
The Partitions work pane table can also display the following optional attributes in the table.
Optional attributes can be displayed when you select the Column configuration icon on the table toolbar. This function allows you to select additional attributes that you want displayed as columns in the table. It also allows you to reorder the columns, see Column configuration for more information.
To display details (properties) about a partition you can select the partition by clicking in the Select column in the work pane table. Then you can either, click Properties from the tasks pad or click on the double-arrow icon next to the partition name and click Properties from the context menu. You can also click on the partition name. In all cases the Properties window is displayed.
The Frames node identifies the frames managed by this HMC.
The Frames work pane table includes the following attributes.
The Custom Groups node provides a mechanism for you to group system resources together in a single view. In addition, groups may be nested to create custom "topologies" of system resources.
Custom groups include the predefined groups All Partitions and All Objects and any user-defined groups that you created using the Manage Custom Groups task under the Configuration category in the tasks pad. The All Partitions group includes all the partitions defined to all servers managed by the HMC. The All Objects group is a collection of all the managed servers, partitions, and frames.
These system-defined groups (All Partitions and All Objects) cannot be deleted. However, if you do not want All Partitions or All Objects displayed under Custom Groups, do the following:
You can use the Views menu on the table toolbar to display your preferred table column configuration, see Views menu for more information.
You can use the Manage Custom Groups task under the Configuration category from the tasks pad to create your own group that you want to work with. This task allows you to create new groups and manage existing ones. To create a group:
You can also create a group by using the pattern match method:
See Manage Custom Groups for more information.
System Plans displays the plans and the tasks to deploy system plans to managed systems. A system plan contains a specification of the logical partition configuration of a single managed system. You can also use this node to import, export, and manage the files containing these system plans.
To display the plans and tasks:
These tasks are described in further detail in System Plans. The table in the work pane displays the system plans that the HMC manages and attributes related to the system plans.
The following attributes are set as the defaults. However, you can select or deselect the attributes that you want displayed in the table by clicking the Column configuration icon on the table toolbar. You can also reorder the columns, see Column configuration for more information.
The create and deploy System Plans tasks are also displayed for a server under the Configuration task group.
If there are no system plans available when you select the System Plans node, you can create or import a plan from the tasks listed in the tasks pad as shown in Figure 11.

HMC Management contains a categorized or alphabetic view of HMC management tasks and their descriptions. These tasks are used for setting up the HMC, maintaining its internal code, and securing the HMC.
To display the tasks in the work pane:
To see what level of the HMC you are currently working with, point your mouse over HMC Version found at the top of the work pane.
If you want an alphabetic listing of the tasks, click Alphabetical List in the upper right corner of the work pane. Click Categorized List to go back to the task categories.
The following alphabetic list of HMC Management tasks are displayed in the work pane depending on the task roles defined to your user ID. They are described in further detail in HMC Management tasks and a listing of the tasks and the default user roles that can use them are shown in Table 10.
Service Management contains a categorized or alphabetic view of tasks and their descriptions used to service the HMC.
To display the tasks in the work pane:
To see what level of the HMC you are currently working with, point your mouse over HMC Version found at the top of the work pane.
If you want an alphabetical listing of the tasks, click Alphabetical List in the upper right corner of the work pane. Click Categorized List to go back to the task categories.
The following alphabetic list of Service Management tasks are represented in the work pane depending on the task roles defined to your user ID. They are described in further detail in Service Management tasks and a listing of the tasks and the default user roles that can use them are shown in Table 10.
Updates provides a way for you to access information on both HMC and system firmware code levels at the same time without running a task. The Updates work pane displays the HMC code level, system code levels, and the ability to install corrective service by clicking Update HMC. Note: Before performing HMC updates, see Update HMC.
To display the tasks:
See Figure 12 for an example of the Updates work pane and tasks pad. The Updates tasks can also be displayed under the Updates task group when you are working with managed objects from the Systems Management node of the navigation pane.

The work pane displays a table of information based on the current selection in the navigation pane or status bar. Selecting an object displays a configurable table in the work pane as shown in Figure 13. The following figure also identifies some of the areas of the work pane table.

The tool bar at the top of the table contains buttons used to select, filter, sort, and arrange the entries in the table. Hovering over the toolbar buttons displays their functions. The toolbar also includes menus that are used with the information displayed in the tables. See Tasks menu and Views menu for more information.

You can select more than one table row at any given time. Rows can be individually selected or a block of rows can be selected at once by first left-clicking the selection box of the first row in the desired block and then shift-clicking the selection box of the last row in the desired block. The Select All or Deselect All buttons can be used to select or deselect all objects in the table. The table summary at the bottom of the table includes the total number of items that are selected.

If you select the Filter Row button a row appears under the title row of the table. Select Filter under a column to define a filter for that column to limit the entries in a table. Tables can be filtered to show only those entries most important to you. The filtered view can be toggled on and off by selecting the check box next to the desired filter in the filter row. Select the Clear All Filters button to return to the complete listing. The table summary includes the total number of items that pass the filter criteria in addition to the total number of items.

The Edit Sort and Clear All Sorts buttons are used to perform multi-column sorts of objects in the table in ascending or descending order. Click Edit Sort to define sorts for columns in a table. Alternatively, single column sorting can be performed by selecting the ^ in the column header to change from ascending to descending order. Click Clear All Sorts to return to the default ordering.

The column configuration buttons give you the ability to select which columns to display for folders in the Systems Management tree view. Click the Configure Columns button to arrange the columns in the table in a desired order or hide columns from view. All available columns are listed in the Columns list box by their column name. You select the columns you want displayed or hidden by checking or unchecking the box next to the column names. The column order is manipulated by clicking on a column name from the list box and using the arrow buttons to the right of the list to change the order of the selected column. When you have completed the configuration of the columns, click OK. The columns appear in the table as you specified. If you want to go back to the original layout of the table, click the Reset Column Order, Visibility, and Widths button from the table toolbar. Select one or more of the properties to be reset back to their original layout, click OK to save.
The views menu is displayed on the toolbar and is only available for table selections when working with servers, custom groups, exceptions view, or attention LEDs view. This table option allows you to display different sets of attributes (columns) in the table. Figure 14 displays an example of the Views options when you are working with servers. Figure 15 displays an example of the Views options when you are working with user-defined custom groups.
You can also change the attributes for each view. For example, if you choose Default from the views menu and you do not want Available Processing Units appearing in the table, use the Configure columns table toolbar button and deselect Available Processing Units, then click OK. Now, when you choose the Default view the view displays the table without the Available Processing Units column. To go back to the original default view for any of the views use the Reset Column Order, Visibility, and Widths table toolbar button (see Column configuration).
The status bar in the bottom left pane, as shown in Figure 16, provides a view of overall system status, including managed system resources and the HMC. A status-sensitive title, background color, and indicator icons are part of the status bar. The status indicators (icons) appear in color when one or more objects go into unacceptable status, have attention LEDs, or have open serviceable events. Otherwise, the status icon is not available.

Click any of the individual icons in the status bar to view a listing of resources with specific status. For example, select the Unacceptable icon to view all resources in an unacceptable state. The results are displayed in a table in the work pane.

If any managed object is in unacceptable state, the Unacceptable indicator (icon) is activated on the status bar. When you select the Unacceptable indicator (icon) it displays a table in the work pane of only the objects in an unacceptable state. By clicking on the icon, help information is opened describing unacceptable status (Error state) of the server or partition. You can also use the Views menu to display your preferred table column configuration for these objects, see Views menu.

If any managed object's Attention LED is activated, the Attention LED (icon) is activated in the status bar. When you select the Attention LED indicator (icon) it displays a table in the work pane of only the objects in Attention LED. By clicking on the icon, help information is opened guiding you in problem determination. You can also use the Views menu to display your preferred table column configuration for these objects, see Views menu for more information.

If at least one serviceable event for the HMC or a managed object is in open state, the serviceable event icon, is activated in the status bar. By clicking on the icon the Manage Serviceable Events task is accessed with the filter set to view all open events.

When you select the Status Overview icon, it displays a highly visible and detailed summary of system status in the work pane, as shown in Figure 17. It displays details about any errors (objects with unacceptable state), attention LEDs active, or open serviceable events found for the HMC or managed objects. It also summarizes the total number of errors, attention LEDs, and open serviceable events by object type. Object types include the server, partition, frames, and the HMC. When any of these conditions are present, links are available to drill down and display all objects with the particular state in the work pane.

Systems Management displays tasks to manage servers, logical partitions, and frames. Use these tasks to set up, configure, view current status, troubleshoot, and apply solutions.
This chapter describes the tasks used when a server is selected.
To launch these tasks, see Launching tasks for managed objects. The following sets of tasks are represented in the tasks pad, tasks menu,
or context menu. The tasks listed in the tasks pad change as selections are made in the work area. The context is always listed at the top of the tasks pad in the format Task: Object. These tasks are listed when a managed system is selected and the context is Tasks: Server-9117-MMA-SN1234ABC.
The Properties task displays the selected managed system's properties. This information is useful in system and partition planning and resource allocation. These properties include:
Related HMC CLI commands:
Use the Update Password task to update HMC access and Advanced System Management Interface (ASMI) passwords on the managed system.
The first time you access a managed system using an HMC, the system prompts you to enter passwords for each of the following:
If you are using an HMC to access the managed system before all required passwords have been set, enter the appropriate password for each password that is presented in the Update Password task.
If another HMC subsequently needs access to this managed system, upon attempting to access this HMC the user is presented with the Update Password Failed Authentication window, which will prompt for the HMC access password you entered.
In the event that the HMC access password changes while you are logged in to the managed system, your HMC will discover that it can no longer authenticate after it attempts to reconnect to that managed system. This will result in a state of Failed Authentication for that managed system. You will be required to enter the new password before any actions can be performed.
Operations contains the tasks for operating servers. The following are represented in the Operations tasks.
Use the Power On task to start a managed system.
Choose from three different options to start your managed system:
This task shuts down the managed system. Powering off the managed system will make all partitions unavailable until the system is again powered on.
Before you power off the managed system, ensure that all logical partitions have been shut down and that their states have changed from Running to Ready. For more information on shutting down a logical partition, see Shut Down
If you do not shut down all logical partitions on the managed system before you power off the managed system, the managed system shuts down each logical partition before the managed system itself powers off. This can cause a substantial delay in powering off the managed system, particularly if the logical partitions are not responsive. Further, the logical partitions might shut down abnormally, which could result in data loss and further delays when you activate the logical partitions once more.
Choose from the following options:
Related HMC CLI commands:
This task contains the tasks for viewing system attention LED information, lighting specific LEDs to identify a system component, and testing all LEDs on a managed system.
The system provides several LEDs that help identify various components, such as enclosures or field replaceable units (FRUs), in the system. For this reason, they are called Identify LEDs. Individual LEDs are located on or near the components. The LEDs are located either on the component itself or on the carrier of the component (for example, memory card, fan, memory module, or processor). LEDs are either green or amber. Green LEDs indicate either of the following:
Amber LEDs indicate a fault or identify condition. If your system or one of the components on your system has an amber LED turned on or blinking, identify the problem and take the appropriate action to restore the system to normal. For more information on troubleshooting an amber LED indicating a fault, see System p Problem Analysis, SA76-0111.
You can activate or deactivate the following types of identify LEDs:
You can deactivate a system attention LED or a logical partition LED. For example, you might determine that a problem is not a high priority and decide to repair the problem at a later time. However, you want to be alerted if another problem occurs, so you must deactivate the system attention LED so that it can be activated again if another problem occurs.
Choose from the following options:
Related HMC CLI commands:
Use this task to create a schedule for certain operations to be performed on the managed system without operator assistance.
Scheduled operations are helpful for situations where automatic, delayed, or repetitious processing of system operations is necessary. A scheduled operation is started at a specified time, without operator assistance to perform the operation. A schedule can be set for one operation or repeated many times.
For example, you could schedule power on or off operations for a managed system.
The Scheduled Operations task displays the following information for each operation:
From the Scheduled Operations window you can:
An operation can be scheduled to occur one time or it can be scheduled to be repeated. You will be required to provide the time and date that you want the operation to occur. If the operation is scheduled to be repeated, you will be asked to select:
The operations that can be scheduled for the managed system are:
To schedule operations on the managed system:
Use the online Help to get additional information for scheduling an operation.
If configured to do so, the HMC connects directly to the Advanced System Management (ASM) interface for a selected system from this task.
ASM is an interface to the service processor that allows you to set flags that affect the operation of the server, such as auto power restart, and to view information about the server, such as the error log and vital product data.
To connect to the Advanced System Management interface:
For more information on the Advanced System Management interface, see Appendix E. Advanced Systems Management Interface (ASMI).
Related HMC CLI commands:
Use this task to set the HMC to collect resource utilization data for a specific managed system or for all systems the HMC manages. The HMC collects utilization data for memory and processor resources. You can use this data to analyze trends and make resource adjustments. The data is collected into records called events. Events are created at the following times:
You must set the HMC to collect utilization data for a managed system before utilization data can display for the managed system.
Related HMC CLI commands:
Use the Rebuild task to extract the configuration information from the managed system and rebuild the information on the Hardware Management Console. The Rebuild operation does not disrupt the operation of the running server.
Rebuilding the managed system updates, or refreshes, the information on the HMC about the managed system. Rebuilding the managed system is useful when the state of the managed system is Incomplete. The Incomplete state means that the HMC cannot gather complete information from the managed system about logical partitions, profiles, or resources.
Rebuilding the managed system is different from simply refreshing the HMC window. When the managed system is rebuilt, the HMC extracts the information from the managed system. You cannot start other tasks while the HMC rebuilds the managed system. This process can take several minutes.
Related HMC CLI commands:
Use the Change Password task to change the HMC access password on the selected managed system. After the password is changed, you must update the HMC access password for all other HMCs from which you want to access this managed system.
Enter the current password. Then enter a new password and verify it by entering it again.
Related HMC CLI commands:
Configuration contains the tasks for configuring your managed system and partitions. The following are represented in the Configuration tasks:
Use this task to create a new AIX or Linux logical partition (LPAR) on your managed system. The Create LPAR Wizard helps you create a new logical partition and a default profile for the partition.
Ensure you have logical partition planning information before you use this wizard. Logical partition planning information can be found at the System Planning Tool (SPT) website at http://www.ibm.com/systems/support/tools/systemplanningtool/. The SPT is available to assist you in system planning, design, validation and to provide a system validation report that reflects your system requirements while not exceeding system recommendations.
You might also find it helpful to be familiar with logical partition concepts. Logical partitioning information can be found in the Logical Partitioning Guide, SA76-0098.
Use the online Help for additional information on logical partition creation.
Related HMC CLI commands:
These tasks record or import specifications for logical partitions, partition profiles, or hardware specifications on a chosen system.
A system plan is a specification of the logical partition configuration of a single managed system. A system plan is stored in a file that is called a system-plan file and has a file suffix of .sysplan. A system-plan file can contain more than one system plan, although multiple plans in a single file are not common.
The System Plans tasks creates a record of the hardware and partition configuration of a managed system at a given time. It records specifications for the logical partitions and partition profiles on the selected system. It can also record hardware specifications that the HMC is able to detect.
To maximize the information that the HMC can obtain from the managed system, power on the managed system and activate the logical partitions on the managed system before creating the new system plan.
The System Plans tasks are the same tasks that are available from the System Plans node from the navigation pane and are documented here: System Plans.
Groups are comprised of logical collections of objects. You can report status on a group basis, allowing you to monitor your system in a way that you prefer.
You can also nest groups (a group contained within a group) to provide hierarchical or topology views.
One or more user-defined groups might already be defined on your HMC. Default groups are listed under the Custom Groups node under Server Management. The default groups are All Partitions and All Objects. You can create others, delete the ones that were created, add to created groups, create groups using the pattern match method, or delete from created groups by using the Manage Custom Groups task.
Use the online Help if you need additional information for working with groups.
This task displays a detailed view of the workload management groups you have specified for this managed system. Each group displays the total number of processors, processing units for partitions using shared mode processing, and the total amount of memory allocated to the partitions in the group.
Related HMC CLI commands:
Use this task to specify the partition-availability priority of each logical partition on this managed system.
The managed system uses partition-availability priorities in the case of processor failure. If a processor fails on a logical partition, and there are no unassigned processors available on the managed system, the logical partition can acquire a replacement processor from logical partitions with a lower partition-availability priority. This allows the logical partition with the higher partition-availability priority to continue running after a processor failure.
You can change the partition availability priority for a partition by selecting a partition and choosing an availability priority from those listed.
Use the online Help if you need additional information about prioritizing partitions.
Related HMC CLI commands:
A system profile is an ordered list of partition profiles that is used by the HMC to start the logical partitions on a managed system in a specific configuration.
When you activate the system profile, the managed system attempts to activate each partition profile in the system profile in the order specified. A system profile helps you activate or change the managed system from one complete set of logical partition configurations to another.
It is possible for you to create a system profile that has a partition profile that has overcommitted resources. You can use the HMC to validate the system profile against the currently available system resources and against the total system resources. Validating your system profile ensures that your I/O devices and processing resources are not overcommitted, and it increases the likelihood that the system profile can be activated. The validation process estimates the amount of memory needed to activate all of the partition profiles in the system profile. It is possible that a system profile can pass validation and yet not have enough memory to be activated.
Use this task to:
Use the online Help if you need additional information about managing system profiles.
Related HMC CLI commands:
A partition profile is a record on the HMC that specifies a possible configuration for a logical partition. When you activate a partition profile, the managed system attempts to start the logical partition using the configuration information in the partition profile.
A partition profile specifies the desired system resources for the logical partition and the minimum and maximum amounts of system resources that the logical partition can have. The system resources specified within a partition profile includes processors, memory, and I/O resources. The partition profile can also specify certain operating settings for the logical partition. For example, you can set a partition profile so that, when the partition profile is activated, the logical partition is set to start automatically the next time that you power on the managed system.
Each logical partition on a managed system that is managed by an HMC has at least one partition profile. You can create additional partition profiles with different resource specifications for your logical partition. If you create multiple partition profiles, you can designate any partition profile on the logical partition to be the default partition profile. The HMC activates the default profile if you do not select a specific partition profile to be activated. Only one partition profile can be active at one time. To activate another partition profile for a logical partition, you must shut down the logical partition before you activate the other partition profile.
A partition profile is identified by partition ID and profile name. Partition IDs are whole numbers used to identify each logical partition that you create on a managed system, and profile names identify the partition profiles that you create for each logical partition. Each partition profile on a logical partition must have a unique profile name, but you can use a profile name for different logical partitions on a single managed system. For example, logical partition 1 cannot have more than one partition profile with a profile name of normal, but you can create a profile named normal for each logical partition on the managed system.
When you create a partition profile, the HMC shows you all of the resources available on your system. The HMC does not verify if another partition profile is currently using a portion of these resources. Therefore, it is possible for you to overcommit resources. When you activate a profile, the system attempts to allocate the resources that you assigned to the profile. If you have overcommitted resources, the partition profile will not be activated.
For example, you have four processors on your managed system. Partition 1 profile A has three processors, and partition 2 profile B has two processors. If you attempt to activate both of these partition profiles at the same time, partition 2 profile B will fail to activate because you have overcommitted processor resources.
When you shut down a logical partition and reactivate the logical partition using a partition profile, the partition profile overlays the resource specifications of the logical partition with the resource specifications in the partition profile. Any resource changes that you made to the logical partition using dynamic logical partitioning are lost when you reactivate the logical partition using a partition profile. This is desirable when you want to undo dynamic logical partitioning changes to the logical partition. However, this is not desirable if you want to reactivate the logical partition using the resource specifications that the logical partition had when you shut down the managed system. Therefore, keep your partition profiles up to date with the latest resource specifications. You can save the current configuration of the logical partition as a partition profile. This allows you to avoid having to change partition profiles manually.
If you shut down a logical partition whose partition profiles are not up to date, and the logical partition is set to start automatically when the managed system starts, you can preserve the resource specifications on that logical partition by restarting the entire managed system using the partition autostart power-on mode. When the logical partitions start automatically, the logical partitions have the resource specifications that the logical partitions had when you shut down the managed system.
Use the Manage Partition Data tasks to:
Use the online Help if you need additional information about managing partition data.
Related HMC CLI commands:
Connections tasks allow you to view the HMC connection status to service processors or frames, reset those connections, connect another HMC to the selected managed system, or connect another managed system to the HMC.
If you have selected a managed system in the work area, the following tasks pertain to that managed system. If you have selected a frame, the tasks pertain to that frame. For managed systems, the tasks are:
Related HMC CLI commands:
Related HMC CLI commands:
Related HMC CLI commands:
To correct a connection problem between the HMC and the managed system or to correct the state of a managed system in No Connection, Incomplete, Recovery, Error, or Failed Authentication state, follow the procedures below.
The No connection state can occur when the HMC is not connected, or the handshake with the managed system failed.
Use this procedure for a system that was previously connected to the same HMC and is now in No connection state. If you have a new system, a new HMC, or have moved your system to a different HMC, refer to Correcting a connection problem between the HMC and a managed system.
The Incomplete state can occur when the HMC failed to get all of the necessary information from the managed system.
To correct an Incomplete state, perform the following steps:
The Recovery state can occur when the save area in the service processor assembly is not synchronized with the HMC.
To recover from the Recovery state, perform the following steps:
The Error state automatically generates a call to the service support center if the function is enabled.
If the automatic call support function is not enabled, contact your next level of support or your hardware service provider.
The Failed Authentication state can occur when the HMC access password for the managed system is not valid.
Use this procedure in the following situations:
If your system was previously connected to the same HMC and is now in No connection state, refer to Correcting a No connection state for a managed system.
Hardware (Information) tasks are used to display information about the hardware attached to a selected managed system.
The following are represented in the Hardware (Information) tasks:
Use the Adapters tasks to view information about the Host Ethernet Adapters (HEA) or Host Channel Adapters (HCA) for a selected managed system.
A Host Ethernet Adapter (HEA) allows multiple logical partitions to share a single physical Ethernet adapter.
Unlike most other types of I/O devices, you can never assign the HEA itself to a logical partition. Instead, multiple logical partitions can connect directly to the HEA and use the HEA resources. This allows these logical partitions to access external networks through the HEA without having to go through an Ethernet bridge on another logical partition.
Use the Host Ethernet task to display or configure the ports of the physical Host Ethernet Adapters (HEAs) on a selected managed system.
To configure a physical port on an HEA, select the port from the list and select Configure.
Use the online Help for additional information on configuring HEA ports.
Related HMC CLI commands:
Host Channel Adapters provide a managed system with port connections to other InfiniBand devices. That port can be connected to another HCA, a target device, or an InfiniBand switch that redirects the data coming in on one of its ports out to a device attached to another of its ports.
Use the Host Channel task to show a list of the HCAs for the managed system. You can select an HCA from the list to display the current partition usage for the HCA.
From this task you can display:
Related HMC CLI commands:
Use the Virtual IO Adapters commands to view the topology of currently configured virtual scsci and virtual ethernet adapters on a selected partition.
Use the SCSI task to view the topology of virtual SCSI adapters on a partition. Displayed are:
Use the Ethernet task to view the current virtual ethernet configuration for the partition.
Partitions assigned to a VLAN that is bridged have access to a external network via a physical shared ethernet adapter owned by a Virtual I/O Server.
This task displays the current hardware topology for the selected managed system and any discrepancies between the current topology and the last valid topology.
High Speed Link (HSL), also known as Remote I/O (RIO), resources provide the connection between system I/O busses and the system processor. HSL/RIO resources are normally configured in loops with the system unit having an HSL/RIO controller resource that handles routing of the data between the system processor and the system I/O busses. System I/O busses connect to the loop with HSL I/O adapter or RIO adapter resources.
Use this task to display the current RIO topology of the selected managed system. Current Topology displays the current topology. Any discrepancies between the current topology and the last valid topology are identified as errors. The following information is shown:
Updates tasks perform a guided update of managed system, power, or I/O Licensed Internal Code.
These Update tasks are the same tasks that are available from the Updates node of the navigation pane and are documented here: Managed System Updates.
Problem Analysis on the HMC automatically detects error conditions and reports to you any problem that requires service to repair it. These problems are reported to you as serviceable events. Use the Manage Events task to view specific events for selected systems. However, if you notice a problem occurred or you suspect a problem is affecting the system but Problem Analysis has not reported it to you, use the Create Serviceable Event task to report the problem to your service provider.
The following are represented in the Serviceability tasks:
Problems on your managed system are reported to the HMC as serviceable events. The Manage Serviceable Events task allows you view the problem, manage problem data, call home the event to your service provider, or repair the problem.
To set the criteria for the serviceable events you to view:
The Serviceable Events Overview panel displays all of the events that match your criteria. The information displayed in the compact table view includes:
The full table view includes more detailed information, including reporting MTMS, first reported time, and serviceable event text.
Select a serviceable event and use the Selected drop down menu to:
Use the online Help if you need additional information on managing serviceable events.
Use this task to report a problem on your managed system to your service provider or to test problem reporting on your managed system.
Submitting a problem is dependent upon whether you have customized your HMC to use the Remote Support Facility (RSF) and if it is authorized to automatically call for service. If so, the problem information and service request is sent to the service provider automatically with a modem transmission.
To report a problem on your managed system:
or
To test problem reporting from the Report a Problem window:
The problems are reported to the service provider for the managed system. Reporting a problem sends to the service provider the information you provide on the Report a Problem window, and machine information that identifies the console.
Use the online Help if you need additional information for reporting a problem or testing if problem reporting works.
Reference codes provide general diagnostic, troubleshooting, and debugging information.
The most recent reference codes are displayed. To view a history of reference codes, enter the number of codes to retrieve from the history and select Go. If detailed information is available on the managed system you are viewing, select the desired reference code to view the details of a specific reference code.
Related HMC CLI commands:
This task displays the available virtual control panel functions for the managed system selected.
(20) Type, Model, Feature displays the managed system's machine type, model, and feature code. Also displayed are the CEC IPL Type and the FSP IPL Type for the managed system.
Related HMC CLI commands:
These tasks are used to add, exchange, or remove hardware from the managed system. From the hardware tasks you can display a list of installed FRUs or enclosures and their locations. Select a FRU or an enclosure and launch a step-by-step procedure to add, exchange, or remove the unit.
Hardware tasks include:
Use the Add FRU task to locate and add a Field Replaceable Unit (FRU).
To add a FRU:
Use the Add Enclosure task to locate and add an enclosure.
To add an enclosure:
Use the Exchange FRU task to exchange one FRU with another.
To exchange a FRU:
Use the Exchange Enclosure task to exchange one enclosure for another.
To exchange an enclosure:
Use the Remove FRU task to remove a FRU from your managed system.
To remove a FRU:
Use the Remove Enclosure task to remove an enclosure.
To remove an enclosure:
Use the Power On/Off IO Unit task to power on or off an IO unit.
Only units or slots that reside in a power domain can be powered on or off. The corresponding power on/off buttons will be disabled for location codes that are not controllable by the HMC.
These tasks are used to manage system, service processor, and power subsystem dumps for systems managed by the HMC.
Use the Manage Dumps task to:
Use the online Help if you need additional information for managing dumps.
Use this task to copy Vital Product Data (VPD) to removable media.
The managed system has VPD that is stored internally. The VPD consists of information such as how much memory is installed, and how many processors are installed. These records can provide valuable information which can be used by remote service and service representatives so that they can help you keep the firmware and software on your managed system up to date.
The information in the VPD file can be used to complete the following types of orders for your managed system:
Using this task, this information can be sent to removable media (diskette, DVD-RAM, or memory key) for use by you or your service provider.
Use the online Help if you need additional information for collecting VPD.
Use this task to display or edit the model, type, machine serial (MTMS) or configuration ID of an enclosure.
The MTMS value or configuration ID for an expansion unit may need to be edited during a replacement procedure.
Use the online Help if you need additional information for editing MTMS.
Use the FSP Failover task to enable a secondary service processor if your managed system's primary service processor fails.
FSP Failover capability is designed to eliminate customer outages due to service processor hardware failures. If a redundant service processor is supported for the current system configuration, use the Setup task to set up FSP Failover for the selected managed system. Use the Initiate task to initiate FSP Failover for the selected managed system.
Capacity on Demand (CoD) tasks activate inactive processors or memory that are installed on your managed server.
Capacity on Demand (COD) allows you to nondisruptively activate (no boot required) processors and memory. Capacity on Demand also gives you the option to temporarily activate capacity to meet intermittent performance needs, to activate additional capacity on a trial basis, and to access capacity to support operations in times of need.
The following are represented in the Capacity on Demand tasks:
Use the Enter CoD Code task to enter any CoD codes that you have obtained for your system.
This code can be any of the following types of CoD codes:
Use the View History Log task to see the CoD history log for your system. The CoD history log contains information about the CoD events that have occurred on your system. The entries are shown in chronological order, starting with the most recent entry. You can see the date and time that each event occurred and a description of each event.
Related HMC CLI commands:
Capacity Upgrade on Demand (CUoD) is permanent capacity for nondisruptive growth.
You can permanently activate inactive processors and memory units by purchasing an activation feature and entering the provided activation code. Capacity Upgrade on Demand (CUoD) enables you to permanently activate one or more inactive processors or memory units without requiring you to restart your server or interrupt your business.
You can order activation features for a new server, a server model upgrade, or an installed server. After you place your order, you will receive a code that activates inactive processors or memory units. For a new server or a server model upgrade, your order can contain one or more activation features for processors or memory units, which results in one or more activation codes. In this case, the activation codes are entered before the server is sent to you.
When you order Capacity Upgrade on Demand (CUoD) activation features for an installed server, you must determine whether you want to permanently activate some or all of your inactive processors or memory units. You must order one or more activation features and then use the resulting one or more activation codes to activate your inactive processors or memory units.
Contact your IBM Business Partner or IBM sales representative to place your order for one or more activation features.
Notes:
Use the View Code Information task to view the information used to generate a CUoD processor activation code for the selected managed system. If you want to save this information to a file, select Save.
Related HMC CLI commands:
On/Off Capacity on Demand (On/Off CoD) is temporary capacity for fluctuating workloads.
You can activate processors or memory units for a number of days, as your business peaks demand, by using inactive resources on a temporary basis. With On/Off CoD, you can temporarily activate and deactivate processors and memory units to satisfy business peaks. After you request that a number of processors or memory units be made temporarily available for a specified number of days, those processors and memory units are available immediately. You can start and stop requests for On/Off CoD, and you can also change the number of resources or days in a running On/Off request. This offering has contract requirements.
To take advantage of On/Off Capacity on Demand (CoD), you must order an On/Off CoD enablement feature. The enablement feature provides the On/Off CoD enablement code that allows you to request temporary activation of inactive processors or memory units by entering the code on your server.
To order On/Off Capacity on Demand (CoD), contact your IBM Business Partner or IBM sales representative. Your IBM Business Partner or IBM sales representative guides you through the completion of the required On/Off CoD contracts with IBM and places a customer order for an On/Off CoD enablement feature.
Use the Manage task to activate or deactivate processors or memory units or to change the number or resources or days in a running On/Off CoD request.
Use the View Capacity Settings task to view:
Use the View Billing Information task to view or save information used to manually report On/Off CoD processor or memory billing information.
Use the View Code Information task to view the information used to generate a On/Off CoD processor or memory enablement code for the selected managed system. If you want to save this information to a file, select Save.
Related HMC CLI commands:
Trial Capacity on Demand is temporary capacity for workload testing or any one time need.
You can evaluate the use of inactive processors, memory, or both, at no charge using Trial CoD. After it is started, the trial period is available for 30 power-on days. This means the trial period advances only while the server is powered on. You can use the HMC to stop a current CoD trial for processors or memory units before the trial automatically expires. If you choose to stop the trial before it expires, you cannot restart it and you forfeit any remaining days.
You can activate your inactive processors or memory for a trial period by obtaining and entering a trial processor code or a trial memory code with Trial Capacity on Demand (CoD).
Before the trial period expires, you must either enter a Capacity Upgrade on Demand activation code to permanently activate the Trial CoD resources, or you must return the Trial CoD resources.
Use the Stop task to terminate Trial CoD.
Use the View Capacity Settings task to view the following settings for the selected managed system:
Use the View Code Information task to view the information used to generate a Trial CoD code for the selected managed system. If you want to save this information to a file, select Save.
Related HMC CLI commands:
Utility Capacity on Demand (Utility CoD) allows you to activate the inactive processors that are installed on your managed system to meet the variable workload demands of your business.
When you use Utility CoD, activated Utility CoD processors are placed in the shared processor pool and are used only as needed by uncapped partitions. If all non-Utility CoD processors in the shared processor pool are being used, and one or more uncapped partitions require additional resources, then the managed system allows the uncapped partitions to use one Utility CoD processor for one minute, and one Utility CoD processor minute of use is recorded. The managed system continues to use this Utility CoD processor and record processor minutes until the Utility CoD processor is no longer needed. The managed system continuously monitors the processor utilization within the shared processor pool. If additional processor resources are needed, the managed system automatically uses additional Utility CoD processors and records processor minutes for those processors. You pay only for the number of processor minutes that the Utility CoD processors are used. Optionally, you may prepay for Utility CoD usage.
Use the Manage Utility CoD task to:
Use the View Capacity Settings task to see current information about Utility CoD, including usage and reporting information.
Use the View Code Information task to view the information used to generate a Utility CoD code for the selected managed system. If you want to save this information to a file, select Save.
Use the View Shared Processor Utilization task to view the distribution and utilization of processors in the shared processor pool.
Related HMC CLI commands:
Reserve Capacity on Demand (CoD) provides prepaid temporary capacity that is automatically used by the server to help meet the demands of business peaks.
With Reserve CoD, you can purchase a reserve capacity prepaid feature that represents a number of processor days. You can then activate the inactive processors using Reserve CoD as your business requires.
The reserve processors are put in the server shared processor pool, where they are used as needed by uncapped partitions. Whenever the capacity of the non-Reserve CoD processors in the shared processor pool reaches the maximum capacity of those processors and is no longer sufficient to support the server workload, then the Reserve CoD processors are used.
When a Reserve CoD processor is used, one processor day is subtracted from the prepaid number of processor days. You pay only for the number of processor days that the reserve processors are actually used. The processors can remain active until all of the reserve processor days that you have paid for have been used.
Because you have already paid for the reserve capacity before you use it, contracts and reporting are not necessary.
Use the View Shared Processor Utilization task to view the distribution and utilization of processors in the shared processor pool.
Related HMC CLI commands:
Advanced POWER Virtualization is a set of comprehensive systems technologies and services designed to enable you to aggregate and manage resources through a consolidated, logical view.
Advanced POWER enables the system for these features:
Use the Enter Activation Code task to enter any Capacity on Demand advanced functions activation codes that you have obtained for your system. Specify the appropriate code in the Code field to activate any of the following on-demand functions:
Use the View History Log task to see the activation history log for Capacity on Demand advanced functions on your system. The history log contains information about the activations of Capacity on Demand advanced functions that have occurred on your system. Capacity on Demand advanced functions include Advanced POWER Virtualization and Enterprise Enablement.
A log entry is created each time an activation code is entered successfully, and an additional log entry is created for each capability that is enabled by the activation code. For each entry in the Capacity on Demand advanced functions activation history log, this table shows the date and time on the system when the entry was logged and a description of the log entry. The entries are shown in chronological order, starting with the most recent entry.
If the history log has wrapped, a message is shown at the bottom of the window. The history log can contain as many as eight activation code entries. (For each activation code entry, an additional log entry is created for each capability that is enabled by the activation code.) When eight activation code entries have been logged to the history log, the next entry causes the history log to wrap (that is, the newest entry overlays the oldest entry).
Use the View Code Information task to view the information used to generate a CoD advanced functions activation code for the selected managed system. If you want to save this information to a file, select Save.
Related HMC CLI commands:
Use the Enterprise Enablement tasks to enter an Enterprise Enablement activation code, view Enterprise Enablement code information, or view a history log of Enterprise Enablement activation activity.
Use the Enter Activation Code task to enter any Capacity on Demand advanced functions activation codes that you have obtained for your system. Specify the appropriate code in the Code field to activate any of the following on-demand functions:
Use the Enter Activation Code task to enter any Capacity on Demand advanced functions activation codes that you have obtained for your system. Specify the appropriate code in the Code field to activate any of the following on-demand functions:
Use the View History Log task to see the activation history log for Capacity on Demand advanced functions on your system. The history log contains information about the activations of Capacity on Demand advanced functions that have occurred on your system. Capacity on Demand advanced functions include Advanced POWER Virtualization and Enterprise Enablement.
A log entry is created each time an activation code is entered successfully, and an additional log entry is created for each capability that is enabled by the activation code. For each entry in the Capacity on Demand advanced functions activation history log, this table shows the date and time on the system when the entry was logged and a description of the log entry. The entries are shown in chronological order, starting with the most recent entry.
If the history log has wrapped, a message is shown at the bottom of the window. The history log can contain as many as eight activation code entries. (For each activation code entry, an additional log entry is created for each capability that is enabled by the activation code.) When eight activation code entries have been logged to the history log, the next entry causes the history log to wrap (that is, the newest entry overlays the oldest entry).
Use the View Code Information task to view the information used to generate a CoD advanced functions activation code for the selected managed system. If you want to save this information to a file, select Save.
Related HMC CLI commands:
Use the Other Advanced Functions tasks to enter an advanced function activation code, view advanced function code information, or view a history log of advanced function activation activity.
Use Enter Activation Code to enter any Capacity on Demand advanced functions activation codes that you have obtained for your system. Specify the appropriate code in the Code field to activate any of the following on-demand functions:
Use the View History Log task to see the activation history log for Capacity on Demand advanced functions on your system. The history log contains information about the activations of Capacity on Demand advanced functions that have occurred on your system. Capacity on Demand advanced functions include Advanced POWER Virtualization and Enterprise Enablement.
A log entry is created each time an activation code is entered successfully, and an additional log entry is created for each capability that is enabled by the activation code. For each entry in the Capacity on Demand advanced functions activation history log, this table shows the date and time on the system when the entry was logged and a description of the log entry. The entries are shown in chronological order, starting with the most recent entry.
If the history log has wrapped, a message is shown at the bottom of the window. The history log can contain as many as eight activation code entries. (For each activation code entry, an additional log entry is created for each capability that is enabled by the activation code.) When eight activation code entries have been logged to the history log, the next entry causes the history log to wrap (that is, the newest entry overlays the oldest entry).
Use the View Code Information task to view the information used to generate a CoD advanced functions activation code for the selected managed system. If you want to save this information to a file, click Save.
Related HMC CLI commands:
Systems Management displays tasks to manage servers, logical partitions, and frames. Use these tasks to set up, configure, view current status, troubleshoot, and apply solutions.
This chapter describes the tasks displayed when a partition is selected.
To launch these tasks, see Launching tasks for managed objects. The following sets of tasks are represented in the tasks pad, tasks menu, or context menu. The tasks listed in the tasks pad change as selections are made in the work area. The context is always listed at the top of the tasks pad in the format Task: Object. These tasks are listed when a partition is selected and the context is Tasks: partition name.
The Properties task displays the selected partition's properties. This information is useful in resource allocation and partition management. These properties include:
Use the Change Default Profile task to change the default profile for the partition.
Select a profile from the drop down list to be the new default profile.
Related HMC CLI commands:
Operations contains the tasks for operating partitions. The following are represented in the Operations tasks.
Use the Activate task to activate a partition on your managed system in the Not Activated state.
A list of profiles is display that are valid to start the selected partition. Select from the list of profiles and click OK to activate the partition. Check Open a terminal window or console to do so.
Use this task to restart the selected logical partition or partitions.
For i5/OS logical partitions, use this window only if you cannot restart the i5/OS logical partition from the command line of the operating system. Using this window to restart an i5/OS logical partition will result in an abnormal IPL.
Choose one of the following options (the Operating System option and the Operating System Immediate option are only enabled if Resource Monitoring and Control (RMC) is up and configured):
Related HMC CLI commands:
Use this task to shut down the selected logical partition or partitions.
For i5/OS logical partitions, use this window only if you cannot shut down the i5/OS logical partition from the command line of the operating system. Using this window to shut down an i5/OS logical partition will result in an abnormal IPL.
Choose from the following options:
Related HMC CLI commands:
Use the Manage Attention LED to activate or deactivate an attention LED on your partition.
All attention LEDs for the partitions on the managed system are listed. Select an LED and choose to activate or deactivate.
Use this task to create a schedule for certain operations to be performed on the logical partition without operator assistance.
Scheduled operations are helpful for situations where automatic, delayed, or repetitious processing of system operations is necessary. A scheduled operation is started at a specified time, without operator assistance to perform the operation. A schedule can be set for one operation or repeated many times.
For example, you could schedule an operation to remove resources from a logical partition or move resources from one logical partition to another.
The Scheduled Operations task displays the following information for each operation:
From the Scheduled Operations window you can:
An operation can be scheduled to occur one time or it can be scheduled to be repeated. You will be required to provide the time and date that you want the operation to occur. If the operation is scheduled to be repeated, you will be asked to select:
The operations that can be scheduled for a logical partition are:
To schedule operations on the HMC:
Use the online Help to get additional information for scheduling an operation.
Use the Delete task to delete the selected partition.
The Delete task deletes the selected partition and all of the partition profiles associated with the partition from the managed system. When you delete a partition, all hardware resources currently assigned to that partition become available to other partitions.
Configuration contains the tasks for configuring your partitions. The following are represented in the Configuration tasks:
Use the Manage Profiles task to create, edit, copy, delete, or activate a profile for the selected partition.
A partition profile contains the resource configuration for the partition. You can modify the processor, memory, and adapter assignments for a profile by editing the profile.
The default partition profile for a logical partition is the partition profile that is used to activate the logical partition if no other partition profile is selected. You cannot delete the default partition profile unless you first designate another partition profile as the default partition profile. The default profile is defined in the status column.
Choose Copy to create an exact copy of the selected partition profile. This allows you to create multiple partition profiles that are nearly identical to one another by copying a partition profile and changing the copies as needed.
Groups are comprised of logical collections of objects. You can report status on a group basis, allowing you to monitor your system in a way that you prefer.
You can also nest groups (a group contained within a group) to provide hierarchical or topology views.
One or more user-defined groups might already be defined on your HMC. Default groups are listed under the Custom Groups node under Server Management. The default groups are All Partitions and All Objects. You can create others, delete the ones that were created, add to created groups, create groups using the pattern match method, or delete from created groups by using the Manage Custom Groups task.
Use the online Help if you need additional information for working with groups.
Use this task to save the current configuration of a logical partition to a new partition profile by entering a new profile name.
This procedure is useful if you change the configuration of a logical partition using dynamic logical partitioning and you do not want to lose the changes when you restart the logical partition. You can perform this procedure at any time after you initially activate a logical partition.
Related HMC CLI commands:
Hardware (Information) tasks are used to display information about the hardware attached to a selected managed system.
The following are represented in the Hardware (Information) tasks:
Use the Adapters tasks to view information about the Host Ethernet Adapters (HEA) or Host Channel Adapters (HCA) for a selected managed system.
A Host Ethernet Adapter (HEA) allows multiple logical partitions to share a single physical Ethernet adapter.
Unlike most other types of I/O devices, you can never assign the HEA itself to a logical partition. Instead, multiple logical partitions can connect directly to the HEA and use the HEA resources. This allows these logical partitions to access external networks through the HEA without having to go through an Ethernet bridge on another logical partition.
Use the Host Ethernet task to display or configure the ports of the physical Host Ethernet Adapters (HEAs) on a selected managed system.
To configure a physical port on an HEA, select the port from the list and select Configure.
Use the online Help for additional information on configuring HEA ports.
Related HMC CLI commands:
Host Channel Adapters provide a managed system with port connections to other InfiniBand devices. That port can be connected to another HCA, a target device, or an InfiniBand switch that redirects the data coming in on one of its ports out to a device attached to another of its ports.
Use the Host Channel task to show a list of the HCAs for the managed system. You can select an HCA from the list to display the current partition usage for the HCA.
From this task you can display:
Related HMC CLI commands:
Use the Switch Network Interface task to display a list of the Switch Network Interface (SNI) adapters for the selected managed system.
Displayed is the SNI adapter handle, the name of the partition to the adapter is assigned, the physical location of the adapter, and the host name or IP address of the adapter.
Dynamic Logical Partitioning (DLPAR) tasks dynamically add or remove processors, memory, and adapters to and from logical partitions.
The following are represented in the Dynamic Logical Partitioning tasks:
Use DLPAR Processor tasks to add or remove processor resources from a logical partition or to move processor resources from one logical partition to another.
Use the Add or Remove task to add processor resources to or remove processor resources from the selected logical partition without restarting the logical partition.
Use the Move task to move processor resources from the selected logical partition to another logical partition without restarting either logical partition.
Use the online Help for more information on adding, removing, or moving processor resources.
Related HMC CLI commands:
Use DLPAR Memory tasks to add or remove memory resources from a logical partition or to move memory resources from one logical partition to another.
Use the Add or Remove task to add memory to or remove memory from the selected logical partition without restarting the logical partition.
Use the Move task to move memory from the selected logical partition to another logical partition without restarting either logical partition.
Use the online Help for more information on adding, removing, or moving processor resources.
Related HMC CLI commands:
Use the DLPAR Physical Adapters tasks to add I/O slots to a logical partition without restarting the partition or to move or remove I/O slots from a logical partition without restarting the partition.
Use the Add task to add I/O slots to a logical partition without restarting the partition. When you add an I/O slot to a logical partition, the I/O adapter in that I/O slot and the devices that are controlled by the I/O adapter can be used by the logical partition. This function is typically used to share infrequently used devices among logical partitions by moving these devices from one logical partition to another.
Use the Move or Remove task to remove I/O slots from a logical partition or move I/O slots between logical partitions without restarting the logical partitions. When you remove an I/O slot from a logical partition, the I/O adapter in that I/O slot and the devices that are controlled by the I/O adapter are also removed from the logical partition. If you choose to move the I/O slot to another logical partition, the I/O adapter and the devices that are controlled by the I/O adapter are also moved to the other logical partition. This function is typically used to share infrequently used devices among logical partitions by moving these devices from one logical partition to another.
It is recommended that you vary off the I/O slot and all I/O adapters and devices connected to the I/O slot before you remove the I/O slot from the logical partition.
Related HMC CLI commands:
This task displays a list of all of the virtual adapters that currently exist for this logical partition or partition profile.
Use this task to create, change, or remove a virtual adapter on a logical partition or in a partition profile.
From this task you can:
Use the online Help for more information on managing virtual adapters.
Related HMC CLI commands:
Use Host Ethernet tasks to add Logical Host Ethernet Adapter (LHEA) logical ports dynamically to a running logical partition.
Use the Add task to add LHEA logical ports dynamically to a running logical partition. These logical ports allow the logical partition to access and use the physical port resources on a physical Host Ethernet Adapter (HEA).
Some operating system or system software versions do not allow you to add logical ports dynamically. Consult the documentation for the operating system or system software for more information.
To add logical ports dynamically to the logical partition, select the HEA whose resources you want to use, select the physical port for which you want to create a logical port, and click Configure. You can then configure the logical port and return to this window. If you change your mind about adding a logical port to the logical partition, select the physical port that corresponds to the logical port and click Reset. You can then configure a different logical port for that physical port.
When you are done adding logical ports to the running logical partition, click OK.
Use the Move or Remove task to move LHEA logical ports dynamically from the selected logical partition.
These logical ports allow the logical partition to access and use the physical port resources on a physical HEA. You can move the logical ports dynamically to another running logical partition, or you can leave the logical ports as unassigned.
Some operating system or system software versions do not allow you to move or remove logical ports dynamically. Consult the documentation for the operating system or system software for more information.
To remove logical ports dynamically from the logical partition, select the HEA whose logical ports you want to remove, select the physical port whose logical ports you want to remove and click OK.
To move logical ports dynamically from the logical partition to another running logical partition, select the HEA whose logical ports you want to remove, select the physical port whose logical ports you want to move, select the destination logical partition in Logical Partition, and click OK.
Related HMC CLI commands:
Use the Open Terminal Window task to open a terminal window to the operating system running on the selected partition.
Use the Close Terminal Connection task to close the connection.
Use the Open Shared 5250 Console task to open a shared console with an i5/OS partition.
Use the Open Dedicated 5250 Console task to open a dedicated console with an i5/OS partition.
Problem Analysis on the HMC automatically detects error conditions and reports to you any problem that requires service to repair it. These problems are reported to you as serviceable events. Use the Manage Events task to view specific events for selected systems. However, if you notice a problem occurred or you suspect a problem is affecting the system but Problem Analysis has not reported it to you, use the Create Serviceable Event task to report the problem to your service provider.
The following are represented in the Serviceability tasks:
Problems on your managed system are reported to the HMC as serviceable events. The Manage Serviceable Events task allows you view the problem, manage problem data, call home the event to your service provider, or repair the problem.
To set the criteria for the serviceable events you to view:
The Serviceable Events Overview panel displays all of the events that match your criteria. The information displayed in the compact table view includes:
The full table view includes more detailed information, including reporting MTMS, first reported time, and serviceable event text.
Select a serviceable event and use the Selected drop down menu to:
Use the online Help if you need additional information on managing serviceable events.
Use the Reference Code History task to view reference codes that have been generated for the selected logical partition. Reference codes are diagnostic aids that help you determine the source of a hardware or operating system problem.
By default, only the most recent reference codes that the logical partition has generated are displayed. To view more reference codes, enter the number of reference codes that you want to view into View history and click Go. The window displays that number of the latest reference codes, with the date and time at which each reference code was generated. The window can display up to the maximum number of reference codes stored for the logical partition.
This task displays the available virtual control panel functions for the partition selected. The tasks are:
Systems Management displays tasks to manage servers, logical partitions, and frames. Use these tasks to set up, configure, view current status, troubleshoot, and apply solutions.
This chapter describes the tasks used when a frame is selected.
To launch these tasks, see Launching tasks for managed objects. The following sets of tasks are represented in the tasks pad, tasks menu, or context menu. The tasks listed in the tasks pad change as selections are made in the work area. The context is always listed at the top of the tasks pad in the format Task: Object. These tasks are listed when a managed system is selected and the context is Tasks: Frame Name.
The Properties task displays the selected frame properties. These properties include:
Use the Update Password task to update HMC access and Advanced System Management Interface (ASMI) passwords on the managed system.
The first time you access a managed system using an HMC, the system prompts you to enter passwords for each of the following:
If you are using an HMC to access the managed system before all required passwords have been set, enter the appropriate password for each password that is presented in the Update Password task.
If another HMC subsequently needs access to this managed system, upon attempting to access this HMC the user is presented with the Update Password Failed Authentication window, which will prompt for the HMC access password you entered.
In the event that the HMC access password changes while you are logged in to the managed system, your HMC will discover that it can no longer authenticate after it attempts to reconnect to that managed system. This will result in a state of Failed Authentication for that managed system. You will be required to enter the new password before any actions can be performed.
Operations contains the tasks for operating frames. The following are represented in the Operations tasks.
Use the Initialize task to initialize a frame.
When you initialize a managed frame, all of the frames managed by the HMC are powered on. As each individual frame is powered on, the I/O units that are contained within the frame are powered on as well. When all the I/O units for the frame have been powered on, then the managed systems that are contained within the frame are powered on. The complete initialization process may take several minutes to complete.
Note: Managed systems that are already powered on will not be affected (meaning they will not be powered off and back on again).
Use the Rebuild task to rebuild frame information on the HMC.
Updating, or rebuilding, the frame acts much like a refresh of the frame information. Rebuilding the frame is useful when the system's state indicator in the Work pane of the HMC is shown as Incomplete. The Incomplete indicator signifies that the HMC cannot gather complete resource information from the managed system within the frame.
No other tasks can be performed on the HMC during this process, which may take several minutes.
Use the Change Password task to change the HMC access password on the selected managed frame. After the password is changed, you must update the HMC access password for all other HMCs from which you want to access this managed frame.
Enter the current password. Then enter a new password and verify it by entering it again.
Related HMC CLI commands:
Use the Power On/Off IO Unit task to power off an IO unit.
Only units or slots that reside in a power domain can be powered off. The corresponding power on/off buttons will be disabled for location codes that are not controllable by the HMC.
Configuration contains the tasks for configuring your frame. The following are represented in the Configuration tasks:
Groups are comprised of logical collections of objects. You can report status on a group basis, allowing you to monitor your system in a way that you prefer.
You can also nest groups (a group contained within a group) to provide hierarchical or topology views.
One or more user-defined groups might already be defined on your HMC. Default groups are listed under the Custom Groups node under Server Management. The default groups are All Partitions and All Objects. You can create others, delete the ones that were created, add to created groups, create groups using the pattern match method, or delete from created groups by using the Manage Custom Groups task.
Use the online Help if you need additional information for working with groups.
Connections tasks allow you to view the HMC connection status to frames or reset those connections.
Use the Bulk Power Assembly Status task to view the state of the connection from the Hardware Management Console (HMC) to side A and side B of the bulk power assembly. The HMC will operate normally with a connection to either side A or side B. However, for code update operations and some concurrent maintenance operations, the HMC needs connections to both sides.
Displayed are:
If the status is not Connected, the Connection status may be:
Use the Reset task to reset the connection between the HMC and the selected managed frame.
When you reset the connection with a managed frame, the connection is broken and then reconnected. Reset the connection with the managed frame if the managed frame is in a No Connection state and you have verified that the network settings are correct on both the HMC and the managed frame.
Hardware (Information) tasks are used to display information about the hardware attached to a selected managed frame.
The following are represented in the Hardware (Information) tasks:
This task displays the current RIO topology for the selected managed frame and any discrepancies between the current topology and the last valid topology.
High Speed Link (HSL), also known as Remote I/O (RIO), resources provide the connection between system I/O busses and the system processor. HSL/RIO resources are normally configured in loops with the system unit having an HSL/RIO controller resource that handles routing of the data between the system processor and the system I/O busses. System I/O busses connect to the loop with HSL I/O adapter or RIO adapter resources.
Use this task to display the current RIO topology of the selected managed system. Current Topology displays the current topology. Any discrepancies between the current topology and the last valid topology are identified as errors. The following information is shown:
Problem Analysis on the HMC automatically detects error conditions and reports to you any problem that requires service to repair it. These problems are reported to you as serviceable events. Use the Manage Serviceable Events task to view specific events for selected systems. Use the Hardware tasks to add, remove, or exchange a Field Replaceable Unit (FRU).
The following are represented in the Serviceability tasks:
Problems on your managed frame are reported to the HMC as serviceable events. The Manage Serviceable Events task allows you view the problem, manage problem data, call home the event to your service provider, or repair the problem.
To set the criteria for the serviceable events you to view:
The Serviceable Events Overview panel displays all of the events that match your criteria. The information displayed in the compact table view includes:
The full table view includes more detailed information, including reporting MTMS, first reported time, and serviceable event text.
Select a serviceable event and use the Selected drop down menu to:
Use the online Help if you need additional information on managing serviceable events.
These tasks are used to add, exchange, or remove hardware from the managed frame. From the hardware tasks you can display a list of installed FRUs or enclosures and their locations. Select a FRU or an enclosure and launch a step-by-step procedure to add, exchange, or remove the unit.
Hardware tasks include:
Use the Add FRU task to locate and add a Field Replaceable Unit (FRU).
To add a FRU:
Use the Add Enclosure task to locate and add an enclosure.
To add an enclosure:
Use the Exchange FRU task to exchange one FRU with another.
To exchange a FRU:
Use the Exchange Enclosure task to exchange one enclosure for another.
To exchange an enclosure:
Use the Remove FRU task to remove a FRU from your managed system.
To remove a FRU:
Use the Remove Enclosure task to remove an enclosure.
To remove an enclosure:
System Plans displays the tasks used to record or import specifications for logical partitions, partition profiles, or hardware specifications on a chosen system.
To display the tasks available for a system plan, select a system plan from the System Plan work pane table. The following tasks are available:
Related HMC CLI commands:
This task is used to review the detailed information in the selected system plan.
The System Plan Viewer consists of four main areas:
Use the navigation tree to determine which aspects of the system plan to view. Some levels of the tree can be expanded or collapsed to reveal more entries. Entries in the tree with a + (plus) symbol contain further entries and are expandable by clicking on the + symbol. When an entry is expanded, the + symbol changes to a - (minus) symbol. Clicking the - symbol collapses the entry and hides any further entries that it contains. Clicking on an entry in the tree displays the contents for that entry in the contents pane.
The first level of the navigation tree is the system plan name. You must select the + symbol next to the name to expand the file and view the main entries within the tree for the system plan.
Use the online Help for more information on viewing a system plan.
Related HMC CLI commands:
This task is used to create a new system plan for a system that this HMC manages. The new system plan contains specifications for the logical partitions and partition profiles of the managed system that you used to create the plan.
The new system plan also can contain hardware information that the HMC is able to obtain from the selected managed system. However, the HMC might not be able to detect all system hardware and partition settings. For example, the HMC is not able to detect the types of disk drives installed on the managed system unless the HMC uses Resource Monitoring and Control (RMC) to monitor resources on the managed system.
To maximize the information that the HMC can obtain from the managed system, power on the managed system and activate the logical partitions on the managed system before creating the new system plan.
When you use the HMC to create a system plan for a managed system, you can capture partition configuration information and a limited amount of associated hardware configuration information. Additionally, you can set up Resource Monitoring and Control (RMC) prior to creating a system plan to capture more detailed information. Although it may cause the creation of the system plan to take several more minutes to finish processing, by using RMC you can capture disk drive and tape drive configuration information for a managed system in the system plan.
Use the online Help for more information on creating a system plan.
Related HMC CLI commands:
This task is used to select the system plan that you want to deploy and the name of the managed system on which you want to deploy the plan.
This task uses the Deploy System Plan wizard to perform the following actions, depending on the contents of the system plan:
Use the online Help for more information on deploying a system plan.
Related HMC CLI commands:
This task is used to export a system plan to other systems or other HMCs.
You have three options for exporting the selected system-plan file:
Use the online Help for more information on exporting a system plan.
This task is used to import a system plan to other systems or other HMCs.
You can save this system plan and import the plan on other systems that this HMC manages that have hardware that is identical to the hardware in the system plan. You can import the system plan on another HMC and use it to deploy the system plan to other systems the target HMC manages that have hardware that is identical to the hardware in the system plan.
You can also import a system plan created using the System Planning Tool (SPT) at http://www.ibm.com/systems/support/tools/systemplanningtool/. The SPT is available to assist you in system planning, design, validation and to provide a system validation report that reflects your system requirements while not exceeding system recommendations. The SPT is a PC-based browser application designed to be run in a standalone environment. The SPT emulates an LPAR configuration and validates that the planned partitions are valid. It allows you to test the placement of hardware within the system to ensure that the placement is valid. When you have prepared your partitioning plan using the SPT, you can save this plan in a system plan file. You can import this file into your HMC and deploy the system plan to a managed system that is managed by the HMC. When you deploy the system plan, the HMC creates the logical partitions from the system plan on the managed system.
You can import a system-plan file from one of three sources:
Use the online Help for more information on importing a system plan.
This task is used to permanently remove the specified system plan from the HMC.
Use the online Help for more information on removing a system plan.
Related HMC CLI commands:
This chapter alphabetically describes the tasks that are available on the Hardware Management Console (HMC) for the HMC Management tasks.
To open these tasks, see HMC Management.
This task backs up (or archives) the data that is stored on your HMC hard disk that is critical to support HMC operations.
You should back up the HMC data after changes have been made to the HMC or information associated with logical partitions.
The HMC data stored on the HMC hard drive can be saved to a DVD-RAM on a local system, a remote system mounted to the HMC file system (such as NFS), or sent to a remote site using File Transfer Protocol (FTP).
Using the HMC, you can back up all important data, such as the following:
To back up the HMC critical data:
Use the online Help if you need additional information for backing up the HMC data.
Related HMC CLI commands:
This task enables you to change the time and date of the battery-operated HMC clock and to add or remove time servers for the Network Time Protocol (NTP) service.
Use this task:
To change the date and time:
To change the time server information:
Use the online Help if you need additional information for changing the date and time of the HMC or for adding or removing time servers for the Network Time Protocol (NTP) service.
Related HMC CLI commands:
This task sets the language and location for the HMC. After you select a language, you can select a locale associated with that language.
The language and locale settings determine the language, the character set, and other settings specific to the country or region (such as formats for date, time, numbers, and monetary units). Changes made in the Change Language and Locale window affect only the language and locale for the HMC itself. If you access the HMC remotely, the language and locale settings on your browser determine the settings that the browser uses to display the HMC interface.
To change the language and locale on the HMC:
Use the online Help if you need additional information for changing the language and locale of the HMC.
Related HMC CLI commands:
This task allows you to view the current network information for the HMC and to change network settings.
The Gateway address is the route to all networks. The default gateway address (if defined) informs this HMC where to send data if the target station does not reside on the same subnet as the source. If your machine can reach all stations on the same subnet (usually a building or a sector within a building), but cannot communicate outside the area, it is usually because of an incorrectly configured default gateway.
You can assign a specific LAN to be the Gateway device or you can choose “any.”
You can select Enable 'routed' to start the routed daemon, which allows it to run and allows any routing information to be exported from the HMC.
Use the online Help to get additional information for customizing the network settings.
Related HMC CLI commands:
This task enables you to customize settings that control how the HMC interface appears. You can display or hide certain user interface components and icons, display or hide specific navigation nodes, and determine whether or not to save user interface settings changes.
To change user interface settings:
Use the online Help to get additional information for changing the user interface settings.
This task allows you to change your existing password used for logging onto the HMC. A password verifies your user ID and your authority to log in to the console.
To change your password:
Use the online Help if you need additional information for changing your password.
Related HMC CLI commands:
This task allows you to customize the welcome message or to display a warning message that appears on the Welcome window before you log onto the HMC. You can use this text to notify users of certain corporate policies or security restrictions applying to the system.
To create a message:
Use the online Help to get additional information about displaying a message before logging onto the HMC.
Related HMC CLI commands:
This task formats a DVD-RAM, diskette, or USB 2.0 Flash Drive Memory Key.
You can use this task to format the following DVD-RAMs:
You can format a diskette by supplying a user-specified label.
To format a DVD-RAM, diskette, or USB 2.0 Flash Drive Memory Key:
Use the online Help if you need additional information for formatting a DVD-RAM, diskette, or USB 2.0 Flash Drive Memory Key.
Use the KDC Configuration task to view the Key Distribution Center (KDC) servers that are used by this HMC for Kerberos remote authentication.
From this task you can:
Kerberos is a network authentication protocol designed to provide strong authentication for client/server applications by using secret-key cryptography.
Under Kerberos, a client (generally either a user or a service) sends a request for a ticket to the Key Distribution Center (KDC). The KDC creates a ticket-granting ticket (TGT) for the client, encrypts it using the client's password as the key, and sends the encrypted TGT back to the client. The client then attempts to decrypt the TGT, using its password. If the client successfully decrypts the TGT (i.e., if the client gave the correct password), it keeps the decrypted TGT, which indicates proof of the client's identity.
The tickets have a time availability period. Kerberos requires the clocks of the involved hosts to be synchronized. If the HMC clock is not synchronized with the clock of KDC server, authentication will fail.
A Kerberos realm is an administrative domain, site, or logical network that uses Kerberos remote authentication. Each realm uses a master Kerberos database that is stored on a KDC server and that contains information about the users and services for that realm. A realm might also have one or more slave KDC servers, which store read-only copies of the master Kerberos database for that realm.
To prevent KDC spoofing, the HMC can be configured to use a service key to authenticate to the KDC. Service key files are also known as keytabs. Kerberos verifies the TGT requested was issued by the same KDC that issued the service key file for the HMC. Before you can import a service key file into an HMC, you must generate a service key for the host principal of the HMC client.
Note: For MIT Kerberos V5 *nix distributions, create a service key file by running the kadmin utility on a KDC and using the ktadd command. Other Kerberos implementations may require a different process to create a service key.
You can import a service key file from one of these sources:
To use Kerberos remote authentication for this HMC, you must complete the following:
# ktutil
ktutil: rkt /etc/krb5.keytab
ktutil: l
slot KVNO Principal
---- ---- ---------------------------------------------------------------------
1 9 host/hmc1.example.com@EXAMPLE.COM
2 9 host/hmc1.example.com@EXAMPLE.COM
Related HMC CLI commands:
To view existing KDC Servers on your HMC, open the KDC Configuration task from the HMC Management work pane. If no servers exist and NTP has not yet been enabled, a warning panel will display. Enable the NTP service on the HMC and configure a new KDC server as desired.
Related HMC CLI commands:
To modify existing KDC Server parameters:
Related HMC CLI commands:
To add a new KDC server:
To modify the default values for ticket lifetime or clock skew, see Modify KDC Server.
Related HMC CLI commands:
Kerberos authentication on the HMC remains enabled until all KDC servers are removed.
To remove a KDC server:
Before you can import a service key file into an HMC, a service key file must first be created on the Kerberos server for the HMC host. The service key file contains the host principal of the HMC client, for example, host/example.com@EXAMPLE.COM. In addition to KDC Authentication, the host service key file is used to enable password-less SSH (Secure Shell) login using GSSAPI.
Note: For MIT Kerberos V5 *nix distributions, create a service key file by running the kadmin utility on a KDC and using the ktadd command. Other Kerberos implementations may require a different process to create a service key.
To import a service key:
Implementation of the service key file will not take effect until the HMC is rebooted. For information on rebooting the HMC, see Shut Down or Restart.
To remove the service key from the HMC:
You must reboot the HMC after removing the service key. Failure to reboot may cause login errors. For information on rebooting the HMC, see Shut Down or Restart.
Change Hardware Management Console configuration information.
To change remote access settings:
chhmc -c {ssh | xntp} -s {enable | disable} [--help]
To add or remove an entry in the syslog configuration file:
chhmc -c syslog -s {add | remove} {-a IP-address | -h host-name} [--help]
To add or remove an entry in the network time protocol configuration file:
chhmc -c xntp -s {add | remove} {-a IP-address | -h host-name} {--ntpversion 1 | 2} [-nm network-mask] [-i interface] [--help]
To configure whether keyboard mapping configuration will occur at the next reboot:
chhmc -c kbdcfg -s {enable | disable} [--help]
To configure the network as a startup device:
chhmc -c netboot -s {enable | disable} [--help]
To configure an alternate disk partition on HMC as a startup device:
chhmc -c altdiskboot -s {enable | disable} --mode {install | upgrade} [--help]
To permit or deny IP addresses from utilizing HMC services:
chhmc -c {ssh | service} -s {add | remove} -a IP-address [-nm network-mask] [-i interface] [--help]
If -nm is omitted, the default network mask will be 255.255.255.255.
If -i is omitted, the rule will be applied to all interfaces.
To add or remove entries from the DNS server search order or the domain suffix search order:
chhmc -c network -s {add | remove} [-ns DNS-server] [-ds domain-suffix] [--help]
To change network settings for a specific network interface:
chhmc -c network -s modify -i interface [-a IP-address] [-nm network-mask] [--lparcomm {on | off}] [--help]
To change other network settings:
chhmc -c network -s modify [-h host-name] [-d network-domain-name] [-g gateway] [--help]
To change the locale for the HMC:
chhmc -c locale -s modify -l locale [--help]
To change the HMC date and time, or time zone:
chhmc -c date -s modify [--datetime date-time] [--clock {local | utc}] [--timezone {time-zone | none}] [--help]
To setup a Kerberos realm for the first time:
chhmc -c kerberos -s add [--realm EXAMPLE.COM] [--h kdc1.example.com] [--help]
To remove a Kerberos realm:
chhmc -c kerberos -s remove [--realm EXAMPLE.COM] [--h kdc1.example.com] [--help]
To change the Kerberos default realm:
chhmc -c kerberos -s modify [--defaultrealm EXAMPLE2.COM] [--help]
To change the Kerberos clock skew (in seconds):
chhmc -c kerberos -s modify [--clockskew 240] [--help]
To change the Kerberos ticket lifetime (Kerberos lifetime string = Integer followed by one of s seconds, m minutes, h hours, or d days):
chhmc -c kerberos -s modify [--ticketlifetime 1d12h30m] [--help]
chhmc changes Hardware Management Console (HMC) configuration information, such as remote access settings and network settings.
For the new locale to take effect for the local HMC console, you must log off the console and log back on. For the new locale to take effect for the HMC command line, you must reboot the HMC.
MMDDhhmm[[CC]YY][.ss]
where MM is the month, DD is the day, hh is the hour in 24 hour format, mm is the minutes, CC is the century, YY is the year, and ss is the seconds.
This option is required when the --clock option is specified.
You must reboot the HMC after setting the date and time.
You must reboot the HMC after setting the time zone.
List Hardware Management Console configuration information.
lshmc {-b | -l | -L | -n | -r | -v | -V} [-F [attribute-names] [--header]] [--help]
lshmc lists Hardware Management Console (HMC) configuration information. This command can be used to list the BIOS level, current locale, supported locales, network settings, remote access settings, Vital Product Data (VPD) information, and version information for the HMC.
This option cannot be specified with the -l, -L, -n, -r, -v, or -V options.
This option cannot be specified with the -b, -L, -n, -r, -v, or -V options.
This option cannot be specified with the -b, -l, -n, -r, -v, or -V options.
This option cannot be specified with the -b, -l, -L, -r, -v, or -V options.
This option cannot be specified with the -b, -l, -L, -n, -v, or -V options.
This option cannot be specified with the -b, -l, -L, -n, -r, or -V options.
This option cannot be specified with the -b, -l, -L, -n, -r, or -v options.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
This task uses a wizard to set up your system and HMC.
Use the online Help or see the Installation and Configuration Guide for the Hardware Management Console, SA76-0084, if you need additional information using the HMC setup wizard.
This task is used to start a session to another Hardware Management Console (HMC).
Use the online Help if you need additional information for contacting another HMC.
This task is used to lock the HMC screen.
This task allows you to end the current user session and logs off the HMC or it allows you to disconnect while your tasks continue running. If you disconnect, you can reconnect at a later time to continue working. However, a disconnected session is eventually ended. (This is because disconnected sessions exist only while the HMC application is running. If the HMC is restarted or the console is shut down or rebooted, all session information is lost.) If you log off, this means you no longer need access to the HMC. Logging off the console does not affect the status of the managed systems.
To log off or disconnect from the HMC:
If you chose to disconnect rather than logoff, when you login again, the Choose a Disconnected Session window appears. You can do one of the following:
Use this task to manage the certificates used on your HMC. It provides the capability of getting information on the certificates used on the console. This task allows you to create a new certificate for the console, change the property values of the certificate, and work with existing and archived certificates or signing certificates.
All remote browser access to the HMC must use Secure Sockets Layer (SSL) encryption. With SSL encryption required for all remote access to the HMC, a certificate is required to provide the keys for this encryption. The HMC provides a self-signed certificate that allows this encryption to occur.
To manage your certificates:
Use the online Help if you need additional information for managing your certificates and see Appendix B. Remote operations for more information on remotely accessing the HMC.
This task enables or disables customized data replication. Customized data replication allows another HMC to obtain customized console data from or send data to this HMC.
The following types of data can be configured:
For more detailed information on customizing console data for data replication, see Appendix C. Customizable data replication.
Use the online Help to get additional information for enabling or disabling customizable data replication.
Use this task to define and customize user roles.
A user role is a collection of authorizations. A user role can be created to define the set of tasks allowed for a given class of user (task roles) or it can be created to define the set of managed objects that are manageable for a user (managed resource roles). Once you have defined or customized the user roles you can use the Manage User Profiles and Access task to create new users with their own permissions. (See Manage User Profiles and Access.)
The predefined managed resource roles include:
The predefined task roles include:
To customize managed resource roles or task roles:
or
To copy, remove, or modify an existing role, select the object you want to customize, click Edit from the menu bar, then click Copy..., Remove, or Modify....
Use the online Help to get additional information for customizing managed resource roles and task roles.
Related HMC CLI commands:
Use this task to manage your system users that log on to the HMC. A user profile is a combination of a user ID, server authentication method, permissions, and a text description. Permissions represent the authority levels assigned to the user profile for the objects the user has permission to access.
Users can be authenticated using local authentication on the HMC or by using Kerberos remote authentication. For more information on setting up Kerberos authentication on the HMC, see KDC Configuration.
If you are using local authentication, the user ID and password are used to verify a user's authorization to log on the HMC. The user ID must start with an alphabetic character and consist of 1 to 32 characters. The password has the following rules:
If you are using Kerberos authentication, specify a Kerberos remote user ID.
The user profile includes managed resource roles and task roles that are assigned to the user. The managed resource roles assign permissions for a managed object or group of objects and the task roles define the access level for a user to perform on a managed object or group of objects. You can choose from a list of available default managed resource roles, task roles, or customized roles created by using the Manage Task and Resource Roles task.
See Appendix A. HMC tasks and user roles/IDs for a listing of all the HMC tasks and the predefined default user IDs that can perform each task.
The default managed resource roles include:
The default task roles include:
To add or customize a user profile:
From the User Profiles window, if the user ID already exists in the window, select the user ID from the list, and then point to User on the menu bar and when its menu is displayed, click Modify.... The Modify User window is displayed.
Use the online Help if you need additional information for creating, modifying, copying, or removing a user profile.
Related HMC CLI commands:
This task displays the logged on users and the tasks they are running.
Or, you can choose to switch to another task or end a task by selecting the task from the Running Tasks list, then click Switch To or Terminate.
Use this task to open a 5250 emulator session so you can communicate with an i5/OS logical partition.
Use this task to acquire a command line session.
To open a restricted shell terminal:
This task is used to enable remote command execution using the ssh facility.
See Appendix B. Remote operations for more information.
This task is used to allow the HMC to be accessed at a remote workstation through a web browser.
To enable the HMC remote access:
Use the online Help to get additional information for allowing remote access to the HMC.
A Remote Virtual Terminal connection is a terminal connection to a logical partition from another remote HMC. Use this task to enable Remote Virtual Terminal access for remote clients.
Use the online Help to get additional information for enabling a remote terminal connection.
This task is used to select a remote repository for restoring critical backup data for the HMC.
Use the online Help if you need additional information about restoring critical backup data for this HMC.
Related HMC CLI commands:
This task uses a wizard to save upgrade data to selected media. This data consists of files that were created or customized while running the current software level. Saving this data to selected media is performed prior to an HMC software upgrade.
Use the online Help if you need additional information for saving upgrade data.
Related HMC CLI commands:
Use this task to create a schedule for certain operations to be performed on the HMC itself without operator assistance.
Scheduled operations are helpful for situations where automatic, delayed, or repetitious processing of system operations is necessary. A scheduled operation is started at a specified time, without operator assistance to perform the operation. A schedule can be set for one operation or repeated many times.
For example, you could schedule a backup of important HMC information to DVD to occur once, or set up a repeating schedule.
The Scheduled Operations task displays the following information for each operation:
From the Scheduled Operations window you can:
An operation can be scheduled to occur one time or it can be scheduled to be repeated. You will be required to provide the time and date that you want the operation to occur. If the operation is scheduled to be repeated, you will be asked to select:
The operation that can be scheduled for the HMC is:
To schedule operations on the HMC:
Use the online Help to get additional information for scheduling an operation.
This task enables you to shut down (power off the console) or to restart the console.
Use the online Help if you need additional information about shutting down or restarting the HMC.
Related HMC CLI commands:
This task displays network diagnostic information for the console's TCP/IP connection. It also allows you to send an echo request (click Ping) to a remote host.
To view information concerning the networking configuration on this HMC:
Use the online Help to get additional information on your console's network information.
Related HMC CLI commands:
This task allows you to view information about using the HMC. A different fact or tip is displayed each time you log in.
The Tip of the Day window is displayed as long as Show tips each time you log on is selected on the window. You can also look at additional information by clicking Previous Tip or Next Tip.
To prevent this window from displaying each time you log in you can deselect Show tips each time you log on, then click Close.
To access this task other than having it appear as you log in to the HMC:
This task enables you to view a record of system events occurring on the HMC. System events are individual activities that indicate when processes occur, begin and end, succeed or fail.
Use the online Help for additional information about viewing HMC events.
Related HMC CLI commands:
Use this task to view the Licensed Internal Code (LIC) that you have agreed to for this HMC. This task is displayed when you initially start the HMC.
This task is used to display a tree view of the network nodes known to this Hardware Management Console. Examples of such nodes are managed systems, logical partitions, storage, and other Hardware Management Consoles.
To view the network topology:
Use the online Help if you need additional information for viewing the network topology of the Hardware Management Console.
This chapter alphabetically describes the tasks that are available on the Hardware Management Console (HMC) for the Service Management tasks.
To open these tasks, see Service Management.
This task reports problems that occurred on your Hardware Management Console to the service provider (for example, the mouse does not work) or lets you test problem reporting.
Submitting a problem is dependent upon whether you have customized this Hardware Management Console to use the Remote Support Facility (RSF) and if it is authorized to automatically call for service. If so, the problem information and service request is sent to the service provider automatically with a modem transmission.
To report a problem on your Hardware Management Console:
To test problem reporting from the Report a Problem window:
Use the online Help if you need additional information for reporting a problem or testing if problem reporting works.
This task formats a DVD-RAM, diskette, or USB 2.0 Flash Drive Memory Key.
You can use this task to format the following DVD-RAMs:
You can format a diskette by supplying a user-specified label.
To format a DVD-RAM, diskette, or USB 2.0 Flash Drive Memory Key:
Use the online Help if you need additional information for formatting a DVD-RAM, diskette, or USB 2.0 Flash Drive Memory Key.
This task allows you to load or reload serviceable events from an XML file.
This task configures the timers that connection monitoring uses to detect outages and enables or disables connection monitoring for selected machines.
You can view and, if authorized, change connection monitoring settings by machine. Connection monitoring generates serviceable events when communication problems are detected between the HMC and managed systems. If you disable connection monitoring, no serviceable events are generated for networking problems between the selected machine and this HMC.
To monitor the connections:
Use the online Help if you need additional information about connection monitoring.
This task enables you to customize the customer information for the HMC.
The Manage Customer Information window displays the following tabs for providing input:
To customize your customer information:
Use the online Help to get additional information about customizing your account information.
This task manages procedures for dumps of the selected system.
To manage a dump:
From Selected on the menu bar:
From Actions on the menu bar:
From Status on the menu bar, you can view the offload progress of the dump.
Use the online Help to get additional information for managing dumps.
Related HMC CLI commands:
This task allows you to request authorization for Electronic Service Agent. Electronic Service Agent associates your system with a user ID and allows access to system information through the Electronic Service Agent facility. This registration is also used by your operating system to automate service processes for your AIX or i5/OS operation system.
To register a user ID:
Use the online Help if you need additional information for registering a customer user ID with the eService web site.
This tasks allows your service provider to temporarily access your local console, such as the HMC, or the partitions of a managed system.
Use the online Help if you need additional information on managing the inbound connectivity.
This task allows you to customize the means for outbound connectivity for the HMC to use to connect to remote service.
You can configure this HMC to attempt connections through the local modem, Internet, Internet Virtual Private Network (VPN), or through a remote pass-through system. Remote service is a two-way communication between the HMC and the IBM Service Support System for the purpose of conducting automated service operations. The connection can only be initiated by the HMC. IBM Service Support System cannot and never attempts to initiate a connection to the HMC.
To customize your connectivity information:
Use the online Help if you need additional information for customizing outbound connectivity information.
This task enables or disables the Electronic Service Agent Connection Manager function and specifies the port location for the connection. Electronic Service Agent Connection Manager allows POWER4 systems to use Electronic Service Agent to call home to transmit service and system information to IBM by specifying the port used for connectivity for a single, secure connection.
Use the online Help if you need additional information for enabling or disabling Electronic Service Agent.
This task enables you to manage remote connections.
The HMC manages remote connections automatically. It puts requests on a queue and processes them in the order in which they are received. However, this task allows you to manage the queue manually, if necessary. You can stop transmissions, move priority requests ahead of others, or delete requests.
To manage remote connections:
Use the online Help if you need additional information for manually managing remote connections.
This task views or manages call-home requests that the console has submitted.
Use the online Help if you need additional information for manually managing remote connections.
This task adds email addresses that notify you when problem events occur on your system and configures how you want to receive notification of system events from the Electronic Service Agent.
To set up notification:
Use the online Help if you need additional information for managing serviceable events notification.
Related HMC CLI commands:
This task allows you to select the criteria for the set of serviceable events you want to view. When you finish selecting the criteria, you can view the serviceable events that match your specified criteria.
To set the criteria for the serviceable events you to view:
Use the online Help if you need additional information managing events.
Related HMC CLI commands:
This task allows you enable or disable the call-home state for managed systems.
By enabling the call-home state for a managed system this causes the console to automatically contact a service center when a serviceable event occurs. When a managed system is disabled, your service representative is not informed of serviceable events.
To manage call-home for the system(s):
Use the online Help if you need additional information for managing serviceable events notification.
Use this task to transmit service information.
Use the online Help for additional information about transmitting service information.
Related HMC CLI commands:
Updates displays tasks to manage Licensed Internal Code (LIC) on your HMC, managed system, power subsystem, or I/O adapters.
Use the Update HMC button to update Licensed Internal Code on the HMC. Before updating LIC on the HMC, see Update HMC.
Other tasks are used to update managed system, power subsystem, and I/O adapter LIC. To launch these tasks, see Launching tasks for managed objects. The following sets of tasks are represented in the tasks pad, tasks menu, or context menu. The tasks listed in the tasks pad change as selections are made in the work area. The context is always listed at the top of the tasks pad in the format Task: Object.
To display the tasks:
When the Updates node is selected in the navigation pane, current code levels for the HMC are displayed in the work pane.
Under HMC Code level is displayed:
The Fix Central web site at http://www.ibm.com/eserver/support/fixes offers online media ordering, installation instructions and related technical information on code updates of the HMC. Before updating the HMC code level, verify the current levels on your HMC and check on the web site to determine if an update is needed or recommended.
Before updating the HMC code level, you should:
Depending on the complexity of the fix you are applying, you may want to:
Once the tasks above have been performed, select the Update HMC button to update the HMC LIC. You will be prompted for the location of the update. Updates can be performed from media or from a remote location.
When a managed system is selected, Updates tasks perform a guided update of managed system, power subsystem, or I/O Licensed Internal Code.
The following are represented in the Updates tasks:
Licensed Internal Code (LIC) can be changed in two ways. You can upgrade the LIC installed on a managed system to a new release, or update the existing LIC running on the system.
An update of a current LIC release may fix problems or add additional function. Updating LIC may or may not be a disruptive process. Updates that do not disrupt the system are called concurrent updates. To update the LIC currently installed on the managed system, use the Change Licensed Internal Code for the current release task.
A new release of LIC may add support for new hardware or add new function. Upgrading LIC to a new release is always a disruptive process requiring a complete shut down, power off, and restart of the system. To upgrade LIC to a new release, use the Upgrade Licensed Internal Code to a new release task.
Concurrent updates allow the system and the applications running on the system to continue to run as the LIC update is applied. This appreciably lessens the system downtime associated with LIC maintenance. Most updates released will be concurrent. However, certain types of problems are critical to fix and can be fixed only with a disruptive update. Using the View system information task, you are able to view the levels of LIC available in a repository and determine which of the available updates are concurrent and which are disruptive.
If the update is disruptive, you are given the option of installing and activating (incurring the disruption) or deferring the activation to a more convenient time. Concurrent updates can only be done for managed system LIC.
Note: Checking is done before LIC update to assure that the system is in the correct state for an update. The state of the system must not change during a code update. For example, partitions should not be shut down during an LIC update.
New releases of LIC (upgrades) and updates to these releases are available from the following repositories:
Fixes and upgrades to LIC can be ordered or downloaded from the Fix Central web site at http://www.ibm.com/eserver/support/fixes/fixcentral.
Use the Flash Side Selection task to select which flash side will be active after the next activation. (This task is intended for service user mode only.)
Use the Check system readiness task to check that all systems selected are in the correct state for LIC update.
Choose the View system information task to view the level of LIC currently installed on your managed system or I/O. When a repository is selected, View system information also displays retrievable levels of LIC available in the repository.
Use this task to apply updates to the currently installed Licensed Internal Code (LIC) on your system.
This task requires access to a service repository, either a remote location, the HMC hard drive, or a DVD drive.
LIC updates can be downloaded directly from IBM's service web site or IBM's support system during the update process.
If you have completed a code update from a repository to one of your managed systems or power subsystems, that code is available in the Hard Drive repository on the HMC for installation on other systems. You can select Hard Drive to update other managed systems or power subsystems with the same code.
LIC updates can also be downloaded and written to a DVD or to another system available to your HMC using FTP. You can select DVD drive or FTP site to install the LIC update from these locations.
Multiple managed systems can be updated simultaneously by selecting them from the target list.
Files are selectively downloaded to the HMC to apply LIC updates. From this task, you can:
See Example: Change Licensed Internal Code for the Current Release for more information.
Select Start Change Licensed Internal Code wizard to perform a guided update of managed system, power, and I/O Licensed Internal Code (LIC):
Select View system information to examine current LIC levels on a managed system, power subsystem, or I/O, including levels retrievable from a repository.
Select Advanced features to update managed system and power LIC with more options and additional targeting choices.
Related HMC CLI commands:
In this example, the managed system is currently running at an activated level 26. We wish to update the managed system to level 28. We have previously downloaded this update to another system. We will FTP to this system to install the new level of LIC on our managed system.
To update the LIC currently installed on the managed system, use the Change Licensed Internal Code for the current release task:.










The Accepted Level of LIC is the previous level, 26. A new level of LIC is installed and activated on the t-side of the FSP. Once testing of the new level, 28 has occurred, or when another level is to be installed (i.e. level 29), the new level, 28 is Accepted, which copies the level from the t-side of the FSP to the p-side (permanent side). This allows you to return to the previous level of LIC should testing prove problematic. In this example, the update we have just installed (level 28) has not yet been Accepted, so the Accepted Level of LIC is at the old level, level 26.
We have successfully updated the Licensed Internal Code on the managed system from level 26 to level 28!
A new release level of Licensed Internal Code (LIC) supports major new function such as the introduction of new hardware models and significant function or features enabled by firmware. In addition to the new function and hardware support, new release levels also contain fixes. Upgrading from one release level to another is disruptive to system operations.
Release levels can be skipped. You can upgrade from release level A to release level D without having to install release level B and C. New release levels of LIC are installed with the this task.
To install a new release of Licensed Internal Code:
Related HMC CLI commands:
In this example, the managed system is currently running at release EC Number 01EM310. We wish to upgrade the LIC on the managed system to release NEWLEVEL. We have previously downloaded this new release of LIC to another system. We will FTP to this system to install the new release of LIC on our managed system.
To upgrade the LIC currently installed on the managed system, use the Upgrade Licensed Internal Code to a New Release task:.






Use this task to select which flash side will be active after the next activation.
Attention: If you select p-side for the next activation, this action disables concurrent Licensed Internal Code (LIC) update.
The flash side is the nonvolatile storage location in the flexible service processor (FSP), divided into t-side (temporary side) and p-side (permanent side), allowing for storing two levels of code. When the p-side is selected, concurrent LIC update is disabled.
Related HMC CLI commands:
Use this task to confirm that the managed system is in the correct state to perform a Licensed Internal Code update or upgrade successfully.
Before updating or upgrading Licensed internal code, all managed systems to be updated must be in Operating, Standby, Power Off, or Recovery state. All Flexible Service Processors (FSP) for the managed system must be properly connected to the HMC. Any problems found during the check will be reported to you to correct before updating LIC. A readiness check will automatically be performed before any update or upgrade begins.
Related HMC CLI commands:
Use this task to examine current LIC levels on the managed system, including installed, activated, and accepted levels. If a repository is selected, this task also displays retrievable levels available in a repository.
The Installed level of LIC is the level that will be activated and loaded into memory at the next system restart. The Activated level of LIC is the level that is activated and loaded into memory at this time. The Accepted level of LIC is a committed level of LIC that can be returned to, if necessary. This is the level of code on the p-side (permanent side). The Unactivated Deferred level of LIC is the latest unactivated level that contains deferred updates. A deferred update requires a system restart to activate.
Concurrent LIC update status indicates whether concurrent LIC update is enabled or disabled. A concurrent update can be installed and activated without rebooting any partitions or disrupting applications.
Reason for disablement indicates why concurrent LIC update is disabled. This might include:
A concurrent LIC update can be installed and activated without rebooting partitions or disrupting applications.
Related HMC CLI commands:
This appendix lists the tasks you can perform using the Hardware Management Console (HMC) and the user roles/IDs that are associated with that task.
You can, however, create customized user profiles which would allow you to have unique user IDs and multiple user roles. The management of these user roles is performed by using the Manage Task and Resource Roles task. The Manage User Profiles and Access task provides the ability to define which user role is associated with each specific user ID.
Table 10 alphabetically lists the HMC Management and Service Management tasks and the corresponding user roles/IDs that can perform these tasks.
Table 11 lists the Systems Management tasks that can be performed on managed objects and the corresponding user roles that can perform these tasks.
| Tasks | User roles/IDs | |||
|---|---|---|---|---|
| Operator (hmcoperator) | Super Administrator (hmcsuperadmin) | Viewer (hmcviewer) | Service Representative (hmcservicerep) | |
| Backup HMC Data | X | X | X | |
| Change Date and Time | X | X | X | |
| Change Language and Locale | X | X | X | X |
| Change Network Settings | X | X | X | |
| Change User Interface Settings | X | X | X | X |
| Change User Password | X | X | X | X |
| Create Serviceable Event | X | X | ||
| Create Welcome Text | X | X | ||
| Format Media | X | X | X | |
| Launch Guided Setup Wizard | X | |||
| Launch Remote Hardware Management Console | X | X | X | X |
| Load Serviceable Events | X | X | X | X |
| Lock HMC Screen | X | X | X | X |
| Logoff or Disconnect | X | X | X | X |
| Manage Certificates | X | |||
| Manage Connection Monitoring | X | X | X | X |
| Manage Customer Information | X | X | X | |
| Manage Data Replication | X | X | ||
| Manage Dumps | X | X | X | |
| Manage eService Registration | X | X | ||
| Manage Inbound Connectivity | X | X | X | |
| Manage Outbound Connectivity | X | X | X | |
| Manage POWER4 Service Agent | X | X | ||
| Manage Remote Connections | X | X | X | |
| Manage Remote Support Requests | X | X | X | X |
| Manage Serviceable Event Notification | X | X | X | |
| Manage Serviceable Events | X | X | ||
| Manage Systems Call-Home | X | X | X | |
| Manage Task and Resource Roles | X | |||
| Manage User Profiles and Access | X | |||
| Manage Users and Tasks | X | X | X | X |
| Open 5250 Console | X | X | X | |
| Open Restricted Shell Terminal | X | X | X | X |
| Remote Command Execution | X | X | X | |
| Remote Virtual Terminal | X | X | X | |
| Remote Operation | X | X | X | X |
| Restore HMC Data | X | X | X | |
| Save Upgrade Data | X | X | X | |
| Schedule Operations | X | X | ||
| Shut Down or Restart | X | X | X | |
| Test Network Connectivity | X | X | X | X |
| Tip of the Day | X | X | X | X |
| Transmit Service Information | X | X | ||
| View HMC Events | X | X | X | |
| View Licenses | X | X | X | X |
| View Network Topology | X | X | X | X |
| View System Data | X | |||
| Tasks | User roles/IDs | |||
|---|---|---|---|---|
| Operator (hmcoperator) | Super Administrator (hmcsuperadmin) | Viewer (hmcviewer) | Service Representative (hmcservicerep) | |
| Properties | X | X | X | X |
| Update Password | X | X | X | |
| Change Default Profile | X | X | X | |
| Operations | ||||
| Power On | X | X | X | |
| Power Off | X | X | X | |
| Activate | X | X | X | |
| Restart | X | X | X | |
| Shut Down | X | X | X | |
| LED Status: View System Attention LED | X | X | X | X |
| LED Status: Identify LED | X | X | X | X |
| LED Status: Test LED | X | X | X | X |
| Manage Attention LED | X | X | X | X |
| Schedule Operations | X | X | ||
| Advanced System Management (ASM) | X | X | X | |
| Utilization Data: Enable | X | X | X | |
| Utilization Data: Disable | X | X | X | |
| Utilization Data: View | X | X | X | X |
| Utilization Data: Refresh | X | X | X | |
| Rebuild | X | X | ||
| Change Password | X | |||
| Configuration | ||||
| Create Logical Partition: AIX or Linux | X | X | ||
| Create Logical Partition: VIO Server | X | X | ||
| Create Logical Partition: i5/OS | X | X | ||
| System Plans: Create | X | |||
| System Plans: Deploy | X | |||
| System Plans: Import | X | |||
| System Plans: Export | X | |||
| System Plans: Remove | X | |||
| System Plans: View | X | |||
| Manage Custom Groups | X | X | X | |
| View Workload Management Groups | X | X | X | X |
| Partition Availability Priority | X | X | ||
| Manage System Profiles | X | X | X | X |
| Manage Partition Data: Restore | X | X | ||
| Manage Partition Data: Initialize | X | X | ||
| Manage Partition Data: Backup | X | X | X | |
| Manage Partition Data: Delete | X | X | ||
| Save Current Configuration | X | X | X | |
| Connections | ||||
| Service Processor Status | X | X | X | X |
| Reset or Remove Connections | X | X | X | |
| Disconnect Another HMC | X | |||
| Add Managed System | X | X | ||
| Hardware (Information) | ||||
| Adapters: GX+ | X | X | X | X |
| Adapters: Host Channel | X | X | X | X |
| Adapters: Host Ethernet | X | X | X | X |
| Adapters: Switch Network Interface | X | X | X | X |
| View RIO Topology | X | X | X | X |
| Virtual I/O Adapters | X | X | X | X |
| Dynamic Logical Partitioning | ||||
| Processor | X | X | X | |
| Memory | X | X | X | |
| Physical Adapters | X | X | X | |
| Virtual Adapter | X | X | X | |
| Host Ethernet | X | X | X | |
| Updates | ||||
| Change Licensed Internal Code for the current release | X | X | ||
| Upgrade Licensed Internal Code to a new release | X | X | ||
| Flash Side Selection | X | X | ||
| Check system readiness | X | X | ||
| View system readiness | X | X | ||
| Console Window | ||||
| Open Terminal Window | X | X | X | |
| Close Terminal Connection | X | X | X | |
| Open Shared 5250 Console | X | X | X | |
| Open Dedicated 5250 Console | X | X | X | |
| Serviceability | ||||
| Manage Serviceable Events | X | X | ||
| Create Serviceable Event | X | X | ||
| Reference Code History | X | X | X | X |
| Control Panel Functions: (20) Type, Model, Feature | X | |||
| Hardware: Add FRU | X | X | ||
| Hardware: Add Enclosure | X | X | ||
| Hardware: Exchange FRU | X | X | ||
| Hardware: Exchange Enclosure | X | X | ||
| Hardware: Remove FRU | X | X | ||
| Hardware: Remove Enclosure | X | X | ||
| Hardware: Power on/off I/O Unit | X | X | ||
| Manage Dumps | X | X | X | |
| Collect VPD | X | X | X | X |
| Edit MTMS | X | |||
| FSP Failover: Setup | X | |||
| FSP Failover: Initiate | X | |||
| Capacity on Demand (CoD) | ||||
| Enter CoD code | X | |||
| View History Log | X | X | X | X |
| Processor: View Capacity Settings | X | X | X | X |
| Processor/CUoD: View Code Information | X | X | X | X |
| Processor/On/Off CoD: Manage | X | |||
| Processor/On/Off CoD: View Capacity Settings | X | X | X | X |
| Processor/On/Off CoD: View Billing Information | X | X | X | X |
| Processor/On/Off CoD: View Code Information | X | X | X | X |
| Processor/Trial CoD: Stop | X | |||
| Processor/Trial CoD: View Capacity Settings | X | X | X | X |
| Processor/Trial CoD: View Code Information | X | X | X | X |
| Processor/Reserve CoD: Manage | X | |||
| Processor/Reserve CoD: View Capacity Settings | X | X | X | X |
| Processor/Reserve CoD: View Code Information | X | X | X | X |
| Processor/Reserve CoD: View Shared Processor Utilization | X | X | X | |
| Advanced POWER Virtualization: Enter Activation Code | X | |||
| Advanced POWER Virtualization: View History Log | X | X | X | X |
| Advanced POWER Virtualization: View Code Information | X | X | X | X |
| Enterprise Enablement: Enter Activation Code | X | |||
| Enterprise Enablement: View History Log | X | X | X | X |
| Enterprise Enablement: View Code Information | X | X | X | X |
| Other Advanced Functions: Enter Activation Code | X | |||
| Other Advanced Functions: View History Log | X | X | X | X |
| Other Advanced Functions: View Code Information | X | X | X | X |
Remote operations use the Graphical User Interface (GUI) used by a local Hardware Management Console (HMC) operator (see Figure 18) or the command line interface (CLI) on the HMC. You can perform operations remotely in the following ways:

The remote HMC is an HMC that is on a different subnet from the service processor, therefore the service processor cannot be autodiscovered with IP multicast.
To determine whether to use a remote HMC or Web browser connected to a local HMC, consider the scope of control that you need. A remote HMC defines a specific set of managed objects that are directly controlled by the remote HMC, while a Web browser to a local HMC has control over the same set of managed objects as the local HMC. The communications connectivity and communication speed is an additional consideration; LAN connectivity provides acceptable communications for either a remote HMC or Web browser control.
A remote HMC gives the most complete set of functions because it is a complete HMC; only the process of configuring the managed objects is different from a local HMC.
As a complete HMC, a remote HMC has the same setup and maintenance requirements as a local Hardware Management Console. A remote HMC needs LAN TCP/IP connectivity to each managed object (service processor) that is to be managed; therefore, any customer firewall that may exist between the remote HMC and its managed objects must permit HMC to service processor communications to occur. A remote HMC may also need communication with another HMC for service and support. Table 12 shows the ports a remote HMC uses for communications.
| Port | Use |
|---|---|
| udp 9900 | HMC to HMC discovery |
| tcp 9920 | HMC to HMC commands |
A remote HMC needs connectivity to IBM (or another HMC that has connectivity to IBM) for service and support. The connectivity to IBM may be in the form of access to the internet (through a company firewall), or a dialed connection through a customer-provided switched phone connection using the supplied modem (see Manage Outbound Connectivity). A remote HMC cannot use the supplied modem for communication with a local HMC or a service processor.
Performance (that is, time to perform an operation) and the availability of the status information and access to the control functions of the service processor depends on the reliability, availability, and responsiveness of the customer network that interconnects the remote HMC with the managed object. A remote HMC monitors the connection to each service processor and attempts to recover any lost connections and can report those connections that cannot be recovered.
Security for a remote HMC is provided by the HMC user-login procedures in the same way as a local HMC. As with a local HMC, all communication between a remote HMC and each service processor is encrypted. Certificates for secure communications are provided, and can be changed by the user if desired (see Manage Certificates).
TCP/IP access to the remote HMC is controlled through its internally managed firewall and is limited to HMC related functions.
If you need occasional monitoring and control of managed objects connected to a single local HMC, use a Web browser. An example of using the Web browser might be an off-hours monitor from home by an operator or system programmer.
Each HMC contains a Web server that can be configured to allow remote access for a specified set of users. If a customer firewall exists between the Web browser and the local HMC, then the ports need to be accessible and the firewall should allow incoming requests on these ports. Table 13 shows the ports a Web browser needs for communication to an HMC.
| Port | Use |
|---|---|
| tcp 443 | Secure browser access to Web server communication |
| tcp 8443 | Secure browser access to Web server communication |
| tcp 9960 | Browser applet communication |
After an HMC has been configured to allow Web browser access, a Web browser gives an enabled user access to all the configured functions of a local HMC, except those functions that require physical access to the HMC such as those that use the local diskette or DVD media. The user interface presented to the remote Web browser user is the same as that of the local HMC and is subject to the same constraints as the local HMC.
The Web browser can be connected to the local HMC using a LAN TCP/IP connection and using only encrypted (HTTPS) protocols. Logon security for a Web browser is provided by the HMC user-login procedures. Certificates for secure communications are provided, and can be changed by the user (see Manage Certificates).
Performance (that is, time to perform an operation) and the availability of the status information and access to the control functions of the managed objects depends on the reliability, availability, and responsiveness of the network that interconnects the Web browser with the local HMC. Because there is no direct connection between the Web browser and the individual managed objects, the Web browser does not monitor the connection to each service processor, does not do any recovery, and does not report any lost connections. These functions are handled by the local HMC
The Web browser system does not require connectivity to IBM for service or support and maintenance of the browser and system level is the responsibility of the customer.
If the URL of the HMC is specified using the format https://xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the IP address) and Microsoft Internet Explorer is used as the browser, a hostname mismatch message is displayed. To avoid this message, a Firefox browser is used or a hostname is configured for the HMC, using the Change Network Settings task (see Change Network Settings), and this hostname is specified in the URL instead of an IP address. Namely, using the format https://hostname.domain_name or https://hostname (for example, using https://hmc1.ibm.com or https://hmc1).
An alternative to performing HMC tasks is using the command line interface (CLI).
From a local HMC, the interface is available by right-clicking on the desktop (outside of the HMC web user interface screen), click Terminals and rshlogin. A restricted shell command line window is displayed. You can also open the Open Restricted Shell Terminal task from the HMC Management work pane.
You can use the command line interface in the following situations:
HMCs typically are placed inside the machine room where managed systems are located, so you might not have physical access to the HMC. In this case, you can remotely access it using either the remote client or the remote command line interface. You must ensure that your script executions between SSH clients and the HMC are secure
To enable scripts to run unattended between an SSH client and an HMC, do the following:
The following files are created in the $HOME/.ssh directory:
The write bits for both group and other are turned off. Ensure that the private key has a permission of 600.
ssh userid@hostname "mkauthkeys –add '<the key string from $HOME/ .ssh/id_dsa
You can use the following procedure to delete the key from the HMC by modifying various files:
scp userid@host_name :.ssh/authorized_keys2 /tmp/mykeyfile
scp /tmp/mykeyfile userid@host_name ".ssh/authorized_keys2"
scp userid@hostname:.ssh/authorized_keys2 authorized_keys2
scp authorized_keys joe@somehost:.ssh/authorized_keys2
You can also use the command line to delete the key from the HMC by using the mkauthkeys command. For example:
ssh userid@hostname "mkauthkeys --remove 'joe@somehost'"
You can enable or disable the remote command line interface access to the HMC by using the SSH facility.
To enable or disable remote commands, you must have a user ID with one of the following roles:
To enable or disable remote commands, do the following:
HMC Web browser support requires HTML 2.0, JavaScript 1.0, Java Virtual Machine (JVM), and cookie support in browsers that will connect to the HMC. Contact your support personnel to assist you in determining if your browser is configured with a Java Virtual Machine. The Web browser must use the HTTP 1.1 protocol; and if you are using a proxy server, the HTTP 1.1 protocol must be enabled for the proxy connections. Additionally, pop-ups must be enabled for all HMCs addressed in the browser if running with pop-ups disabled. The following browsers have been tested:
Before you can use a Web browser to access an HMC, you must:
Use the following steps to log in to the HMC from a LAN connected Web browser:
If this is the first access of the HMC for the current Web browser session you can receive a certificate error. This certificate error is displayed if:
In either case, if you know that the certificate being displayed to the browser is the one used by the HMC, you can continue and all communications to the HMC will be encrypted.
If you do not want to receive notification of a certificate error for the first access of any browser session, you can configure the browser to trust the HMC or the CA. In general, to configure the browser:
If the certificate is self-signed, the HMC itself is considered the CA that issued the certificate.
The Customizable Data Replication service provides the ability to configure a set of Hardware Management Consoles (HMCs) to automatically replicate any changes to certain types of data so that the configured set of HMCs automatically keep this data synchronized without manual intervention.
The following types of data can be configured:
The Customizable Data Replication service can be enabled for the following types of operations:
Provides automatic replication of the selected customized data types between peer HMCs. Changes made on any of these consoles are replicated to the other consoles.
Provides automatic replication of the selected customized data types from one or more designated master HMCs to one or more designated slave HMCs. Changes made on a master(s) console are automatically replicated to the slave console(s).

or
Enter the TCP/IP address of the Hardware Management Console to be a used as a data source in the TCP/IP Address Information field, and then click Find.


Setting up a Master Console(s):
Setting up the Slave Console(s):
or
Enter the TCP/IP address of the HMC to be a used as the master data source in the TCP/IP Address Information field, then click Find.

As data is replicated from one Hardware Management Console to another, an internal level indicator for the data being replicated is incremented each time the data is altered on the data source. Each Hardware Management Console keeps track of the level indicator for each type of data and will not accept data from a data source when the level indicator is not greater than that on the receiving Hardware Management Console.
If for some reason there is a need to force the replication of data from one or more data sources and the level indicator on the receiving Hardware Management Console is greater than that of the data sources, do the following:
This appendix alphabetically describes the HMC commands you can use to perform tasks on the HMC. This information, including examples, is available from the HMC command line using the man command. You can also refer to the Command Line Support education module (http://www.ibm.com/servers/resourcelink/lib03030.nsf/page) andUsing the HMC remote command line for more information.
To view the command information, type man and then the command name. For example, to learn more about the "Create a user for the HMC" (mkhmcusr) command, type the following at the command line:
man mkhmcusr
Provides access to Advanced System Management menu.
asmmenu --ip <IP address of system> [--help]
asmmenu provides access to the Advanced System Management menu. This command takes the IP address or host name of the managed system and launches the Advanced System Management menu using the browser on the Hardware Management Console (HMC).
Back up console data.
bkconsdata -r {dvd | ftp | nfs | none} [-h host-name] [-u user-ID] [--passwd password] [-l mount-resource-location] [-o "mount-command-options"] [-d remote-directory] [--help]
bkconsdata backs up critical Hardware Management Console (HMC) data, which is HMC data that is stored on the HMC hard disk. This backup data may be used to restore the HMC if the HMC needs to be reinstalled from the HMC recovery CDs in the event of an HMC hard disk failure.
This option is required when backing up the data to a remote FTP site or NFS file system. Otherwise, this option is not valid.
This option is required when backing up the data to a remote FTP site. Otherwise, this option is not valid.
This option is only valid when backing up the data to a remote FTP site.
This option is required when backing up the data to a remote NFS file system. Otherwise, this option is not valid.
This option is only valid when backing up the data to a remote NFS file system.
This option is only valid when backing up the data to a remote FTP site or NFS file system.
Back up profile data.
bkprofdata -m managed-system -f file [--force] [--help]
bkprofdata backs up profile data for the managed-system.
The rstprofdata command can be used to restore profile data for the managed-system.
The rmprofdata command can be used to remove a profile data backup file.
If file already exists, this command will fail unless the --force option is specified.
To back up the profile data to removable media, the media must be present in the removable media device and the device must be mounted with the mount command before this command is issued. The lsmediadev command can be used to display all of the removable media devices on the HMC.
Change access control configuration.
chaccfg -t {resourcerole | taskrole} {-f configuration-file | -i "configuration-data"} [--help]
chaccfg changes the configuration of an access control role.
The configuration data consists of attribute name/value pairs, which are in comma separated value (CSV) format. These attribute name/value pairs form a configuration record. A line feed marks the end of a configuration record. There can only be one configuration record in the file.
The format of a configuration record is as follows:
attribute-name=value,attribute-name=value,...<LF>
Note that certain attributes accept a comma separated list of values, as follows:
"attribute-name=value,value,...",...<LF>
When a list of values is specified, the attribute name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
If '+=' is used in the attribute name/value pair instead of '=', then the specified value is added to the existing value for the attribute if the attribute is numerical. If the attribute is a list, then the specified value(s) is added to the existing list.
If '-=' is used in the attribute name/value pair instead of '=', then the specified value is subtracted from the existing value for the attribute if the attribute is numerical. If the attribute is a list, then the specified value(s) is deleted from the existing list.
The '+=' and '-=' operators can only be used when changing a managed resource role.
Attribute names for managed resource roles:
Attribute names for task roles:
The -f and the -i options are mutually exclusive.
The -i and the -f options are mutually exclusive.
Change Capacity on Demand.
To enter a CoD code:
chcod -o e -m managed-system -k CoD-code [--help]
To activate or change On/Off CoD resources:
chcod -o a -m managed-system -c onoff -r {mem | proc} -q quantity-of-resources -d number-of-days [--help]
To activate or change Reserve CoD processors:
chcod -o a -m managed-system -c reserve -r proc-q quantity-of-processors [--help]
To deactivate all On/Off CoD, all Reserve CoD, or all Trial CoD resources:
chcod -o d -m managed-system -c {onoff | reserve | trial} -r {mem | proc} [--help]
chcod performs Capacity on Demand (CoD) operations on the managed-system.
chcod is used to enter a CoD code for the managed-system. It is also used to activate On/Off CoD and Reserve CoD resources, or to deactivate On/Off CoD, Reserve CoD, or Trial CoD resources. CoD resources are either memory or processors.
To change the number of On/Off CoD resources or days that are currently activated, specify an activate operation with this option, specify the total number of activated On/Off CoD resources that you want with the -q option, and specify the number of days that you want them for with the -d option. An activate operation is to be used regardless of whether the total number of activated On/Off CoD resources is being increased, decreased, or kept the same. A deactivate operation is to be used only when you no longer want to have any activated On/Off CoD resources.
To change the number of Reserve CoD processors that are currently activated, specify an activate operation with this option, and specify the total number of activated Reserve CoD processors that you want with the -q option. An activate operation is to be used regardless of whether the total number of activated Reserve CoD processors is being increased or decreased. A deactivate operation is to be used only when you no longer want to have any activated Reserve CoD processors.
When requesting On/Off CoD memory, the value specified must be in megabytes, and it must be a multiple of 1024 megabytes.
Change Hardware Management Console configuration information.
To change remote access settings:
chhmc -c {ssh | xntp} -s {enable | disable} [--help]
To add or remove an entry in the syslog configuration file:
chhmc -c syslog -s {add | remove} {-a IP-address | -h host-name} [--help]
To add or remove an entry in the network time protocol configuration file:
chhmc -c xntp -s {add | remove} {-a IP-address | -h host-name} {--ntpversion 1 | 2} [-nm network-mask] [-i interface] [--help]
To configure whether keyboard mapping configuration will occur at the next reboot:
chhmc -c kbdcfg -s {enable | disable} [--help]
To configure the network as a startup device:
chhmc -c netboot -s {enable | disable} [--help]
To configure an alternate disk partition on HMC as a startup device:
chhmc -c altdiskboot -s {enable | disable} --mode {install | upgrade} [--help]
To permit or deny IP addresses from utilizing HMC services:
chhmc -c {ssh | service} -s {add | remove} -a IP-address [-nm network-mask] [-i interface] [--help]
If -nm is omitted, the default network mask will be 255.255.255.255.
If -i is omitted, the rule will be applied to all interfaces.
To add or remove entries from the DNS server search order or the domain suffix search order:
chhmc -c network -s {add | remove} [-ns DNS-server] [-ds domain-suffix] [--help]
To change network settings for a specific network interface:
chhmc -c network -s modify -i interface [-a IP-address] [-nm network-mask] [--lparcomm {on | off}] [--help]
To change other network settings:
chhmc -c network -s modify [-h host-name] [-d network-domain-name] [-g gateway] [--help]
To change the locale for the HMC:
chhmc -c locale -s modify -l locale [--help]
To change the HMC date and time, or time zone:
chhmc -c date -s modify [--datetime date-time] [--clock {local | utc}] [--timezone {time-zone | none}] [--help]
To setup a Kerberos realm for the first time:
chhmc -c kerberos -s add [--realm EXAMPLE.COM] [--h kdc1.example.com] [--help]
To remove a Kerberos realm:
chhmc -c kerberos -s remove [--realm EXAMPLE.COM] [--h kdc1.example.com] [--help]
To change the Kerberos default realm:
chhmc -c kerberos -s modify [--defaultrealm EXAMPLE2.COM] [--help]
To change the Kerberos clock skew (in seconds):
chhmc -c kerberos -s modify [--clockskew 240] [--help]
To change the Kerberos ticket lifetime (Kerberos lifetime string = Integer followed by one of s seconds, m minutes, h hours, or d days):
chhmc -c kerberos -s modify [--ticketlifetime 1d12h30m] [--help]
chhmc changes Hardware Management Console (HMC) configuration information, such as remote access settings and network settings.
For the new locale to take effect for the local HMC console, you must log off the console and log back on. For the new locale to take effect for the HMC command line, you must reboot the HMC.
MMDDhhmm[[CC]YY][.ss]
where MM is the month, DD is the day, hh is the hour in 24 hour format, mm is the minutes, CC is the century, YY is the year, and ss is the seconds.
This option is required when the --clock option is specified.
You must reboot the HMC after setting the date and time.
You must reboot the HMC after setting the time zone.
Change a Hardware Management Console user.
chhmcusr -u user-name -t {assign | desc | name | passwd | pwage | taskrole} [-o {a | r}] [-r {resource | resourcerole}] [-v new-attribute-value] [--help]
chhmcusr changes an attribute of a Hardware Management Console (HMC) user.
This option is required when changing the user's managed resource object assignment or managed resource role assignment. This option is not valid when changing any other user attribute.
This option is required when changing the user's managed resource object assignment or managed resource role assignment. This option is not valid when changing any other user attribute.
When changing the user's managed resource role assignment, specify the managed resource role to be added or removed.
When changing the user's description, specify the new description with this option. The new description can be any string.
When changing the user's user name, specify the new user name with this option. The new user name must not be longer than 32 characters, and it must begin with a letter.
When changing the user's password, you can either specify the new password with this option, or you can omit this option and you will be prompted to enter the password. The new password must be at least 7 characters in length.
When changing the number of days until the user's password expires, specify the new number of days with this option.
When changing the user's access control task role, specify the new task role with this option. Valid values are hmcsuperadmin, hmcoperator, hmcviewer, hmcpe, hmcservicerep, or a user-defined task role.
This option is required when changing any user attribute other than the user's password.
Change hardware resources.
To add, remove, or move a physical I/O slot:
chhwres -r io -m managed-system -o {a | r | m} {-p partition-name | --id partition-ID} [{-t target-partition-name | --tid target-partition-ID}] -l slot-DRC-index [-a "attributes"] [-w wait-time] [-d detail-level] [--force]
To set physical I/O attributes:
chhwres -r io -m managed-system -o s {-p partition-name | --id partition-ID} --rsubtype {iopool | taggedio} -a "attributes"
To add or remove a virtual I/O adapter:
chhwres -r virtualio -m managed-system -o {a | r} {-p partition-name | --id partition-ID} [--rsubtype {eth | scsi | serial}] [-s virtual-slot-number] [-a "attributes"] [-w wait-time] [-d detail-level] [--force]
To set virtual I/O attributes:
chhwres -r virtualio -m managed-system -o s [{-p partition-name | --id partition-ID}] --rsubtype {eth | hsl | virtualopti} -a "attributes"
To add, remove, or move memory:
chhwres -r mem -m managed-system -o {a | r | m} {-p partition-name | --id partition-ID} [{-t target-partition-name | --tid target-partition-ID}] -q quantity [-w wait-time] [-d detail-level] [--force]
To set memory attributes:
chhwres -r mem -m managed-system -o s -a "attributes"
To add, remove, or move processing resources:
chhwres -r proc -m managed-system -o {a | r | m} {-p partition-name | --id partition-ID} [{-t target-partition-name | --tid target-partition-ID}] [--procs quantity] [--procunits quantity] [--5250cpwpercent percentage] [-w wait-time] [-d detail-level] [--force]
To set processing attributes:
chhwres -r proc -m managed-system -o s {-p partition-name | --id partition-ID} -a "attributes"
To add, remove, or move a Host Ethernet Adapter (HEA) logical port (POWER6 servers only):
chhwres -r hea -m managed-system -o {a | r | m} {-p partition-name | --id partition-ID} [{-t target-partition-name | --tid target-partition-ID}] -l HEA-adapter-ID [--physport physical-port-ID] -g port-group --logport logical-port-ID [-a "attributes"] [-w wait-time] [-d detail-level] [--force]
To set HEA attributes (POWER6 servers only):
chhwres -r hea -m managed-system -o s -l HEA-adapter-ID [--physport physical-port-ID] -g port-group -a "attributes"
chhwres changes the hardware resource configuration of the managed-system. chhwres is used to perform dynamic logical partitioning (DLPAR) operations.
HEA resouces are only supported on POWER6 servers.
This option is required for physical I/O or virtual I/O set operations, and for virtual I/O add operations.
This option is not valid for memory, processor, or HEA operations.
You can either use this option to specify the name of the partition for which the operation is to be performed, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
A partition is required to be specified with this option or the --id option for all operations except a virtual ethernet, memory, or HEA set operation.
You can either use this option to specify the ID of the partition for which the operation is to be performed, or use the -p option to specify the partition's name. The --id and the -p options are mutually exclusive.
A partition is required to be specified with this option or the -p option for all operations except a virtual ethernet, memory, or HEA set operation.
You can either use this option to specify the name of the target partition, or use the --tid option to specify the ID of the partition. The -t and the --tid options are mutually exclusive.
A target partition is required to be specified with this option or the --tid option for a move operation. This option is not valid for any other operation.
You can either use this option to specify the ID of the target partition, or use the -t option to specify the name of the target partition. The --tid and the -t options are mutually exclusive.
A target partition is required to be specified with this option or the -t option for a move operation. This option is not valid for any other operation.
When performing an HEA operation, use this option to specify the adapter ID of the HEA for which the operation is to be performed.
This option is not valid for any other operation.
When adding a virtual I/O adapter, if this option is not specified then the next available virtual slot number will be assigned to the virtual I/O adapter.
When removing a virtual I/O adapter, this option is required.
When adding or removing processing resources to or from a partition using shared processors, or when moving processing resources from a partition using shared processors to another partition using shared processors, use this option to specify the quantity of virtual processors to add, remove, or move.
When moving processing resources from a partition using dedicated processors to a partition using shared processors, use this option to specify the quantity of dedicated processors to be moved from the source partition and added as shared processors to the target partition.
This option is not valid when moving processing resources from a partition using shared processors to a partition using dedicated processors. The --procunits option must be used instead.
The quantity of processing resources specified with this option must be a whole number greater than 0.
When moving processing resources from a partition using shared processors to a partition using dedicated processors, use this option to specify the quantity of shared processors to be moved from the source partition and added as dedicated processors to the target partition.
This option is not valid when moving processing resources from a partition using dedicated processors to a partition using shared processors. The --procs option must be used instead.
When moving processing resources from a partition using shared processors to a partition using dedicated processors, the quantity of processing units specified with this option must be a whole number. Otherwise, the quantity of processing units specified with this option can have up to 2 decimal places. In either case, the quantity specified must be greater than 0.
This option is only valid for i5/OS partitions and can only be used when the managed-system supports the assignment of 5250 CPW percentages to partitions.
wait-time must be a whole number. If wait-time is 0, the operation will not be timed out.
If this option is not specified, a default value of 5 minutes is used.
This option is valid for all add, remove, and move operations for AIX, Linux, and virtual I/O server partitions. This option is also valid for memory add, remove, and move operations for i5/OS partitions.
If this option is not specified, a default value of 0 is used.
This option is valid for all add, remove, and move operations for AIX, Linux, and virtual I/O server partitions.
This option also allows you to force an add, remove, or move operation to be performed for an AIX, Linux, or virtual I/O server partition that does not have an RMC connection to the HMC. If this command completes successfully, you will need to restart your operating system for the change to take affect. You should only use this option if you intentionally configured your LAN to isolate the HMC from the operating system of your partition.
The format of the configuration data is as follows:
attribute-name=value,attribute-name=value,...
Note that certain attributes accept a comma separated list of values, as follows:
"attribute-name=value,value,...",...
When a list of values is specified, the attribute name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
If '+=' is used in the attribute name/value pair instead of '=', then the specified value is added to the existing value for the attribute if the attribute is numerical. If the attribute is a list, then the specified value(s) is added to the existing list.
If '-=' is used in the attribute name/value pair instead of '=', then the specified value is subtracted from the existing value for the attribute if the attribute is numerical. If the attribute is a list, then the specified value(s) is deleted from the existing list.
Valid attribute names for attributes that can be set when adding, removing, or moving a physical I/O slot:
slot_io_pool_id
Valid attribute names for setting I/O pool attributes:
Valid attribute names for setting tagged I/O resources (i5/OS partitions only):
Valid attribute names for adding a virtual ethernet adapter:
Required
Required for a trunk adapter
Valid attribute names for adding a virtual SCSI adapter:
Required
Valid attribute names for adding a virtual serial adapter:
Required
Valid attribute names for setting virtual ethernet attributes:
Valid attribute names for setting HSL OptiConnect attributes (i5/OS partitions only):
Valid attribute names for setting virtual OptiConnect attributes (i5/OS partitions only):
Valid attribute names for setting memory attributes:
Valid attribute names for setting processing attributes:
Valid values for partitions using shared processors are:
Valid attribute names when adding an HEA logical port:
capability
or
5/ieq/nieq/qp/cq/mr
where ieq (interruptible event queues), nieq (non-interruptible event queues), qp (queue pairs), cq (completion queues), and mr (memory regions) each specify the resource amount in addition to the base minimum.
Valid values for capability:
For example:
5/22/128/1021/1019/63424
Valid attribute names for setting HEA physical port attributes:
Valid attribute names for setting HEA port group attributes:
Check media readiness.
chkmedia -r {dvd | diskette | usbdiskette | usbflashmem} [--help]
chkmedia allows a user to test for media readiness on the Hardware Management Console (HMC). The media devices that can be tested for readiness are the DVD drive (DVD-RAM media only), the internal diskette drive, a USB diskette drive, and a USB flash memory device. In order to test for media readiness, a small amount of data is written to, read from, then deleted from the specified media. No other diagnostic actions are performed on the media or the media device.
Change LED.
chled -r sa -t {phys | virtuallpar | virtualsys} -m managed-system -o {on | off} [{-p partition-name | --id partition-ID}] [--help]
chled changes the state of an LED on the managed-system.
The value on is not valid when changing the physical SA LED for the managed-system.
To change a virtual partition SA LED, you must either use this option to specify the name of the partition for which the LED is to be changed, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
This option is not valid when changing the physical SA LED or the virtual SA LED for the managed-system.
To change a virtual partition SA LED, you must either use this option to specify the ID of the partition for which the LED is to be changed, or use the -p option to specify the partition's name. The --id and the -p options are mutually exclusive.
This option is not valid when changing the physical SA LED or the virtual SA LED for the managed-system.
Change utilization data collection settings.
chlparutil -r config [-m managed-system] -s sample-rate [--help]
chlparutil changes the Hardware Management Console (HMC) settings for utilization data collection for managed systems.
If this option is not specified, then the HMC settings for utilization data collection for all of the systems currently managed by this HMC, and for all of the systems for which utilization data has been previously collected by this HMC will be changed. Even though utilization data collection is enabled for a managed system, the HMC will only collect utilization data for that managed system if the HMC currently has a connection to that managed system.
This command only changes the settings for utilization data collection for this HMC. Utilization data collection by other HMCs for the same managed systems is not affected.
Change Service Agent configuration.
To change customer email notification settings:
chsacfg -t email -o {enable | disable | setsmtp | add | remove | test} [-a {email-address | all}] [--events {all | callhome}] [-h host-name [-p port-number]]
To change FTP firewall settings:
chsacfg -t ftpfirewall [-o {add | remove}] [-h host-name] [-p port-number] [-u user-ID] [--passwd password] [--passive passive-mode] [--fwtype firewall-type] [-n name]
To change FTP offload server settings:
chsacfg -t ftpoffload [-o {enable | disable}] [-h host-name] [-p port-number] [-u user-ID] [--passwd password] [--passive passive-mode] [-d directory]
To change SNMP trap configuration:
chsacfg -t snmp -o {add | remove} -a {SNMP-address | all} [--events SNMP-trap-list]
chsacfg changes the Service Agent configuration.
When performing a remove or test operation for a customer notification email address, all can be specified with this option instead of a specific email address. If all is specified, then the remove or test operation will be performed for all notification email addresses.
When performing a remove operation for an SNMP address, all can be specified with this option instead of a specific SNMP address. If all is specified, then the remove operation will be performed for all SNMP trap notification addresses.
This option is required when adding, removing, or testing a customer notification email address. This option is not valid for any other operation.
When adding an address for SNMP trap notifications, specify the list of SNMP traps for which the SNMP address is to be notified. If there is more than one SNMP trap, the SNMP traps must be separated by blanks. The defined SNMP traps can be listed by issuing the command lssacfg -t snmptrapnames.
This option is only valid when adding a customer email notification address or when adding an SNMP address for SNMP trap notifications.
When changing the FTP firewall settings, use this option to specify the host name or IP address of the firewall server.
When changing the FTP offload server settings, use this option to specify the host name or IP address of the FTP offload server.
This option is required when setting the SMTP server information for customer notification email.
When changing the FTP firewall settings, use this option to specify the port number to use on the firewall server.
When changing the FTP offload server settings, use this option to specify the port number to use on the FTP offload server.
The default port number for an FTP offload server or firewall server is 21.
When changing the FTP offload server settings, use this option to specify the user ID to use to log in to the FTP offload server.
When changing the FTP offload server settings, use this option to specify the password to use to log in to the FTP offload server. If this option is omitted, you will be prompted to enter the password.
When changing the FTP offload server settings, use this option to specify the passive mode to use. Valid values are on for always use PASV and off for always use PORT.
0 - do not use a firewall
1 - connect to firewall server, but send "USER user@real.host.name"
2 - connect to firewall server, log in with "USER fwuser" and "PASS fwpassword", and then "USER user@real.host.name"
3 - connect to and log in to firewall server, and then use "SITE real.host.name" followed by "USER user" and "PASS password"
4 - connect to and log in to firewall server, and then use "OPEN real.host.name" followed by "USER user" and "PASS password"
5 - connect to firewall server, but send "USER user@fwuser@real.host.name" and "PASS pass@fwpass" to log in
6 - connect to firewall server, but send "USER fwuser@real.host.name" and "PASS fwpass" followed by "USER user" and "PASS password" to complete the login
7 - connect to firewall server, but send "USER user@real.host.name fwuser" and "PASS pass" followed by "ACCT fwpass" to complete the login
This option is only valid when changing the FTP firewall settings.
This option is required when adding or removing a name in the exclusion list for the FTP firewall server. This option is not valid for any other operation.
Updates serviceable events on the HMC.
chsvcevent -o {close | closeall} [-p problem-number -h analyzing-HMC] [--help]
chsvcevent closes serviceable events on the Hardware Management Console (HMC).
The problem number can be obtained using the lssvcevents command.
The analyzing HMC can be obtained using the lssvcevents command.
Change system resources.
chsyscfg -r {lpar | prof | sys | sysprof | frame} {-m managed-system | -e managed-frame} {-f configuration-file | -i "configuration-data"} [--help]
chsyscfg changes the attributes of partitions, partition profiles, or system profiles for the managed-system. It can also change the attributes of the managed-system.
chsyscfg can also change the attributes of the managed-frame.
This option is required when changing the attributes of partitions, partition profiles, system profiles, or the managed system. This option is not valid otherwise.
This option is required when changing the attributes of the managed frame. This option is not valid otherwise.
The format of a configuration record is as follows:
attribute-name=value,attribute-name=value,...<LF>
Note that certain attributes accept a comma separated list of values, as follows:
"attribute-name=value,value,...",...<LF>
When a list of values is specified, the attribute name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
If '+=' is used in the attribute name/value pair instead of '=', then the specified value is added to the existing value for the attribute if the attribute is numerical. If the attribute is a list, then the specified value(s) is added to the existing list.
If '-=' is used in the attribute name/value pair instead of '=', then the specified value is subtracted from the existing value for the attribute if the attribute is numerical. If the attribute is a list, then the specified value(s) is deleted from the existing list.
Attribute names for partitions:
Valid values are a, b, c, or d
This attribute replaces the shared_proc_pool_util_auth attribute. Setting this attribute also sets the shared_proc_pool_util_auth attribute to the same value.
This attribute has been deprecated. Use the allow_perf_collection attribute instead. Setting this attribute also sets the allow_perf_collection attribute to the same value.
Valid values are 0 - 255.
Valid values are:
Attribute names for partition profiles:
Valid values for partitions using shared processors are:
slot-DRC-index/slot-IO-pool-ID/is-required
Both '/' characters must be present, but optional values may be omitted. Optional values are slot-IO-pool-ID.
Valid values for is-required:
DRC index of I/O slot, or virtual slot number
DRC index of I/O slot, or virtual slot number
DRC index of I/O slot, DRC index of HEA logical port (POWER6 servers only), virtual slot number, or the value hmc
DRC index of I/O slot
DRC index of I/O slot
Valid values are:
Valid values are:
Valid values are:
virtual-slot-number/is-IEEE/port-vlan-ID/additional-vlan-IDs/trunk-priority/is-required
All 5 '/' characters must be present, but optional values may be omitted. Optional values are additional-vlan-IDs and trunk-priority.
Valid values for is-IEEE and is-required:
Valid values for trunk-priority:
virtual-slot-number/client-or-server/remote-lpar-ID/remote-lpar-name/remote-slot-number/is-required
All 5 '/' characters must be present, but optional values may be omitted. Optional values for server adapters are remote-lpar-ID, remote-lpar-name, and remote-slot-number. Optional values for client adapters are remote-lpar-ID or remote-lpar-name (one of those values is required, but not both).
Valid values for client-or-server:
Valid values for is-required:
virtual-slot-number/client-or-server/supports-HMC/remote-lpar-ID/remote-lpar-name/remote-slot-number/is-required
All 6 '/' characters must be present, but optional values may be omitted. Optional values for server adapters are supports-HMC, remote-lpar-ID, remote-lpar-name, and remote-slot-number. Optional values for client adapters are remote-lpar-ID or remote-lpar-name (one of those values is required, but not both), and the supports-HMC value is not allowed.
Valid values for client-or-server:
Valid values for supports-HMC:
Valid values for is-required:
Comma separated list of Host Channel adapters (HCA), with each adapter having the following format:
adapter-ID/GUID/capability
All 3 values must be specified for each adapter.
Valid values for capability:
Comma separated list of Logical Host Ethernet adapter (LHEA) logical ports, with each logical port having the following format:
adapter-ID/port-group/physical-port-ID/ logical-port-ID/allowed-VLAN-IDs
All 4 '/' characters must be present, but optional values may be omitted. Optional values are allowed-VLAN-IDs.
Comma separated list of LHEA capabilities, with each capability having one of the following formats:
adapter-ID/capability
or
adapter-ID/5/ieq/nieq/qp/cq/mr
where ieq (interruptible event queues), nieq (non-interruptible event queues), qp (queue pairs), cq (completion queues), and mr (memory regions) each specify the resource amount in addition to the base minimum.
Valid values for capability:
Comma separated list of Switch Network Interface (SNI) adapter device IDs
Valid values are:
Valid values are:
Attribute names for a managed system:
Attribute names for system profiles:
Attribute names for a managed frame:
The -f and the -i options are mutually exclusive.
When this option is used, only a single resource can be changed.
The -i and the -f options are mutually exclusive.
Change system password.
chsyspwd -t {access | admin | general} {-m managed-system | -e managed-frame} [--passwd current-password] [--newpasswd new-password] [--help]
chsyspwd changes a password for the managed-system or the managed-frame.
The -m and the -e options are mutually exclusive.
The -e and the -m options are mutually exclusive.
The new password must be at least 4 characters in length, and cannot be longer than 63 characters.
Change partition state or system state.
To power on a managed system:
chsysstate -m managed-system -r sys -o {on | onstandby | onsysprof} [-f system-profile-name] [-k keylock-position]
To power off a managed system:
chsysstate -m managed-system -r sys -o off [--immed]
To restart a managed system:
chsysstate -m managed-system -r sys -o off --immed --restart
To rebuild a managed system or a managed frame:
chsysstate {-m managed-system | -e managed-frame} -r {sys | frame} -o rebuild
To recover partition data for a managed system:
chsysstate -m managed-system -r sys -o recover
To initiate service processor failover for a managed system:
chsysstate -m managed-system -r sys -o spfailover
To set the keylock position for a managed system or a partition:
chsysstate -m managed-system -r {sys | lpar} -o chkey -k keylock-position [{-n partition-name | --id partition-ID}]
To activate a partition:
chsysstate -m managed-system -r lpar -o on {-n partition-name | --id partition-ID} [-f partition-profile-name] [-k keylock-position] [-b boot-mode] [-i IPL-source]
To shut down or restart a partition:
chsysstate -m managed-system -r lpar -o {shutdown | osshutdown | dumprestart | retrydump} {-n partition-name | --id partition-ID} [--immed] [--restart]
To perform an operator panel service function on a partition:
chsysstate -m managed-system -r lpar -o {dston | remotedstoff | remotedston | consoleservice | iopreset | iopdump} {-n partition-name | --id partition-ID}
To validate or activate a system profile:
chsysstate -m managed-system -r sysprof -n system-profile-name [-o on] [--continue] [--test]
To power off all of the unowned I/O units in a managed frame:
chsysstate -e managed-frame -r frame -o unownediooff
To power off all of the unowned I/O units in a managed frame:
chsysstate -e managed-frame -r frame -o unownediooff
chsysstate changes the state of a partition, the managed-system, or the managed-frame.
This option is required when performing a partition, system profile, or managed system operation.
This option is not valid otherwise.
This option is required when performing a managed frame operation. This option is not valid otherwise.
When powering on a managed system with a system profile, use this option to specify the name of the system profile to use. This option is required.
This option is required when setting the keylock position for a partition or a managed system.
This option is optional when powering on a managed system or activating a partition.
This option must be specified when restarting a managed system.
If this option is specified when shutting down or restarting a partition, an immediate shut down or restart is performed.
When performing a partition operation, use either this option to specify the name of the partition on which to perform the operation, or use the --id option to specify the partition's ID. The -n and the --id options are mutually exclusive for partition operations.
Displays welcome text at local console login or displays text when remotely login using SSH..
chusrtca [-o { a | r | ab | rb}] [-f welcome-file] [-b banner-file] [-c] [--help]
chusrtca provides a method to deploy text file(s) containing welcome or warning message and present to all users who login locally on the Hardware Management Console (HMC). The text file must be named WelcomeFile.txt. A banner file can also be specified, to have its contents displayed prior to login with SSH. The banner file must first be copied to the HMC, then it will be copied to a location accessible by SSH daemon. The banner file must be named BannerFile.txt.
Activate Capacity on Demand advanced functions.
chvet -o e -m managed-system -k activation-code [--help]
chvet performs activation of Capacity on Demand (CoD) advanced functions on the managed-system. CoD advanced functions include Advanced POWER Virtualization and Enterprise Enablement.
Copy dumps.
cpdump -r {dvd | ftp} -f "file1 file2 ...fileN" [-h host-name] [-u user-ID] [--passwd password] [-d directory] [--help]
cpdump copies managed system dumps and managed frame dumps from the Hardware Management Console (HMC) to DVD or a remote FTP site.
Use the lsdump command to list the managed system dumps and managed frame dumps that reside on the HMC.
This option is required when copying a dump to a remote FTP site. Otherwise, this option is not valid.
This option is required when copying a dump to a remote FTP site. Otherwise, this option is not valid.
This option is only valid when copying a dump to a remote FTP site.
This option is only valid when copying a dump to a remote FTP site.
Copy system plan.
cpsysplan -r {ftp | media} -f file-name -o {import | export} [-h host-name] [-p ftp-port-number] [-u user-ID] [--passwd password] [-d directory] [--check] [--help]
cpsysplan copies a system plan file between the Hardware Management Console (HMC) and either removable media or a remote host.
cpsysplan performs a raw file copy. It does not parse or validate the system plan file content.
The file will be searched for in the system plan file directory on the HMC when copying from the HMC. When copying to the HMC, the file will be written to this directory. If the file already exists, it will be overwritten unless the --check option is specified.
The file name must end with the .sysplan suffix.
This option is required when copying a file to or from a remote FTP site. Otherwise, this option is not valid.
This option is only valid when copying a file to or from a remote FTP site.
This option is required when copying a file to or from a remote FTP site. Otherwise, this option is not valid.
This option is only valid when copying a file to or from a remote FTP site.
This option is required when copying a system plan file to or from media. The directory is the name of the mounted removable media where the file is read from when -o import is specified or written to when -o export is specified.
This option is only valid when -o import is specified.
Define system plan resource.
defsysplanres -r osinstall -n resource-name -v "resource-value" [-d "resource-description"] [--help]
defsysplanres defines a system plan resource for use by system plans deployed from the Hardware Management Console (HMC).
This command does not create the resource. It sets the reference to an OS installation resource that can later be used within system plans that are deployed from the HMC where the resource has been defined. This resource is defined only to the HMC and not to any system plan or managed system. If the resource defined appears with a location attribute in a system plan, the plan location will be used instead.
Specify vios with this option to define the OS installation resource for installing a Virtual I/O Server with a system plan
Specify i5osv5r3m0 with this option to define the OS installation resource for installing the i5/OS V5R3M0 release with a system plan.
Specify sles9 with this option to define the OS installation resource for installing the SLES9 LINUX operating system with a system plan.
Specify rhel4 with this option to define the OS installation resource for installing the Red Hat 4 LINUX operating system with a system plan.
Specify aix52 with this option to define the OS installation resource for installing the AIX V5R2 operating system with a system plan.
Specify aix53 with this option to define the OS installation resource for installing the AIX V5R3 operating system with a system plan.
Otherwise the name specified with this option is the name of the resource to define.
Deploy system plan.
deploysysplan -f file-name -o {dv | v | d} [-m managed-system] [--force] [--plan plan-number] [-v] [-i ["deployment-plan-step-identifier"]] [--help]
deploysysplan deploys a managed system's partition plan from a system plan file.
The file name must end with the .sysplan suffix.
Use the dv option to validate the system plan on the managed system, and if it is valid, to deploy it.
Use the v option to validate the system plan on the managed system but not deploy it.
Use the d option to skip validation of the system plan against the managed system, and just deploy the plan-specified partitions and profiles on the managed system.
The name may either be the user-defined name for the managed system, or be in the form tttt-mmm*ssssssss, where tttt is the machine type, mmm is the model, and ssssssss is the serial number of the managed system. The tttt-mmm*ssssssss form must be used if there are multiple managed systems with the same user-defined name.
When -o dv or -o d is specified, this option specifies that a list of log entries that record the steps performed as part of deploying the system plan should be written to stdout. Otherwise, this list will not be written out.
The values representing the system plan steps to be performed will be separated by a blank delimiter and the entire list must be enclosed in double quotes.
When this option is specified, only the system plan steps identified in this list will be performed. The system plan steps can be specified in any order but must identify deployment steps that appear in the system plan specified by the input file. The command processing will fail and none of the identified steps will be performed if an identifier is passed that does not identify a step in the system plan file.
Steps specified might be determined by command processing that already have been completed on the managed system. That will be logged by the command processing, however, is not an error.
This option is useful when only specific steps in a system plan file are desired to be performed. The command processing does not validate that the resulting deployment is valid but it will determine that dependent steps in the system plan will be checked for and enforced. The command processing will fail and none of the identified steps will be performed if there are dependent steps that are not specified. (For example a partition profile must exist before a system plan step to install its OS can be specified.)
Perform dump operation.
dump -m managed-system -t sys -o set -a "attributes" [--help]
dump sets the system dump parameters for the managed-system. This operation is only supported for POWER6 servers.
The format of the configuration data is as follows:
attribute-name=value,attribute-name=value,...
Valid attribute names:
Valid values:
Setting as_needed to 0 will remove the ability of service personnel to diagnose server errors. Do not set as_needed to 0 unless directed to do so by your hardware service representative.
Valid values:
Setting sys_hardware to max will cause system dumps to take longer to complete. Do not set sys_hardware to max unless directed to do so by your hardware service representative.
Valid values:
Setting sys_firware to max, io, virtualio, hps, or hcaio will cause system dumps to take longer to complete. Do not set sys_firware to one of these values unless directed to do so by your hardware service representative.
Get dump.
getdump {-m managed-system | -e managed-frame} -t {pss | sp | sys} [-s {a | b | p | s}] [--help]
getdump offloads a dump from the managed-system or the managed-frame to the Hardware Management Console (HMC). The dump is written to a file in the /dump directory on the HMC.
The lsdump command can be used to list the dumps that are available on the managed-system or the managed-frame.
This option is required when offloading a service processor dump or a platform dump. This option is not valid otherwise.
This option is required when offloading a power subsystem dump. This option is not valid otherwise.
When offloading a service processor dump, use this option to specify the service processor from which to offload the dump. Valid values are p for the primary service processor and s for the secondary service processor. If this option is not specified, the service processor dump will be offloaded from the primary service processor.
Get upgrade files.
getupgfiles -h host-name -u user-ID [--passwd password] -d remote-directory [--help]
getupgfiles obtains required files for a Hardware Management Console (HMC) upgrade from a directory on an FTP server. The files will be transferred onto a special partition on the HMC hard drive. After the files have been transferred, the chhmc command can be used to allow the HMC to boot from this partition and perform the upgrade.
Shut down the Hardware Management Console.
hmcshutdown -t {now | number-of-minutes} [-r] [--help]
hmcshutdown shuts down the Hardware Management Console (HMC). If requested, the HMC will be rebooted after the shutdown completes.
Provides screen capture on HMC.
hmcwin { -o c | v | r } -f file-name [--help]
hmcwin provides screen capture on the HMC.
Network install a Virtual I/O Server Logical Partition.
installios [-p partition-name -i ipaddr-or-hostname -S subnet-mask -g gateway -d path -s system-name -m mac-address -r profile [-n] [-P speed] [-D duplex] [-l language]] | -u
installios installs the Virtual I/O Server. It must be run from the HMC. All of the flags are optional. If no flags are provided, the installios wizard will be invoked and the user will be prompted to interactively enter the information contained in the flags.
Log ssh command usage.
logssh
logssh is a script that can be added to a user's authorized_keys2 file to restrict a user from being able to open a pseudo-tty using ssh. Furthermore, it will log all commands executed by the user in syslog. This command is not intended to be run interactively.
Retrieve MAC address and physical location code from network adapters for a partition or instruct a partition to network boot.
To retrieve MAC address and physical location code:
lpar_netboot -M -n [-v] [-x] [-f] [-i] [-A] -t ent [-D -s speed -d duplex -S server -G gateway -C client] partition-name partition-profile managed-system
To perform network boot:
lpar_netboot [-v] [-x] [-f] [-i] [-g args] [{-A -D | [-D] -l physical-location-code | [-D] -m MAC-address}] -t ent -s speed -d duplex -S server -G gateway -C client partition-name partition-profile managed-system
To retrieve MAC address and physical location code on a system supporting a full system partition:
lpar_netboot -M -n [-v] [-x] [-f] [-i] [-A] -t ent [-D -s speed -d duplex -S server -G gateway -C client] managed-system managed-system
To perform network boot on a system supporting a full system partition:
lpar_netboot [-v] [-x] [-f] [-i] [-g args] [{-A -D | [-D] -l physical-location-code | [-D] -m MAC-address}] -t ent -s speed -d duplex -S server -G gateway -C client managed-system managed-system
lpar_netboot instructs a logical partition to network boot by having it send out a bootp request to a server specified with the -S option. The server can be an AIX NIM server serving SPOT resources or any server serving network boot images. If specified with the -M and -n options, lpar_netboot will return the Media Access Control (MAC) address and the physical location code for a network adapter of the type specified with the -t option. When the -m option is specified, lpar_netboot will boot a partition using the network adapter which has the specified MAC address. When the -l option is specified, lpar_netboot will boot a partition using the network adapter which has the specified physical location code. The MAC address and physical location code of a network adapter is dependent upon the hardware resource allocation in the partition profile the partition was booted with. The lpar_netboot command requires arguments for partition name, partition profile, and the name of the managed system which has the partition.
Perform a partition configuration image operation.
lpcfgop -m managed-system -o {clear | dump} [--help]
lpcfgop clears or dumps partition configuration data on the managed-system.
The clear operation clears all partition configuration data on the managed-system and sets the configuration back to its original state. This operation can only be performed when the managed-system is in the Standby state.
The dump operation dumps all partition configuration data on the managed-system to a file. The file is written to the /tmp directory on the Hardware Management Console (HMC).
List access control configuration information.
lsaccfg -t {resource | resourcerole | taskrole} [--script] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lsaccfg lists managed resource objects, managed resource roles, or task roles.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Multiple values can be specified for each filter.
Valid filter names for managed resource objects:
Valid filter names for managed resource roles:
Valid filter names for task roles:
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List Capacity on Demand information.
lscod -t {bill | cap | code | hist | util} -m managed-system [-c {cuod | mobile | onoff | reserve | trial | trialexc | trialstd | utility | utilityen}] [-r {mem | proc}] [-F [attribute-names] [--header]] [--help]
lscod lists Capacity on Demand (CoD) information for the managed-system.
Reserve CoD is only supported on POWER5 servers. Utility CoD is only supported on POWER6 servers.
This option is required when listing CoD capacity information or CoD code generation information. If this option is not specified when listing shared processor pool utilization information, this option defaults to Reserve CoD. This option is not valid when listing the CoD history log.
To list Trial CoD capacity information, specify trial with this option. To list Trial CoD code generation information, specify trialexc or trialstd with this option.
To list Utility CoD capacity information, specify utility with this option. To list Utility CoD code generation information, specify utility for Utility CoD reporting codes or utilityen for Utility CoD enablement codes.
mobile can only be specified when listing CoD code generation information.
Reserve CoD is only supported on POWER5 servers. Utility CoD is only supported on POWER6 servers.
This option is required when listing On/Off CoD billing information, CoD capacity information, CoD code generation information, or shared processor pool utilization information. This option is not valid when listing the CoD history log.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List dump information.
To list the dumps that are available on a managed system or managed frame:
lsdump {-m managed-system | -e managed-frame} [-r avail] [-s {a | b | p | s}] [-F [attribute-names] [--header]]
To list the managed system dumps and managed frame dumps that are available on the HMC:
lsdump -h [-r avail] [--filter "filter-data"] [-F [attribute-names] [--header]]
To list the system dump parameters (POWER6 servers only):
lsdump -m managed-system -r parm [-F [attribute-names] [--header]]
lsdump lists the dumps that are available on the managed-system or the managed-frame. lsdump can also list the managed system dumps and the managed frame dumps that are available on the Hardware Management Console (HMC).
lsdump also lists the system dump parameters for the managed-system. This is only supported for POWER6 servers.
The getdump command can be used to offload an available dump from the managed-system or the managed-frame to the HMC.
The cpdump command can be used to copy a dump from the HMC to DVD or a remote FTP site.
Either this option, the -e option, or the -h option is required. The -m, -e, and the -h options are mutually exclusive.
Either this option, the -m option, or the -h option is required. The -e, -m, and the -h options are mutually exclusive
.Either this option, the -m option, or the -e option is required. The -h, -m, and the -e options are mutually exclusive.
System dump parameters can only be listed on POWER6 servers.
When listing dumps that are available on a managed system, use this option to specify the service processor for which available dumps are to be listed. Valid values are p for the primary service processor and s for the secondary service processor. If this option is not specified, available dumps on the primary service processor will be listed. Platform dumps are only available from the primary service processor.
This option is not valid when listing the managed system dumps and managed frame dumps that are available on the HMC.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Valid filter names for this command:
Valid values are:
This option is not valid when listing the dumps that are available on a managed system or managed frame, or when listing the system dump paramters.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List Hardware Management Console configuration information.
lshmc {-b | -l | -L | -n | -r | -v | -V} [-F [attribute-names] [--header]] [--help]
lshmc lists Hardware Management Console (HMC) configuration information. This command can be used to list the BIOS level, current locale, supported locales, network settings, remote access settings, Vital Product Data (VPD) information, and version information for the HMC.
This option cannot be specified with the -l, -L, -n, -r, -v, or -V options.
This option cannot be specified with the -b, -L, -n, -r, -v, or -V options.
This option cannot be specified with the -b, -l, -n, -r, -v, or -V options.
This option cannot be specified with the -b, -l, -L, -r, -v, or -V options.
This option cannot be specified with the -b, -l, -L, -n, -v, or -V options.
This option cannot be specified with the -b, -l, -L, -n, -r, or -V options.
This option cannot be specified with the -b, -l, -L, -n, -r, or -v options.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List Hardware Management Console user information.
lshmcusr [--script] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lshmcusr lists Hardware Management Console (HMC) user information.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Multiple values can be specified for each filter.
Valid filter names for this command:
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List environmental information.
lshwinfo -r {frame | sys} -e managed-frame [-F [attribute-names] [--header]] [--help]
lshwinfo lists environmental information, such as input power levels and ambient air temperatures, for the managed-frame.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List hardware resources.
To list physical I/O resources:
lshwres -r io --rsubtype {unit | bus | slot | iopool | taggedio} -m managed-system [--level {pool | sys}] [-R] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list virtual I/O resources:
lshwres -r virtualio --rsubtype {eth | hsl | virtualopti | scsi | serial | slot} -m managed-system [--level {lpar | slot | sys}] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list memory resources:
lshwres -r mem -m managed-system --level {lpar | sys} [-R] [--maxmem quantity] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list processing resources:
lshwres -r proc -m managed-system --level {lpar | pool | sys} [-R] [--procunits quantity] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list Host Channel adapter (HCA) resources:
lshwres -r hca -m managed-system --level {lpar | sys} [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list Host Ethernet adapter (HEA) resources (POWER6 servers only):
lshwres -r hea -m managed-system --rsubtype {logical | phys} --level {port | port_group | sys} [-R] [--stat] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list Switch Network Interface (SNI) adapter resources:
lshwres -r sni -m managed-system [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lshwres lists the hardware resources of the managed-system, including physical I/O, virtual I/O, memory, processing, Host Channel adapter (HCA), Host ethernet adapter (HEA) and Switch Network Interface (SNI) adapter resources.
HEA resources are only supported on POWER6 servers.
This option is required when listing physical I/O, virtual I/O resources, or HEA resources. This option is not valid when listing memory, processing, HCA, or SNI adapter resources.
This option is required when listing I/O pool resources, virtual ethernet, serial, or slot resources, or memory, processing, HCA, or HEA resources.
Valid levels for I/O pool resources are pool or sys. Valid levels for virtual ethernet resources are lpar or sys. Valid levels for virtual serial resources are lpar. Valid levels for virtual slot resources are lpar or slot. Valid levels for memory resources are lpar or sys. Valid levels for processing resources are lpar, pool, or sys. Valid levels for HCA resources are lpar or sys. Valid levels for physical HEA resources are port, port_group, or sys. Valid levels for logical HEA resources are port or sys.
rsthwres command can be used to restore those hardware resources.
This option is only valid for listing physical I/O slots, partition level memory or processing resources, or logical HEA resources.
This information is useful for specifying memory amounts in partition profiles.
The required minimum memory amount listed is the minimum memory amount required for a partition by the managed system's system firmware. An operating system installed on the partition may require more memory than the amount listed.
This option is only valid when listing system level memory resources.
This information is useful when specifying the 5250 CPW percentages for partitions or partition profiles.
This option is only valid when listing system level processing resources. Also, this option is only valid when the managed-system supports the assignment of 5250 CPW percentages to partitions.
This option is only valid when listing HEA physical port resources.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Unless otherwise indicated, multiple values can be specified for each filter.
Valid filter names for this command:
Valid filters with -r io --rsubtype unit:
units
Valid filters with -r io --rsubtype bus:
buses, units
Valid filters with -r io --rsubtype slot:
buses, lpar_ids | lpar_names, pools, slots, units
Valid filters with -r io --rsubtype iopool --level pool:
lpar_ids | lpar_names, pools
Valid filters with -r io --rsubtype taggedio:
lpar_ids | lpar_names
Valid filters with -r virtualio --rsubtype eth --level lpar:
lpar_ids | lpar_names, slots, vlans
Valid filters with -r virtualio --rsubtype hsl:
lpar_ids | lpar_names, pools
Valid filters with -r virtualio --rsubtype virtualopti:
lpar_ids | lpar_names, pools
Valid filters with -r virtualio --rsubtype scsi:
lpar_ids | lpar_names, slots
Valid filters with -r virtualio --rsubtype serial --level lpar:
lpar_ids | lpar_names, slots
Valid filters with -r virtualio --rsubtype slot --level lpar:
lpar_ids | lpar_names
Valid filters with -r virtualio --rsubtype slot --level slot:
lpar_ids | lpar_names, slots
Valid filters with -r mem --level lpar:
lpar_ids | lpar_names
Valid filters with -r proc --level lpar:
lpar_ids | lpar_names
Valid filters with -r hca --level sys:
adapter_ids
Valid filters with -r hca --level lpar:
adapter_ids, lpar_ids | lpar_names
Valid filters with -r hea --rsubtype logical --level sys:
adapter_ids, lpar_ids | lpar_names
Valid filters with -r hea --rsubtype logical --level port:
adapter_ids, lpar_ids | lpar_names, port_groups
Valid filters with -r hea --rsubtype phys --level sys:
adapter_ids
Valid filters with -r hea --rsubtype phys --level port:
adapter_ids, port_groups
Valid filters with -r hea --rsubtype phys --level port_group:
adapter_ids, port_groups
Valid filters with -r sni:
lpar_ids | lpar_names, sni_device_ids
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List LEDs.
lsled -r sa -t {phys | virtuallpar | virtualsys} -m managed-system [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lsled lists LED information for the managed-system.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Valid filter names for this command are lpar_names or lpar_ids. Only one of these filters may be specified. Multiple partitions can be specified with the filter.
This option is not valid when listing the physical SA LED or the virtual SA LED for the managed-system.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List Licensed Internal Code levels.
lslic {-m managed-system | -e managed-frame | -w} [-t {sys | power | syspower | powerfru}] [-r {ibmretain | ibmwebsite | ftp | dvd | disk | mountpoint} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-F [attribute-names] [--header]] [--help]
lsled lists Licensed Internal Code (LIC) levels installed, activated, and accepted. The LIC levels that are available to be retrieved from a repository can also be listed.
This option is required when displaying LIC levels that are available to be retrieved from a remote FTP site. This option is not valid otherwise.
This option is required when displaying LIC levels that are available to be retrieved from a remote FTP site. This option is not valid otherwise.
This option is only valid when displaying LIC levels that are available to be retrieved from a remote FTP site.
This option is only valid when displaying LIC levels that are available to be retrieved from a mountpoint or a remote FTP site.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List lock information.
lslock -e managed-frame [-F [attribute-names] [--header]] [--help]
lslock lists which Hardware Management Console (HMC) owns the lock on the managed-frame. If the managed-frame is not locked, then "No results were found." will be displayed.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List utilization data.
To list utilization data collected for a managed system:
lslparutil -r {hmc | lpar | pool | sys | all} -m managed-system [-d number-of-days] [-h number-of-hours] [--startyear year] [--startmonth month] [--startday day] [--starthour hour] [--endyear year] [--endmonth month] [--endday day] [--endhour hour] [-n number-of-events] [-s sample-rate] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
To list HMC settings for utilization data collection:
lslparutil -r config [-m managed-system] [-F [attribute-names] [--header]] [--help]
lslparutil lists utilization data collected for a managed-system. This command also lists the Hardware Management Console (HMC) settings for utilization data collection.
The HMC collects the following types of utilization data: sampling events, state change events, configuration change events, and Utility Capacity on Demand (CoD) processor usage events.
Sampling events are collected for the managed system, for each partition in the managed system, and for the shared processor pool in the managed system. Sampling events are collected hourly, daily at midnight, and monthly at midnight on the first day of each month. Sampling events are also collected immediately following the collection of a Utility CoD processor usage event. Sampling events contain information about memory and processor utilization.
State change events are collected for the managed system, for each partition in the managed system, and for the HMC. State change events are collected when a state change occurs for the managed system, a partition, or when the HMC is started or shut down.
Configuration change events are collected for the managed system, for each partition in the managed system, and for the HMC. Configuration change events are collected when a configuration change affecting memory or processor resources occurs for the managed system or for a partition. Configuration change events are also collected when the local time is changed on the HMC.
Utility CoD processor usage events are collected for the managed system when a Utility CoD processor minute is used. All Utility CoD processor minutes used during a single minute are grouped into one event.
Hourly sampling events and all state change, configuration change, and Utility CoD processor usage events collected are only saved on the HMC for about 2 months. Daily sampling events are saved for about 2 years, and monthly sampling events are saved for about 10 years.
Utilization data collection for managed systems is not automatically enabled. The chlparutil command can be used to enable utilization data collection.
If this option is specified when listing HMC configuration settings, then the HMC configuration settings for the managed-system will be listed. Otherwise, the HMC configuration settings for all of the systems currently managed by this HMC, and for all of the systems for which utilization data has been previously collected by this HMC will be listed.
This option cannot be specified with the -h, --startyear, --startmonth, --startday, --starthour, --endyear, --endmonth, --endday, or --endhour options.
This option cannot be specified with the -d, --startyear, --startmonth, --startday, --starthour, --endyear, --endmonth, --endday, or --endhour options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
This option cannot be specified with the -d or -h options.
If this option is not specified, and neither are any of the -d, -h, --startyear, --startmonth, --startday, --starthour, --endyear, --endmonth, --endday, or --endhour options, then only the most recent event will be listed.
If this option is not specified, then hourly sampling events and all state change, configuration change, and Utility CoD processor usage events will be listed.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Multiple values can be specified for each filter.
Valid filter names for this command:
sample, state_change, config_change, utility_cod_proc_usage
Valid filters with -r hmc:
Valid filters with -r lpar:
Valid filters with -r pool:
Valid filters with -r sys:
Valid filters with -r all:
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
Command attributes:
List storage media devices.
lsmediadev [-F [attribute-names] [--header]] [--help]
lsmediadev lists the storage media devices that are available for use on the Hardware Management Console (HMC).
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List reference codes.
lsrefcode -r {sys | lpar} -m managed-system [-s {p | s}] [-n number] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lsrefcode lists reference codes for the managed-system or for partitions in the managed-system.
This option is only valid when listing managed system reference codes.
The number specified must be greater than 0. If there are fewer reference codes available than number, only the available reference codes will be listed.
If this option is omitted, only the current reference code will be listed.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
filter-name=value,filter-name=value,...<LF>
Note that certain filters accept a comma separated list of values, as follows:
"filter-name=value,value,...",...<LF>
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Valid filter names for this command are lpar_names or lpar_ids. Only one of these filters may be specified. Multiple partitions can be specified with the filter.
This option is not valid when listing managed system reference codes.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List Service Agent configuration information.
lssacfg -t {email | ftpfirewall | ftpoffload | snmp | snmptrapnames} [-F [attribute-names] [--header]] [--help]
lssacfg lists Service Agent configuration information.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List console or serviceable events.
lssvcevents -t {console | hardware} [-d number-of-days | -i number-of-minutes] [-m managed-system] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lssvcevents lists console events logged by the Hardware Management Console (HMC), or serviceable events.
If this option is omitted when listing console events, console events that occurred within the past 7 days will be listed.
If this option is omitted when listing serviceable events, all serviceable events will be listed.
If this option is omitted, all serviceable events will be listed.
This option is only valid when listing serviceable events.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Multiple values can be specified for each filter.
Valid filter names for serviceable events:
This option is not valid when listing console events.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List system resources.
lssyscfg -r {lpar | prof | sys | sysprof | cage | frame} [-m managed-system | -e managed-frame] [--filter "filter-data"] [-F [attribute-names] [--header]] [--help]
lssyscfg lists the attributes of partitions, partition profiles, or system profiles for the managed-system. It can also list the attributes of the managed-system, and of all of the systems managed by this Hardware Management Console (HMC).
lssyscfg can also list the attributes of cages in the managed-frame, the attributes of the managed-frame, or the attributes of all of the frames managed by this HMC.
This option is required when listing partitions, partition profiles, or system profiles. This option is optional when listing managed systems, and if it is omitted, then all of the systems managed by this HMC will be listed. This option is not valid when listing managed frame cages or managed frames.
This option is required when listing managed frame cages. This option is optional when listing managed frames, and if it is omitted, then all of the frames managed by this HMC will be listed. This option is not valid when listing partitions, partition profiles, system profiles, or managed systems.
The filter data consists of filter name/value pairs, which are in comma separated value (CSV) format. The filter data must be enclosed in double quotes.
The format of the filter data is as follows:
"filter-name=value,filter-name=value,..."
Note that certain filters accept a comma separated list of values, as follows:
""filter-name=value,value,...",..."
When a list of values is specified, the filter name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character. Multiple values can be specified for each filter.
Valid filter names for partitions:
Valid filter names for partition profiles:
lpar_names | lpar_ids, profile_names
Valid filter names for system profiles:
profile_names
This option is not valid when listing managed systems, managed frame cages, or managed frames.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List system connections.
lssysconn -r all [-F [attribute-names] [--header]] [--help]
lssysconn lists connection information for all of the systems and frames managed by this Hardware Management Console (HMC). Connection information for all systems and frames to which this HMC is connected or attempting to connect is listed.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List system plans.
lssysplan [-F [attribute-names] [--header]] [--help]
lssysplan lists the system plan files in the system plan file directory on the Hardware Management Console (HMC).
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
The possible attributes that can be listed are: name, description, source, version, and date.
List system plan resources.
lssysplanres -r osinstall [-F [attribute-names][--header]] [--help]
lssysplanres lists the system plan resources that are defined on this Hardware Management Console (HMC). These resources can be used when deploying system plans from this HMC.
When this option is specified, only those specified attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
List Capacity on Demand advanced functions activation information.
lsvet -t {code | hist} -m managed-system [-F [attribute-names] [--header]] [--help]
lsvet lists Capacity on Demand (CoD) advanced functions activation information for the managed-system. CoD advanced functions include Advanced POWER Virtualization and Enterprise Enablement.
CoD advanced functions are sometimes referred to as Virtualization Engine systems technologies.
When this option is specified, only attribute values will be displayed. No attribute names will be displayed. The attribute values displayed will be separated by the delimiter which was specified with this option.
This option is useful when only attribute values are desired to be displayed, or when the values of only selected attributes are desired to be displayed.
Migrate configuration.
migrcfg -m managed-system -t 1 -f file [--help]
migrcfg migrates partition configuration data to a managed-system.
Create access control object.
mkaccfg -t {resourcerole | taskrole} {-f configuration-file | -i "configuration-data"} [--help]
mkaccfg creates a new access control role.
The format of a configuration record is as follows:
attribute-name=value,attribute-name=value,...<LF>
Note that certain attributes accept a comma separated list of values, as follows:
"attribute-name=value,value,...",...<LF>
When a list of values is specified, the attribute name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Attribute names for managed resource roles (all attributes are required):
Attribute names for task roles (all attributes are required):
The -f and the -i options are mutually exclusive.
The -i and the -f options are mutually exclusive.
Create a Hardware Management Console user.
mkhmcusr -u user-name -a task-role [-d description] [--passwd password] [-M number-of-days] [--help]
mkhmcusr creates a Hardware Management Console (HMC) user.
Create system resources.
mksyscfg -r {lpar | prof | sysprof} -m managed-system [{-f configuration-file | -i"configuration-data"}] [-o save {-p partition-name | --id partition-ID} [-n profile-name] [--help]
mksyscfg creates partitions, partition profiles, or system profiles for the managed-system.
mksyscfg can be used to save the current configuration of a partition to a new partition profile.
When a partition is created, the default profile for the partition is also created.
The format of a configuration record is as follows:
attribute-name=value,attribute-name=value,...<LF>
Note that certain attributes accept a comma separated list of values, as follows:
"attribute-name=value,value,...",...<LF>
When a list of values is specified, the attribute name/value pair must be enclosed in double quotes. Depending on the shell being used, nested double quote characters may need to be preceded by an escape character, which is usually a '\' character.
Attribute names for partitions (see below for attribute names that are common to both partitions and partition profiles):
[lpar_id]
Attribute names for partition profiles (see below for attribute names that are common to both partition profiles and partitions):
Attribute names for both partitions and partition profiles:
Valid values for partitions using shared processors are:
slot-DRC-index/slot-IO-pool-ID/ is-required
Both '/' characters must be present, but optional values may be omitted. Optional values are slot-IO-pool-ID.
Valid values for is-required:
Valid values are:
Valid values are:
Valid values are:
virtual-slot-number/is-IEEE/ port-vlan-ID/additional-vlan-IDs/ trunk-priority/is-required
All 5 '/' characters must be present, but optional values may be omitted. Optional values are additional-vlan-IDs and trunk-priority.
Valid values for is-IEEE and is-required:
Valid values for trunk priority:
virtual-slot-number/client-or-server/remote-lpar-ID/remote-lpar-name/remote-slot-number/is-required
All 5 '/' characters must be present, but optional values may be omitted. Optional values for server adapters are remote-lpar-ID, remote-lpar-name, and remote-slot-number. Optional values for client adapters are remote-lpar-ID or remote-lpar-name (one of those values is required, but not both).
Valid values for client-or-server:
Valid values for is-required:
virtual-slot-number/client-or-server/supports-HMC/remote-lpar-ID/remote-lpar-name/remote-slot-number/is-required
All 6 '/' characters must be present, but optional values may be omitted. Optional values for server adapters are supports-HMC, remote-lpar-ID, remote-lpar-name, and remote-slot-number. Optional values for client adapters are remote-lpar-ID or remote-lpar-name (one of those values is required, but not both), and the supports-HMC value is not allowed.
Valid values for client-or-server:
Valid values for supports-HMC:
Valid values for is-required:
Comma separated list of Host Channel adapters (HCA), with each adapter having the following format:
adapter-ID/GUID/capability
All 3 values must be specified for each adapter.
Valid values for capability:
Comma separated list of Logical Host Ethernet adapter (LHEA) logical ports, with each logical port having the following format:
adapter-ID/port-group/physical-port-ID/ logical-port-ID/allowed-VLAN-IDs
All 4 '/' characters must be present, but optional values may be omitted. Optional values are allowed-VLAN-IDs.
adapter-ID/capability
or
adapter-ID/5/ieq/nieq/qp/cq/mr
where ieq (interruptible event queues), nieq (non-interruptible event queues), qp (queue pairs), cq (completion queues), and mr (memory regions) each specify the resource amount in addition to the base minimum.
Valid values for capability:
Comma separated list of Switch Network Interface (SNI) adapter device IDs
Valid values are:
Valid values are:
Attribute names for system profiles:
Brackets around an attribute name indicate that the attribute is optional.
The -f and the -i options are mutually exclusive.
Configuration data is required to be specified with this option or the -i option except when -o save is specified to save the current configuration of a partition to a new partition profile. This option is not valid when -o save is specified.
When this option is used, only a single system resource can be created.
The -i and the -f options are mutually exclusive.
Configuration data is required to be specified with this option or the -f option except when -o save is specified to save the current configuration of a partition to a new partition profile. This option is not valid when -o save is specified.
If this option is not specified, then new system resources will be created using the configuration data specified with the -f or -i option.
You can either use this option to specify the name of the partition whose current configuration is to be saved, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
A partition is required to be specified with this option or the --id option when -o save is specified to save the current configuration of a partition to a new partition profile. This option is not valid otherwise.
A partition is required to be specified with this option or the -p option when -o save is specified to save the current configuration of a partition to a new partition profile. This option is not valid otherwise.
This option is required when -o save is specified to save the current configuration of a partition to a new partition profile. This option is not valid otherwise.
Create system connection.
mksysconn --ip IP-address [-r {sys | frame}] [--passwd password] [--help]
mksysconn establishes a connection from the Hardware Management Console (HMC) to a system in the network and adds the system to the systems managed by the HMC. If a connection to the system cannot be established because the network is down, the service processor for the system is down, or too many other HMCs have already established a connection to the system, the system will be added as a managed system which is in the No Connection state.
mksysconn can also establish a connection from the HMC to a frame in the network and add the frame to the frames managed by the HMC. If a connection to the frame cannot be established because the network is down, the bulk power assembly (BPA) for the frame is down, or too many other HMCs have already established a connection to the frame, the frame will be added as a managed frame which is in the No Connection state.
If your HMC is set up as a DHCP server on a private network, do not use this command to establish HMC connections to managed systems and frames that are DHCP clients. This command is intended for use on a public network only, where the systems are set to use static IP addresses. Using this command in a DHCP environment establishes a temporary connection that will not continue to work properly over network configuration changes, system power loss, and service repair actions.
To connect to a frame and add the frame to the frames managed by the HMC, specify the IP address or host name of one side of the bulk power assembly (BPA) for the frame. Note that to properly connect to a frame, it is recommended that you issue this command twice, once for each side of the BPA, in order to connect to both sides of the BPA for the frame.
Make system plan file.
mksysplan -f file-name -m managed-system [--check] [-d "description"] [-o noprobe] [-v] [--help]
mksysplan creates a system plan file that represents the information known about a managed system's hardware, partitions, profiles, and partition provisioning information.
The file name is restricted to the alphanumeric characters (upper and lower case) and a set of special characters (comma, period, hyphen, underscore, and space). The file name cannot begin with a period or hyphen.
The file name must end with the .sysplan suffix.
The name may either be the user-defined name for the managed system, or be in the form tttt-mmm*ssssssss, where tttt is the machine type, mmm is the model, and ssssssss is the serial number of the managed system. The tttt-mmm*ssssssss form must be used if there are multiple managed systems with the same user-defined name.
Open a virtual terminal session.
mkvterm -m managed-system {-p partition-name | --id partition-ID} [--help]
mkvterm opens a virtual terminal session for an AIX, Linux, or virtual I/O server partition.
After establishing a virtual terminal session, the ~ character sequence can be entered in the terminal window to terminate it, or the rmvterm command can be used to force the session to be closed.
A partition can only have one open virtual terminal session at a time.
You must either use this option to specify the name of the partition, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
You must either use this option to specify the ID of the partition, or use the -p option to specify the partition's name. The --id and the -p options are mutually exclusive.
Monitor HMC subsystems and system resources.
To monitor Hardware Management Console (HMC) subsystems:
monhmc -s {hmcsvr | rmc} [-n <interval>] [--help]
To monitor HMC system resources:
monhmc -r {disk | proc | mem | swap} [-n <interval>] [--help]
monhmc provides a dynamic real-time view of HMC related subsystems and system resources. The top, watch, and df commands are used to implement this command. Refer to documentation for those commands for additional information.
Either this option or the -r option is required. The -s and the -r options are mutually exclusive.
Either this option or the -s option is required. The -r and the -s options are mutually exclusive
If an interval of 0 is specified, then statistics are displayed only once, and this command exits. If any other interval is specified, or if this option is omitted, then statistics are updated every interval seconds, and this command runs until interrupted with Ctrl-c.
Product Engineering debug tools.
pedbg {-d {on | off} | -j {on | off} | -l {rmc | se} | -c | -s | -q {n} | -r} [--help]
pedbg provides debug tools for Product Engineer/Support Personnel. This command requires PE authority to run, i.e, only hscpe user can access this command.
Options for log collection:
Options for managed system dumps:
Provides PE Shell access.
pesh <serial number of machine>
pesh provides full shell access to Product Engineer/Support Personnel. pesh takes the serial number of the machine where full shell access is requested, then prompts the user for a 1 day password obtained from the support organization. If the password is valid, the user will be granted full shell access. Only user hscpe can access this command.
Remove access control object.
rmaccfg -t {resource | resourcerole | taskrole} -n name [--help]
rmaccfg removes an access control role from the Hardware Management Console (HMC), or it removes inactive managed resource objects assigned to an HMC user.
When removing an access control role, use this option to specify the name of the role to remove. Note that the predefined task roles hmcsuperadmin, hmcoperator, hmcviewer, hmcpe, and hmcservicerep cannot be removed.
If the specified access control role is currently assigned to one or more HMC users, you will be prompted to confirm that you want to remove the role.
Remove a Hardware Management Console user.
rmhmcusr -u user-name [--help]
rmhmcusr removes a Hardware Management Console (HMC) user.
Remove lock.
rmlock -e managed-frame [--help]
rmlock forces a Hardware Management Console (HMC) lock on the managed-frame to be released.
Remove utilization data.
rmlparutil -m managed-system [--help]
rmlparutil removes the utilization data collected for a managed system from the Hardware Management Console (HMC).
Removing the utilization data for a managed system does not disable the collection of utilization data for that managed system. Use the chlparutil command to disable the collection of utilization data.
Remove profile data.
rmprofdata -m managed-system -f file [--help]
rmprofdata removes a profile data backup file for the managed-system.
To remove profile data from removable media, the media must be present in the removable media device and the device must be mounted with the mount command before this command is issued. The lsmediadev command can be used to display all of the removable media devices on the HMC.
Remove a system resource.
rmsyscfg -r {lpar | prof | sysprof} -m managed-system [-n resource-name] [-p partition-name] [--id partition-ID] [--help]
rmsyscfg removes a partition, a partition profile, or a system profile from the managed-system.
When a partition is removed, all of the partition profiles that are defined for that partition are also removed.
When a partition profile is removed, any system profiles that contain just that one partition profile are also removed.
To remove a partition, you must either use this option to specify the name of the partition to remove, or use the --id option to specify the partition's ID. The -n and the --id options are mutually exclusive when removing a partition.
To remove a partition profile or a system profile, you must use this option to specify the name of the profile to remove.
To remove a partition profile, you must either use this option to specify the name of the partition which has the partition profile to remove, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
To remove a partition, you must either use this option to specify the ID of the partition to remove, or use the -n option to specify the partition's name. The --id and the -n options are mutually exclusive when removing a partition.
To remove a partition profile, you must either use this option to specify the ID of the partition that has the profile to remove, or use the -p option to specify the partition's name. The --id and the -p options are mutually exclusive when removing a partition profile.
This option is not valid when removing a system profile.
Remove a system connection.
rmsysconn -o {remove | reset} {-m managed-system | -e managed-frame | --ip IP-address} [--help]]
rmsysconn removes or resets a connection from the Hardware Management Console (HMC) to a managed system or a managed frame.
If your HMC is set up as a DHCP server on a private network, do not use this command to remove HMC connections to managed systems and frames. The remove option of this command is intended for use on a public network only, where the HMC is not set up as a DHCP server. Using the remove option of this command prevents the HMC from managing any system or frame at that IP address, even though that address may still be assigned through DHCP.
When reset is specified, the HMC disconnects from the specified managed system or the specified managed frame then attempts to reconnect.
The reset operation is useful for retrying to establish a connection to a managed system or a managed frame that is in the "No Connection" state.
If the managed system has a single service processor, the connection to the service processor is removed or reset. When the connection is removed, the managed system is removed from the HMC.
If the managed system has two service processors, the connections to both service processors for the managed system are removed or reset. When the connections to both service processors for the managed system are removed, the managed system is removed from the HMC. To remove or reset the connection to just one service processor for the managed system, use the --ip option.
Either this option, the --ip option, or the -e option is required. The -m, --ip, and the -e options are mutually exclusive.
When this option is used to specify the managed frame to remove or to reset the connection to, the connections to both sides of the bulk power assembly (BPA) for the managed frame are removed or reset. When the connections to both sides of the BPA for the managed frame are removed, the managed frame is removed from the HMC.
To remove or reset the connection to just one side of the BPA for the managed frame, use the --ip option.
Either this option, the --ip option, or the -m option is required. The -e, --ip, and the -m options are mutually exclusive.
To remove or reset the connection to just one service processor for a managed system with two service processors, you can use this option to specify the IP address or host name of the service processor to remove or to reset the connection to. To remove or reset the connection to both service processors for a managed system, use the -m option. Note that a managed system with two service processors will not be removed from the HMC until the connections to both service processors for the managed system are removed.
To remove or reset the connection to just one side of the BPA for a managed frame, you can use this option to specify the IP address or host name of the BPA side to remove or to reset the connection to. To remove or reset the connection to both sides of the BPA for a managed frame, use the -e option. Note that a managed frame will not be removed from the HMC until the connections to both sides of the BPA for the managed frame are removed.
Either this option, the -m option, or the -e option is required. The --ip, -m, and the -e options are mutually exclusive.
Remove system plan.
rmsysplan -f file-name [--help]
rmsysplan removes a system plan file from the system plan file directory on the Hardware Management Console (HMC).
Remove system plan resource.
rmsysplanres -r osinstall -n resource-name [--help]
rmsysplanres removes a system plan resource that is defined on this Hardware Management Console (HMC). These resources can be used when deploying system plans from this HMC.
Close a virtual terminal session.
rmvterm -m managed-system {-p partition-name | --id partition-ID} [--help]
rmvterm forces the closure of a virtual terminal session for an AIX, Linux, or virtual I/O server partition.
To close the virtual terminal session normally, enter the ~. character sequence in the terminal window.
You must either use this option to specify the name of the partition, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
You must either use this option to specify the ID of the partition, or use the -p option to specify the partition's name. The --id and the -p options are mutually exclusive.
Restore hardware resources.
To restore memory or processing resources:
rsthwres -r {mem | proc} -m managed-system [{-p partition-name | --id partition-ID}]
To restore physical I/O slots:
rsthwres -r io -m managed-system [{-p partition-name | --id partition-ID}] [-l slot-DRC-index]
To restore Host Ethernet Adapter (HEA) resources (POWER6 servers only):
rsthwres -r hea -m managed-system [{-p partition-name | --id partition-ID}] [-l HEA-adapter-ID] [-g port-group --logport logical-port-ID]
rsthwres restores the hardware resource configuration of partitions in the managed-system. This operation may need to be performed after a dynamic logical partitioning (DLPAR) operation fails.
HEA resources are only supported on POWER6 servers.
To restore hardware resources for a single partition, you must either use this option to specify the name of the partition, or use the --id option to specify the partition's ID. Otherwise, hardware resources for all partitions in the managed-system will be restored.
The -p and the --id options are mutually exclusive.
To restore hardware resources for a single partition, you must either use this option to specify the ID of the partition, or use the -p option to specify the partition's name. Otherwise, hardware resources for all partitions in the managed-system will be restored.
The --id and the -p options are mutually exclusive.
When restoring HEA resources, specify the adapter ID of the HEA to restore. If this option is omitted and a partition is specified with the -p or --id option, then all HEA resources, including Logical Host Ethernet Adapters and logical ports, assigned to the specified partition will be restored. If this option is omitted and a partition is not specified, then all HEA resources in the managed-system will be restored. This option is required when the -g and --logport options are specified to restore a specific logical port.
This option is only valid when restoring physical I/O slots or HEA resources.
Restore profile data.
rstprofdata -m managed-system -l restore-type [-f file] [--help]
rstprofdata restores profile data for the managed-system from a backup file. rstprofdata can also be used to initialize the profile data for the managed-system.
The bkprofdata command can be used to back up profile data for the managed-system.
1 - full restore from the backup file.
2 - merge the current profile data and profile data from the backup file, giving priority to the backup data. If the profile data conflicts, the backup data is restored over the current data.
3 - merge the current profile data and profile data from the backup file, giving priority to the current data. If the profile data conflicts, the backup data is not restored over the current data.
4 - initialize the profile data. All partitions, partition profiles, and system profiles for the managed system will be deleted.
To restore the profile data from removable media, the media must be present in the removable media device and the device must be mounted with the mount command before this command is issued. The lsmediadev command can be used to display all of the removable media devices on the HMC.
This option is required for all restore types except 4 (initialize).
Restore upgrade data.
rstupgdata -r dvd [--help]
rstupgdata copies the current partition profile data, Hardware Management Console (HMC) user data, and HMC configuration data previously saved on DVD-RAM into a portion of the HMC hard drive that the HMC upgrade process cannot erase. After this command has been executed, reboot the HMC to automatically recover the data.
The DVD-RAM media must be present in the drive, and mounted with the mount command, before running this command.
Save upgrade data.
saveupgdata -r {disk | diskdvd} [--help]
saveupgdata stores the current partition profile data, Hardware Management Console (HMC) user data, and HMC configuration data in a portion of the HMC hard drive that the HMC upgrade process cannot erase. The HMC automatically recovers the data after the upgrade process completes.
This command should be run immediately prior to performing an HMC upgrade. If the HMC is rebooted without performing an upgrade after running this command, this command needs to be run again.
If diskdvd is specified, then in addition to storing the upgrade data on the HMC hard drive, this command will copy the same upgrade data onto DVD-RAM media. You must ensure that the media is present in the DVD drive and that the DVD drive is mounted with the mount command before issuing this command.
Transfer file from the HMC to a remote system.
sendfile -f filename -h remote-system -d remote-directory -u user [--passwd password] [-s] [-k keyfile] [--help]
sendfile transfer a file from the HMC to a remote system using File Transfer Protocol. Optionally allows Secure FTP over an encrypted ssh transport to be used. When selecting the secure ftp option, user have the option to specify an identity key file, generated by the ssh-keygen command for public key authentication. If the matching public key file resides on the remote system, and the passphrase is empty, no password will be prompted.
Start dump.
startdump {-m managed-system | -e managed-frame} -t {pss | sp | sys} [-s {a | b | p | s}] [--help]
startdump initiates a dump on the managed-system or the managed-frame.
The lsdump command can be used to determine when the dump has completed and is available. The getdump command can then be used to offload the dump from the managed-system or the managed-frame to the Hardware Management Console (HMC).
This option is required when initiating a service processor dump or a platform dump. This option is not valid otherwise.
This option is required when initiating a power subsystem dump. This option is not valid otherwise.
When a service processor dump is started on the primary service processor, all communications between the HMC and the managed-system will be halted. When the dump has completed, communications will be resumed.
When a platform dump is started, the managed-system will be halted. When the dump has completed, the managed-system will be restarted.
When initiating a service processor dump, use this option to specify the service processor on which to initiate the dump. Valid values are p for the primary service processor and s for the secondary service processor. If this option is not specified, the service processor dump will be initiated on the primary service processor.
Update code on the Hardware Management Console.
updhmc -t {m | s | l} [-h ftp-server -u user-id [-p password | -i]] [-f patch-file] [-r] [-c] [--help]
updhmc updates code on the Hardware Management Console (HMC). This command performs the equivalent of the Install Corrective Service task under Licensed Internal Code Maintenance/HMC Code Update on the console.
Update Licensed Internal Code (LIC).
To retrieve, install, and activate LIC updates on a managed system:
updlic -o a -m managed-system -t {sys | power | syspower | io | all} -r {ibmretain | ibmwebsite | ftp | dvd | disk | mountpoint} -l {latest | latestconcurrent | sss | ccc,ppp} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-q]
To retrieve and install, but not activate LIC updates on a managed system:
updlic -o i -m managed-system -t {sys | power | syspower | io | all} -r {ibmretain | ibmwebsite | ftp | dvd | disk | mountpoint} -l {latest | latestconcurrent | sss | ccc,ppp} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-q]
To remove the most recently installed LIC updates and activate the previously accepted level on a managed system:
updlic -o r -m managed-system -t syspower [-q]
To change a managed system's LIC update control to the Hardware Management Console (HMC):
updlic -o h -m managed-system
To change a managed system's LIC update control to Operating System:
updlic -o o -m managed-system
To disruptively activate LIC updates on a managed system:
updlic -o d -m managed-system [-q]
To accept currently activated LIC updates on a managed system:
updlic -o c -m managed-system
To reject installed LIC updates on a managed system:
updlic -o j -m managed-system
To upgrade Licensed Internal Code to a new release on a managed system:
updlic -o u -m managed-system -r {ibmretain | ibmwebsite | ftp | dvd | mountpoint} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-q]
To check system readiness on a managed system:
updlic -o k -m managed-system
To retrieve, install, and activate LIC updates on all High Performance Switches managed by the HMC:
updlic -o a -w -r {ibmretain | ibmwebsite | ftp | dvd | disk | mountpoint} -l {latest | latestconcurrent | sss | ccc,ppp} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-q]
To retrieve and install, but not activate LIC updates on all High Performance Switches managed by the HMC:
updlic -o i -w -r {ibmretain | ibmwebsite | ftp | dvd | disk | mountpoint} -l {latest | latestconcurrent | sss | ccc,ppp} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-q]
To remove the most recently installed LIC updates and activate the previously accepted level on all High Performance Switches managed by the HMC:
updlic -o r -w [-q]
To disruptively activate LIC updates on all High Performance Switches managed by the HMC:
updlic -o d -w [-q]
To accept currently activated LIC updates on all High Performance Switches managed by the HMC:
updlic -o c -w
To reject installed LIC updates on all High Performance Switches managed by the HMC:
updlic -o j -w
To upgrade Licensed Internal Code to a new release on all High Performance Switches managed by the HMC:
updlic -o u -w -r {ibmretain | ibmwebsite | ftp | dvd | mountpoint} [-h host-name] [-u user-ID] [--passwd password] [-d directory] [-q]
To check system readiness on all High Performance Switches managed by the HMC:
updlic -o k -w
updlic updates Licensed Internal Code (LIC) on the managed-system or on all High Performance Switches managed by this Hardware Management Console (HMC).
Use the a operation to retrieve, install, and activate LIC updates. Previously activated updates will be automatically accepted.
Use the i operation to retrieve and install, but not activate, LIC updates.
Use the r operation to remove the most recently installed LIC updates and activate the previously accepted level. This operation is only valid when the LIC type is both Managed System and Power.
Use the h operation to change LIC update control to the Hardware Management Console (HMC). This option is only valid for a managed system.
Use the o operation to change LIC update control to Operating System. This option is only valid for a managed system.
Use the d operation to disruptively activate LIC updates.
Use the c operation to accept currently activated LIC updates (copy T to P).
Use the j operation to reject installed LIC updates (copy P to T).
Use the u operation to upgrade Licensed Internal Code to a new release.
Use the k operation to check system readiness for LIC operations.
This option is required for a and i operations, and is optional for the r operation. This option is not valid otherwise.
This option is required for a and i operations. This option is not valid otherwise.
Specify latest to retrieve the latest LIC updates, even if disruptive.
Specify latestconcurrent to retrieve the latest concurrent LIC updates.
Specify sss to retrieve a specific level of Managed System or Power LIC updates, even if disruptive. sss is the three character identifier of the specific level to retrieve. This is only valid when the LIC type is either Managed System only or Power only.
Specify ccc,ppp to retrieve a specific level of Managed System and Power LIC updates, even if disruptive. ccc is the three character identifier of the specific level of Managed System LIC updates to retrieve. ppp is the three character identifier of the specific level of Power LIC updates to retrieve. This is only valid when the LIC type is both Managed System and Power.
This option is required for a, i, and u operations. This option is not valid otherwise.
This option is required when retrieving LIC updates from a remote FTP site. This option is not valid otherwise.
This option is required when retrieving LIC updates from a remote FTP site. This option is not valid otherwise.
This option is only valid when retrieving LIC updates from a remote FTP site.
This option is only valid when retrieving LIC updates from a mountpoint or a remote FTP site.
This option allows you to determine if the specified update is disruptive. If so, you can shut down operating systems or configure I/O devices offline prior to performing the specified update.
When this option is used with -m, one of the following return codes will be returned:
Any other return code value indicates that an error occurred.
When this option is used with -w, one of the following return codes will be returned:
Any other return code value indicates that an error occurred.
When this option is not used, a return code value of zero indicates success. Any other value indicates that an error occurred.
Issue virtual I/O server command.
viosvrcmd -m managed-system {-p partition-name | --id partition-ID} -c "command" [--help]
viosvrcmd issues an I/O server command line interface (ioscli) command to a virtual I/O server partition.
The ioscli commands are passed from the Hardware Management Console (HMC) to the virtual I/O server partition over an RMC session. RMC does not allow interactive execution of ioscli commands.
You must either use this option to specify the name of the partition, or use the --id option to specify the partition's ID. The -p and the --id options are mutually exclusive.
You must either use this option to specify the ID of the partition, or use the -p option to specify the partition's name. The --id and the -p options are mutually exclusive.
command must be enclosed in double quotes. Also, command cannot contain the semicolon (;), greater than (>), or vertical bar (|) characters.
Some repair procedures require connection to the Advanced Systems Management Interface (ASMI).
Connect your server to an ASCII terminal or a graphics terminal to interface with the system management services (SMS) menus. Connect your server to an ASCII terminal to interface with the Advanced System Management Interface (ASMI).
The ASCII terminal is connected to the server through a serial link. The ASCII interface to the ASMI provides a subset of the ASMI functions that are available using the Web interface, and the ASCII interface is available only when the server is in the platform standby state. The ASCII interface to the ASMI is not available during initial program load or run time. See Accessing the ASMI using an ASCII terminal to set up the ASCII terminal for direct or remote access to the ASMI.
This connection also allows you to access the SMS menus. Use the menus to view information about your system and to perform tasks such as changing the boot list and setting the network parameters. See Starting the system management services to get started.
The graphics terminal is available to users who want to use a graphical user interface (GUI) to their AIX® or Linux® servers. To use the graphics terminal, plug the graphics adapter into a PCI slot in the back of the server. You can connect a standard monitor, keyboard, and mouse to the adapter to use the terminal.
This connection allows you to access the SMS menus. For instructions, see Starting the system management services.
Learn how to control the system power using the power button on the control panel and the ASMI.
Use the Advanced System Management Interface (ASMI) to manually and automatically control the system power.
View 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:
Several IPL options that you can set pertain to the server firmware. Firmware is an integral part of the server that is stored in flash memory, whose contents are preserved when the system is powered off. The firmware is code that automatically starts when the server is turned on. Its main purpose is to bring the server to a state where it is ready to operate, which means the server is ready to install or boot an operating system. Firmware also enables the handling of exception conditions in the hardware and provides extensions to the functions of the server hardware platform. You can view the server's current firmware level on the Advanced System Management Interface (ASMI) Welcome pane.
This server has a permanent firmware boot side, or P side, and a temporary firmware boot side, or T side. When updating the firmware, install new levels of firmware on the temporary side first to test the compatibility with your applications. When the new level of firmware has been approved, copy it to the permanent side.
To view and change IPL settings, perform the following steps:
Enable or disable the function that automatically restarts the system.
You can set your system to automatically restart. This function is useful when power has been restored and any backup power supply has recharged after a temporary power failure or after an unexpected power line disturbance that caused the system to shut down. Auto-power restart works only if the system operating mode is set to normal in the Power On/Off System settings. For information about setting the system operating mode, see Powering the system on and off.
When the system restarts, it returns to the state it was in at the time of the power loss. If the system is not managed by a Hardware Management Console (HMC), the system reboots the operating system. If the system is managed by an HMC, all of the partitions that were running before the power loss are reactivated.
To perform this operation, your authority level must be one of the following:
To set the auto-power restart function, do the following:
You can power off your system faster by using the immediate power off option. Typically, this option is used when an emergency power off is needed. The operating system is not notified before the system is powered off.
To perform this operation, your authority level must be one of the following:
To perform an immediate power off, do the following:
You can reboot your system without a complete system shutdown.
To perform this operation, your authority level must be one of the following:
To perform a system reboot, do the following:
Enable or disable the function that powers on a system remotely through a local area network (LAN) connection.
You can power on a system remotely through a local area network (LAN) connection. Wake on LAN® can be enabled for logical partition configurations as well as nonpartitioned environments.
To perform this operation, your authority level must be one of the following:
To enable or disable Wake on LAN, complete the following steps:
Understand how to manage the Advanced System Management Interface (ASMI).
The Advanced System Management Interface (ASMI) is the interface to the service processor that is required to perform general and administrator-level service tasks, such as reading service processor error logs, reading vital product data, setting up the service processor, and controlling the system power. The ASMI might also be referred to as the service processor menus.
Learn about ASMI setup and functionality requirements.
To successfully access and use the ASMI, note the following requirements:
There are several authority levels for accessing the service processor menus using the ASMI. The following levels of access are supported:
There are three authorized service provider login IDs: celogin0, celogin1, and celogin2.
During the initial administrator and general user logins, the only menu option available is Change Password. In order to gain access to additional ASMI menus, you must change the administrator and general user default passwords. If you are an authorized service provider, you cannot change your password. For information about how to change your password, see Changing ASMI passwords.
Learn about ASMI login restrictions, including the maximum number of user logins allowed.
Only three users can log in at the same time. For example, if three people are logged in to the ASMI and a person with a higher authority level than one of the current logged in users attempts to log in, the ASMI forces one of the lowest privileged users to log out. In addition, if you are logged in and not active for 15 minutes, your session expires. You receive no immediate notification when your session expires. However, when you select anything on the current page, you are returned to the ASMI Welcome pane.
To see who is logged in to the ASMI, view Current users on the ASMI Welcome pane after you log in.
If you make five login attempts that are not valid, your user account is locked out for five minutes and none of the other accounts are affected. For example, if the administrator account is locked, the general user can still log in using the correct password. This login restriction applies to the general user, administrator, and authorized service provider IDs.
You can access the ASMI through a Web browser or an ASCII terminal.
Connect a PC or mobile computer to the server to access the ASMI. The Web interface to the ASMI is available during all phases of system operation including the initial program load (IPL) and run time.
The Web interface to the Advanced System Management Interface (ASMI) is accessible through Microsoft Internet Explorer 6.0, Netscape 7.1, or Opera 7.23 running on a PC or mobile computer connected to the service processor. The Web interface is available during all phases of system operation including the initial program load (IPL) and run time. However, some of the menu options in the Web interface are unavailable during IPL or run time to prevent usage or ownership conflicts if the system resources are in use during that phase.
The following instructions apply to systems that are not connected to an HMC. If you are managing the server using an HMC, see the Operations Guide for the Hardware Management Console and Managed Systems, SA76-0085 (https://www.ibm.com/servers/resourcelink/lib03030.nsf/pages/OperationsGuideForHardwareManagementConsole/$file/sa76-0085.pdf).
To set up the Web browser for direct or remote access to the ASMI, complete the following tasks:
If you do not plan to connect your server to your network, this PC or mobile computer will be your ASMI console.
If you plan to connect your server to your network, this PC or mobile computer will be temporarily connected directly to the server for setup purposes only. After setup, you can use any PC or mobile computer on your network that is running Microsoft Internet Explorer 6.0, Netscape 7.1, or Opera 7.23 as your ASMI console.
| Server connector | Subnet mask | IP address |
|---|---|---|
| HMC1 | 255.255.255.0 | 169.254.2.147 |
| HMC2 | 255.255.255.0 | 169.254.3.147 |
For example, if you connected your PC or mobile computer to HMC1, the IP address for your PC or mobile computer could be 169.254.2.146 and the subnet mask would be 255.255.255.0. Set the gateway IP address to the same IP address as the PC or mobile computer.
| User ID | Password |
|---|---|
| general | general |
| admin | admin |
If your PC or mobile computer is connected to HMC2, fill in the section labeled Network interface eth1.
Ensure that the following fields are filled in correctly.
| Field | Value |
|---|---|
| Configure this interface? | Selected |
| Type of IP address | Static |
| IP address | This is a set IP address obtained from the network administrator |
| Subnet mask | This is a set subnet mask obtained from the network administrator |
https://host name.domain namewhere host name and domain name are the host name and domain name you entered when completing step 8c.
To access the ASMI through a Web browser you first need to set the IP address on your PC or mobile computer. The following procedures describe setting the IP address on PC and mobile computers running Microsoft Windows® and Linux.
Setting the IP address in Windows XP and Windows 2000
To set the IP address within Windows XP and Windows 2000, complete these steps.
Setting the IP address in Linux
To set the IP address in Linux, complete these steps. You will need the information from step 4 in Accessing the ASMI using a Web Browser to complete step 4 in the following procedure.
Connect the ASCII terminal to the server to access the ASMI.
The ASCII interface to the ASMI provides a subset of the Web interface functions. The ASCII terminal is available only when the system is in the platform standby state. It is not available during the initial program load (IPL) or run time. The ASMI on an ASCII terminal is not available during the other phases of system operation, including the initial program load (IPL) and run time.
To set up the ASCII terminal for direct or remote access to the ASMI, complete the following tasks:

These attributes are the default settings for the diagnostic programs. Be sure your terminal is set according to these attributes before proceeding to the next step.
| General setup attributes | 3151 /11/31/41 settings | 3151 /51/61 settings | 3161 /64 settings | Description |
|---|---|---|---|---|
| Line speed | 19,200 | 19,200 | 19,200 | Uses the 19,200 (bits per second) line speed to communicate with the system unit. |
| Word length (bits) | 8 | 8 | 8 | Selects eight bits as a data word length (byte). |
| Parity | No | No | No | Does not add a parity bit and is used together with the word length attribute to form the 8–bit data word (byte). |
| Stop bit | 1 | 1 | 1 | Places a bit after a data word (byte). |
| User ID | Password |
|---|---|
| general | general |
| admin | admin |
Learn how to change passwords, view login audits, change the default language, and update the installed languages.
Change the general user, administrator, and HMC access passwords.
You can change the general user, administrator, and HMC access passwords. If you are a general user, you can change only your own password. If you are an administrator, you can change your password and the passwords for general user accounts. If you are an authorized service provider, you can change your password, the passwords for general and administrator user accounts, and the HMC access password.
Passwords can be any combination of up to 64 alphanumeric characters. The default password for the general user ID is general, and the default password for the administrator ID is admin. After your initial login to the ASMI and after the reset toggle jumpers are moved, the general user and administrator passwords must be changed.
The HMC access password is usually set from the HMC during initial login. If you change this password using the ASMI, the change takes effect immediately.
To change a password, follow these steps:
View the login history.
You can view the login history for the ASMI to see the last 20 successful logins and the last 20 logins that failed.
To perform this operation, your authority level must be one of the following:
To retrieve login audits, follow these steps:
Select the language that will be used to display the ASMI Web and TTY menus.
You can select the language that is displayed on the ASMI welcome screen prior to login and during your ASMI session if you do not choose an alternative language at the time of login. You must provide all requested input in English-language characters regardless of the language selected to view the interface.
To perform this operation, your authority level must be one of the following:
To change the default language, follow these steps:
Select additional languages to install on the service processor.
A maximum of five languages can be supported on the service processor at any given time. By default, English is always installed. Languages installation changes take effect when the firmware is updated.
To perform this operation, your authority level must be one of the following:
To update the installed language, do the following:
View vital product data (VPD), persistent storage, system power control network (SPCN) trace data, and progress indicator data.
View selected or all manufacturer's VPD, such as serial numbers and part numbers.
You can view manufacturer's vital product data (VPD) stored from the system boot prior to the one in progress now.
To perform this operation, your authority level must be one of the following:
To view the VPD, complete the following steps:
Learn how to display the contents of the registry.
You can gather additional debug information from a failing system by viewing the contents of the registry. The term registry key can refer to either the key part of a registry entry or the entire registry entry, depending on the context. The registry key hierarchy and the contents of any key can be 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 second part is the name of the key. For example, the TerminalSize key of the esw_menu component is identified as menu/TerminalSize. Each registry key also has a value, which is up to 255 bytes 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:
You can view the files systems that currently display on the control panel.
To perform this operation, your authority level must be authorized service provider.
To view the file systems, perform the following task:
View 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, or server drawer, to gather additional debug information. Producing a trace may take an extended period of time based on your system type and configuration. This delay is due to the amount of time the system requires to query the data.
To perform this operation, your authority level must be one of the following:
To view this trace data, do the following:
Learn how to display the boot progress indicator from the previous system boot.
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 a successful boot, nothing is displayed.
To perform this operation, your authority level must be one of the following:
The progress indicator information is stored in nonvolatile memory. If the system is powered off using the power-on button on the control panel, this information is retained. If the ac power is disconnected from the system, this information is lost.
To view the progress indicator from the previous boot, do the following:
You can view progress codes that appeared in the control panel display during the last boot. The codes display in reverse chronological order.
To perform this operation, your authority level must be one of the following:
To view the progress indicator history, perform the following task:
You can view the progress and error codes that currently display on the control panel. Viewing progress and error codes is useful when diagnosing boot-related issues.
To perform this operation, your authority level must be one of the following:
To view the progress indicator, perform the following task:
View and perform custom system configurations, such as enabling PCI (Peripheral Component Interconnect) error injection policies, viewing system identification information, and changing memory configuration.
You can change the name that is used to identify the system. This name helps your support team (for example, your system administrator, network administrator, or authorized service provider) to more quickly identify the location, configuration, and history of your server.
To perform this operation, your authority level must be one of the following:
The system name is initialized to the 31-character value Server-tttt-mmm-SNooooooo, where the substitution characters mean the following:
| Characters | Description |
|---|---|
| tttt | Machine type |
| mmm | Model number |
| ooooooo | Serial number |
The system name can be changed to any valid ASCII string. It does not have to follow the initialized format.
To change the system name, do the following:
The new system name is displayed in the status frame, the area where the logout button is located. If another method, such as the HMC, is used to change the system name, the status frame does not reflect the change.
View and change various enclosure attributes.
After the server firmware has reached the standby state, you can configure I/O enclosure attributes as follows:
To perform this operation, your authority level must be one of the following:
To configure I/O enclosures, do the following:
Display and change the time and date stored by the system.
You can display and change the system's current date and time. The date and time can only be changed when the system is powered off. The time is stored as UTC (Coordinated Universal Time), formerly expressed as Greenwich mean time (GMT).
To perform this operation, your authority level must be one of the following:
To change the time of day, do the following:
Configure your system to only allow firmware updates from the selected source.
You can change the source for firmware updates. For example, if you choose the Hardware Management Console (HMC) as the source for a firmware update, the HMC must be used to perform the update. The HMC performs all tasks to update the server firmware.
Firmware updates can be initiated from the HMC) or from the operating system on your IBM System i5™ and eServer™ i5 server.
If your server has an HMC attached, the firmware update can only be performed from the HMC. The firmware update must be initiated from the HMC concurrently (while the system is running), but the update will not be applied until the server is rebooted. .
For information about performing a firmware update, see Managed System Updates.
On an i5 server, a firmware update can be initiated from either the HMC or the operating system. Firmware updates for IBM System i5 and eServer i5 servers are delivered by the program temporary fix (PTF) process. For more information, see Getting fixes in the Service and support topic.
To perform this operation, your authority level must be one of the following:
To change the firmware update policy, perform the following task:
Change the PCI error injection policy that forces errors to be injected to PCI cards.
You can enable or disable the injection of errors on the PCI bus. For example, independent software vendors who develop device drivers can inject errors to test the error handling code in the device driver.
To perform this operation, your authority level must be one of the following:
To enable or disable the PCI error injection policy, do the following:
Configure the server firmware and HMC monitoring.
To configure monitoring, your authority level must be an authorized service provider.
Monitoring is accomplished by periodic samplings called heartbeats, which can detect an HMC or server firmware connection failure.
To configure monitoring, do the following:
Display and remove disconnected HMC data.
By default, HMC connection data expires on the managed system after 14 days of disconnection from the HMC. If you want to perform a task that requires all HMCs to be disconnected from the managed system, you can remove the HMC 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:
View and change the multiple chip module (MCM) interposer plug count.
You can track the number of times that a multiple chip module (MCM) has been replaced or reseated on a given interposer. This interposer plug count provides you with information needed to prevent field problems due to damaged or overused interposers. You can use the ASMI to view and alter the interposer plug count for all MCMs in the system. Whenever a service action is performed on a system that requires the replacement or reseating of an MCM, service personnel are responsible for updating the plug count for that interposer.
To perform this operation, your authority level must be authorized service provider.
To view and modify the interposer plug count, do the following:
View and change the maximum number of Highspeed Link (HSL) Opticonnect Connections allowed for your system.
To perform this operation, your authority level must be one of the following:
To change the number of HSL Opticonnect Connections, do the following:
Increase 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 Adapter Enlarged Capacity option is enabled, specific PCI slots receive the largest memory-mapped address spaces that are available.
To perform this operation, your authority level must be one of the following:
To enable or disable I/O adapter memory allocation, do the following:
Set deconfiguration policies, change processor configuration, change memory configuration, view deconfigured resources, and clear all deconfiguration errors.
Set various processor and memory configuration and deconfiguration policies.
You can set various policies to deconfigure processors and memory in certain situations. You can enable policies 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, functional failure, or system bus failure. You can also enable the firmware to power off a processing unit (node) for concurrent maintenance when any of the resources in that node are deconfigured.
To set the deconfiguration policies, your authority level must be one of the following (any user can view the deconfiguration policies):
To set deconfiguration policies, complete the following steps:
Learn how to display data and change the state for each processor.
All processor failures that stop the system, even if intermittent, are reported to the authorized service provider as a diagnostic call out for service repair. To prevent the recurrence of intermittent problems and improve 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:
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 processor remains offline for subsequent reboots until it is replaced or the deconfiguration policy is disabled. The deconfiguration policy also provides the user with the option of manually deconfiguring a processor or re-enabling a previously manually deconfigured processor. This state is displayed as deconfigured by user.
To perform this operation, your authority level must be one of the following:
To view or change the processor configuration, do the following:
Display data for each memory unit and bank. You can change the state of each bank.
Each memory bank 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 memory bank. If memory DIMMs are being monitored for errors, each memory bank will be in one of the following states:
With ASMI, you can change the state of the memory bank from cs to md, from mc to md, and from md to mc for one or more DIMMs. If one DIMM is deconfigured, the other DIMM in the memory bank automatically becomes deconfigured.
The error type is the cause of memory deconfiguration and applies to the bank in the ds state. The error type is displayed only when the bank is in the ds state.
To perform this operation, your authority level must be one of the following:
To view or change the memory configuration, do the following:
View the resources deconfigured by the system.
To view the deconfigured resources, your authority level must be authorized service provider.
Clear 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.
To clear all deconfiguration errors, do the following:
Specify settings to control your virtual Ethernet environment.
You can configure system firmware settings that enable you to restrict virtual input/output (I/O) connectivity between partitions, control the number of virtual Ethernet switches allocated by the firmware, and control when to run the floating point unit computation test.
Use the ASMI to set the policy for virtual input/output connectivity.
Specifying this configuration setting enables you to control virtual input/output activity between partitions. The policy is set to enabled by default, which allows all virtual input/output connectivity between partitions. If this setting is disabled, only virtual TTY sessions to the Hardware Management Console (HMC) are allowed.
To set the policy for virtual I/O connections, complete the following steps:
Control the number of virtual Ethernet switches allocated by the system server firmware.
You can set a configuration value that enables you to specify the number of virtual Ethernet switches that can be allocated by the system server firmware. This value is set to 0 by default. A value of 0 enables the Hardware Management Console (HMC) to control the number of virtual Ethernet switches allocated by the system server firmware. You can change this value to specify up to 16 allowable virtual switches.
The default value is generally used for most configurations. However, in a more complex environment where you might want the system server firmware to create a larger number of virtual Ethernet switches during platform power on, you can set this number higher and override the HMC's control.
After setting this value, when a virtual Ethernet adapter is created using the HMC, the adapter will be connected to a particular virtual switch depending on the virtual slot number chosen during creation. The adapter's virtual slot number will be divided by the number of virtual Ethernet switches, and the remainder of this division operation will be used to determine with which switch the adapter will be associated. Each virtual Ethernet adapter will be able to communicate only with other virtual Ethernet adapters on the same virtual switch.
To configure the value for virtual Ethernet switches, complete the following steps:
For example, if you set the number of virtual Ethernet switches to 3, virtual Ethernet adapters in virtual slot 3, 6, and 9 are assigned to the same switch. A virtual Ethernet adapter in virtual slot 4 would be assigned to another switch, and would not be able to communicate with the adapters in slots 3, 6, and 9.
Learn how to accept the firmware license agreement.
To perform this operation, your authority level must be authorized service provider.
To accept the firmware license agreement, perform the following task:
Control the policy of when to run the floating point unit computation test.
Specifying this configuration setting allows you to control when you want to run this test. You can set it to run immediately or to run at various times.
To perform this operation, your authority level must be one of the following:
To specify when to run this test, complete the following steps:
The ASMI allows you to program the system vital product data (VPD) such as system brand, system identifiers, and system enclosure type. To access any of the VPD-related panels, your authority level must be administrator or authorized service provider.
Set and view the system brand.
The system brand identifies your system using a 2-character system brand as shown in the following table.
| System brand | Description |
|---|---|
| D0 | IBM Storage |
| I0 | IBM eServer i5 |
| P0 | IBM System p™ |
Changing the system brand is only allowed if the value has not been set, or if the current value is P0 and the new value will be D0. Additionally, for IBM Storage, each of the systems that constitutes the storage facility must be set to D0 for storage to be accessible online.
To perform this operation, your authority level must be one of the following:
To change the system brand, complete the following steps:
Attention: Once set, this value cannot be changed unless it is 'P0', and then only to 'D0'.
Set 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 know the system-unique ID, contact your next level of support.
To perform this operation, your authority level must be one of the following:
To set the system keywords, do the following:
Set values that uniquely identify the type of enclosures attached to the system.
When setting the system enclosure type, ensure that the enclosure serial number field matches the original value, which can be found on a label affixed to the unit. Updating the enclosure serial field keeps the configuration and error information synchronized, and this information is used by the system when creating the location codes. This task must be done using the ASMI, not with the control panel. However, if you do not have access to the ASMI, the system will still operate without updating this information.
For example, when replacing the I/O backplane, you must re-enter the original enclosure serial number into the enclosure serial number field to overwrite the serial number that is recorded for the new I/O backplane. Failure to enter the correct enclosure serial number will result in logical partition mappings being incorrect.
To perform this operation, your authority level must be one of the following:
To change the system enclosure type, complete the following steps:
The value of the Enclosure serial number field is different than the serial number of the system. Set the Reserved field to blank spaces unless directed otherwise by service and support.
Turn off system attention indicator, enable enclosure indicators, change indicators by 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 method for 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 indicator is in an identify state, then the corresponding enclosure indicator will change to an identify state automatically. You cannot turn off the enclosure indicator until all FRU indicators within that enclosure are in an off state.
Learn how to turn off the system attention indicator.
The system attention indicator provides a visual signal that the system as a whole requires attention or service. Each system has a single system attention indicator. When an event occurs that either needs your intervention or that of service and support, the system attention indicator lights continuously. The system attention indicator is turned on when an entry is made in the service processor error log. The error entry is transmitted to the system level and operating system error logs.
To perform this operation, your authority level must be one of the following:
To turn off the system attention indicator, do the following:
Find 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. For example, a processing unit enclosure represents all of the indicators within the processing unit and an I/O enclosure represents all of the indicators within that I/O enclosure. Enclosures are listed by their location code.
To perform this operation, your authority level must be one of the following:
To enable the enclosure indicator states, do the following:
To turn off all of the indicators for this enclosure, click Turn off all. A report page is displayed indicating success or failure.
You can specify the location code of any indicator to view or modify its current state. If you provide the wrong location code, the advanced system manager attempts to go to the next higher level of the location code.
The next level is the base-level location code for that field replaceable unit (FRU). For example, a user types the location code for the FRU located on the second I/O slot of the third enclosure in the system. If the location code for the second I/O slot is incorrect (the FRU does not exist at this location), an attempt to set the indicator for the third enclosure is initiated. This process continues until a FRU is located or no other level is available.
To perform this operation, your authority level must be one of the following:
To change the current state of an indicator, do the following:
You can perform an LED test on the control panel to determine if one of the LEDs is not functioning properly.
To perform this operation, your authority level must be one of the following:
To perform an LED test on the control panel, perform the following task:
You might enhance the performance of your managed system by changing the logical memory block size and increasing the system memory page size.
You might enhance the managed system performance by manually or automatically changing the logical memory block size.
The system kernel uses the memory block size to read and write files. By default, the logical memory block size is set to Automatic. This setting allows the system to set the logical block memory size based on the physical memory available. You can also manually change the logical memory block size.
To select a reasonable logical block size for your system, consider both the performance desired and the physical memory size. Use the following guidelines when selecting logical block sizes:
To perform this operation, your authority level must be one of the following:
To configure logical memory block size, perform the following task:
Improve your system performance by setting up the system with larger memory pages.
You can improve your system performance by setting up the system with larger memory pages. Performance improvements vary depending on the applications running on your system. Only change this setting if advised by service and support.
To perform this operation, your authority level must be one of the following:
To set up your system with larger memory pages, do the following:
Use ASMI to configure network interfaces, configure network access, and debug the virtual TTY.
Configure 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 to the specific needs of your system.
You can change the network configurations when the system is in any state.
To perform this operation, your authority level must be one of the following:
To configure network interfaces, do the following:
Specify which IP addresses will be allowed to access the server.
When you configure network access, you specify which IP addresses can access the service processor. You can specify a list of allowed IP addresses and a list of denied IP addresses.
To perform this operation, your authority level must be one of the following:
To configure network access, do the following:
If a login is received from an IP address that matches a complete or partial IP address in the allowed list, access to the service processor is granted. Access to the service processor is not allowed if a login is received from an IP address that matches a complete or partial IP address from the denied list.
Debug the virtual TTY from the master service processor.
You can gather additional debug information from a failing system by using the debug virtual server (DVS). The DVS enables communication with the server firmware and partition firmware. DVS allows a maximum of eight open connections. External interfaces such as the ASMI and service processor remote application can communicate with the server firmware and partition firmware through DVS. This communication is bidirectional. External interfaces can send a message to the server firmware and partition firmware through DVS.
DVS uses the partition ID and session ID to distinguish between the server firmware and partition firmware. The range for both 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 this communication.
The partition ID and the session ID parameters must be specified to start communicating. After specifying both parameters, a telnet session must be opened to send messages. The telnet session must be started and messages must be sent within the time-out period of 15 minutes. If both actions are not taken within the time-out period, the connection is closed.
To perform this operation, your authority level must be authorized service provider.
To debug the virtual TTY, do the following:
Troubleshoot common problems associated with setting up access to the ASMI, and learn how to view and customize troubleshooting information using various service aids.
Troubleshoot common problems associated with setting up access to the ASMI.
The following table contains information about common problems that might occur while you are trying to access the Advanced System Management Interface (ASMI) through a Web browser. The table also provides common resolutions to those problems.
| Problem | Resolution |
|---|---|
| After you enter the server's IP address in the Web browser, you receive a security alert. | Usually this means that your PC or mobile computer does
not accept the server as a secure site. To resolve this problem, complete
the following steps:
|
| After you enter the server's IP address in the Web browser, the browser displays an error message stating that it cannot find the IP address that you entered. |
|
| You are using Microsoft Internet Explorer 6.0 running on Windows XP, you have correctly cabled the PC or mobile computer to the server, and you cannot access the ASMI. | Usually this means that the Use TLS 1.0 option in Microsoft Internet
Explorer is enabled. To connect to the ASMI, this option must be disabled.
To resolve this problem, complete the following steps:
|
| You are locked out of the ASMI after you enter the default user ID and password either incorrectly or more than five times. | Reset the default password and network settings to the
default settings using one of the following methods:
|
View and customize troubleshooting information with various service aids (such as viewing error logs and initiating service processor dumps).
Display 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 can be useful in solving hardware or server firmware problems.
To perform this operation, your authority level must be one of the following:
Informational, error, and miscellaneous logs can be viewed by all authority levels. Hidden error logs can be viewed by authorized service providers.
The following table shows error log types that might be displayed, the conditions that make an error log specific to that error log type, and the user authority level that will allow you to view specific types of error logs:
| Error log type | Conditions | User availability | |
|---|---|---|---|
| Severity | Action | ||
| Informational logs | Informational | Report to operating system (OS) but not hidden | Available to all users |
| Error logs | Not informational | Report to OS but not hidden | Available to all users |
| Hidden logs | Not informational and informational | Report to OS, hidden, or both | Available only to the authorized service provider and users with higher authority. |
| Miscellaneous | Informational | Not reported to OS | Available to all users |
To view error and event logs in summary or full detailed format, do the following:
Specify 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 the selected port is examined, or snooped, as it arrives. You can also specify the snoop string, a particular sequence of bytes that resets the service processor if detected. The system port S1 serves as a "catchall" reset device.
To perform this operation, your authority level must be one of the following:
To view and change the current Serial Port Snoop settings, complete the following steps:
Control how frequently a system dump is performed and the amount of data collected from the hardware 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 can be used to resolve a hardware or server firmware problem. A system dump can also be automatically initiated after a system malfunction, such as a checkstop or hang. It is typically 34 MB.
To perform this operation, your authority level must be one of the following:
To configure and initiate a system dump, do the following:
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 policy to determine if a system dump will be initiated.
The dump policy options are the following:
The system firmware makes a recommendation for the dump content based on the type of error that has occurred. This recommendation is combined with the hardware content to determine how much dump data is actually collected.
The dump policy options available are the following:
To save the setting changes and instruct the system to immediately process a dump with the current settings, click Save settings and initiate dump.
For information about copying, reporting, and deleting the dump using the HMC, see Manage Dumps.
Enable or disable the service processor dump in addition to immediately initiating a service processor dump.
Use this procedure only under the direction of your hardware service provider. With this function, you can preserve error data after a service processor application failure, external reset, or user request for a service processor dump. The existing service processor dump is considered valid if neither the server firmware nor Hardware Management Console (HMC) has collected the previous failure data.
To perform this operation, your authority level must be authorized service provider.
To enable or disable the service processor dump and view the status of the existing service processor dump, do the following:
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 dumps on the HMC, see Manage Dumps.
Enable or disable the partition dump in addition to immediately initiating a partition dump.
Use this procedure only under the direction of your hardware service provider. By initiating a partition dump, you can preserve error data that can be used to diagnose server firmware or operating system problems. The state of the operating system is saved on the hard disk and the partition restarts. This function can be used when the operating system is in an abnormal wait state or endless loop.
To perform this operation, your authority level must be one of the following:
To perform a partition dump, do the following:
Configure a system port for use with the call-home and call-in options.
You can configure a system port used with the call-home and call-in features. You can also set the baud rate for a system port.
To perform this operation, your authority level must be one of the following:
To configure a system port, complete the following steps:
Configure your modem that is connected to the system port.
To perform this operation, your authority level must be one of the following:
To configure the modem, complete the following steps:
Configure your system to call home and call in.
You can select which system port is used to call home and to call in, set various telephone numbers, and add customer information.
To perform this operation, your authority level must be one of the following:
To configure the call-in and call-home policies, complete the following steps:
You can test the call-home policy configuration after the modem is installed and configured correctly.
To perform this operation, your authority level must be one of the following:
To test your call-home policy configuration, do the following:
Reboot the service processor.
In critical system situations, such as during system hangs, you can reboot the service processor. Perform this task only when directed by your service provider.
To perform this operation, your authority level must be one of the following:
To reboot your service processor, do the following:
Restore firmware settings, network configuration, and passwords to their factory defaults.
You can reset all the factory settings on your server to the factory default settings, or you can choose to reset specific settings by using the following options:
If you choose to reset all settings, all three of these actions are performed resulting in the service processor settings, the server firmware settings, and the PCI bus configuration being reset in one operation.
Resetting the service processor settings results in the loss of all system settings (such as the HMC access and ASMI passwords, time of day, network configuration, and hardware deconfiguration policies) that you may have set through user interfaces.
Resetting the PCI bus configuration results in the following sequence of events:
To restore factory default settings, your authority level must be one of the following:
To restore factory default settings, do the following:
Enter commands to perform on the service processor.
You can enter commands to perform on the service processor. Currently, no syntactical validation is performed on the command string that is entered. As a result, ensure that the command is entered correctly before initiating the action.
To perform this operation, your authority level must be an authorized service provider.
To enter service processor commands, do the following:
The control panel functions allow you to interface with the server. Control panel functions range in complexity from functions that display status (such as IPL speed) to low-level service functions that only service representatives must access.
The physical control panel is your initial interface with the server. You can use the physical control panel to perform functions such as IPL, power on, and power off.

The system attention light is located along the upper right edge of the first drawer.
Activating a control panel function with the physical control panel is a two-step procedure.
To activate a control panel function, do the following:
You must first put the physical control panel in manual operating mode before you can select or activate certain functions.
To put the physical control panel in manual operating mode, do the following:
0 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0 2 _ _ B _ _ N < _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _
0 2 _ _ B _ _ M < _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _
The control panel is in manual operating mode. For information about other options in function 02, see Function 02: Select IPL type, IPL speed override, system operating mode, and firmware mode.
Learn about function codes that are displayed on the control panel to indicate status and function options.
To display all functions, put the control panel in manual operating mode. See Putting the physical control panel in manual operating mode.
The following table includes descriptions of the primary and customer-extended control panel function codes.
| Function code | Function selected |
|---|---|
| 01 |
Displays the current IPL parameters. This function is available in both normal and manual operating mode. |
| 02 | Used to select the IPL type, system operating mode, IPL speed, and firmware IPL mode. This function is available in both normal and manual operating mode. |
| 03 | Restarts an IPL of the system using the selected IPL parameters. This function is available only in manual operating mode and when the system power is on. |
| 04 | Performs a lamp test; all displays and indicators are lit. This function is available in both normal and manual operating mode. |
| 05 and 06 | Reserved. |
| 07 | Allows you to perform SPCN service functions. This function is available only in the manual operating mode and from power on standby. |
| 08 | Causes a fast power off. This function is available only when the system is in manual operating mode and the system power is on. |
| 09 and 10 | Reserved. |
| 11 | Displays a system reference code (SRC) on the control panel using up to 32 ASCII characters, including non-hexadecimal characters. This function is available in both normal and manual operating mode when an SRC is available. |
| 12 | Displays an SRC on the control panel using up to four extended SRC data words. This function is available in both normal and manual operating mode when an SRC is available. |
| 13 | Displays an SRC on the control panel using up to eight extended SRC data words. This function is available in both normal and manual operating mode when an SRC is available. |
| 14 through 19 | Displays an SRC on the control panel using callout data. These functions are available in both normal and manual operating mode when an SRC is available. |
| 20 | Displays the machine type and model, VPD card CCIN, and IPL types. This function is available in both normal and manual operating mode. |
| 21 | Causes the Use Dedicated Service Tool (DST) display to appear on the system console. To exit the DST, select the Resume operating system display option. This function is available only in the manual operating mode and when activated by the operating system.Not applicable. |
| 22 | Forces a partition dump. This function is available only in the manual operating mode and when activated by the operating system. |
| 23 and 24 | Reserved. |
| 25 and 26 | Use service switches 1 and 2 to enable or disable functions 50 through 99. These functions are available only in the manual operating mode. |
| 27 through 29 | Reserved. |
| 30 | Displays the service processor IP address and port location. This function is available only in the manual operating mode and from power on standby. |
| 31 through 33 | Reserved. |
| 34 | Retries the partition dump. This function is available only in the manual operating mode and when activated by the operating system.Not applicable. |
| 35 through 41 | Reserved. |
| 42 | Performs a platform dump. This function is available only in the manual operating mode and when activated by the operating system or the service processor. |
| 43 | Performs a service processor dump. This function is available only in the manual operating mode. |
| 44 through 54 | Reserved. |
| 55 | Displays or changes the platform dump collection policy, platform dump hardware content, and platform dump firmware content settings. This function is available only in the manual operating mode. |
| 56 through 62 | Reserved. |
| 63 | Displays up to the last 25 system status SRCs. This function is available only in the manual operation mode. |
| 64 | Displays up to the last 25 diagnostic status SRCs. This function is available only in the manual operation mode. |
| 65 through 70 | Not applicable. |
| 71 through 99 | Reserved. |
If you cannot find the function code in this chart, added features or devices might not have been available when this information was produced. Look on the control panel for supplemental unit function code information for the function code that you displayed.
Learn about the primary control panel functions that are available.
This function allows you to display the current system operating mode, the IPL speed for the next IPL, the firmware mode for the next IPL, and the operating system IPL mode (when enabled).
This function is available in both normal and manual operating mode.
This function displays the following information:
| Function/Data | Action or description |
|---|---|
0 1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 01. |
0 1 _ _ A _ _ M _ _ V = F _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _ |
Valid OS IPL types are A, B, C, and D. Valid system operating modes are M and N. Valid IPL speed displays are F, V=F, S, V=S, H, V=H, X, and V=X. Valid firmware IPL modes are P and T. |
0 1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll through the control panel functions. |
This function allows you to select the IPL type and logical key mode when the system is either powered on or off.
This function is available in both normal and manual operating mode.
Before you can select the IPL speed, the system must be at power on standby.
For powered-on systems, function 02 is used to select the operating system (OS) IPL type, system operation mode, or firmware IPL mode. The following table shows an example of the function 02 IPL type, system operating mode, and firmware IPL mode selection sequence for a powered-on system.
| Function/Data | Action or description |
|---|---|
0 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 02. |
0 2 _ _ A < _ M _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _ |
Press Enter to start function 02.
|
0 2 _ _ B < _ M _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _ |
Use the Increment or Decrement buttons to scroll through the OS IPL types. |
0 2 _ _ B _ _ M < _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _ |
Press Enter to select the OS IPL type.
|
0 2 _ _ B _ _ N < _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P _ _ _ |
Use the Increment or Decrement buttons to scroll through the system operating modes. |
0 2 _ _ B _ _ N _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P < _ _ |
Press Enter to select the system operating mode.
|
0 2 _ _ B _ _ N _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ T < _ _ |
Use the Increment or Decrement buttons to scroll through the firmware IPL modes. |
0 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to select the firmware IPL mode and exit function 02. |
0 1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll through the control panel functions. |
For powered-off systems, function 02 is used to select the OS IPL type, system operating mode, system IPL speed, and firmware IPL mode. The following table shows an example of the function 02 OS IPL type, system operating mode, system IPL speed, and firmware IPL mode selection sequence for a powered-off system.
| Function/Data | Action or description |
|---|---|
0 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 02. |
0 2 _ _ A < _ M _ _ _ _ V _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ T _ _ _ |
Press Enter to start function 02.
|
0 2 _ _ B < _ M _ _ _ _ V _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ T _ _ _ |
Use the Increment or Decrement buttons to scroll through the OS IPL types. |
0 2 _ _ B _ _ M < _ _ _ V _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ T _ _ _ |
Press Enter to select the IPL type.
|
0 2 _ _ B _ _ N < _ _ _ V _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ T _ _ _ |
Use the Increment or Decrement buttons to scroll through the system operating modes. |
0 2 _ _ B _ _ N _ _ _ _ V < _ _ _ _ _ _ _ _ _ _ _ _ _ _ T _ _ _ |
Press Enter to select the system operating mode.
|
0 2 _ _ B _ _ N _ _ _ _ S < _ _ _ _ _ _ _ _ _ _ _ _ _ _ T _ _ _ |
Use the Increment or Decrement buttons to scroll through the IPL speeds. |
0 2 _ _ B _ _ N _ _ _ _ S _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ T < _ _ |
Press Enter to select the IPL speed.
|
0 2 _ _ B _ _ N _ _ _ _ S _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ P < _ _ |
Use the Increment or Decrement buttons to scroll through the firmware IPL modes. |
0 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to select the firmware IPL mode and exit function 02. |
0 1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll through the control panel functions. |
This function restarts an IPL of the system using the selected IPL parameters.
This function is available only in manual operating mode and when the system power is on.
When you select function 03 and press Enter, a restart IPL debounce is performed. The restart IPL debounce SRC (A1008003) is displayed.
Notifications are not required prior to restarting the IPL.
This function shows whether any control panel indicators are burned out and whether characters that are displayed in the Function/Data display on the control panel are valid.
This function is available in both normal and manual operating mode.
When you activate the lamp test, all of the control panel lights and indicators are lit. The lamp test continues on the system control panel for four minutes.
Use the following procedure to verify that the lights on the system control panel are working correctly. If you cannot complete these steps, see the Problem Analysis, SA76-0111, guide.
Press Enter on the control panel.
| Yes | No |
|---|---|
| ↓ | Exchange the control panel or the replaceable unit that contains the control panel function [system unit backplane (MB1) or tower card (CB1)]. See Customer-Installable Features for the IBM System p 570 (9117-MMA), SA76-0104. |
| Yes | No |
|---|---|
| ↓ | Exchange the control panel on the expansion unit. See Customer-Installable Features for the IBM System p 570 (9117-MMA), SA76-0104. |
The lights on the system control panel are working correctly.
This function is reserved.
This function allows you to perform a System Power Control Network (SPCN) operation.
This function is available only in the manual operating mode and from power on standby.
To perform an SPCN operation that is controlled by function 07, do the following:
| Function | Description | For more information |
|---|---|---|
| A1 | Broadcasts a power-on command. | Go to step 5. |
| A6 | Displays frame address on all I/O enclosures. | Go to step 5. |
| A8 | Displays the SPCN configuration ID number for a selected frame. | 07A8 is displayed. Go to step 3. |
| A9 | Sets the SPCN configuration ID for a selected frame. | 07A9 is displayed. Go to step 4. |
.
Then return to step 1.This function allows you to power off the system when it is suspended.
This function is available only when the system is in manual operating mode and the system power is on.
The first time that you select function 08 and press Enter, a fast power off (FPO) debounce is performed and the system displays SRC A1008008. The second time that you select function 08 and press Enter, an FPO is performed and the system returns to its default display.
These functions are reserved.
This function displays a system reference code (SRC) on the control panel using up to 32 ASCII characters, including non-hexadecimal characters, and can be displayed in all display positions. This function serves as a diagnostic aid that helps you determine the source of a hardware or operating system problem.
This function is the default SRC display and is available in both normal and manual operating mode when an SRC is available.
Function 11, if enabled, represents the words of the SRC.
Record SRC information for error reporting. For more information, see Collecting reference codes and system information.
For
more information about interpreting SRCs, go to the appropriate System Reference
Codes guide on the Resource Link Web site at http://www.ibm.com/servers/resourcelink
.
To use an SRC for problem analysis, see the Problem Analysis, SA76-0111, guide.
This function displays a system reference code (SRC) on the control panel using up to four extended SRC data words to serve as a diagnostic aid that helps you determine the source of a hardware or operating system problem.
This function is available in both normal and manual operating mode when an SRC is available.
The extended SRC data words are displayed depending on the number in the SRC. Extended SRC data words are displayed four words at a time. If any extended SRC data words exist, function 12 is scrollable. Unused words are presented as blanks in the required display.
Record SRC information for error reporting. For more information, see Collecting reference codes and system information.
For
more information about interpreting SRCs, go to the appropriate System Reference
Codes guide on the Resource Link Web site at http://www.ibm.com/servers/resourcelink
.
To use an SRC for problem analysis, see the Problem Analysis, SA76-0111, guide.
This function displays a system reference code (SRC) on the control panel using up to four more extended SRC data words to serve as a diagnostic aid that helps you determine the source of a hardware or operating system problem.
This function is available in both normal and manual operating mode when an SRC is available.
The extended SRC data words are displayed depending on the number in the SRC. Extended SRC data words are displayed four words at a time. If there are only one to four extended SRC data words, function 13 is not scrollable. If there are five to eight extended SRC data words, function 13 is scrollable. Unused words are presented as blanks in the required display.
Record SRC information for error reporting. For more information, see Collecting reference codes and system information.
For
more information about interpreting SRCs, go to the appropriate System Reference
Codes guide on the Resource Link Web site at http://www.ibm.com/servers/resourcelink
.
To use an SRC for problem analysis, see the Problem Analysis, SA76-0111, guide.
These functions display a system reference code (SRC) on the control panel using callout data to serve as a diagnostic aid to help you determine the source of a hardware or operating system problem.
These functions are available in both normal and manual operating mode when an SRC is available.
Functions 14 though 19, if enabled, display field replaceable unit (FRU) and procedure callout data. This data is displayed following any present extended SRC data words. Multiple FRU and procedure callout data entries can be included with each SRC. One FRU or procedure callout data entry is displayed for each function number. Up to six different FRU or procedure callout data entries can be presented at the control panel using functions 14 through 19.
The following table shows an example of a function 14 FRU callout display selection sequence.
| Function/Data | Action or description |
|---|---|
1 4 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 14. |
H_ -PARTNUM_ CCIN_ _ U970305010ABCDE-_ _ _ |
Press Enter to select function 14. The FRU callout data is displayed. |
1 4 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Pressing Enter toggles between function and data display. |
The following table shows an example of a function 15 procedure callout display selection sequence.
| Function/Data | Action or description |
|---|---|
1 5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 15. |
M_ -FSPSP04_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to select function 15. The procedure callout data is displayed. |
1 5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Pressing Enter toggles between function and data display. |
Record SRC information for error reporting. For more information, see Collecting reference codes and system information.
For more information
about interpreting SRCs, go to the appropriate System Reference Codes guide on the Resource Link Web site at http://www.ibm.com/servers/resourcelink
.
To use an SRC for problem analysis, see the Problem Analysis, SA76-0111, guide.
This function displays the machine type and model, VPD card CCIN, and IPL types.
This function is available in both normal and manual operating mode.
The machine type, model, VPD card CCIN, and IPL type are displayed in the following format:
|
p p p p - m m m _ _ _ _ c c c c T T T T T T T T t t t t t t t t |
The values are indicated as follows:
Record this information with the system reference code (SRC).
If you select this function and it has not been activated, the command is rejected.
Learn about the customer-extended panel functions that are available.
This function makes Dedicated Service Tools (DST) available on the system console display.Not applicable.
This function is available only in the manual operating mode and when activated by the operating system.
The Use Dedicated Service Tools (DST) display is available on the primary or alternative console.
To exit the DST and return to the operating system, select the Resume operating system display option on the Use Dedicated Service Tools (DST) display.
For more information, see Overview of service and support.
This function initiates a dump of a partition's operating system data.
This function is available only in the manual operating mode and when activated by the operating system.
You must perform two consecutive function 22 selections to initiate a partition dump. The following table shows an example of function 22.
| Function/Data | Action or description |
|---|---|
2 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 22. |
2 2 _ _ _ _ 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to start function 22. |
A 1 0 0 3 0 2 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Displays the partition dump verification system reference code (SRC). |
2 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 22. |
2 2 _ _ _ _ 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to start function 22. |
These functions are reserved.
These functions are used to set the service function range (50 to 99).
These functions are available only in the manual operating mode.
To set the service function range (50 to 99), use function 25 to set the service representative switch 1, and then use function 26 to set the service representative switch 2.
These functions are reserved.
This function displays the service processor IP address and port location.
This function is available only in the manual operating mode and from power on standby.
The following table shows an example of function 30.
| Function/Data | Action or description |
|---|---|
3 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 30. |
3 0 * * _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to enter sub-function mode. |
3 0 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to select an IP address
|
S P _ A : _ E T H O : _ _ _ T 5 9 . 5 . 1 0 5 . 2 4 3 _ _ _ _ _ |
Press Enter to display the selected IP address. |
3 0 * * _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to select sub-function exit. |
3 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to exit sub-function mode. |
These functions are reserved.
Not applicable.
These functions are reserved.
This function initiates a platform dump.
This function is available only in the manual operating mode and when activated by the operating system or the service processor.
You can use function 42 to dump IBM POWER™ hypervisor main storage and hardware data. You must perform two consecutive function 42 selections to initiate a platform dump. The following table shows an example of function 42:
| Function/Data | Action or description |
|---|---|
4 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 42. |
4 2 _ _ _ _ 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to start function 42. |
A 1 0 0 3 0 4 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Displays the confirmation SRC. |
4 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 42. |
4 2 _ _ _ _ 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to start function 42. |
This function initiates a service processor dump.
This function is available only in the manual operating mode.
You must perform two consecutive function 43 selections to initiate a service processor dump. The following table shows an example of function 43.
| Function/Data | Action or description |
|---|---|
4 3 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 43. |
4 3 0 0 _ _ _ _ __ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to confirm. |
A 1 0 0 3 0 4 3 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Displays the confirmation system reference code (SRC). |
4 3 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 43. |
4 3 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to confirm. |
These functions are reserved.
This function allows you to view and change the platform dump data.
This function is available only in the manual operating mode.
When you select function 55 and press Enter, you can view and change the platform dump collection policy, platform dump hardware content, and platform dump firmware content settings
The following table shows an example of how to view the platform dump data.
| Function/Data | Action or description |
|---|---|
5 5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 55. |
5 5 * * _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to enter sub-function mode. |
5 5 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to select to view the platform dump variables. |
5 5 0 0 _ xxyyzz_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to execute selected sub-function.
|
5 5 * * _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to select sub-function exit. |
5 5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to exit sub-function mode. |
The following table shows an example of how to change the platform dump data.
| Function/Data | Action or description |
|---|---|
5 5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to scroll to function 55. |
5 5 * * _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to enter sub-function mode. |
5 5 0 2 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to select to
change the platform dump variable.
|
5 5 0 2 _ 0 0 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to execute selected sub-function.
|
5 5 * * _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Use the Increment or Decrement buttons to select sub-function exit. |
5 5 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
Press Enter to exit sub-function mode. |
These functions are reserved.
This function displays system status SRCs.
This function is available only in the manual operating mode.
When you select function 63 and press Enter, you can display up to the last 25 system status SRCs.
This function displays diagnostic status SRCs.
This function is available only in the manual operating mode.
When you select function 64 and press Enter, you can display up to the last 25 diagnostic status SRCs.
These functions are not applicable.
These functions are reserved.
Learn about the valid initial program load (IPL) types, system operating modes, speeds, and firmware IPL modes that are used in control panel functions.
Refer to the following tables:
| Initial program load (IPL) type | Action or description |
|---|---|
| A | IPL from disk using copy A of the system Licensed Internal Code. |
| B | IPL from disk using copy B of the system Licensed Internal Code. |
| C | Reserved for hardware service use only.
Attention: Incorrect use of this function can cause severe data loss. |
| D | IPL from media other than load-source disk. Alternate IPL for code installation support. |
| System operating mode | Action or description |
|---|---|
| Manual (M) | Allows you to perform an attended IPL and provides access to restricted control panel functions. |
| Normal (N) | Allows you to perform an unattended IPL. |
| IPL speed | Action or description | Details |
|---|---|---|
| F | Fast override for one IPL. | Fast IPL runs. Some hardware diagnostics are passed over. |
| S | Slow override for one IPL. | Full hardware diagnostics runs. Use this
speed whenever hardware is changed, for intermittent hardware failure, or
on the first installation IPL. The following diagnostics are run:
|
| V=F | Use system-defined speed. | Fast IPL set by the system value (displayed at function 01). |
| V=S | Use system-defined speed. | Slow IPL set by the system value (displayed at function 01). |
| V | Fast IPL or slow IPL set by the system value (selected at function 02). | Function 02 selection, or the system default at each IPL. |
| H | Hyperboot override for one IPL. | Hyperboot IPL runs. Most hardware diagnostics are skipped and the system's cached data is used unless new VPD is discovered. |
| X | Extreme override for one IPL. | Extreme IPL runs. All hardware diagnostics are skipped and the system's cached data is used. There are no checks for new hardware. |
| V=H | Use system-defined speed. | Hyperboot IPL is set by the system value (displayed at function 01). |
| V=X | Use system-defined speed. | Extreme IPL is set by the system value (displayed at function 01). |
| IPL type | Action or description |
|---|---|
| P | IPL from disk using copy P of the system Licensed Internal Code. |
| T | IPL from disk using copy T of the system Licensed Internal Code. |
Learn about the control panel functions, IPL modes and values, and other concepts.
The IBM i5/OS remote control panel lets you use control panel functions through a PC.
The graphical user interface of the remote control panel looks similar to the physical control panel. The remote control panel has the following characteristics:
For information about deciding whether the remote control panel or the virtual control panel will best meet your needs, see Differences between the virtual control panel and remote control panel.

Determine which remote control panel (RCP) configuration is best for your environment.
The following information can help you determine which IBM i5/OS remote control panel (RCP) configuration is best for your environment:
After the configuration is authorized, it reappears in Properties the next time you connect.
The IBM i5/OS virtual control panel is an alternative to the remote control panel on servers that do not support a directly connected remote control panel and do not have a network adapter. Like the remote control panel, the virtual control panel is a way to use control panel functions through a PC.
The graphical user interface for the virtual control panel is identical to the remote control panel. Also, the virtual control panel can perform most of the same functions as the remote control panel.
For information about deciding whether the remote control panel or the virtual control panel best meets your needs, see Differences between the virtual control panel and remote control panel.
The following table lists requirements and restrictions for the virtual control panel.
| Requirements | Restrictions |
|---|---|
|
|
Ensure that you understand the following connectivity and usage requirements and restrictions before you install the Operations Console virtual control panel (VCP). For information about installing the VCP, see Setting up the virtual control panel.
| Requirements | Restrictions |
|---|---|
|
|
| Requirements | Restrictions |
|---|---|
|
|

The major functional difference between the directly connected remote control panel (RCP) and the virtual control panel (VCP) is that the virtual control panel cannot power on the server.
If you need to power on the system at a later time, you can use the IPL scheduling function in Operational Assistant by pressing the Attention key. You can also use the GO POWER command, and select option 2 (Change power on and off schedule). You can also use the Hardware Management Console (HMC), if installed, or the Advanced System Management interface (ASMI) to control power on a partition.
The following POWER5 server models work with the virtual control panel (VCP) and the LAN-connected remote control panel (RCP):
Learn about the control panel function codes used to indicate status and function options for a system that is managed by a Hardware Management Console (HMC).
If you are managing the system with the Hardware Management Console (HMC), use the HMC to perform control panel functions. Servers without physical panels (for example, 9406-595, 9119, 590, or 9118-575) require the HMC to perform the equivalent control panel functions. The HMC affects the physical control panel in the following ways:
The following table lists the control panel functions that you can perform on the HMC.
| Function | Description |
|---|---|
| 01 |
This function is available in both normal and manual operating mode. |
| 02 | Performs a slow boot. This function is available in both normal and manual operating mode. |
| 03 | Performs a re-IPL. The IPL uses the selected IPL options. This function is available only in manual operating mode and when the system power is on. |
| 04 | Performs a lamp test; all displays and indicators are switched on. This function is available in both normal and manual operating mode. |
| 05-06 | Reserved. |
| 07 | Allows you to set SPCN configuration IDs. This function is available only in manual operating mode when the system is in standby. |
| 08 | Causes a fast power off. This function is available only when the system is in manual operating mode and the system power is on. |
| 09-10 | Reserved. |
| 11-19 | Displays a system reference code (SRC) on the control panel. These functions are available in both normal and manual operating mode when an SRC is available. |
| 20 | Displays the machine type, model, processor feature code, processor class indicator, and IPL path description. This function is available in both normal and manual operating mode. |
| 21 | Causes the Use Dedicated Service Tool (DST) display to appear on the system console. This function is available only in the manual operating mode and when activated by the operating system. |
| 22 | Forces a partition dump. This function is available only in the manual operating mode and when activated by the operating system. |
| 23-24 | Reserved. |
| 25-26 | Not applicable. |
| 27-29 | Reserved. |
| 30 | Displays CEC FSP IP address and location. This function is available only in the manual operating mode and when activated by the FSP. |
| 31-33 | Reserved. |
| 34 | Retries the partition dump. This function is available only in the manual operating mode and when activated by the operating system. |
| 35-41 | Reserved. |
| 42-43 | Not applicable. |
| 44-49 | Reserved. |
| 50-52 | Reserved. |
| 53 | Unconfigures an intermittently failing processor (repeat GARD function). This function is available only in the manual operating mode. |
| 54 | Reserved. |
| 55 | Platform dump override. This function is available only in the manual operating mode when activated by the FSP and when CE scroll ranges are enabled. |
| 56-62 | Reserved. |
| 63 | Progress indicator history. This function is available only in the manual operating mode. |
| 64 | Diagnostic status SRC trace. This function is available only in the manual operating mode. |
| 65 | Deactivates remote service. This function is available only in the manual operating mode when activated by the operating system and when CE scroll ranges are enabled. |
| 66 | Activates remote service. This function is available only in the manual operating mode when activated by the operating system and when CE scroll ranges are enabled. |
| 67 | Disk unit I/O processor (IOP) reset/reload is enabled only by specific disk unit SRCs. This function is available only in the manual operating mode when activated by the operating system and when CE scroll ranges are enabled. |
| 68 | Turns off power domains during concurrent maintenance of IOPs and IOAs. This function is available only in the manual operating mode when activated by the operating system and when CE scroll ranges are enabled. |
| 69 | Turns on power domains during concurrent maintenance of IOPs and IOAs. This function is available only in the manual operating mode when activated by the operating system and when CE scroll ranges are enabled. |
| 70 | Dump service processor control storage. Initiates an I/O processor (IOP) dump; enabled by specific error conditions. This function is available only in the manual operating mode when activated by the operating system and when CE scroll ranges are enabled. |
Learn about the control panel function codes used to indicate status and function options for the 7037-A50 server and the 7047-185 workstation.
The following table includes descriptions of the control panel function codes.
| Function code | Function selected |
|---|---|
| 01 | Displays the current IPL parameters. This function is available in both normal and manual operating mode. |
| 02 | Used to select the firmware IPL mode. |
| 03 | Not applicable. |
| 04 | Lamp test; all displays and indicators are lit. This function is available in both normal and manual operating mode. |
| 05 | Used for Remind mode. This function is available in both normal and manual operating mode. |
| 06 | Displays the base motherboard controller (BMC) version. This function is available in both normal and manual operating mode. |
| 07 through 08 | Not applicable. |
| 09 | Displays the base motherboard controller (BMC) fan speed. This function is available in both normal and manual operating mode. |
| 10 | Displays the temperature. This function is available in both normal and manual operating mode. |
| 11 through 19 | Not applicable. |
| 20 | Displays the machine type and model. This function is available in both normal and manual operating mode. |
| 21 | Not supported. |
| 22 | Forces a partition dump. To perform a system main storage dump, see Performing dumps. |
| 23 through 49 | Not applicable. |
If you cannot find the function code in this chart, added features or devices might not have been available when this information was produced. Look on the control panel for supplemental unit function code information for the function code that you displayed.
Learn about which function codes are supported by the remote control panel (RCP), virtual control panel (VCP), or HMC .
There are few functional differences among the remote control panel (RCP), virtual control panel (VCP), and physical control panel. The main difference is in how they can or cannot be used to power up the server. For example, consider the following:
If you are managing the system with the Hardware Management Console (HMC), use the HMC to perform control panel functions. The HMC affects the physical control panel in the following ways:
The following table describes the control panel function codes and whether the virtual control panel, remote control panel, and HMC support them.
| Function code | Virtual control panel function and LAN-connected remote control panel | HMC | Function description |
|---|---|---|---|
| 01 | Yes | Yes |
|
| 02 | Yes | Yes. Initiates a slow boot. | Used to select the IPL type, system operating mode, IPL speed, and firmware IPL mode. |
| 03 | Yes | Yes | Starts an IPL to load the system. The IPL uses the selected IPL options. |
| 04 | Yes | Yes | Lamp test; all displays and indicators are lit. |
| 05 through 06 | No | Not applicable | Reserved. |
| 07 | Not applicable | Yes | Allows you to perform SPCN service functions. |
| 08 | Yes | Yes | Fast power off. For more information, see the following: |
| 09 through 10 | Not applicable | Reserved | Reserved. |
| 11 through 19 | Yes | Yes | Displays a system reference code (SRC) on the control panel. |
| 20 | Yes | Yes | Displays the machine type, model, processor feature code, processor class indicator, and IPL path description. |
| 21 | Yes | Yes | Causes the Use Dedicated Service Tool (DST) display to appear on the system console. To exit the DST, select the Resume operating system display option. |
| 22 | Yes | Yes | Forces a partition dump. First, see Function 34: Retry partition dump. To perform a system main storage dump, see Performing dumps. |
| 23 | Not applicable | Reserved | Reserved. |
| 24 | Not applicable | Reserved | Reserved. |
| 25 | Yes | Yes | Uses service switches 1 and 2 to enable or disable functions 50 through 70. |
| 26 | Yes | Not applicable | Uses service switches 1 and 2 to enable or disable functions 50 through 70. |
| 27 through 29 | Not applicable | Reserved | Reserved. |
| 30 | Not applicable | No. This function is intended to be used from the physical control panel when no HMC is available. | Displays CEC FSP IP address and location. |
| 31 through 33 | Not applicable | Reserved | Reserved. |
| 34 | Yes | Yes | Retries the partition dump. |
| 35 through 41 | Not applicable | Reserved | Reserved. |
| 42 | Not applicable | No | Performs a platform dump. |
| 43 | Not applicable | No | Performs a service processor dump. |
| 44 through 49 | Not applicable | Reserved | Reserved. |
| 50 through 53 | Not applicable | Reserved | Reserved. |
| 54 | Not applicable | Reserved | Reserved. |
| 55 | Not applicable | Not applicable | Platform dump override. |
| 56 through 62 | Not applicable | Reserved | Reserved. |
| 63 | Not applicable | Yes | System status SRC trace. |
| 64 | Not applicable | Yes | Service processor diagnostic status SRC trace. |
| 65 | Yes | Yes | Deactivates remote service. |
| 66 | Yes | Yes | Activates remote service. |
| 67 | Yes | Yes | Disk unit I/O processor (IOP) reset/reload is enabled only by specific disk unit SRCs. |
| 68 | Yes | Yes | Concurrent maintenance power domain power off. |
| 69 | Yes | Yes | Concurrent maintenance power domain power on. |
| 70 | No | Initiated by specific error conditions. | IOP dump. |
| Power button | Power button in graphical interface for powering off the server only. | For information about using the HMC to power on the server, see Powering on the managed system. | OFF = Delayed power off
ON = Immediate power on (can be timed power on) |
| Attention light | Yes | Not applicable | Attention state LED. |
| Power indicator | Power indicator in graphical interface. | Not applicable | Lit when power is fully operational. |
You can set up the remote control panel (RCP) through an Operations Console configuration.
To receive control panel functions with the RCP, you must install the Operations Console and configure a remote control panel.
You can set up the virtual control panel (VCP) through an Operations Console configuration.
To receive control panel functions with the VCP, you must install the Operations Console and configure a virtual control panel. The configuration path to create the VCP connection uses the Operations Console on a network path but does not require a network or network adapter.
You must have a local console directly attached to the server configured in order for the virtual control panel to function. To set up a local console directly attached to the server configuration, follow the setup instructions in the Operations Console. The virtual control panel functions have some limitations and restrictions.
To install the virtual control panel (VCP), do the following:
The Operations Console virtual control panel (VCP) requires an available, unused service tools device ID.
If the console value in IBM i5/OS is not set for Operations Console (LAN attachment), you can use the existing service tools device ID of QCONSOLE for the VCP.
To create a service tools device ID for the Operations Console VCP, do the following:
| Option | Description |
|---|---|
| DST |
|
| SST |
|
If you are using a service tools user ID other than QSECOFR, QSRV, 22222222, or 11111111 for use with the Operations Console virtual control panel (VCP), you must set the service tools user privileges for the partition remote panel key to allow access to the mode function.
To verify or set the service tools user privilege, do the following:
| Option | Description |
|---|---|
| DST |
|
| SST |
|
There are various methods to access control panel functions, including the physical control panel, an i5/OS virtual control panel or remote control panel, and through the Hardware Management Console (HMC).
Figure 25 shows an example of a control panel.

To select a function number, press the Increment (↑) or Decrement (↓) button on the control panel. To activate the function, press Enter on the control panel while the desired function number is displayed.
The i5/OS virtual control panel and remote control panel are graphical representations of the physical control panel. They install through Operations Console and allow you to access control panel functions using a PC.
If you are managing the system with the HMC, you should use the HMC to perform control panel functions. The HMC affects the physical control panel in the following ways:
For information on using the HMC to access control panel functions, see the Operations Guide for the Hardware Management Console and Managed Systems, SA76-0085.
To use a remote control panel (RCP) to select and activate functions on the control panel, you must have the Operations Console configured to use a remote control panel and you must establish a connection to the remote control panel.
If you do not have the Operations Console configured to use a remote control panel, see Setting up the remote control panel.
To connect to the remote control panel (RCP), do the following:
If the console configuration includes the remote control panel, the remote control panel automatically starts. If the console configuration does not include the remote control panel, you can add it by clicking Properties → Configuration and selecting the appropriate settings.
To use a virtual control panel (VCP) to select and activate functions on the control panel, you must install and establish a connection between the virtual control panel configuration and the server.
If you have not installed a virtual control panel, see Setting up the virtual control panel.
To connect to the virtual control panel (VCP), do the following steps:
If you are managing the system with the Hardware Management Console (HMC), you can perform control panel functions with the HMC instead of using the physical control panel.
For details about which control panel functions are available on the HMC, see Control panel function codes on the HMC. For information about how to perform control panel actions on the HMC, see the following table:
| Function | HMC action |
|---|---|
| 01 |
To view the power-on parameters or settings on the HMC, do the following:
|
| 02 | To perform a slow boot on the HMC,
do the following:
|
| 03 |
To re-IPL using the HMC, do the following:
|
| 04 | To perform the lamp test using the Service Utilities
in Service Focal Point, do the following:
|
| 05-06 | View the serviceable event log. For more information about viewing serviceable events, see Viewing serviceable events. |
| 07 | Use the Advanced System Management interface (ASMI)
to configure I/O enclosures. To access the ASMI, do the following:
|
| 08 | Power off the logical partition.
To power off a logical partition, do the following:
The immediate option is equivalent to the fast power off. The delayed option is equivalent to the white button power off. |
| 09-10 | Reserved. |
| 11-19 | To view reference code information on the HMC,
do the following:
|
| 20 | To display the machine type, model, and processor feature
code on the HMC, do the
following:
|
| 21 | Use the Service Utilities in Service Focal Point. To
use the Service Utilities, do the following:
|
| 22 |
Dump the logical partition. To dump a partition, do the following:
|
| 23-24 | Reserved. |
| 25-26 |
No longer needed to access functions equivalent to 50-70. |
| 27-32 | Reserved. |
| 33 | This function is no longer needed. |
| 34 |
Retry partition dump. To retry a partition dump, do the following:
|
| 35-41 | Reserved. |
| 42-43 |
These functions are performed on the physical operator panel on the managed system. Use the following procedure to work with dump information. Use the Service Utilities in Service Focal Point. To use the Service Utilities, do the following:
|
| 44-49 | Reserved. |
| 50 | No longer used. |
| 51 | No longer used. |
| 52 | No longer used. |
| 53 | Use the Advanced System Management interface (ASMI).
To access the ASMI, do the following:
|
| 54 | Reserved. |
| 55 | Use the Advanced System Management interface (ASMI)
to initiate a platform dump. To access the ASMI interface, do the following:
|
| 56-62 | Reserved . |
| 63 | View either your managed system's properties or the
logical partition properties.
To view your managed system's properties, see Viewing information about a managed system. On the managed system properties window, click the Reference Code tab, and then click DETAILS. To view logical partition properties, do the following:
|
| 64 | Use the Advanced System Management interface (ASMI).
To access the ASMI, do the following:
|
| 65 | Use the Service Utilities in Service Focal Point. To
use the Service Utilities, do the following:
|
| 66 | Use the Service Utilities in Service Focal Point. To
use the Service Utilities, do the following:
|
| 67 | Use the Service Utilities in Service Focal Point, and
. To use the Service Utilities, do the following:
|
| 68 | Use the Service Utilities in Service Focal Point. To
use the Service Utilities, do the following:
|
| 69 | Use the Service Utilities in Service Focal Point. To
use the Service Utilities, do the following:
|
| 70 | Use the Service Utilities in Service Focal Point. To
use the Service Utilities, do the following:
|
Learn about problems that might occur when accessing the remote control panel (RCP) or virtual control panel (VCP).
When setting up your initial connection, you might encounter problems accessing your remote control panel (RCP) or virtual control panel (VCP). The following sections describe some of the control panel problems that might occur:
Learn why the remote control panel (RCP) might fail to start.
If you are connecting over a network, the RCP might fail to start when either the user ID or service tools device ID being used does not have permission to use the RCP.
Learn why the virtual control panel (VCP) might fail to start.
If the virtual control panel (VCP) fails to start, do the following:
Direct 192.168.0.0 255.255.255.0
A SOCKS-enabled PC accesses the Internet through a firewall, such as Microsoft Proxy Client, Hummingbird SOCKS Client, or others.
Learn about why you might be unable to use the mode function on a remote control panel (RCP) or virtual control panel (VCP).
If you are unable to use the mode function on a remote control panel (RCP) or virtual control panel (VCP), check that the user that authenticated the connection (Service Device Sign-on) has the Partition remote panel key privilege for the logical partition to which they are connected. To verify the privilege setting, do the following:
| Option | Description |
|---|---|
| DST |
|
| SST |
|
That user must be granted this privilege, by logical partition, in order to use the mode function. Also, if the system supports the keystick, the keystick must be inserted before the mode function is active.
Learn about virtual control panel (VCP) authentication errors and solutions.
See the following table for Operations Console virtual control panel (VCP) authentication errors and solutions.
| Error message | Solution |
|---|---|
| The current access password entered is not valid. Please enter the valid access password. | This message typically means that the access password that you entered in the Service Device Sign-on window is not the same as the password that you entered in the Specify Access Password window during the configuration wizard. Ensure that the Caps Lock key is not active, and then re-enter the access password using the password that you assigned. Passwords are case sensitive. |
| The PC service tools device password and the service tools device password do not match. Either the service tools device ID <name> is already in use or the passwords must be RESET on this PC and the server. | This is an indication that the Service Tools Device ID password might be incorrect. If this is the case, then the Service Device ID password stored on the PC no longer matches the value stored on the server. The password assigned to the Service Device ID during the configuration wizard on the PC must match the password assigned to the service device ID on server. If you used the QCONSOLE device ID, then both the PC and server must have the password set to QCONSOLE. Each time that you authenticate successfully, this password is re-encrypted to a new value and stored on both sides of the connection. In rare situations, this password does not synchronize, so you need to reset the value back to the original default values on both the PC and the server. For instructions, see Resynchronize the PC's and the server's service tools device ID passwords. |
Use the menus within system management services (SMS) to view information about your system or partition and to perform tasks such as changing the boot list and setting the network parameters. These menus can be used for AIX or Linux partitions.
Learn how to start the system management services (SMS) from a partitioned or nonpartitioned server.
To start the SMS, select one of the options below, depending on whether the system is partitioned or nonpartitioned.
The system will reboot into the SMS menus.
The system will reboot into the SMS menus.
Learn how to use each of the system management services (SMS) menus and how each option on the menus can help you manage your system.
If you have not performed the steps to start the system management services, see Starting the system management services and select the correct procedure for your system before you continue.
The following table contains the titles of the menus or tasks that can be accessed in the SMS application. Use it to access and review the specific task that you want.
| Menu or task | Description |
|---|---|
| Main Menu | Describes the opening menu when first starting SMS. |
| Select Language | You can change the language used by the SMS menus. |
| Setup Remote IPL | You can enable and set up the remote startup capability of your server. |
| Adapter Configuration | You can set the network speed, enable or disable spanning tree, and set the protocol. |
| Speed, Duplex | You can set the interface speed at which the card runs and select half or full duplex. |
| Spanning Tree Enabled | You can enable or disable the spanning tree option. |
| Protocol | You can set the appropriate protocol for your network. |
| Ping Test | You can test an adapter's network connection to a remote system. |
| Advanced Setup: BOOTP | You can view and modify the BOOTP values. |
| Change SCSI Settings | You can view and change the addresses of the SCSI controllers attached to your system. |
| Select Console | You can select which console to use to display the SMS menus. |
| Select Boot Options | You can view and set various options regarding the installation devices and boot devices. The Select boot options menu gives you the following options: Select Install or Boot Device, Select Boot Devices, Multiboot Startup |
| Normal Mode Boot or Service Mode Boot | You can have your system perform a boot in the normal or service mode. |
| Hard Drive | Displays a menu identifying the different types of hard drives installed on your system. (for example, SCSI or SSA) |
| Set Boot Sequence | You can set the location of the device in the boot list. It gives options to Display current settings, Restore default settings, Multiboot startup, and Exiting system management services |
Main Menu
1. Select Language
2. Setup Remote IPL (Initial Program Load)
3. Change SCSI Settings
4. Select Console
5. Select Boot Options
--------------------------------------------------------------------------------
Navigation keys:
X = eXit System Management Services
--------------------------------------------------------------------------------
Type the number of the menu item and press Enter or Select a Navigation key: _
On all menus except the main menu, there are several navigation keys:
If you enter X, you are asked to confirm your choice to exit the SMS menus and start the operating system.
When there is more than one page of information to display, there are two additional navigation keys:
On each menu, you are given the option of choosing a menu item and pressing Enter (if applicable), or selecting a navigation key.
SELECT LANGUAGE 1. English 2. Francais 3. Deutsch 4. Italiano 5. Espanol -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select this option, you can enable and set up the remote startup capability of your server. A list of network interface card (NIC) adapters in the server is displayed. An example of this menu follows:
NIC Adapters Device Slot Hardware Address 1. Port 1 - 2 PORT Gigabit Et Un-P1-T9 00096bff616b 2. Port 2 - 2 PORT Gigabit Et Un-P1-T10 00096bff616a 3. 10/100/1000 Base-TX PCI-X Un-CB1-C03-T1 000295e3814f -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select an adapter, the Network Parameters menu is displayed:
Network Parameters Port 1 - 2 PORT Gigabit Et Un-P1-T9 00096bff616b 1. IP Parameters 2. Adapter Parameters 3. Ping Test 4. Advanced Setup: BOOTP -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Selecting the IP (Internet Protocol) parameters option displays the following menu:
IP Parameters Port 1 - 2 PORT Gigabit Et Un-P1-T9 00096bff616b 1. Client IP Address [000.000.000.000] 2. Server IP Address [000.000.000.000] 3. Gateway IP Address [000.000.000.000] 4. Subnet Mask [255.255.255.000] -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
To change IP parameters, type the number of the parameters for which you want to change the value. Entering IP parameters on this menu automatically updates the parameters on the ping test menu.
Adapter Configuration Port 1 - 2 PORT Gigabit Et Un-P1-T9 00096bff616b 1. Speed, Duplex 2. Spanning Tree Enabled 3. Protocol -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Adapter Configuration Port 1 - 2 PORT Gigabit Et Un-P1-T9 00096bff616b 1. auto, auto 2. 10,half 3. 10,full 4. 100,half 5. 100,full -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
The spanning tree protocol is a link-management protocol that provides path redundancy while preventing duplicate loops in a network. The spanning tree option is enabled or disabled on the network switch. If the LAN adapter port being configured with the SMS adapter menus is attached to a network switch that has the spanning tree protocol enabled, the spanning tree option on the Adapter Configuration menu remains enabled, which is the default. If the network switch does not support the spanning tree protocol, or it is disabled, the spanning tree option on the Adapter Configuration menu can be disabled. Leaving this option enabled does not affect the adapter's operation. This setting potentially affects the ping test and NIM installation. If the port's spanning tree setting is disabled, but it is enabled on the network switch to which it is attached, the ping test and NIM installation might fail even though the network and the adapter are operational.
Protocol Port 1 - 2 PORT Gigabit Et Un-P1-T9 00096bff616b 1. Standard <=== 2. IEEE802.3 -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Advanced Setup: BOOTP Port 1-IBM 2 PORT 1000 Base-SX PCI-X Adapter: U788D.001.23A0034-P1-T7 1. Bootp Retries 5 2. Bootp Blocksize 512 3. TFTP Retries 5 -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select this option, you can view and change the addresses of the SCSI controllers attached to your system.
SCSI Utilities 1. Hardware Spin Up Delay 2. Change SCSI Id -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select the Select Console utility, you can select which console to use to display the SMS menus. This selection is only for the SMS menus and does not affect the console used by the operating system.
Follow the instructions that are displayed on the menu. The firmware automatically returns to the menu on which the POST indicators (memory, keyboard, network, SCSI, speaker) display across the bottom of the menu. Press the numeric 1 key after the word keyboard is displayed and before the word speaker is displayed to return to the SMS main menu.
Select this option to view and set various options regarding the installation devices and boot devices.
1. Select Install or Boot a Device 2. Select Boot Devices 3. Multiboot Startup -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
If you select Select Install or Boot Device, the following menu is displayed:
Select Device Type 1. Diskette 2. Tape 3. CD/DVD 4. IDE 5. Hard Drive 6. Network 7. List All Devices -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Select Hard Drive Type 1. SCSI 2. SSA 3. SAN 4. SAS 5. SATA 6. USB 7. IDE 8. ISA 9. List All Devices -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Version EM310_024 SMS 1.6 (c) Copyright IBM Corp. 2000, 2005 All rights reserved. -------------------------------------------------------------------------------- Select Media Adapter 1. Un-P1-T14 /pci@80000002000000d/pci@2/pci1069,b166@1/scsi@0 2. Un-P1-T12 /pci@80000002000000f/pci@2,2/pci1069,b166@1/scsi@0 3. Un-P1-T13 /pci@80000002000000f/pci@2,2/pci1069,b166@1/scsi@1 4. List all devices -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select an adapter, the next menu displays the devices of the requested type that are attached to that adapter. In the following example, all of the SCSI hard files that are attached to the first adapter are listed:
Version EM310_024
SMS 1.6 (c) Copyright IBM Corp. 2000, 2005 All rights reserved.
--------------------------------------------------------------------------------
Select Device
Device Current Device
Number Position Name
1 1 SCSI 73407 MB Harddisk Un-P1-T14 /pci@80000002000000d/pci@2/
pci1069,b166@1/scsi@0
--------------------------------------------------------------------------------
Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services
--------------------------------------------------------------------------------
Type the number of the menu item and press Enter or Select a Navigation key: _
You can now select the appropriate device for this installation or boot.
When a device is selected for installing the operating system, or to boot from, the Select Task menu retrieves more information about the device, or to boot from that device in normal mode or service mode. The following is an example of this menu.
Select Task SCSI 73407 MB Harddisk Un-P1-T14 /pci@80000002000000d/pci@2/pci1069,b166@1/scsi@0 1. Information 2. Normal Mode Boot 3. Service Mode Boot --------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
device type -> bus type -> adapter -> devices attached to the adapter
By selecting List All Devices from the Select Device Type menu or the Select Media Type menu, you can view all of the potentially bootable devices at one time.
The List All Devices function can take a long time on a large system with many I/O adapters and devices, such as large disk arrays.
Select Select Boot Devices to view and change the customized boot list, which is the sequence of devices read at startup.
Configure Boot Device Order 1. Select 1st Boot Device 2. Select 2nd Boot Device 3. Select 3rd Boot Device 4. Select 4th Boot Device 5. Select 5th Boot Device 6. Display Current Setting 7. Restore Default Setting -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select any of the options 1-5, the Select Device Type menu is displayed.
Select Device Type 1. Diskette 2. Tape 3. CD/DVD 4. IDE 5. Hard Drive 6. Network 7. None 8. List All Devices -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select a device type, such as option 5, a Select Media Type menu is displayed. The following is an example of that menu.
Select Media Type 1. SCSI 2. SSA 3. SAN 4. IDE 5. ISA 7. None 8. List All Devices -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
When you select the media type, all adapters of that type are displayed on the Select Media Adapter menu. The following is an example of that menu for a SCSI media type.
Version EM310_024 SMS 1.6 (c) Copyright IBM Corp. 2000, 2005 All rights reserved. -------------------------------------------------------------------------------- Select Media Adapter 1. Un-P1-T14 /pci@80000002000000d/pci@2/pci1069,b166@1/scsi@0 2. Un-P1-T12 /pci@80000002000000f/pci@2,2/pci1069,b166@1/scsi@0 3. Un-P1-T13 /pci@80000002000000f/pci@2,2/pci1069,b166@1/scsi@1 4. List all devices -------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Then, you must select each adapter individually to see the devices that are attached to it. The following is an example of this menu for the first adapter in the previous example:
Version EM310_024
SMS 1.6 (c) Copyright IBM Corp. 2000, 2005 All rights reserved.
--------------------------------------------------------------------------------
Select Device
Device Current Device
Number Position Name
1 1 SCSI 73407 MB Harddisk Un-P1-T14 /pci@80000002000000d/pci@2/
pci1069,b166@1/scsi@0
--------------------------------------------------------------------------------
Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services
--------------------------------------------------------------------------------
Type the number of the menu item and press Enter or Select a Navigation key: _
When you select a device type, you can view detailed information about the device or set the device location in the boot list from the Select Task menu. The following is an example of the menu for a hard disk.
Select Task SCSI 73407 MB Harddisk Un-P1-T14 /pci@80000002000000d/pci@2/pci1069,b166@1/scsi@0 1. Information 2. Set Boot Sequence: Configure as 1st Boot Device --------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _
Selecting Information displays a menu similar to the following for a hard disk.
Device Information
/pci@8000000200000dd/pci@2/pci1069,b166@1/scsi@1/sd@5,0
: (Bootable)
DEVICE : SCSI 73407 MB Harddisk Un-P1-T14 /pci@80000002000000d/pci@2/
pci1069,b166@1/scsi@0
NAME : sd
DEVICE-TYPE : block
Parent Information
IBM,FW-ADAPTER-NAME: Ultra-320
NAME : scsi
DEVICE-TYPE : scsi-2
---------------------------------------------------------------------------------
Navigation keys:
M = return to main menu
ESC key = return to previous screen X = eXit System Management Services
---------------------------------------------------------------------------------
Type the number of the menu item and press Enter or Select a Navigation key: _
This option displays the current setting of the customized boot list. An example of this menu, with one device in the boot list, follows.
Current Boot Sequence 1. SCSI 73407 MB Harddisk Un-P1-T14 /pci@80000002000000d/pci@2/pci1069,b166@1/scsi@0 2. None 3. None 4. None 5. None ------------------------------------------------------------------------------------ Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services ------------------------------------------------------------------------------------ Type the number of the menu item and press Enter or Select a Navigation key: _
This option restores the boot list to the default boot list. The default boot list varies depending on the devices that are installed in the system.
The default boot list is as follows:
Multiboot Startup toggles the multiboot startup flag, which controls whether the multiboot menu is invoked automatically on startup.
After you finish using the SMS menus, type x (for exit) to boot your system.
Learn how the Power-on self-test (POST) keys can start services or initiate service mode boots used for configuring the system and diagnosing problems.
After power is turned on and before the operating system is loaded, the system does a power-on self-test (POST). This test performs checks to ensure that the hardware is functioning correctly before the operating system is loaded. During the POST, a POST screen is displayed, and POST indicators appear on the firmware console (if one is connected).
The POST keys, if pressed after the keyboard POST indicator is displayed and before the last POST indicator speaker is displayed, cause the system to start services or to initiate service mode boots used for configuring the system and diagnosing problems.
Numeric 1 key
The numeric 1 key, when pressed during POST, starts the system management services interface.
Numeric 5 key
The numeric 5 key, when pressed during POST, initiates a system boot in service mode using the default service mode boot list.
This mode attempts to boot from the first device of each type found in the list. It does not search for other bootable devices of that type if the first device is not bootable. Instead, it continues to the next device type in the list. The firmware supports up to five entries in the boot list.
The default boot sequence is:
Numeric 6 key
The numeric 6 key works like the numeric 5 key, except that firmware uses the customized service mode boot list that was set up by AIX when AIX was first booted, or manually using the AIX service aids.
Learn how to collect reference codes and other system information.
The reference codes and system information can help determine the correct solution to fix a problem.
Learn how to use the control panel to collect reference codes and other system information.
Follow these steps to collect reference codes and system information (functions 11 through 20) using the control panel:
Learn how to use AIX tools to collect reference codes and other system information.
Learn more about procedures that can aid you in analyzing problems.
Occasionally your problem analysis will lead you to more extensive procedures that can help analyze a problem.
Use these tools to diagnose hardware problems on your AIX or Linux systems.
Use these diagnostics only if you are directed to do so by your next level of support or your hardware service provider.
Diagnostics are available for AIX and Linux systems, which can help you perform hardware analysis. Additionally, there are various service aids in AIX diagnostics that can help you with service tasks on the system. If there is a problem, you will receive a Service Request Number (SRN) that can pinpoint the problem and determine a corrective action.
If you have AIX installed and it is running, you can perform online diagnostics. However, if the installed AIX cannot be started, or you have Linux installed, you will need to run the diagnostics from CD or from a NIM server.
If you have AIX installed and it can be started, use this procedure to perform diagnostic procedures when directed from another procedure or by service and support.
When you run the online diagnostics, and AIX is installed, the support for some devices might not be automatically installed. If this happens, that device will not display in the test list when online diagnostics run.
Three modes are available for running the online diagnostics:
Use this procedure to run the online diagnostics in service mode.
Perform the following steps:
Use this procedure to run the online diagnostics in maintenance mode.
Maintenance mode requires that all activity on the system running the AIX operating system be stopped so that the online diagnostics have most of the resources available. All of the system resources, except the SCSI adapters, memory, processor, and the disk drive used for paging can be checked.
Perform the following steps to run the online diagnostics in maintenance mode:
Use this procedure to run the online diagnostics in concurrent mode.
Use concurrent mode to run online diagnostics on some of the system resources while the system is running normal activity.
Because the system is running in normal operation, the following resources cannot be tested in concurrent mode:
The following levels of testing exist in concurrent mode:
Perform the following steps to run online diagnostics in concurrent mode:
Learn how to perform a stand-alone diagnostic procedure from CD-ROM or a Network Installation Management (NIM) server when directed from another procedure or by your next level of support.
Learn how to run stand-alone diagnostics from a CD.
Learn how to perform a slow boot using the control panel or ASMI menus depending on your configuration.
In some cases, you need to perform a slow-mode boot in order to perform extended diagnostic testing.
Learn how to use the control panel to perform a slow boot.
In some cases, you need to perform a slow-mode boot in order to perform extended diagnostic testing.
Learn how to use the ASMI menus to perform a slow boot.
In some cases, you need to perform a slow-mode boot in order to perform extended diagnostic testing.
Use this information to learn how to contact the IBM service and support organization.
In general, the term service includes repair of hardware, the ability to ask usage and defect questions about your software, and on-site and remote support for any system concerns through IBM Support.
For up-to-date contact information, visit the Directory of Worldwide Contacts Web site (www.ibm.com/planetwide/)
.
| Type of problem | Call |
|---|---|
|
|
Software:
Hardware:
|
1-800-IBM-SERV (1–800–426–7378) |
Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products successfully.
The following list includes the major accessibility features:
See the IBM Accessibility Center at http://www.ibm.com/able/ for more information about the commitment that IBM has to accessibility.
If you need an accessible version of this publication, send a request to reslink@us.ibm.com. In the request, make sure that you include the publication number and the title.
This information was developed for products and services offered in the U.S.A.
The manufacturer may not offer the products, services, or features discussed in this document in other countries. Consult the manufacturer's representative for information on the products and services currently available in your area. Any reference to the manufacturer's product, program, or service is not intended to state or imply that only that product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any intellectual property right of the manufacturer may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any product, program, or service.
The manufacturer may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the manufacturer.
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: THIS INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The manufacturer may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to Web sites not owned by the manufacturer are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this product and use of those Web sites is at your own risk.
The manufacturer may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning products not produced by this manufacturer was obtained from the suppliers of those products, their published announcements or other publicly available sources. This manufacturer has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to products not produced by this manufacturer. Questions on the capabilities of products not produced by this manufacturer should be addressed to the suppliers of those products.
All statements regarding the manufacturer's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
The manufacturer's prices shown are the manufacturer's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
The drawings and specifications contained herein shall not be reproduced in whole or in part without the written permission of the manufacturer.
The manufacturer has prepared this information for use with the specific machines indicated. The manufacturer makes no representations that it is suitable for any other purpose.
The manufacturer's computer systems contain mechanisms designed to reduce the possibility of undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience unplanned outages, system failures, power fluctuations or outages, or component failures must verify the accuracy of operations performed and data saved or transmitted by the system at or near the time of the outage or failure. In addition, users must establish procedures to ensure that there is independent data verification before relying on such data in sensitive or critical operations. Users should periodically check the manufacturer's support websites for updated information and fixes applicable to the system and related software.
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
Intel, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
InfiniBand and the InfiniBand design marks are trademarks and/or service marks of the InfiniBand Trade Association.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product or service names may be trademarks or service marks of others.
The following Class A statements apply to the IBM servers that contain the POWER6 processor.
Federal Communications Commission (FCC) statement
Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user's authority to operate the equipment.
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
Industry Canada Compliance Statement
This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d'Industrie Canada
Cet appareil numérique de la classe A respecte est conforme à la norme NMB-003 du Canada.
European Community Compliance Statement
This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards.
This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment.
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.
VCCI Statement - Japan

The following is a summary of the VCCI Japanese statement in the box above.
This product is a Class A Information Technology Equipment and conforms to the standards set by the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures.
Electromagnetic Interference (EMI) Statement - People's Republic of China

Declaration: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may need to perform practical action.
Electromagnetic Interference (EMI) Statement - Taiwan

The following is a summary of the EMI Taiwan statement above.
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user will be required to take adequate measures.
IBM Taiwan Contact Information

Electromagnetic Interference (EMI) Statement - Korea

Please note that this equipment has obtained EMC registration for commercial use. In the event that it has been mistakenly sold or purchased, please exchange it for equipment certified for home use.
Germany Compliance Statement
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022 Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen
werden:
"Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung
kann im Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom
Betreiber verlangt werden, angemessene Maßnahmen zu ergreifen und dafür
aufzukommen."
Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG)“. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A.
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen.
Verantwortlich für die Konformitätserklärung nach des EMVG ist die IBM Deutschland GmbH, 70548 Stuttgart.
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
Electromagnetic Interference (EMI) Statement - Russia
Permissions for the use of these publications is granted subject to the following terms and conditions.
Personal Use: You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative works of these publications, or any portion thereof, without the express consent of the manufacturer.
Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of the manufacturer.
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any data, software or other intellectual property contained therein.
The manufacturer reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by the manufacturer, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.
THE MANUFACTURER MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THESE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.