The event cli pattern "show ip interface brief" sync yes command will cause Embedded Event Manager (EEM) to check the value of the _exit_status variable after anapplet is finished. The event cli command configures EEM to monitor commandline interface (CLI) commands and to trigger the event when a specified pattern is matched one or more times. Events can be processed synchronously or asynchronously. The sync yeskeywords are used with the event cli command to configure synchronous processing. With synchronous processing, the EEM applet must finish before the CLI command can be executed, and the _exit_status variable determines whether the CLI command is executed or skipped. If the _exit_status variable is set to a value of 0 or is not configured, the CLI command will not execute after the EEM applet is finished? if the _exit_status variable is set to a value of 1, the CLI command will execute after the EEM applet is finished.

The set 1 _exit_status 0 command sets the _exit_status variable to a value of 0, which will cause EEM to not execute the CLI command after the applet is finished.

The set 1 _exit_status 1 command sets the _exit_status variable to a value of 1, which will cause EE to execute the CLI command after the applet is finished.

The sync no keywords are used with the event cli command to configure asynchronous processing. With asynchronous processing, the EEM applet is processed at the same time the CLI command is executed. Asynchronous processing does not check the value of the _exit_status variable. Instead, asynchronous processing uses the skip no or skip yeskeywords to indicate whether the CLI command should be executed or skipped, respectively.

The event cli pattern "show ip interface brief" sync no skip no command will cause EE to execute the CLI command when the applet runs. The event cli pattern "show ipinterface brief" sync no skip yes command will not execute the CLI command when the applet runs.