User`s guide

6
Known issues
Problem
No.
Description
3342
The switch’s internal system storage can occasionally become lost, if the switch is power cycled
while configuration changes are being made. To avoid this, use of “reset” rather than power cycling
is recommended.
Should it occur, the following procedure will restore the switch to operability:
(1) Power down the corrupted switch
(2) Push and hold the Flasher Reset button and power up the switch,
Wait until both the power and heartbeat LED’s are on, solid Green and Yellow respectively.
(3) Telnet into the switch using IP address 10.0.0.1
(4) Login as user “prom” with the password “prom”
(5) The following menu will be presented:
0) Exit
1) Image Unpack
2) Reset Network Config
3) Reset Password File
4) Copy Log Files
5) Remove Switch Config
6) Remake Filesystem
7) Reset Switch
Option:
(6) Enter “6” at the prompt and “y” at the warning.
(7) Enter “7” at the prompt and “y” at the warning.
(8) If you have previously saved the switch configuration, download it to the switch, using ftp with the
user “images” password “images” and with the ftp “put” command download the “configdata” file to
the switch.
(9) Telnet into the switch as user “admin”
(10) Use the CLIsh command “config restore”, or you may manually reconfigure the switch.
4199
If you have a fabric with SANbox2 and McData and/or Brocade switches, you cannot use SANbox
Manager to see nameserver entries for devices attached to the Brocade or McData switch nor can
you zone them via SANbox Manager. You can use telnet/clish to work around this problem. If you
have a SANbox 1Gb switch in the fabric, this problem does not exist.
4200
After activating a large zoneset, the CLIsh “zoning list” command did not list all zoning information.
This is a Windows only issue with the default telnet application. A 3
rd
party telnet application is
recommended on a Windows platform.
If you use the default telnet and it appears hung when you first open the session, “set term vt100” at
the telnet prompt will resolve this issue.
4308
In a SANbox2/SANbox 1Gb/Brocade/Mcdata mesh configuration, if you have a JNI initiator in loop
mode and assign the same domain ID to all switches and bring all of them online, the JNI initiator
does not log back into the same port on SANbox2. This is not a switch problem. If you do not set the
JNI to loop only mode, this problem is avoided.
4610
Zoning limits are not enforced during a zone merge with other vendor switches. If another vendor’s
switch exceeds the SANbox2 zoning limits and that zoning data is merged, the switch sends out an
alarm message letting you know that you have exceeded the zoning limits. The zoning limits that are
enforced within the SANbox2 switch are:
256 Zone sets, 256 Zones, 256 Aliases
2000 Members per zone, 2000 Members per alias, 2000 Total members
4658 A TL Initiator will be unable to discover target devices connected to non-SANbox2 switches, including
SANbox 1Gb switch, McData, and Brocade. Target devices which are to be accessed via a TL port must
be connected to a SANbox2 switch.
4705 The Unzoned Name Server ignores the frame size specified in the PLOGIN.
4981 If a device had registered (using the SCR command) to receive state changes and later unregistered
(again using SCR), we fail to stop sending them state changes.
If a VPF hard zone crosses multiple switches but doesn't contain the ISL in the zone, a nameserver query
outside the zone will show devices that are inside the zone on the remote switch. However, device access
will be prevented by hardware enforcement. Therefore, all VPF zones that overlap switches must contain
the ISL(s) in the zone.