hvragenttest

Usage

hvragenttest [-Cagent_pub_cert_fname] [-Kclient_pub_cert_fname] [-kclient_priv_key_fname] [-Luser[/pwd]] [-S] [-stoken] host port

Description

Command hvragenttest tests the remote connection to HVR Agent. To test the connection to the HVR Agent, execute the command hvragenttest on the machine from which you are connecting to the HVR Agent. You can also check whether hvragentlistener is running by executing the hvragenttest command directly on the HVR Agent machine.

Options

This section describes the options available for command hvrtestagent.

Parameter	Description
`-Cagent_pub_cert_fname`	The directory path where a PEM file containing the agent public certificate is located. This is required to verify the identity of the remote HVR Agent by verifying its public certificate. For more information, see the agent property Agent_Server_Public_Certificate.
`-Kclient_pub_cert_fname`	The directory path where a PEM file containing the client public certificate is located. This is required to verify the public certificate and private key (option `-k`) of the hub that connects to the agent. For more information, see the repository property Agent_Client_Public_Certificate.
`-kclient_priv_key_fname`	The directory path where a PEM file containing the client private key is located. A password will be prompted for the client private key. For more information, see the repository properties Agent_Client_Private_Key and Agent_Client_Private_Key_Password.
`-Luser[/pwd]`	Authenticate with the user name (`user`) or user name and password (`user/pwd`) on the agent machine for connecting the hub to the agent. If you do not specify a password `pwd`, it will be prompted for. This option cannot be combined with options `-S` and `-s`. For more information, see the location properties Agent_User and Agent_Password.
`-Ttestcase`	Perform test (requires successful authorization). Valid values for `testcase` are: perf: Performance test ping: Network performance test echo: Network liveliness test: echo sleep: Network liveliness test: sleep
`-tN`	Timeout after `N` seconds if the network is hanging or it takes too long for the agent to reply.
`-S`	Authenticate using the time-based setup mode. This option cannot be combined with options `-L` and `-s`. For more information, see the agent property Setup_Mode_Timed_Until.
`-stoken`	Authenticate using the token-based setup mode. This option cannot be combined with options `-L` and `-S`. For more information, see the agent properties Setup_Mode_Token_Name and Setup_Mode_Token_Value.
`-v`	Verbose. Print the discovered location properties of the agent.

Examples

This section provides examples of using the hvragenttest command.

Example 1. Check connection to HVR Agent

You can check the connection to the HVR Agent installed/running on a remote machine with username and password authentication enabled. Execute the following command on the hub machine or on the machine from which you are connecting to the HVR Agent:

hvragenttest -L myuser/mypassword mynode 4343

Sample output in Linux with successful authentication and also indicating that the agent listener is running:

hvragenttest: HVR 6.0.1/2 (linux_glibc2.17-x64-64bit)
hvragenttest: Agent version 6.0.1/2.
hvragenttest: Authentication with username and password enabled.
hvragenttest: Authentication successful.
hvragenttest: Finished. (elapsed=0.34s)

Example 2. Check whether hvragentlistener is running

After installing and starting the HVR Agent Listener service, you can verify whether the hvragentlistener is running on the agent machine. Execute the following command on the agent machine:

hvragenttest mynode 4343

Sample output in Windows with successful authentication indicating that the agent listener is running:

hvragenttest: HVR 6.0.1/2 (windows-x64-64bit)
hvragenttest: Agent version 6.0.1/2.
hvragenttest: Authentication with username and password enabled.
hvragenttest: Authentication successful.
hvragenttest: Finished. (elapsed=0.18s)