Configuring Monitoring Agent
This section lists the configuration tasks for Monitoring Agent.
Configuring Properties
The properties for Monitoring Agent determine the behavior of the application. The default values allow the Monitoring Agent application to operate, but you can specify different timeout values, device names, or RADIUS ports.
To configure properties for Monitoring Agent:
- On the server host, log in as
rootor as an authorized nonroot admin user.- Verify that Monitoring Agent is not running. (See Displaying Monitoring Agent Status and Stopping Monitoring Agent.)
- With a text editor, edit the /opt/UMC/monAgent/etc/ma_default.properties file. Change the properties using the following descriptions to configure the Monitoring Agent application.
- Save the file.
- Start Monitoring Agent for the changes to take effect. (See Starting Monitoring Agent.)
MonAgent.capture.devices
- Space-delimited list of devices where packets are captured. When this list is empty, packets on all available interfaces are captured.
- Value—Text string in the format <interfaceName> <interfaceName>
- <interfaceName> identifies the network interface on the host where the Monitoring Agent application is running.
MonAgent.capture.pool
MonAgent.timeout
- Time to keep an event handler alive for reuse.
- Value—Number of seconds in the range 0-2147483647
- Default—300
MonAgent.event.timeout
- Time to wait before discarding failed events.
- Value—Number of seconds in the range 0-2147483647
- Default—300
MonAgent.event.retry_time
- Time to wait before retrying failed events.
- Value—Number of seconds in the range 0-2147483647
- Default—30
MonAgent.dhcp.packet.forward
MonAgent.dhcp.enable
MonAgent.radius.enable
MonAgent.radius.port
- UDP port on which RADIUS accounting messages are expected.
- Value—Integer; valid port number in the range 1-65535
- Default—1813
MonAgent.ttl
- Time to wait for a detected IP address.
- Value—Number of seconds in the range 0-2147483647
- Guidelines—This timeout value should be larger than interim update interval; we recommend twice the value.
- Default—1800
Configuring NIC Proxy
To configure a NIC proxy for the Monitoring Agent application, see SDX Network Guide: SAE, Juniper Networks Routers, and NIC, Chapter 7, Configuring Applications to Communicate with an SAE.