The following env-instances.sh settings are suitable to configure a P3 probe:

KALEID_<instance_id>_PATH=”/opt/tsa/bin/passive_latencyd3”
KALEID_<instance_id>_XMLRPC_PORT=<xmlrpc port number>
KALEID_<instance_id>_ARGS=” -h”

For usage instructions, see below:

USAGE:
 
/opt/tsa/bin/passive_latencyd3 {-i <id>|-f <filename>} [-p <port>]
[--check_model_only] [-e] [-m
<messages>] [--] [--version] [-h]
 
 
Where:
 
-i <id>, --id <id>
(OR required) Analyser ID in the database
-- OR --
-f <filename>, --config_filename <filename>
(OR required) JSON configuration filename
 
-p <port>, --xml_rpc_port <port>
XML RPC port to listen to
 
--check_model_only
Generates the model implementation and exits
 
-e, --enforce
Enforce some correlation engine rules
 
-m <messages>, --msg_pool_size <messages>
Initial message pool size
 
--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.
 
--version
Displays version information and exits.
 
-h, --help
Displays usage information and exits.

See Controlling VMX-Capture using the vmxadmin command for details of how to stop and start the P3 process.

P3 Process Licensing

As with other VMX-Capture components, the VMX-Capture P3 process needs a valid licence in order to run.

The licence specifies the following:

  • Client ID

  • Expiry date

  • Licence type

  • Maximum cores

  • Node Address

  • Capabilities

Multiple different directories are searched in order to find a valid licence file.

In descending priority order, with the first location searched listed first, PMUX processes will search for a valid licenses.cf file in the following locations:

  1. <confdir>/p3/<instance_id>/licenses.cf

  2. /opt/tsa/etc/licenses.cf

  3. global/licenses.cf

Contact your Beeks Account Manager to obtain a valid licence for your system.