Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Monitoring Agent

 

Tasks to configure Monitoring Agent are:

Configuring Properties

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:

  1. On the server host, log in as root or as an authorized nonroot admin user.

  2. Verify that Monitoring Agent is not running. (See Displaying Monitoring Agent Status and Stopping Monitoring Agent).

  3. With a text editor, edit the /opt/UMC/monAgent/etc/ma_default.properties file.

    See Monitoring Agent Properties.

  4. Save the file.

  5. Start Monitoring Agent for the changes to take effect. (See Starting Monitoring Agent).

Monitoring Agent Properties

Monitoring Agent Properties

With a text editor, you can configure the following properties for 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.

  • Default—Empty

  • Example—dmfe0 dmfe1

MonAgent.capture.pool

  • Maximum number of concurrent event handlers.

  • Value—Integer in the range 0-2147483647

  • Default—8

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

  • Controls the attachment of the whole packet to the notification.

  • Value

    • true—Enables the attachment of the packet.

    • false—Disables the attachment of the packet.

  • Default—true

MonAgent.dhcp.enable

  • Controls the monitoring of DHCP messages.

  • Value

    • true—Enables the monitoring of DHCP messages.

    • false—Disables the monitoring of DHCP messages.

  • Default—true

MonAgent.radius.enable

  • Controls the monitoring of RADIUS messages.

  • Value

    • true—Enables the monitoring of RADIUS messages.

    • false—Disables the monitoring of RADIUS messages.

  • Default—true

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.radius.server

  • Controls the monitoring of RADIUS packets by the pseudo–RADIUS server on the RADIUS accounting port. If you enable the pseudo–RADIUS server, you must also set MonAgent.radius.enable=true.

  • Value

    • true—Enables the pseudo RADIUS server to receive RADIUS packets.

    • false—Disables the pseudo RADIUS server from receiving RADIUS packets.

  • Default—false

MonAgent.radius.secret.<IP address>

  • Shared secret between the RADIUS server and trusted RADIUS client. This value is ignored if MonAgent.radius.server is false.

  • Value—IP address and shared secret pair in the format MonAgent.radius.secret.<ip address>=<shared secret>

    For example, a RADIUS client with an IP address of 10.227.7.47 that has a shared secret of secret with the pseudo–RADIUS server would be specified as MonAgent.radius.secret.10.227.7.47=secret.

  • Default—MonAgent.radius.secret.127.0.0.1 = secret

MonAgent.ttl

  • Time before a subscriber session resulting from a detected IP address is automatically terminated. RADIUS interim accounting messages and DHCP renews will reset this timeout.

  • Value—Number of seconds in the range 0-2147483647

  • Guidelines—This timeout value should be larger than the RADIUS interim update interval. If you are certain that RADIUS messages will not be lost, we recommend 1.5 times the interim update interval. Otherwise, we recommend 2.5 times the interim update interval.

  • Default—1800

Configuring NIC Proxy

Configuring NIC Proxy

To configure a NIC proxy for the Monitoring Agent application, see NIC Proxy Configuration Overview.