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
66 SAN High Availability Planning Guide
Figure 23: Public device connectivity
Public devices support normal fabric operational requirements, such as fabric
busy and reject conditions, frame multiplexing, and frame delivery order.
■ Private device — A loop device that cannot transmit an FLOGI command to
the switch nor communicate with fabric-attached devices is a private device.
As shown in Figure 24, device D
2
is a private loop device that cannot
communicate with any fabric-attached device. However, device D
2
can
communicate with switch-attached server S
2
(using private addressing mode).
Public and private devices are partitioned into two separate address spaces
defined in the Fibre Channel address, and the switch’s embedded FL_Port
ensures that private address spaces are isolated from a fabric. The switch does
not support any other form of Fibre Channel address conversion (spoofing)
that would allow private device-to-fabric device communication.
Note: A private device can connect to the switch (loop) while a public device is
connected and using the B_Port to communicate with a fabric device.