Simple Network Monitoring Protocol (SNMP)Network and Network Component Monitoring
Isode's own GUI tools, such as MConsole, and M-Vault Console are ideal for monitoring Isode's servers in smaller configurations. Larger deployments will often use SNMP (Simple Network Monitoring Protocol) to monitor a wide range of network and other components.
SNMP is supported by many network components and applications as well as a wide range of management consoles. Isode servers incorporate SNMP capabilities for integration with third-party monitoring tools.
Isode uses as sub-agent model for support of SNMP. This works by having a single Master Agent on a server, that will respond to external queries. Then the master agent interacts with sub-agents associated with each of the monitored servers. This enables the Management Console to get information from the application. Isode uses the Internet Standard AgentX protocol (RFC 2741) to communicate between the master agent and sub-agent. Full sub-agent and AgentX support is included with the Isode servers.
MADMAN MIB Support
The SNMP framework enables monitoring of a large variety of network components and applications, in a manner which can be integrated with the general monitoring of an enterprise infrastructure, by use of the MIB (Management Information Base) concept.
An MIB defines the variables that are available in the application to be monitored using SNMP. Isode servers support monitoring using the latest MIBs, collectively known as the MADMAN (Mail and Directory MANagement) MIBs, these are:
There are three Internet Standard MIBs of particular importance to Isode, that are collectively known as the MADMAN (Mail And Directory MANagement) MIBs. These are:
RFC 2788 Network Services Monitoring
RFC 2788 defines a generic MIB that is appropriate to any application that can make a network connection. It provides information on the basic application status, and information on active connections, including how long the connection has been running and the protocol. Isode supports this MIB for its M-Vault and M-Switch products, and plans to extend it to use in other servers. This MIB provides basic information, which is supplemented by two specific MIBs. This MIB is illustrated above, showing a system running two networked applications
RFC 2789 Mail Monitoring
RFC 2789 defines additional information for a message switch. This includes information on messages queued, and historical information on messages transferred in and out over various channels. This MIB is implemented in Isode's M-Switch products
RFC 2605 Directory Server Monitoring
RFC 2605 defines additional information for a directory server, and in particular information on the various directory operations performed, so that directory operation rate and performance can be monitored. This MIB is implemented in Isode's M-Vault products.
Isode's MIB implementation can be observed using a MIB Browser that connects with SNMP to examine the MIB contents and interpret them in terms of the MIB definitions. MIBs are defined in a standard format, and a management console will usually import these to help render the information in a useful manner. Isode recommends the Unbrowse MIB browser from Unleash Networks.
The SNMP monitoring has been tested with a number of SNMP monitors, including SunNet Manager and HP Openview. For more information on Isode's approach to SNMP, see the whitepaper [SNMP and Isode Servers].
|RFC 2605||Directory Server Monitoring MIB. S. Kille, G. Mansfield, June 1999|
|RFC 2788||Network Services Monitoring MIB. S. Kille, N. Freed, March 2000|
|RFC 2789||Mail Monitoring MIB. S. Kille, N. Freed, March 2000|