SORT Documents > Veritas Storage Foundation™ Manager Manual Pages
vxpal -a agent_name [ [-f] [ -c control_cmd [-u user@domain_name.domain_type] [-p password] -l host [ -d agent_domain -e port ] [-s service_name ] ] ]
vxpal runs or issues commands to Veritas Provider Access Layer (VxPAL) agents. An agent is uniquely identified on the host by its name and is bound to a specific port on that host. Configuration information for the agent is present in /etc/vx/isis/Registry. An agent can participate in a secured domain by joining the domain using the veaconfig command. Agents can participate in more than one domain.
You might need to shut down agents on a local host using vxpalctrl.
The configuration information for the agent is present in /etc/vx/isis/Registry file. Entries for the agent in this file are mandatory. The registry can also be used to configure the location for the log files created for the agent.
veaconfig commands can be used to configure the agent.
csf_resolv.conf can be used to specify the security defaults for an agent to avoid having to specify authentication credentials when running commands on remote hosts. The presence of this file is optional and the location of the file can be specified through the environment variable CSF_DOMAIN_RESOLVE_CONF.
The default location is /etc/default/csf_resolv.conf (Solaris).
Agent log files are located using the values defined in the agents section (TRACEFILE key) of the Domain Controller registry. By default, agent log files are located in: /var/vx/isis/vxisis33_agentname.log
By default, the StorageManager agent log resides in: /var/vx/isis/StorageManager/StorageManager_vxisis.log
vxpal may output messages similar to the following:
The input agent is not installed and configured on the machine. The registry entries for the agent are missing.
See veaconfig for agent configuration:
Agent agentname is not installed. vxpal -a unknownAgent
This message may be issued on stderr if there is a previously running instance of the specified agent. This can be verified using the ps command. If no other instance is running, remove lock file belonging to the specified agent. /var/vx/isis/agent_name. Lock and restart the agent:
Another instance of Agent <agentname> seems to be running.
This message is issued when a command is specified for run on an agent but insufficient information is provided. Every command requires that the agent be specified by the agent name in conjunction with the agents hostname and port or the agents hostname and domain name:
ERROR:Missing domain information for this agent
This message is issued when a command is specified for run on an agent but the domain information provided is not valid. The domain does not exist or cannot be contacted. Check to see that the status of the server on the Domain Controller. If up, confirm that the agent is participating in the domain:
ERROR: Domain invalid or cannot be contacted.
This section provides usage examples for vxpal.
The following command checks the status of the gridnode agent:
vxpal -a gridnode -c status
The following command sets the error logging level for actionagent to messages that are level 5 (warning) or higher:
vxpal -a actionagent -c settracelevel=5
The following command checks to see if the gridcentral agent is running:
vxpal -a gridcentral -c isalive -s gridcentral
The following command checks the status of the gridnode agent on the remote host, my_remote_host:
vxpal -a gridnode -c status -l my_remote_host.example.com -s gridnode
The following command checks the status of the gridnode agent on the remote host, my_remote_host, using a user ID other than the one declared in csf_resolv.conf. In this situation, vxpal will prompt for a password for the user ID. The Authentication Broker host in this example is my_ab_host:
vxpal -a gridnode -c status -u root@my_ab_host.example.com.unixpwd -l my_remote_host.example.com -s gridnode
The following command stops the actionagent agent on the remote host, my_remote_host:
vxpal -a actionagent -c stop -l my_remote_host.example.com -s actionagent
Last updated: 09/22/2008
Copyright ©2009 Symantec Corporation
All rights reserved.