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
Table 6-1 nPartition commands messages (continued)
Recommended ActionCauseMessage
Retry the command, or use a
management PC with a more reliable
network connection to the target MP or
nPartition.
NOTE: This error might occur if -w and
-g options are used in the same
command. This condition should be
reported by the parstatus command
as a syntax error because there is never
a local partition when using the -g and
-h option combination.
In most cases, these messages are
caused by lost datagrams over an
unreliable network connection. See
the AEL entry for more information.
<info> identifies the specific data that
is not available.
<component> identifies the specific
component for which data was not
available.
Cannot read <info>.
Unable to read <info>.
Unable to get <info>.
No information available for
<component>.
<Component> information
unavailable.
Do not specify a non-existent LED.Attempted to turn on or off an LED
that does not exist on the target
complex. Only Superdome servers
support all LEDs. Midrange
partitionable servers (like rx8620) do
not have cabinet or I/O chassis LEDs.
See the AEL entry to confirm this.
LED operation on <component>
failed.
Application Event Log messages
Due to limitations in the Microsoft WMI implementation, some of the error message data returned
by the nPartition provider are not transmitted through the WMI server to the client command
when the error occurs. However, under Windows, the provider logs the error data in the
Application Event Log (AEL). Additional information about an error is obtained by examining
the most recent entries logged by the nPartition provider in the AEL.
Access the AEL from the context menu of the My Computer desktop icon. Select My Computer
> Manage, and when the application opens select System Tools > Event Viewer > Application
in the left hand pane. Select the desired entry in the right hand pane and then select Properties
from the context menu to see the message itself.
After retrieving the error message from the AEL, see the following table to locate that message
and see the recommended course of action. In some cases, additional information will follow the
general message shown in the table below.
Table 6-2 Application Event Log messages
Recommended ActionCauseMessage
See additional information in AEL.Request could not be completed.Operation failed.
System firmware failed to perform
the requested operation.
Firmware error.
MP firmware failed to perform
requested operation.
Service processor error.
Add additional power supplies or
replace a defective power supply.
There is insufficient system power to
service a cell that was specified to be
powered on.
The power-on request could not be
satisfied because an N- power
condition would result.
Add additional fans or blower units or
replace a defective fan or blower.
There is insufficient system cooling
to service a cell that was specified to
be powered on.
The power-on request could not be
satisfied because an insufficient
cooling condition would result.
Retry command or use a management
PC with a more reliable connection to
the target MP or nPartition.
Datagram was lost.Timed out waiting for a response.
Error messages and corrective actions 117