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
read/write permissions (applies to Partition Manager only – when using the nPartition
commands, the rule is this: Administrators have full access, and all other authenticated
accounts have read-only access).
Remote management using IPMI
Authentication issues associated with the remote-by-IPMI management mode include the
following:
• You must first log in to the local operating system to access the tools. However, local operating
system permissions do not apply when you use the remote modes of the nPartition tools.
• You must specify a remote MP host name or IP address and an IPMI password to enable
the remote IPMI connection to the MP.
Authorization issues associated with the remote-by-IPMI management mode include:
• Because only one remote IPMI account exists (which is fixed as “Admin”, and therefore not
specified in the tools), this account always has full (read/write) access to all nPartition
configurations in the complex.
• The nPartition Config Privilege setting has no effect when you use remote IPMI to manage
the complex: Users logged in through remote IPMI have full access to all nPartitions,
regardless of the current nPartition Config Privilege setting.
Remote management using WBEM
Authentication issues associated with the remote-by-WBEM management mode include:
• You must first log in to the local operating system to access the tools. However, local operating
system permissions do not apply when you use the remote modes of the nPartition tools.
• You must specify a remote nPartition host name or IP address and an operating system
account and password that are used to log in to that remote nPartition.
Authorization issues associated with the remote-by-WBEM management mode include:
• Authorization is based on the operating system authorization group to which the account
used for the remote login belongs.
• In Windows, if the login account is a member of the local or domain Administrators group
of the remote nPartition, you are given full permission to view and modify nPartition
configurations. Accounts that do not belong to the local or domain Administrators group
are given read-only access to the nPartition tools.
• If the nPartition Config Privilege option is enabled for the complex, users logging in to a
given nPartition with full privileges are able to modify the configuration of that nPartition
only. All other nPartition configurations are read-only for them.
Setting up the management station
A management station is often used to configure and administer nPartitions on an HP Integrity
server.
NOTE: The nPar tools can also be installed on, and run from, an nPartition on the server being
managed.
If HP provided your management station (for example, the PC-SMS management system supplied
with Superdome servers), then all of the nPartition tools and support components have already
been installed on that system.
However, if you are providing your own PC as a management station (for example, you have
an HP Integrity mid-range server), then you must install the tools and components on that system
by using the Smart Setup media provided with your server. For more information on how to do
this, See Chapter 2: “Installing nPartition Management Utilities” (page 31).
22 Introduction