HP 8/20q HP StorageWorks 8/20q Fibre Channel Switch Installation and Reference - Page 22

To con transparent routing using QuickTools or Enterprise Fabric Management Suite - san switch

Page 22 highlights

You can connect multiple 8/20q Fibre Channel Switches to one or more remote fabrics using multiple TR_Ports. Local and remote devices are identified by their respective port worldwide names. Consider the following mapping rules: • A TR_Port can support a maximum of 32 local device/remote device mappings. • A specific local device can be mapped to devices on only one remote fabric. Local devices on the same 8/20q Fibre Channel Switch can each be mapped to different remote fabrics. • For mappings between a specific 8/20q Fibre Channel Switch and a remote fabric, each local device or remote device can be mapped over only one TR_Port. Additional mappings to either device must use that same TR_Port. • Mulitple local devices connected to different local switches can be mapped to the same remote device over one TR_Port on each local switch. • A local device cannot be mapped over an E_Port to another local switch, then over a TR_Port to the remote device. The local switch to which the local device is connected must connect directly to the remote fabric over a TR_Port. NOTE: When a local device is mapped over a TR_Port to a remote device, the local device and its TR_Port appear as an NPIV connected device in the remote fabric. It is possible, though not recommended, to map such a local device over a second TR_Port to a local device in a second local fabric. In this case, if you merge the two local fabrics, the transparent route becomes inactive for the devices that now have a path over an ISL, and an alarm is generated. You can configure transparent routing using QuickTools, Enterprise Fabric Management Suite, or the CLI, though QuickTools and Enterprise Fabric Management Suite are recommended because they validate your entries, manage the zone mapping for the local fabric, and create a list of zoning commands that can be run in a script on a HP StorageWorks B-series or C-series SAN switch. For more information, see the HP StorageWorks 8/20q Fibre Channel Switch QuickTools Switch Management User Guide, HP StorageWorks 8/20q and SN6000 Enterprise Fabric Management Suite User Guide, or the HP StorageWorks 8/20q Fibre Channel Switch Command Line Interface Guide. IMPORTANT: Since C-series switches do not support the Unzoned Name Server, C-series fabrics must be "pre-zoned" before you can set up TR mappings to a remote C-series fabric using the TR Mapping Manager dialog box. The C-series fabric zoneset must be changed to add zones so that the WWNs of the remote devices are mapped and the WWNs of the 8/20q Fibre Channel Switch TR ports are zoned together. For more information, see the C-series documentation for specific information to configure zoning. Retain these zones in the zoneset after completion of the TR mapping, until you no longer need to map the device to the local fabric. To configure transparent routing using QuickTools or Enterprise Fabric Management Suite: 1. Determine what devices on the local fabric require access to devices on the remote fabric. Local devices must be attached directly to the 8/20q Fibre Channel Switch. 2. Configure one or more TR_Ports on the local 8/20q Fibre Channel Switch, and then connect the TR_Port to the remote fabric. The application prompts you to configure TR_Ports where existing port connections to remote fabrics are isolated. For remote HP StorageWorks B-series or C-series fabrics, the switch to which the TR_Port connects must support N-Port ID Virtualization (NPIV) and for B-series fabrics, the interoperability mode must be configured to InteropMode=0. Other B-series or C-series switches in the remote fabric need not support NPIV. 22

  • 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
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88

22
You can connect multiple 8/20q Fibre Channel Switches to one or more remote fabrics using multiple
TR_Ports. Local and remote devices are identified by their respective port worldwide names. Consider the
following mapping rules:
A TR_Port can support a maximum of 32 local device/remote device mappings.
A specific local device can be mapped to devices on only one remote fabric. Local devices on the same
8/20q Fibre Channel Switch can each be mapped to different remote fabrics.
For mappings between a specific 8/20q Fibre Channel Switch and a remote fabric, each local device
or remote device can be mapped over only one TR_Port. Additional mappings to either device must use
that same TR_Port.
Mulitple local devices connected to different local switches can be mapped to the same remote device
over one TR_Port on each local switch.
A local device cannot be mapped over an E_Port to another local switch, then over a TR_Port to the
remote device. The local switch to which the local device is connected must connect directly to the
remote fabric over a TR_Port.
NOTE:
When a local device is mapped over a TR_Port to a remote device, the local device and its
TR_Port appear as an NPIV connected device in the remote fabric. It is possible, though not
recommended, to map such a local device over a second TR_Port to a local device in a second
local fabric. In this case, if you merge the two local fabrics, the transparent route becomes inactive
for the devices that now have a path over an ISL, and an alarm is generated.
You can configure transparent routing using QuickTools, Enterprise Fabric Management Suite, or the CLI,
though QuickTools and Enterprise Fabric Management Suite are recommended because they validate your
entries, manage the zone mapping for the local fabric, and create a list of zoning commands that can be
run in a script on a HP StorageWorks B-series or C-series SAN switch. For more information, see the
HP
StorageWorks 8/20q Fibre Channel Switch QuickTools Switch Management User Guide
,
HP
StorageWorks 8/20q and SN6000 Enterprise Fabric Management Suite User Guide
, or the
HP
StorageWorks 8/20q Fibre Channel Switch Command Line Interface Guide
.
IMPORTANT:
Since C-series switches do not support the Unzoned Name Server, C-series fabrics must be
“pre-zoned” before you can set up TR mappings to a remote C-series fabric using the TR Mapping
Manager dialog box. The C-series fabric zoneset must be changed to add zones so that the WWNs of the
remote devices are mapped and the WWNs of the 8/20q Fibre Channel Switch TR ports are zoned
together. For more information, see the C-series documentation for specific information to configure zoning.
Retain these zones in the zoneset after completion of the TR mapping, until you no longer need to map the
device to the local fabric.
To configure transparent routing using QuickTools or Enterprise Fabric Management Suite:
1.
Determine what devices on the local fabric require access to devices on the remote fabric. Local devices
must be attached directly to the 8/20q Fibre Channel Switch.
2.
Configure one or more TR_Ports on the local 8/20q Fibre Channel Switch, and then connect the
TR_Port to the remote fabric. The application prompts you to configure TR_Ports where existing port
connections to remote fabrics are isolated. For remote HP StorageWorks B-series or C-series fabrics, the
switch to which the TR_Port connects must support N-Port ID Virtualization (NPIV) and for B-series
fabrics, the interoperability mode must be configured to InteropMode=0. Other B-series or C-series
switches in the remote fabric need not support NPIV.