Effective System Management Using The Ibm

Hardware Management Console For Pseries Ibm

Redbooks download

https://ebookbell.com/product/effective-system-management-using-
the-ibm-hardware-management-console-for-pseries-ibm-
redbooks-51841916

Explore and download more ebooks at ebookbell.com

Here are some recommended products that we believe you will be
interested in. You can click the link to download.

Creating An Effective Management System Integrating Policy Deployment

Twi And Kata 1st Edition Patrick Graupp

https://ebookbell.com/product/creating-an-effective-management-system-
integrating-policy-deployment-twi-and-kata-1st-edition-patrick-
graupp-12053532

Effective Implementation Of An Iso 50001 Energy Management System Enms

Marvin T Howell

https://ebookbell.com/product/effective-implementation-of-an-
iso-50001-energy-management-system-enms-marvin-t-howell-5308034

Automotive System Safety Critical Considerations For Engineering And

Effective Management 1st Edition Joseph D Miller

https://ebookbell.com/product/automotive-system-safety-critical-
considerations-for-engineering-and-effective-management-1st-edition-
joseph-d-miller-11363542

Unix Administration A Comprehensive Sourcebook For Effective Systems

And Network Management Bozidar Levi

https://ebookbell.com/product/unix-administration-a-comprehensive-
sourcebook-for-effective-systems-and-network-management-bozidar-
levi-4122588
Effective Portfolio Management Systems 1st Edition Christopher F Voehl
Author H James Harrington Author William S Ruggles Author

https://ebookbell.com/product/effective-portfolio-management-
systems-1st-edition-christopher-f-voehl-author-h-james-harrington-
author-william-s-ruggles-author-12053650

Effective Implementation Of Management Systems Management Systems As A

Success Factor For The Efficiency Of Organizations 1st Ed Jan Kopia

https://ebookbell.com/product/effective-implementation-of-management-
systems-management-systems-as-a-success-factor-for-the-efficiency-of-
organizations-1st-ed-jan-kopia-10490930

Effective Implementation Of Quality Management Systems Woodhead

Publishing India 1st B Purushothama

https://ebookbell.com/product/effective-implementation-of-quality-
management-systems-woodhead-publishing-india-1st-b-
purushothama-2343298

Meeting The Challenge Of 9 11 Blueprints For More Effective Government

Advances In Management Information Systems James Loy

https://ebookbell.com/product/meeting-the-challenge-
of-9-11-blueprints-for-more-effective-government-advances-in-
management-information-systems-james-loy-2138746

Effective Resource Management In Manufacturing Systems Optimization

Algorithms For Production Planning Springer Series In Advanced
Manufacturing 1st Edition Massimiliano Caramia

https://ebookbell.com/product/effective-resource-management-in-
manufacturing-systems-optimization-algorithms-for-production-planning-
springer-series-in-advanced-manufacturing-1st-edition-massimiliano-
caramia-2243728
IBM Front cover

Effective System Management

Using the IBM Hardware
Management Console for
pSeries
Using service-related functions on
the HMC

Planning and implementing a

secure network

Exploiting HMC
commands

Keigo Matsubara
Matt Robbins
Ron Barker
Theeraphong Thitayanun

ibm.com/redbooks
International Technical Support Organization

Effective System Management Using the IBM

Hardware Management Console for pSeries

August 2003

SG24-7038-00
 Note: Before using this information and the product it supports, read the information in
“Notices” on page xix.

First Edition (August 2003)

This edition applies to Release 3, Version 2 of the software (program number 5639-N47) installed
on the IBM Hardware Management Console for pSeries.

© Copyright International Business Machines Corporation 2003. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Chapter 1. Introduction to the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 What is the HMC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 HMC at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Supported managed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.1 pSeries 690 and pSeries 670 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2.2 pSeries 655 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.3 pSeries 650 Model 6M2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.4 pSeries 630 models 6C4 and 6E4 . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.5 pSeries 615 models 6C3 and 6E3 . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.6 RS-422 serial connection to the 7040-W42 system rack . . . . . . . . . 14
1.3 HMC architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 HMC connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4.1 Serial connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4.2 Remote connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.5 HMC order information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.5.1 Supported number of managed systems and partitions . . . . . . . . . . 24
1.5.2 HMC software release numbering scheme . . . . . . . . . . . . . . . . . . . . 24
1.5.3 Ethernet adapter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.5.4 Asynchronous serial adapter configurations . . . . . . . . . . . . . . . . . . . 25

Chapter 2. HMC graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.1 Login and logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.2 HMC graphical user interface at a glance . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.2.1 Navigation area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.2.2 Contents area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.2.3 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.2.4 Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

© Copyright IBM Corp. 2003. All rights reserved. iii

 2.2.5 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3 HMC application overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.4 Server and Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.4.1 Connect and disconnect managed systems . . . . . . . . . . . . . . . . . . . 45
2.4.2 Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.4.3 Server Management menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.5 Virtual terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.1 Virtual terminal window concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.5.2 Virtual terminal window in the Full System Partition . . . . . . . . . . . . . 52
2.5.3 Partition virtual terminal windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.6 Open xterm to access remote system using telnet . . . . . . . . . . . . . . . . . . 52

Chapter 3. Basic managed system operation tasks . . . . . . . . . . . . . . . . . 55

3.1 Viewing properties of the managed system . . . . . . . . . . . . . . . . . . . . . . . 56
3.1.1 Machine property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.1.2 Processor property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.1.3 Policy property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.1.4 I/O Slot property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.1.5 Memory property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.2 Power on the managed system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.2.1 Operation states of a managed system . . . . . . . . . . . . . . . . . . . . . . 64
3.2.2 Rebuild the managed system in the HMC. . . . . . . . . . . . . . . . . . . . . 64
3.3 Activate partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.3.1 Change the default partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.3.2 Activate a specific partition profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.3.3 Activate partitions without selecting a specific partition profile . . . . . 66
3.3.4 Reactivating a partition with a different partition profile. . . . . . . . . . . 66
3.3.5 Partition operating states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.4 Shut down the operating system in a partition . . . . . . . . . . . . . . . . . . . . . 68
3.5 Reset the operating system in a partition . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.6 Power off the managed system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.7 Operating the managed system with the HMC . . . . . . . . . . . . . . . . . . . . . 72
3.7.1 Operator panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.7.2 Power button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.7.3 Reset button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 4. Configuring the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4.1 HMC Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.1.1 User role descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.1.2 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.2 HMC Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.2.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.2.2 Customize Console Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

iv Effective System Management Using the IBM Hardware Management Console for pSeries
 4.2.3 View Console Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.2.4 Customize Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.2.5 Test Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.2.6 Scheduled Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2.7 Enable/Disable Remote Command Execution . . . . . . . . . . . . . . . . . 95
4.2.8 Configure Serial Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.2.9 Enable/Disable Remote Virtual Terminal . . . . . . . . . . . . . . . . . . . . . 97
4.2.10 Change Current Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 5. Managing partition profile data on the HMC . . . . . . . . . . . . . . 99

5.1 Managing profile data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.1.1 Back up profile data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.1.2 Restore profile data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.1.3 Initialize profile data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.1.4 Remove profile data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 6. Managing software levels on the HMC . . . . . . . . . . . . . . . . . . 107

6.1 Software Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.1.1 Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.1.2 HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.1.3 Microcode Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.2 Install, recover, and upgrade strategies . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.2.1 Refresh Install using the recovery CD. . . . . . . . . . . . . . . . . . . . . . . 119
6.2.2 Recovery install using the critical console data backup . . . . . . . . . 120
6.2.3 Upgrade install using the save upgrade data . . . . . . . . . . . . . . . . . 121

Chapter 7. Secure remote GUI access to the HMC . . . . . . . . . . . . . . . . . 125

7.1 System Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.1.1 Configuration steps to set up secure system manager server . . . . 127
7.1.2 Certificate Authority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
7.1.3 Server Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
7.1.4 Overview and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
7.1.5 Object Manager Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7.2 Remote client setup on a Windows system. . . . . . . . . . . . . . . . . . . . . . . 141
7.2.1 Install a remote client on a Windows system . . . . . . . . . . . . . . . . . 142
7.2.2 Uninstall a remote client from a Windows system. . . . . . . . . . . . . . 143
7.2.3 Install remote client security on a Windows system . . . . . . . . . . . . 143
7.2.4 Uninstall remote client security from a Windows system . . . . . . . . 145
7.3 Remote client setup on a Linux system. . . . . . . . . . . . . . . . . . . . . . . . . . 145
7.3.1 Install a remote client on a Linux system . . . . . . . . . . . . . . . . . . . . 146
7.3.2 Uninstall a remote client from a Linux system. . . . . . . . . . . . . . . . . 147
7.3.3 Install remote client security on a Linux system . . . . . . . . . . . . . . . 147
7.3.4 Uninstall remote client security from a Linux system . . . . . . . . . . . 148
7.4 Remote access to the HMC graphical user interface . . . . . . . . . . . . . . . 148

Contents v
 7.4.1 Using the remote client on Windows systems. . . . . . . . . . . . . . . . . 149
7.4.2 Using the remote client on AIX systems . . . . . . . . . . . . . . . . . . . . . 151

Chapter 8. Secure networking in a partitioned environment . . . . . . . . . 155

8.1 Networking in a partitioned environment . . . . . . . . . . . . . . . . . . . . . . . . . 156
8.2 Network paths in a partitioned environment . . . . . . . . . . . . . . . . . . . . . . 157
8.2.1 HMC to partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
8.2.2 Administrative workstation to HMC . . . . . . . . . . . . . . . . . . . . . . . . . 159
8.2.3 Administrative workstation to partition. . . . . . . . . . . . . . . . . . . . . . . 161
8.2.4 HMC access to the enterprise network . . . . . . . . . . . . . . . . . . . . . . 162
8.3 Providing security to the HMC and partitions . . . . . . . . . . . . . . . . . . . . . 163
8.3.1 Securing the HMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
8.3.2 Separating partitions from the others . . . . . . . . . . . . . . . . . . . . . . . 165
8.4 A sample implementation of port filtering rules . . . . . . . . . . . . . . . . . . . . 167
8.4.1 Between the HMC and partitions . . . . . . . . . . . . . . . . . . . . . . . . . . 168
8.4.2 Between the administrative workstation and HMC . . . . . . . . . . . . . 170
8.4.3 Between the administrative workstation and partitions . . . . . . . . . . 172
8.5 Service Agent and security concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
8.5.1 Firewall and Service Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Chapter 9. HMC command line interface . . . . . . . . . . . . . . . . . . . . . . . . . 175

9.1 Secure remote connection to the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . 176
9.1.1 Setting up OpenSSH on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
9.2 Syntax and common HMC command line flags . . . . . . . . . . . . . . . . . . . 180
9.2.1 The -m flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
9.2.2 The -r flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
9.2.3 The -n flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
9.2.4 The -o flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
9.2.5 The -p flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.2.6 The -f flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.2.7 The -F flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.2.8 The --help flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
9.3 HMC commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
9.3.1 Commands to manage HMC itself . . . . . . . . . . . . . . . . . . . . . . . . . 184
9.3.2 Commands to manage users on the HMC . . . . . . . . . . . . . . . . . . . 191
9.3.3 Commands for CUoD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
9.3.4 Commands to manage system configuration . . . . . . . . . . . . . . . . . 195
9.3.5 Commands to back up and restore partition profile data . . . . . . . . 203
9.3.6 Commands to manage hardware resources . . . . . . . . . . . . . . . . . . 205
9.3.7 Commands for virtual terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
9.3.8 Commands used in recovery situations . . . . . . . . . . . . . . . . . . . . . 211
9.3.9 Commands used for other purposes. . . . . . . . . . . . . . . . . . . . . . . . 212

Chapter 10. Advanced HMC command examples . . . . . . . . . . . . . . . . . . 217

vi Effective System Management Using the IBM Hardware Management Console for pSeries
10.1 Frequently asked questions and HMC commands . . . . . . . . . . . . . . . . 218
10.1.1 What is the managed system name? . . . . . . . . . . . . . . . . . . . . . . 218
10.1.2 What is my managed system’s MT-MDL*S/N? . . . . . . . . . . . . . . . 219
10.1.3 What is my frame name? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
10.1.4 Is my managed system CUoD-capable?. . . . . . . . . . . . . . . . . . . . 219
10.1.5 How many affinity partitions are defined or running? . . . . . . . . . . 220
10.1.6 Which partitions are DLPAR capable? . . . . . . . . . . . . . . . . . . . . . 220
10.1.7 How many processors are allocated to each partition? . . . . . . . . 221
10.1.8 How many processors are free? . . . . . . . . . . . . . . . . . . . . . . . . . . 222
10.1.9 How much memory is allocated to each partition now? . . . . . . . . 222
10.1.10 How much memory is free now? . . . . . . . . . . . . . . . . . . . . . . . . . 223
10.1.11 Display empty I/O slots allocation status. . . . . . . . . . . . . . . . . . . 223
10.1.12 Which partition currently has CD/DVD assigned to it? . . . . . . . . 224
10.1.13 Is the system attention LED light on? . . . . . . . . . . . . . . . . . . . . . 224
10.1.14 How can I turn off the system attention LED?. . . . . . . . . . . . . . . 225
10.1.15 When was the critical console data backup performed? . . . . . . . 225
10.1.16 When did I do the profile data backup?. . . . . . . . . . . . . . . . . . . . 225
10.1.17 Display the operator panel while managed system boots . . . . . . 226
10.1.18 Display the operator panel when the partition is activated . . . . . 226
10.2 Basic command line samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
10.2.1 Power on the managed system. . . . . . . . . . . . . . . . . . . . . . . . . . . 227
10.2.2 Activate a partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
10.2.3 Shut down the operating system in a partition . . . . . . . . . . . . . . . 230
10.2.4 Reboot the operating system in a partition . . . . . . . . . . . . . . . . . . 230
10.2.5 Reset the operating system in a partition . . . . . . . . . . . . . . . . . . . 231
10.2.6 Hard reset a partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
10.2.7 Power off the managed system. . . . . . . . . . . . . . . . . . . . . . . . . . . 232
10.2.8 Create a partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
10.2.9 Create a partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
10.2.10 Automate adding users to HMC . . . . . . . . . . . . . . . . . . . . . . . . . 234
10.2.11 Record all partition/profile configurations for printing . . . . . . . . . 237
10.2.12 Record current HMC information before upgrade . . . . . . . . . . . . 244

Chapter 11. Service functions on the HMC. . . . . . . . . . . . . . . . . . . . . . . . 247

11.1 Service Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
11.2 Inventory Scout Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
11.2.1 Inventory Scout Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
11.2.2 Collect VPD Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
11.2.3 Restart Inventory Scout Daemon . . . . . . . . . . . . . . . . . . . . . . . . . 253
11.3 Service Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
11.3.1 Service Agent UI - registration/customization . . . . . . . . . . . . . . . . 257
11.3.2 Stop Service Agent UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
11.3.3 Change Service Agent mode (server/client) . . . . . . . . . . . . . . . . . 257

Contents vii
 11.3.4 Start Service Agent processes . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
11.3.5 Stop Service Agent processes . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
11.4 Service Focal Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
11.4.1 Service Focal Point Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
11.4.2 Select Serviceable Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
11.4.3 Hardware Service Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
11.5 Microcode Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Chapter 12. Sample Service Agent configurations on the HMC . . . . . . . 281

12.1 Configuring the Service Agent dialer. . . . . . . . . . . . . . . . . . . . . . . . . . . 282
12.2 Testing the dialer settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
12.3 Registering your HMC with IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
12.4 Sending VPD to IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
12.5 Define Service Agent clients on a gateway server . . . . . . . . . . . . . . . . 292

Appendix A. Configuring asynchronous adapters on the HMC . . . . . . . 295

Hardware setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Add an 8-port asynchronous adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Add a 128-port asynchronous adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Set the RAN node number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Configure Serial Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
8-port asynchronous adapter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 299
128-port asynchronous adapter configuration . . . . . . . . . . . . . . . . . . . . . . . . 301
Configuring RS-422 ports on an 8-port asynchronous adapter. . . . . . . . . 305
Verifying asynchronous adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Adapter status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Ports status (8-port asynchronous adapter) . . . . . . . . . . . . . . . . . . . . . . . 306
RANs status (128-port asynchronous adapter) . . . . . . . . . . . . . . . . . . . . . 308
Removing an asynchronous adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Appendix B. Recommended network configuration in a partitioned

environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Appropriate network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Trouble-free network planning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Diagnosing communication problems between the HMC and partitions . . . . 314

Appendix C. A brief introduction to VLAN . . . . . . . . . . . . . . . . . . . . . . . . 317

Historical networking review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
What is a switch? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
What is VLAN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Several VLAN technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Port-based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Layer 2 VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Policy-based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

viii Effective System Management Using the IBM Hardware Management Console for pSeries
 802.1Q VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
AIX VLAN support (802.1Q VLAN interface) . . . . . . . . . . . . . . . . . . . . . . . . . 325
Vendor-specific VLAN technologies (Cisco). . . . . . . . . . . . . . . . . . . . . . . . . . 326
Private VLAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
VLAN ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
IBM Redpapers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
pSeries hardware publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
AIX official publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
CSM for AIX official publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
CSM for Linux official publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Contents ix
x Effective System Management Using the IBM Hardware Management Console for pSeries
Figures

1-1 7135-C02 rear view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1-2 Communication between the HMC and the service processor . . . . . . . . 5
1-3 pSeries 670 and pSeries 690 CEC rear view (primary I/O book) . . . . . . 8
1-4 Rear view of pSeries 655 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-5 Rear view of pSeries 650 Model 6M2 . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1-6 Views of pSeries 630 models 6C4 and 6E4. . . . . . . . . . . . . . . . . . . . . . 12
1-7 Views of pSeries 615 models 6C3 and 6E3. . . . . . . . . . . . . . . . . . . . . . 13
1-8 RS-422 serial cable connection from HMC to 7040-W42 system rack . 15
1-9 HMC software architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1-10 Serial connectivity option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1-11 Remote connectivity option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1-12 8-port fanout box with a connector cable . . . . . . . . . . . . . . . . . . . . . . . . 25
1-13 Connecting with an 8-port asynchronous adapter . . . . . . . . . . . . . . . . . 26
1-14 Connecting with a 128-port asynchronous adapter . . . . . . . . . . . . . . . . 27
1-15 128-port asynchronous adapter card edge . . . . . . . . . . . . . . . . . . . . . . 27
1-16 Enhanced Remote Asynchronous Node 16-port (FC 8137) . . . . . . . . . 28
1-17 Distance solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2-1 HMC graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2-2 Reload button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2-3 Details, Tree, Tree-Details buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2-4 Detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2-5 Tree view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2-6 Tree-Details view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2-7 Status bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2-8 HMC application folders in the Navigation area . . . . . . . . . . . . . . . . . . . 40
2-9 Object hierarchy for the Server Management application . . . . . . . . . . . 42
2-10 Server Management (one managed system). . . . . . . . . . . . . . . . . . . . . 43
2-11 Server Management (three pSeries 655 servers) . . . . . . . . . . . . . . . . . 44
2-12 Server Management (four managed systems). . . . . . . . . . . . . . . . . . . . 44
2-13 Server Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2-14 Virtual terminal window on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2-15 Virtual terminal window on the remote WebSM client . . . . . . . . . . . . . . 51
3-1 System properties: Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3-2 System properties: Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3-3 System properties: Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3-4 System properties: I/O Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3-5 System properties: Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3-6 Power On Modes panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

© Copyright IBM Corp. 2003. All rights reserved. xi

 3-7 Activate a partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3-8 Partition activation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3-9 Read Boot Error Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3-10 Operating System shutdown or reset. . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3-11 Operating System shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3-12 Operating system reset options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3-13 Hardware Management Console operator panel codes . . . . . . . . . . . . 73
4-1 HMC Management, Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4-2 Adding a new user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4-3 System Configuration application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4-4 Date/Time Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4-5 View Console Events logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-6 Network Configuration: IP Address tab . . . . . . . . . . . . . . . . . . . . . . . . . 84
4-7 Network Configuration: Name Services tab . . . . . . . . . . . . . . . . . . . . . . 86
4-8 Network Configuration: Hosts tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4-9 Host Entries window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-10 Network Configuration: Routing tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4-11 Routing Entries window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4-12 Network Configuration: Device Attributes tab . . . . . . . . . . . . . . . . . . . . 91
4-13 Ping Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4-14 Customize Scheduled Operations window . . . . . . . . . . . . . . . . . . . . . . 93
4-15 Set up a Scheduled Operation: Date and time tab . . . . . . . . . . . . . . . . 94
4-16 Set up a Scheduled Operation: Repeat tab . . . . . . . . . . . . . . . . . . . . . . 95
4-17 Remote Execution Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4-18 Enable Remote Virtual Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4-19 Change Locale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5-1 Profile Data submenus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5-2 Four partition data locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5-3 Profile Data Backup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5-4 Profile Data Restore window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5-5 Profile Data Remove window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
6-1 Software Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6-2 Software Maintenance: Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6-3 Software Maintenance: HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6-4 Backup Critical Console Data (insert DVD-RAM media) . . . . . . . . . . . 113
6-5 Save Upgrade Data (Hard drive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6-6 Save Upgrade Data (warning) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6-7 Install Corrective Service window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6-8 Format Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6-9 Software Maintenance: Microcode Updates . . . . . . . . . . . . . . . . . . . . 117
6-10 Install/Recovery or Upgrade selection . . . . . . . . . . . . . . . . . . . . . . . . . 119
7-1 System Manager Security folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7-2 Warning window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

xii Effective System Management Using the IBM Hardware Management Console for pSeries
7-3 Certificate Authority (after being configured) . . . . . . . . . . . . . . . . . . . . 129
7-4 Define Internal Certificate Authority wizard . . . . . . . . . . . . . . . . . . . . . 130
7-5 Organization name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7-6 Certificate expiration date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
7-7 Entering password for the CA key ring file . . . . . . . . . . . . . . . . . . . . . . 131
7-8 CA configured message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7-9 Certificate Authority Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7-10 Entering certificate authority password . . . . . . . . . . . . . . . . . . . . . . . . 133
7-11 Generate Servers’ Private Key Ring Files . . . . . . . . . . . . . . . . . . . . . . 133
7-12 Copy CA Public Key to Diskette. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
7-13 Server Security (after being configured) . . . . . . . . . . . . . . . . . . . . . . . 136
7-14 Server Security Properties (Server Certificate) . . . . . . . . . . . . . . . . . . 137
7-15 Install Private Key Ring file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7-16 Configure System Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . 139
7-17 Overview and Status (after being configured) . . . . . . . . . . . . . . . . . . . 139
7-18 Object Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7-19 Configure Object Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7-20 Remote client install image download . . . . . . . . . . . . . . . . . . . . . . . . . 142
7-21 Remote client security install image download . . . . . . . . . . . . . . . . . . 144
7-22 Web-based Sysyem Manager Windows client Log On dialog box . . . 149
7-23 File Chooser dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
7-24 Web-based System Manager Windows client managing the HMC . . . 151
7-25 The locked keypad icon (SSL connection). . . . . . . . . . . . . . . . . . . . . . 151
7-26 Web-based System Manager on AIX 5L Version 5.2 . . . . . . . . . . . . . 152
7-27 Add a host dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
7-28 Remote HMC is shown in the Navigation Area . . . . . . . . . . . . . . . . . . 153
7-29 Managing HMC from the Web-based System Manager on AIX . . . . . 154
8-1 Network paths in a partitioned environment. . . . . . . . . . . . . . . . . . . . . 157
8-2 Possible attacks from compromised partitions or rogue users . . . . . . 165
8-3 Multiple security zones for partitions . . . . . . . . . . . . . . . . . . . . . . . . . . 166
8-4 Primary network interface must be IP-reachable from all partitions. . . 166
8-5 Sample firewall placement (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
8-6 Sample firewall placement (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11-1 Service Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
11-2 Error reporting and consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
11-3 Inventory Scout Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
11-4 Inventory Scout Configuration Assistant (select managed system) . . . 251
11-5 Inventory Scout Configuration Assistant (select partitions) . . . . . . . . . 252
11-6 Initiate Inventory Scout Data Collection . . . . . . . . . . . . . . . . . . . . . . . . 253
11-7 Inventory Scout: VPD Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
11-8 Service Agent on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
11-9 Service Agent on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
11-10 Service Agent client/server configuration on multiple HMCs . . . . . . . . 258

Figures xiii
 11-11 Change Service Agent mode (server/client) . . . . . . . . . . . . . . . . . . . . 259
11-12 Service Focal Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
11-13 Service Focal Point Settings: CEC Call Home. . . . . . . . . . . . . . . . . . . 263
11-14 Service Focal Point Settings: Surveillance Setup . . . . . . . . . . . . . . . . 264
11-15 Service Focal Point Settings: Surveillance Notification . . . . . . . . . . . . 265
11-16 Select Serviceable Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
11-17 Serviceable Event Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
11-18 Serviceable event details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
11-19 Hardware Service Functions overview. . . . . . . . . . . . . . . . . . . . . . . . . 269
11-20 FRU LED Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
11-21 FRU LED Management: manual changes . . . . . . . . . . . . . . . . . . . . . . 271
11-22 Umber LED flashing in a PCI slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
11-23 Mechanism of the Microcode Updates. . . . . . . . . . . . . . . . . . . . . . . . . 274
11-24 Download and Apply Microcode Updates . . . . . . . . . . . . . . . . . . . . . . 275
11-25 Select Repository Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
11-26 Microcode License Agreement Message . . . . . . . . . . . . . . . . . . . . . . . 276
11-27 Microcode Survey Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
11-28 Microcode Installation - Device Information . . . . . . . . . . . . . . . . . . . . . 278
11-29 Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
11-30 Microcode Updates Finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
12-1 Service Agent – Enter the Password . . . . . . . . . . . . . . . . . . . . . . . . . . 282
12-2 Service Agent - blank dialer configuration . . . . . . . . . . . . . . . . . . . . . . 283
12-3 Service Agent - select dialer location . . . . . . . . . . . . . . . . . . . . . . . . . . 284
12-4 Service Agent: configured dialer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
12-5 Service Agent: testing the dialer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
12-6 Registration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
12-7 Service Agent: registering HMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
12-8 Service Agent Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
12-9 Service Agent: VPD tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
12-10 Service Agent: VPD collection status. . . . . . . . . . . . . . . . . . . . . . . . . . 291
12-11 Service Agent - VPD Collection Results . . . . . . . . . . . . . . . . . . . . . . . 291
12-12 Service Agent: VPD transmittal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
12-13 Network, Add, Child, Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
12-14 Defining an Service Agent client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
A-1 RAN front view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
A-2 Configure Serial Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
A-3 configAsync window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
A-4 Specify number of adapters and adapter type . . . . . . . . . . . . . . . . . . . 300
A-5 Specify total number of ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
A-6 Specify number of RANs and wiring scheme. . . . . . . . . . . . . . . . . . . . 303
A-7 Specify bit rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
A-8 Adapter status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
A-9 Port status for 8-port asynchronous adapter . . . . . . . . . . . . . . . . . . . . 307

xiv Effective System Management Using the IBM Hardware Management Console for pSeries
A-10 Successful microcode download to RAN . . . . . . . . . . . . . . . . . . . . . . . 308
C-1 OSI seven-layered networking reference model and TCP/IP model . . 318
C-2 VLAN concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
C-3 Port-based VLAN concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
C-4 Overlapping port definition based on the port-based VLAN. . . . . . . . . 322
C-5 VLAN-tagged Ethernet frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
C-6 802.1Q VLAN concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
C-7 Private VLAN concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Figures xv
xvi Effective System Management Using the IBM Hardware Management Console for pSeries
Tables

1-1 Supported managed systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1-2 Maximum number of processors, memory size, and partitions . . . . . . . . 6
1-3 Description of components in the primary I/O book . . . . . . . . . . . . . . . . . 8
1-4 Previous Hardware Management Console feature code or MT-MDL . . 23
2-1 Elements in the HMC graphical user interface. . . . . . . . . . . . . . . . . . . . 33
2-2 HMC application folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3-1 Properties of the managed system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3-2 Operating states of managed systems . . . . . . . . . . . . . . . . . . . . . . . . . 64
3-3 Operating states of partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4-1 Tasks in the System Configuration application . . . . . . . . . . . . . . . . . . . 81
6-1 Applications in the Software Maintenance folder . . . . . . . . . . . . . . . . . 108
7-1 System Manager Security applications . . . . . . . . . . . . . . . . . . . . . . . . 126
8-1 Network paths in a partitioned environment. . . . . . . . . . . . . . . . . . . . . 157
8-2 Required TCP and UDP ports (HMC to partitions) . . . . . . . . . . . . . . . 158
8-3 Required TCP ports (Administrative workstation to HMC) . . . . . . . . . . 160
8-4 TCP ports (an administrative workstation to a partition) . . . . . . . . . . . 161
9-1 Command groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
9-2 Values for affinity_capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
9-3 Values for cec_capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
9-4 Values for runtime_capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
9-5 Values for mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
9-6 Values for BootMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
11-1 Service Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
11-2 Inventory Scout Services tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
11-3 Service Agent tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
11-4 Service Focal Point tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
B-1 Authentication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

© Copyright IBM Corp. 2003. All rights reserved. xvii

xviii Effective System Management Using the IBM Hardware Management Console for pSeries
Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM 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:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions
are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES
THIS PUBLICATION "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. IBM 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 non-IBM Web sites 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 IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.

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.

COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to IBM for the purposes of
developing, using, marketing, or distributing application programs conforming to IBM's application
programming interfaces.

© Copyright IBM Corp. 2003. All rights reserved. xix

Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
AIX® Electronic Service Agent™ Redbooks (logo) ™
AIX 5L™ ibm.com® Redbooks™
DB2 Universal Database™ IBM® RS/6000®
DB2® POWER4+™ SP™
^™ POWER4™
™ pSeries™

The following terms are trademarks of other companies:

ActionMedia, LANDesk, MMX, Pentium and ProShare 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.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure
Electronic Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.

xx Effective System Management Using the IBM Hardware Management Console for pSeries
Preface

The IBM Hardware Management Console for pSeries (hereafter referred to as

HMC) is a tool used for administering and managing IBM Eserver pSeries™
servers. It was first announced in late 2001 with the IBM Eserver pSeries 690
Model 681, the first partitioning-capable pSeries server model, then has been
supporting the other partitioning-capable pSeries server models in conjunction
with several software release level updates.

The major function provided by the HMC is partitioning management, which is

well covered by several publications, including the sibling redbook The Complete
Partitioning Guide for IBM Eserver pSeries Servers, SG24-7039. This IBM
Redbook, designed to be used as a deskside reference for systems
administrators who manage partitioning-capable pSeries servers using the HMC,
is meant to complement other publications by covering the following topics:
򐂰 Configuring the HMC
򐂰 Managing software levels on the HMC
򐂰 Secure remote GUI access to the HMC
򐂰 Secure networking in a partitioned environment
򐂰 Service functions on the HMC

In addition, this book covers the basic usage of the HMC graphical user interface.
New HMC commands, available with the HMC software Release 3, Version 2,
are fully exploited in Chapter 9, “HMC command line interface” and Chapter 10,
“Advanced HMC command examples”.

The team that wrote this redbook

This book was produced by a team of specialists from around the world working
at the International Technical Support Organization, Austin Center.

Keigo Matsubara is an advisory IT specialist at the International Technical

Support Organization (ITSO), Austin Center. Before joining the ITSO, he worked
in the System and Web Solution Center in Japan as a Field Technical Support
Specialist (FTSS) for pSeries. He has worked for IBM for 11 years.

Matt Robbins is a pSeries Technical Sales Specialist in Dallas, Texas. He has

more than eight years of experience working with pSeries systems and AIX®. His
areas of expertise include UNIX, TCP/IP, and designing e-business solutions for

© Copyright IBM Corp. 2003. All rights reserved. xxi

 Internet security and Web traffic. He attended the University of North Texas as a
student of computer science.

Ron Barker is a Consulting IT Specialist for pSeries Advanced Technical

Support in the Americas. He has 16 years of experience in AIX and RISC-based
systems. He has worked at IBM for 20 years. His areas of expertise include
mid-range and high-end pSeries hardware, logical partitioning, AIX systems
management, and AIX Workload Manager.

Theeraphong Thitayanun is a Certified Consulting IT Specialist for IBM

Thailand. His main responsibility is to provide billable services and support in all
areas of high-end pSeries products. His areas of expertise include PSSP,
HACMP, and DB2® Universal Database™. He holds a Bachelors degree in
Computer Engineering from Chulalongkorn University and, as a Monbusho
student, a Masters degree in Information Technology from Nagoya Institute of
Technology, Japan.

Thanks to the following people for their contributions to this project:

International Technical Support Organization, Austin Center

Scott Vetter and Betsy Thaggard

IBM Austin
Bob Minns, Andy McLaughlin, Bob Foster, Christine Trinh, Christine Wang,
Christopher Chan, Dave Willoughby, Eric Marshall, Stephanie Jensen, Minh
Nguyen, Quan Wang, Richard Cutler, Trish Pierce, Truc Nguyen, and Walter Lipp

IBM Endicott
Scott Nettleship and Lenny Nichols

IBM Japan
Tomoyuki Niijima and Yuan Zong

IBM Poughkeepsie
Michael Schmidt and Anthony Pioli

IBM U.K.
Dave Williams

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook
dealing with specific products or solutions, while getting hands-on experience
with leading-edge technologies. You will team with IBM technical professionals,
Business Partners and/or customers.

xxii Effective System Management Using the IBM Hardware Management Console for pSeries
 Your efforts will help increase product acceptance and customer satisfaction. As
a bonus, you will develop a network of contacts in IBM development labs, and
increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and
apply online at:
ibm.com/redbooks/residencies.html

Comments welcome
Your comments are important to us!

We want our Redbooks™ to be as helpful as possible. Send us your comments

about this or other Redbooks in one of the following ways:
򐂰 Use the online Contact us review redbook form found at:
ibm.com/redbooks
򐂰 Send your comments in an e-mail to:
[email protected]
򐂰 Mail your comments to:
IBM® Corporation, International Technical Support Organization
Dept. JN9B Building 003 Internal Zip 2834
11400 Burnet Road
Austin, Texas 78758-3493

Preface xxiii
xxiv Effective System Management Using the IBM Hardware Management Console for pSeries
 1

Chapter 1. Introduction to the HMC

This chapter introduce the IBM Hardware Management Console for pSeries by
providing the following sections:
򐂰 “What is the HMC?” on page 2
򐂰 “Supported managed systems” on page 6
򐂰 “HMC architecture” on page 16
򐂰 “HMC connectivity” on page 18
򐂰 “HMC order information” on page 23

For the detailed information about the HMC, refer to the following publications:
򐂰 IBM Hardware Management Console for pSeries Maintenance Guide,
SA38-0603
򐂰 IBM Hardware Management Console for pSeries Installation and Operations
Guide, SA38-0590

You can access the soft copy of these publications, by accessing the IBM
Eserver pSeries Information Center, found at:
http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/index.htm

Click Hardware documentation → Hardware Management Console for

pSeries.

© Copyright IBM Corp. 2003. All rights reserved. 1

1.1 What is the HMC?
The HMC is a dedicated desktop PC workstation that provides several functions
for configuring and operating pSeries servers functioning either partitioned or in
the Full System Partition, using the graphical user interface1(GUI) or command
line interface2 (CLI). The functions provided by HMC include:
򐂰 Logical partitioning management
The HMC provides a set of tasks that are necessary to manage logical
partitions. These tasks include:
– Starting, stopping, resetting, and shutting down a partition.
We explain these tasks in sections 3.3, “Activate partitions” on page 65
through 3.5, “Reset the operating system in a partition” on page 70.
– Opening a virtual console for each partition or connected pSeries server
system.
We explain this task in sections 2.5, “Virtual terminal window” on page 49
through 3.5, “Reset the operating system in a partition” on page 70.
– Creating partition profiles that define the processor, memory, and I/O
resources allocated to an individual partition.
This book does not contain detailed information about these tasks except
for the advanced command line interface examples explained in
Chapter 10, “Advanced HMC command examples” on page 217. Refer to
these publications for this subject:
• IBM Hardware Management Console for pSeries Installation and
Operations Guide, SA38-0590
• The Complete Partitioning Guide for IBM Eserver pSeries Servers,
SG24-7039
– Performing DLPAR operations that dynamically change the resource
allocation (such as processor, memory, and I/O) for the specified partition.
This task is not also covered by this book. Refer to the publications listed
above for this subject:
򐂰 Displaying system resources and status.
We explain these tasks in 3.1, “Viewing properties of the managed system” on
page 56.
򐂰 Booting, starting, and stopping the connected pSeries server systems.
We explain these tasks in 3.2, “Power on the managed system” on page 61.

1
See Chapter 2, “HMC graphical user interface” on page 31.
2 See Chapter 9, “HMC command line interface” on page 175.

2 Effective System Management Using the IBM Hardware Management Console for pSeries
 Note: A pSeries server managed by HMC is also referred to as a managed
system.

򐂰 Configuring the HMC itself

We explain these tasks in 4.2, “HMC Maintenance” on page 80.
򐂰 Managing the HMC software level
We explain these tasks in Chapter 6, “Managing software levels on the HMC”
on page 107.
򐂰 A service focal point that gives you tools for problem determination and
service support such as call-home and error log notification through an
analog phone line
We explain these tasks in Chapter 11, “Service functions on the HMC” on
page 247.

1.1.1 HMC at a glance

Figure 1-1 on page 4 shows the rear view of 7135-C02, which is the current
HMC. It features one DVD-RAM drive, one Ethernet port, two native serial ports,
six USB ports, as well as other ports.

Note: IBM may adopt newer PC hardware models to be used as the HMC in
the future.

Chapter 1. Introduction to the HMC 3

 Figure 1-1 7135-C02 rear view3

Numbers shown in Figure 1-1 represents the following connectors:

1. Power connector
2. Mouse connector
3. Serial connector (S2)
4. Parallel connector
5. Ethernet connector
6. Audio line in connector
7. PCI slots (three available)
8. AGP slot (not used)
9. Audio line out connector (not used)
10.Microphone connector (not used)
11.USB connectors
12.VGA monitor connector
13.Serial connector (S1)
3 Two USB connectors are located in the front.

4 Effective System Management Using the IBM Hardware Management Console for pSeries
14.USB connectors
15.Keyboard connector

The HMC provides two native serial ports. One serial port should be used to
attach a modem for the Service Agent. The second port can be used to attach a
server. If multiple servers are attached to the HMC, additional serial ports are
necessary. The ports can be provided by adding asynchronous adapters.4

The HMC also provides an Ethernet port to connect to partitions on its managed
systems. The network connection is mandatory for the support of the following
functions as well as the system management purpose on those partitions:
򐂰 Dynamic logical partitioning
򐂰 Service functions (for example, Microcode Updates and Service Focal Point)

Figure 1-2 illustrates a simple but typical network configuration in a partitioned

environment that is composed of an HMC and its managed system running two
partitions. We explain the technical detail of the network configuration in a
partitioned environment in Chapter 8, “Secure networking in a partitioned
environment” on page 155 and Appendix B, “Recommended network
configuration in a partitioned environment” on page 309.

IP Network

AIX 5.1 AIX 5.2 Unassigned

Resources

Partition 1 Partition 2

Boot Firmware / RTAS / Hypervisor

Non-Volatile RAM

Processors Service
Mem Regions Processor RS/232C
I/O Slots LPAR
Allocation HMC
Tables

Managed System
Figure 1-2 Communication between the HMC and the service processor

4 See 1.5.4, “Asynchronous serial adapter configurations” on page 25 for the detailed information.

Chapter 1. Introduction to the HMC 5

1.2 Supported managed systems
At the time of writing, the following IBM Eserver pSeries server models shown
in Table 1-1 can be managed by HMC.

Table 1-1 Supported managed systems

Official product model name Short product name MT-MDL Relevant section

IBM Eserver pSeries 690 Model 681 pSeries 690 7040-681 1.2.1, “pSeries 690
and pSeries 670” on
IBM Eserver pSeries 670 Model 671 pSeries 670 7040-671 page 7

IBM Eserver pSeries 655 pSeries 655 7039-651 1.2.2, “pSeries 655”
on page 9

IBM Eserver pSeries 650 Model 6M2 pSeries 650 Model 6M2 7038-6M2 1.2.3, “pSeries 650
Model 6M2” on
page 10

IBM Eserver pSeries 630 Model 6C4 pSeries 630 Model 6C4 7028-6C4 1.2.4, “pSeries 630
models 6C4 and
IBM Eserver pSeries 630 Model 6E4 pSeries 630 Model 6E4 7028-6E4 6E4” on page 11

IBM Eserver pSeries 615 Model 6C3 pSeries 615 Model 6C3 7029-6C3 1.2.5, “pSeries 615
models 6C3 and
IBM Eserver pSeries 615 Model 6E3 pSeries 615 Model 6E3 7029-6E3 6E3” on page 13

Note: Hereafter, short product names are used throughout this book.

The logical partitioning concept and required tasks are basically similar on these
partitioning-capable pSeries server models. However, there is a substantial
difference when assigning I/O resources to partitions depending on the models.
For the hardware model-specific information about the I/O resource assignment,
refer to the appropriate publications listed in the following sections.

The maximum number of partitions, which depends on the supported number of

processors, is shown in Table 1-2.

Table 1-2 Maximum number of processors, memory size, and partitions

Short product Maximum Maximum Maximum Maximum
name number of memory size number of I/O number of
processors in GB drawers partitions

pSeries 690 321 512 8 32

pSeries 670 16 256 3 16

6 Effective System Management Using the IBM Hardware Management Console for pSeries
 Short product Maximum Maximum Maximum Maximum
name number of memory size number of I/O number of
processors in GB drawers partitions

pSeries 655 8 32 1 2

pSeries 650 8 64 8 82
Model 6M2

pSeries 630 4 32 2 43
Model 6C4

pSeries 630 4 32 0 2
Model 6E4

1. The High Performance Computing (HPC) feature of pSeries 690 is equipped with
up to 16 processors.
2. Needs external disk subsystems for the boot disk.
3. When equipped with I/O drawers.

Note: pSeries 615 models 6C3 and 6E3 do not support partitioning.

1.2.1 pSeries 690 and pSeries 670

The high-end pSeries 690 and the mid-range pSeries 670 are both
partitioning-capable pSeries server models that share the same physical
component design. Several hardware components, Bulk Power Assembly (BPA),
Central Electronics Complex (CEC), media drawer, and I/O drawers, as well as
optional internal battery features (IBFs) are combined in one or two 7040-61R
system racks.5

The pSeries 690 and pSeries 670 are equipped with two HMC ports (HMC1 and
HMC2) in the primary I/O book, which is plugged into the rear of CEC, as shown
in Figure 1-3 on page 8.

5 The pSeries 690 supports up to two system racks, whereas the pSeries 670 supports only one.

Chapter 1. Introduction to the HMC 7

Figure 1-3 pSeries 670 and pSeries 690 CEC rear view (primary I/O book)

Table 1-3 explains numbers shown in Figure 1-3.

Table 1-3 Description of components in the primary I/O book

Number Description

1 Primary I/O book, GX slot 0 (U1.18-P1-H2)

4 I/O port 0 (A0) (U1.18-P1-H2/Q1)

5 I/O port 0 (A1) (U1.18-P1-H2/Q2)

6 Operator panel (U1.18-P1-H2/Q7)

7 BPC Y-cable connector1

8 I/O port 1 (B0) (U1.18-P1-H2/Q3)

9 I/O port 1 (B1) (U1.18-P1-H2/Q4)

10 Diskette Drive (U1.18-P1-H2/Q10)

8 Effective System Management Using the IBM Hardware Management Console for pSeries
 Number Description

11 HMC port 1 (U1.18-P1-H2/S3)

12 HMC port 2 (U1.18-P1-H2/S4)

13 Serial port 1 (U1.18-P1-H2/S1)

14 Serial port 2 (U1.18-P1-H2/S2)

15 SPCN 0 (manufacturing use only)

16 SPCN 1 (manufacturing use only)

17 Debug (manufacturing use only)

24 Indicator LEDs

26 Camming latches

1. The Y-cable that attaches to this connector, terminates at BPC-A connector

U1.35-P1-X4/Q10 and BPC-B connector U1.35-P2-X4/Q10.

For further detailed information about these models, refer to the following
publications:
򐂰 IBM Eserver pSeries 670 and pSeries 690 System Handbook, SG24-7040
򐂰 IBM Eserver pSeries 670 Service Guide, SA38-0615
򐂰 IBM Eserver pSeries 670 User’s Guide, SA38-0614
򐂰 IBM Eserver pSeries 670 Installation Guide, SA38-0613
򐂰 IBM Eserver pSeries 690 Service Guide, SA38-0589
򐂰 IBM Eserver pSeries 690 User’s Guide, SA38-0588
򐂰 IBM Eserver pSeries 690 Installation Guide, SA38-0587

1.2.2 pSeries 655

The mid-range pSeries 655 is a partitioning-capable pSeries server model. The
pSeries 655 is designed as a building block of clusters, especially for the
high-performance computing (HPC) area, therefore multiple pSeries 655 servers
can be accommodated in a single 7040-W42 system rack. The 7040-W42
system rack shares the same physical form factor with 7040-R61 used for
pSeries 670 or pSeries 690, but the BPA of 7040-W42 must be connected to
HMC using RS-422.6

The pSeries 655 is equipped with two HMC ports (HMC1 and HMC2) on the rear
side as shown in Figure 1-4 on page 23.

6
See 1.2.6, “RS-422 serial connection to the 7040-W42 system rack” on page 14 for the detailed
information about the RS-422 connection between the HMC and 7040-W42.

Chapter 1. Introduction to the HMC 9

 Note: The pSeries 655 has no native serial or parallel port.

PCI slots
Second processor subsystem 1 2 3 First processor subsystem

RIO connectors Ethernet Debug HMC connector 2

connectors connector
HMC connector 1

Figure 1-4 Rear view of pSeries 6557

For further detailed information about the pSeries 655, refer to the following
publications:
򐂰 IBM Eserver pSeries 655 Installation Guide, SA38-0616
򐂰 IBM Eserver pSeries 655 Service Guide, SA38-0618
򐂰 IBM Eserver pSeries 655 User’s Guide, SA38-0617

1.2.3 pSeries 650 Model 6M2

The mid-range pSeries 650 Model 6M2 is a partitioning-capable pSeries server
model. It is a rack mount server that can be accommodated in an industry
standard 19-inch rack.

The pSeries 650 Model 6M2 is equipped with two HMC ports (HMC1 and HMC2)
on the rear side as shown in Figure 1-5 on page 11.

7 Two pSeries 655 processor systems are contained in a single frame cage in a rack drawer position.

10 Effective System Management Using the IBM Hardware Management Console for pSeries
 PCI-X slots SCSI
GX slots

1 2 3 4 5 6 7 Rack 1 2
ETH Indicator

MOUSE
DEBUG
reserved reserved
OP PNL SER 2 SER 1 HMC 1

SPCN 1 SPCN 0 KBD SER 4 SER 3 HMC 2

Power Power
supply 1 supply 2
Fan 1 Fan 2

Figure 1-5 Rear view of pSeries 650 Model 6M2

For further detailed information about the pSeries 650 Model 6M2, refer to the
following technical white paper and publications:
򐂰 IBM Eserver pSeries 650 Model 6M2 Technical Overview and Introduction,
REDP0194, available at:
http://www.redbooks.ibm.com/redpapers/pdfs/redp0194.pdf
򐂰 IBM Eserver pSeries 650 Model 6M2 Installation Guide, SA38-0610
򐂰 IBM Eserver pSeries 650 Model 6M2 User’s Guide, SA38-0611
򐂰 IBM Eserver pSeries 650 Model 6M2 Service Guide, SA38-0612

1.2.4 pSeries 630 models 6C4 and 6E4

The low-end pSeries 630 models 6C4 and 6E4 are both partitioning-capable
pSeries server models. The pSeries 630 Model 6C4 is a rack mount server that
can be accommodated in an industry standard 19 inch rack, whereas the pSeries
630 Model 6E4 is a deskside-type server.

The pSeries 630 models 6C4 and 6E4 are equipped with two HMC ports (HMC1
and HMC2) on the rear side as shown in Figure 1-6 on page 12.

Chapter 1. Introduction to the HMC 11

 Processor card #1 Processor card cooling fan bays 1 and 2
Operator panel
Processor card #2 s
to r
Power supply #1 ica s
i nd tor Six PCI-X slots
ED ica
Power supply #2 ly L ind
p D
up LE 4-pack disk backplane and
rs pp
ly
we su disks
Front serial connector Po er
w
Po

Media bay #2

Media bay #1
Six PCI-X slots

Operator panel
PCI cooling fan bays 1 and 2
Media bay #1 Media bay #2
4-pack disk backplane and
disks

Keyboard and mouse ports

Serial ports 1, 2, and 3

Power supply LED indicators Power supply #2 Power supply #1

Ethernet ports Power

Parallel port
HMC port 1 supply #2
SPCN ports
HMC port 2 Power
Rack SPCN port supply #1
indicator blanks
HMC port 2
Six PCI-X slots Serial ports 1, 2, and 3 Ethernet ports HMC port 1 Parallel port
Keyboard and mouse ports
RIO ports
Model 6C4 Model 6E4
Figure 1-6 Views of pSeries 630 models 6C4 and 6E48

For further detailed information about the pSeries 630 models 6C4 and 6E4,
refer to the following technical white paper and publications:
򐂰 IBM Eserver pSeries 630 Models 6C4 and 6E4 Technical Overview and
Introduction, REDP0195, available at:
http://www.redbooks.ibm.com/redpapers/pdfs/redp0195.pdf
򐂰 IBM Eserver pSeries 630 Model 6C4 and 6E4 Installation Guide,
SA38-0605
򐂰 IBM Eserver pSeries 630 Model 6C4 and 6E4 User’s Guide, SA38-0606
򐂰 IBM Eserver pSeries 630 Model 6C4 and 6E4 Service Guide, SA38-0604

8 This figure shows the views of latest pSeries 630 models 6C4 and 6E4 (POWER4™+ system with six PCI-X slots).

12 Effective System Management Using the IBM Hardware Management Console for pSeries
1.2.5 pSeries 615 models 6C3 and 6E3
The low-end pSeries 615 models 6C3 and 6E3 are both non partitioning-capable
pSeries server models. The pSeries 615 Model 6C3 is a rack mount server that
can be accommodated in an industry standard 19-inch rack, whereas the
pSeries 615 Model 6E3 is a deskside-type server.

The pSeries 615 Model 6C3 can be used as a building block of the IBM cluster
product IBM Eserver Cluster 1600, so multiple pSeries 615 Model 6C3 servers
can be incorporated into the cluster, which is managed by Cluster Systems
Management (CSM).9

The pSeries 615 models 6C3 and 6E3 are equipped with two HMC ports (HMC1
and HMC2) on the rear side as shown in Figure 1-7.

Power supply LED indicators

Model 6C3 CSP and I/O ports card Model 6E3 Operator panel

!
Front view
Six PCI-X slots
Two slim line
Full height media bay media bays

#1

#2
#3

s Hot-swap disk drives

an
gf
olin
Co

Power supply #2 (default)

Hot-swap disk drives Power supply #1 (redundant option)
Operator panel Rear view
Full height media bay Power supply
Two slim line media bays connector #1

Front view Power supply

connector #2
(Base power
supply)
HMC port 1
HMC port 2
Operator panel Parallel port
Keyboard & Mouse
Serial port 3
Serial port 3 Test port (only MFG) 10/100 Ethernet
Serial port 2
Keyboard & Mouse Parallel port Serial port 2
10/100/1000 Ethernet Test port
Power supply
connector #2 Rack indicator (only MFG)
(Base power supply) Rear view Serial port 1

Power supply Six PCI-X slots

connector #1
HMC port 1 10/100 Ethernet Serial port 1
HMC port 2 10/100/1000 Ethernet Rack indicator

Figure 1-7 Views of pSeries 615 models 6C3 and 6E3

9
Refer to the publications listed in “CSM for AIX official publications” on page 335 for detailed
information about CSM.

Chapter 1. Introduction to the HMC 13

 If a pSeries 615 Model 6C3 or pSeries 615 Model 6E3 is managed by CSM, an
HMC must be attached to an HMC port of these models for power management.

For further detailed information about the pSeries 630 models 6C4 and 6E4,
refer to the following technical white paper and publications:
򐂰 IBM Eserver pSeries 615 Models 6C3 and 6E3 Technical Overview and
Introduction, REDP0160, available at:
http://www.redbooks.ibm.com/redpapers/pdfs/redp0160.pdf
򐂰 IBM Eserver pSeries 615 Model 6C3 and 6E3 Installation Guide,
SA38-0628
򐂰 IBM Eserver pSeries 615 Model 6C3 and 6E3 User’s Guide, SA38-0630
򐂰 IBM Eserver pSeries 615 Model 6C3 and 6E3 Service Guide, SA38-0629

1.2.6 RS-422 serial connection to the 7040-W42 system rack

If the 7040-W42 system rack is used to accommodate hardware components,
such as pSeries 655 servers, the BPA of the rack must be connected to an HMC
using RS-422, as shown in Figure 1-8 on page 15.

14 Effective System Management Using the IBM Hardware Management Console for pSeries
 BPC (A side) cable connector BPC (B side) cable connector BPC cable route
(front of rack) (rear of rack) at rear of rack

BPC cable route

at front of rack

Processor or
I/O subsystems

Processor or
I/O subsystems

8-port connector box

RS-422
cable

Figure 1-8 RS-422 serial cable connection from HMC to 7040-W42 system rack10

A BPA contains two Bulk Power Controllers (BPCs) in its front and rear sides. An
RS-422 connection is required for each BPC; thus two RS-422 connections are
needed per 7040-W42 system rack.

10 The RS-422 cable shown in Figure 1-8 is connected to the 8-port asynchronous adapter of the HMC.

Chapter 1. Introduction to the HMC 15

 Note: If the 8-port asynchronous adapter (FC 2943) is used to connect the
HMC to the BPCs of 7040-W42, the corresponding serial ports must be
explicitly set to the RS-422 mode (see Appendix , “Configuring RS-422 ports
on an 8-port asynchronous adapter” on page 305).

1.3 HMC architecture

The HMC provides a graphical user interface for configuring and operating single
or multiple managed systems. It consists of a 32-bit Intel-based desktop PC with
a DVD-RAM drive and running the Linux operating system. The application
environment, with a set of hardware management applications for configuration
and partitioning, is written in Java. The applications are based on the
object-oriented schema using the Common Information Model (CIM), an industry
standard sponsored by the Distributed Management Task Force (DMTF). A CIM
Object Manager acts as repository and database look-up for all managed
objects.

The DMTF Standards web site can be a good starting point to learn these
technologies, found at:
http://www.dmtf.org/standards/standard_cim.php

The graphical user interface is based on the AIX 5L™ Version 5.2 Web-based
System Manager, which allows the management integration of other HMCs or
pSeries systems running AIX 5L Version 5.1 and 5.2. Except for IBM customer
engineers and debugging purposes, the native Linux interfaces are hidden from
the user and are not accessible. No Linux skills are required to operate the HMC.
The graphical user interface can display dynamic events and static information
from pSeries machines running AIX as well as from partitions on any
partitioning-capable pSeries servers.

Figure 1-9 on page 17 shows an overview of the HMC software architecture.

򐂰 A user who logs in to the HMC from the local console is accessing the
application using the Web-based System Manager graphical user interface as
represented in the big upper arrow.
򐂰 The HMC communicates with the service processor on the managed system
using the serial communication.
򐂰 If configured, the Service Agent communicates with the modem using the
serial communication.
򐂰 The Resource Monitoring and Control (RMC) subsystem on the HMC
connects the RMC subsystem on remote nodes, such as partitions, over the
TCP/IP network (shown as A in Figure 1-9 on page 17).

16 Effective System Management Using the IBM Hardware Management Console for pSeries
򐂰 A remote user can access the HMC using either the ssh or rexec facility over
the TCP/IP network (shown as B).
򐂰 A user who logs in to the HMC from the local console can access to the
remote Web-based System Manager server on remote nodes, such as AIX
partitions over the TCP/IP network (shown as C).
򐂰 A user using the remote Web-based System Manager client can access the
HMC over the TCP/IP network (shown as D).

Further detailed information about the remote connection over the TCP/IP
network is provided in 8.1, “Networking in a partitioned environment” on
page 156.

Graphical User Interface

Remote WebSM server

C Remote WebSM clients

D

WebSM client HMC

WebSM server
Service Agent

CIM
Object
Manager

Resource managers
HMC commands
Communication
Interface
RMC sshd/rexecd

A B

Modem RMC on remote node ssh/rexec client Service Processor

Internal software components

Serial connection
TCP/IP connection

Figure 1-9 HMC software architecture overview11

11
The figure does not show all communication paths and software components. For example,
remote virtual terminal access is not shown to avoid unnecessary complexity.

Chapter 1. Introduction to the HMC 17

1.4 HMC connectivity
In this section, we explain several HMC connectivity configurations. We group
these configurations into two categories: 1.4.1, “Serial connectivity” on page 18
and 1.4.2, “Remote connectivity” on page 21.

Note: You should not confuse the managed system name with the host name.
Because multiple operating system instances can run concurrently on a single
partitioning-capable pSeries server, you cannot use the host name, which
usually depends on the IP address, to distinguish multiple partitioning-capable
pSeries servers. The managed system name is a label used for this purpose.

1.4.1 Serial connectivity

A managed system has to be connected by at least one HMC using a serial
connection. To connect a serial line between an HMC and a managed system,
use one of the serial ports on the HMC and one of two dedicated serial ports
(HMC1 and HMC2) on the managed system.

As long as at least one serial connection is configured, you can configure the
following serial connectivity options:
򐂰 Redundant HMC configuration
For redundancy of the system management control point, you can configure a
redundant HMC configuration, as shown in Figure 1-10 on page 19. In this
case, both serial ports have one HMC connected.
For further information about redundant HMC configuration, see “Redundant
HMC configuration consideration” on page 19.
򐂰 Multiple managed system configuration
To save space and to centralize multiple system management control points,
you can configure multiple managed systems using a single HMC, as shown
in Figure 1-10 on page 19. If more than two managed systems are connected
with one HMC, asynchronous adapters must be configured on the HMC.12
The information is considered as objects in the HMC applications. Because
the serial connection is relatively slow (19200 bps), the HMC applications run
slower as the number of objects increases.
The performance of the HMC applications are affected by three factors:
– Number of the managed systems
– Number of the equipped I/O devices on each managed system
– Number of defined partitions defined on each managed system
12 See 1.4.1, “Serial connectivity” on page 18 for the detailed information.

18 Effective System Management Using the IBM Hardware Management Console for pSeries
 Note: The HMC gathers all of the objects from managed systems on every
power cycle. Therefore if the connected multiple managed systems reboot at
the same time, it can take longer for HMC to discover all of the information
from the managed systems.

HMC1
Managed
System 1

HMC1
Managed
System 2
HMC 1 HMC1
Managed
HMC
HMC2 System 1
HMC 2
Managed
HMC1 System 3

Managed
HMC1 System 4

Redundant HMC Multiple Managed-

Configuration System Configuration

Figure 1-10 Serial connectivity option

Redundant HMC configuration consideration

In a redundant HMC configuration, both HMCs are fully active and accessible at
all times, enabling you to perform management tasks from either HMC at any
time. There is no primary or backup designation.

Because both HMCs can be used concurrently, you have to consider the
following points:
򐂰 Because authorized users can be defined independently for each HMC,
determine whether the users of one HMC should be authorized on the other.
If so, the user authorization must be set up separately on each HMC.

Chapter 1. Introduction to the HMC 19

 򐂰 Because both HMCs provide Service Focal Point and Service Agent
functions, connect a modem and phone line to only one of the HMCs and
enable its Service Agent. To prevent redundant service calls, do not enable
the Service Agent on both HMCs.
򐂰 Perform software maintenance separately on each HMC, at separate times,
so that there is no interruption in accessing HMC function. This allows one
HMC to run at the new fix level, while the other HMC can continue to run at
the previous fix level. However, the best practice is to upgrade both HMCs to
the same fix level as soon as possible.

The basic design of HMC eliminates the possible operation conflicts issued from
two HMCs in the redundant HMC configuration. A locking mechanism provided
by the service processor allows inter-operation in a parallel environment. This
allows an HMC to temporarily take exclusive control of the interface, effectively
locking out the other HMC. Usually, this locking is held only for the short duration
of time it takes to complete an operation, after which the interface is available for
further commands.

Both HMCs are automatically notified of any changes that occur in the managed
systems, so the results of commands issued by one HMC are visible in the other.
For example, if you choose to activate a partition from one HMC, you will observe
the partition going to the Starting and Running states on both HMCs.

The locking between HMCs does not prevent users from running commands that
might seem to be in conflict with each other. For example, if the user on one HMC
activates a partition, and a short time later a user on the other HMC selects to
power the system off, the system will power off. Effectively, any sequence of
commands that you can do from a single HMC is also permitted when it comes
from redundant HMCs. For this reason, it is important to consider carefully how to
use this redundant capability to avoid such conflicts. You might choose to use
them in a primary and backup role, even though the HMCs are not restricted in
that way. The interface locking between two HMCs is automatic, usually of short
duration, and most console operations wait for the lock to release without
requiring user intervention. However, if one HMC experiences a problem while in
the middle of an operation, it may be necessary to manually release the lock.13

Connect and disconnect managed systems

Because the HMC is not required for managed systems to properly function, you
can connect or disconnect them from the HMC without service interruption of
managed systems. For further details about connecting or disconnecting
managed systems to or from the HMC, see 2.4.1, “Connect and disconnect
managed systems” on page 45.

13 See “Release Console Lock” on page 48.

20 Effective System Management Using the IBM Hardware Management Console for pSeries
 Note: If your managed system is connected to only one HMC, you cannot
perform several administration tasks, such as partition management and
DLPAR operation, while the HMC is disconnected from the managed system.

1.4.2 Remote connectivity

Depending on what communication method or protocols are used, there are
several options in the remote connectivity of HMC, as illustrated in Figure 1-11 on
page 22. In this figure, we assume the following points:
򐂰 The dashed lines between HMCs and managed systems are serial
connections.
򐂰 The solid lines connecting HMCs and other systems are Ethernet
connections. These systems have appropriate TCP/IP configuration, so they
can communicate using various TCP/IP protocols supported by the HMC.
򐂰 We exclude the possible connection to the AIX systems managed by
Web-based System Manager from the HMC to avoid complexity in
Figure 1-11 on page 22. You can also manage these AIX systems from the
HMC, even if the AIX system is running in a partition.
򐂰 We assume that the HMC1 shown in Figure 1-11 on page 22 is a server ; all
connections are made to HMC1 from the other systems, and some operations
are executed on it, such as configuring a partition or powering on the
managed system.

Chapter 1. Introduction to the HMC 21

 Any TCP/IP 2
Capable
System

Serial
Connection Managed
HMC 1
System 1

1-B
Linux WebSM
1-A
Client

Serial
Connection Managed
HMC 2
System 2

1-C
Windows
WebSM Client

Figure 1-11 Remote connectivity option

Figure 1-11 shows two categories of remote connectivity options explained in the
following sections: remote access to the HMC graphical user interface, as shown
by 1-A, 1-B, and 1-C (using the dotted line), and the remote execution of
command line function, as shown by 2 (using the dotted line).

Remote access to the HMC graphical user interface

The HMC allows remote access to the graphical user interface from the
Web-based System Manager client installed on the following operating systems:
򐂰 AIX
򐂰 Linux14
򐂰 Windows

For installation and usage of the remote client, see 7.2, “Remote client setup on
a Windows system” on page 141 and 7.3, “Remote client setup on a Linux
system” on page 145.

14 Only the Linux operating system for the IA-32 architecture is supported.

22 Effective System Management Using the IBM Hardware Management Console for pSeries
 Remote execution of command line functions
The HMC provides a set of commands in order to be used for many management
tasks; however, those commands are only accessible from the remote system,
not from the HMC local console. This remote connectivity option is shown as 2 in
Figure 1-11 on page 22, and any TCP/IP-capable system that supports rexec or
ssh can use the remote execution of command line functions.

Note: We recommend that you use ssh instead of rexec, because the rexec
method transports a non-secure clear text copy of the password across the
network.

For further information about the command line interface on the HMC, see
Chapter 9, “HMC command line interface” on page 175.

1.5 HMC order information

In order to configure and administer a partitioning-capable pSeries server, you
must attach at least one IBM Hardware Management Console for pSeries (HMC)
to the system. Depending on the partitioning-capable pSeries server model, the
HMC is ordered as a feature code or a separate orderable product, as shown in
Table 1-4.

Note: Currently, only the 7315-C02 is orderable. The 7316 and 7315-C01 are
shown only for reference purposes.

Table 1-4 Previous Hardware Management Console feature code or MT-MDL

Short product name HMC FC or MT-MDL Note

pSeries 690 FC 7316 1

pSeries 670 FC 7316 1

pSeries 655 MT-MDL 7315-C01 1

pSeries 650 Model 6M2 MT-MDL 7315-C01 2

pSeries 630 Model 6C4 MT-MDL 7315-C01 2

pSeries 630 Model 6E4 MT-MDL 7315-C01 2

1. The HMC is required regardless of whether the system is partitioned or running in

the Full System Partition.
2. The HMC is required if the system is partitioned. If the system is running in the Full
System Partition, the HMC is not required.

Chapter 1. Introduction to the HMC 23

 To place an order of a new HMC (7315-C02), use the IBM Configurator for
e-business (e-config). The redbook IBM Eserver pSeries 670 and pSeries 690
System Handbook, SG24-7040, can be used as a good example of how to use
this application.

1.5.1 Supported number of managed systems and partitions

One HMC is capable of controlling multiple pSeries servers. As this publication is
being written, an HMC can control any of the following:
򐂰 12 pSeries 670 and pSeries 690 servers with 64 partitions
򐂰 16 pSeries 655 servers with up to 32 partitions
򐂰 16 pSeries 630 models 6C4 and 6E4 or pSeries 650 Model 6M2 servers with
up to 64 partitions
򐂰 16 pSeries servers and 64 partitions in a mixed server environment
A mixed server environment can contain a combined maximum of eight
pSeries 670 or pSeries 690 servers.

1.5.2 HMC software release numbering scheme

The latest HMC software release (program number 5639-N47) is preloaded on
the HMC upon product shipment.

Although many IBM software products follow the release numbering scheme
known as V.R.M.F (version, release, maintenance, and fix), the current HMC
uses a different scheme, represented as R.V.M.F (release, version, maintenance,
and fix). Therefore, the latest release available at the time of writing this book is
represented as Release 3, Version 2.2, not Version 3, Release 2.2.

1.5.3 Ethernet adapter configuration

The HMC can be equipped with an optional Ethernet adapter in addition to the
built-in Ethernet port. To use the second Ethernet port, the following feature must
be configured:
򐂰 10/100 Mbps Ethernet PCI adapter II (FC 4962)

The second Ethernet port typically is used when the HMC is incorporated into a
cluster complex that is managed by CSM.

24 Effective System Management Using the IBM Hardware Management Console for pSeries
Random documents with unrelated
content Scribd suggests to you:
weight which no language can describe. I felt that I no longer
breathed the air of liberty; that slavery was spreading her Upas
branches athwart my sky also. The convenient apology that the sin
was not mine, but another’s, no longer stood me in stead; and I
have wondered ever since to hear any honest Northern man employ
it. There are Northern men, from whom nothing could surprise me.
And what have we since witnessed? The inferior officers of the law
prowling throughout the North for victims on whom to enforce it.
Their superiors, even to the highest, laboring by speeches and
proclamations and journeyings to and fro in the land (is it too much
to say?) to dragoon the people into its support. The national
treasury thrown wide open to meet its “extraordinary expenses.”
Fanueil Hall hung in chains, to ensure its execution. Presidential
candidates vieing with each other in expressions of attachment and
fidelity to it. Able men, in church and State, spotted for proscription
for no other sin than hating that law, and daring to declare that
hatred. And to crown the whole, the wisdom of the nation, in
Baltimore Conventions once and again assembled, pronouncing the
new doctrines of constitutional responsibility, with the law that
embodies it, not only a certainty, but (hear it, O heavens!) a finality!
A new word in the political vocabulary, and verily a new thing in the
earth! “Finality,” in the legislation of freemen! A finality, that forever
precludes reconsideration, amendment, or repeal! When such things
are said, and gravely said, by men professing to be American
statesmen, I can almost imagine the fathers of my country turning
painfully in their graves. And can it be possible, that in the same
breath with which men assume to roll political responsibilities on
freemen, they dare require perpetual silence and unconsidering
submission thereto? Then, what is it to be free?
But let no one dream that these formidable pronouncements have
any enduring force. It is natural, that Southern statesmen should
seek, by every possible expedient, to keep out the flood of
discussion from a system which can so illy bear it. And it is not
strange, that Northern politicians should, for temporary purposes,
assist them in the effort. This is for a day; but the great tide of
human thought flows on forever, and there is no spot from which it
will be shut out. I remember when the right of petition was denied
by our Southern brethren, in respect to this subject; and they found
compliant tools enough from the North to work with for a season.
But was the right of petition sacrificed? Of course not. And is the
right of free discussion, the right to make and (if we please) unmake
our laws, less precious? This subject will be agitated. This law will be
reconsidered; and, if it is not repealed, it will be for the same
reasons that ensures the continuance of other laws, namely, because
it is able to sustain severe and ever recurring scrutiny.
But what is to become of the Union meanwhile? One thing is very
certain. If it deliberately place itself in competition with those
“blessings of liberty,” which it was created to “secure,” it ought to
fall. Shall the end be sacrificed to preserve the means, to which the
end alone gives value? And what are we to think of the
statesmanship of those, who, to effect that preservation, would force
such an issue on a people nursed at the breasts of freedom? I would
rather die than live a traitor to my country; but let me die ten
thousand deaths before I prove treacherous to freedom and to God.
“If this be treason, make the most of it.”
But it is worse than idle to talk so. There is no such issue before the
nation. We are not compelled to choose between disunion and
slavery; a slavery, too, that would not only hold the black man in its
remorseless gripe, but put its fetters on the conscience of the white
man, and its gag into his mouth. Our Southern brethren themselves,
even to save their cherished institution, would not dare, would not
desire to press such an alternative. Were it so, who would not be
ready to surrender the Union as valueless to him, and to part
company with Southrons as men unworthy to be free? But it is not
so. There are Hotspurs, doubtless, enough of them at the South;
and Jehus, too many, at the North. And there are cunning politicians
to stand between the two sections, and play upon the prejudices of
both, and into each other’s hands, for selfish ends. But the great
heart of the nation, North and South, on the whole and according to
the measure of its understanding, beats true alike to freedom and
the constitution,—true to that immortal sentiment which, as long as
this nation endures, shall encircle its author’s name with a halo, in
whose splendor some later words that have fallen from his lips will
be happily lost and forgotten: “Liberty and Union, now and forever,
one and inseparable.” Whatever differences there may be as to the
nature, conditions, and obligations of freedom, or as to the intent
and meaning of the constitution, no party among the people will
refuse to submit them to the ordeal of discussion, and the
arbitrament of the appointed tribunals.
While this is so, let him be deemed the traitor, who stands up before
the world, and belies his country by declaring it to be otherwise. And
let every man prepare to enter into those discussions which no
human power can now stave off, in a spirit of intelligent candor and
kindness, but, at the same time, of inflexible fidelity to God and
man.

J. H. Raymond
 PLACIDO.

The true wealth and glory of a nation consist not in its gold dust, nor
in its commerce, nor in the grandeur of its palaces, nor yet in the
magnificence of its cities,—but in the intellectual and moral energy
of its people. Egypt is more glorious because of her carrying into
Greece the blessings of civilization, than because of her pyramids,
however wondrous, her lakes and labyrinths, however stupendous,
or her Thebes, though every square marked a palace, or every alley
a dome. Who hears of the moneyed men of Athens, of Rome? And
who does not hear of Socrates, of Plato, of Demosthenes, of Virgil,
of Cicero? Are you in converse with him of the “Sea-girt Isle,” and
would touch the chord that vibrates most readily in his heart?—then
talk to him of Shakspeare, of Milton, of Cowper, of Bacon, of
Newton; of Burns, of Scott. To the intelligent son of the “Emerald
Isle,” talk of Curran, of Emmett, of O’Connell.
Great men are a nation’s vitality. Nations pass away,—great men,
never. Great men are not unfrequently buried in dungeons or in
obscurity; but they work out great thoughts for all time,
nevertheless. Did not Bunyan work out a great thought all-vital and
vitalizing, when he lay twelve years in Bedford jail, weaving his
tagged lace, and writing his Pilgrim’s Progress? The greatest man in
all America is now in obscurity. It is he who is “the Lord of his own
soul,” on whose brow wisdom has marked her supremacy, and who,
in his sphere, moves
“Stilly as a star, on his eternal way.”
A great writer hath said, “Nature is stingy of her great men.” I do
not believe it. God doeth all his work fitly and well; how, therefore,
could he give us great men, not plentifully, but stingily? The truth is,
there are great men, and they are plentiful,—plentiful for the times,
I mean,—but we do not see them, because we will not come into
the sun-light of truth and rectitude where, and where only, dwelleth
greatness.
Placido was a great man. He was a great poet besides. He was a
patriot, also,—how could he be otherwise? Are not all poets patriots?
“Adios Mundo,” cried he, as with tear-bedimmed eyes he looked up
into the blue heavens above him, and upon the green earth beneath
him; and upon the portals of the universe read wisdom, majesty,
and power. Was there no poetry in this outburst of a full heart, and
in this looking upward to heaven? “Adios Mundo,” cried he, as now
beholding, for the last time, the home of his love,—he bared his
bosom to the death-shot of the soldiers.
Great was Placido in life,—he was greater still in death. His was the
faith which fastens itself upon the EVERLASTING I AM.
Call you that greatness which Pizarro achieved when, seizing a
sword and drawing a line upon the sand from east to west, he
himself facing south, he said to his band of pirates:—“Friends,
comrades, on that side are toil, hunger, nakedness, the drenching
storm, desertion, and death; on this side, ease and pleasure. There
lies Peru with its richness; here Panama with its poverty. Choose,
each man what best becomes a brave Castillian. For my part I go to
the south;”—suiting the action to the word? So do I,—but look ye,
this is merely the greatness of overwhelming energy and
concentrated purpose, not illuminated by a single ray of light from
the Divine. See here, how Placido dwarfeth Pizarro when he thus
prayeth,
“God of unbounded love, and power eternal!
To Thee I turn in darkness and despair;
Stretch forth Thine arm, and from the brow infernal
Of calumny the veil of justice tear!

O, King of kings!—my father’s God!—who only

Art strong to save, by whom is all controlled,—
Who giv’st the sea its waves, the dark and lonely
Abyss of heaven its light, the North its cold,
The air its currents, the warm sun its beams,
Life to the flowers, and motion to the streams:

All things obey Thee; dying or reviving

As thou commandest; all, apart from Thee,
From Thee alone their life and power deriving,
Sink and are lost in vast eternity!

O, merciful God! I cannot shun Thy presence,

For through its veil of flesh, Thy piercing eye
Looketh upon my spirit’s unsoiled essence,
As through the pure transparence of the sky;
Let not the oppressor clap his bloody hands,
As o’er my prostrate innocence he stands.

But if, alas, it seemeth good to Thee

That I should perish as the guilty dies,
Still, fully in me, Thy will be done, O God!”
Placido had a symmetrically developed character. All great men have
this. His intellectual and moral nature blended harmoniously as
“Kindred elements into one.”
An ancient philosopher hath said that the passions and the soul are
placed in the same body, so that the passions might have ready
opportunity to persuade the soul to become subservient to their
purpose. A terrible conflict. And yet through it Placido passed
triumphantly.
Placido was born a slave on the island of Cuba, on the plantation of
Don Terribio De Castro. The year of his birth I am unable to give,
but it must have been somewhere between the years 1790 and
1800. He was of African origin. But little is known of his earliest days
save that he was of gentle demeanor, and wore an aspect which,
though mild, indicated the working of great thoughts within. He was
allowed some little advantage of education in his youth, and he
evinced great poetic genius. The prayer just quoted was composed
by him while he lay in prison, and repeated on his way from his
dungeon to his place of execution.
The Heraldo, a leading journal of Havana, thus spoke of him after his
arrest:—
“Placido is a celebrated poet,—a man of great genius, but too wild
and ambitious. His object was to subdue Cuba, and make himself
the chief.”
The following lines, also, were found inscribed upon the walls of his
dungeon. They were written on the day previous to his execution.
 “O Liberty! I wait for thee,
To break this chain, and dungeon bar;
I hear thy voice calling me,
Deep in the frozen North, afar,
With voice like God’s, and vision like a star.

Long cradled in the mountain wind,

Thy mates, the eagle and the storm:
Arise; and from thy brow unbind
The wreath that gives its starry form,
And smite the strength, that would thy strength deform.

Yet Liberty! thy dawning light,

Obscured by dungeon bars, shall cast
A splendor on the breaking night,
And tyrants, flying thick and fast,
Shall tremble at thy gaze, and stand aghast.”

In poetic feeling, patriotic spirit, living faith, and, withal in literary

beauty, these lines are not surpassed; and they cannot fail to rank
Placido not only with the great-hearted, but with the gifted men of
the earth. A tribute to his genius is recorded in the fact, that he was
ransomed from slavery by the contributions of slave-holders of Cuba.
Placido was executed on the 7th of July, 1844. On the first fire of the
soldiers, no ball entered his heart. He looked up, but with no spirit of
revenge, no aspect of defiance,—only sat upon his countenance the
desire to pass at once into the region where no death is.
“Pity me,” said he, “and fire here,”—putting his hand upon his heart.
Two balls then entered his body, and Placido fell.
As Wordsworth said of Toussaint, so may it be said of Placido,—
 “Thou hast left behind thee
Powers that will work for thee; air, earth, and skies.
There’s not a breathing of the common wind
That will forget thee; thou hast great allies,
Thy friends are exultations, agonies,
And love, and man’s unconquerable mind.”
The charge against Placido was, that he was at the head of a
conspiracy to overthrow slavery in his native island. Blessings on
thee, Placido! Nor didst thou fail of thy mission. Did the martyrs,
stake-bound, fail of theirs? As the Lord liveth, Cuba shall yet be free.
That Placido was at the head of this conspiracy there is not a doubt;
but what his plans in detail were, I know not; the means of
acquiring them are not within my reach. Nevertheless, from the
treatment throughout of the Cuban authorities towards Placido, we
may safely conclude that Placido’s plan in detail evinced no lack of
ability to originate and execute, nor of that sagacity which should
mark a revolutionary leader. Placido hated slavery with a hatred
intensified by the remembrance of wrongs which a loving and loved
mother had borne. The iron, too, had entered into his own soul; and
he had been a daily witness of scenes such as torment itself could
scarcely equal, nor the pit itself outdo. Call you this extravagance?
You will not,—should you but study a single chapter in the history of
Cuban slavery.
Do you honor Kossuth?—then forget not him who is worthy to stand
side by side with Hungary’s illustrious son.
What may be the destiny of Cuba in the future near at hand, I will
not venture to predict. What may be her ultimate destiny is written
in the fact that,—“God hath no attribute which, in a contest between
the oppressed and the oppressor, can take sides with the latter.”
This sketch, though hastily written, and meagre in detail as it must
necessarily be, will show, at least, by the quotations of poetry
introduced, that God hath not given to one race alone, all intellectual
and moral greatness.
William G. Allen
 FOOTNOTES:
[A] A son of that distinguished friend of humanity William
Wilberforce.
[B] “Take counsel, execute judgment; make thy shadow as the
night in the midst of the noonday; hide the outcasts; bewray not
him that wandereth. Let my outcasts dwell with thee, Moab; be
thou a covert to them, from the face of the spoiler.” Isaiah 16: 3,
4.
[C] “Inasmuch as ye did it not to one of the least of these, ye did
it not to me.”—Jesus Christ. Matt. 25: 45.
[D] “Is it not that thou deal thy bread to the hungry, and that
thou bring the poor that are cast out to thy house? when thou
seest the naked that thou cover him? and that thou hide not
thyself from thine own flesh?” “If thou take away from the midst
of thee the yoke, the putting forth of the finger, and speaking of
vanity,” etc. Isa. 58: 6-9.
[E] “Therefore, all things whatsoever ye would that men should
do to you, do ye even so to them; for this is the law and the
prophets.”—Jesus Christ. Matt. 7: 12.
[F] “Thou shalt not deliver unto his master, the servant which is
escaped from his master unto thee. He shall dwell with thee; even
among you in that place which he shall choose, in one of thy
gates, where it liketh him best; thou shalt not oppress him.” Deut.
23: 15, 16.
[G] “Thou shalt love thy neighbor as thyself.” Lev. 19: 18. Matt.
19: 19.
[H] “Hearken unto me, ye that know righteousness; the people in
whose heart is my law: fear ye not the reproach of men, neither
be ye afraid of their revilings. For the moth shall eat them up like
a garment, and the worm shall eat them like wool; but my
righteousness shall be forever, and my salvation from generation
to generation.” Isaiah 51: 7, 8.
[I] “Ye that love the Lord, hate evil.” Ps. 97: 10. “The fear of the
Lord is to hate evil.” Prov. 8: 13.
[J] “Who art thou, that thou shouldst be afraid of a man? * * *
And forgettest the Lord thy Maker, * * * and hast feared
continually every day, because of the fury of the oppressor, as if
he were ready to destroy? And where is the fury of the
oppressor?” Isaiah 51: 12, 13, 14.
[K] “We ought to obey God rather than men.” Acts 5: 29.
[L] “The captive exile hasteth that he may be loosed,” etc. Isaiah
51: 15.
[M] Haynau.
[N] Editor of the Glasgow Courier. Poor Motherwell! I have it from
a mutual friend that he sympathized with the cause of Freedom,
while paid to write against it.
[O] Daniel Webster’s oration, at the laying the corner-stone of
Bunker Hill Monument, 17 June 1825.
[P] Daniel Webster’s speech in the Senate of the U. S. 7 March
1850.
[Q] Daniel Webster’s speech at the Capron Springs, Virginia,
1851.
[R] It is vain to say that rich governments cannot, and do not,
offer effective temptations to clever and eloquent men, whose
religious views differ from the national form, to induce them to
adopt the latter.
[S] Congress, the legislative department, and, of course, the
judicial, its interpreter, were intended to be founded on such
undoubted principles of liberty, that it would be difficult for them
to use their everywhere acknowledged rights, and perform their
everywhere expected duties, without first putting aside the
strongest impediment to their exercise, slavery. In our judgment
this has been done. There is no truth in public law more certain
than that protection and allegiance are reciprocal. They must exist
together or not at all. The power of the United States is adequate
for the protection of all within her limits, and from all within them
she expects allegiance. If she is informed in any way to be relied
on, that any person is restrained of his rights under the
constitution of the United States, it is her duty to see him set at
liberty, if he be confined, and see that he is redressed. It is in vain
for Congress to excuse itself from acting, by saying that it is a
State concern. Can a citizen of the United States, if he be a
citizen, be tortured or tormented by a State, when there is no
pretence that he has violated the law of either?
The constitution of the United States authorizes no man to hold
another as a slave. The United States has no power to hold a
slave. It matters not that it was intended to allow some to hold
others as their slaves. A very vile person may intend to lock up in
prison an innocent and just one, but through mistake he leaves
the door unlocked; does this, in the eyes of any reasonable men,
prevent his making his escape through the door? We are certain
not. The only proper inquiry here is, which is supreme, the
government of the Union, or the government of a particular State
of it. It is not necessary to answer this. If the first deal with no
one as a slave, the subordinate cannot by law. Persons may be
held as slaves by fraud, by cunning, by taking advantage of the
ignorance in which we hold them, by force, or a successful
combination of force, but not by LAW.
[T] “Our house stood within a few rods of the Chesapeake bay,
whose broad bosom was ever white with sails from every quarter
of the habitable globe. Those beautiful vessels, robed in purest
white, so delightful to the eye of freemen, were to me so many
shrouded ghosts to terrify and torment me with thoughts of my
wretched condition. I have often, in the deep stillness of a
summer’s Sabbath, stood all alone upon the lofty banks of that
noble bay, and traced, with saddened heart and tearful eye, the
countless number of sails moving off to the mighty ocean. The
sight of these always affected me powerfully. My thoughts would
compel utterance; and then, with no audience but the Almighty, I
would pour out my soul’s complaint, in my rude way, with an
apostrophe to the moving multitude of ships:—
“You are loosed from your moorings, and are free; I am fast in my
chains, and am a slave! You move merrily before the gentle gale,
and I sadly before the bloody whip! You are freedom’s swift-
winged angels that fly around the world; I am confined in bands
of iron! O that I were free! O that I were on one of your gallant
decks, and under your protecting wing! Alas! betwixt me and you
the turbid waters roll. Go on, go on. O that I could also go! Could
I but swim! If I could fly! O, why was I born a man, of whom to
make a brute! The glad ship is gone; she hides in the dim
distance. I am left in the hottest hell of unending slavery. O God,
save me! God, deliver me! Let me be free! Is there any God? Why
am I a slave? I will run away. * * * Only think of it; one hundred
 miles straight north, and I am free! Try it? Yes! God helping me, I
will. It cannot be that I shall live and die a slave. * * *”—
Autobiography of Douglass, pp. 64, 65.
[U] “There was no getting rid of it [the thought of his condition].
It was pressed upon me by every object within sight or hearing,
animate or inanimate. The silver trump of freedom had roused my
soul to eternal wakefulness. Freedom now appeared, to disappear
no more forever. It was heard in every sound, and seen in
everything. It was ever present to torment me with a sense of my
wretched condition. I saw nothing without seeing it, I heard
nothing without hearing it, and felt nothing without feeling it. It
looked from every star; it smiled in every calm, breathed in every
wind, and moved in every storm.”—Autobiography, pp. 40, 41.

TRANSCRIBER’S NOTES:
The cover image for this eBook was created by the transcriber and is placed in the public
domain.
Obvious typographical errors have been corrected.
Archaic or alternate spellings which may have been in use at the time of publication have
been retained.
*** END OF THE PROJECT GUTENBERG EBOOK AUTOGRAPHS FOR
FREEDOM ***

Updated editions will replace the previous one—the old editions

will be renamed.

Creating the works from print editions not protected by U.S.

copyright law means that no one owns a United States
copyright in these works, so the Foundation (and you!) can copy
and distribute it in the United States without permission and
without paying copyright royalties. Special rules, set forth in the
General Terms of Use part of this license, apply to copying and
distributing Project Gutenberg™ electronic works to protect the
PROJECT GUTENBERG™ concept and trademark. Project
Gutenberg is a registered trademark, and may not be used if
you charge for an eBook, except by following the terms of the
trademark license, including paying royalties for use of the
Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such
as creation of derivative works, reports, performances and
research. Project Gutenberg eBooks may be modified and
printed and given away—you may do practically ANYTHING in
the United States with eBooks not protected by U.S. copyright
law. Redistribution is subject to the trademark license, especially
commercial redistribution.

START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE
 PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the

free distribution of electronic works, by using or distributing this
work (or any other work associated in any way with the phrase
“Project Gutenberg”), you agree to comply with all the terms of
the Full Project Gutenberg™ License available with this file or
online at www.gutenberg.org/license.

Section 1. General Terms of Use and

Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand,
agree to and accept all the terms of this license and intellectual
property (trademark/copyright) agreement. If you do not agree
to abide by all the terms of this agreement, you must cease
using and return or destroy all copies of Project Gutenberg™
electronic works in your possession. If you paid a fee for
obtaining a copy of or access to a Project Gutenberg™
electronic work and you do not agree to be bound by the terms
of this agreement, you may obtain a refund from the person or
entity to whom you paid the fee as set forth in paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only

be used on or associated in any way with an electronic work by
people who agree to be bound by the terms of this agreement.
There are a few things that you can do with most Project
Gutenberg™ electronic works even without complying with the
full terms of this agreement. See paragraph 1.C below. There
are a lot of things you can do with Project Gutenberg™
electronic works if you follow the terms of this agreement and
help preserve free future access to Project Gutenberg™
electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright
law in the United States and you are located in the United
States, we do not claim a right to prevent you from copying,
distributing, performing, displaying or creating derivative works
based on the work as long as all references to Project
Gutenberg are removed. Of course, we hope that you will
support the Project Gutenberg™ mission of promoting free
access to electronic works by freely sharing Project Gutenberg™
works in compliance with the terms of this agreement for
keeping the Project Gutenberg™ name associated with the
work. You can easily comply with the terms of this agreement
by keeping this work in the same format with its attached full
Project Gutenberg™ License when you share it without charge
with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside
the United States, check the laws of your country in addition to
the terms of this agreement before downloading, copying,
displaying, performing, distributing or creating derivative works
based on this work or any other Project Gutenberg™ work. The
Foundation makes no representations concerning the copyright
status of any work in any country other than the United States.

1.E. Unless you have removed all references to Project

Gutenberg:

1.E.1. The following sentence, with active links to, or other

immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project
Gutenberg™ work (any work on which the phrase “Project
Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed,
viewed, copied or distributed:

This eBook is for the use of anyone anywhere in the United

States and most other parts of the world at no cost and
with almost no restrictions whatsoever. You may copy it,
give it away or re-use it under the terms of the Project
Gutenberg License included with this eBook or online at
www.gutenberg.org. If you are not located in the United
States, you will have to check the laws of the country
where you are located before using this eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is

derived from texts not protected by U.S. copyright law (does not
contain a notice indicating that it is posted with permission of
the copyright holder), the work can be copied and distributed to
anyone in the United States without paying any fees or charges.
If you are redistributing or providing access to a work with the
phrase “Project Gutenberg” associated with or appearing on the
work, you must comply either with the requirements of
paragraphs 1.E.1 through 1.E.7 or obtain permission for the use
of the work and the Project Gutenberg™ trademark as set forth
in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is

posted with the permission of the copyright holder, your use and
distribution must comply with both paragraphs 1.E.1 through
1.E.7 and any additional terms imposed by the copyright holder.
Additional terms will be linked to the Project Gutenberg™
License for all works posted with the permission of the copyright
holder found at the beginning of this work.

1.E.4. Do not unlink or detach or remove the full Project

Gutenberg™ License terms from this work, or any files
 containing a part of this work or any other work associated with
Project Gutenberg™.

1.E.5. Do not copy, display, perform, distribute or redistribute

this electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the
Project Gutenberg™ License.

1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must,
at no additional cost, fee or expense to the user, provide a copy,
a means of exporting a copy, or a means of obtaining a copy
upon request, of the work in its original “Plain Vanilla ASCII” or
other form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,

performing, copying or distributing any Project Gutenberg™
works unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or

providing access to or distributing Project Gutenberg™
electronic works provided that:

• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
 payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who

notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of

any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project

Gutenberg™ electronic work or group of works on different
terms than are set forth in this agreement, you must obtain
permission in writing from the Project Gutenberg Literary
Archive Foundation, the manager of the Project Gutenberg™
trademark. Contact the Foundation as set forth in Section 3
below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend

considerable effort to identify, do copyright research on,
transcribe and proofread works not protected by U.S. copyright
law in creating the Project Gutenberg™ collection. Despite these
efforts, Project Gutenberg™ electronic works, and the medium
on which they may be stored, may contain “Defects,” such as,
but not limited to, incomplete, inaccurate or corrupt data,
transcription errors, a copyright or other intellectual property
infringement, a defective or damaged disk or other medium, a
computer virus, or computer codes that damage or cannot be
read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except

for the “Right of Replacement or Refund” described in
paragraph 1.F.3, the Project Gutenberg Literary Archive
Foundation, the owner of the Project Gutenberg™ trademark,
and any other party distributing a Project Gutenberg™ electronic
work under this agreement, disclaim all liability to you for
damages, costs and expenses, including legal fees. YOU AGREE
THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT
LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT
EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE
THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you

discover a defect in this electronic work within 90 days of
receiving it, you can receive a refund of the money (if any) you
paid for it by sending a written explanation to the person you
received the work from. If you received the work on a physical
medium, you must return the medium with your written
explanation. The person or entity that provided you with the
defective work may elect to provide a replacement copy in lieu
of a refund. If you received the work electronically, the person
or entity providing it to you may choose to give you a second
opportunity to receive the work electronically in lieu of a refund.
If the second copy is also defective, you may demand a refund
in writing without further opportunities to fix the problem.

1.F.4. Except for the limited right of replacement or refund set

forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’,
WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied

warranties or the exclusion or limitation of certain types of
damages. If any disclaimer or limitation set forth in this
agreement violates the law of the state applicable to this
agreement, the agreement shall be interpreted to make the
maximum disclaimer or limitation permitted by the applicable
state law. The invalidity or unenforceability of any provision of
this agreement shall not void the remaining provisions.

1.F.6. INDEMNITY - You agree to indemnify and hold the

Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and
distribution of Project Gutenberg™ electronic works, harmless
from all liability, costs and expenses, including legal fees, that
arise directly or indirectly from any of the following which you
do or cause to occur: (a) distribution of this or any Project
Gutenberg™ work, (b) alteration, modification, or additions or
deletions to any Project Gutenberg™ work, and (c) any Defect
you cause.

Section 2. Information about the Mission

of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new
computers. It exists because of the efforts of hundreds of
volunteers and donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the

assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™
collection will remain freely available for generations to come. In
2001, the Project Gutenberg Literary Archive Foundation was
created to provide a secure and permanent future for Project
Gutenberg™ and future generations. To learn more about the
Project Gutenberg Literary Archive Foundation and how your
efforts and donations can help, see Sections 3 and 4 and the
Foundation information page at www.gutenberg.org.

Section 3. Information about the Project

Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-
profit 501(c)(3) educational corporation organized under the
laws of the state of Mississippi and granted tax exempt status
by the Internal Revenue Service. The Foundation’s EIN or
federal tax identification number is 64-6221541. Contributions
to the Project Gutenberg Literary Archive Foundation are tax
deductible to the full extent permitted by U.S. federal laws and
your state’s laws.

The Foundation’s business office is located at 809 North 1500

West, Salt Lake City, UT 84116, (801) 596-1887. Email contact
links and up to date contact information can be found at the
Foundation’s website and official page at
www.gutenberg.org/contact
 Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission
of increasing the number of public domain and licensed works
that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated
equipment. Many small donations ($1 to $5,000) are particularly
important to maintaining tax exempt status with the IRS.

The Foundation is committed to complying with the laws

regulating charities and charitable donations in all 50 states of
the United States. Compliance requirements are not uniform
and it takes a considerable effort, much paperwork and many
fees to meet and keep up with these requirements. We do not
solicit donations in locations where we have not received written
confirmation of compliance. To SEND DONATIONS or determine
the status of compliance for any particular state visit
www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states

where we have not met the solicitation requirements, we know
of no prohibition against accepting unsolicited donations from
donors in such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot

make any statements concerning tax treatment of donations
received from outside the United States. U.S. laws alone swamp
our small staff.

Please check the Project Gutenberg web pages for current

donation methods and addresses. Donations are accepted in a
number of other ways including checks, online payments and
credit card donations. To donate, please visit:
www.gutenberg.org/donate.

Section 5. General Information About

Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could
be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose
network of volunteer support.

Project Gutenberg™ eBooks are often created from several

printed editions, all of which are confirmed as not protected by
copyright in the U.S. unless a copyright notice is included. Thus,
we do not necessarily keep eBooks in compliance with any
particular paper edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,

including how to make donations to the Project Gutenberg
Literary Archive Foundation, how to help produce our new
eBooks, and how to subscribe to our email newsletter to hear
about new eBooks.
Welcome to our website – the perfect destination for book lovers and
knowledge seekers. We believe that every book holds a new world,
offering opportunities for learning, discovery, and personal growth.
That’s why we are dedicated to bringing you a diverse collection of
books, ranging from classic literature and specialized publications to
self-development guides and children's books.

More than just a book-buying platform, we strive to be a bridge

connecting you with timeless cultural and intellectual values. With an
elegant, user-friendly interface and a smart search system, you can
quickly find the books that best suit your interests. Additionally,
our special promotions and home delivery services help you save time
and fully enjoy the joy of reading.

Join us on a journey of knowledge exploration, passion nurturing, and

personal growth every day!

ebookbell.com