HP 4400 HP B-series Fabric OS 6.3.2d Release Notes (5697-1105, July 2011) - Page 26

Virtual Fabrics, Licensing behavior, Adaptive Networking/flow-based QoS prioritization

Page 26 highlights

• Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is disruptive if ethsw is enabled on Fabric OS 6.3. • Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is nondisruptive if ethsw has never been enabled with Fabric OS 6.3. • HA Failover of CP blades in DC SAN Backbone or DC04 SAN Director also results in disruption of traffic through the 10/24 blades. • Connecting a 2408 FCoE Converged Network Switch to an FCR-capable switch with fcrbcast config enabled will cause a storm of broadcast traffic, resulting in termination of iswitchd. • When rebooting a DC SAN director or DC04 SAN director with DC SAN 10/24 FCoE blade, Qlogic CNA and LSAN zoning, the switch becomes unresponsive for a period of time. This is due to the CNA sending excessive MS queries to the switch. • A DC SAN 10/24 FCoE blade installed in the highest numbered slot of a DC SAN director or DC04 SAN director does not send out FIP unsolicited advertisements. Therefore, it does not support FCoE functionality when installed in this slot. Virtual Fabrics • On VF-capable platforms, the VF feature (initially supported with Fabric OS 6.2.0a) must be enabled in order to utilize the related capabilities, including logical switches and logical fabrics. Any switch shipped from the factory with 6.3.1a or later installed that is capable of supporting VF will have it enabled by default. • When creating logical fabrics that include switches that are not VF-capable, it is possible to have two logical switches with different FIDs in the same fabric. Be sure to verify that the FIDs match for all switches in the same logical fabric. • In order to support non-disruptive Hot Code Load on an HP 8/40 SAN Switch with VF enabled, the total zoning DB size for the entire chassis should not exceed 1 MB. • A switch with VF enabled cannot participate in a fabric that uses IP filter or password database distribution or administrative domains. You must disable the VF feature before deploying it in a fabric that uses these features. • VF is not supported on the 1606 Extension SAN switch. • VF-dedicated ISLs are supported on the DC SAN Director Switch Multiprotocol Extension Blade. XISLs are not supported. • On an HP 8/40 SAN switch with Virtual Fabrics enabled, ports may be re-initialized causing frame drops during a hot code load (HCL) if the switch has a zoning database that is 1MB or larger in size. To prevent this from occurring, ensure the zoning database is less than 1MB when activating new firmware. Licensing behavior When operating a switch with Fabric OS 6.3.x, some licenses may be displayed as Unknown. This is due to changes in licensing requirements for some features that no longer require a license key and may still be installed on a switch. Adaptive Networking/flow-based QoS prioritization • When using QoS in a fabric with 4-Gb ports or switches, Fabric OS 6.0 or later must be installed on all products in order to pass QoS information. E_Ports from the DC SAN Backbone Director or DC04 SAN Director to other switches must come up after 6.0 is running on those switches. • Flow-based QoS is not supported on any 8-Gb Fibre Channel blades in the 4/256 SAN Director. • Any products that cannot operate with Fabric OS 6.x cannot exist in a fabric with flow-based QoS. Major problems occur if previous-generation 2-Gb products exist in the fabric. 26

  • 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

Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is disruptive if
ethsw
is enabled on Fabric OS
6.3.
Downgrade from Fabric OS 6.3 to 6.1.2_cee1 is nondisruptive if
ethsw
has never been enabled
with Fabric OS 6.3.
HA Failover of CP blades in DC SAN Backbone or DC04 SAN Director also results in disruption
of traffic through the 10/24 blades.
Connecting a 2408 FCoE Converged Network Switch to an FCR-capable switch with
fcrbcast
config
enabled will cause a storm of broadcast traffic, resulting in termination of
iswitchd
.
When rebooting a DC SAN director or DC04 SAN director with DC SAN 10/24 FCoE blade,
Qlogic CNA and LSAN zoning, the switch becomes unresponsive for a period of time. This is due
to the CNA sending excessive MS queries to the switch.
A DC SAN 10/24 FCoE blade installed in the highest numbered slot of a DC SAN director or
DC04 SAN director does not send out FIP unsolicited advertisements. Therefore, it does not support
FCoE functionality when installed in this slot.
Virtual Fabrics
On VF-capable platforms, the VF feature (initially supported with Fabric OS 6.2.0a) must be enabled
in order to utilize the related capabilities, including logical switches and logical fabrics. Any switch
shipped from the factory with 6.3.1a or later installed that is capable of supporting VF will have
it enabled by default.
When creating logical fabrics that include switches that are not VF-capable, it is possible to have
two logical switches with different FIDs in the same fabric. Be sure to verify that the FIDs match
for all switches in the same logical fabric.
In order to support non-disruptive Hot Code Load on an HP 8/40 SAN Switch with VF enabled,
the total zoning DB size for the entire chassis should not exceed 1 MB.
A switch with VF enabled cannot participate in a fabric that uses IP filter or password database
distribution or administrative domains. You must disable the VF feature before deploying it in a
fabric that uses these features.
VF is not supported on the 1606 Extension SAN switch.
VF-dedicated ISLs are supported on the DC SAN Director Switch Multiprotocol Extension Blade.
XISLs are not supported.
On an HP 8/40 SAN switch with Virtual Fabrics enabled, ports may be re-initialized causing
frame drops during a hot code load (HCL) if the switch has a zoning database that is 1MB or
larger in size. To prevent this from occurring, ensure the zoning database is less than 1MB when
activating new firmware.
Licensing behavior
When operating a switch with Fabric OS 6.3.
x
, some licenses may be displayed as
Unknown
. This
is due to changes in licensing requirements for some features that no longer require a license key and
may still be installed on a switch.
Adaptive Networking/flow-based QoS prioritization
When using QoS in a fabric with 4-Gb ports or switches, Fabric OS 6.0 or later must be installed
on all products in order to pass QoS information. E_Ports from the DC SAN Backbone Director
or DC04 SAN Director to other switches must come up after 6.0 is running on those switches.
Flow-based QoS is not supported on any 8-Gb Fibre Channel blades in the 4/256 SAN Director.
Any products that cannot operate with Fabric OS 6.x cannot exist in a fabric with flow-based
QoS. Major problems occur if previous-generation 2-Gb products exist in the fabric.
26