The Measurement, Aggregation, and Correlation Engine (MACE) Exporter receives the Flexible NetFlow (FNF) templates from the
MACE configuration plane and builds FNF records based on these templates. It then passes the flow templates along with each
record to the NetFlow infrastructure. FNF requires these templates to understand the layout of the records so that it can
export the correct fields at the time of export.
The MACE Exporter allows you to configure the export time interval. The intervals 1, 2, 5, 10, and 15, in minutes, are supported.
The export timer starts when the MACE is enabled. There are two ways to enable MACE: by using the MACE policy or by using
the MACE along with the WAAS policy. To synchronize the export time of multiple devices that run the MACE across the network
with the collector, the export timer expires when the current time modulo configured interval is zero. For instance, if a
user configures a 5 minute interval at 10:07, the first export timer will expire at 10:10 (because 10:10 modulo 5 is 0) and
subsequently at a gap of every 5 minutes (10:15, 10:20, and so on).
Note |
Modulo is the resulting remainder when one number is divided by another. For example, the modulo of 5 and 4 is 1 because 5
divided by 4 leaves a remainder of 1.
|
This export mechanism ensures that the time when the first export interval expires is independent from the time when the
MACE policy was applied to the target. Any future update to the timeout interval causes the current timer to stop, and a new
timer starts. The timer also stops when the policy is removed from the interface.
Note |
The MACE Exporter works on a best-effort basis. Also, MACE being a monitoring tool, the export process does execute with a
high priority.
|
When the MACE Exporter timer expires, all engines are notified to process the metrics. After this notification, a second
set of calls are sent to collect the processed metrics. The MACE Exporter receives the metrics data from various sources,
aggregates them into a single FNF record, and passes it to the NetFlow component. Aggregation is done on the basis of Layer
7 keys. Application ID (Network-Based Application Recognition [NBAR]) is provided as a metric only when requested through
the configuration.