Cisco Cisco IOS Software Release 12.4(4)T Données agrégées
Product Bulletin
© 2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 28 of 299
Each type of event has specific options, parameters and detailed information that is available to the
policy when it is invoked. All of these details are described in the Cisco IOS documentation.
policy when it is invoked. All of these details are described in the Cisco IOS documentation.
Feature Specifications
Please use the Cisco IOS Feature Navigator application on Cisco.com to check the latest
information on software and product availability. Go to: http://cisco.com/go/fn. The following table
includes EEM feature availability information.
information on software and product availability. Go to: http://cisco.com/go/fn. The following table
includes EEM feature availability information.
Table 5.
EEM Feature Specifications
Product
compatibility
compatibility
EEM is available for the Catalyst 6500 Series Switches, Cisco Integrated Services Routers, Cisco
7200 Series Routers, Cisco 7300 Series Routers, Cisco 7600 Series Routers, Cisco 10000 Series
Routers; EEM is also available for the Catalyst 4500 Series Switches and the Catalyst 3700 Series
Switches and the ASR-1000 Series Routers. Please refer to the Cisco IOS Feature Navigator for the
latest device support information.
7200 Series Routers, Cisco 7300 Series Routers, Cisco 7600 Series Routers, Cisco 10000 Series
Routers; EEM is also available for the Catalyst 4500 Series Switches and the Catalyst 3700 Series
Switches and the ASR-1000 Series Routers. Please refer to the Cisco IOS Feature Navigator for the
latest device support information.
Software
compatibility
compatibility
EEM is available in Cisco IOS Software Releases 12.2SX, 12.2SR, 12.2SB, 12.4, and 12.4T, 12.2SG,
12.2SE, Cisco IOS XE and future versions. EEM function is also included in Cisco IOS XR and Cisco
NX OS.
12.2SE, Cisco IOS XE and future versions. EEM function is also included in Cisco IOS XR and Cisco
NX OS.
Software
Packaging
Packaging
Some Cisco products require an enhanced feature set license to acquire support for EEM. Please
refer to the Cisco IOS Feature Navigator for the latest packaging information.
refer to the Cisco IOS Feature Navigator for the latest packaging information.
System Requirements
The EEM software subsystem will consume CPU and memory resources in its operation. Tcl-based
policies reside on flash disk and will take up space. Customers should examine the operation in
their environment to ensure resources exist for their specific scenarios. Some basic guidelines are
included in Table 5.
policies reside on flash disk and will take up space. Customers should examine the operation in
their environment to ensure resources exist for their specific scenarios. Some basic guidelines are
included in Table 5.
Table 6.
EEM System Requirements
Disk Space
Tcl-based policies are files stored on flash disk. The amount space required depends on the size and
number of policies and any programmed storage requirements
number of policies and any programmed storage requirements
Hardware
CPU utilization requirements are solution dependent
Memory
Each Tcl-based policy will use approximately 500KB when initialized. Beyond that utilization is specific
to the policy’s operational requirements
to the policy’s operational requirements
Software
A Tcl interpreter is included within the Cisco IOS Software. The current version is Tcl 8.3.4.
For More Information
For more information about the Cisco IOS Embedded Event Manager, visit
or contact your local account representative or send email to
.
Product Management Contact:
Rick Williams,
3.2.2) Flexible NetFlow—NetFlow v5 Export Format
Flexible NetFlow exporter introduces the support of NetFlow v5 export format. NetFlow v5 export
format must be used in conjunction with the v5 tupple in Flexible NetFlow (FNF) for one pre-defined
flow record named original-NetFlow.
Flexible NetFlow exporter introduces the support of NetFlow v5 export format. NetFlow v5 export
format must be used in conjunction with the v5 tupple in Flexible NetFlow (FNF) for one pre-defined
flow record named original-NetFlow.
When transitioning from traditional NetFlow to Flexible NetFlow, the user will be able to create a
Flow Monitor with the original-NetFlow record and export it using NetFlow v5 to the existing
NetFlow v5 collector. In addition, the user will be able to create a second Flow Monitor to take
advantage of other innovative FNF capabilities, such as Flow record customization and NetFlow v9
export.
Flow Monitor with the original-NetFlow record and export it using NetFlow v5 to the existing
NetFlow v5 collector. In addition, the user will be able to create a second Flow Monitor to take
advantage of other innovative FNF capabilities, such as Flow record customization and NetFlow v9
export.