- erspan-id
- ethanalyzer local interface
- ethanalyzer local read
- event cli
- event counter
- event fanabsent
- event fanbad
- event gold
- event manager applet
- event manager clear counter
- event manager clear history events
- event manager environment
- event manager policy
- event manager run
- event manager scheduler
- event manager scheduler clear
- event manager scheduler hold
- event manager scheduler modify
- event manager scheduler release
- event module-failure
- event module status
- event oir
- event policy-default
- event snmp
- event storm-control
- event syslog
- event temperature
- event track
- exporter
E Commands
This chapter describes the Cisco NX-OS system management commands that begin with the letter E.
erspan-id
To configure the flow ID for an Encapsulated Remote Switched Port Analyzer (ERSPAN)) session, use the erspan-id command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure the flow ID for an ERSPAN session:
Related Commands
ethanalyzer local interface
To capture packets to or from the supervisor or management interface, use the ethanalyzer local interface command. To stop packet capture, use the no form of this command.
ethanalyzer local interface { inband | mgmt } [[ capture-filter capt-expression ] [capture-ring-buffer duration seconds write bootflash | files files write bootflash |
filesize kilobytes write bootflash [ display-filter disp-expression ] [ limit-captured-frames limit ] [ limit-frame-size bytes ] [ write location ]] [ brief ]
no ethanalyzer local interface { inband | mgmt } [[ capture-filter capt-expression ] [capture-ring-buffer duration seconds write bootflash | files files write bootflash | filesize kilobytes write bootflash [ display-filter disp-expression ] [ limit-captured-frames limit ] [ limit-frame-size bytes ] [ write location ]] [ brief ]
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
---|---|
Added the option capture-ring-buffer to the syntax description. |
|
Usage Guidelines
Cisco Ethanalyzer is based on the Wireshark open source code.
Examples
This example shows how to capture all packets on the mgmt 0 port:
Related Commands
|
|
---|---|
ethanalyzer local read
To read packets captured by Ethanalyzer, use the ethanalyzer local read command. To stop reading the packet capture, use the no form of this command.
ethanalyzer local read location
no ethanalyzer local read location
Syntax Description
Location to read captured packets from. The location can be any case-sensitive, alphanumeric string up to 64 characters. |
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
---|---|
Usage Guidelines
Cisco Ethanalyzer is based on the Wireshark open source code.
Examples
This example shows how to capture all packets on the mgmt 0 port:
Related Commands
|
|
---|---|
event cli
To specify the event criteria for an Embedded event manager (EEM) applet that is run by matching a Cisco NX-OS command-line interface (CLI) command, use the event cli command. To remove the CLI command event criteria, use the no form of this command.
event cli [ tag tag] match regex [ count countnum ] [ time interval ]
no event cli match regex [ count countnum ] [ time interval ]
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
The event cli match regex command must meet the following criteria:
1. It must be a fully qualified CLI string that must include the complete, not relative, path. For example, to describe the shutdown command under interface mode, the command should be:
2. The delimiter between the modes must be “ ; ”, which is a space followed by a semi-colon and followed by another space.
Examples
This example shows how to specify a CLI command for the EEM applet to match:
event counter
To specify the event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a named counter crossing a threshold, use the event counter command. To remove the counter event criteria, use the no form of this command.
event counter [ tag tag] name name entry-val value entry-op { gt | ge | eq | ne | lt | le } [ exit-val value exit-op { gt | ge | eq | ne | lt | le }]
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify an event criteria for an EEM applet that is run when the defined critical_errors counter exceeds the entry value:
event fanabsent
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a fan absent event, use the event fanabsent command. To remove the fan absent event criteria, use the no form of this command.
event fanabsent [ fan number ] time interval
no event fanabsent [ fan number ] time interval
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when a fan absent event occurs:
event fanbad
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a fan bad event, use the event fanbad command. To remove the fan bad event criteria, use the no form of this command.
event fanbad [ fan number ] time interval
no event fanbad [ fan number ] time interval
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when a fan bad event occurs:
event gold
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a Generic Online Diagnostic (GOLD) failure event when monitoring one or more modules, use the event gold command. To remove the GOLD failure event criteria, use the no form of this command.
event gold [failure-type {sup | fabric | lc | port}] module { module | all } test { name | test-id } [ severity { minor | moderate | major }] testing-type { bootup | ondemand | scheduled | monitoring } consecutive-failure cnt
no event gold [failure-type {sup | fabric | lc | port}] module {module | all} test { name | test-id }
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when a new GOLD failure event occurs for any module:
event manager applet
To register an applet with the Embedded Event Manager (EEM) and to enter applet configuration mode, use the event manager applet command. To remove the applet command from the configuration, use the no form of this command.
event manager applet applet-name [override policy-name ] [ class class-options ]
no event manager applet applet-name
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to register an applet with EEM and to enter applet configuration mode:
event manager clear counter
To specify an Embedded Event Manager (EEM) counter to clear, use the event manager clear counter command.
event manager clear counter counter-name
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to clear an EEM counter:
event manager clear history events
To clear all Embedded Event Manager (EEM) event history, use the event manager clear history events command.
event manager clear history events
Syntax Description
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to clear all of the EEM event history:
event manager environment
To set an Embedded Event Manager (EEM) environment variable, use the event manager environment command. To disable an EEM environment variable, use the no form of this command.
event manager environment varname varvalue
no event manager environment varname
Syntax Description
String of characters, including embedded spaces, to be placed in the environment variable varname. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to set an EEM environment variable:
event manager policy
To register an Embedded Event Manager (EEM) policy with the EEM, use the event manager policy command. To remove the event manager policy command from the configuration file, use the no form of this command.
event manager policy VSHscriptfilename
no event manager policy VSHscriptfilename
Syntax Description
Name of the VSH script file to register with the EEM. This name becomes the name of the EEM policy. Note System policy names begin with two underscore characters (__). |
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
This command does not require a license.
The EEM schedules and runs policies on the basis of an event specification that is contained within the policy itself. When the event manager policy command is invoked, the EEM examines the policy and registers it to be run when the specified event occurs.
Examples
This example shows how to register a policy:
event manager run
To manually run a registered Embedded Event Manager (EEM) policy, use the event manager run command.
Syntax Description
Name of the registered EEM policy to run. Note System policy names begin with two underscore characters (__). |
Defaults
Command Modes
Applet configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to manually run a registered EEM policy:
event manager scheduler
To schedule Embedded Event Manager (EEM) policies and set the policy scheduling options, use the event manager scheduler command in global configuration mode. To remove the scheduling of EEM policies, use the no form of this command.
event manager scheduler applet thread class class-options number thread-number
no event manager scheduler applet thread class class-options number thread-number
Syntax Description
Defaults
Command Modes
Global Configuration (config#).
Command History
|
|
Usage Guidelines
During registration, EEM policies will be assigned a class if class class-letter is specified by the event manager applet or event manager policy commands. EEM policies registered without a class will be assigned the default class. Threads that have default as the class will service the default class when the thread is available for work. Threads that are assigned specific class letters will service any policy with a matching class letter.
If there is no EEM execution thread available to run the policy in the specified class and a scheduler rule for the class is configured, the policy will wait until a thread of that class is available for execution. Synchronous policies that are triggered from the same input event should be scheduled in the same execution thread.
For class, specify any of these options- class-letter, default, or range class-letter-range. You can specify all these options in the same CLI statement.
To schedule EEM policies and set the script scheduling options, use the event manager scheduler script command in global configuration mode. To remove the EEM script scheduling options and restore the default value, use the no form of this command.
Examples
The following example shows how to create two EEM scheduling threads to run applets of the default class:
The following example shows how to create one EEM execution thread to run Tcl scripts of class A, B, D and E.
Related Commands
|
|
---|---|
Registers an EEM applet with the EEM and enters applet configuration mode. |
|
event manager scheduler clear
To clear Embedded Event Manager (EEM) policies that are executing or pending execution, use the event manager scheduler clear command in privileged EXEC mode.
event manager scheduler clear { all | policy job-id | queue-type applet [ class class-options ]} [ processor { rp_primary | rp_standby }]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
For class, specify atleast one of the options: class-letter, default, or range class-letter-range. You can specify all these options in the same CLI statement.
Examples
The following example shows how to clear EEM policies that are pending execution. The show commands display sample output before and after the policy is cleared.
Related Commands
|
|
---|---|
event manager scheduler hold
To hold a scheduled Embedded Event Manager (EEM) policy event or event queue in the EEM scheduler, use the event manager scheduler hold command in the privileged EXEC mode. To resume the policy event or event queue, use the event manager scheduler release command.
event manager scheduler hold { all | policy job-id | queue-type applet [ class class-options ]}
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the show event manager policy pending command to display the policies pending in the server execution queue.
Use the event manager scheduler hold command to hold a policy or a policy queue in the server.
For class, specify any of the options- class-letter, default, and range class-letter-range. You can specify all these options in the same CLI statement.
Examples
The following example shows how to hold a scheduled policy event in the EEM scheduler. The show commands display sample output before and after the policy event is held.
Related Commands
|
|
---|---|
event manager scheduler modify
To modify the scheduling parameters of the Embedded Event Manager (EEM) policies, use the event manager scheduler modify command in the privileged EXEC mode.
event manager scheduler modify { all | policy job-id | queue-type applet } { class class-options [ queue-priority { high | last | low |normal }] | queue-priority { high | last | low | normal } [ class class-options ] }
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the show event manager policy pending command to display the policies pending in the server execution queue.
Use the event manager scheduler modify command to modify the scheduling parameters of a policy.
For class, specify any of the options- class-letter or default. You can specify all these options in the same CLI statement..
Examples
The following example shows how to modify the scheduling parameters of EEM policies. The show commands display sample output before and after the scheduling parameters are modified.
Related Commands3 A pend Thu Sep 7 02:54:04 2006 syslog applet: three 3 A pend Thu Sep 7 02:54:04 2006 syslog applet: three
|
|
---|---|
event manager scheduler release
To resume execution of the specified Embedded Event Manager (EEM) policies, use the event manager scheduler release command in the privileged EXEC mode.
event manager scheduler release { all | policy job-id | queue-type applet [ class class-options ]}
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
To release the EEM policies held using the event manager scheduler hold command, use the event manager scheduler release command.
For class, specify any of the options: class-letter, default or range class-letter-range. You can specify all these options in the same CLI statement.
Examples
The following example shows how to resume the execution of all EEM policies.
The following example shows how to resume the execution for policies of class A to E.
Related Commands
|
|
---|---|
event module-failure
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a module failure event, use the event module-failure command. To remove the module failure event criteria, use the no form of this command.
event module-failure type err-name module { all | module } count count [ time interval ]
no event module-failure type err-name module { all | module } count count
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when a module failure event occurs:
event module status
To configure a status event on a module, use the event module status command. To remove the status event configuration, use the no form of this command.
event module status { online | offline | any } module { all | module-number}
no event module status { online | offline | any } module { all | module-number}
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure a status event on a module:
This example shows how to remove the status event configuration:
Related Commands
|
|
---|---|
Registers an Embedded Event Manager (EEM) policy with the EEM. |
event oir
To specify that an Embedded Event Manager (EEM) applet be run on the basis of an event raised when a hardware online insertion and removal (OIR) occurs, use the event oir command. This command has three forms; fan, module, and powersupply. To remove the OIR specification from the configuration, use the no form of this command.
event oir [tag tag ] { fan | module | powersupply } { insert | remove | anyoir } [ number ]
no event oir [tag tag ] { fan | module | powersupply } { insert | remove | anyoir } [ number ]
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet be run on the basis of an event raised when a module OIR occurs:
event policy-default
To use the event if a system policy is being overridden, use the event policy-default command. To use the overridden policy, use the no form of this command.
event policy-default count count [ time interval ]
no event policy-default count count
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to use the event in the system policy being overridden:
event snmp
To specify the event criteria for an Embedded Event Manager (EEM) applet that is run by sampling Simple Network Management Protocol (SNMP) object identifier values, use the event snmp command. To remove the SNMP event criteria, use the no form of this command.
event snmp [tag tag] oid value get-type {exact | next} entry-op {gt | ge | eq | ne | lt | le} entry-val value [{ exit-comb {or | and} exit-op {gt | ge | eq | ne | lt | le} exit-val value exit-time time } | {exit-op {gt | ge | eq | ne | lt | le} exit-val value }] poll-interval value
no event snmp [tag tag] oid value get-type {exact | next} entry-op {gt | ge | eq | ne | lt | le} entry-val value [{ exit-comb {or | and} exit-op {gt | ge | eq | ne | lt | le} exit-val value exit-time time } | {e xit-op {gt | ge | eq | ne | lt | le} exit-val value }] poll-interval value
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify the event criteria for an EEM applet that is run by sampling SNMP object identifier values:
event storm-control
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a storm control event, use the event storm-control command. To remove the storm control event criteria, use the no form of this command.
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when a storm control event occurs:
event syslog
To configure Cisco NX-OS Embedded Event Manager (EEM) to monitor an event, use the event syslog command. To remove the syslog configuration, use the no form of this command.
event syslog [ tag tag] [ occurs | pattern msg-text | period | priority [ 0-7 | emergencies | alerts | critical | errors | warnings | notifications | informational | debugging ]]
no event syslog [tag tag] [ occurs | pattern msg-text | period | priority [ 0-7 | emergencies | alerts | critical | errors | warnings | notifications | informational | debugging ]]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure a syslog message to monitor when an EEM applet is triggered:
This example shows how to remove the syslog message monitor configuration:
Related Commands
|
|
---|---|
Configures a syslog message to generate when an Embedded Event Manager (EEM) applet is triggered. |
event temperature
To specify an event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of a temperature event, use the event temperature command. To remove the temperature event criteria, use the no form of this command.
event temperature [ module module ] [ sensor number ] threshold {major | minor | any}
no event temperature threshold {major | minor | any}
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when a temperature event occurs:
event track
To specify the event criteria for an Embedded Event Manager (EEM) applet that is run on the basis of an object tracking subsystem report for the specified object number, use the event track command. To remove the report event criteria, use the no form of this command.
event track [tag tag] object-id state {any | up | down}
no event track [tag tag] object-id
Syntax Description
Defaults
Command Modes
Applet Configuration (config-applet)
Command History
|
|
Usage Guidelines
Examples
This example shows how to specify that an EEM applet runs when the state of a tracked object changes:
exporter
To specify a NetFlow exporter to use for a NetFlow monitor, use the exporter command. To remove a NetFlow exporter, use the no form of this command.
Syntax Description
Defaults
Command Modes
NetFlow monitor configuration (config-flow-monitor)
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure a NetFlow exporter for a NetFlow monitor:
This example shows how to remove a NetFlow exporter:
Related Commands
|
|
---|---|