Cisco Cisco Web Security Appliance S160 Guia Do Utilizador

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 host name, but if you do, traps will only work if DNS 
is working.)

MIB files are available from 

Use the latest version of each MIB file. 

There are multiple MIB files: 

asyncoswebsecurityappliance-mib.txt — an SNMPv2 compatible description of the Enterprise MIB 
for Web Security appliances.

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

IRONPORT-SMI.txt — This “Structure of Management Information” file defines the role of the 
asyncoswebsecurityappliance-mib.

This release implements a read-only subset of MIB-II as defined in RFCs 1213 and 1907. 

To configure SNMP to gather system status information for the appliance, use the 

snmpconfig

 command 

in the command-line interface (CLI). After you choose and configure values for an interface, the 
appliance responds to SNMPv3 GET requests. 

When you use SNMP monitoring, keep the following points in mind: 

These version 3 requests must include a matching passphrase. 

By default, version 1 and 2 requests are rejected. 

If enabled, version 1 and 2 requests must have a matching community string. 

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

To determine the hardware-related objects available for monitoring (for example, the number of fans or 
the operating temperature range), see the hardware guide for your appliance model.