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

Inability to connect to the iLO 2 processor through the NIC

Page 196 highlights

Inability to connect to the iLO 2 processor through the NIC If you cannot connect to the iLO 2 processor through the NIC, try any or all of the following troubleshooting methods: • Confirm that the green LED indicator (link status) on the iLO 2 RJ-45 connector is on. This condition indicates a good connection between the PCI NIC and the network hub. • Look for intermittent flashes of the green LED indicator, which indicates normal network traffic. • Run the iLO 2 RBSU to confirm that the NIC is enabled and verify the assigned IP address and subnet mask. • Run the iLO 2 RBSU and use the F1-Advanced tab inside of the DNS/DHCP page to see the status of DHCP requests. • Ping the IP address of the NIC from a separate network workstation. • Attempt to connect with browser software by entering the IP address of the NIC as the URL. You can see the iLO 2 Home page from this address. • Reset iLO 2. NOTE: If a network connection is established, you may have to wait up to 90 seconds for the DHCP server request. ProLiant BL p-Class servers have a Diagnostic Port available. Connecting a live network cable to the diagnostic port causes iLO 2 to automatically switch from the iLO 2 port to the diagnostic port. When switching between the diagnostic and back ports, allow one minute for the network switchover to be complete before attempting connection through the browser. Inability to log in to iLO 2 after installing the iLO 2 certificate If the iLO 2 self-signed certificate is installed permanently into some browsers and the iLO 2 is reset, you might not be able to log back in to iLO 2 because iLO 2 generates a new self-signed certificate every time it is reset. When a certificate is installed in the browser, it is indexed by the name contained in the certificate. This name is unique to each iLO 2. Every time iLO 2 resets, it generates a new certificate with the same name. To avoid this problem, do not install the iLO 2 self-signed certificate in the browser certificate store. If you want to install the iLO 2 certificate, a permanent certificate should be requested from a CA and imported into the iLO 2. This permanent certificate can then be installed in the browser certificate store. Firewall issues iLO 2 communicates through several configurable TCP/IP ports. If these ports are blocked, the administrator must configure the firewall to allow for communications on these ports. See the Administration section of the iLO 2 user interface to view or change port configurations. Proxy server issues If the Web browser software is configured to use a proxy server, it will not connect to the iLO 2 IP address. To resolve this issue, configure the browser not to use the proxy server for the IP address of iLO Troubleshooting iLO 2 196

  • 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

Troubleshooting iLO 2 196
Inability to connect to the iLO 2 processor through the NIC
If you cannot connect to the iLO 2 processor through the NIC, try any or all of the following
troubleshooting methods:
Confirm that the green LED indicator (link status) on the iLO 2 RJ-45 connector is on. This condition
indicates a good connection between the PCI NIC and the network hub.
Look for intermittent flashes of the green LED indicator, which indicates normal network traffic.
Run the iLO 2 RBSU to confirm that the NIC is enabled and verify the assigned IP address and
subnet mask.
Run the iLO 2 RBSU and use the F1-Advanced tab inside of the DNS/DHCP
page to see the status of
DHCP requests.
Ping the IP address of the NIC from a separate network workstation.
Attempt to connect with browser software by entering the IP address of the NIC as the URL. You can
see the iLO 2 Home page from this address.
Reset iLO 2.
NOTE:
If a network connection is established, you may have to wait up to 90 seconds for the
DHCP server request.
ProLiant BL p-Class servers have a Diagnostic Port available. Connecting a live network cable to the
diagnostic port causes iLO 2 to automatically switch from the iLO 2 port to the diagnostic port. When
switching between the diagnostic and back ports, allow one minute for the network switchover to be
complete before attempting connection through the browser.
Inability to log in to iLO 2 after installing the iLO 2 certificate
If the iLO 2 self-signed certificate is installed permanently into some browsers and the iLO 2 is reset, you
might not be able to log back in to iLO 2 because iLO 2 generates a new self-signed certificate every time
it is reset. When a certificate is installed in the browser, it is indexed by the name contained in the
certificate. This name is unique to each iLO 2. Every time iLO 2 resets, it generates a new certificate with
the same name.
To avoid this problem, do not install the iLO 2 self-signed certificate in the browser certificate store. If you
want to install the iLO 2 certificate, a permanent certificate should be requested from a CA and imported
into the iLO 2. This permanent certificate can then be installed in the browser certificate store.
Firewall issues
iLO 2 communicates through several configurable TCP/IP ports. If these ports are blocked, the
administrator must configure the firewall to allow for communications on these ports. See the
Administration section of the iLO 2 user interface to view or change port configurations.
Proxy server issues
If the Web browser software is configured to use a proxy server, it will not connect to the iLO 2 IP
address. To resolve this issue, configure the browser not to use the proxy server for the IP address of iLO