Local Zone discovery is inconsistent and/or missing in Veritas Operations Manager (VOM)
|Article:TECH195591|||||Created: 2012-08-24|||||Updated: 2012-08-27|||||Article URL http://www.symantec.com/docs/TECH195591|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
This issue can have many different symptoms in the reporting of local zones configured on a Managed Host (MH).
Typically there would no error message, just an inconsistency in the reporting of a local zone (possibly missing).
Any Solaris Operating System supporting local zones.
This issue was discovered in VOM 4.1 but may be seen in any VOM version where local zone discovery is supported.
The configuration of the zone at the OS layer is missing it's UUID.
# zoneadm list -cp 0:global:running:/::native:shared 1:torccr02:running:/zones/torccr02/zone_root:2842a86e-16a8-cf99-cdec-c53ed85d1810:native:shared 3:dstsdbs01:running:/zones/dstsdbs01/zone_root:dd138f8a-b35a-4ca3-a006-f4523efa07ef:native:shared 5:dstsapp1:running:/zones/dstsapp1/zone_root::native:shared 5:dstsapp1:running:/zones/dstsapp1/zone_root::native:shared (note: missing UUID ^^)
Once it is determined that the UUID is missing from the zone configuration file, it is suggested to engage Oracle for the most effective and supported method to fix the issue. There are 2 issues to be resolved; 1 - why is the UUID missing and 2 - how to fix it.
Article URL http://www.symantec.com/docs/TECH195591