My Oracle Support Banner

HA-zones Got "unavailable" State and Could Not Start After Reboot of Crashed Node (Doc ID 2778410.1)

Last updated on MAY 09, 2024

Applies to:

Solaris Cluster - Version 4.4 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

After a node in cluster panicked and reboot, the HA-Zones could not start because of status "unavailable". 
The systems are running Solaris 11.4 SRU27-32 and Oracle Solaris Cluster 4.4
The zone resources in the cluster failed to start after a node panicked and a switch of the resources could not start the zones.

Changes

 The issue occurred after OS SRU upgrade. This behavior can happen with Solaris 11.4 SRU26 through SRU32.

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!

In this Document
Symptoms
Changes
Cause
Solution
References


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