Configuring snmp traps – Cisco ASA 5505 User Manual

Page 1800

Advertising
background image

79-20

Cisco ASA 5500 Series Configuration Guide using the CLI

Chapter 79 Configuring SNMP

Configuring SNMP

What to Do Next

See the

“Configuring SNMP Traps” section on page 79-20

.

Configuring SNMP Traps

To designate which traps that the SNMP agent generates and how they are collected and sent to NMSs,
enter the following command:

Command

Purpose

snmp-server enable traps

[all |

syslog

| snmp [authentication |

linkup | linkdown | coldstart |

warmstart] | entity [config-change |

fru-insert | fru-remove |

fan-failure

| cpu-temperature | chassis-fan-

failure | power-supply-failure] |

chassis-temperature |

power-supply-presence |

power-supply-temperature] ikev2

[start | stop] |ipsec [start | stop]

| remote-access

[session-threshold-exceeded]|

connection-limit-reached

| cpu

threshold rising

|

interface-threshold

|

memory-threshold

| nat

[packet-discard]

Example:

hostname(config)# snmp-server enable

traps snmp authentication linkup

linkdown coldstart warmstart

Note

The interface-threshold trap is not
supported on the ASASM.

Sends individual traps, sets of traps, or all traps to the NMS. Enables syslog
messages to be sent as traps to the NMS. The default configuration has all
SNMP standard traps enabled, as shown in the example. To disable these traps,
use the no snmp-server enable traps snmp command. If you enter this
command and do not specify a trap type, the default is the syslog trap. By
default, the syslog trap is enabled. The default SNMP traps continue to be
enabled with the syslog trap. You need to configure both the logging history
command and the snmp-server enable traps syslog command to generate traps
from the syslog MIB. To restore the default enabling of SNMP traps, use the
clear configure snmp-server command. All other traps are disabled by default.

Keywords available in the admin context only:

connection-limit-reached

entity

memory-threshold

Traps generated through the admin context only for physically connected
interfaces in the system context:

interface-threshold

All other traps are available in the admin and user contexts in single mode. In
multi-mode, the fan-failure trap, the power-supply-failure trap, and the
cpu-temperature trap are generated only from the admin context, and not the
user contexts (applies only to the ASA 5512-X, 5515-X, 5525-X, 5545-X, and
5555-X).

If the CPU usage is greater than the configured threshold value for the
configured monitoring period, the cpu threshold rising trap is generated.

When the used system context memory reaches 80 percent of the total system
memory, the memory-threshold trap is generated from the admin context. For
all other user contexts, this trap is generated when the used memory reaches 80
percent of the total system memory in that particular context.

Note

SNMP does not monitor voltage sensors.

Advertising