HP StorageWorks 2/16V Brocade Web Tools Administrator's Guide - Supporting Fab - Page 254

General Web Tools limitations, Continued

Page 254 highlights

19 General Web Tools limitations TABLE 14 Area Web Tools limitations (Continued) Details Firmware download Firmware downgrade There are multiple phases to firmware download and activation. When Web Tools reports that firmware download has completed successfully, this indicates that a basic sanity check, package retrieval, package unloading, and verification was successful. Web Tools forces a full package install. A reboot is required to activate the newly downloaded firmware. This reboot is done automatically; however, although Web Tools screens will continue to be visible during the reboot, they will not be available. Wait approximately 10 minutes to ensure that all of the application windows have been restored. If Web Tools fails to respond after 20 minutes, you might need to close all Web Tools applications windows and restart them, or to contact your system administrator for network assistance. The Web Tools loss of network connectivity during a failover or reboot (initiated though the firmwareDownload) varies for different configurations: Brocade 24000 and 48000 directors: loss of network connectivity is up to 5 minutes if the power-on self-test (POST) is disabled. If POST is enabled, the loss of network connectivity can exceed 5 minutes. Brocade 200E, 3250, 3850, 3900, 4012, 4016, 4018, 4020, 4024, 4100, 4900, 5000, and 7500 switches: loss of network connectivity is up to 1 minute if POST is disabled. If POST is enabled, the loss of network connectivity can exceed 1 minute. If you try to run Web Tools on a switch after downgrading the firmware, Web Tools may not open. This is due to the presence of old application cache files in Java. The workaround is to delete the application cache files using the Java Control Panel. HTTP timeout Java Plug-in Java Plug-in Very occasionally, you might see the following message when you try to get data from a switch or to send a request to the switch: Failed to get switch response. Please verify the status of your last operation and try again if necessary. This indicates that an HTTP request did not get a response. The request was sent to the switch, but the connection was down, probably caused by a temporary loss of the Web server on the switch. Due to the nature of an HTTP connection, Web Tools will report this error after a 90-second default timeout. In this case, verify the status of your last request, using telnet to check related status, or click the Refresh button from the Web Tools application you were working on to retrieve related data. If your request did not get through to the switch, resubmit it. Executing a refresh from Web Tools retrieves a copy of switch data at that moment; the data you entered can be lost if it had not already committed to the switch. If you remove the certificate (not recommended) from the Java Control Panel, you must close and reopen the browser for the certificate removal to take effect. If you have a Web Tools session open and you open a second session using the File > New browser menu, this results in unexpected behavior of the original Web Tools session. For example, you cannot change Admin Domains in the second session. Web Tools supports only one browser instance per JRE, and when you open another window using the File > New menu, the two windows share the same JRE environment. Workaround: Open two independent browser sessions. 232 Web Tools Administrator's Guide Publication Number: 53-1000435-01

  • 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
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266

232
Web Tools Administrator’s Guide
Publication Number: 53-1000435-01
General Web Tools limitations
19
Firmware download
There are multiple phases to firmware download and activation. When Web Tools
reports that firmware download has completed successfully, this indicates that a basic
sanity check, package retrieval, package unloading, and verification was successful.
Web Tools forces a full package install.
A reboot is required to activate the newly downloaded firmware. This reboot is done
automatically; however, although Web Tools screens will continue to be visible during
the reboot, they will not be available. Wait approximately 10 minutes to ensure that all
of the application windows have been restored. If Web Tools fails to respond after 20
minutes, you might need to close all Web Tools applications windows and restart them,
or to contact your system administrator for network assistance.
The Web Tools loss of network connectivity during a failover or reboot (initiated though
the
firmwareDownload
) varies for different configurations:
Brocade 24000 and 48000 directors:
loss of network connectivity is up to 5 minutes if
the power-on self-test (POST) is disabled. If POST is enabled, the loss of network
connectivity can exceed 5 minutes.
Brocade 200E, 3250, 3850, 3900, 4012, 4016, 4018, 4020, 4024, 4100, 4900,
5000, and 7500 switches:
loss of network connectivity is up to 1 minute if POST is
disabled. If POST is enabled, the loss of network connectivity can exceed 1 minute.
Firmware downgrade
If you try to run Web Tools on a switch after downgrading the firmware, Web Tools may
not open. This is due to the presence of old application cache files in Java. The
workaround is to delete the application cache files using the Java Control Panel.
HTTP timeout
Very occasionally, you might see the following message when you try to get data from a
switch or to send a request to the switch:
Failed to get switch response. Please verify the status
of your last operation and try again if necessary.
This indicates that an HTTP request did not get a response. The request was sent to the
switch, but the connection was down, probably caused by a temporary loss of the Web
server on the switch. Due to the nature of an HTTP connection, Web Tools will report
this error after a 90-second default timeout.
In this case, verify the status of your last request, using telnet to check related status,
or click the
Refresh
button from the Web Tools application you were working on to
retrieve related data. If your request did not get through to the switch, resubmit it.
Executing a refresh from Web Tools retrieves a copy of switch data at that moment; the
data you entered can be lost if it had not already committed to the switch.
Java Plug-in
If you remove the certificate (not recommended) from the Java Control Panel, you must
close and reopen the browser for the certificate removal to take effect.
Java Plug-in
If you have a Web Tools session open and you open a second session using the
File
>
New
browser menu, this results in unexpected behavior of the original Web Tools
session. For example, you cannot change Admin Domains in the second session.
Web Tools supports only one browser instance per JRE, and when you open another
window using the File > New menu, the two windows share the same JRE environment.
Workaround
: Open two independent browser sessions.
TABLE 14
Web Tools limitations
(Continued)
Area
Details