HP Fibre Channel Fabric Migration Guide

8
Fabric Migration Guide
Migrating to Fabric
Scalability
• Fabrics allow you to expand beyond a single loop with a maximum of
126 loop ports to a SAN environment where it is possible to use
multiple fabrics and attach virtually unlimited numbers of devices in
several configurations.
• In addition to attaching devices directly to the fabric or having public
loops in the SAN, you can attach an existing (but separate) private
loop to the fabric, and have all of the devices managed by the fabric.
This configuration creates a highly scalable and modular network of
storage devices that you can extend as desired with minor effects to
the existing network.
Sharing
Devices, such as tapes, that needed to be configured in a point-to-point
configuration in a loop can now be shared with disk devices when they
are in a fabric environment.
Device File Addressing Changes
Be aware of the following changes in your device files when you migrate
to fabric:
• Device file names and iotree paths will change when you replace a
private loop with a fabric switch.
• Device file names and iotree paths will change when you move a
target device from one port on a fabric switch to another port on the
switch.
• Device files and iotree nodes will change if the switch domain
changes.
For more information on device file addressing changes, see the section
“Fabric Device Addressing Changes” on page 16.
Requirements for Arbitrated Loop and Fabric
Support
• A5158A PCI Tachyon TL adapter
— OS version HP-UX 11.00 or 11i