Creating A Supplemental Policy For The Temperature Threshold Event; Configuration Examples For The Power Over-Budget Policy; Shutting Down Modules; Shutting Down A Specified List Of Modules - Cisco Nexus 9000 Series Configuration Manual

Embedded Event Manager System Events and Configuration Examples
[no] event fanabsent [fan fan-tray-number] time time-interval
In addition to the default policy, this example shows how to execute the policy myappletname and action 3
if fan tray 1 is absent for 60 seconds:
switch# configure terminal
switch(config)# event manager applet myappletname
switch(config-applet)# event fanabsent fan 1 time 60
switch(config-applet)# action 3 cli "show env fan"
switch(config-applet)# end

Creating a Supplemental Policy for the Temperature Threshold Event

This example shows how to create a supplemental policy using the event temperature command:
[no] event temperature [mod module-number] [sensor sensor-number] threshold {major | minor | any}
In addition to the default policy, this example shows how to execute the policy myappletname and action 1
if the temperature crosses the minor threshold on sensor 3 of module 2:
switch# configure terminal
switch(config)# event manager applet myappletname
switch(config-applet)# event temperature module 2 sensor 3 threshold minor
switch(config-applet)# action 1 cli "show environ temperature"
switch(config-applet)# end

Configuration Examples for the Power Over-Budget Policy

The power over-budget policy gets triggered when the available power capacity drops below zero and the
device is no longer able to keep the previously powered-up modules in the powered-up state. The default
action is to print a syslog to notify the user of the occurrence of power over budget.
You can enable an additional action to power down modules until the available power recovers from the red
(negative) zone.

Shutting Down Modules

If you do not specify any modules, the power over-budget shutdown starts from slot 1 and shuts down modules
until the power recovers from the red (negative) zone. Empty slots and slots that contain a supervisor, standby
supervisor, spine, or crossbar are skipped.
This example shows how to shut down modules starting from module 1 when the available power drops below
zero:
switch# configure terminal
switch(config)# event manager applet <myappletname4a> override __pfm_power_over_budget
switch(config-applet)# event poweroverbudget
switch(config-applet)# action 4 overbudgetshut
switch(config-applet)# end

Shutting Down a Specified List of Modules

You can specify a list of modules that the power over-budget action uses to shut down modules until the power
recovers from the red (negative) zone. Empty slots and slots that contain a supervisor, standby supervisor,
spine, or crossbar are skipped.
Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x
Configuration Examples for the Power Over-Budget Policy
247