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
130 SAN High Availability Planning Guide
b. Ensure that the Enable Switch Binding check box is checked (enabled).
c. Select the Restrict E_Ports radio button to restrict connections from
specific fabric elements to E_Ports. WWNs can be added to the
membership list to allow fabric element connection and removed from the
list to prohibit fabric element connection. Devices are allowed to connect
to any F_Port or FL_Port without restriction.
d. Click Activate to close the dialog box and enforce the connection policy.
9. Update channel path and control unit definitions — A cascaded FICON
environment requires channel entry switch and link address updates to the
input/output configuration program (IOCP) as follows:
a. In the IOCP, define an entry switch ID in the SWITCH keyword of the
channel path identifier (CHPID) definition.
Note: An entry switch is a fabric director or switch connected to the FICON channel
of a zSeries processor and a second fabric director or switch.
b. In the IOCP, define a 2-byte link address (consisting of a switch (or
domain) address and port address) for the cascaded switch in the LINK
keyword of the control unit (CNTLUNIT) definition.
Note: An cascaded switch is a fabric director or switch connected to a destination
control unit and an entry switch.
c. Run the IOCP to create an input/output configuration data
set (IOCDS). The switch ID (CHPID macroinstructions) and 2-byte link
address (control unit macroinstructions) are updated in the IOCDS.
Refer to the IBM FICON Native Implementation and Reference Guide
(SG24-6266) for additional information.
10. Verify FICON devices log back in — Inspect the Node List View
(Figure 51) and verify FICON devices (channels and control units inspected
in step 5) log back in to the fabric as expected.
11. Verify cascaded FICON operation — Verify operation of established
logical FICON paths between channels and control units, and verify that
cascaded FICON traffic is transmitted through the fabric as expected.