HP 1606 HP StorageWorks Fabric OS 6.3.2b Release Notes (5697-0777, November 20 - Page 26

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

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

Page 26 highlights

• VF-dedicated ISLs are supported on the DC SAN Director Switch Multiprotocol Extension Blade. XISLs are not supported. • On an HP StorageWorks 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. • QoS is supported on switches in Access Gateway mode with Fabric OS 6.3x and later. 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. • TI over FCR is supported only in edge-to-edge configurations. There is no support for TI in backboneto-edge routing configurations. IP over Fibre Channel (IPFC)/FCR IPFC over FCR is now disabled by default. Switches that are upgraded to Fabric OS 6.3 will retain their configuration settings for IPFC over FCR. The change to the default configuration applies only to new units shipping with Fabric OS 6.3.1a or units running Fabric OS 6.3x that are reset to a default configuration. Use fcrbcast --enable to explicitly enable IPFC over FCR. 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
•
VF-dedicated ISLs are supported on the DC SAN Director Switch Multiprotocol Extension Blade.
XISLs are not supported.
•
On an HP StorageWorks 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.
•
QoS is supported on switches in Access Gateway mode with Fabric OS 6.3x and later. 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.
•
TI over FCR is supported only in edge-to-edge configurations. There is no support for TI in backbone-
to-edge routing configurations.
IP over Fibre Channel (IPFC)/FCR
IPFC over FCR is now disabled by default. Switches that are upgraded to Fabric OS 6.3 will retain
their configuration settings for IPFC over FCR. The change to the default configuration applies only to
new units shipping with Fabric OS 6.3.1a or units running Fabric OS 6.3x that are reset to a default
configuration. Use
fcrbcast ––enable
to explicitly enable IPFC over FCR.
26