HP StorageWorks 8/80 Brocade EZSwitchSetup Administrator's Guide v6.2.0 (53-10 - Page 60

General limitations, EZSwitchSetup Switch Manager Limitations Continued, Problem Area, Details

Get HP StorageWorks 8/80 - SAN Switch PDF manuals and user guides View all HP StorageWorks 8/80 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 60 highlights

A General limitations TABLE 3 EZSwitchSetup Switch Manager Limitations (Continued) Problem Area Details Loss of Connection Switch Name Change Occasionally, you may see the following message when you try to retrieve data from the switch or send a request to the switch: Switch Status Checking The switch is not currently accessible. The dialog title may vary, because it indicates which module is having the problem. This is caused by the loss of HTTP connection with the switch, due to a variety of possible problems. Switch Manager automatically tries to regain the connection. While Switch Manager is trying to regain the connection, check if your Ethernet connection is still functioning. If the problem is not with the Ethernet connection, wait for Switch Manager to recover the connection and display the following message: You will have to resubmit your request after closing this message. If the temporary switch connection loss is caused by switch hot code load, or other similar operation, the Switch Explorer you are currently running can be downloaded from a different firmware version than the new one. In this case the following message displays: Switch connection is restored. The firmware version you are running is not in sync with the version currently on switch. Close your browser and re-launch Webtools. You must close Switch Manager and relaunch it to reopen the connection. If you change the switch name using EZSwitchSetup or SNMP and then open a Telnet window to verify the name change, the CLI prompt (for example, switch:admin>) displays the previous name. The Telnet prompt cannot pick up the new switch name until the switch is rebooted. Workaround: To display the correct switch name in the CLI prompt after a switch name update using EZSwitchSetup or SNMP, fastboot the switch. 48 EZSwitchSetup Administrator's Guide 53-1001193-02

  • 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
48
EZSwitchSetup Administrator’s Guide
53-1001193-02
General limitations
A
Loss of Connection
Occasionally, you may see the following message when you try to retrieve data from the
switch or send a request to the switch:
Switch Status Checking
The switch is not currently accessible.
The dialog title may vary, because it indicates which module is having the problem.
This is caused by the loss of HTTP connection with the switch, due to a variety of
possible problems. Switch Manager automatically tries to regain the connection. While
Switch Manager is trying to regain the connection, check if your Ethernet connection is
still functioning. If the problem is not with the Ethernet connection, wait for Switch
Manager to recover the connection and display the following message:
You will have to resubmit your request after closing this message.
If the temporary switch connection loss is caused by switch hot code load, or other
similar operation, the Switch Explorer you are currently running can be downloaded
from a different firmware version than the new one. In this case the following message
displays:
Switch connection is restored. The firmware version you are running is not in sync with
the version currently on switch. Close your browser and re-launch Webtools.
You must close Switch Manager and relaunch it to reopen the connection
.
Switch Name Change
If you change the switch name using EZSwitchSetup or SNMP and then open a Telnet
window to verify the name change, the CLI prompt (for example,
switch:admin>
)
displays the previous name. The Telnet prompt cannot pick up the new switch name
until the switch is rebooted.
Workaround:
To display the correct switch name in the CLI prompt after a switch name
update using EZSwitchSetup or SNMP,
fastboot
the switch.
TABLE 3
EZSwitchSetup Switch Manager Limitations (Continued)
Problem Area
Details