Dell POWEREDGE M1000E - Manual (Page 111)

Fabric OS Command Reference 83
53-1002746-01
bottleneckMon
2
When you specify one of the three alert options, the following parameters become
available, although the threshold options are subject to the restrictions stated
above.
-cthresh congestion_threshold
Specifies the severity threshold for congestion that triggers an alert. The
threshold indicates the percentage of one-second intervals affected by the
bottleneck condition within the specified time window. The threshold is
expressed as the equivalent fraction between 0 and 1. The default value is
0.8.
-lthresh latency_threshold
Specifies the severity threshold for latency that triggers an alert. The
threshold indicates the percentage of one-second intervals affected by the
bottleneck condition within the specified time window. The threshold is
expressed as the equivalent fraction between 0 and 1. The default value is
0.1.
-time window
Specifies the time window in seconds over which the percentage of seconds
affected by bottleneck conditions is computed and compared with the
threshold. The maximum window size is 10800 seconds (3 hours). The
default is 300 seconds. This parameter is valid with all three alert options.
-qtime quiet_time
Specifies the minimum number of seconds between consecutive alerts. The
default is 300 seconds. The maximum is 31556926 seconds (approximately
one year). This parameter is valid with all three alert options.
-noalert
Disables alerts. This is the default state assumed if neither -alert nor -noalert is
specified.
-lsubsectimethresh time_threshold
Sets the threshold for latency bottlenecks at the sub-second level. The
time_threshold specifies the minimum fraction of a second that must be affected
by latency in order for that second to be considered affected by a latency
bottleneck. For example, a value of 0.75 means that at least 75% of a second
must have had latency bottleneck conditions in order for that second to be
counted as an affected second. The time threshold value must be greater than 0
and no greater than 1. The default value is 0.8. Note that the application of the
sub-second numerical limits is approximate. This command erases the statistics
history and restarts alert calculations (if alerting is enabled) on the specified ports.
When used with the config option, you must specify a port.
-lsubsecsevthresh severity_threshold
Specifies the threshold on the severity of latency in terms of the throughput loss
on the port at the sub-second level. The severity threshold is a floating-point value
in the range of no less than 1 and no greater than 1000. This value specifies the
factor by which throughput must drop in a second in order for that second to be
considered affected by latency bottlenecking. For example, a value of 20 means
that the observed throughput in a second must be no more than 1/20th the
capacity of the port in order for that second to be counted as an affected second.
The default value is 50. This command erases the statistics history and restarts
alert calculations (if alerting is enabled) on the specified ports. When used with the
config option, you must specify a port.