Adding An Port Offline Policy - Brocade Communications Systems Brocade BladeSystem 4/24 User Manual

9. Enter all or part of the message ID associated with SNMP traps and Syslog messages in the
10. Define the trigger in the IP Address, Node WWN, and Name list.
11. Enter a value (between 2 and 999) in the Count field.
12. Enter a value (between 1 and 999) in the Duration field.
13. Select the duration type (Seconds or Minutes) from the Duration list.
14. Select the check box in the Actions list for each action you want to occur when this policy is
15. Click OK on the Add Event Policy dialog box.
16. Select the Active check box for the policy you want to activate.
17. Click OK on the Event Policies dialog box.

Adding an Port offline policy

To add an Port offline policy, complete the following steps.
1. Select Monitor > Event Policies.
2. Click Add.
3. Enter a name (1024 characters maximum) for the policy in the Name field.
4. Enter a description (1024 characters maximum) for the policy in the Description field.
5. Select Port Offline from the Policy Type list.
DCFM Enterprise User Manual
53-1001775-01
Message ID field.
If the entry matches or is part of the message ID, the policy is triggered.
The trigger is limited to 1024 characters. Multiple values must be separated by a semi-colon.
When multiple values are entered, as long as at least one value matches in the event and all
other conditions are met, an action is triggered.
IP addresses can either be in IPv4 or IPv6 format and must be complete.
A Node WWN is accepted with or without the colon.
The maximum duration is 30 minutes.
triggered.
For a list of the available actions, refer to
refer to "Defining the broadcast message action"
action" on page 263, "Defining the send e-mail action"
data capture action" on page 265.
The Event Policies dialog box displays.
The Add Event Policy dialog box displays.
Policy names must be unique; however, they are case insensitive.
Adding an Port offline policy
"Policy actions" on page 258. To define an action,
on page 262, "Defining the launch script
on page 264, or
10
"Configuring support
259