HP Surestore Tape Library Model 20/700 HP Surestore Bridge FC 2/1 LV and FC 4/ - Page 242

General DHCP Troubleshooting, will produce a warning message stating

Page 242 highlights

General DHCP Troubleshooting What happens if the DHCP server cannot be contacted? Serial Interface: the following occurs over the serial line: the following text appears above the Main menu within the hyperterminal window, "Attempting to contact DHCP server..." After about 3 minutes, the following message appears, "Can't renew DHCP boot lease." Within Telnet: the user will see only a blank Telnet window which is not accessible. Instead of an IP address value displaying in the upper left heading of the Telnet window, "(None)" appears instead. Within half a minute, Telnet will produce a warning message stating "Connect Failed!" Within HTTP: the user will be able to submit a new web page and reboot (as is typically the case). However, since the DHCP isn't contacted, a new IP address will not be generated after reboot. Therefore, HTTP will no longer be useful since no IP address is available. The previous non-DHCP will not work either. HTTP will time out and provide a warning message to the user stating that "a connection with server could not be established." 244 General DHCP Troubleshooting Appendix D

  • 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
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260

244
General DHCP Troubleshooting
Appendix D
General DHCP Troubleshooting
What happens if the DHCP server cannot be contacted?
Serial Interface: the following occurs over the serial line: the following text
appears above the
Main
menu within the hyperterminal window,
“Attempting to contact DHCP server…”
After about 3 minutes, the
following message appears,
“Can't renew DHCP boot lease.”
Within Telnet: the user will see only a blank Telnet window which is not
accessible. Instead of an IP address value displaying in the upper left heading
of the Telnet window,
“(None)”
appears instead. Within half a minute, Telnet
will produce a warning message stating
“Connect Failed!”
Within HTTP: the user will be able to submit a new web page and reboot (as is
typically the case). However, since the DHCP isn't contacted, a new IP address
will not be generated after reboot. Therefore, HTTP will no longer be useful
since no IP address is available. The previous non-DHCP will not work either.
HTTP will time out and provide a warning message to the user stating that
“a
connection with server could not be established.”