Monitors many kinds of servers
InterMapper will monitor devices with pings and SNMP. But
this may not be enough to determine whether a particular server is
actively running. For example, the Web server might have stopped
delivering pages, even though the host computer might still be operating
and answering pings.
Built-in Probes
In addition to pings and SNMP probes, InterMapper has
dozens of built-in probe types. They are listed in the InterMapper User Guide. A sample selection of the
probes is listed below.
| UDP/DDP Probes |
SNMP Probes |
TCP Probes |
Automatic Ping/Echo DHCP DNS
Keyserver Multicast Stream NTP RADIUS RTMP
BlitzWatch
|
SNMP Probe SNMPv2c Probe Airport
Base Station Basic OID Cisco Aironet Cisco Router Probe
Cisco Router v2c Karlnet Wireless MIB TCP Check
|
4D Server AppleShare IP Basic TCP
Custom TCP CVS DND FileMaker FirstClass FTP
Gopher HTTP/HTTPS HTTP/HTTPS Post HTTP Proxy
HTTP Redirection IMAP4/IMAP4-SSL
|
IRC LDAP/LDAP-SSL Lotus Notes
LPR MeetingMaker NNTP POP3 RTSP
SMTP SMTP-TLS SNPP Telnet VNC Xserve Monitor
|
Build your own Custom Probes
In addition to its set of built-in probes, you can create
your own probes based on TCP connections, or on SNMP queries. TCP probes
can use a script language to send requests to the device being tested and
examine the response to determine the state of the device.
SNMP probes can request multiple MIB variables by OID, and
then compare the responses to user-defined thresholds to set the state of
the device.
Command-line (Plugin) Probes
InterMapper can run a program "from the command line" to
test a device. The program can be any executable program on your platform
- C or C++, Perl, Python, shell or .BAT script, etc. The result of the
program will set the device's condition. You can develop your own
programs, or use some of the the pre-written plugins/scripts that work
with NagiosŪ and Big Brother.
|