Service Manual

Version Description
9.8(0.0P5) Introduced on the S4048–ON.
9.8(0.0P2) Introduced on the S3048–ON.
9.7(0.0) Introduced on the S4810, S4820T, S5000, S6000, S6000–
ON, Z9000, Z9500, and MXL.
9.6(0.0) Introduced on the S5000.
9.5(0.1) Introduced on the Z9500.
9.3(0.0) Introduced on the S6000.
9.2(0.0) Introduced on the S4810, S4820T, Z9000, and MXL Switch.
Usage Information
The maximum number of events you can configure is 20. The maximum number
of allowed tag patterns in a log event trigger is three. The tags of the log events
must be an exact comparison. The three tags work in a logical OR operation format
(match with any one of the tags occurs).
NOTE: Before deleting a trigger event, you MUST unlink the script from the
event.
If you use the caret symbol (^) as a pattern, the Dell Networking OS generates
blank space as the starting character of the SYSLOG. The special character $ is not
allowed to use in regular expressions, as the last word in the SYSLOG is line feed.
NOTE: The time-events schedule time takes effect once after the device
configures the trigger-event (event). A single trigger event can contain
combinations of interval, weekday, month, and month day.
Related Command script event-handler — Allows you to provide mapping between the scripts and
trigger events.
Examples
Following example shows how the event triggers a script, even if any one of the
pattern matches.
Dell(conf)# script trigger-event Server_Reporter_Event log-
event tag tag-or-ex "Major alarm" "Minor alarm"
Following example shows how the event triggers a script, if the system throws the
SYSLOG message like: Oct 29 05:28:16: %RPM0-P:CP %IFMGR-5-
OSTATE_UP: Changed interface state to up: Ma 0/0.
Dell(conf)# script trigger-event Port_State_Event log-event
tag tag-regex "OSTATE.*up"
Following example shows the script triggering at 22:22 and then triggers every
Monday midnight and stops at 02:02–11/10/14.
Dell(conf)# script trigger-event Event2 time-event start at
22:22 stop at 02:02-11/10/14 weekday mon
Smart Scripting CLI
109