EasyManuals Logo

Cisco ME 3400 User Manual

Cisco ME 3400
1138 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #576 background imageLoading...
Page #576 background image
30-4
Cisco ME 3400 Ethernet Access Switch Software Configuration Guide
OL-9639-07
Chapter 30 Configuring Embedded Event Manager
Understanding Embedded Event Manager
Embedded Event Manager Actions
These actions occur in response to an event:
• Modifying a named counter.
• Publishing an application-specific event.
• Generating an SNMP trap.
• Generating prioritized syslog messages.
• Reloading the Cisco IOS software.
Embedded Event Manager Policies
EEM can monitor events and provide information, or take corrective action when the monitored events
occur or a threshold is reached. An EEM policy is an entity that defines an event and the actions to be
taken when that event occurs.
There are two types of EEM policies: an applet or a script. An applet is a simple policy that is defined
within the CLI configuration. It is a concise method for defining event screening criteria and the actions to
be taken when that event occurs. Scripts are defined on the networking device by using an ASCII editor.
The script, which can be a bytecode (.tbc) and text (.tcl) script, is then copied to the networking device
and registered with EEM. You can also register multiple events in a .tcl file.
Cisco enhancements to TCL in the form of keyword extensions facilitate the development of EEM
policies. These keywords identify the detected event, the subsequent action, utility information, counter
values, and system information.
For complete information on configuring EEM policies and scripts, see the Cisco IOS Network Management
Configuration Guide, Release 12.4T.
Embedded Event Manager Environment Variables
EEM uses environment variables in EEM policies. These variables are defined in a EEM policy tool
command language (TCL) script by running a CLI command and the event manager environment
command.
User-defined variables
Defined by the user for a user-defined policy.
• Cisco-defined variables
Defined by Cisco for a specific sample policy.
• Cisco built-in variables (available in EEM applets)
Defined by Cisco and can be read-only or read-write. The read-only variables are set by the system
before an applet starts to execute. The single read-write variable, _exit_status, allows you to set the
exit status for policies triggered from synchronous events.
Cisco-defined environment variables and Cisco system-defined environment variables might apply to
one specific event detector or to all event detectors. Environment variables that are user-defined or
defined by Cisco in a sample policy are set by using the event manager environment global
configuration command. You must defined the variables in the EEM policy before you register the
policy.

Table of Contents

Other manuals for Cisco ME 3400

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Cisco ME 3400 and is the answer not in the manual?

Cisco ME 3400 Specifications

General IconGeneral
CategorySwitch
Rack MountableYes
Jumbo Frame SupportYes
Authentication MethodRADIUS, TACACS+
RAM128 MB
Flash Memory32 MB
Power DeviceInternal power supply
ModelME 3400
LayerLayer 2
MAC Address Table Size8000 entries
Remote Management ProtocolSNMP, Telnet, SSH, HTTP, HTTPS
FeaturesVLAN support, IGMP snooping, Quality of Service (QoS)
Compliant StandardsIEEE 802.3, IEEE 802.3u, IEEE 802.1D, IEEE 802.1Q, IEEE 802.3ab, IEEE 802.3x
Memory128 MB
Power SupplyAC 120/230 V (50/60 Hz)
Dimensions (H x W x D)4.4 cm x 44.5 cm x 24.2 cm
Routing ProtocolStatic routing

Related product manuals