HP StorageWorks 1606 Brocade Fabric Watch Administrator's Guide v6.3.0 (53-100 - Page 28

Fabric Watch audit messages, Data values

Page 28 highlights

1 Fabric Watch audit messages Fabric Watch audit messages Fabric Watch events caused by configuration value changes are tagged as Audit messages. NOTE Audit messages are generated for port fencing configuration changes, whether port fencing is enabled or disabled. You can set up an external host to receive Audit messages so you can easily monitor unexpected changes. For information on error messages generated by Fabric Watch, see the Fabric OS Message Reference. For information on configuring an Audit Log, see the Fabric OS Administrator's Guide. Data values A data value represents three aspects of a fabric: a counter value, a measured value, or a state value. Data values are updated by Fabric Watch approximately every six seconds, an interval that you cannot change. • Counter value is the total number of times that a given event has occurred. For each monitored event during the time period, the value is incremented. • Measured value is the current, measurable value of a fabric or fabric element, such as environmental temperature. • State value, which is the only qualitative data value, provides information on the overall state of a fabric component. Instead of numerical data, state values contain information on whether components are faulty, active, or in another state. Fabric Watch compares counter values and measured values to a set of configurable limits to determine whether fabric monitoring has occurred and whether to notify you. You must set appropriate threshold boundaries to trigger an event. State values are handled differently, as Fabric Watch monitors state values for certain states which you can select. When a state value transitions to one of the monitored states, an event is triggered. 4 Fabric Watch Administrator's Guide 53-1001342-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

4
Fabric Watch Administrator’s Guide
53-1001342-01
Fabric Watch audit messages
1
Fabric Watch audit messages
Fabric Watch events caused by configuration value changes are tagged as Audit messages.
NOTE
Audit messages are generated for port fencing configuration changes, whether port fencing is
enabled or disabled.
You can set up an external host to receive Audit messages so you can easily monitor unexpected
changes. For information on error messages generated by Fabric Watch, see the
Fabric OS
Message Reference
. For information on configuring an Audit Log, see the
Fabric OS Administrator’s
Guide.
Data values
A data value represents three aspects of a fabric: a counter value, a measured value, or a state
value. Data values are updated by Fabric Watch approximately every six seconds, an interval that
you cannot change.
Counter value
is the total number of times that a given event has occurred. For each monitored
event during the time period, the value is incremented.
Measured value
is the current, measurable value of a fabric or fabric element, such as
environmental temperature.
State value
, which is the only qualitative data value, provides information on the overall state
of a fabric component. Instead of numerical data, state values contain information on whether
components are faulty, active, or in another state.
Fabric Watch compares counter values and measured values to a set of configurable limits to
determine whether fabric monitoring has occurred and whether to notify you. You must set
appropriate threshold boundaries to trigger an event.
State values are handled differently, as Fabric Watch monitors state values for certain states which
you can select. When a state value transitions to one of the monitored states, an event is triggered.