HP Brocade 8/12c Fabric Watch Administrator's Guide v6.4.0 (53-1001770-01, Jun - Page 28

Types of event behaviors, Continuous event behavior, Triggered event behavior

Page 28 highlights

1 Fabric Watch event settings Types of event behaviors Based on the number of notifications delivered for events, there are two categories of automatic notifications: • Continuous event behavior • Triggered event behavior Continuous event behavior A continuous alarm provides a warning message whenever a threshold is breached; it continues to send alerts until the condition is corrected. For example, if a switch exceeds its temperature threshold, Fabric Watch activates an alarm at every measurement interval until the temperature returns to an acceptable level. You can set behavior type events to continuously trigger during a given sample period, until the fabric no longer meets the criteria defined for the event. As an 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 A triggered alarm generates the first warning when a threshold condition is reached and a second alarm when the threshold condition is cleared. 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. Triggered is the default behavior type signal for all class areas. 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. Whereas a triggered behavior type sends only one event notification when the fabric meets the criteria for the event, a continuous behavior type signals you continuously after a threshold has been crossed. For specific configuration procedures, refer to the following chapters in this guide: • "Setting Fabric Watch custom and default values" on page 35 • "Customizing thConfig command settings" on page 52 • "portThConfig command procedures" on page 69 • "System monitoring using the sysMonitor command" on page 85 For detailed information about all Fabric Watch commands, refer to the Fabric OS Command Reference Manual. 8 Fabric Watch Administrator's Guide 53-1001770-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
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144

8
Fabric Watch Administrator’s Guide
53-1001770-01
Fabric Watch event settings
1
Types of event behaviors
Based on the number of notifications delivered for events, there are two categories of automatic
notifications:
Continuous event behavior
Triggered event behavior
Continuous event behavior
A
continuous alarm
provides a warning message whenever a threshold is breached; it continues to
send alerts until the condition is corrected. For example, if a switch exceeds its temperature
threshold, Fabric Watch activates an alarm at every measurement interval until the temperature
returns to an acceptable level.
You can set behavior type events to continuously trigger during a given sample period, until the
fabric no longer meets the criteria defined for the event.
As an 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
A
triggered alarm
generates the first warning when a threshold condition is reached and a second
alarm when the threshold condition is cleared.
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
. Triggered is the default behavior type
signal for all class areas.
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.
Whereas a
triggered
behavior type sends only one event notification when the fabric meets the
criteria for the event, a
continuous
behavior type signals you continuously after a threshold has
been crossed.
For specific configuration procedures, refer to the following chapters in this guide:
“Setting Fabric Watch custom and default values”
on page 35
“Customizing thConfig command settings”
on page 52
“portThConfig command procedures”
on page 69
“System monitoring using the sysMonitor command”
on page 85
For detailed information about all Fabric Watch commands, refer to the
Fabric OS Command
Reference Manual
.