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
the MP. It can also happen when long or unreliable network connections exist between the MP
and the remote management PC, or if the MP is busy with some other internal operation.
This condition is normally transient. If it occurs, retry the command; it should succeed when
tried again. If the locked data condition persists it can be remedied with the parunlock command.
Use the parunlock command carefully, however. Make sure the locked data is not currently
being used by another user or process before issuing the command.
Fruled: LED error messages (mid-range servers only)
When using the fruled command with the rx8620 or rx7620, you will see the following error
message:
Error: LED operation on cabinet number failed
Error: LED operation on component number failed
This is not really an error, since the HP Integrity mid-range servers do not have I/O chasses or
cabinet LEDs.
Frupower: cannot power off error
When using the frupower command, you might see the following error message:
ERROR: Cannot power off I/O chassis x/x/x (your chassis number).
Chassis is attached to inactive cell x (your cell number).
Please turn cell power off.
You will see this error message if you try to power off an I/O chassis independently from its
attached cell. This can only be done successfully in very limited circumstances. See the on-line
documentation for the frupower command for those circumstances. HP recommends that
customers power off the cell, which automatically powers off the I/O chassis.
Parcreate and parmodify: cell local memory warnings
When using the parcreate or parmodify commands along with the option to set or modify
the amount of Cell Local Memory (CLM), you might see the following warning:
WARNING: Unable to determine if the target partition supports cell local
memory.
This is normal behavior. The operating system that is running (or will be installed) on the partition
cannot be determined remotely by parcreate or parmodify, but Windows 2003 Server does
in fact support CLM.
Parcreate, parmodify, and parremove: failure to update stable complex
configuration data (SCCD)
You might see the following errors when using parcreate or parmodify to add or remove
cells from a partition, or to modify the CLM values for cells in a partition, or when using
parremove to remove a partition.
ERROR: The Partition Configuration Data was written out, but could not
write Stable Complex Configuration Data. Attempts to undo the Partition
Configuration Data changes have failed. As a result, options which cause
partition reconfiguration i.e., addition or deletion of cells have
failed, all other options have succeeded.
Subsequent attempts to run other commands might result in either:
ERROR: Unable to update the Stable Configuration Data.
or:
ERROR: Failed to connect to target partition or complex.
112 Troubleshooting