Cisco Nexus 9000 Series Configuration Manual page 186

Defining a User Policy Using the CLI
Command
event fib {adjacency extra | resource tcam usage |
route {extra | inconsistent | missing}}
Example:
switch(config-applet)# event fib adjacency
extra
event gold module {slot | all} test test-name
[severity {major | minor | moderate}] testing-type
{bootup | monitoring | ondemand | scheduled}
consecutive-failure count
Example:
switch(config-applet)# event gold module 2
test ASICRegisterCheck testing-type
ondemand consecutive-failure 2
event interface [tag tag] {name interface slot/port
parameter}
Example:
switch(config-applet)# event interface
ethernet 2/2 parameter
event memory {critical | minor | severe}
Example:
switch(config-applet)# event memory
critical
event module [tag tag] status {online | offline | any}
module {all | module-num}
Example:
switch(config-applet)# event module status
offline module all
Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x
166
Configuring the Embedded Event Manager
Purpose
Triggers an event for one of the following:
• adjacency extra—If there is an extra route in
the unicast FIB.
• resource tcam usage—Each time the TCAM
utilization percentage becomes a multiple of 5,
in either direction.
• route {extra | inconsistent | missing}—If a
route is added, changed, or deleted in the unicast
FIB.
Triggers an event if the named online diagnostic test
experiences the configured failure severity for the
configured number of consecutive failures. The slot
range is from 1 to 10. The test-name is the name of
a configured online diagnostic test. The count range
is from 1 to 1000.
Triggers an event if the counter is exceeded for the
specified interface.
The tag tag keyword-argument pair identifies this
specific event when multiple events are included in
the policy.
To use this command, you must first enable
Note
the feature evmed command to enable
generic event detectors.
Triggers an event if a memory threshold is crossed.
See also Configuring Memory Thresholds, on page
173.
Triggers an event if the specified module enters the
selected status.
The tag tag keyword-argument pair identifies this
specific event when multiple events are included in
the policy.