HP Xw460c HP Integrated Lights-Out 2 User Guide for Firmware 1.75 and 1.77 - Page 106

Using a remote Windows Kernel Debugger, IP Address = <String&gt

Page 106 highlights

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Debug (com2)" /fastdetect /debug /debugport=com2 /baudrate=115200 If the server is configured to boot into debug mode, and a normal virtual serial port connection is established while the server is booting, several bytes of debug data are sent to the virtual serial port client. To avoid this, do not boot the server into debug mode while a normal virtual serial port connection is in use. Serial Port Configuration displays server configuration information, available serial ports, and virtual serial port status. Status appears as: • Available-The virtual serial port is not in use • In use-Normal mode when the virtual serial port is connected normally • In use-Raw mode when the WiLODbg.exe utility is used to connect When the virtual serial port is in use, the Disconnect button is enabled and can be used to terminate any type of virtual serial port connection. Using the Disconnect features to terminate a virtual serial port connection that was established using SSH completely disconnects the SSH connection and does not return to the hpiLO-> prompt. A similar disconnect occurs if the virtual serial port connection is established using telnet. If a remote serial connection applet is used to make the connection from a browser, the applet is disconnected. The applet window must be closed and reopened to reestablish the remote serial connection. Using a remote Windows Kernel Debugger To start a Windows® Kernel Debugger, you must launch the WiLODbg.exe utility on a client system that has Microsoft® WinDBG.exe or KD.exe installed, and then reboot the remote server into debug mode to attach the debugger. WiLODbg automatically launches WinDBG.exe or KD.exe. For example: WiLODbg [ -c CommandLine][ -e][ -k][ -p Password][ -s SocketNumber][ -t][ -u Username] If a parameter has whitespace in it, enclose it in quotes. Required Parameters: IP Address = -is the IP Address in dot format or full UNC name. is a series of characters. Required parameters must occur in the order shown in the example. Optional Parameters: • -c CommandLine = -Provides additional command line parameters to the selected debugger. If there are embedded spaces or dashes (-) enclose them in quotation marks. = A series of characters. • -e = -Turns on encryption for the communications link. Encryption only works with the telnet option in this version. Default is disabled. • -k = -Use KD instead of WinDbg. Default is to use WinDbg. • -p Password = -Sets the Password to use for iLO 2 login. If not provided, password is requested. is a series of characters. • -s SocketNumber = -Sets the socket number for connection to iLO 2. SocketNumber must match the Raw Serial Data Port setting on the iLO 2 you are connecting to. Socket 3002 is the default. = [sign]digits. • -t = -Uses a telnet connection indirectly through this utility from the debugger. Socket connection to socket 3002 is the default setting. Using iLO 2 106

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235

Using iLO 2 106
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Debug (com2)"
/fastdetect /debug /debugport=com2 /baudrate=115200
If the server is configured to boot into debug mode, and a normal virtual serial port connection is
established while the server is booting, several bytes of debug data are sent to the virtual serial port
client. To avoid this, do not boot the server into debug mode while a normal virtual serial port
connection is in use.
Serial Port Configuration displays server configuration information, available serial ports, and virtual
serial port status. Status appears as:
Available—The virtual serial port is not in use
In use—Normal mode when the virtual serial port is connected normally
In use—Raw mode when the WiLODbg.exe utility is used to connect
When the virtual serial port is in use, the Disconnect button is enabled and can be used to terminate any
type of virtual serial port connection. Using the Disconnect features to terminate a virtual serial port
connection that was established using SSH completely disconnects the SSH connection and does not
return to the
</>hpiLO->
prompt. A similar disconnect occurs if the virtual serial port connection is
established using telnet. If a remote serial connection applet is used to make the connection from a
browser, the applet is disconnected. The applet window must be closed and reopened to reestablish the
remote serial connection.
Using a remote Windows Kernel Debugger
To start a Windows® Kernel Debugger, you must launch the WiLODbg.exe utility on a client system that
has Microsoft® WinDBG.exe or KD.exe installed, and then reboot the remote server into debug mode to
attach the debugger. WiLODbg automatically launches WinDBG.exe or KD.exe. For example:
WiLODbg <IP Address>[ -c CommandLine][ -e][ -k][ -p Password][ -s
SocketNumber][
-t][ -u Username]
If a parameter has whitespace in it, enclose it in quotes.
Required Parameters:
IP Address = <String>
—is the IP Address in dot format or full UNC name. <String> is a series of
characters. Required parameters must occur in the order shown in the example.
Optional Parameters:
-c CommandLine = <String>
—Provides additional command line parameters to the selected
debugger. If there are embedded spaces or dashes (-) enclose them in quotation marks. <String> =
A series of characters.
-e = <Boolean>
—Turns on encryption for the communications link. Encryption only works with
the telnet option in this version. Default is disabled.
-k = <Boolean>
—Use KD instead of WinDbg. Default is to use WinDbg.
-p Password = <String>
—Sets the Password to use for iLO 2 login. If not provided, password
is requested.
<String>
is a series of characters.
-s SocketNumber = <Integer>
—Sets the socket number for connection to iLO 2.
SocketNumber must match the Raw Serial Data Port setting on the iLO 2 you are connecting to.
Socket 3002 is the default.
<Integer> = [sign]digits.
-t = <Boolean>
—Uses a telnet connection indirectly through this utility from the debugger. Socket
connection to socket 3002 is the default setting.