Dell POWEREDGE M1000E - Manual (Page 380)

380 Fabric OS Administrator’s Guide
53-1002745-02
Enabling bottleneck detection on a switch
13
The following credit loss recovery methods are supported for Brocade 6520 back-end ports:
• For all the credit loss methods described above, a link reset will automatically be performed,
assuming that this option was enabled. See
“Enabling back-end credit loss detection and
recovery” below for details on enabling this feature.
• A manual link reset option using the bottleneckmon command is also available. See “Enabling
back-end credit loss detection and recovery” below for instructions.
NOTE
Whenever a link reset is performed on this switch, the RASlog C3-1014 message is displayed
and recorded.
Enabling back-end credit loss detection and recovery
Credit loss detection and recovery is enabled and disabled through the CLI using the
bottleneckmon --cfgcredittools command.
Notes:
• The execution of this command is subject to Virtual Fabric or Admin Domain restrictions that
may be in place. Refer to the Fabric OS Troubleshooting and Diagnostics Guide for more
information.
• The bottleneck detection commands are supported on F_Ports, FL_Ports, E_Ports, and
EX_Ports.
• The credit recovery commands are supported only on back-end ports of 4G, 8G, and 16G
Capable FC platforms for blades in the Brocade DCX, DCX-4S, DCX 8510-8, and DCX 8510-4
chassis.
Enabling bottleneck detection on a switch
Enabling bottleneck detection permits both latency and congestion detection.
Bottleneck detection is enabled on a switch basis. It is recommended that you enable bottleneck
detection on every switch in the fabric. If you later add additional switches, including logical
switches, to the fabric, be sure to enable bottleneck detection on those switches as well.
When you enable bottleneck detection on a switch, the settings are applied to all eligible ports on
that switch. If ineligible ports later become eligible or, in the case of a logical switch, if ports are
moved to the logical switch, bottleneck detection is automatically applied to those ports.
You can later override these settings on a per-port basis, as described in “Changing bottleneck
detection parameters” on page 384.
Use the following procedure to enable bottleneck detection:
1. Connect to the switch and log in using an account with admin permissions.
2. Enter the bottleneckmon --enable command to enable bottleneck detection on all eligible
ports on the switch.
By default, alerts are not sent unless you specify the alert parameter; however, you can view a
history of bottleneck conditions for the port as described in
“Displaying bottleneck statistics”
on page 391.