HP 8/20q HP StorageWorks 8/20q and SN6000 Fibre Channel Switch Enterprise Fabr - Page 43

Viewing inter-fabric routes - storageworks npiv

Page 43 highlights

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. For details of switches supported in a remote fabric, see release notes for the HP H-Series Fibre Channel Switch, and the HP StorageWorks SAN Design Reference Guide on the HP website http://www.hp.com/go/sandesignguide. You can configure TR mappings to connect devices on the local HP H-Series Fibre Channel Switch fabric with devices on remote fabrics. To establish a transparent route between devices: 1. Connect a remote switch to a TR_port on the HP H-Series Fibre Channel Switch. 2. Map the devices together. 3. Create and activate the inter-fabric zones (IFZ) in both fabrics. Each fabric contains a matching IFZ, which must contain exactly three WWN members: local device, remote device, and TR_Port attached to the remote fabric. NOTE: Be sure to configure the TR_Port before connecting the remote fabric to the HP H-Series Fibre Channel Switch. If the remote fabric is connected to a port on the HP H-Series Fibre Channel Switch that is not a TR_Port, the two fabrics may establish an E_Port connection and the local and remote fabrics may merge. This mixed fabric is not a supported configuration. If the port type is changed to TR_Port after connecting the remote fabric, a port reset may be required to completely establish the TR connection. A TR_Port is used as a bridge between the transparent router's local fabric and a remote fabric. A TR_Port uses standard NPIV login methods to attach to the remote fabric. For remote 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. The TR_Port logs into the remote fabric using the WWN of the TR_Port. The TR_Port accesses fabric services of the remote fabric, such as Name Server and Management Server, and may receive registered state change notifications (RSCNs). The TR_Port uses FDISCs to login proxies for devices attached to an N_Port on the HP H-Series Fibre Channel Switch. Any of the HP H-Series Fibre Channel Switch 8Gb ports may be configured as a TR_Port. IMPORTANT: Because C-series switches do not support Unzoned Name Server queries (which are an option of the Fibre Channel standard), 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 zone set must be changed to add zones so that the WWNs of the remote devices to be mapped and the WWNs of the HP H-Series 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 zone set after completion of the TR mapping as a best practice, until you no longer need to map the device to the local fabric. Viewing inter-fabric routes You can view inter-fabric routes in the Transparent Routes data window and the TR Mapping Manager dialog box. HP StorageWorks 8/20q and SN6000 Fibre Channel Switch Enterprise Fabric Management Suite User Guide 43

  • 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
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

HP StorageWorks 8/20q and SN6000 Fibre Channel Switch Enterprise Fabric Management Suite User Guide
43
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.
For details of switches supported in a remote fabric, see release notes for the HP H-Series Fibre Channel
Switch, and the
HP StorageWorks SAN Design Reference Guide
on the HP website
.
You can configure TR mappings to connect devices on the local HP H-Series Fibre Channel Switch fabric
with devices on remote fabrics. To establish a transparent route between devices:
1.
Connect a remote switch to a TR_port on the HP H-Series Fibre Channel Switch.
2.
Map the devices together.
3.
Create and activate the inter-fabric zones (IFZ) in both fabrics. Each fabric contains a matching IFZ,
which must contain exactly three WWN members: local device, remote device, and TR_Port attached to
the remote fabric.
NOTE:
Be sure to configure the TR_Port before connecting the remote fabric to the HP H-Series Fibre
Channel Switch. If the remote fabric is connected to a port on the HP H-Series Fibre Channel Switch that is
not a TR_Port, the two fabrics may establish an E_Port connection and the local and remote fabrics may
merge. This mixed fabric is not a supported configuration. If the port type is changed to TR_Port after
connecting the remote fabric, a port reset may be required to completely establish the TR connection.
A TR_Port is used as a bridge between the transparent router’s local fabric and a remote fabric. A TR_Port
uses standard NPIV login methods to attach to the remote fabric. For remote 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. The TR_Port logs into the remote fabric using
the WWN of the TR_Port. The TR_Port accesses fabric services of the remote fabric, such as Name Server
and Management Server, and may receive registered state change notifications (RSCNs). The TR_Port uses
FDISCs to login proxies for devices attached to an N_Port on the HP H-Series Fibre Channel Switch. Any of
the HP H-Series Fibre Channel Switch 8Gb ports may be configured as a TR_Port.
IMPORTANT:
Because C-series switches do not support Unzoned Name Server queries (which are an
option of the Fibre Channel standard), 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 zone
set must be changed to add zones so that the WWNs of the remote devices to be mapped and the
WWNs of the HP H-Series 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 zone set
after completion of the TR mapping as a best practice, until you no longer need to map the device to the
local fabric.
Viewing inter-fabric routes
You can view inter-fabric routes in the Transparent Routes data window and the TR Mapping Manager
dialog box.