Cisco Cisco Email Security Appliance C160 Mode D'Emploi
34-37
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
Chapter 34 Managing and Monitoring Using the CLI
Monitoring System Health and Status with SNMP
•
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 enable and configure SNMP monitoring. 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
The following MIB files for Cisco Email Security Appliances are available from
. Use the latest available MIB files.
•
ASYNCOS-MAIL-MIB.txt — an SNMPv2 compatible description of the Enterprise MIB for Cisco
appliances.
appliances.
•
AsyncOS-SMI.txt (IRONPORT-SMI.txt) — a “Structure of Management Information” (SMI) file
that defines the role of the ASYNCOS-MAIL-MIB in Cisco content security products.
that defines the role of the ASYNCOS-MAIL-MIB in Cisco content security products.
Hardware Objects
Hardware sensors conforming to the Intelligent Platform Management Interface Specification (IPMI)
report information such as temperature, fan speed, and power supply status.
report information such as temperature, fan speed, and power supply status.
It is a good idea to poll for the hardware status and identify possible hardware failures before they
become critical. Temperatures within 10 per cent of the critical value may be a cause for concern.
become critical. Temperatures within 10 per cent of the critical value may be a cause for concern.
For information such as the number of power supplies and the range of operating temperatures for your
appliance, see the hardware guide for your model. For the location of hardware guides, see
appliance, see the hardware guide for your model. For the location of hardware guides, see
.
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).
every 5 seconds. The other traps are failure condition alarm traps — they are sent once when the state
changes (healthy to failure).
For example, if the following thresholds are reached, traps are sent from C170 appliances:
Table 34-11
Hardware Traps on C170 Appliances: Temperature and Hardware Conditions
Model
High
Temp
(CPU)
Temp
(CPU)
High Temp
(Ambient)
(Ambient)
High Temp
(Backplane)
(Backplane)
High
Temp
(Riser)
Temp
(Riser)
Fan
Failure
Failure
Power
Supply
Supply
RAID
Link
C170
90C 47C NA
NA 0
RPMs
Status
Change
Change
Status
Change
Change
Status
Change
Change