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
HP_NParDynamicProfile
HP_NParCellConnectedToIOChassis
HP_NParComponentInSlot
HP_NParIOChassisInSlot
HP_NParCellInSlot
HP_NParSlotInCabinet
HP_NParCellSlotInCabinet
HP_NParIOChassisSlotInCabinet
HP_NParCellSlotInPartition
HP_NParDomainInCabinet
HP_NParLocalPartition
HP_NParRemoteComplex
If an obvious error occurs, or if the output looks significantly different from what is shown above,
you should uninstall and then reinstall the nPartition Provider. This will re-register the provider
with WMI.
Verify WMI nPartition Provider operation
To check if the nPartition Provider is running properly and responding to client requests, open
a command prompt and run the following commands:
set CIM_NAMESPACE=root/cimv2/npar
wmiop ci HP_NParRemoteComplex
When prompted, enter the following information:
[ key ] string Address? <Management Processor hostname or IP>
string Password? <MP Admin password>
If successful, you should see the following message:
Instance [root/cimv2/npar:HP_NParRemoteComplex.Address="<mp address>"]
successfully created!
Otherwise, if you see the following error:
Error: [6] CIM_ERR_NOT_FOUND: The requested object could not be found
This indicates that the nPartition Provider is either not running, or not handling requests
appropriately. Verify that the WMI nPartition Provider service is started. If not, start it from the
Services control panel, or reboot and repeat the test. If the service is started, you should uninstall
and then reinstall the nPartition Provider.
Operational problems
The problems described below are generally associated with the use of specific commands. They
are grouped in alphabetical order, by command, with any generic or non-specific problems listed
at the beginning.
All commands: ordinal not found
This problem might be due to a conflict between the version of the OpenSSL libraries used by
the nPartition commands and nPartition Provider and the versions installed by other tools.
Currently, ActivCard Gold software is one source of this conflict.
This problem manifests itself in other ways too. For a complete description and solution, see
“nPartition Provider fails to start during installation” (page 107).
All commands: required data unavailable or locked
Because of data locking within the MP, issuing an nPartition command might display an error
message stating that required data is temporarily unavailable or locked. For example, this can
happen if multiple daemons, services, applications or administrators are simultaneously accessing
cell information, the stable complex configuration data, or the partition configuration data on
Operational problems 111