HP StorageWorks 1606 HP StorageWorks Fabric OS 6.3.0 release notes (5697-0358, - Page 31

Adaptive Networking/flow-based QoS prioritization, FCR backbone fabric ID changes

Get HP StorageWorks 1606 - Extension SAN Switch PDF manuals and user guides View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

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.0 cannot exist in a fabric with flow-based QoS. Major problems occur if previous-generation 2-Gb products exist in the fabric. • Beginning with the Fabric OS 6.2.1 firmware, the default behavior of the Adaptive Networking QoS feature was changed as follows: • Default QoS behavior is disabled on 4-Gb platforms. • Default QoS behavior is disabled on the Extended Fabrics E_Ports on both 4-Gb and 8-Gb platforms. This fix addressed the following unexpected behaviors that occurred when the Adaptive Networking QoS feature was enabled by default in earlier Fabric OS releases: • Splitting of a single trunk group into multiple trunk groups upon port toggle, since the toggled ports come online with QoS enabled, while the remaining ports in the trunk group have QoS disabled. • Fewer buffer credits being made available to normal E_Ports after a port toggle, even when QoS is not being utilized. • An unexpected change to a fill-word configuration on an Extended Fabrics E_Port after a port toggle. If an Extended Fabrics E_Port is using IDLE primitives as fill words, and if that port toggles, the fill-word configuration is changed to use ARB primitives. NOTE: After upgrading to this firmware release, if users want to enable the Adaptive Networking QoS feature on 4-Gb platforms and on the Extended Fabrics E_Ports on both 4-Gb and 8-Gb platforms, they must do so explicitly through the available user interfaces. • QoS is supported on switches in Access Gateway mode with Fabric OS 6.3.0. The fabric switches should be running Fabric OS 6.3 to support QoS. If the fabric switch is Fabric OS 6.2, QoS must be disabled on either switch or AG. 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. FCR backbone fabric ID changes • With 8-Gb director blades, the switch must be disabled to change the backbone fabric ID. • With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the IDs unique. Traffic Isolation over FCR • All switches and Fibre Channel routers, both in edge and backbone fabrics, must be running Fabric OS 6.1.0 or later in order to support this feature. • In order for TI over FCR to function properly, the associated TI zones in each fabric (edge and backbone) must have failover enabled. HP StorageWorks Fabric OS 6.3.0 release notes 31

  • 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
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.0 cannot exist in a fabric with flow-based
QoS. Major problems occur if previous-generation 2-Gb products exist in the fabric.
•
Beginning with the Fabric OS 6.2.1 firmware, the default behavior of the Adaptive Networking
QoS feature was changed as follows:
•
Default QoS behavior is disabled on 4-Gb platforms.
•
Default QoS behavior is disabled on the Extended Fabrics E_Ports on both 4-Gb and 8-Gb
platforms.
This fix addressed the following unexpected behaviors that occurred when the Adaptive Networking
QoS feature was enabled by default in earlier Fabric OS releases:
•
Splitting of a single trunk group into multiple trunk groups upon port toggle, since the toggled
ports come online with QoS enabled, while the remaining ports in the trunk group have QoS
disabled.
•
Fewer buffer credits being made available to normal E_Ports after a port toggle, even when
QoS is not being utilized.
•
An unexpected change to a fill-word configuration on an Extended Fabrics E_Port after a port
toggle. If an Extended Fabrics E_Port is using IDLE primitives as fill words, and if that port
toggles, the fill-word configuration is changed to use ARB primitives.
NOTE:
After upgrading to this firmware release, if users want to enable the Adaptive Networking QoS feature
on 4-Gb platforms and on the Extended Fabrics E_Ports on both 4-Gb and 8-Gb platforms, they must
do so explicitly through the available user interfaces.
•
QoS is supported on switches in Access Gateway mode with Fabric OS 6.3.0. The fabric switches
should be running Fabric OS 6.3 to support QoS. If the fabric switch is Fabric OS 6.2, QoS must
be disabled on either switch or AG. 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.
FCR backbone fabric ID changes
•
With 8-Gb director blades, the switch must be disabled to change the backbone fabric ID.
•
With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the
IDs unique.
Traffic Isolation over FCR
•
All switches and Fibre Channel routers, both in edge and backbone fabrics, must be running
Fabric OS 6.1.0 or later in order to support this feature.
•
In order for TI over FCR to function properly, the associated TI zones in each fabric (edge and
backbone) must have failover enabled.
HP StorageWorks Fabric OS 6.3.0 release notes
31