Cisco Cisco Email Security Appliance C160 Mode D'Emploi
34-37
User Guide for AsyncOS 9.7 for Cisco Email Security Appliances
Chapter 34 Managing and Monitoring Using the CLI
SNMP Monitoring
•
If you use only SNMPv1 or SNMPv2, you must set a community string. The community string does
not default to
not default to
public
.
•
For SNMPv1 and SNMPv2, you must specify a network from which SNMP GET requests are
accepted.
accepted.
•
To use traps, an SNMP manager (not included in AsyncOS) must be running and its IP address
entered as the trap target. (You can use a hostname, but if you do, traps will only work if DNS is
working.)
entered as the trap target. (You can use a hostname, but if you do, traps will only work if DNS is
working.)
Use the
snmpconfig
command to configure SNMP system status for the appliance. After you choose and
configure values for an interface, the appliance responds to SNMPv3 GET requests. These version 3
requests must include a matching password. By default, version 1 and 2 requests are rejected. If enabled,
version 1 and 2 requests must have a matching community string.
requests must include a matching password. By default, version 1 and 2 requests are rejected. If enabled,
version 1 and 2 requests must have a matching community string.
MIB Files
MIB files for Cisco Email Security Appliances are available from
MIB files include:
•
AsyncOS Mail MIB for ESA (ASYNCOS-MAIL-MIB.txt) — an SNMPv2 compatible description
of the Enterprise MIB for Cisco appliances.
of the Enterprise MIB for Cisco appliances.
•
AsyncOS SMI MIB for ESA (IRONPORT-SMI.txt) — a “Structure of Management Information”
(SMI) file that defines the role of the ASYNCOS-MAIL-MIB.
(SMI) file that defines the role of the ASYNCOS-MAIL-MIB.
Hardware Objects
Hardware sensor reporting conforms to the Intelligent Platform Management Interface Specification
(IPMI).
(IPMI).
Hardware Traps
Status change traps are sent when the status changes. Fan Failure and high temperature traps are sent
every 5 seconds. The other traps are failure condition alarm traps — they are sent once when the state
changes (healthy to failure). It is a good idea to poll for the hardware status tables and identify possible
hardware failures before they become critical. Temperatures within 10 per cent of the critical value may
be a cause for concern.
every 5 seconds. The other traps are failure condition alarm traps — they are sent once when the state
changes (healthy to failure). It is a good idea to poll for the hardware status tables and identify possible
hardware failures before they become critical. Temperatures within 10 per cent of the critical value may
be a cause for concern.
Note that failure condition alarm traps represent a critical failure of the individual component, but may
not cause a total system failure. For example, when there are multiple fans or power supplies, a single
fan or power supply can fail and the appliance will continue to operate.
not cause a total system failure. For example, when there are multiple fans or power supplies, a single
fan or power supply can fail and the appliance will continue to operate.
SNMP Traps
SNMP provides the ability to send traps, or notifications, to advise an administration application (an
SNMP management console, typically) when one or more conditions have been met. Traps are network
packets that contain data relating to a component of the system sending the trap. Traps are generated
when a condition has been met on the SNMP agent (in this case, the Cisco appliance). After the condition
has been met, the SNMP agent then forms an SNMP packet and sends it over port 162, the standard
SNMP management console, typically) when one or more conditions have been met. Traps are network
packets that contain data relating to a component of the system sending the trap. Traps are generated
when a condition has been met on the SNMP agent (in this case, the Cisco appliance). After the condition
has been met, the SNMP agent then forms an SNMP packet and sends it over port 162, the standard