[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference spezko::cluster

Title:	+ OpenVMS Clusters - The best clusters in the world! +
Notice:	This conference is COMPANY CONFIDENTIAL. See #1.3
Moderator:	PROXY::MOORE

Created:	Fri Aug 26 1988
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5320
Total number of notes:	23384

5219.0. "MSCP served DSSI disks slow to become available" by CSC32::T_SULLIVAN () Mon Jan 27 1997 16:07

	(VAX4000-600 OpenVMS V5.5-2H4 MSCP serving DSSI disks)

	I have a customer experiencing delayed availability of MSCP
	served DSSI disks after the host reboots.  The disks do not
	show "available" on remote nodes until long after the disks
	have been configured on the serving node. Attempts to perform
	a $mount/cluster during systartup_V5.com will fail unless a
	wait (>2min) is performed.

	Thanks in advance for any ideas.

	Tim

T.R	Title	User	Personal Name	Date	Lines
5219.1		UTRTSC::jvdbu.uto.dec.com::JurVanDerBurg	Change mode to Panic!	`Tue Jan 28 1997 00:23`	18
	> I have a customer experiencing delayed availability of MSCP > served DSSI disks after the host reboots. The disks do not > show "available" on remote nodes until long after the disks > have been configured on the serving node. Attempts to perform > a $mount/cluster during systartup_V5.com will fail unless a > wait (>2min) is performed. How long is long? There's a delay of about 1-2 minutes before a node starts serving disks after system startup. Is the customer doing a 'mount/cluster' on the bootnode? If so that's not needed, a 'mount/system' on every individual node should give the same effect and that would avoid problems like this. Mount/cluster is only needed for doing manual maintenance on disks, not for use in the system startup. That's the responsibility of every individual node. Jur.
5219.2	SYS$EXAMPLES:MSCPMOUNT.COM	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Tue Jan 28 1997 10:50`	9
	Have the customer take a look at SYS$EXAMPLES:MSCPMOUNT.COM -- that procedure needs tweaking for the local configuration. The procedure performs a MOUNT/SYSTEM on each node, and can clear up disks automatically -- the procedure runs on each (major) node at periodic intervals, and runs once during startup. (We make use of this procedure here in OpenVMS.)