3

Using Fabric Watch

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

3-8

Fabric Watch User’s Guide

Page 19 Page 21
Page 20
Image 20
Finisar Brocade Fabric Watch manual Triggered Events
Page 19 Page 21

Brocade Fabric Watch specifications

Finisar Brocade Fabric Watch is an advanced network management solution designed to simplify the monitoring and administration of storage networks. Its primary goal is to enhance the performance and reliability of data center operations by providing comprehensive visualization and management capabilities.

One of the standout features of Fabric Watch is its ability to deliver real-time monitoring of the health and performance of network devices. This is critical for organizations that require constant uptime and high availability for their storage systems. Fabric Watch continuously assesses the status of switches, routers, and other devices within the fabric, enabling administrators to quickly identify potential issues before they escalate into problems that could disrupt operations.

The technology behind Fabric Watch encompasses various innovative aspects that enhance its functionality. For instance, the solution uses advanced analytics to assess historical performance trends, allowing IT teams to predict potential bottlenecks and optimize resource allocation effectively. This predictive capability not only improves operational efficiency but also reduces the risk of downtime, ensuring that organizations can maintain consistent access to critical data.

Furthermore, Fabric Watch supports a range of protocols and standards, making it compatible with various environments and configurations. This flexibility is crucial for companies that have heterogeneous systems and diverse technology stacks. As a result, organizations can deploy Fabric Watch across different platforms, ensuring a unified approach to network management.

Another notable characteristic of Fabric Watch is its intuitive user interface, which makes it user-friendly for administrators of varying skill levels. The dashboard presents a centralized view of the entire storage network, complete with graphical representations of performance metrics, alerts, and health statuses. This visual approach facilitates rapid decision-making, allowing teams to address issues quickly and maintain optimal performance.

In addition, Fabric Watch integrates seamlessly with existing data center management tools and workflows, providing a holistic view of the infrastructure. This integration capability supports broader initiatives around automation and orchestration, enabling organizations to create more streamlined and efficient operational processes.

In summary, Finisar Brocade Fabric Watch stands out as a robust solution for managing and monitoring storage networks. Its real-time monitoring, predictive analytics, compatibility across platforms, and user-friendly interface make it an essential tool for IT teams seeking to enhance performance and reliability in today’s demanding data environments. By employing Fabric Watch, organizations can better navigate the complexities of their storage networks, ensuring they remain agile and responsive to business needs.
Top Page Image Contents