CHAPT ER
30-1
Cisco ME 3400 Ethernet Access Switch Software Configuration Guide
OL-9639-06
30
Configuring Embedded Event Manager
This chapter describes how to use the embedded event manager (EEM) to monitor and manage the Cisco
ME 3400 Ethernet Access switch and how to configure it. The switch must be running the metro IP
access or metro access image to support this feature.
Note For complete syntax and usage information for the commands used in this chapter, see the command
reference for this release and the Cisco IOS Configuration Fundamentals and Network Management
Command Reference, Release 12.3T. For complete configuration information, see the Cisco IOS Network
Management Configuration Guide, Release 12.4T.
This chapter consists of these sections:
• Understanding Embedded Event Manager, page 30-1
• Configuring Embedded Event Manager, page 30-5
• Displaying Embedded Event Manager Information, page 30-7

Understanding Embedded Event Manager

The embedded event manager (EEM) monitors key system events and then acts on them though a set
policy. This policy is a programmed script that you can use to customize a script to invoke an action
based on a given set of events occurring. The script generates actions such as generating custom syslog
or Simple Network Management Protocol (SNMP) traps, invoking CLI commands, forcing a failover,
and so forth. The event management capabilities of EEM are useful because not all event management
can be managed from the switch and because some problems compromise communication between the
switch and the external network management device. Network availability is improved.if automatic
recovery actions are performed without rebooting the switch,
Figure 30-1 shows the relationship between the EEM server, the core event publishers (event detector s),
and the event subscribers (policies). The event publishers screen events and when there is a match on an
event specification that is provided by the event subscriber. Event detectors notify the EEM server when
an event occurs. The EEM policies then implement recovery based on the current state of the system and
the actions specified in the policy for the given event.