HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2.0g release notes (5697-0355 - Page 24

Fibre Channel Routing, FCR backbone fabric ID changes, Traffic isolation over FCR, Integrated routing

Page 24 highlights

Fibre Channel Routing All FCR switches must be running Fabric OS 6.2.x in order to support M-EOS 239 Domain Mode on the Mi10K FCR backbone fabric ID changes • With 8Gb 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 Traffic Isolation over FCR to function properly, the associated TI zones in each fabric (edge and backbone) need to have failover enabled. Integrated routing • To allow Hot Code Load on an HP StorageWorks 8/40 SAN Switch when using Integrated Routing, the edge switch connected to the 8/40 SAN Switch must be running Fabric OS 6.1 or later. • The HP StorageWorks 8/40 SAN Switch does not support Hot Code Load from Fabric OS 6.1.0 to 6.2.x in a dual backbone configuration with a routed connection to an M-EOS product. • Integrated Routing EX_Ports are supported only in the base switch on a switch with VF enabled. To test Integrated Routing functionality, disable the VF feature (fosconfig --disable vf) first. • Integrated Routing and TopTalkers are not concurrently supported in Fabric OS 6.2.x. To use Integrated Routing, be sure to disable TopTalkers before configuring EX_Ports. Access gateway 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. 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 allows FCS Automatic Distribution only when in strict mode, requiring only switches with Fabric OS 6.0 or later. FIPS FIPS mode should not be enabled on the 4/8 and 4/16 SAN Switches. If FIPS is enabled, the 4/8 and 4/16 SAN Switches will not boot. 24

  • 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

Fibre Channel Routing
All FCR switches must be running Fabric OS 6.2.x in order to support M-EOS 239 Domain Mode on
the Mi10K
FCR backbone fabric ID changes
With 8Gb 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 Traffic Isolation over FCR to function properly, the associated TI zones in each fabric
(edge and backbone) need to have failover enabled.
Integrated routing
To allow Hot Code Load on an HP StorageWorks 8/40 SAN Switch when using Integrated
Routing, the edge switch connected to the 8/40 SAN Switch must be running Fabric OS 6.1 or
later.
The HP StorageWorks 8/40 SAN Switch does not support Hot Code Load from Fabric OS 6.1.0
to 6.2.x in a dual backbone configuration with a routed connection to an M-EOS product.
Integrated Routing EX_Ports are supported only in the base switch on a switch with VF enabled.
To test Integrated Routing functionality, disable the VF feature (
fosconfig --disable vf
)
first.
Integrated Routing and TopTalkers are not concurrently supported in Fabric OS 6.2.x. To use In-
tegrated Routing, be sure to disable TopTalkers before configuring EX_Ports.
Access gateway
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.
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 allows FCS Automatic Distribution only when in strict mode, requiring only
switches with Fabric OS 6.0 or later.
FIPS
FIPS mode should not be enabled on the 4/8 and 4/16 SAN Switches. If FIPS is enabled, the 4/8
and 4/16 SAN Switches will not boot.
24