Brocade Fabric OS Documentation Updates - Supporting Fabric OS v6.4.x (53-1002063-09, August 2012)

38 Fabric OS Documentation Updates
53-1002063-09
bottleneckMon
5
To display the configuration:
switch:admin> bottleneckmon --status
Bottleneck detection - Enabled
==============================
Switch-wide alerting parameters:
============================
Alerts - Congestion only
Congestion threshold for alert - 0.800
Averaging time for alert - 300 seconds
Quiet time for alert - 300 seconds
Per-port overrides for alert parameters:
========================================
Port Alerts? LatencyThresh CongestionThresh Time (s) QTime (s)
===========================================================================
1 Y 0.100 0.800 300 300
2 C -- 0.800 600 600
3 L 0.100 -- 300 300
4 N -- -- -- --
2. Credit recovery enhancements
SYNTAX The credit recovery command syntax has been enhanced to support on-demand checking of certain
types of backend ports for credit loss.
bottleneckmon --cfgcredittools -intport -recover [off | onLrOnly | onLrThresh]
bottleneckmon --cfgcredittools -intport -check slot/blade_port,VC
bottleneckmon --linkreset slot/blade_port
DESCRIPTION Credit recovery on backend ports
Use the --cfgcredittools commands to enable or disable credit recovery of external backend ports and
to display the configuration. When this feature is enabled, credit is recovered on external backend ports
(ports connected to the core blade or core blade backend ports) when credit loss has been detected on
these ports. If complete loss of credit on a Condor2 backend port causes frame timeouts, a link reset will
be performed on that port regardless of the configured setting, even if that setting is -recover off. When
used with the -recover onLrOnly option, the recovery mechanism takes the following escalating actions:
• When it detects credit loss, it performs a link reset and logs a RASlog message (RAS Cx-1014).
• If the link reset fails to recover the port, the port reinitializes. A RASlog message is generated (RAS
Cx-1015). Note that the port reinitialization does not fault the blade.
• If the port fails to reinitialize, the port is faulted. A RASlog message (RAS Cx-1016) is generated.
• If a port is faulted and there are no more online backend ports in the trunk, the core blade is faulted.
(Note that the port blade will always be faulted). A RASlog message is generated (RAS Cx-1017).
When used with the -recover onLrThresh option, recovery is attempted through repeated link resets
and a count of the link resets is kept. If the threshold of more than two link resets per hour is reached, the
blade is faulted (RAS Cx-1018). Note that regardless of whether the link reset occurs on the port blade or
on the core blade, the port blade is always faulted.
If you suspect complete credit loss on a particular virtual channel (VC) on a particular backend port, use
the -check option to examine that particular backend port and VC for credit loss.