Brocade Communications Systems IP250 Special events handling, Acknowledging special events

37 Event action definitions

•Event Sender: Deploy the payload to the product that sent the event. If the event was sent by a non-IronWare OS or Network OS product, the event action will not be deployed to that product.

•Derived from: Deploy the payload to the product that matches the IP address as specified in the attribute of the selected source. If the matching product is a non-IronWare OS or Network OS product, the event action will not be deployed to that product.

•Specified in the Config: Deploy the payload to the product that is specified in the payload. If the configuration you choose contains a non-IronWare OS or Network OS product as a target, the configuration will not be deployed to the non-IronWare OS or Network OS product.

14.If you selected Derived from as the target in step 13, select the attribute from the Source list.

15.From the Transformation column, specify what you want Event Processor to do with the value in the attribute:

•None — Event Processor only reports the occurrence of the product.

•Find Device — Find the product with the IP address in the attribute and deploy the payload to that product.

•Find Intruder MAC — Find the product with the IP address in the attribute that matches the intruder MAC address and deploy the CLI configuration to that product.

•Find Port — Find the port on a product with the IP address in the attribute and deploy the CLI configuration to that port.

The Transformation column uses the product IP addresses and MAC addresses listed in the Address Finder. If the Address Finder list is empty, the product or port will not be found.

16.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.

See step 8 of “Editing event actions” on page 1173 for information on enabling special events handling for an event using the Actions pane of the Edit Event Action dialog box.

Acknowledging special events

When the Management application receives and processes events selected as special events, the following status bar icon displays:

1176	Brocade Network Advisor IP User Manual
	53-1003056-01