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
Physical Planning Considerations
158 SAN High Availability Planning Guide
If the configurations cannot merge, E_Ports that form the ISL for each fabric
element become segmented. The ports cannot transmit data frames between
attached switches (Class 2 or 3 traffic) but can transmit control frames (Class F
traffic).
Zoning configurations are compatible if there are no duplicate domain IDs, the
active zone set name is the same for each fabric (or switch in the fabric), and
zones with the same names in each fabric have identical members.
Factors to Consider When Implementing Zoning
Consider the following factors when planning to implement zoning for one or
more directors or switches in the enterprise. In particular, consider the
implications of zoning within a multi-switch fabric.
■ Reasons for zone implementation — Determine if zoning is to be
implemented for the enterprise. If so, evaluate if the purpose of zoning is to
differentiate between operating systems, data sets, user groups, devices,
processes, or some combination thereof. Plan the use of zone members, zones,
and zone sets accordingly.
■ Zone members specified by port number or WWN — Determine if zoning
is to be implemented by port number or WWN. Because changes to port
connections or fiber-optic cable configurations disrupt zone operation and
may incorrectly include or exclude a device from a zone, zoning by WWN is
recommended. However, if zoning is implemented by WWN, removal and
replacement of a device’s HBA or Fibre Channel interface disrupts zone
operation and will exclude a new device from a zone unless the device is
added to the zone set.
■ Zoning implications for a multi-switch fabric — For a multi-switch fabric,
zoning is configured on a fabric-wide basis, and any change to the zoning
configuration is applied to all switches in the fabric. To ensure zoning is
consistent across a fabric, there can be no duplicate domain IDs, the active
zone set name must be consistent, and zones with the same name must have
identical elements. Ensure these rules are enforced when planning zones and
zone sets, and carefully coordinate the zoning and multi-switch fabric tasks.
Obtaining Professional Services
Planning and implementing a multi-switch fabric can be a complex and difficult
task. HP recommends that you obtain planning assistance from our professional
services organization before implementing a fabric topology.