When a resource is configured to run inside a Solaris local zone, the error message "VCS ERROR V-16-1-10600 Cannot connect to VCS engine" is most likely caused by the execution of the VCS commands (e.g. halog) when halogin environment is not setup properly. For example, in the VCS entry point scripts, it is common to call "halog" (through VCSAG_LOG_MSG or VCSAG_LOGDBG_MSG functions) to log a message to the engine log.

Inside a Solaris local zone, the VCS commands cannot connect to the VCS engine (had) directly because VCS engine is only running in the global zone. In order for the VCS commands to connect to the VCS engine, halogin environment is setup in the local zone.

It is highly recommended the VCS "Zone" resource be setup with the hazonesetup command. hazonesetup will setup a proper "halogin" environment for the VCS commands to run successfully inside a Solaris local zone.

Parameters are- Service Group Name- Zone Resource Name <<< this is name of the VCS "Zone" resource to be created - Zone Name <<< Name of Solaris local zone- Password <<< a new password for the service group administrator- Systems

The hazonesetup command will setup the followings.

1. VCS Group Administrator in the main.cf. The name should be like z_<Zone resource name>, e.g.