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
155SAN High Availability Planning Guide
■ Software-enforced zoning — For earlier versions of director or switch
firmware (prior to version 6.0), the device configuration on a fabric element
enforces zoning by limiting access to name server information in response to
a device query. Only devices in the same zone as the requesting device are
returned in the query response. This type of zoning is also called name server
zoning or soft zoning.
■ Hardware-enforced zoning — For later versions of director or switch
firmware (Version 6.0 and later), the device configuration on a fabric element
enforces zoning by programming route tables that strictly prevent Fibre
Channel traffic between devices that are not in the same zone. This type of
zoning is also called hard zoning.
Zones are configured through the HAFM application by authorizing or restricting
access to name server or route table information (depending on the firmware
release level) associated with device N_Ports that attach to director or switch
F_Ports.
Benefits of Zoning
System administrators create zones to increase network security measures,
differentiate between operating systems, and prevent data loss or corruption by
controlling access between devices (such as servers and data storage units) or
between separate user groups (such as engineering or human resources). Zoning
allows an administrator to establish:
■ Logical subsets of closed user groups. Administrators can authorize access
rights to specific zones for specific user groups, thereby protecting
confidential data from unauthorized access.
■ Barriers between devices that use different operating systems. For example, it
is often critical to separate servers and storage devices with different
operating systems because accidental transfer of information from one to
another can delete or corrupt data. Zoning prevents this by grouping devices
that use the same operating systems into zones.
■ Groups of devices that are separate from devices in the rest of a fabric. Zoning
allows certain processes (such as maintenance or testing) to be performed on
devices in one group without interrupting devices in other groups.
■ Temporary access between devices for specific purposes. Administrators can
remove zoning restrictions temporarily (for example, to perform nightly data
backup), then restore zoning restrictions to perform normal processes.