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 other option is to install the nPar tools onto an existing nPartition on the server, and then
use them to manage the other nPartitions in the system. This is called the “local management”
mode.
When the nPartition tools run on an nPartition in local management mode, they default to
managing the local complex using the IPMI/BT interface to the MP. This is the simplest mode to
use. Because the tools run on the system being managed, you do not need to provide additional
authentication or remote connection information to make them work.
For example, when you run the nPartition commands in the local mode, you do not need -g,
-u, or -h options to manage the local complex. When you run Partition Manager in the local
mode, the connection to the local complex is made automatically (no additional connection or
authentication information is required).
You can even manage another complex remotely, from an nPartition configured to run in local
management mode, by using the -g or -u options with the nPartition commands, or by selecting
Tools > Switch Complexes in Partition Manager.
A list of the advantages and disadvantages of the different management modes and connection
methods follows. Also included are a listing of the authentication and authorization issues
associated with each mode.
Local management
The following are some of the advantages of local management:
• Simple installation: Install all components on an nPartition (fewer components must be
installed manually when reinstall media is used).
• Simple connection: Log in to SMH and run Partition Manager, or run nPartition commands
with no -g/-u options. No additional authentication or login steps are required to manage
the local complex.
• Controlled configuration of specific nPartitions with the nPartition Config Privilege option:
You can restrict to configuration of certain nPartitions.
Some of the disadvantages of local management follow:
• Requires at least one nPartition to be configured already and booted to Windows (or to
another operating system supporting the nPartition tools).
• Requires nPartition tools to be installed on at least one nPartition in each partitionable
complex.
• Requires login to an nPartition in each complex to be managed, through the SMH web (in
the case of Partition Manager), telnet, or Remote Desktop (in the case of the nPartition
commands).
Remote management using IPMI
Some of the advantages of remote management using IPMI are as follows:
• Installs easily: Install all components onto a remote management station and you are ready
to manage all complexes in the data center.
• Enables you to manage a complex even if no nPartitions are currently configured in the
complex.
• Enables you to manage all complexes in the data center from a single management station.
Some of the disadvantages of remote management using IPMI are as follows:
20 Introduction