Q-Logic 5800V Manuel D’Utilisation
2–Planning
Multiple Chassis Fabrics
2-14
59265-02 B
You can configure transparent routing using QuickTools, Enterprise Fabric Suite,
or the CLI. However, only QuickTools and Enterprise Fabric Suite 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 an Brocade or Cisco SAN switch. For
more detailed information, see the QLogic 5800V Series QuickTools Switch
Management User’s Guide, QLogic 5800V Series Enterprise Fabric Suite User’s
Guide,
or the CLI. However, only QuickTools and Enterprise Fabric Suite 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 an Brocade or Cisco SAN switch. For
more detailed information, see the QLogic 5800V Series QuickTools Switch
Management User’s Guide, QLogic 5800V Series Enterprise Fabric Suite User’s
Guide,
and the QLogic 5800V Series Fibre Channel Switch Command Line
Interface Guide.
You can connect multiple QLogic 5800V Series 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:
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.
mappings.
A specific local device can be mapped to devices on only one remote fabric.
Local devices on the same QLogic 5800V Series Fibre Channel Switch can
each be mapped to different remote fabrics.
Local devices on the same QLogic 5800V Series Fibre Channel Switch can
each be mapped to different remote fabrics.
For mappings between a specific QLogic 5800V Series 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.
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.
Multiple local devices connected to different local switches can be mapped
to the same remote device over one TR_Port on each local switch.
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.
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.
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.