Event and Accounting Logs
7450 ESS System Mangement Guide Page 395
Figure 11: EHS Object Relationships
Complex rules can be configured to match on log events as a trigger for an EHS handler.
When a log event is generated in SR OS it will be subject to discard via suppression and throttling
(config>log>event-control) before it is evaluated as a trigger for EHS:
• EHS will not trigger on log events that are suppressed through config>log>event-control
• EHS will not trigger on log events that are throttled by the logger
EHS will trigger on log events that are dropped by user configured log filters that are assigned to
individual logs (config>log>filter). The EHS event trigger logic occurs before the distribution of
log event streams into individual logs.
config>log>event-trigger
event oam 1234
trigger-entry 10
event-handler my-handler-1
log-filter 2001
trigger-entry 20
log-filter 2002
event-handler my-handler-2
event bgp 4567
...
config>log
filter 2001
entry 10
action forward
match
subject eq "interface_1" regexp
message eq "crossing“
entry 20
action forward
match
subject eq "interface_2" regexp
message eq "Session my-session-xyz“
filter 2002
entry 10
action forward
match
subject eq "interface_3" regexp
message eq "clearing"
config>system>script-control
script-policy my-spolicy-1
max-completed 5
script my-script-1
...
script-control
config>system>script-control
script my-script-1
location "cf1:\scripts\script1.txt"
...
config>system>script-control
script-policy my-spolicy-2
max-completed 5
script my-script-2
...
script-control
config>system>script-control
script my-script-2
location "cf1:\scripts\script2.txt"
...
config>log>event-handling
handler my-handler-1
action-list
entry 10
script-policy my-spolicy-1
entry 20
...
config>system>cron
schedule my-sched-1
interval 300
script-policy my-spolicy-2
The CLI in this figure is representational
and is not intended to be completely
correct syntax or values.
24884
To Next Page
Loading...
