SDX 6.4.x Network Guide > Configuring NIC Host Redundancy > Configuring Monitors

Configuring Monitors

You can add NIC monitors to track redundant components.

Complete the following tasks to configure NIC monitors:

1. Configuring Operating Parameters for Monitors
2. Configuring a Monitor Process
3. Configuring JacORB Properties on Redundant NIC Hosts
4. Starting NIC Hosts
5. Starting NIC Monitors

Configuring Operating Parameters for Monitors

You must configure operating parameters for each monitor in your NIC configuration. The operating parameters define how the monitor interacts with other SDX components, such as the directory.

To configure the operating parameters:

1. Log in as root.
2. Start the local configuration tool in the directory where you installed the redundancy monitor software.

/opt/UMC/monitor/etc/config

The Redundant Monitor window appears.

3. Set the parameters in each tab of this window. See Setting the JRE for a Redundant Monitor and Chapter 5, Locating Subscriber Information.
4. Click OK.

Setting the JRE for a Redundant Monitor

You can set the value for the Redundant Monitor Java in the Monitor tab.

Redundant Monitor Java

• Path to the JRE.
• Value—Path (absolute or relative) to the directory that contains the JRE
• Example—../jre/bin

Configuring a Monitor Process

You configure a monitor by adding it to a monitoring process, referred to as a monitor in SDX Configuration Editor

To configure a monitoring process:

1. In the configuration file for the NIC, click on the Redundancy tab.
2. Expand the Monitors entry, and create a new instance of a monitor (monitoring process).

The Monitor fields appear in the Redundancy pane.

3. Specify the monitors that this monitoring process supports.

Monitor List

• List of monitors that the monitoring process will support.
• Value—Comma-separated list of monitors; each monitor has the format <monitorName>:/communities/<communityName>

• <monitorName>—Name of monitor; must match the name specified in the community (see Configuring Communities)
• <communityName>—Name of community; must match the name specified in the configuration for the community (see Configuring Communities)

• Example—DemoMonitor:/communities/Demohost, nicSaeDemoMonitor:/communities/nicsaeDemo

Configuring JacORB Properties on Redundant NIC Hosts

If the system on which a NIC hosts resides uses an object request broker (ORB) different from the one provided in the SDX software distribution, it is important to configure some JacORB properties on each NIC host to enable the ORB to correctly determine when connections between redundant NIC hosts are unavailable. If you do not configure these properties properly, the ORB relies on the TCP default socket timeout (usually 8 minutes) to determine when a connection between redundant NIC hosts is unavailable or cannot be established. Using high values for these properties affects overall system availability.

To configure the JacORB properties:

1. With a text editor, open the jacorb.properties file.
2. Ensure that the property jacorb.connection.client_idle_timeout is uncommented, and set this property to a value between 5,000 and 30,000 milliseconds.
3. (JRE 1.4 only) If the default value is not appropriate for your network configuration, change the value of the property net.juniper.smgt.socket_factory.timeout.connect.
4. Save and close the jacorb.properties file.
5. Repeat Steps 1 to 4 for each NIC host.

jacorb.connection.client_idle_timeout

• Time after which the ORB assumes that an existing connection between two machines has become unavailable.
• Value—Number of milliseconds in the range 5000-30000
• Default—30000
• Example—jacorb.connection.client_idle_timeout=10000

net.juniper.smgt.socket_factory.timeout.connect

• Time after which the ORB assumes that a new connection cannot be established between two machines.
• Value—Number of milliseconds in the range 0-2147483647
• Default—5000
• Example—net.juniper.smgt.socket_factory.timeout.connect=10000

Starting NIC Monitors

You must start each NIC monitor before its associated components can begin operating.

To start a monitor:

1. On the machine on which the monitor is installed, log in as root or as an authorized nonroot admin user.
2. Start the monitor from its installation directory:

/opt/UMC/monitor/etc/monitor start

After you have started a monitor, you can view log files of its operation and stop the host or monitor (see SDX Monitoring and Troubleshooting Guide, Chapter 7, Managing the NIC).

Starting NIC Hosts

You must configure operating parameters for each NIC host and then start each NIC host before its associated components can begin operating. For information about how to configure NIC host parameters and how to start NIC hosts see Chapter 5, Locating Subscriber Information.