Windows nPartition Guide v5.5
Table Of Contents
- nPartition Administrator's Guide
- Table of Contents
- 1 Introduction
- Quick Start
- Getting to know nPartitions
- Choosing a management tool
- Management interface options
- Choosing a management mode
- Setting up the management station
- Performing nPartition management tasks
- 2 Installing nPartition Management Utilities
- 3 Using Partition Manager
- 4 Using Other Tools to Manage nPartitions
- Complex-level tasks
- nPartition-level tasks
- Boot configuration options for nPartition systems
- Find bootable devices
- List nPartition configurations
- List the local (current) nPartition number
- List memory configurations
- Configure boot paths and options
- Configure autoboot options
- Configure boot-time system tests
- Boot Windows Server 2003
- Boot over a network
- Shut down Windows Server 2003
- Reboot and reset
- Reboot for reconfiguration
- Shut down to a shutdown for reconfig (inactive) state
- Boot an inactive nPartition
- Perform a transfer of control reset
- Create a Genesis Partition
- Create a new nPartition
- Remove (delete) an nPartition
- Add cells to an nPartition
- Set core cell choices
- Rename an nPartition
- Cell-level tasks
- Power-, status-, and hardware-level tasks
- List input/output (I/O) configurations
- List cabinets in a server complex
- List power status and power supplies
- List fan and blower status
- Turn attention indicators (LEDs) on and off
- Power server cabinets on and off
- Power cells and I/O chassis on and off
- Configure and deconfigure cells
- Configure and deconfigure processors (CPUs)
- Configure and deconfigure memory (DIMMs)
- 5 nPartition Commands Reference
- 6 Troubleshooting
- Installation problems
- Checking component installation and operation
- Operational problems
- All commands: ordinal not found
- All commands: required data unavailable or locked
- Fruled: LED error messages (mid-range servers only)
- Frupower: cannot power off error
- Parcreate and parmodify: cell local memory warnings
- Parcreate, parmodify, and parremove: failure to update stable complex configuration data (SCCD)
- Parremove: shutdown and reset instructions
- Parstatus -c -V: apparent incorrect output
- Parstatus -p -V: apparent incorrect output
- Parstatus: local partition error
- Parstatus: unable to get read lock error
- Using WMIOP.EXE to pinpoint problems
- Error messages and corrective actions
- Index
b. Enter the hostname/IP address of the remote nPartition that you want to connect to, an
account, and password with administrative privileges on the remote nPartition in the
top half of the Partition Manager login screen.
c. Click OK.
d. Go to Step 5 to verify correct installation and operation.
4. To test remote IPMI connections, you must enter the hostname/IP address of the remote MP
that you want to connect to and the IPMI password for that MP in the bottom half of the
Partition Manager login screen, then click OK. Then go to Step 5 to verify the correct
installation and operation.
5. Verify correct operation of Partition Manager: After you log into Partition Manager, a message
should appear for several seconds to a minute:
Loading complex information.
After that, Partition Manager should display top-level information about the complex,
including all currently configured nPartitions and their associated cells and I/O chassis.
6. When Partition Manager is up and running, verify that the complex information looks
correct, and that no error messages are displayed. For example, in the Action menu on the
right side of the screen, select Complex to expand the complex-level submenu. Select Show
Complex Details to display a complete listing of the complex configuration.
Verify that this information looks correct, and that no error messages are displayed. Then
close the Complex Details window by clicking OK in the upper-left corner of the window.
7. In the same Complex menu, select Clear All LEDs. A dialog box should appear, stating that
the command ran successfully. If possibly, verify that all server LEDs are now off, by looking
at the server.
If these tests do not give the desired results, you can perform additional tests to help pinpoint
the problem. See “Checking component installation and operation” (page 107).
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, do the following:
Part 1 — On the Server
1. Locate the WBEM SSL certificate file (cert.pem) on the remote nPartition that you want
to connect to.
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
nPartition, 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 the configuration file contains no sslCertificateFilePath entry, the default server
certificate file is found here:
%PEGASUS_HOME%\server.pem
3. Copy the certificate file located in Step 2 (cert.pem or server.pem) to the client system.
Part 2 — On the Client
34 Installing nPartition Management Utilities