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
similar to the following should result (the specific values will be different for each machine; if
obvious errors occur, you should uninstall and then reinstall the WMI Mapper component):
Instances of [Win32_ComputerSystem] (1 instances):
Instance of Win32_ComputerSystem:
{
AdminPasswordStatus = 3
AutomaticResetBootOption = TRUE
AutomaticResetCapability = TRUE
BootROMSupported = TRUE
BootupState = "Normal"
Caption = "FCTMARTIN"
ChassisBootupState = 3
CreationClassName = "Win32_ComputerSystem"
CurrentTimeZone = -420
DaylightInEffect = FALSE
Description = "AT/AT COMPATIBLE"
Domain = "DOMAIN-NAME"
DomainRole = 3
FrontPanelResetStatus = 3
InfraredSupported = FALSE
KeyboardPasswordStatus = 3
Manufacturer = "Hewlett-Packard"
Model = "HP Kayak PC"
Name = "HOSTNAME"
NetworkServerModeEnabled = TRUE
NumberOfProcessors = 1
OEMStringArray[?] = "SMBIOS 2.3 BIOS with HP DMI extensions "
PauseAfterReset = -1
PowerOnPasswordStatus = 3
PowerState = 0
PowerSupplyState = 3
PrimaryOwnerName = "Joe Owner"
ResetCapability = 1
ResetCount = -1
ResetLimit = -1
Roles[?] = "LM_Workstation LM_Server NT Server_NT Backup_Browser "
Status = "OK"
SystemStartupDelay = 30
SystemStartupOptions[?] = ""Microsoft Windows 2000 Server" /fastdetect "
SystemStartupSetting = 0
SystemType = "X86-based PC"
ThermalState = 3
TotalPhysicalMemory = 1341636608
UserName = "DOMAIN-NAME\jowner"
WakeUpType = 6
}
Verify WMI Mapper service with HTTP connection
This set of commands verifies that the WMI Mapper service is running and properly responding
to client requests. Note that running the nPartition commands with the -g option (to connect
remotely to the MP on the partitionable system) does not go through the WMI Mapper service,
so this test does not apply for those cases.
The following test uses a basic HTTP connection to the service, which eliminates any possible
SSL/certificate problems. By default, the WMI Mapper service is configured for HTTPS/SSL
connections only. Therefore this test will not work without first reconfiguring the service for
HTTP connections. See the installed file %PEGASUS_HOME%\ConfigREADME.txt for
instructions on how to configure the service. To test the default configuration (HTTPS connections),
you should skip this test and use the next one instead.
Open a Command Prompt window and run the following commands:
set CIM_HOST=localhost
108 Troubleshooting