Solaris Cluster 3.x and Solaris Volume Manager (SVM) Errors Like "rpc.metad: Permission denied" or "rpc.metacld 13" or "node failed to become the primary" (Doc ID 1009367.1)

Last updated on DECEMBER 07, 2021

Applies to:

Solaris Cluster - Version 3.0 to 3.3 [Release 3.0 to 3.3]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.10.0 [Release 11.0]
Solstice DiskSuite Software - Version 4.2 to 4.2.1 [Release 4.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

During a standard Solaris Cluster 3.x device group failover condition, Solaris Volume Manager (SVM) errors, such as these, can be seen which cause the 'scswitch' or 'cldevicegroup switch' command to fail (two different types of errors can bee seen):

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Solaris Cluster 3.x and Solaris Volume Manager (SVM) Errors Like "rpc.metad: Permission denied" or "rpc.metacld 13" or "node failed to become the primary" (Doc ID 1009367.1)

Applies to:

Symptoms

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!