378
Fabric OS Administrator’s Guide
53-1002745-02
Supported configurations for bottleneck detection
13
High availability considerations for bottleneck detection
The bottleneck detection configuration is maintained across a failover or reboot; however,
bottleneck statistics collected are lost.
Upgrade and downgrade considerations for bottleneck detection
The bottleneck detection configuration is persistent across firmware upgrades and downgrades.
The sub-second latency criterion parameter settings are not preserved on downgrade to firmware
versions earlier than Fabric OS 7.0.0. If you downgrade and then upgrade back to Fabric OS 7.0.0,
the settings revert to their default values.
Trunking considerations for bottleneck detection
A trunk behaves like a single port. Both latency and congestion bottlenecks are reported on the
master port only, but apply to the entire trunk.
For masterless trunking, if the master port goes offline, the new master acquires all the
configurations and bottleneck history of the old master and continues with bottleneck detection on
the trunk.
Virtual Fabrics considerations for bottleneck detection
Bottleneck detection is supported in both VF and non-VF modes.
In VF mode, if a port on which bottleneck detection is enabled is moved out of a logical switch, any
per-port configurations are retained by the logical switch. The per-port configuration does not
propagate outside of the logical switch. If the port is returned to the logical switch, the previous
per-port configurations are automatically set for the port. See
“Changing bottleneck detection
parameters”
on page 384 for more information about changing per-port configurations.
In logical fabrics, bottleneck detection is not performed on logical ISLs.
Because a base fabric carries traffic from multiple logical fabrics, bottlenecks reported in the base
fabric can be caused by a mixture of traffic from multiple logical fabrics or by traffic from a single
logical fabric. It is not possible to attribute a base fabric bottleneck to the exact logical fabric
causing it. Dedicated ISLs are exclusive to one logical fabric, and any bottleneck on a dedicated ISL
E_Port pertains entirely to the traffic of that logical fabric.
Access Gateway considerations for bottleneck detection
If bottleneck detection is enabled on a logical switch with some F_Ports connected to an Access
Gateway, you do not get information about which device is causing a bottleneck, because devices
are not directly connected to this port. To detect bottlenecks on an Access Gateway, enable
bottleneck detection on the Access Gateway to which the devices are actually connected.
Summary of Contents for Fabric OS 7.1.0
Page 1: ...53 1002745 02 25 March 2013 Fabric OS Administrator s Guide Supporting Fabric OS 7 1 0 ...
Page 24: ...24 Fabric OS Administrator s Guide 53 1002745 02 ...
Page 28: ...28 Fabric OS Administrator s Guide 53 1002745 02 ...
Page 32: ...32 Fabric OS Administrator s Guide 53 1002745 02 ...
Page 42: ...42 Fabric OS Administrator s Guide 53 1002745 02 ...
Page 132: ...132 Fabric OS Administrator s Guide 53 1002745 02 Frame Redirection 4 ...
Page 194: ...194 Fabric OS Administrator s Guide 53 1002745 02 Ports and applications used by switches 6 ...
Page 254: ...254 Fabric OS Administrator s Guide 53 1002745 02 Brocade configuration form 8 ...
Page 274: ...274 Fabric OS Administrator s Guide 53 1002745 02 Validating a firmware download 9 ...
Page 302: ...302 Fabric OS Administrator s Guide 53 1002745 02 Creating a logical fabric using XISLs 10 ...
Page 344: ...344 Fabric OS Administrator s Guide 53 1002745 02 Concurrent zone transactions 11 ...
Page 374: ...374 Fabric OS Administrator s Guide 53 1002745 02 Setting up TI over FCR sample procedure 12 ...
Page 462: ...462 Fabric OS Administrator s Guide 53 1002745 02 ...
Page 490: ...490 Fabric OS Administrator s Guide 53 1002745 02 Ports on Demand 18 ...
Page 498: ...498 Fabric OS Administrator s Guide 53 1002745 02 Supported topologies for ICL connections 19 ...
Page 626: ...626 Fabric OS Administrator s Guide 53 1002745 02 Preparing a switch for FIPS B ...
Page 630: ...630 Fabric OS Administrator s Guide 53 1002745 02 Hexadecimal Conversion C ...
Page 666: ...666 Fabric OS Administrator s Guide 53 1002745 02 ...