HP 4400 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 28

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

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 28 highlights

• 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. • The 2408 FCoE Converged Network Switch and DC SAN 10/24 FCoE blade can handle 169 small FCoE frames in bursts. If you are using the 2408 FCoE Converged Network Switch or DC SAN 10/24 FCoE blade, and you delete a large number of V_Ports with HCM, some of the V_Ports may not appear to be deleted. To correct this, disable and re-enable FCoE with the following CLI commands: switch:admin>fcoe --disable switch:admin>fcoe --enable 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 has 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. • 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. Licensing behavior When operating a switch with Fabric OS 6.3.x and later, 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 4Gb 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 8Gb 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 2Gb products exist in the fabric. • When running Adaptive Networking in Access Gateway mode, note the following: ◦ QoS takes precedence over ingress rate limiting. ◦ Ingress Rate Limiting is not enforced on trunked ports. Access Gateway device-based mapping in ESX environments Users who want to utilize Access Gateway's Device-based mapping feature in the ESX environments should refer to the Brocade Tech Note Using Brocade Access Gateway Device-Based Mapping in 28

  • 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
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
•
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.
•
The 2408 FCoE Converged Network Switch and DC SAN 10/24 FCoE blade can handle
169 small FCoE frames in bursts. If you are using the 2408 FCoE Converged Network Switch
or DC SAN 10/24 FCoE blade, and you delete a large number of V_Ports with HCM, some
of the V_Ports may not appear to be deleted. To correct this, disable and re-enable FCoE with
the following CLI commands:
switch:admin>
fcoe --disable
switch:admin>
fcoe --enable
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 has 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.
•
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.
Licensing behavior
When operating a switch with Fabric OS 6.3.
x
and later, 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 4Gb 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 8Gb 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 2Gb products exist in the fabric.
•
When running Adaptive Networking in Access Gateway mode, note the following:
◦
QoS takes precedence over ingress rate limiting.
◦
Ingress Rate Limiting is not enforced on trunked ports.
Access Gateway device-based mapping in ESX environments
Users who want to utilize Access Gateway’s Device-based mapping feature in the ESX environments
should refer to the Brocade Tech Note
Using Brocade Access Gateway Device-Based Mapping in
28