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

nPartition tools and components are supported on management stations running one of the
following operating systems:
• Windows 2000, SP3 or later
• Windows XP
• Windows Server 2003 (both 32- and 64-bit editions)
Controlling the management station remotely
Locate the management station running the nPartition tools close to the server being managed
to minimize the likelihood of UDP datagrams being lost in transmission. If, as a result, you cannot
access the management station directly, you can use a remote desktop control or telnet application
to access the management station remotely. To connect to the management station remotely, you
can use any of the following applications.
Remote Control
To view the desktop of the management station from a remote terminal running an operating
system other than Windows Server 2003, Windows XP, or Windows Server 2000, use third-party
remote control software, such as the free VNC (www.realvnc.com) or the Symantec pcAnywhere
software.
Terminal Services
Windows Server 2000 and Windows Server 2003 include a Terminal Services feature that enables
you to create a login session different from the console, leaving the console available for other
administration tasks.
To enable Terminal Services on the management station, click its check box in Add Windows
Components. Windows 2000 Professional and some Windows Server editions do not include a
client for Terminal Services. Download the free client from www.microsoft.com.
Remote Desktop
If you are running Windows Server 2000 with Terminal Services, Windows Server 2003, or
Windows XP on the management station and Windows Server 2003 or Windows XP on the
remote terminal, you can take advantage of the remote desktop display feature provided by
these operating systems.
The Remote Desktop Connection feature is not enabled by default in Windows XP or Windows
Server 2003. To enable Remote Desktop Connections on the management station, do the following:
1. Right-click the My Computer icon on your desktop and select the Properties option. The
System Properties dialog appears.
2. Click the Remote tab.
3. Select the Allow users to connect remotely to this computer check box and click OK.
To connect to the management station from the remote terminal:
• On Windows XP, select Start > All Programs > Accessories > Communications > Remote
Desktop Connection.
• On Windows Server 2003, select Start > Administrative > Tools > Remote Desktops. To
connect to a Windows 2003 console, use the /console switch with the Remote Desktop
Connection application. This is present on the latest version available at www.microsoft.com
and on Windows Server 2003. (This version is a 32-bit program available on both the 32-bit
and 64-bit Windows Server 2003 operating systems.)
Telnet
Because the nPartition commands are executed from a command prompt, you can use a telnet
application (either the telnet command in Windows or a third-party application, such as Reflection
Setting up the management station 23