After following the steps inSOL17526, you still fail on join the computer in sparse zone to the domain
# /opt/quest/bin/vastool configure nss
WARNING: Could not create /usr/lib/nss_vas3.so.1 -> /opt/quest/lib/nss/nss_vas3.so.1 symlink, err = 30
WARNING: Could not create /usr/lib/sparcv9/nss_vas3.so.1 -> /opt/quest/lib/nss/sparcv9/nss_vas3.so.1 symlink, err = 30
This occurs as the global zone isnt joined to Active Directory.
Technically, the global zone doesnt need to be joined to the domain in order for sparse zones to work, but you either need
1) vas installed in the global zone or
2) an empty file called /opt/quest/lib/nss/nss_vas3.so.1 and /opt/quest/lib/nss/sparcv9/nss_vas3.so.1.
The symlink has to exist in the global zone from /usr/lib/nss_vas3.so.1 and /usr/lib/sparcv9/nss_vas3.so.1 to their counterparts in /opt/quest/lib/nss (which is usually accomplished when joining the machine and needs either of those two steps completed for the symlink to exist).
Otherwise, when the sparse zones look for that symlink in /usr, they wont be able to find it and cant create it because of the permissions on /usr. This holds true for sparse zones where /usr is shared.
If /opt/quest is shared, the complete product must be installed on the global zone in order for it to work. Of course, if /usr isnt shared, then you dont need to worry about those symlinks in the global zone.