Filter
Top Products
3-8 Fabric Watch User’s Guide
Using Fabric Watch
3
• Abbreviation for the area name (alpha characters, title case). For example, “Temp” for the
Temperature area.
• Index number for the number of the item within the series. Consists of three numbers, for
example: 000 for the first port, 001 for the next, etc. Index numbers for the Fabric, Port, E_Port,
F/FL_Port (Optical), F/FL_Port (Copper), and GBIC classes begin with 000, and index numbers
for the Environment class begin with 001.
Example of a Threshold Name:
The threshold corresponding to the first thermometer in the switch is in the Environment class,
Temperature area, and is therefore named
envTemp001.
Events
An event is generated each time a boundary, as defined by the threshold, is crossed. Boundaries are
not inclusive, so events are generated only when a boundary is exceeded, not when the monitored
value has only reached them. If the event has an assigned alarm, an alarm is also generated. The
alarm can be designated as an SNMP trap, an entry in the switch error log, locking of the port log,
or a combination of these options.
When an item such as an E_Port, F/FL_Port (optical), F/FL_Port (copper), FINISAR Smart GBIC,
fan, or power supply is removed, Fabric Watch may raise an event (such as a below event), then the
threshold is hidden and disabled. When an item is added, the threshold is displayed and enabled,
and Fabric Watch may raise an event.
Event policies control the generation of events, and can be configured for either triggered events or
continuous events.
Triggered Events
A triggered event results in a single event when a boundary is exceeded. The event is not generated
again until the threshold value has returned within the boundaries and then once again exceeded
them. For example, if the switch temperature exceeds the upper boundary, a triggered event is
generated at the point the boundary is crossed, but is not repeated while the temperature remains
above the upper boundary.
The following events can be generated as triggered events:
Started No alarm is generated.
Below Counter is below the lower boundary. Must be preceded by a start, above, or in-
between event.
Above Counter is above the upper boundary. Must be preceded by a start, below, or in-
between event.
Exceeded Counter is below the lower boundary or above the upper boundary. Accompanies
a below or above event.
Changed Counter value has changed.
In-between Counter falls below the upper boundary minus buffer, or rises above the lower
boundary plus buffer. Must be preceded by an above or below event. If the buffer
is set to zero, this event is suppressed.