[ Main Index | HowTo Index ]

ipSentry provides the built in capability of being remotely monitored by another installation of ipSentry to make sure that the application is running.  

The logic used behind this is quite simple.

  • ipSentry is installed on two machines (Master & Secondary)

  • The Master will be the installation that performs monitoring of your network devices.

  • The Secondary will simply monitor the Master to make sure it is functioning.

  • In the simplest terms, you will be turning on a feature and creating a device entry within the ipSentry machine list to cross-monitor the two applications.

In order to accomplish this, you must first install ipSentry on two different machines that are accessible to each other over TCP/IP on the port numbers defined using the below procedures (we will use port 6767 as an example).

The following steps will apply to configuration on both ipSentry systems.

Enabling the feature.

  1. From the ipSentry active display console, select Action, System Options.

  2. On the Remote Access tab, make sure that Redundant Monitor Port is checked.

  3. Set the port # field to 6767 (or other unused TCP port)

  4. Press OK to save the changes.

  5. ipSentry must be restarted for this change to become active since ipSentry opens the port for listening upon startup.

Utilizing the feature (On the secondary ipSentry system)

  1. From the ipSentry active display console, select Options, Edit Devices.

  2. Select to add a new NETWORK (Custom Port Monitor) entry.

  3. Set the Type, of entry to "Network TCP/IP"

  4. Set the following fields:
    Name: {unique descriptive name}
    Description: {meaningful description - ipSentry Backup / Master}
    IP Address:  The address of the other ipSentry machine on which Redundant Monitor Port is enabled.
    Port: 6767 (or the port specified in the configuration on the remote system.)
    Data To Send: ^
    Data To Receive: ipSentry
    Timeout: 10
    The remainder of the fields and alert options will be up to you.

Now, when the ipSentry cycle checks this device and it fails, you will be notified via the alert options you have specified for this device.  If ipSentry is not running or either ipSentry monitoring system is down, you will be aware that your network is not being monitored and that you should take immediate action to correct the problem.

Note: We recommend setting the "First After" alert schedule value to '2' since ipSentry could possibly be in the middle of an activity that may not allow it to respond within the time frame specified in step 5 above. 

     If you require additional assistance, please visit our on-line support forum at http://forum.ipsentry.com.
  Copyright ┬ę1997-2018 by RGE, Inc. - All Rights Reserved
  ipSentry┬« is a registered trademark of RGE, Inc.
Web Site: https://ipsentry.com
Support Email: support@ipsentry.com