Installation guide

6
Known issues
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://support.qlogic.com
Email: [e-mail]
Phone: [phone]
Problem
No.
Description
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.
6360 On a HDS9960 2Gb device, changing the port speed to 1Gb and then to auto-negotiate causes the port to
stay at 1Gb. Traffic is not interrupted, but is only running at 1Gb speed. Reset the port and set to auto-
negotiate to recover.
6528 After a SANbox2-64 hotswap insert or replace operation, donor ports, used for extended distance
applications, do not continue to provide the port assigned credits. An alarm is issued and the donor port is
downed.
6529 In CLIsh, “show port xx” does not display correct values for most of the top half of the display when “xx” is
less than 10. If “xx” is 10 or greater, the values displayed are correct.