Brocade Fabric OS Command Reference (Supporting Fabric OS v7.3.0) - Manual (Page 108)

78 Fabric OS Command Reference
53-1003131-01
bottleneckMon
2
bottleneckMon
Monitors and reports latency and congestion bottlenecks on F_Ports and E_Ports.
SYNOPSIS
bottleneckmon --enable [-cthresh congestion_threshold]
[-lthresh latency_threshold] [-time seconds]
[-qtime seconds] [-alert | -alert=congestion |
-alert=latency | -noalert]
[-lsubsectimethresh time_threshold]
[-lsubsecsevthresh severity_threshold]
bottleneckmon --disable
bottleneckmon --config [-cthresh congestion_threshold]
[-lthresh latency_threshold][-time seconds]
[-qtime seconds] [-alert | -alert=congestion |
-alert=latency | -noalert]
[-lsubsectimethresh time_threshold]
[-lsubsecsevthresh severity_threshold]
[[slot/]port_list]
bottleneckmon --configclear [slot/]port_list
bottleneckmon --exclude [slot/]port_list
bottleneckmon --include [slot/]port_list
bottleneckmon --show [-interval seconds] [-span seconds]
[-refresh][-congestion | -latency] [[slot/]port | '*']
bottleneckmon --status
bottleneckmon --help
DESCRIPTION
Use this command to (1) detect latency and congestion bottlenecks on F[L]_Ports and E_Ports and (2) to
manage credit recovery on backend ports. Bottleneck detection and credit recovery are two independent
functions; enabling credit recovery has no impact on bottleneck detection and vice versa.
Bottleneck Detection
For bottleneck detection, this command provides the following management functions:
• Enabling or disabling bottleneck detection on a switch and optionally configuring thresholds and alert
parameters.
•
Changing alert parameters on specified ports after you have enabled the feature on the switch.
•
Configuring severity thresholds for congestion and latency bottlenecks for a switch or for a specified
port list.
•
Configuring for congestion and/or latency bottlenecks for a switch or for a specified port list.
•
Refining the criterion for defining latency bottleneck conditions to allow for more (or less) sensitive
monitoring at the sub-second level.
• Clearing the configuration on specified ports only (this option cannot be performed switch-wide).
• Excluding specified ports from being monitored or including previously excluded ports.
• Generating history or status reports that show congestion bottlenecks and latency bottlenecks.