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
6 Troubleshooting
Additional information about failures or error messages is usually obtained by examining the
Application Event Log, or AEL. Locate the AEL by right-clicking on the My Computer icon on
nPartition Window Server 2003 desktop and selecting Manage from the pop-up menu. In the
Computer Management window, expand the System Tools and Event Viewer items, then select
Application by clicking on it. A list of system-wide Error, Warning, and Informational messages
displays in the right pane of the window. To view detailed information about a specific message,
double-click it.
Installation problems
Services (WMI Mapper + nPartition Provider) fail to start during installation
Possible causes for this error are:
• You must be logged in with privileges (an account in the local Administrators group) to
install/uninstall these components on the local system
• The Services Control Panel (Start > Control Panel > Administrative Tools > Services)
was open during installation; it cannot be open during installation or the services will fail
nPartition Provider fails to start during installation
This problem is caused by a conflict between the version of the OpenSSL libraries used by
nPartition commands/nPartition Provider and the versions installed by other tools. Currently,
ActivCard Gold software is one source of this conflict.
Until the problem is resolved, reinstalling WMI Mapper (WMIMapper.msi) might fix the problem
temporarily, but might also break the other software that relies on the incompatible version of
OpenSSL.
A workaround for this problem is:
1. Copy the OpenSSL dynamic link library files, or .dll’s (LIBEAY32.dll and SSLEAY32.dll)
from the %PEGASUS_HOME%\bin directory (usually at C:\Program Files\The Open
Group\WMI Mapper\bin) to:
a. the WMINParProvider directory (usually C:\Program
Files\Hewlett-Packard\WMINParProvider)
b. the ParCLI directory (usually C:\Program Files\Hewlett-Packard\nParCommands)
2. Move the string “%PEGASUS_HOME%\bin” from the front of the system path to the end
of the system path (right-click: My Computer > Properties > Advanced > Environment
Variables, and so on).
This should fix the problem for both the nPartition Tools and the other applications that were
relying on the incompatible version of OpenSLL. This problem will be fixed in a future release
of the nPartition Tools software.
Checking component installation and operation
Verify WMI Mapper installation
To verify that the WMI Mapper files are installed correctly, and are accessible through the current
system PATH, open a Command Prompt window and run the following command:
wmiop ei Win32_ComputerSystem
This command requests that WMI enumerate the instances of all known objects of type
Win32_ComputerSystem. If the WMI Mapper is installed and operating correctly, then output
Installation problems 107