Page History
...
To use local agent control1. Run
Run the following command on the agent server:
Windows
...
infra\bin\psin_cli.bat
-i3-user <user
...
_
...
name>
{-i3-encrypted-password
...
<encrypted_
...
password> | -i3-clear-password
...
<clear_
...
password>}
-action control-agent-local
[-proxy-alias
...
<node_
...
alias>]
-product <product
...
_
...
code>
-installation
...
<installation_
...
code>
-type <type>
[-instance-name
...
<instance_
...
name>]
...
UNIX ./infra/bin/psin_cli.sh
-i3-user <user
...
_
...
name>
{-i3-encrypted-password
...
<encrypted_
...
password> | -i3-clear-password
...
<clear_
...
password>}
-action control-agent-local
[-proxy-alias
...
<node_
...
alias>]
-product <product
...
_
...
code>
-installation
...
<installation_
...
code>
-type <type>
[-instance-name
...
<instance_
...
name>]
...
Table 6-
...
2 Elements of the Local Agent Control
...
Element Description i3-
...
user See Authenticate to CLI Utility on page 8.
i3-encrypted-
...
password See Authenticate to CLI Utility on page 8.
...
action
...
Values: control-agent-local Mandatory: Yes
proxy-
...
alias The proxy alias. Values: alias of the related node
Mandatory: Only for a federated installation
product
...
The agent's product code. Values: See Product Codes on page 175.
Mandatory: Yes
installation
...
The agent installation type code. Values: See Installation Type Codes on page 175.
Mandatory: Yes
...
type Operation to perform on the agent. Values: One of: STATUS, STOP, START, IVP
instance-
...
name The agent's instances name. Values: string
Mandatory: Instance name argument should be supplied for agent which are per instance (instance column in AdminPoint>Agent, contains instance name)
...
...
Precise. Performance intelligence from click to storage. Learn more > >
...