Cisco Nexus 7000 Series Configuration Manual page 277

Configuring the Embedded Event Manager
Command
event fanbad [fan number] time seconds
Example:
switch(config-applet)# event fanbad time
3000
event fib {adjacency extra | resource tcam usage | route
{extra | inconsistent | missing}}
Example:
switch(config-applet)# event fib adjacency
extra
event gold [failure-type {sup | fabric | lc | port}] module
{module | all} test {test-name | test-id} [severity {major | minor
| moderate}] testing-type {bootup | monitoring | ondemand
| scheduled} consecutive-failure count
Example:
switch(config-applet)# event gold failure-type module
2
test 7 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
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
Defining a User Policy Using the CLI
Purpose
Triggers an event if a fan fails for more
than the configured time, in seconds. The
number range is module dependent. The
seconds range is from 10 to 64000.
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 module specifies the number of the
module that needs to be monitored.
The test-name is the name of a configured
online diagnostic test. The test-id specifies
the test ID of the event criteria. The range
is from 1 to 30.
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.
Note To use this command, you must
first enable 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 264.
249