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
set CIM_USER=<domain\username>
set CIM_PASSWORD=<password for user, above>
set CIM_NOSSL=1
wmiop ei Win32_ComputerSystem
The output should be the same as in the previous test. If an error occurs, ensure that the WMI
Mapper service is started. If not, start it and repeat the test. If it is running, you should uninstall
and then reinstall the WMI Mapper component.
If you see the following error, the most likely cause is that the server is not configured for HTTP
connections:
Cannot connect to localhost: 5988. Connection failed
As noted above, the default configuration is for HTTPS connections only. To configure the service
for HTTP connections, open the %PEGASUS_HOME%\cimserver_planned.conf file and
add/edit the following entry: enableHttpConnection=true.
Then restart (or stop, then start) the Pegasus WMI Mapper service from the Services control
panel applet for the change to take effect.
Verify WMI Mapper service with HTTPS connection
This set of commands verifies that the WMI Mapper service is running and properly responding
to client requests by secure HTTP. Note that running the nPartition commands with the -g option
(to connect remotely to the MP on the partitionable system) does not go through the WMI Mapper
service, so this test does not apply for those cases.
The following test uses HTTPS/SSL connections to the service, which assumes the default WMI
Mapper configuration for HTTPS/SSL connections. See the installed file
%PEGASUS_HOME%\ConfigREADME.txt for instructions on how to configure the service.
Open a Command Prompt window and run the following commands:
set CIM_HOST=localhost
set CIM_USER=<domain\username>
set CIM_PASSWORD=<password for user, above>
The current directory must be where the known_hosts.pem file resides (either the
PEGASUS_HOME or the HP_SSL_SHARE directories) so enter the following command:
cd %PEGASUS_HOME%
Finally, run the wmiop command:
wmiop ei Win32_ComputerSystem
The output should be the same as in the previous test. If an error occurs, you should uninstall
and then reinstall the WMI Mapper component. If an SSL certificate problem is suspected, try
deleting the entire %PEGASUS_HOME% and %HP_SSL_SHARE% directories after uninstalling
and before reinstalling. This deletes all of the installed certificates, causing the certificates to be
re-generated during installation.
Verify WMI nPartition Provider registration
To check if the nPartition Provider is properly registered in WMI, open a command prompt and
run the following commands:
set CIM_NAMESPACE=root/cimv2/npar
wmiop ecn
The output should appear like this, indicating the nPartition Provider is properly registered in
WMI:
Checking component installation and operation 109