Document revision date: 19 July 1999

Chapter 6
6	Configuring Multiple Paths to SCSI and Fibre Channel Storage
6.1	Overview of Multipath SCSI Support
6.1.1	Direct SCSI to Direct SCSI Failover
6.1.2	Direct SCSI to MSCP Served Failover
6.1.3	Configurations Combining Both Types of Multipath Failover
6.2	Configuration Requirements and Restrictions
6.3	HSx Failover Modes
6.3.1	Transparent Failover Mode
6.3.2	Multibus Failover Mode
6.3.3	Port Addressing for Controllers in Multibus Mode
6.4	Parallel SCSI Multipath Configurations
6.4.1	Transparent Failover
6.4.2	Multibus Failover and Multiple Paths
6.4.3	Configurations Using Multiported Storage Controllers
6.5	Device Naming for Parallel SCSI Multipath Configurations
6.5.1	Review of Node Allocation Classes
6.5.2	Review of Port Allocation Classes
6.5.3	Device Naming Using HSZ Allocation Classes
6.6	Fibre Channel Multipath Configurations
6.7	Implementing Multipath Configurations
6.7.1	Valid Multipath Configurations
6.7.2	Invalid Multipath Configuration
6.7.3	Multipath System Parameters
6.7.4	Path Identifiers
6.7.5	Displaying Paths
6.7.5.1	Displaying Paths With SHOW DEVICE/FULL
6.7.5.2	Displaying Paths With SHOW DEVICE/MULTIPATH_SET
6.7.6	Path Polling
6.7.7	Switching Current Paths Manually
6.7.8	Path Selection by OpenVMS
6.7.9	How OpenVMS Performs Multipath Failover
6.7.10	Enabling or Disabling Paths as Path Switch Candidates
6.7.11	Console Considerations
Chapter 7
7	Configuring Fibre Channel as an OpenVMS Cluster Storage Interconnect
7.1	Overview of Fibre Channel
7.2	Fibre Channel Configuration Requirements and Restrictions
7.2.1	Mixed-Version and Mixed-Architecture Cluster Support
7.3	Example Configurations
7.4	Fibre Channel Addresses, WWIDs, and Device Names
7.4.1	Fibre Channel Addresses and WWIDs
7.4.2	OpenVMS Names for Fibre Channel Devices
7.4.2.1	Fibre Channel Storage Adapter Names
7.4.2.2	Fibre Channel Path Names
7.4.2.3	Fibre Channel Storage Device Identification
7.5	Using the AlphaServer Console for Configuring FC
7.5.1	Viewing the FC Configuration from the Console
7.5.2	Setting up FC Disks for Booting and Dumping
7.6	Setting up an HSG80 for Use with OpenVMS
7.6.1	Setting a Dual HSG80 to Multibus Failover Mode
7.6.2	Setting an HSG80 to SCSI-3 Mode
7.6.3	Setting the Device Identifier for the CCL
7.6.4	Setting the HSG80 Port Parameters
7.6.5	Setting Up Logical Units on the HSG80
7.6.6	Configuring the HSG80 Host Connections
7.7	Creating a Cluster with a Shared FC System Disk
7.8	Online Reconfiguration
Chapter 8
8	Configuring OpenVMS Clusters for Availability
8.1	Availability Requirements
8.2	How OpenVMS Clusters Provide Availability
8.2.1	Shared Access to Storage
8.2.2	Component Redundancy
8.2.3	Failover Mechanisms
8.2.4	Related Software Products
8.3	Strategies for Configuring Highly Available OpenVMS Clusters
8.3.1	Availability Strategies
8.4	Strategies for Maintaining Highly Available OpenVMS Clusters
8.4.1	Strategies for Maintaining Availability
8.5	Availability in a LAN OpenVMS Cluster
8.5.1	Components
8.5.2	Advantages
8.5.3	Disadvantages
8.5.4	Key Availability Strategies
8.6	Configuring Multiple LANs
8.6.1	Selecting MOP Servers
8.6.2	Configuring Two LAN Segments
8.6.3	Configuring Three LAN Segments
8.7	Availability in a DSSI OpenVMS Cluster
8.7.1	Components
8.7.2	Advantages
8.7.3	Disadvantages
8.7.4	Key Availability Strategies
8.8	Availability in a CI OpenVMS Cluster
8.8.1	Components
8.8.2	Advantages
8.8.3	Disadvantages
8.8.4	Key Availability Strategies
8.9	Availability in a MEMORY CHANNEL OpenVMS Cluster
8.9.1	Components
8.9.2	Advantages
8.9.3	Disadvantages
8.9.4	Key Availability Strategies
8.10	Availability in an OpenVMS Cluster with Satellites
8.10.1	Components
8.10.2	Advantages
8.10.3	Disadvantages
8.10.4	Key Availability Strategies
8.11	Multiple-Site OpenVMS Cluster System
8.11.1	Components
8.11.2	Advantages
8.12	Disaster-Tolerant OpenVMS Cluster Configurations

	privacy and legal statement
6318PRO_CONTENTS_001.HTML