1.Access Policy Manager as described in the topic, ”Accessing Policy Manager” on page 532.
2.In the Policy Manager tree in the middle pane, expand the node, Infrastructure Policies. Then, click Events.
3.Click the Add button.
4.In the Name field, type a name for the policy.
5.In the Description field, type a description for the policy.
6.In the
The rearm period is the amount of time after the policy executes before it can execute again. It is useful for limiting the number of times the same actions will execute.
IMPORTANT: Specify shorter periods for important applications.
7.Select one or more element types.
When a condition is fulfilled on a select element, Policy Manager generates an event, sends an
8.Select Fire when event is cleared if you want the policy to fire when the event is cleared, Otherwise the event fires when the event is received.
9.In the Severity
10.To the right of the Severity
IMPORTANT: Since the severity level for an element is set by the manufacture, the meanings of the severity levels vary. It is best to view the description of the event.
•Unknown - The severity level is not known.
•Informational - An example of an informational event is a progress report event for firmware download operation currently in progress.
•Warning - An example of a warning is one or more new physical fabric objects (device port, switch, or fabric) have appeared.
•Minor - An example of a minor event is a physical fabric object (switch port or fabric) has changed state.
•Major - An example of a major event is one or more physical fabric objects (device port, switch, or fabric) have disappeared.
•Critical - An example of a critical event is Brocade switches that have a failed firmware download and the failure reason code for each respective switch.
11.Select one of the following from the Summary Text
•Is anything - Regardless of the contents of the event's summary text, Policy Manager sends an
•Contains - If the event's summary text contains the specified text, Policy Manager sends an
540 Managing Policies