Brocade Communications Systems Network Advisor 12.3.0, User Manual

Page: 1341 / 1940

Brocade Network Advisor SAN User Manual 1289
53-1003154-01
Event action definitions
32
NOTE
Auto Acknowledge is enabled only when Take actions for the selected events when they occur
is selected in the Policy step of the Event Actions Wizard. If you edit an Event Action that has
Auto Acknowledge selected and change this option in the Policy step to Time-bound or
Frequency-bound, you will be required to confirm your choice.
3. Select the Alert by E-mail check box if you want an e-mail message to be sent to an
administrator if the policy criteria have been met.
4. Select the Run Policy Monitor check box to execute a policy monitor as an action based on a
selected event, and then select the target for the policy monitor from the list. Target options
include Event Sender and Specified in Config.
5. Select the Launch a Script check box if you want to execute to an external script file when the
matching criteria have been met, and then enter the script in the accompanying field.
6. Select the Broadcast to Client check box, and click Configure to broadcast a message to all the
clients when the matching criteria have been met.
NOTE
The remaining parameters are not available if a non-Fabric OS product is selected as an event
sender.
The Broadcast Message dialog box displays.
a. Select a severity level from the list.
b. Type a message in the Message Content field.
c. Click OK.
7. The Mark as Special Events check box is unselected by default. Leave it this way if you want
the event action to be added to the Special Event Handling event action category. Refer to
“Special events handling” for more complete information.
8. Click the Collect support save check box to enable SupportSave on the event. The check box is
unselected by default.
9. Click Next to display the Action Group - E-mail Settings pane of the Add Event Action dialog box
if you selected Alert by E-mail. If you did not select Alert by E-mail, you will advance to the
Summary pane.
Special events handling
The following special error conditions are examples of events that are categorized as Special
Events Handling events, a separate category that appears in the Name list of the Event Actions
dialog box. All pre-selected events are SNMP traps.
•
Invalid T1 zone configuration event
•
48-blade inserted into a non-Virtual Fabric chassis
•
Port fencing Fabric Watch trap, when a port is fenced
•
Blade Processor FPGA version is incompatible with the Fabric OS firmware version
Though these error conditions are automatically considered “special events handling” events, you
can add or edit any event action and mark the action as a special event for special events handling
using the Actions pane of the Edit Event Action dialog box.