Dell Brocade 6520 Release Notes v1.0 - Page 39

Virtual Fabrics, Zoning, Miscellaneous

Page 39 highlights

Virtual Fabrics  When creating Logical Fabrics that include switches that are not Virtual Fabrics capable, it is possible to have two Logical Switches with different FIDs in the same fabric connected via a VF incapable switch. Extra caution should be used to verify the FIDs match for all switches in the same Logical Fabric.  A switch with Virtual Fabrics enabled may not participate in a fabric that is using Password Database distribution or Administrative Domains. The Virtual Fabrics feature must be disabled prior to deploying in a fabric using these features. Zoning  Support for up to 2MB zone database in a fabric with only DCX/DCX-4S/DCX8510 systems. The presence of any other platform in the fabric will limit the maximum zone database to 1MB. Please note that there is no enforcement by FOS 7.1 to restrict users to operate within a zone database limit it is the responsibility of the user to not exceed this limit.  There are limitations to zoning operations that can be performed from a FOS v6.x switch that is in the same fabric as a FOS v7.0 or later switch if the FOS v6.x switch is not running the recommended firmware version. Please see Fabric OS Interoperability section for details. Beginning with the FOS v6.2.0 release, all WWNs containing upper-case characters are automatically converted to lower-case when associated with a zone alias and stored as part of a saved configuration on a switch. For example, a WWN entered as either "AA.BB.CC.DD.EE.FF.GG.HH" or "aa.bb.cc.dd.ee.ff.gg.hh" when associated with a zone alias will be stored as "aa.bb.cc.dd.ee.ff.gg.hh" on a switch operating with FOS v6.2.0 or later. This behavioral change in saved zone alias WWN members will not impact most environments. However, in a scenario where a switch with a zone alias WWN member with upper case characters (saved on the switch with pre-FOS v6.2.0 code) is merged with a switch with the same alias member WWN in lower case characters, the merge will fail, since the switches do not recognize these zoning configurations as being the same. For additional details and workaround solutions, please refer to the latest FOS Admin Guide updates or contact Brocade Customer Support. Miscellaneous  Using a Windows anonymous FTP server for supportsave collection When using anonymous ftp, to avoid long delays or failure of simultaneous supportsave collections when AP blades are present in a director chassis, the number of unlimited anonymous users for a Windows FTP server should be configured as follows: Number of anonymous FTP connections = (Number of director chassis) + (Number of installed Application Blades x 3)  RASlog message AN-1010 may be seen occasionally indicating "Severe latency bottleneck detected". Even though it is a "Warning" message, it is likely to be a false alarm and can be ignored.  POST diagnostics for the Brocade 5100 have been modified beginning with FOS v6.3.1b and v6.4.0 to eliminate an "INIT NOT DONE" error at the end of an ASIC diagnostic port loopback test. This modification addresses BL-1020 Initialization errors encountered during the POST portloopbacktest. (Defect 263200)  It is important to note that the outputs of slotshow -p and chassishow commands also display the maximum allowed power consumption per slot. These are absolute maximum values and should not be confused with the real-time power consumption on 16G blades. The chassisshow command has a "Power Usage (Watts):" field that shows the actual power consumed in real-time on 16G blades. Fabric OS v7.1.0a Release Notes v1.0 Page 39 of 41

  • 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

Fabric OS v7.1.0a Release Notes v1.0
Page 39 of 41
Virtual Fabrics
When creating Logical Fabrics that include switches that are not Virtual Fabrics capable, it is possible
to have two Logical Switches with different FIDs in the same fabric connected via a VF incapable
switch.
Extra caution should be used to verify the FIDs match for all switches in the same Logical
Fabric.
A switch with Virtual Fabrics enabled may not participate in a fabric that is using Password Database
distribution or Administrative Domains.
The Virtual Fabrics feature must be disabled prior to deploying
in a fabric using these features.
Zoning
Support for up to
2MB zone database
in a fabric with only DCX/DCX-4S/DCX8510 systems. The
presence of any other platform in the fabric will limit the maximum zone database to 1MB. Please
note that there is no enforcement by FOS 7.1 to restrict users to operate within a zone database limit -
it is the responsibility of the user to not exceed this limit.
There are limitations to zoning operations that can be performed from a FOS v6.x switch that is in the
same fabric as a FOS v7.0 or later switch if the FOS v6.x switch is not running the recommended
firmware version. Please see Fabric OS Interoperability section for details.
Beginning with the FOS v6.2.0 release, all WWNs containing upper-case characters are automatically
converted to lower-case when associated with a zone alias and stored as part of a saved configuration
on a switch.
For example, a WWN entered as either “AA.BB.CC.DD.EE.FF.GG.HH” or
“aa.bb.cc.dd.ee.ff.gg.hh” when associated with a zone alias will be stored as “aa.bb.cc.dd.ee.ff.gg.hh”
on a switch operating with FOS v6.2.0 or later.
This behavioral change in saved zone alias WWN members will not impact most environments.
However, in a scenario where a switch with a zone alias WWN member with upper case characters
(saved on the switch with pre-FOS v6.2.0 code) is merged with a switch with the same alias member
WWN in lower case characters, the merge will fail, since the switches do not recognize these zoning
configurations as being the same.
For additional details and workaround solutions, please refer to the latest FOS Admin Guide updates
or contact Brocade Customer Support.
Miscellaneous
Using a Windows anonymous FTP server for supportsave collection
When using anonymous ftp, to avoid long delays or failure of simultaneous supportsave
collections when AP blades are present in a director chassis, the number of unlimited
anonymous users for a Windows FTP server should be configured as follows:
Number of anonymous FTP connections = (Number of director chassis)
+
(Number of
installed Application Blades
x
3)
RASlog message AN-
1010 may be seen occasionally indicating “
Severe latency bottleneck
detected”
.
Even though it is a “Warning” message, it
is likely to be a false alarm and can be
ignored.
POST diagnostics for the Brocade 5100 have been modified beginning with FOS v6.3.1b and
v6.4.0 to eliminate an “INIT NOT DONE” error at the end of an ASIC diagnostic port loopback
test. This modification addresses BL-1020 Initialization errors encountered during the POST
portloopbacktest. (Defect 263200)
It is important to note that the outputs of slotshow
p and chassishow commands also
display the maximum allowed power consumption per slot. These are absolute maximum
values and should not be confused with the real-time power consumption on 16G blades. The
chassisshow command has a “Power Usage (Watts):” field that shows the actual power
consumed in real-time on 16G blades.