HP Fibre Channel Fabric Migration Guide

20
Fabric Migration Guide
Fabric Device Addressing Changes
Figure 0-8 shows a Direct Fabric Attachment configuration.
Figure 0-8 Direct Fabric Attachment Configuration
The ioscan output for this configuration could be as follows:
Class I H/W Path Driver S/W State H/W Type Description
-----------------------------------------------------------------------------
fc 0 0/1/2/0 td CLAIMED INTERFACE HP Tachyon
TL/TS Fibre Channel Mass Storage Adapter
fcp 1 0/1/2/0.1 fcp CLAIMED INTERFACE FCP Domain
ext_bus 3 0/1/2/0.1.19.0.0 fcparray CLAIMED INTERFACE FCP Array
Interface
target 6 0/1/2/0.1.19.0.0.0 tgt CLAIMED DEVICE
disk 3 0/1/2/0.1.19.0.0.0.0 sdisk CLAIMED DEVICE HP OPEN-8
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 10 0/1/2/0.1.19.0.0.0.7 sdisk CLAIMED DEVICE HP OPEN-8
/dev/dsk/c4t0d7 /dev/rdsk/c4t0d7
target 7 0/1/2/0.1.19.0.0.1 tgt CLAIMED DEVICE
disk 18 0/1/2/0.1.19.0.0.1.7 sdisk CLAIMED DEVICE HP OPEN-9
/dev/dsk/c4t1d7 /dev/rdsk/c4t1d7
Looking at the iotree examples, you can see the following:
• There has been no changeto the adapter pathor the associated device
file which is used for the fcmsutil diagnostic tool.
• The node 0/1/2/0.8, FCP Protocol Adapter, is in both ioscan output
files. In a private loop configuration, the interface and target devices
will reside behind this node. In a fabric environment, this node may
be created as a dummy node generated by the scan logic if the HBA is
scanned when it cannot see the fabric (for example, no cable attached,
switch down, etc.).
In the original Private Loop implementation of the Fibre Channel
driver, this node of the iotree was used to indicate the Fibre Channel
FC4 “TYPE”. A type of “8” denotes that the FCP protocol is being used
to encapsulate the SCSI protocol. With the introduction of fabric, this
node contains the domain portion of the N_Port address. To maintain
backward compatibility, the domain of 8 is reserved for use with
Private Loop devices.
Host
Switch
Disk
Device