[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here

HP OpenVMS Cluster Systems


Previous Contents Index

Index
Index
Examples
7-1 Sample Commands for Creating OpenVMS Cluster Queues
7-2 Common Procedure to Start OpenVMS Cluster Queues
8-1 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Add a Computer as a Boot Server
8-2 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Add a Computer Running DECnet--Plus
8-3 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Add a Satellite with Local Page and Swap Files
8-4 Configuring Node TULIP to Enable Cluster over IP
8-5 Configuring Node ORCHID to Enable Cluster over IP
8-6 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Remove a Satellite with Local Page and Swap Files
8-7 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Enable the Local Computer as a Disk Server
8-8 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Change the Local Computer's ALLOCLASS Value
8-9 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Enable the Local Computer as a Boot Server
8-10 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Change a Satellite's Hardware Address
8-11 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Enable the Local Computer as a Tape Server
8-12 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Change the Local Computer's TAPE_ALLOCLASS Value
8-13 Sample Interactive CLUSTER_CONFIG_LAN.COM Session to Convert a Standalone Computer to a Cluster Boot Server
8-14 Sample Interactive CLUSTER_CONFIG_LAN.COM CREATE Session
10-1 Sample NETNODE_UPDATE.COM File
10-2 Sample SYSMAN Session to Change the Cluster Password
C-1 LAN Device-Attention Entry
D-1 Portion of LAVC$FAILURE_ANALYSIS.MAR to Edit
F-1 SDA Command SHOW PORT Display
F-2 SDA Command SHOW PORT/VC Display
F-3 SDA Command PE LAN_DEVICE
F-4 SDA Command SHOW PORT/BUS Display
F-5 SDA Command SHOW LAN/COUNTERS Display
F-6 SDA Command SHOW PORT/BUS =BUS_IP_interface
F-7 SDA Command SHOW PORT/CHANNEL Display
Figures
1-1 OpenVMS Cluster System Communications
1-2 Single-Point OpenVMS Cluster System Management
2-1 OpenVMS Cluster System Architecture
3-1 LAN OpenVMS Cluster System with Single Server Node and System Disk
3-2 Virtual LAN
3-3 LAN Failover Support
3-4 Cluster Communication Design Using IP
3-5 OpenVMS Cluster Configuration Based on IP
3-6 Two-Node MEMORY CHANNEL OpenVMS Cluster Configuration
3-7 Three-Node MEMORY CHANNEL OpenVMS Cluster Configuration
3-8 OpenVMS Cluster System Using FC and Ethernet Interconnects
3-9 Three-Node OpenVMS Cluster Configuration Using a Shared SCSI Interconnect
3-10 Two-Node OpenVMS Integrity server Cluster System
5-1 Resource Sharing in Mixed-Architecture Cluster System (Integrity servers and Alpha)
5-2 Resource Sharing in Mixed-Architecture Cluster System (Integrity servers and Alpha)
5-3 Directory Structure on a Common System Disk
5-4 File Search Order on Common System Disk
5-5 Translation Order Specified by LNM$FILE_DEV
5-6 Virtual Private Network for Protecting Cluster Traffic
6-1 Dual-Ported Disks
6-2 Dual-Pathed Disks
6-3 Configuration with Cluster-Accessible Devices
6-4 Disk and Tape Dual Pathed Between Computers
6-5 Device Names in a Mixed-Interconnect Cluster
6-6 SCSI Device Names Using a Node Allocation Class
6-7 Device Names Using Port Allocation Classes
6-8 Shadow Set With Three Members
6-9 Shadow Sets Accessed Through the MSCP Server
7-1 Sample Printer Configuration
7-2 Print Queue Configuration
7-3 Clusterwide Generic Print Queue Configuration
7-4 Sample Batch Queue Configuration
7-5 Clusterwide Generic Batch Queue Configuration
F-1 Protocols in the SCA Architecture
F-2 Protocols in the SCA Architecture for Cluster over IP
F-3 Channel-Formation Handshake
F-4 Lost Messages Cause Retransmissions
F-5 Lost ACKs Cause Retransmissions
F-6 NISCA Headers
F-7 Ethernet Header
F-8 DX Header
F-9 CC Header
F-10 TR Header
Tables
1-1 Interconnect Support by OpenVMS Platform
1-2 HP System Management Tools
2-1 Communications Services
2-2 Transitions Caused by Adding a Cluster Member
2-3 Transitions Caused by Loss of a Cluster Member
3-1 Satellite Booting Process
4-1 Information Required to Perform an Installation
4-2 Installing Layered Products on a Common System Disk
4-3 Procedure for Configuring the DECnet Network
5-1 Default Clusterwide Logical Name Tables and Logical Names
5-2 Alias Collisions and Outcomes
5-3 Security Files
5-4 Procedure for Coordinating Files
6-1 Device Access Methods
6-2 Examples of Device Names with Port Allocation Classes 1-32767
6-3 Examples of Device Names With Port Allocation Class 0
6-4 MSCP_LOAD and TMSCP_LOAD Parameter Settings
6-5 MSCP_SERVE_ALL and TMSCP_SERVE_ALL Parameter Settings
8-1 Summary of Cluster Configuration Functions
8-2 Preconfiguration Tasks
8-3 Data Requested by CLUSTER_CONFIG_LAN.COM and CLUSTER_CONFIG.COM
8-4 Preparing to Add Computers to an OpenVMS Cluster
8-5 Preparing to Add a Quorum Disk Watcher
8-6 Preparing to Remove Computers from an OpenVMS Cluster
8-7 Preparing to Remove a Quorum Disk Watcher
8-8 CHANGE Options of the Cluster Configuration Procedure
8-9 Tasks Involved in Changing OpenVMS Cluster Configurations
8-10 Actions Required to Reconfigure a Cluster
9-1 Differences Between Alpha and Integrity server Satellites
9-2 Checklist for Satellite Booting
9-3 Procedure for Defining a Pseudonode Using DECnet MOP Services
9-4 Procedure for Defining a Pseudonode Using LANCP MOP Services
9-5 Procedure for Creating Different DECnet Node Databases
9-6 Procedure for Creating Different LANCP Node Databases
9-7 Controlling Satellite Booting
9-8 Techniques to Minimize Network Problems
10-1 Backup Methods
10-2 Upgrading the OpenVMS Operating System
10-3 OPCOM System Logical Names
10-4 AUTOGEN Dump-File Symbols
10-5 Common SYSUAF.DAT Scenarios and Probable Results
10-6 Reducing the Value of Cluster Quorum
A-1 Adjustable Cluster System Parameters
A-2 Cluster System Parameters Reserved for OpenVMS Use Only (Integrity servers and Alpha)
B-1 Building a Common SYSUAF.DAT File
C-1 Sequence of Booting Events
C-2 Alpha Booting Messages (Alpha Only)
C-3 Port Failures
C-4 How to Verify Virtual Circuit States
C-5 Informational and Other Error-Log Entries
C-6 Port Messages for All Devices
C-7 Port Messages for LAN Devices
C-8 OPA0 Messages
C-9 Integrity server Satellite Booting Messages
D-1 Procedure for Using the LAVC$FAILURE_ANALYSIS.MAR Program
D-2 Creating a Physical Description of the Network
E-1 Subroutines for LAN Control
E-2 SYS$LAVC_START_BUS Status
E-3 SYS$LAVC_STOP_BUS Status
E-4 SYS$LAVC_DEFINE_NET_COMPONENT Parameters
E-5 SYS$LAVC_DEFINE_NET_PATH Parameters
E-6 SYS$LAVC_DEFINE_NET_PATH Status
F-1 SCA Protocol Layers
F-2 SCA Protocol Layers for Cluster over IP
F-3 Communication Paths
F-4 System Parameters for Timing
F-5 Channel Timeout Detection
F-6 SHOW PORT/VC Display
F-7 Channel Formation
F-8 Fields in the Ethernet Header
F-9 Fields in the DX Header
F-10 Fields in the CC Header
F-11 Fields in the TR Header
F-12 Tracing Datagrams
F-13 Capturing Retransmissions on the LAN
F-14 Capturing All LAN Packets (LAVc_all)
F-15 Setting Up a Distributed Enable Filter (Distrib_Enable)
F-16 Setting Up the Distributed Trigger Filter (Distrib_Trigger)
F-17 Setting Up the Distributed Enable Message (Distrib_Enable)
F-18 Setting Up the Distributed Trigger Message (Distrib_Trigger)
G-1 Conditions that Create HELLO Datagram Congestion

Previous Next Contents Index