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
114 SAN High Availability Planning Guide
allowed with another fabric switch. The director or switch reports an
attempted E_Port connection as invalid and prevents the port from
coming online.
— For later versions of director or switch firmware (version 4.0 and later),
the domain field of the destination ID is added to the Fibre Channel link
address, thus specifying the link address on source and target fabric
elements and enabling E_Port (ISL) connectivity. This connectivity is
called FICON cascading. For additional information, refer to “FICON
Cascading” on page 124.
■ When employing inband (Fibre Channel) director or switch management, the
open-systems management server (OSMS) is associated with the FCP
protocol, and the FICON management server (FMS) is associated with the
FICON protocol. Management server differences tend to complicate security
and control issues.
Each server provides facilities to change zoning information (FCP protocol)
or the logical port address-based connectivity configuration (FICON
protocol), but neither provides sufficient functionality for both protocols.
Features that Impact Protocol Intermixing
The following features impact how a director or switch behaves when deployed in
an intermixed environment:
■ Hardware-Enforced Zoning
■ SANtegrity Binding
■ FICON Cascading
Hardware-Enforced Zoning
Hardware-enforced zoning (hard zoning) allows a user to program director or
switch route tables that enable hardware logic to route Fibre Channel frames. This
process prevents traffic between source and destination devices not in the same
zone. Hard zoning provides the open-systems environment with the same
protection that PDCM arrays provide in the FICON environment.
In environments that include discovery-oriented devices (FCP) and
definition-oriented devices (FICON), system administrators must keep device
definitions and zoning definitions synchronized. Hard zoning enforces zoning
information at the director or switch level and ensures that the information takes
precedence over access definitions configured at the device level. This provides a
security element that is useful for mixed environments that use both definition and
discovery. For additional information, refer to “Zoning” on page 154.