I have a server that is reporting a failed zone named "test". This zone was installed and removed before installing ops center agent, but Ops Center somehow digs the information from somewhere and reports it as Unreachable.
There are no entries in /etc/zones/index for test-zone, is there a way to make Ops Center / Agent re-read the config or what can I do to fix this?
Im using the latest version of 12. Also running Solaris 1 SRU 8.5.
For the 'test' zone I see very few options on the right side;
- Edit tags
- Place in maintenace mode
- apply monitoring profile
- add asset to grp
- switch mgmt access
- add assets
- find assets
The zone it self is 'uncreachable' and not agent managed.
Another possibility, was the globalzone built via flar, and is either of the following files baked into the flar...
Global Zones = /etc/opt/sun/oc/zonectrlr.id
Local Zones = /etc/opt/SUNWxvm/xvm_zone_id <<< wouldn't be this file the ng-zone does not exist.
Both GZ & NGZ's /var/sadm/servicetag/registry/servicetag.xml
If so, the hostname for the ng-zone that once existed but does no longer may be trapped in the file, you can edit the file and delete it, then may need to re-discover the globalzone to totally clear things up.
Even if "test" zone no longer exists; one of the other existing non-global zones on the server may have an older /opt/SUNWxvm/xvm_zone_id file set with an id that Ops Center knows as "test". Uninstall agent from global zone server; then remove xvm_zone_id file from all non-global zones and install agent again. Agent install should create a new xvm_zone_id file for each non-global zone.