• Here you will learn what (Embedded Event Manager) is.
    is a Cisco IOS feature that lets you automate tasks directly on a router.

    How EEM Works

    The idea is simple:

    • An event happens (example: an interface goes down, a message appears, a command is entered)

    • reacts by executing one or more actions automatically

    To understand this, look at the diagram below.

    EEM event sources list: Syslog, SNMP trap, Timer, CLI and Interface triggers monitored by Embedded Event Manager

    Figure 1 - Event Sources

    1. Event Sources

    Event Sources are the different “inputs” that can monitor on the device.
    In this figure, you can see common examples:

    • : a log message is generated

    • : a trap is received

    • Timer: a scheduled trigger

    • CLI: a command is entered

    • Interface: a link/state change is detected

    Answer the question below

    Which component generates a log message that EEM can monitor?

    2. EEM Engine

    The Engine is the component that receives these events and checks whether they match a condition you configured.
    In other words: events arrive at the top, and the engine decides whether something should happen next.

    EEM event sources such as Syslog, SNMP and Timer feeding into the EEM Engine on the router

    Figure 2 - Engine

    Answer the question below

    Which component decides whether an event should trigger an action?

    3. EEM Applets

    Now let’s extend the workflow: when an event matches, can launch an applet.

    EEM workflow: event sources feed the EEM Engine, which launches an EEM applet with event and actions

    Figure 3 - Applet

    An applet is a small IOS script that describes what to react to and what to do when it happens.

    It contains:

    • an event: the trigger condition

    • actions: the list of tasks the device will execute

    EEM applet details: one event trigger followed by actions to log, no shut the interface, notify administrator

    Figure 4 - Applet details

    If we summarize the full chain:

    • Event Sources: an event happens (example: “interface down”)

    • Engine: detects it and checks for a match

    • Applet: if there is a match, runs the applet actions (the “script” executed automatically)

    Answer the question below

    What IOS feature contains the trigger and the list of actions to execute automatically?