HP 4400 HP StorageWorks Fabric OS 6.4.0c Release Notes (5697-0703, September 2 - Page 30

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 30 highlights

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 VMware ESX Server Environments for best implementation practices. This document can be downloaded from the following HP website: http://www.hp.com/support/manuals Under storage, select Storage networking, and then select the appropriate switch under B-series Switches. Bottleneck detection Due to memory constraints, when using Bottleneck Detection on the 4/256 SAN Director, a maximum of 100 ports should be configured and enabled for monitoring at any time. FCR backbone fabric ID changes • With 8Gb director blades, the switch must be disabled to change the backbone fabric ID. 30

  • 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
shipped from the factory with 6.3.1a or later installed that is capable of supporting VF has it en-
abled 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
VMware ESX Server Environments
for best implementation practices. This document can be downloaded
from the following HP website:
h
t
tp://w
w
w
.hp
.co
m/su
ppo
r
t/man
uals
Under
storage
, select
Storage networking
, and then select the appropriate switch under
B-series
Switches
.
Bottleneck detection
Due to memory constraints, when using Bottleneck Detection on the 4/256 SAN Director, a maximum
of 100 ports should be configured and enabled for monitoring at any time.
FCR backbone fabric ID changes
•
With 8Gb director blades, the switch must be disabled to change the backbone fabric ID.
30