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 hardware of a cell-based server—including all cells, I/O expansion cabinets, cables, cabinet
hardware, fans, and power and utility components—is known as a server complex.
• A Superdome server complex can consist of one or two server cabinets and can also include
one or two I/O expansion cabinets (which provide additional I/O chassis).
• An rx8620 or rx8640 server complex consists of a single server cabinet and can include one
I/O expansion cabinet (which provides two additional I/O chassis).
• An rx7620 or rx7640 server complex consists of a single server cabinet only.
An nPartition is a partition of the server complex that you can reconfigure without physically
modifying the server hardware. An nPartition contains one or more cells communicating
coherently over a high-bandwidth, low-latency, crossbar fabric. Special firmware in each cell
defines the boundaries of an nPartition to ensure isolation from other nPartitions.
Each nPartition has exclusive use of the memory, processor, and I/O resources belonging to the
cells that are assigned to that nPartition. An nPartition must have at least one core I/O card to
support console services, booting, and management operations. Each nPartition has its own
system boot interface, boots independently, and executes its own operating system image.
Properties of nPartitions
An nPartition has the following properties:
Partition Numbers Each nPartition is identified by a unique partition number.
When you create an nPartition, it is assigned the lowest
available number. That is, the first nPartition always is
partition number 0 and the second nPartition is partition
number 1.
When you remove an nPartition, its partition number is
released and you can reuse it when you create a new
nPartition. Consider a server with partitions numbered 0,
1, 2, and 3. When you remove partition 2, for example, and
then create a new nPartition, the new nPartition is
identified as partition 2.
Assigned and Unassigned Cells If a cell in a server complex is not assigned to an nPartition,
the cell is considered unassigned. If an I/O chassis is
attached to an assigned cell, then the chassis is likewise
assigned to that nPartition. Cells that are unassigned are
considered to be available resources; they are free to be
assigned to any existing nPartition or used to create a new
nPartition.
Base Cells All cells within an nPartition are base cells. If you do not
specify the cell type, the nPartition administration tools
automatically set the cell type to base cell.
Active and Inactive Cells Active cells are assigned cells that boot to form an
nPartition whose resources (processors, memory, and any
attached I/O) can be used by software running in that
nPartition.
Cells that are inactive are either not assigned to an
nPartition or have not participated in partition rendezvous
with other cells in the nPartition to form an nPartition.
(Partition rendezvous is the event during the nPartition
boot process when all available cells in an nPartition join
to determine which cells are active for the current boot of
the nPartition.) The resources belonging to inactive cells
are not used by an nPartition.
Getting to know nPartitions 13