Solaris Cluster the Use of VxVM Volumes in Zone Clusters via "device match" is Failing with "No such device or address" in Zone
Last updated on MAY 09, 2017
Applies to:Solaris Cluster - Version 3.2 U2 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Since Solaris Cluster 3.2 2/09 update2 its possible to configure a Zone Cluster on top of Solaris Cluster in global zone.
A zonecluster configuration where VxVM (Veritas Volume Manager from Symantec Storage Foundation) devices are mapped from the global zone via "device match" will generate inaccessible device links in that zones of the zonecluster.
In this example the zonecluster is called "sunzc" and the one of the zones is called "sun1". The VxVM diskgroup is called "sun_crs11dg".
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 hundreds of Community platforms