IBM XIV User Manual

Name Type Description Mandatory Default
except_
codes
N/A Filter only events
with other codes.
N All events.
escalation
_only
Boolean Specifies that this
rule can only be
used for escalation.
Nno
dests Object name Comma separated
list of destinations
and destination
groups for event
notification.
Y N/A
snooze_
time
Integer Snooze time in
minutes.
N No snoozing.
escalation
_rule
Object name Escalation rule. N N/A
escalation
_time
Integer Escalation time in
minutes. Escalation
time should not be
defined as shorter
than snooze time.
Refer to
escalation_rule
above for more
information.
N No escalation.
This command defines a new event notification rule. An event notification rule is
used in order to determine which events should create which notifications. When
an event is created, it is checked by all currently defined rules, and based on these
rules the notifications are created.
Each rule has filtering and notifications configuration.
The filtering configuration controls which events match this rule. The filtering can
be based on the event's code, by specifying a minimum severity. When using this
configuration, each event with a severity higher or equal to the rule's min_severity
parameter match this rule. Alternatively, the rule may match only a specific event
code. The two filters can be combined together, when required for events whose
severity depends on a run-time parameter.
The second part of the configuration of a rule is a list of destinations and
destination groups that receive the notification when an event matches the filtering
criteria. If a destination is included both in the rule and in one of the rule's
destination groups, it still gets only one notification. The same applies if a
destination is included in two destination groups, or if the event matches the
filtering criteria of several rules, all using the same destination.
A rule can be defined as alerting, which means that notifications are being sent
repeatedly until the matching events are cleared using the Clearing Alerting Events
command.
Note:
Clearing the event does not mean that the problem has been solved. It only means
that it was noticed and there is no need to continue to send notifications.
Chapter 14. Event Handling 287

IBM XIV Specifications

General

Power Supply	Redundant power supplies
Drive Type	SATA
Redundancy	Fully redundant components
Connectivity	Fibre Channel, iSCSI
Form Factor	Rack-mounted
Cache	Distributed cache across modules
Data Protection	Snapshots, remote mirroring
Performance	High throughput and low latency
Scalability	Modular, scale-out architecture
Cooling	Redundant cooling
Architecture	Grid-based, distributed architecture