Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)

110 Fabric Manager Administrator’s Guide
53-10000610-02
Performance monitoring components
8
Performance monitoring components
Before you start using performance monitoring on your fabric, you need to be familiar with the
following components:
• “Port statistics” on page 110
• “End-to-end monitoring” on page 110
• “Granularity” on page 111
• “Reports” on page 112
• “Graphs” on page 112
• “Templates” on page 113
Port statistics
The port statistics component within the performance monitoring feature in Fabric Manager allows
you to see how much traffic a particular port is generating on a fabric over a period of time. The
receive (RX) and transmit (TX) values for ports are retrieved over a specific timeframe and stored in
a database. Error monitoring for ports is also available in port statistic performance monitoring;
there are eight possible error counters that can be monitored.
Monitoring port statistics does not require an Advanced Performance Monitoring license.
Port statistic data collection is not supported on switches running Fabric OS 2.x and earlier.
End-to-end monitoring
End-to-end monitoring sets all possible target and initiator pairs from the filtered list retrieved from
the API for the fabric. Fabric Manager stores the configuration of the monitors persistently and
periodically re-creates them on the fabric as necessary. Each time the Fabric Manager server
retrieves the monitor values, it checks for and re-creates any monitors (configured through Fabric
Manager) that are no longer present. If a resource limit is reached while trying to set all of the
possible pairs, performance monitoring does not attempt to determine the best set of monitors.
Instead, monitors are set on a first-come, first-serve basis (in the order presented to Fabric
Manager from the API).
Configuration of data capture file information is not supported. The monitor values for the
end-to-end monitors are retrieved at a set interval (that is not configurable) and stored in the
database from the previous release. You can then request that reports be generated from the
stored data (see “Custom reports and graphs” on page 118 for more information on running the
reports).
Fabric Manager attempts to set the monitors between the following types of devices only:
• initiator-target
• initiator-unknown
• target-unknown
• initiator and target-any device role
• unknown-any device role
Monitors between initiator-initiator and target-target are not set. Monitors between all other device
types are valid.