Home » HP Manuals » Servers » HP Integrity rx5670 » Manual Viewer

HP Integrity rx5670 Windows Integrity nPartition Guide - Page 40

Miscellaneous installation issues, Configuring for secure WBEM communications

View all HP Integrity rx5670 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 40 highlights

Installing nPartition Management Utilities Miscellaneous installation issues Miscellaneous installation issues The installation-related issues described in this section may or may not apply to you, depending on your connection method and mode. Configuring for secure WBEM communications To configure for secure WBEM communications: Part 1 - On the Server: Step 1. Locate the WBEM SSL Certificate file (cert.pem) on the remote nPartition that you want to connect to. Step 2. To verify you are copying the correct certificate file, open the CIM Server/WMI Mapper configuration file (%PEGASUS_HOME%\cimserver_current.conf) on the remote nPar, and look for the sslCertificateFilePath entry. This entry indicates the server certificate file currently configured for use by the CIM Server/WMI Mapper (on a Windows system, this entry is usually: %SystemDrive%\hp\sslshare\cert.pem). NOTE If there is no sslCertificateFilePath entry, the default server certificate file is found here: %PEGASUS_HOME%\server.pem. Step 3. Copy the certificate file located in Step 2 (cert.pem or server.pem) to the client system. Part 2 - On the Client: Step 1. Import the certificate (cert.pem) into the parmgr keystore (parmgr.keystore) by entering the following command at the command line (all one line): %JAVA_HOME%\bin\keytool -import -alias server_hostname -file cert.pem -keystore %SystemDrive%\hp\sslshare\parmgr.keystore Step 2. When prompted, enter the password to the keystore. If the parmgr.keystore file does not yet exist (in other words, if this is the first certificate you have tried to import), the keytool -import command creates a new keystore file and any password you enter becomes the assigned password for this new keystore. NOTE Use a password that you will remember. You will need it the next time you import a certificate into the keystore. Step 3. To enable certificate validation for the commands used by Partition Manager, append the contents of cert.pem to the end of the file: %SystemDrive%\hp\sslshare\known_hosts.pem. NOTE Earlier versions of the nPartition commands used client.pem, instead of known_hosts.pem. Consult the nPartition Commands release notes to determine which file you should use. Step 4. Finally, restart the JSP/Servlet Container by restarting the HP System Management Homepage service (SysMgmtHP), or by rebooting Windows. 40 Chapter 2

Section	Page
1 Introduction	7
Quick Start	9
Getting to know nPartitions	10
Partitioning continuum	10
Cell structure of nPartitions	11
Properties of nPartitions	11
Cell and nPartition boot process	13
Cell boot phase	13
nPartition boot phase	13
Choosing a management tool	15
Management interface options	16
Intelligent Platform Management Interface (IPMI)	16
IPMI Block Transfer (IPMI BT)	16
IPMI over LAN	16
Managing nPartitions using IPMI over LAN	17
Web-Based Enterprise Management (WBEM)	18
Securing the WBEM connection	18
Managing nPartitions using WBEM	19
Choosing a management mode	21
Local management	21
Remote management via IPMI	22
Remote management via WBEM	22
Authentication and authorization issues	22
Local management	22
Remote management via IPMI	23
Remote management via WBEM	23
Setting up the management station	25
Controlling the management station remotely	25
Remote Control	25
Terminal Services	25
Remote Desktop	26
Telnet	26
Performing nPartition management tasks	27
Listing the status of an nPartition or complex	27
Using the Partition Manager	27
Using the nPartition commands	27
Using the Management Processor Command menu	28
Using the EFI Shell	28
Creating nPartitions	28
Creating the first nPartition in a server complex	28
Creating a Genesis Partition for a server complex	29
Creating additional nPartitions in a server complex	29
Modifying nPartitions	29
Booting and resetting nPartitions	30
Using the Management Processor Command menu	31
Using the EFI Shell	31
Using Microsoft Windows commands	31
2 Installing nPartition Management Utilities	33
nPartition Commands	35
Install nPartition Commands bundle from the Smart Setup media	35
Partition Manager	36
Install Partition Manager Bundle from the Smart Setup media	36
Verifying the installation	38
Verifying nPartition Commands	38
Verifying Partition Manager	38
Miscellaneous installation issues	40
Configuring for secure WBEM communications	40
Upgrading service packs later (after installation)	41
3 Using Partition Manager	43
4 Using Other Tools for Managing nPartitions	51
Complex-level tasks	53
Rename a server complex	53
Unlock complex profile entries	53
Cancel pending changes to the complex profile	54
List product and serial numbers	55
nPartition-level tasks	56
Boot configuration options for nPartition systems	56
Find bootable devices	57
List nPartition configurations	58
List the local (current) nPartition number	58
List memory configurations	59
Configure boot paths and options	60
Configure autoboot options	62
Configure boot-time system tests	64
Boot Windows Server 2003	65
Boot over a network	66
Shut down Windows Server 2003	68
Reboot and reset	69
Reboot for reconfiguration	73
Shut down to a shutdown for reconfig (inactive) state	74
Boot an inactive nPartition	77
Perform a transfer of control (TOC) reset	78
Create a genesis nPartition	79
Create a new nPartition	81
Remove (delete) an nPartition	84
Add cells to an nPartition	86
Set core cell choices	89
Rename an nPartition	90
Cell-level tasks	92
List processor configurations	92
List cell configurations	92
Unassign (remove) cells from an nPartition	93
Set cell attributes	95
Power-, status-, and hardware-level tasks	98
List input/output (I/O) configurations	98
List cabinets in a server complex	98
List power status and power supplies	99
List fan and blower status	99
Turn attention indicators (LEDs) on and off	100
Power server cabinets on and off	102
Power cells and I/O chassis on and off	104
Configure and deconfigure cells	105
Configure and deconfigure processors (CPUs)	106
Configure and deconfigure memory (DIMMs)	107
5 nPartition Commands Reference	109
parcreate	110
parmodify	115
parremove	121
parstatus	124
parunlock	127
fruled	129
frupower	132
cplxmodify	135
6 Troubleshooting	137
Installation problems	139
Services (WMI Mapper + nPartition Provider) fail to start during installation	139
nPartition Provider fails to start during installation	139
Checking component installation and operation	140
Verify WMI Mapper installation	140
Verify WMI Mapper service with HTTP connection	141
Verify WMI Mapper service with HTTPS connection	142
Verify WMI nPartition Provider registration	143
Verify WMI nPartition Provider operation	145
Operational problems	147
All commands: ordinal not found	147
All commands: required data unavailable or locked	147
Fruled: LED error messages (mid-range servers only)	147
Frupower: cannot power off error	147
Parcreate and parmodify: cell local memory warnings	148
Parcreate, parmodify, and parremove: failure to update stable complex configuration data (SCCD)	148
Parremove: shutdown and reset instructions	149
Parstatus -c -V: apparent incorrect output	149
Parstatus -p -V: apparent incorrect output	149
Parstatus: local partition error	150
Parstatus: unable to get read lock error	150
Using WMIOP.EXE to pinpoint problems	151
Error messages and corrective actions	153
nPartition commands messages	153
Application Event Log messages	155
Index	159
A	159
B	159
C	159
D	159
E	159
F	159
I	159
L	159
M	159
N	159
P	159
R	160
S	160
T	160
U	160

Match case Limit results 1 per page

Installing nPartition Management Utilities

Miscellaneous installation issues

Chapter 2

Miscellaneous installation issues

The installation-related issues described in this section may or may not apply to you,

depending on your connection method and mode.

Configuring for secure WBEM communications

To configure for secure WBEM communications:

Part 1 — On the Server:

Step 1.

Locate the WBEM SSL Certificate file (

cert.pem

) on the remote nPartition that you

want to connect to.

Step 2.

To verify you are copying the correct certificate file, open the CIM Server/WMI Mapper

configuration file (

%PEGASUS_HOME%\cimserver_current.conf

) on the remote nPar, and

look for the

sslCertificateFilePath

entry. This entry indicates the server certificate

file currently configured for use by the CIM Server/WMI Mapper (on a Windows system,

this entry is usually:

%SystemDrive%\hp\sslshare\cert.pem

NOTE

If there is no

sslCertificateFilePath

entry, the default server certificate file is found

here:

%PEGASUS_HOME%\server.pem

Step 3.

Copy the certificate file located in Step 2 (

cert.pem

server.pem

) to the client system.

Part 2 — On the Client:

Step 1.

Import the certificate (

cert.pem

) into the parmgr keystore (

parmgr.keystore

) by

entering the following command at the command line (all one line):

%JAVA_HOME%\bin\keytool -import -alias server_hostname

-file cert.pem -keystore %SystemDrive%\hp\sslshare\parmgr.keystore

Step 2.

When prompted, enter the password to the keystore. If the

parmgr.keystore

file does

not yet exist (in other words, if this is the first certificate you have tried to import), the

keytool -import

command creates a new keystore file and any password you enter

becomes the assigned password for this new keystore.

NOTE

Use a password that you will remember. You will need it the next time you import a

certificate into the keystore.

Step 3.

To enable certificate validation for the commands used by Partition Manager, append the

contents of

cert.pem

to the end of the file:

%SystemDrive%\hp\sslshare\known_hosts.pem

NOTE

Earlier versions of the nPartition commands used

client.pem

, instead of

known_hosts.pem

. Consult the nPartition Commands release notes to determine which

file you should use.

Step 4.

Finally, restart the JSP/Servlet Container by restarting the HP System Management

Homepage service (

SysMgmtHP

), or by rebooting Windows.