HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.1.2 release notes (5697-0349, - Page 16

Description, Topic, Port Fencing is only supported on E_Port and F_Port classes. Port Fencing is

Page 16 highlights

Topic Description Adaptive Networking/flow-based QoS prioritization When using Quality of Service (QoS) in a fabric with 4-Gb ports or switches, Fabric OS 6.x or later must be installed on all products to pass QoS information. E_Ports from the DC Director to other switches must come up after 6.0 is running on those switches. Flow-based QoS is not supported on 8-Gb blades in the 4/256 SAN Director. Any products that are not able to operate with Fabric OS 6.x may not exist in a fabric with flow-based QoS. Major problems occur if previous generation 2-Gb products exist in the fabric. FCR backbone fabric ID change 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. Integrated routing Ports 16-47 on the FC8-48 blade must not be used as Ex_Ports. Only ports 0-15 should be used for FCR on the 48-port blade. To allow hot code load on an HP 8/40 SAN Switch when using Integrated Routing, the edge switch connected to the HP 8/40 SAN Switch must be running Fabric OS 6.1 or later. The HP 8/40 SAN Switch does not support Hot Code Load from Fabric OS 6.1.0 to 6.1.2 in a dual backbone configuration with a routed connection to an M-EOS product. FCS Automatic Distribution When using the FCS Automatic Distribution feature in Fabric OS 6.0 or later, all switches in the fabric must be running Fabric OS 6.0 or later. If any switches are running Fabric OS 5.x or earlier, only manual distribution can be used. Fabric OS 6.0 or later will only allow FCS automatic distribution when in strict mode, requiring only switches with Fabric OS 6.0 or later. Access Gateway Ports 16-47 on the FC8-48 blade must not be used for AG F_Port Trunking connections. When in Access Gateway mode, the Automatic Port Configuration policy may not work when attached to M-EOS switches. M-EOS ports should be set to G_Port to prevent problems with port type discovery. Traffic isolation over FCR All switches and Fibre Channel routers, in both edge and backbone fabrics, must be running Fabric OS 6.1.0a or later to support this feature. The failover policy must be enabled in all edge fabrics that are part of the traffic isolation zones for the proper functioning of traffic isolation over FCR. FICON CUP cascading All switches must operate with Fabric OS 6.1.x or later to support this feature. Port Fencing The default settings for Port Fencing reflect very low thresholds and may cause fence ports to experience errors. HP recommends increasing these threshold values for use in production environments. Different platforms may require different threshold settings for optimum behavior. When the port fencing feature is enabled for ITW or CRC errors, the first set of errors detected on an active link that meet the custom high threshold level set by the user (or the default threshold level) is always ignored to account for expected link transition errors. The port is disabled only upon detection of a second set of errors, that is, the next time the user-set threshold level (or default threshold level) is reached. This prevents a port from being disabled due to normal link transition behaviors. Port Fencing is only supported on E_Port and F_Port classes. Port Fencing is available with the optional Fabric Watch license. 16

  • 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

Description
Topic
When using Quality of Service (QoS) in a fabric with 4-Gb ports or switches,
Fabric OS 6.x or later must be installed on all products to pass QoS information.
E_Ports from the DC Director to other switches must come up
after
6.0 is running
on those switches.
Flow-based QoS is
not
supported on 8-Gb blades in the 4/256 SAN Director.
Any products that are not able to operate with Fabric OS 6.x may
not
exist in a
fabric with flow-based QoS. Major problems occur if previous generation 2-Gb
products exist in the fabric.
Adaptive Network-
ing/flow-based QoS prior-
itization
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.
FCR backbone fabric ID
change
Ports 16-47 on the FC8-48 blade must not be used as Ex_Ports. Only ports 0-15
should be used for FCR on the 48-port blade.
To allow hot code load on an HP 8/40 SAN Switch when using Integrated Routing,
the edge switch connected to the HP 8/40 SAN Switch must be running Fabric
OS 6.1 or later. The HP 8/40 SAN Switch does not support Hot Code Load from
Fabric OS 6.1.0 to 6.1.2 in a dual backbone configuration with a routed
connection to an M-EOS product.
Integrated routing
When using the FCS Automatic Distribution feature in Fabric OS 6.0 or later, all
switches in the fabric must be running Fabric OS 6.0 or later. If any switches are
running Fabric OS 5.x or earlier, only manual distribution can be used.
Fabric OS 6.0 or later will only allow FCS automatic distribution when in strict
mode, requiring only switches with Fabric OS 6.0 or later.
FCS Automatic Distribu-
tion
Ports 16-47 on the FC8-48 blade must not be used for AG F_Port Trunking
connections. When in Access Gateway mode, the Automatic Port Configuration
policy may not work when attached to M-EOS switches. M-EOS ports should be
set to G_Port to prevent problems with port type discovery.
Access Gateway
All switches and Fibre Channel routers, in both edge and backbone fabrics, must
be running Fabric OS 6.1.0a or later to support this feature.
The failover policy must be enabled in all edge fabrics that are part of the traffic
isolation zones for the proper functioning of traffic isolation over FCR.
Traffic isolation over FCR
All switches must operate with Fabric OS 6.1.x or later to support this feature.
FICON CUP cascading
The default settings for Port Fencing reflect very low thresholds and may cause
fence ports to experience errors. HP recommends increasing these threshold values
for use in production environments. Different platforms may require different
threshold settings for optimum behavior.
When the port fencing feature is enabled for ITW or CRC errors, the first set of
errors detected on an active link that meet the custom high threshold level set by
the user (or the default threshold level) is always ignored to account for expected
link transition errors. The port is disabled only upon detection of a second set of
errors, that is, the next time the user-set threshold level (or default threshold level)
is reached. This prevents a port from being disabled due to normal link transition
behaviors.
Port Fencing is only supported on E_Port and F_Port classes. Port Fencing is
available with the optional Fabric Watch license.
Port Fencing
16