Filter
Top Products
agent_config
NAME
agent_config -- Access HP Application Discovery Certificate on Managed System
SYNOPSIS
Path: /opt/amgr/bin/agent_config
agent_config -a [-dir config_directory]
agent_config -amx
agent_config -c
agent_config -printAgentTrust
agent_config -r
agent_config -start
agent_config -stop
DESCRIPTION
The agent_config command allows you to interact with an HP Application Discovery agent
to print its certificate or to remove a counterpart CMS certificate, and to check the status of the
agent, to start an AD agent, or to stop an AD agent.
You can use agent_config remotely from the HP SIM graphical user interface or from the
command line on a managed system. You will need root access to use this command.
Options
If no options are specified, the usage string is printed, and the command exits.
The agent_config command recognizes the following options.
-a
Copies CMS certificate from standard input to directory
specified by config_directory. First line following this is expected
to be the name of the CMS. Agent certificate is printed to
standard output.
-amx
Print agent certificate to standard output.
-c
Check agent state on a managed node.
-dir config_directory
Destination to which to copy the certificate.
-printAgentTrust
Print the trusted certificate of the HP Application Discovery
agent.
-pushWbemAccessList
Store HP Application Discovery WBEM provider access list
from standard input.
-r
Remove the target CMS certificate from a managed node.
-start
Start the agent as a daemon on a managed node.
-stop
Stop the agent on a managed node.
Installation
The agent_config command can be installed from a depot available on the HP VSE Managed
Node Software Update Web site. For installation instructions, please visit the VSE Management
Web site at the following URL:
http://docs.hp.com/en/vsemgmt/agents.html
Beginning with VSE Management Software Version A.03.00.00, agent_config is installed on
the CMS when the VSE Management Software is installed.
RETURN VALUES
0 The command completed successfully; no errors were detected.
1 An error occurred and the command did not complete successfully.
3 Unrecognized command parameters are detected.
4 Missing post-install configuration of AD agent is detected.
59