Several local zones were discovered on a Managed Host (MH) in Veritas Operations Manager (VOM) but 1 was missing.

Article:TECH197906

Created: 2012-10-04

Updated: 2012-10-11

Article URL http://www.symantec.com/docs/TECH197906

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Problem

Local zone torgfici01 not discovered on global zone torcomm05; several other local zones are discovered properly.

Error

(this is the view seen when viewing the host list in Manage / Hosts and enteing the global zone hostname as a filter; near upper left)

Environment

MH:

                       Solaris 10 11/06 s10s_u3wos_10 SPARC
           Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 14 November 2006

   PKGINST: VRTSsfmh
   VERSION: 4.1.119.0
    PSTAMP: VRTSsfmh-4.1.119.0-Thu Nov 10 03:01:05 2011

CS:

Linux

VRTSsfmcs-4.1.119.0-0

(it is possible that the workaround below may apply to other VOM versions)

Cause

unknown, see Workaround below

Solution

TROUBLESHOOTING

- Using Operating System (OS) based commands, verify that the zones are active at the MH.

torcomm05# zoneadm list -cv
  ID NAME             STATUS     PATH                           BRAND    IP    
   0 global           running    /                              native   shared
   6 fiusgfidb1       running    /zones/fiusgfidb1              native   shared
   7 dstsapp3         running    /zones/dstsapp3/zone_root      native   shared
  13 torhmd01         running    /zones/torhmd01/zone_root      native   shared
  15 torgfici01       running    /zones/torgfici01/zone_root    native   shared
   - torgfici02       configured /zones/torgfici02/zone_root    native   shared
   - dstsapp1         configured /zones/dstsapp1/zone_root      native   shared
   - dstsapp2         configured /zones/dstsapp2/zone_root      native   shared

(note: zone must have been "installed" to be discovered)

- There is a known issue related to UUIDs missing in Solaris local zones; verify that each "installed" zone has a UUID (contact Oracle to resolve missing UUIDs).

torcomm05# zoneadm list -cp
0:global:running:/::native:shared
6:fiusgfidb1:running:/zones/fiusgfidb1:50b3b011-7ac4-e0cf-912a-de95f1c3dec7:native:shared
7:dstsapp3:running:/zones/dstsapp3/zone_root:1a499ad2-ef5b-65f7-c009-bc7dddf4459f:native:shared
13:torhmd01:running:/zones/torhmd01/zone_root:18eeca5b-6bcd-4da1-c75f-be4fe9f660c3:native:shared
15:torgfici01:running:/zones/torgfici01/zone_root:d74a1da1-2311-43b6-8c64-8fd74f05ed7a:native:shared
-:torgfici02:configured:/zones/torgfici02/zone_root::native:shared
-:dstsapp1:configured:/zones/dstsapp1/zone_root::native:shared
-:dstsapp2:configured:/zones/dstsapp2/zone_root::native:shared

WORKAROUND

Summary Procedure

- Remove the MH from the VOM doman and re-add it.

Detailed Proceure

- The MH must be forcefully removed from the domain (this will only affect VOM reporting for this MH)

(use one of the 2 procedures below depending on the VOM verson used)

o VOM 4.1: The following patch will need to be installed and the MH will be removed at the command line.

Patch ID: HF040101190-07

Go to http://sort.symantec.com and search for the patch ID (near upper right) or Browse patch table

(Downloads / Patches) or ...

Direct link: https://sort.symantec.com/patch/detail/6040

(follow the installation instructions at this page to deploy this patch)

Command: /opt/VRTSsfmh/bin//vomadm host-mgmt -remove -host <hostname_of_MH> --force

Example:

[root@vom01 logs]# /opt/VRTSsfmh/bin/vomadm host-mgmt -remove -host torcomm05.tor.xxxxx.xxxx.com --force

          Removing host torcomm05.tor.xxxx.xxxx.com...
          Removing the CH forcefully
          Removed host torcomm05.tor.xxxx.xxxx.com successfully
          Refer /var/opt/VRTSsfmh/logs/vomadm.log for details

o In VOM 5.0, the MH will be removed at the command line (patch not required).

Example:

(this view is the Virtual Machines tab in the Hosts view)