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

4 Using Other Tools to Manage nPartitions
This chapter describes some of the other tools and methods for managing nPartitions on HP
Integrity servers. In nearly every case, you can use Partition Manager to perform these tasks,
and HP recommends that you do so whenever possible.
Because the scope of this document is limited to HP Integrity Servers running Microsoft Windows
Server 2003, emphasis is placed on the tools provided with that platform (such as nPartition
commands), even when other tools might also exist. For those procedures that you can perform
with an nPartition command, that is the only method presented. However, for procedures that
you cannot perform using an nPartition command, the alternate methods are provided (such as
issuing commands from the MP or EFI Shell menus).
For a complete and comprehensive description of all the HP Integrity nPartitioning procedures,
tools, and topics, on all supported platforms, see the HP System Partitions Guide: Administration
for nPartitions at:
http://docs.hp.com/hpux/multiOS/index.html
NOTE: HP recommends that you put the target nPartition into a Shutdown for Reconfig state
before changing any of its cell assignments, such as adding cells to the nPartition or deleting
cells from it.
NOTE: In addition, you must enable the ACPI flag for modified and newly created nPartitions
after performing management tasks on them, by running the EFI acpiconfig windows
command, followed by a reset.
Complex-level tasks
This section describes tasks you can perform for the entire complex.
Rename a server complex
You can assign a name for each server complex to better identify the complex as you work with
it. The server complex name serves as a helpful identifier; changing the name does not affect the
way in which commands and utilities interact with the complex.
Several commands and utilities display the server complex name as part of their output and
interfaces. For example, some nPartition commands and Partition Manager list the complex
name.
Each server complex name has up to 20 characters, which can include upper- and lowercase
letters; numbers; and dashes (-), underscores (_), periods (.), and spaces ( ).
The server complex name is stored as part of the Complex Profile for the server (part of its Stable
Complex Configuration Data).
Procedure 4-1 Renaming a server complex [nPartition commands]
Rename a server complex using the following procedure:
1. Log in to Windows on the management station PC.
Complex-level tasks 43