创建博客 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

hty

 
 
 

日志

 
 

"VCS ERROR V-16-1-10600 Cannot connect to VCS engine" is logged in the engine log when VCS resource is configured for a Solaris local zone.  

2009-02-16 22:54:44|  分类: 默认分类 |  标签: |举报 |字号 订阅


"VCS ERROR V-16-1-10600 Cannot connect to VCS engine" is logged in the engine log when VCS resource is configured for a Solaris local zone.

Exact Error Message
VCS ERROR V-16-1-10600 Cannot connect to VCS engine

Details:
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.

The hazonesetup command is called with the following parameters.

# hazonesetup     servicegroup_name     zoneres_name     zone_name     password     systems

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.

cluster alawclus (
       UserNames = { admin = GnoGniNkoJooMwoInl,
                z_Z_pseudoCluster = JqrJqlQnrMrrPzrLqo }    <<< VCS Service Group Administrator
       ClusterAddress = "192.168.66.1"
       Administrators = { admin }
       CredRenewFrequency = 0
       HacliUserLevel = COMMANDROOT
       CounterInterval = 5
       )

group SGZoneAppl (
       SystemList = { alaw1 = 0 }
       AutoStartList = { alaw1 }
       Administrators = {  z_Z_pseudoCluster }        <<< Administrator of the Service Group
       )

2. halogin environment in the local zone.

In the local zone, you should have the following two files

/etc/VRTSvcs/.vcshost
- should be the hostname of the global zone

/.vcspwd
- the password for the VCS zone user

The hostname in the .vcshost file should be pingable from within the local zone.

local# ping `cat /etc/VRTSvcs/.vcshost`

The VCS commands should run successfully in the local zone.

local# haclus -list

VCS commands should also be run successfully from the Solaris global zone through zlogin.

global# zlogin localzone /opt/VRTSvcs/bin/haclus -list
alawclus







引文来源  "VCS ERROR V-16-1-10600 Cannot connect to VCS engine" is logged in the engine log when VCS resource is configured for a Solaris local zone.
  评论这张
 
阅读(5090)| 评论(0)
推荐 转载

历史上的今天

最近读者

热度

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2014