VAXcluster - Revision history

Vaxorcist: /* Early VAXcluster Evolution */ LAVC abbreviation added

2025-09-07T07:36:44Z

‎Early VAXcluster Evolution: LAVC abbreviation added

Vaxorcist: /* External links */ Link to VSI page about the current state of cluster technology added

2025-04-11T18:17:41Z

‎External links: Link to VSI page about the current state of cluster technology added

Vaxorcist: Link to "VAXcluster Revision Matrix" added

2025-04-11T18:13:04Z

Link to "VAXcluster Revision Matrix" added

Vaxorcist: /* General Open VMS Cluster Configuration Rules */ Fixed typo

2024-10-31T08:07:51Z

‎General Open VMS Cluster Configuration Rules: Fixed typo

Jnc: Rename VAX cat

2024-08-12T01:23:23Z

Rename VAX cat

Vaxorcist: /* VMScluster as of 1996 */ Centered table

2024-04-27T17:25:49Z

‎VMScluster as of 1996: Centered table

Vaxorcist: renamed heading

2024-04-27T08:36:56Z

renamed heading

Vaxorcist: "FIRST DRAFT" removed

2024-04-27T08:35:47Z

"FIRST DRAFT" removed

Vaxorcist: Section "VAXcluster as of 1996" added

2024-04-27T08:34:58Z

Section "VAXcluster as of 1996" added

Vaxorcist: /* External links */ Removed double order number

2023-09-11T20:20:48Z

‎External links: Removed double order number

@@ Line 137: / Line 137: @@
 * Volume shadowing, introduced in Version 4.4 of VMS, improved information availability by replicating data on multiple disk volumes. Since volume shadowing can also be applied to system disks, it also improved system availability.
-* Version 4.5 introduced [[Ethernet]] based [[Local Area VAXcluster]]s.
+* Version 4.5 introduced [[Ethernet]] based [[Local Area VAXcluster]]s (LAVCs).
 * Version 5.0 introduced the use of multiple interconnects in VAXcluster configurations. It also supported failover of VAXcluster communication from one interconnect to another.

@@ Line 212: / Line 212: @@
 * [http://www.dtjcd.vmsresource.org.uk/pdfs/dtj_v03-03_1991.pdf Availability in VAXcluster Systems; Network Performance and Adapters] (Digital Technical Journal, Volume 3 Number 3 1991)
 * [http://www.vaxhaven.com/images/c/c6/EK-VAXCT-CG-006.pdf VAXcluster Systems - Guidelines for VAXcluster System Configurations] (EK-VAXCT-CG-006)
+* [https://wiki.vmssoftware.com/Cluster VSI page about the current state of cluster technology]
 [[Category: VAX]]

@@ Line 127: / Line 127: @@
 == Early VAXcluster Evolution ==
-(1984 to 1992 period)
+(1984 to 1993 period)
 (taken from: [http://www.vaxhaven.com/images/d/d5/EK-QUORM-Q1-001.pdf VAXcluster Systems Quorum, Volume 8, Issue 2, November 1992])
@@ Line 150: / Line 150: @@
 * With [[Fiber Distributed Data Interface|FDDI (Fiber Distributed Data Interface)]] support in VMS version 5.4-3, the geographic distribution of nodes in a VAXcluster configuration can be measured in tens of kilometers. When bridges are used to combine FDDI and Ethernet, even larger VAXcluster configurations can be achieved. Support for clustering over even larger geographies is planned. Support for FDDI as a VAXcluster interconnect leads to another form of resource availability in the VAXcluster computing environment - disaster tolerance through site redundancy.  This concept is based on duplicating critical hardware and software components of a VAXcluster configuration in two distinct and widely separated locations. Even though there is a great distance between these two locations, the OpenVMS systems and storage in both locations function as a single VAXcluster configuration. These systems all satisfy the Rule of Total Connectivity. If disaster strikes one location, the other location continues to provide the critical elements of the computing environment.
 == VMScluster as of 1996 ==

@@ Line 184: / Line 184: @@
 | AlphaStation Series || || || || X || X || S
 |-
-| AlphaSook Laptop || || || || || || S
+| Alphabook Laptop || || || || || || S
 |-
 | DEC 7000/10000 || X || || X || || S || X

@@ Line 208: / Line 208: @@
 * [https://research.cs.wisc.edu/areas/os/Qual/papers/vaxclusters.pdf VAXclusters: A Closely-Coupled Distributed System] - a very good paper on VAXclusters
 * [http://www.dtjcd.vmsresource.org.uk/pdfs/dtj_v03-03_1991.pdf Availability in VAXcluster Systems; Network Performance and Adapters] (Digital Technical Journal, Volume 3 Number 3 1991)
-[[Category: VAXen]]
+* [http://www.vaxhaven.com/images/c/c6/EK-VAXCT-CG-006.pdf VAXcluster Systems - Guidelines for VAXcluster System Configurations] (EK-VAXCT-CG-006)
-* [http://www.vaxhaven.com/images/c/c6/EK-VAXCT-CG-006.pdf VAXcluster Systems - Guidelines for VAXcluster System Configurations] (EK-VAXCT-CG-006)
+[[Category: VAX]]

@@ Line 169: / Line 169: @@
 The following table shows the OpenVMS Cluster interconnects supported for VAX and Alpha systems:
-{| class="wikitable" style="margin:auto"
+{| class="wikitable" style="text-align: center;
 |+ Supported OpenVMS Cluster interconnects
 |-

@@ Line 151: / Line 151: @@
 * With [[Fiber Distributed Data Interface|FDDI (Fiber Distributed Data Interface)]] support in VMS version 5.4-3, the geographic distribution of nodes in a VAXcluster configuration can be measured in tens of kilometers. When bridges are used to combine FDDI and Ethernet, even larger VAXcluster configurations can be achieved. Support for clustering over even larger geographies is planned. Support for FDDI as a VAXcluster interconnect leads to another form of resource availability in the VAXcluster computing environment - disaster tolerance through site redundancy.  This concept is based on duplicating critical hardware and software components of a VAXcluster configuration in two distinct and widely separated locations. Even though there is a great distance between these two locations, the OpenVMS systems and storage in both locations function as a single VAXcluster configuration. These systems all satisfy the Rule of Total Connectivity. If disaster strikes one location, the other location continues to provide the critical elements of the computing environment.
-== VAXcluster as of 1996 ==
+== VMScluster as of 1996 ==
 Sometime after the release of the new [[Alpha]] hardware platform in 1992, '''VAXcluster''' was renamed to '''VMScluster'''.

← Older revision		Revision as of 08:35, 27 April 2024
Line 1:		Line 1:
−	~~'''FIRST DRAFT'''~~
−
	== VAXcluster Terminology and Key Components ==		== VAXcluster Terminology and Key Components ==

← Older revision		Revision as of 08:34, 27 April 2024
Line 152:		Line 152:

	* With [[Fiber Distributed Data Interface\|FDDI (Fiber Distributed Data Interface)]] support in VMS version 5.4-3, the geographic distribution of nodes in a VAXcluster configuration can be measured in tens of kilometers. When bridges are used to combine FDDI and Ethernet, even larger VAXcluster configurations can be achieved. Support for clustering over even larger geographies is planned. Support for FDDI as a VAXcluster interconnect leads to another form of resource availability in the VAXcluster computing environment - disaster tolerance through site redundancy. This concept is based on duplicating critical hardware and software components of a VAXcluster configuration in two distinct and widely separated locations. Even though there is a great distance between these two locations, the OpenVMS systems and storage in both locations function as a single VAXcluster configuration. These systems all satisfy the Rule of Total Connectivity. If disaster strikes one location, the other location continues to provide the critical elements of the computing environment.		* With [[Fiber Distributed Data Interface\|FDDI (Fiber Distributed Data Interface)]] support in VMS version 5.4-3, the geographic distribution of nodes in a VAXcluster configuration can be measured in tens of kilometers. When bridges are used to combine FDDI and Ethernet, even larger VAXcluster configurations can be achieved. Support for clustering over even larger geographies is planned. Support for FDDI as a VAXcluster interconnect leads to another form of resource availability in the VAXcluster computing environment - disaster tolerance through site redundancy. This concept is based on duplicating critical hardware and software components of a VAXcluster configuration in two distinct and widely separated locations. Even though there is a great distance between these two locations, the OpenVMS systems and storage in both locations function as a single VAXcluster configuration. These systems all satisfy the Rule of Total Connectivity. If disaster strikes one location, the other location continues to provide the critical elements of the computing environment.
		+
		+	== VAXcluster as of 1996 ==
		+
		+	Sometime after the release of the new [[Alpha]] hardware platform in 1992, '''VAXcluster''' was renamed to '''VMScluster'''.
		+
		+	The following information is taken from the [http://bitsavers.org/pdf/dec/catalog/Digital_Systems_and_Options_Catalog_Nov96.pdf Systems and Options Catalog November 1996], pdf page 386.
		+
		+	=== General Open VMS Cluster Configuration Rules ===
		+
		+	The following rules apply to all Open VMS Cluster systems:
		+
		+	* A maximum of 96 Alpha and VAX (combined total) systems can be configured in an OpenVMS Cluster.
		+	* Every system in an Open VMS Cluster system must be connected to every other system via any of the supported OpenVMS Cluster interconnects.
		+	* A VAX and an Alpha system may not boot from the same system disk. System disks are architecture specific, and may only be shared by systems of the same architecture.
		+	* Cross architecture satellite booting is supported. Alpha satellites (clients) may boot from a VAX boot server, and VAX satellites (clients) may boot from an Alpha boot server.
		+	* Configurations that use a shared (multi-host) SCSI bus must also be configured with any of the other supported OpenVMS Cluster interconnects (this is because node-to-node communication does not occur across the SCSI bus).
		+
		+	The following table shows the OpenVMS Cluster interconnects supported for VAX and Alpha systems:
		+
		+	{\| class="wikitable" style="margin:auto"
		+	\|+ Supported OpenVMS Cluster interconnects
		+	\|-
		+	! Systems !! CI !! [[Memory Channel\|MEMORY <br> CHANNEL]] !! [[DSSI]] !! [[SCSI]] !! [[FDDI]] !! [[Ethernet]]
		+	\|-
		+	\| AlphaServer 8400, 8200 \|\| X \|\| X \|\| X \|\| X \|\| S \|\| X
		+	\|-
		+	\| AlphaServer 4100, 4000,<br> 2100, 2100A, 2000 \|\| X \|\| X \|\| X \|\| X \|\| S \|\| S
		+	\|-
		+	\| AlphaServer 1000, 1000A \|\| \|\| X \|\| X \|\| X \|\| X \|\| S
		+	\|-
		+	\| AlphaServer 400 \|\| \|\| \|\| X \|\| X \|\| X \|\| S
		+	\|-
		+	\| AlphaStation Series \|\| \|\| \|\| \|\| X \|\| X \|\| S
		+	\|-
		+	\| AlphaSook Laptop \|\| \|\| \|\| \|\| \|\| \|\| S
		+	\|-
		+	\| DEC 7000/10000 \|\| X \|\| \|\| X \|\| \|\| S \|\| X
		+	\|-
		+	\| DEC 4000 \|\| \|\| \|\| X \|\| \|\| X \|\| S
		+	\|-
		+	\| DEC 3000 \|\| \|\| \|\| \|\| X \|\| S \|\| S
		+	\|-
		+	\| DEC 2000 \|\| \|\| \|\| \|\| \|\| X \|\| S
		+	\|-
		+	\| VAX 6000/7000/10000 \|\| X \|\| \|\| X \|\| \|\| X \|\| X
		+	\|-
		+	\| VAX 4000, MicroVAX 3100 \|\| \|\| \|\| X \|\| \|\| X \|\| S
		+	\|-
		+	\| VAXstation 4000 \|\| \|\| \|\| \|\| \|\| X \|\| S
		+	\|-
		+	\|}
		+
		+	* '''X''' = Full function, i.e. boot node or satellite node.
		+	* '''S''' = Ability to boot over the interconnect as satellite node only.

	==External links==		==External links==

← Older revision		Revision as of 20:20, 11 September 2023
Line 160:		Line 160:
	[[Category: VAXen]]		[[Category: VAXen]]

−	* [http://www.vaxhaven.com/images/c/c6/EK-VAXCT-CG-006.pdf ~~EK-VAXCT-CG-006~~ VAXcluster Systems - Guidelines for VAXcluster System Configurations] (EK-VAXCT-CG-006)	+	* [http://www.vaxhaven.com/images/c/c6/EK-VAXCT-CG-006.pdf VAXcluster Systems - Guidelines for VAXcluster System Configurations] (EK-VAXCT-CG-006)