FW V06.XX/HAFM SW V08.02.00 HP StorageWorks SAN High Availability Planning Guide (AA-RS2DD-TE, July 2004)
Table Of Contents
- SAN HA Planning Guide
- Contents
- About this Guide
- Introduction to HP Fibre Channel Products
- Product Management
- Planning Considerations for Fibre Channel Topologies
- Fibre Channel Topologies
- Planning for Point-to-Point Connectivity
- Characteristics of Arbitrated Loop Operation
- Planning for Private Arbitrated Loop Connectivity
- Planning for Fabric-Attached Loop Connectivity
- Planning for Multi-Switch Fabric Support
- Fabric Topologies
- Planning a Fibre Channel Fabric Topology
- Fabric Topology Design Considerations
- FICON Cascading
- Physical Planning Considerations
- Port Connectivity and Fiber-Optic Cabling
- HAFM Appliance, LAN, and Remote Access Support
- Inband Management Access (Optional)
- Security Provisions
- Optional Features
- Configuration Planning Tasks
- Task 1: Prepare a Site Plan
- Task 2: Plan Fibre Channel Cable Routing
- Task 3: Consider Interoperability with Fabric Elements and End Devices
- Task 4: Plan Console Management Support
- Task 5: Plan Ethernet Access
- Task 6: Plan Network Addresses
- Task 7: Plan SNMP Support (Optional)
- Task 8: Plan E-Mail Notification (Optional)
- Task 9: Establish Product and HAFM Appliance Security Measures
- Task 10: Plan Phone Connections
- Task 11: Diagram the Planned Configuration
- Task 12: Assign Port Names and Nicknames
- Task 13: Complete the Planning Worksheet
- Task 14: Plan AC Power
- Task 15: Plan a Multi-Switch Fabric (Optional)
- Task 16: Plan Zone Sets for Multiple Products (Optional)
- Index

Planning Considerations for Fibre Channel Topologies
117SAN High Availability Planning Guide
director or switch incompatibility. In addition, the SANtegrity Binding
feature (with Enterprise Fabric Mode enabled) is required to support
FICON cascading.
4. Logically assign ports — To organize devices into manageable groups for
zoning, director or switch ports should be logically assigned to FCP port
groups and FICON port groups. Although FICON devices can be zoned by
device WWN, they must also be assigned logical port addresses that
correspond to the port addresses configured by the attached host HCD.
FICON devices must be attached to these assigned ports. In addition, PDCM
arrays affect port connections at the hardware level, so a range of port
addresses must be established for FCP device use, and a separate range of port
addresses must be established for FICON device use. FCP ports should
always be configured to allow communication with each other but disallow
communication with FICON ports, and vice versa.
5. Configure FICON cascading — Configure and enable FICON cascading for
all fabric elements. Refer to “FICON Cascading Best Practices” on page 126
for instructions. As part of this step, ensure that the SANtegrity Binding
feature key is installed and Enterprise Fabric Mode is enabled for all
directors and switches.
— In conjunction with the SANtegrity Binding feature (fabric and switch
binding), consider enabling port binding from a director or switch’s
Element Manager application. Port binding explicitly defines (by WWN
or nickname) the device allowed to attach to a Fibre Channel port and
provides additional security when logically allocating ports to FCP and
FICON groups. Although this process creates additional configuration
overhead, port binding is useful for implementations that require
protection from accidental misconfigurations.
6. Configure PDCM arrays — For each director or switch managed by the
FICON management style, define the allow and prohibit settings for FICON
device connectivity. Use the Element Manager application’s Configure
Allow/Prohibit Matrix - Active dialog box. Port connectivity assignment
(step 4) should be reflected in PDCM arrays for FICON connectivity
management. The baseline configuration for each fabric element must
prohibit communication between FICON and FCP devices.
— Because PDCM arrays affect port connections at the hardware level, it is
imperative to establish a range of port addresses for FCP use and another
range for FICON use. FCP-assigned ports should be configured to allow
communication with each other and prohibit communication with
FICON-assigned ports, and vice versa.