Messaging Server implements two standardized MIBs, the Network Services Monitoring MIB (RFC 2788) and the Mail Monitoring MIB (RFC 2789). The Network Services Monitoring MIB provides for the monitoring of network services such as POP, IMAP, HTTP, and SMTP servers. The Mail Monitoring MIB provides for the monitoring of MTAs. The Mail Monitoring MIB allows for monitoring both the active and historical state of each MTA channel. The active information focuses on currently queued messages and open network connections (for example, counts of queued messages, source IP addresses of open network connections), while the historical information provides cumulative totals (for example, total messages processed, total inbound connections).
For a complete listing of Messaging Server SNMP monitoring information, refer to RFC 2788 and RFC 2789.
SNMP is supported on platforms running Solaris and Red Hat Linux. Messaging Server on the Solaris 9 Operating System uses Solstice Enterprise Agents (SEA). Starting with the Solaris 10 Operating System, Messaging Server supports the open source Net-SNMP monitoring framework, relegating the Solaris 9 OS Solstice Enterprise Agents (SEA) technology to legacy (end of support life) status. Additionally, Net-SNMP is widely used on Linux platforms. Messaging Server will use its Net-SNMP-based SNMP subagent on Solaris 10 and later as well as Linux platforms.
With the adoption of the Net-SNMP framework, Messaging Server's SNMP subagent provides new functionality:
Support for SNMP versions 2c and 3. This support is provided by the Net-SNMP framework. The former SNMP technology, Solstice Enterprise Agents, only provided support for SNMP version 1. Enhanced security features and access controls are the primary benefit of these two versions of SNMP.
The subagent may be configured to run as a "standalone" SNMP agent. This provides sites with additional means of isolating their various SNMP agents running on the same system.
Multiple "instances" of Messaging Server running on the same system may concurrently be monitored. This support is provided through either Item 2 above, or through the use of SNMP version 3 "context names". This allows for SNMP monitoring of Messaging Server in failover clusters.
Only one instance of Messaging Server per host computer can be monitored via SNMP on Solaris 9 OS.
The SNMP support is for monitoring only. No SNMP management is supported.
No SNMP traps are implemented. (RFC 2788 provides similar functionality without using traps.)
The Messaging Server SNMP process is an SNMP subagent which, upon startup, registers itself with the platform’s native SNMP master agent. SNMP requests from clients go to the master agent. The master agent then forwards any requests destined for the Messaging Server to the Messaging Server subagent process. The Messaging Server subagent process then processes the request and relays the response back to the client via the master agent. This process is shown in Figure A–1.