HP StorageWorks 2/16V Brocade Fabric Watch Administrator's Guide - Supporting - Page 27

Configuring events, Event behavior types, Continuous event behavior, Triggered event behavior

Get HP StorageWorks 2/16V - SAN Switch PDF manuals and user guides View all HP StorageWorks 2/16V manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

Configuring events 1 Subclasses are a minor exception to the preceding mapping rule. Subclasses, such as E_Ports, contain areas with elements equivalent to the number of valid entries. Within the same example used thus far in this section, in a 64-port switch in which eight ports are connected to another switch, each area within the E_Port class would contain eight elements. Each area of a subclass with defined thresholds will act in addition to the settings applied to the element through the parent class. Assignment of elements to subclasses does not need to be performed by a network administrator. These assignments are seamlessly made through automated detection algorithms. Configuring events The following area attributes are used to define and detect events in Fabric Watch: • "Event behavior types," next • "Data values" on page 12 • "Threshold values" on page 12 • "Time bases" on page 13 • "Event settings" on page 16 You can customize the information reported by Fabric Watch by configuring event behavior types, threshold values, time bases, and event settings. You cannot change data values; these represent switch behavior that is updated by the software. EVENT BEHAVIOR TYPES Based on the number of notifications delivered for events there are two categories of event behavior types: • "Continuous event behavior," • "Triggered event behavior" Continuous event behavior Areas with event behavior types set to continuous trigger events in every sample period until the fabric no longer meets the criteria defined for the event. For example, you can configure Fabric Watch to notify you during every sample period that a port is at full utilization. This information can help you plan network upgrades. Triggered event behavior If you do not want notification during each sample period from the port hardware failure to the time of its repair, you can define the event behavior as triggered. When an event behavior is defined as triggered, Fabric Watch sends only one event notification when the fabric meets the criteria for the event. It does not send out any more notifications. For example, when a port fails, Fabric Watch sends you a notification of the failure. After you repair the port, Fabric Watch detects the repair. At this time, Fabric Watch determines that the fabric no longer meets the event criteria, and watches for the error again. The next time the port fails, it sends you another notification. Fabric Watch Administrator's Guide 11 53-0000438-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
Fabric Watch Administrator’s Guide
11
53-0000438-01
Configuring events
1
Subclasses are a minor exception to the preceding mapping rule. Subclasses, such as E_Ports,
contain areas with elements equivalent to the number of valid entries. Within the same example
used thus far in this section, in a 64-port switch in which eight ports are connected to another
switch, each area within the E_Port class would contain eight elements.
Each area of a subclass with defined thresholds will act in addition to the settings applied to the
element through the parent class. Assignment of elements to subclasses does not need to be
performed by a network administrator. These assignments are seamlessly made through
automated detection algorithms.
Configuring events
The following area attributes are used to define and detect events in Fabric Watch:
•
“Event behavior types,”
next
•
“Data values”
on page 12
•
“Threshold values”
on page 12
•
“Time bases”
on page 13
•
“Event settings”
on page 16
You can customize the information reported by Fabric Watch by configuring event behavior types,
threshold values, time bases, and event settings. You cannot change data values; these represent
switch behavior that is updated by the software.
EVENT BEHAVIOR TYPES
Based on the number of notifications delivered for events there are two categories of event
behavior types:
•
“Continuous event behavior,”
•
“Triggered event behavior”
Continuous event behavior
Areas with event behavior types set to
continuous
trigger events in every sample period until the
fabric no longer meets the criteria defined for the event.
For example, you can configure Fabric Watch to notify you during every sample period that a port is
at full utilization. This information can help you plan network upgrades.
Triggered event behavior
If you do not want notification during each sample period from the port hardware failure to the time
of its repair, you can define the event behavior as
triggered
.
When an event behavior is defined as triggered, Fabric Watch sends only one event notification
when the fabric meets the criteria for the event. It does not send out any more notifications.
For example, when a port fails, Fabric Watch sends you a notification of the failure. After you repair
the port, Fabric Watch detects the repair. At this time, Fabric Watch determines that the fabric no
longer meets the event criteria, and watches for the error again. The next time the port fails, it
sends you another notification.