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
105SAN High Availability Planning Guide
■ Local Tier 1 devices — A video server application with I/O capabilities of 40
MBps and 2,000 IOPS must be connected to the fabric. Because the
application is critical and high bandwidth (in excess of 35 MBps), the server
and associated storage are directly attached to the core director as Tier 1
devices. No ISLs are used for server-to-storage connectivity.
■ 11 to 1 fan-out region — Eleven NT servers with I/O capabilities of 10
MBps and 1,000 IOPS are fabric-attached through a 32-port edge switch. The
primary applications are e-mail and online transaction processing (OLTP).
Because bandwidth use is light and noncritical, the servers are connected to
the core director with a single ISL that is intentionally oversubscribed (1.1
Gbps plus Class F traffic). The servers are connected to storage devices with
I/O capabilities of 11,000 IOPS.
■ 6 to 1 fan-out region — Six servers with I/O capabilities of 20 MBps and
1,500 IOPS are fabric-attached through a 16-port edge switch. Bandwidth use
is light to medium but critical, so the servers are connected to the core director
with two ISLs (0.6 Gbps each plus Class F traffic). The servers are connected
to storage devices with I/O capabilities of 9,000 IOPS.
■ 3 to 1 fan-out region — Three servers with I/O capabilities of 30 MBps and
2,000 IOPS are fabric-attached through a 16-port edge switch. Bandwidth use
is medium but non-critical, so the servers are connected to the core director
with one ISL (0.9 Gbps plus Class F traffic). The servers are connected to
storage devices with I/O capabilities of 6,000 IOPS.
Fabric Availability
Many fabric-attached devices require highly available connectivity to support
applications such as disk mirroring, server clustering, or business continuance
operations. High availability is accomplished by deploying a resilient fabric
topology or redundant fabrics.
A fabric topology that provides at least two internal routes between fabric
elements is considered resilient. A single director, switch, or ISL failure does not
affect the remaining elements, and the overall fabric remains operational.
However, unforeseen events such as human error, software failure, or disaster can
cause the failure of a single resilient fabric. Using redundant fabrics (with
resiliency) mitigates these effects and significantly increases fabric availability.
Fibre Channel fabrics are classified by four levels of resiliency and redundancy.
From least available to most available, the classification levels are: