parmgr(1M) parmgr(1M)
NAME
parmgr - Start Partition Manager
SYNOPSIS
Path: /opt/parmgr/bin
[-h] [-F] [-b]
-t create [-F] [-b]
-t modify -p nPartition_id [-F] [-b]
-t par_details -p nPartition_id [-F] [-b]
-t cell_details -c {cab_num/slot_num|global_cell_num} [-F] [-b]
-t io_details -i cab_num/bay_num/chassis_num [-F] [-b]
-t complex_details [-F] [-b]
DESCRIPTION
The command starts HP System Management Homepage and a client Web browser running Partition Manager. Partition Manager is a Web-based
application that allows system administrators to use a convenient graphical user interface to configure and manage nPartitions on HP server
systems. Partition Manager also provides automatic detection of several types of nPartition configuration problems.
Partition Manager can also be started without using this command by launching it from a Web browser. Different methods of starting Parti-
tion Manager are available depending on which version of HP-UX is being used:
o On systems running HP-UX 11i v1 (B.11.11) or later, Partition Manager can be started using the command, System Management Home-
page, or HP Systems Insight Manager.
o On systems running HP-UX 11i v1 (B.11.11) or HP-UX 11i v2 (B.11.23), Partition Manager also can be started from sam(1M).
Partition Manager runs within the HP-UX Tomcat-based Servlet Engine (a component in the HP-UX Web Server Suite). The Servlet Engine will
be started automatically by HP System Management Homepage when Partition Manager starts.
Partition Manager uses HP WBEM Services provided by a CIM Server to obtain information about nPartitions. Refer to the section below for
information about configuring and running the CIM Server. Interaction with local nPartitions occurs over the IPMI BT interface. Interac-
tion with remote complexes occurs over the IPMI over LAN interfaces. See the section below for additional information.
Partition Manager interacts with the user through a Web browser running on a client system. The client system may be the same as the
server system, or it may be a separate workstation or PC. Not all Web browsers are supported by Partition Manager. On workstations and
servers running HP-UX 11i v1 (B.11.11), HP-UX 11i v2 (B.11.23), or HP-UX 11i v3 (B.11.31), Partition Manager supports the use of the
default Web browser that is installed by the bundle. On PCs, Partition Manager supports the use of version 6.0 and version 7.0.
The command will start the client Web browser if it is not already running. If the Web browser is already running, will attempt to use the
existing browser window. The Web browser will display the login screen. After logging in and authenticating your identity, Partition Man-
ager will start.
Partition Manager will only start the Web browser if it can determine that the communication between the X server and the client Web
browser is secure, or if the -F option is used.
Note: If none of the -t options are used, Partition Manager will start in the . However, if Partition Manager detects any possible
configuration problems in the complex, the action will be displayed first. To start Partition Manager in a different view, use
the -t options described in the following section.
Options
The following options can be used on the command line.
-h Display help about the command line parameters, then exit.
-F Force a client Web browser to be used, even though cannot determine if the communication between the X server and the client
browser is secure. Use this option if the security of X traffic is not an issue in your environment.
When is invoked by sam(1M), the -F option is used. If the security of network traffic is a concern in your environment, do not
launch Partition Manager from .
-b Bypass HP System Management Homepage authentication if you are already logged in with root permissions.
-t create Create a new nPartition by starting Partition Manager in the action.
-t modify -p nPartition_id
Modify the nPartition identified by the -p option, by starting Partition Manager in the action. The nPartition is selected by
its partition number.
-t par_details -p nPartition_id
Display details about the nPartition identified by the -p option, by starting Partition Manager in the . The nPartition is
selected by its partition number. If Partition Manager detects any possible configuration problems in the complex, the action
will be displayed first.
-t cell_details -c {cab_num/slot_num|global_cell_num}
Display details about the cell identified by the -c option, by starting Partition Manager in the . The cell is selected by its
cabinet number and slot number, or by its global cell number. If Partition Manager detects any possible configuration problems
in the complex, the action will be displayed first.
-t io_details -i cab_num/bay_num/chassis_num
Display details about the I/O chassis identified by the -i option, by starting Partition Manager in the . The I/O chassis is
selected by its cabinet number, I/O bay number, and I/O chassis slot number. If Partition Manager detects any possible configu-
ration problems in the complex, the action will be displayed first.
-t complex_details
Display details about the entire complex by starting Partition Manager in the action. If Partition Manager detects any possible
configuration problems in the complex, the action will be displayed first.
User Authentication
Your access to Partition Manager depends on whether you are a or a . Non-privileged users can only view information, and cannot perform
any tasks that change the remote nPartition or the complex that it belongs to. Privileged users can perform all tasks in Partition Manager
(refer to the section below for information about restrictions that may apply to privileged users).
When your Web browser connects to Partition Manager, your identity is authenticated in two stages.
1. The login screen requests your user name and password. If you are running on a local nPartition, Partition Manager will then
start immediately. If the user name represents a privileged user on the local system you will have privileged access.
2. If you are not running Partition Manager on a local nPartition, you must provide additional credentials for access to a remote
system. You will be presented with two choices.
A remote nPartition
To manage a remote nPartition (and the complex that it belongs to), you must provide the hostname or IP address of the
nPartition, a user name known to the remote nPartition, and the password associated with that user name. The user name
defaults to the user name entered at the HP System Management Homepage login screen. After filling in the fields,
click .
Partition Manager will communicate with the remote nPartition via WBEM, using the supplied user name and password. If
the user name represents a privileged user on the remote nPartition you will have privileged access.
If the WBEM user name and password is not valid on all nPartitions in the complex, then Partition Manager will be
unable to obtain some information from other nPartitions. To simplify management of a complex, use a consistent set of
WBEM user names and passwords on all nPartitions in the complex.
A remote partitionable complex
To manage a remote complex via IPMI over LAN, you must provide the hostname or IP address of the service processor on
the remote complex and the IPMI password for that service processor. (The IPMI password can be set or changed by log-
ging on to the service processor and using the command from the Command Menu.) After filling in the fields, click .
If an error is reported when you attempt to connect using this option, check to see that IPMI over LAN access has not
been disabled on the remote service processor. Access to the complex via IPMI over LAN can be enabled or disabled by
logging on to the service processor and using the command from the Command Menu.
Within Partition Manager, you can use the Switch Complexes action from the Partition Manager Tools menu to display these choices.
You can then select a different complex to be managed.
Session Timeout
If HP System Management Homepage sees no activity for approximately 30 minutes, the session will expire. You will have to login again in
order to continue. To end the session manually, click the Log off link in the upper right corner of the screen.
Online Help
Detailed information about using Partition Manager is provided in the online help. From Partition Manager, use the Help menu or Help but-
ton to display context-sensitive help.
EXTERNAL INFLUENCES
Environment Variables
DISPLAY Specifies the X server to be used as the display by the client Web browser. This variable must be set if is used to start the
Web browser.
BROWSER Specifies the path to the client Web browser. If a supported Web browser is installed at the default location, this variable
will not be used. Otherwise, this variable must be set for to be able to start the Web browser.
Partition Commands
Partition Manager executes partition(1) commands to perform administration functions.
CIM Server
The CIM server implements the Common Information Model for HP WBEM Services. Partition Manager depends on the CIM server in the following
ways.
o When Partition Manager is running on an nPartition to manage the local complex, then the CIM server must be running on the local
nPartition.
o When Partition Manager is connected to the service processor of a remote partitionable system via IPMI over LAN, then the CIM
server must be running on the system that Partition Manager is running on.
o When Partition Manager is connected to a remote nPartition via WBEM, then the CIM server must be running on that remote nParti-
tion. In order to connect in this manner, you may need to perform the following additional configuration steps.
1. In order to connect as a privileged user, the enableRemotePrivilegedUserAccess parameter on the CIM server running on the
remote nPartition must be set to true. This is the default setting, but it may have been changed by a system administrator.
Use the cimconfig(1M) command to check or change the setting of this parameter. Restart the CIM server after making any con-
figuration changes.
If you are not connected as a privileged user, you will only be able to view information in Partition Manager. You will not
be able to perform any tasks that change the remote nPartition or the complex that it belongs to.
2. Partition Manager uses Secure Socket Layer (SSL) connections between the client and the CIM server. The CIM server must have
SSL connections enabled (the enableHttpsConnection parameter must be set to true). Use the cimconfig(1M) command to check or
change the setting of this parameter. Restart the CIM server after making any configuration changes.
3. By default, Partition Manager validates the certificates used with SSL connections. This means that the client Certificate
Trust Store must include the server certificates from the remote nPartition. Refer to the section below for instructions on
exporting and importing certificates.
If your environment does not require the additional security provided by certificate validation, you can disable this feature.
To do so, edit the CIM properties file:
/opt/hpsmh/tomcat/webapps/parmgr/WEB-INF/lib/cim.properties
Remove the comment prefix (//) from the following line in the file:
//TrustManager=org.snia.wbemcmd.xml.DontValidateCertificate
For more information about configuring the CIM server, refer to the cimconfig(1M) and cimserver(1M) manpages.
Managing SSL Certificates
To enable SSL certificate validation in Partition Manager, you must export the server certificates from the remote CIM server(s) that you
want to connect to, and import those certificates into the CIM client's keystore. Follow the steps below.
On the CIM Server:
1. Locate the WBEM services provider certificate file (cert.pem) on the remote nPartition that you want to connect to. To find the
correct file, open the configuration file:
$PEGASUS_HOME/cimserver_current.conf
The location of the server certificate file is configured by the sslCertificateFilePath setting. Normally, this will be set to:
/etc/opt/hp/sslshare/cert.pem
If there is no sslCertificateFilePath setting, the default server certificate file is:
$PEGASUS_HOME/server.pem
2.
Copy the certificate file located in step 1 (cert.pem or server.pem) to the client system.
On the Client:
1. Import the certificate into the Partition Manager keystore:
$JAVA_HOME/bin/keytool -import
-alias server_hostname
-file cert.pem
-keystore /etc/opt/hp/sslshare/parmgr.keystore
When prompted, enter the password to the keystore. If the parmgr.keystore file does not yet exist (this is the first certificate
that you have imported), then this command will create a new keystore file. In that case, any password that you enter will
become the assigned password for this keystore. Use a password that you will remember. You will need it the next time that you
import a certificate into the keystore.
2.
To enable certificate validation for the partition(1) commands used by Partition Manager, append the contents of cert.pem to the
end of the file:
/var/opt/wbem/client.pem
nPartition Configuration Privilege
When running Partition Manager on a local nPartition, or when connecting via WBEM to a remote nPartition, the ability to perform configura-
tion operations on a complex is affected by the setting of the nPartition Configuration Privilege. If the privilege is unrestricted, all
configuration operations are permitted. If the privilege is restricted, then you will only be able to perform operations that affect the
local or remote nPartition, and no operation that modifies the Stable Complex Configuration Data will be permitted (including adding and
deleting nPartitions).
The default setting of the nPartition Configuration Privilege is unrestricted. The setting can be changed by logging onto the service pro-
cessor and using the command from the Command Menu.
RETURN VALUES
The command will return one of the following exit codes.
Successful.
An error occurred when starting Partition Manager, the HP-UX
Tomcat-based Servlet Engine, or the client Web browser.
The command was invoked with invalid parameters.
EXAMPLES
Start the HP-UX Tomcat-based Servlet Engine and the client Web browser on the local host.
parmgr
Start the HP-UX Tomcat-based Servlet Engine and the client Web browser, displaying details about the I/O chassis in cabinet 0, I/O bay 1,
I/O chassis number 3.
parmgr -t io_details -i 0/1/3
WARNINGS
When managing a remote partitionable complex, the performance degrades when the connection traverses long network distances, e.g. managing
a partitionable complex in California from a system in New York. Furthermore, when managing a remote system, performance can be improved
by connecting to a remote nPartition, rather than connecting directly to the remote system's service processor.
A noticeable delay may occur the first time that each Partition Manager view is displayed after the HP-UX Tomcat-based Servlet Engine is
started or restarted. This is due to the initial compilation of Java Server Pages. Once a given view has been displayed, subsequent dis-
plays of that view will be significantly faster.
When managing a remote system, possible performance improvements can be obtained by running the Web browser on the local system, instead of
running the browser remotely to a local X Server.
The nPartition provider maintains a cache of information about systems being managed. This cache is cleared when the nPartition Provider
is unloaded by the CIM server. Performance may be reduced when managing a system for the first time, or immediately after the CIM server
has been restarted. Subsequent management sessions of the same system will be faster.
When using Partition Manager, be aware of the following limitations concerning commonly used Web browser features.
o The browser's Back and Forward buttons should be avoided, especially when using checkboxes to select items, and in the and tasks.
Instead, navigate around Partition Manager by:
1. clicking on hyperlinks;
2. clicking on cell and I/O chassis icons;
3. clicking on navigation buttons at the bottom of task dialogs.
o The browser's Refresh or Reload button does cause Partition Manager to update the displayed data. Instead, use Partition Man-
ager's Refresh button at the top right of the window, or use the Refresh Data action from the Tools menu.
AUTHORS
parmgr was developed by Hewlett-Packard.
FILES
Partition Manager creates or writes to the following files on the server host.
/var/sam/log/samlog
Partition Manager events are logged to this file. This log can be viewed from within Partition Manager by the Show Log File menu
action. It can also be viewed outside of Partition Manager by samlog_viewer(1).
/opt/hpwebadmin/logs/
The HP-UX Tomcat-based Servlet Engine maintains log files in this directory.
/var/opt/hpwebadmin/parmgr/
Partition Manager creates temporary files in this directory.
SEE ALSO
partition(1), cimauth(1M), cimconfig(1M), cimserver(1M), smhstartconfig(1M), sam(1M), samlog_viewer(1)
Partition Manager Web site: http://docs.hp.com/en/PARMGR2/
. This document can be found on the HP Technical Documentation Web site at http://docs.hp.com.
Partition Manager online help.
parmgr(1M)