Cisco Cisco Web Security Appliance S690 사용자 가이드
S N M P T R A P S
C H A P T E R 1 8 : M O N I T O R I N G
409
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.
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.
Note that failure condition alarm traps represent a critical failure of the individual
component, but may not cause a total system failure. For example, a single fan or power
supply can fail on a S650 appliance and the appliance will continue to operate.
component, but may not cause a total system failure. For example, a single fan or power
supply can fail on a S650 appliance 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 IronPort appliance). After the condition has been met, the SNMP agent then
forms an SNMP packet and sends it over port 162, the standard SNMP trap port. In the
example below, the trap target of
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 IronPort appliance). After the condition has been met, the SNMP agent then
forms an SNMP packet and sends it over port 162, the standard SNMP trap port. In the
example below, the trap target of
10.1.1.29
and the Trap Community string are entered.
This is the host running the SNMP management console software that will receive the SNMP
traps from the IronPort appliance.
traps from the IronPort appliance.
You can configure SNMP traps (enable or disable specific traps) when you enable SNMP for
an interface. To specify multiple trap targets: when prompted for the trap target, you may enter
up to 10 comma separated IP addresses.
an interface. To specify multiple trap targets: when prompted for the trap target, you may enter
up to 10 comma separated IP addresses.
CLI Example
In the following example, the
snmpconfig
command is used to enable SNMP on the
“PublicNet” interface on port 161. A passphrase for version 3 is entered and then re-entered
for confirmation. The system is configured to service version 1 and 2 requests, and the
community string
for confirmation. The system is configured to service version 1 and 2 requests, and the
community string
public
is entered for GET requests from those versions 1 and 2. The trap
target of
10.1.1.29
is entered. Finally, system location and contact information is entered.
example.com> snmpconfig
Current SNMP settings:
SNMP Disabled.
Current SNMP settings:
SNMP Disabled.
Choose the operation you want to perform:
- SETUP - Configure SNMP.
[]> setup
- SETUP - Configure SNMP.
[]> setup
Do you want to enable SNMP? [N]> y
Please choose an IP interface for SNMP requests.
1. Management (192.168.1.1/24: wsa01-vmw1-tpub.qa)
[1]>
1. Management (192.168.1.1/24: wsa01-vmw1-tpub.qa)
[1]>
Enter the SNMPv3 passphrase.