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
82 SAN High Availability Planning Guide
Note: The hop count is equal to the number of ISL connections traversed in a single
path, not the total number of ISL connections between devices. As shown in Figure 35,
the number of ISL connections between Switch S
1
and S
2
is 4, while the number of
hops is 1.
Factors to Consider When Implementing a Fabric Topology
Director and switch-based fabrics offer scalable, high-performance, and
high-availability connectivity solutions for the enterprise. To enable a
multi-switch fabric, all fabric elements must be defined to the HAFM application
and must be physically cabled to form the requisite ISL connections. In addition,
HP recommends that each director or switch in the fabric be assigned a unique
preferred domain ID.
When planning to implement a fabric topology, consider the following
connectivity and cabling concepts:
■ Physical characteristics and performance objectives — Most enterprises
have unique configurations determined by the characteristics of end devices,
fabric elements, cost, and the installation’s performance objectives (such as
high data transfer rate or high availability). These factors, along with
nondisruptive growth and service requirements, must be evaluated when
planning an initial fabric. For additional information, refer to “Planning a
Fibre Channel Fabric Topology” on page 99.
■ Distance requirements — The distance between elements in a fabric affects
the type of optical port transceiver and cabling required. In addition, variables
such as the number of connections, grade of fiber-optic cable, device
restrictions, application restrictions, buffer-to-buffer credit limits, and
performance requirements can affect distance requirements. Consider the
following:
— If the distance between two fabric elements is less than 250 meters (at
2.125 Gbps), any port type (shortwave or longwave laser) and any
fiber-optic cable type (multimode or single-mode) can be used to create
an ISL connection. In this case, cost or port availability may be the
determining factor.
— If the distance between two fabric elements exceeds 300 meters (at 2.125
Gbps), only longwave laser ports and single-mode fiber-optic cable can
be used to create an ISL.