 |
IPSentry - Server Settings - Network
After selecting "Network" on the left side of the "Server Settings" tab, you will have access to the following fields for configuration.
Please see the How-To section for additional information on various configurations.
Name
Select a short yet meaningful name to describe this monitor entry.
The name must be unique in order to identify this configuration from any other.
Also note that when IPSentry cycles through these items, the devices are ordered
alphabetically. Dependent machines are ordered within their respective
parent machines. Therefore, a system named AROUTER will be checked before
an item named CROUTER.
Description
Use this field to further describe this monitoring entry. A brief
description of the unit, device, etc. In many cases, this can be the same
as the name however it can be better used for various identification
purposes. This field must contain a value even though the value is used
only for various 'display' operations.
IP Address
Enter the TCP/IP Address of the host you wish to monitor in dotted numeric
notation (i.e. 10.1.1.4). While using the domain name will work for
performing monitoring, if your domain name server is not available to resolve
the domain name, IPSentry may consider this unit unavailable and alert you
to a failure on this device when the actual cause of the failure is due to DNS
resolution failure on only the DNS servers specified in your system networking
configuration.
Port
The port setting (combined with Data To Receive and Data To Receive) is what
makes IPSentry so incredibly flexible. You may either select one of
IPSentry's pre-configured well-known ports in the drop-down list (these are
well-known ports such as HTTP, SMTP, POP3, NNTP, etc..) or you can enter your
own port number for more customized entry. (See the How-To
section for
more information on custom port uses.)
Note: Special (non-standard) Port Numbers
If you are using non-standard ports for some of the standard protocols such as
HTTP, ECHO, TELNET, etc. You can select the port type HTTP, ECHO, etc.. -
click Auto Configure and then change the port to the non-standard port number
you are using (such as 8080 for HTTP).
Note: Re: ICMP-Ping
ICMP-Ping requires Windows 98 or NT. On Windows 95, you must install the
latest Windows 95 Winsock 2 update from Microsoft. Also, IPSentry
will perform a default of 4 internal retries to obtain a ping response. If
a response is not received in the amount of time specified in the Timout field,
another ICMP packet will be sent. You can override this value by making
the following modification in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\RGE INC\IPSentryV4\SysInfo:ICMPInternalRetry=n
where (n) = the number of internal retries. The default value is 4.
TTL {only available
when port is set to ICMP-Ping}
Represents the maximum number of hops allowed for an ICMP packet. The
default is 0 (or no limit) and should only be changed if the hop-count is a
critical issue.
Data To Send
After IPSentry makes a connection to the server at IP Address on the specified
Port, IPSentry will attempt to send the data contained in this field. (i.e.
Standard HTTP Data To Send: GET / HTTP/1.0^^ will send a GET request for the
default page - usually default.htm or index.html)
There are a couple special characters that are transformed in this field and you
must be aware.
They are:
^ = Converted to a Line Feed (x0A, Dec:10)
~ = Converted to a Carriage Return (x0D, Dec:13)
If you require specific symbols or characters to be sent to the remote host
(such as high ASCII or nulls), you can use the HEX translation sequence of &Hxx
to send binary data to the remote host.
i.e. &H0A would be converted the same as using the special character ^.
If you need to send one of the two special characters, you can use &H5E for
~, and &H7E for ^.
Data To Receive
After IPSentry connects and any data in the Data To Send field is successfully
sent to the remote host, IPSentry will await the arrival of the contents of this
field. This is case-sensitive and incorporates the same character rules as
the Data To Send field. If you are unsure of the data that will be
received, but you know that something will be received, you can use '*'.
If any data is received and the Data To Receive field is set to *, IPSentry will
consider this as a success. (See the How-To
section for more information on
custom port uses.)
Auto Config
(button)
IPSentry comes pre-configured with several standard protocol options (HTTP,
NNTP, SMTP, NNTP,FTP, etc..). When using one of the pre-configured ports,
you may click this button to automatically configure the Data To Send and Data
To Receive fields with the appropriate information as outlined in the protocols
respective RFC of initial respones.
For example, if you have selected HTTP as your port, IPSentry will set the
following:
Data To Send: GET / HTTP/1.0
Data To Recv: HTTP/1.
While receipt of HTTP/1. does not guarantee anything more than the web server
sending a response, it is the most basic response to ensure the server is
accessible.
Note: HTTP/1. will appear in the header of any response from the server, so
if the response is a "Document Not Found" or one of many other errors,
that will not be detected.
If you want to ensure that the page is being delivered, you must set the Data To
Recv field to text that will only appear in the results (HTML Source) normally
received by a browser.
Timeout
Enter to number of seconds that IPSentry should wait for the completion of
Connect, Send, or Receive. You can set this field to {default} in order to
use the value specified when configuring the default machine.
When using ICMP-Ping, this value is represented in milliseconds rather than
seconds in order to give you finer control over acceptable network speeds.
Remember to set this value accordingly (1000 = 1 Second) We recommend
setting this value to 1000 or great for ICMP-Ping monitoring since there is some
internal routines running that may cause timing delays.
COMMON TO ALL MONITORING TYPES
Schedule (Button)
This will bring up the IPSentry Down-Time Scheduling tool and allow you to
specify what times during which days that this entry should or should not be
monitored.
(See Down-Time Scheduling )
Reverse Alert
In some cases, you may find it necessary to be notified when a server or network
device is available as opposed to unavailable. (I.e. Specific DHCP lease
activated, or a backup system has been enabled). By selecting this option,
a successful attempt on the device will trigger the alerts and a failure will
simply continue on to the next monitored device.
Suspend Sentry
Select this option to suspend this
monitoring option indefinitely. No monitoring or alerting will be
performed on this entry until the suspend flag has been removed. You can
easily identify suspended machines in the item list as identified by the yellow
triangular warning icon.
In version 4.6.55 and later, you are not prompted for the duration in
Days:Hours:Minutes. The release date/time is calculated from the moment
you hit "OK". Leaving the field blank or entering 0:0:0 will suspend the
item indefinitely.
Poll Frequency
Some systems require a more or less frequent monitoring. In order to
decrease network overhead, you scan select to have IPSentry skip a monitoring
entry for the defined number of cycles.
For example: If you enter a value of 5 in this field, IPSentry will have to
perform 5 full monitoring cycles before this entry will be monitored once.
If you have your Sentry Cycle Interval set to 5, that would be a minimum of once
very 5*5 or 25 minutes. Then, you must add-in the amount of time consumed
to complete an entire cycle and multiply that times this value.
Depends On
Provides a list of existing monitoring entries from which you may select one
that MUST be available (successful) before the current entry will be checked.
For Example: If Web1 is on the other side of Router1, there is no need to
check Web1 if Router1 is down. While editing the Web1 configuration,
you would select Router1 for this field. This would cause Web1 to be
skipped whenever there is a failure at Router1.
Sync Failure
Count
Checking this option keeps the Attempt + Failure counters synchronized among
dependents of specific machines. If the entry on which this item depends
is in a failure status, this item will be skipped yet the failure counters will
be incremented.
Example: If Web1 Depends on Router1 and Router1 fails, Web1 will also show as a
failure thereby reducing the up-time percentage.
Current
Dependents
This area lists all the monitoring entries that depend on the success of this
machine whether directly, or indirectly through another machine. This area
provides a basic tree-view of dependency information for the given device.
Add (button)
Use this option to quickly add direct dependents to this device by selecting the
entries from a list presented after clicking this button. Simply check the
items that will depend on the current machine and click OK.
Remove (button)
Use this option to quickly remove the selected dependent from this device.
Simply highlight the dependent that should no longer depend on the current
device and hit the Remove button.
Copy From (button)
This option loads a list of machines from which you can copy the entire
configuration. Very handy when you have several entries to create that are
all relatively similar in function (i.e. Adding 10 web servers where the only
difference is the IP Address, adding 25 routers with only the IP Address being
different.) (See Copy From )
Order Alerts
(button)
When you hit this button, you will be presented with the list of alerts in the
order in which they will be triggered. In some cases, you may want to have
fast alerts such as Email, Syslog, Launch, executed before the pager alerts.
In other cases, you may want pager alerts to be the first alert triggered.
Use this option to order the alerts to meet your specific needs. (See Ordering
Alerts)
Test (button)
This button simply tests the device monitoring configuration as entered.
You will either receive a "Sentry OK" response if no alerts would be
triggered based on the result of the test, or you will receive a
"Failed" message noting that in live operation, any configured alerts
would have been triggered.
This allows you test a known 'good' system to ensure that your settings are
correct.
SCREEN SAMPLES
|
|
||
| Contact: support@ipsentry.com | https://ipsentry.com | © 2006 by RGE, Inc. - All Rights Reserved |