HP Integrity rx5670 Windows Integrity nPartition Guide - Page 141

Verify WMI Mapper service with HTTP connection, SystemType = X86-based PC

Page 141 highlights

Troubleshooting Checking component installation and operation 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 Management Processor 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 set CIM_USER= set CIM_PASSWORD= Chapter 6 141

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

Troubleshooting
Checking component installation and operation
Chapter 6
141
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 Management Processor 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
set CIM_USER=<domain\username>
set CIM_PASSWORD=<password for user, above>