Cisco Cisco Email Security Appliance C160 Mode D'Emploi

If you use only SNMPv1 or SNMPv2, you must set a community string. The community string does 
not default to 

public

.

For SNMPv1 and SNMPv2, you must specify a network from which SNMP GET requests are 
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.)

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.

Cisco Systems provides an “enterprise” MIB as well as a “Structure of Management Information” (SMI) 
file:

ASYNCOS-MAIL-MIB.txt — an SNMPv2 compatible description of the Enterprise MIB for Cisco 
appliances.

IRONPORT-SMI.txt — defines the role of the ASYNCOS-MAIL-MIB in IronPort’s SNMP 
managed products.

These files are available on the documentation CD included with your Cisco appliance. You can also 
request these files through Cisco Customer Support.

Hardware sensors conforming to the Intelligent Platform Management Interface Specification (IPMI) 
report temperature, fan speed, and power supply status.

 shows what hardware derived objects are available for monitoring on what models. The 

number displayed is the number of instances of that object that can be monitored. For example, you can 
query the RPMs for 3 fans in the C160/170 appliances and 6 fans in the C300/C600/X1000 appliances.

1

1

0

0

3

0

2

2

0 0

0

0

0

0

2 

(C60 

has 4)

3