Firmware Release Notes

Version 1.3.25
50207-06 Rev A
This software is licensed by QLogic for use by its customers only.
Copyright (c) 2001 QLogic Corporation
All rights reserved
Version 1.3.25 is a feature release of firmware for the QLogic SANbox2 switch. If using
the SANbox Manager fabric management application, you must use SANbox Manager
version 1.03.28 in conjunction with this firmware.
TM

New Features in this Release

Version 1.3.25 adds the following features:
Simple Broadcast Support Broadcast is supported on the SANbox2 switch, which
allows for TCP/IP support. Broadcast is implemented using the proposed standard
specified in "Multi-Switch Broadcast for FC-SW-3", T11 Presentation Number
T11/02-031v0. FSPF is used to setup a fabric spanning tree used in transmission of
broadcast frames. Broadcast frames are retransmitted on all ISLs indicated in the
spanning tree and all online F/FL ports. Broadcast zoning is supported with Access
Control List (ACL) and Virtual Private Fabric (VPF) hard zones. When a broadcast
frame is received, these hard zones are enforced at the F/FL port. If the originator of
the broadcast is in a hard zone, the frame is retransmitted on all online F/FL ports
within the hard zone. If the originator of the broadcast frame is not in a hard zone,
the frame is retransmitted on online F/FL ports that are not in a hard zone.
This feature is enabled by default. To disable this feature, set the broadcastEnable
flag to False via the CLIsh set config switch command.

LINIT (Loop Initialize) - LINIT is an ELS command that causes a loop init to occur
on a remote port. It is initiated by a remote device, rather than a management entity.
The LINIT ELS frame is autorouted by the fabric to the destination loop port, where
it is vectored up to the processor for processing.

On-line Diagnostics This feature allows for a port diagnostic capability while the
port is operational, or online. This feature can be used via the CLIsh test <port>
online command.

Brocade Silkworm 3800 Compatibility This release of SANbox2 firmware now

supports the Brocade 3800 firmware, 3.0.2a. Refer to the Interoperability section for
more details.

SNMP Proxy Support In a fabric consisting entirely of SANbox2 switches, a

single switch can proxy for the entire fabric. This single switch can also proxy traps
for the entire fabric. To obtain traps for mixed SANbox 1Gb and SANbox2 switches,
you will need a separate SANbox 1Gb proxy switch and a SANbox2 proxy switch.

Remote Logging Logs can now be spooled remotely as well as being written to
local flash. To use this feature, set the RemoteLogEnable flag to True via the
CLIsh set setup system command. Admin mode is required. The
LogHostIPAddress must be set to the IP address of a UNIX machine that is running
syslog.
The following is an example of how to set up the syslog for remote logging.
<Example> Using Linux Red Hat 6.2 (kernel version: 2.2.14-5)
cd etc/rc.d/init.d
edit the script syslog
change the line daemon syslogd -m 0 to add the r so the line now reads
daemon syslog -m 0 -r
save and exit
type ./syslog stop
type ./syslog start
to see the log type, type tail -f /var/log/messages
For Windows NT, there are third-party applications that will accommodate remote
logging.

Menu Driven Telnet - In Forced Prom Mode, we no longer support http. Menu
driven telnet sessions from an Ethernet or Serial connection is now supported.
Procedure is as follows:
(1) Power down the switch
(2) Push and hold the Flasher Reset button and power up the switch, wait until both
the power and heartbeat LEDs 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:
2

Documentation
Installation, setup and management of the SANbox2 switch are described in the
following manuals. These manuals are available on the distribution CD.

SANbox2 Switch Management User's Manual, Publication No 59022-03 Rev. B

SANbox2-16 Fibre Channel Switch Installer's/User's Manual, Publication No 5902103 Rev. B

Installing the Firmware via telnet

The following procedure should be used, to download Version 1.3.25:
After downloading new firmware from QLogic, change directory to the directory
where the new firmware is located.
ftp to the switch
login using username images, password images
enter the following commands:
> bin
> put fullimage.XXX (where XXX represents the version of the firmware)
> quit
telnet to the switch
login using username: admin, password: password
enter the following commands:
> admin start
> image unpack fullimage.XXX
reset the switch (resetting switch will disrupt traffic)
Interoperability

SANbox The SANbox2 switch is fully interoperable with the SANbox 1Gb switch
when running in E_Port mode. Interoperation requires firmware release version
4.01.45 or later, for the SANbox. To obtain this release, contact QLogic Technical
Support. Contact information is listed at the end of these release notes.

MKII - The SANbox2 switch does not support the legacy T_Port mode and therefore
does not interoperate with MKII switches.

Brocade Silkworm 2400/2800; Firmware supported: 2.4.1c

Configuring the Brocade 2400/2800 switch:

Certain configuration parameters need to be set on the Brocade switch before it will
operate with a standards compliant switch. The following parameters can be changed
with the Brocade telnet interface.
switch:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no] y
VC Encoded Address Mode: (0..1) [0]
Switch Operating Mode (yes, y, no, n): [no] y
Interoperability Mode: (0..1) [1]
Zoning Operation parameters (yes, y, no, n): [no] y
Standard Mode: (0..1) [1]
In a mixed fabric with SANbox2, Brocade and McData switches, Domain IDs must
be in the 0x61-7f range. If a SANbox 1Gb switch is in the fabric, this is further
restricted to 0x61-6f or 70-7f. The Domain ID can be set with the Brocade telnet
interface.
switch:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no] y
Domain: (97..127) [97]
Known Issues with Brocade/SANbox2 operation:
The SANbox2 switch supports 2 modes of treating devices when there is no
active zoneset, either visible to each other or visible to none. When operating with
a Brocade switch, the SANbox2 switch should be set to no orphan visibility. Do
this by using the CLIsh command set config zoning to set Default to None.
When zoning, the SANbox2 allows you to specify zone members as WWNs,
domain/portNos, or by Fibre Channel address. Brocade switches accept only the
WWN specification.

Brocade Silkworm 3800; Firmware supported: 3.0.2a

Configuring the Brocade 3800 switch:
Certain configuration parameters need to be set on the Brocade switch before it will
operate with a standards compliant switch. The following commands must be entered
from the Brocade telnet interface.
switch:admin> switchdisable
switch:admin> interopmode 1

switch:admin> fastboot
In a mixed fabric with SANbox2, Brocade and McData switches, Domain IDs must
be in the 0x61-7f range. If a SANbox 1Gb switch is in the fabric, this is further
restricted to 0x61-6f or 70-7f.The Domain ID can be set with the Brocade telnet
interface.
switch:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no] y
Domain: (97..127) [97]
Known Issues with Brocade/SANbox2 operation:
Minor anomalies have been observed in Domain ID assignment. To avoid these,
it is advisable to configure each switch with a unique Domain ID and to lockdown
the Domain Ids.
The SANbox2 switch supports 2 modes of treating devices when there is no
active zoneset, either visible to each other or visible to none. When operating with
a Brocade switch, the SANbox2 switch should be set to no orphan visibility. Do
this by using the CLIsh command set config zoning to set Default to None.
When zoning, the SANbox2 allows you to specify zone members as WWNs,
domain/portNos, or by Fibre Channel address. Brocade switches accept only the
WWN specification.
Brocade mode is unsupported with the Brocade Silkworm 3800 switch.
Furthermore, this compatibility mode will be removed in a future release.

McData ED-5000
Firmware supported: 04.00.00.01
Configuring the McData switch:
Certain configuration parameters need to be set on the McData switch before it will
operate with a standards compliant switch. The following parameter can be changed
with the McData GUI.
-

In the Hardware View window, bring up the Operating Mode window and
set Interop Mode to Open Fabric 1.0
In a mixed fabric with SANbox2, Brocade and McData switches, Domain
IDs must be in the 0x61-7f range. If a SANbox 1Gb switch is in the fabric,
this is further restricted to 0x61-6f or 70-7f. Note that in the McData GUI,
the Domain IDs are listed as 1-15 which does equate to 0x61-7f.

Known Issues with McData/SANbox2 operation:

The McData switch does not support Port and FC Address zoning. Their use on
the SANbox2 switch should be avoided, if connected to a McData switch.
As with the Brocade switch, orphan visibility should be off. Do this by using the
CLIsh command set config zoning to set Default to None.

Problems corrected in this release

Problem
No.

Description

3741

If you enable Authentication Trap, a trap is never generated if the authentication fails for a SNMP
query.
AN F_RJT (reject) is not being sent when a class A frame is not forwardable.
When a soft zone crosses a hard zone, the hard zone should revert to a soft zone and it is not.
Proxy server is not supported for SNMP in this release.
TL_Port initiator support is at a beta-level for this release.

3906
4024

Known issues
Problem
No.

Description

3342

The switchs 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 LEDs 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.
If you have a fabric with SANbox2 and McData and/or Brocade switches, you cannot use
SANsurfer2 to see nameserver entries for devices attached to the Brocade or McData switch nor
can you zone them via SANsurfer2. 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.
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 3rd 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.
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 SANbox 2. This is not a switch problem. If you do not set
the JNI to loop only mode, this problem is avoided.
Zoning limits are not enforced during a zone merge with other vendor switches. If another vendors
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
There are JBODs that do not send a LIP when a drive is removed. This causes the name server
entries to remain in the table.

4199

4200

4308

4610

4654
4658
4705
4853
4658

With a mixed SANbox 1Gb and SANbox2 fabric, a TL initiator on the SANbox2 switch cannot find the
drives on a TL port connected to the SANbox 1Gb switch.
The Unzoned Name Server ignores the frame size specified in the PLOGIN.
In large fabrics, SNMP may not initialize properly. The result is that it will not respond to queries. If this
occurs, the switch can be reset, or a different switch in the fabric can be used for gathering fabric SNMP
data.
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.

Support
Please feel free to contact your QLogic approved reseller or QLogic Technical Support at
any phase of integration for assistance. QLogic Technical Support can be reached by the
following methods:
Web: http://www.qlogic.com/support/report_problem.asp
Email: [email protected]
Phone: (952) 932-4040