HP Fabric OS 7.1.0, Administrator'S Manual

Page: 377 / 666

Fabric OS Administrator’s Guide 377
53-1002745-02
Supported configurations for bottleneck detection
13
You can use the bottleneckMon command to specify alerting parameters for the following:
•
Whether alerts are to be sent when a bottleneck condition is detected
•
The size of the time window to look at when determining whether to alert
•
How many affected seconds are needed to generate the alert
•
How long to stay quiet after an alert
•
If an enabled alert is for congestion, for latency, or for both
NOTE
Changing alerting parameters affects RASlog alerting as well as SNMP traps.
For more detailed information on the bottleneckmon command, consult the Fabric OS Command
Reference .
Supported configurations for bottleneck detection
The following configuration rules apply to bottleneck detection:
•
Bottleneck detection is supported only on Fibre Channel ports and FCoE F_Ports.
•
Bottleneck detection is supported only on the following port types:
-
E_Ports
-
EX_Ports
-
F_Ports
-
FL_Ports
•
F_Port and E_Port trunks are supported.
•
Long distance E_Ports are supported.
•
FCoE F_Ports are supported.
•
Bottleneck detection is supported on 4-Gbps, 8-Gbps, and 16-Gbps platforms, including
10-Gbps speeds.
•
Bottleneck detection is supported in Access Gateway mode.
•
Bottleneck detection is supported whether Virtual Fabrics is enabled or disabled. In VF mode,
bottleneck detection is supported on all fabrics, including the base fabric. See
“Virtual Fabrics
considerations for bottleneck detection” on page 378 for additional information on using
bottleneck detection in VF mode.
Limitations of bottleneck detection
The bottleneck detection feature detects latency bottlenecks only at the point of egress, not
ingress. For example, for E_Ports, only the traffic egressing the port is monitored. For FCoE ports at
the FC-DCB (Data Center Bridging) boundary, traffic going from FC to DCB is monitored, but traffic
going from DCB to FC is not monitored.
ATTENTION
Using this feature for latency bottleneck detection is not recommended for link utilizations above 85%.