EasyManuals Logo

Cisco Catalyst 2960 Series User Manual

Cisco Catalyst 2960 Series
2288 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 #1852 background imageLoading...
Page #1852 background image
Only the first environment variable supports multiple parameter substitution. Individual parameters can
still be specified with additional environment variables after the initial variable.
Note
To illustrate the substitution, a single environment variable, $_eem_syslog_statement is configured as:
::cisco::eem::event_register_syslog pattern COUNT
Using the registration substitution, the $_eem_syslog_statement environment variable is used in the following
EEM user policy:
$_eem_syslog_statement occurs $_eem_occurs_val
action_syslog this is test 3
Environment variables must be defined before a policy using them is registered. To define the
$_eem_syslog_statement environment variable:
Device(config)# event manager environment eem_syslog_statement
::cisco::eem::event_register_syslog pattern COUNT
Device(config)# event manager environment eem_occurs_val 2
Cisco File Naming Convention for EEM
All Embedded Event Manager policy names, policy support files (for example, e-mail template files), and
library filenames are consistent with the Cisco file naming convention. In this regard, Embedded Event
Manager policy filenames adhere to the following specification:
An optional prefix--Mandatory.--indicating, if present, that this is a system policy that should be registered
automatically at boot time if it is not already registered. For example: Mandatory.sl_text.tcl.
A filename body part containing a two-character abbreviation (see the table below) for the first event
specified; an underscore part; and a descriptive field part that further identifies the policy.
A filename suffix part defined as .tcl.
Embedded Event Manager e-mail template files consist of a filename prefix of email_template, followed by
an abbreviation that identifies the usage of the e-mail template.
Embedded Event Manager library filenames consist of a filename body part containing the descriptive field
that identifies the usage of the library, followed by _lib, and a filename suffix part defined as .tcl.
Table 167: Two-Character Abbreviation Specification
event_register_applap
event_register_clicl
event_register_counterct
event_register_goldgo
event_register_interfaceif
event_register_ioswdsysmonio
Consolidated Platform Configuration Guide, Cisco IOS Release 15.2(4)E (Catalyst 2960-X Switches)
1770
Information About Writing Embedded Event Manager Policies Using Tcl

Table of Contents

Other manuals for Cisco Catalyst 2960 Series

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Cisco Catalyst 2960 Series and is the answer not in the manual?

Cisco Catalyst 2960 Series Specifications

General IconGeneral
LayerLayer 2
Power over Ethernet (PoE)Available on some models
RAM128 MB
Flash Memory32 MB
MAC Address Table Size8000
Operating Temperature0°C to 45°C (32 to 113°F)
Ports24 or 48 x 10/100/1000

Related product manuals