show statistics am-scheduler

If you execute the command as show statistics am-scheduler, the output will display information in several distinct blocks. The first block of display data gives you a high level summary of the active measurement system. The remaining sections show various active measurement statistics, such as probe rates attempted and completed, failures, DNS behavior.

ssf-neat-5008# show stat am-scheduler
 
Thu Dec 11 13:58:31 PST 2003
 
Current State: RUNNING
 
Start Time   : 1071113800423 ms, 2003/12/10 19:36:40.423, 18h21m50s940ms ago
 
Reconfig Time: 1071176828121 ms, 2003/12/11 13:07:08.121, 51m23s242ms ago
 
Clear Time   : 1071113800443 ms, 2003/12/10 19:36:40.443, 18h21m50s920ms ago
 
Last EFC Resp: 1071179911191 ms, 2003/12/11 13:58:31.191, 172ms ago
 
Debug Mode   : off
 
Configuration Summary
 
Total Number of Targets                 : 84
 
Number of TCP Targets                   : 34
 
Number of ICMP Targets                  : 50
 
Number of Traceprobe Targets            : 0
 
Number of Unknown Targets               : 0
 
Configured Total Probes Per Second      : 510.766667
 
Configured Max Probes Per Second        : 1000.0
 
Multiplying rates by scale factor       : 1.0
 
Expected DNS Lookups Per Second         : 0.0
 
Configuration Errors
 
         Group           Target          Type  Error
 
Normal Events (per minute)
 
name               total-count    1-min    5-min   60-min     peak peak age
 
Tot Req Att           32030931    30214    30177    29246    31681 0d00:06:41
 
Tot Req Sent          32030931    30214    30177    29246    31681 0d00:06:41
 
TCP Req Att              74471       68       67       68       78 0d05:23:12
 
TCP Req Sent             74471       68       67       68       78 0d05:23:12
 
ICMP Req Att          31956460    30146    30109    29178    31609 0d00:06:41
 
ICMP Req Sent         31956460    30146    30109    29178    31609 0d00:06:41
 
Trace Req Att                0        0        0        0        0 0d18:21:50
 
Use Trace Cache              0        0        0        0        0 0d18:21:50
 
Trace Req Sent               0        0        0        0        0 0d18:21:50
 
Results Rcvd          32019819    30155    30179    29234    31218 0d00:06:52
 
Result Recorded       32019826    30155    30179    29234    31218 0d00:06:52
 
Trace Meas Sent              0        0        0        0        0 0d18:21:50
 
Trace No Conv                0        0        0        0        0 0d18:21:50
 
Bifurcated Prov              0        0        0        0        0 0d18:21:50
 
EFC Successes           128106      118      117      117      123 0d00:07:27
 
Fail Rpts Rcvd        17339161    16313    16313    15284    18798 0d14:22:04
 
Fail Rpts Sent          397196      446      447      437      989 0d14:22:10
 
Fail Rpts Supp        16941965    15867    15866    14847    17974 0d14:35:28
 
Error Events (per minute)
 
name               total-count    1-min    5-min   60-min     peak peak age
 
EFC Failures                 0        0        0        0        0 0d18:21:50
 
EFC Timeouts                 7        0        0        0        5 0d05:48:15
 
DNS No Host                  0        0        0        0        0 0d18:21:50
 
DNS Timeouts                 0        0        0        0        0 0d18:21:50
 
DNS Error                    0        0        0        0        0 0d18:21:50
 
Unk Resolver                 0        0        0        0        0 0d18:21:50
 
Req Connect Err              0        0        0        0        0 0d18:21:50
 
Runt Req Err                 0        0        0        0        0 0d18:21:50
 
Req Send Err                 0        0        0        0        0 0d18:21:50
 
Result Rcv Err               0        0        0        0        0 0d18:21:50
 
Times (in microseconds)
 
name               1-min    5-min   60-min     peak peak age
 
DNS Time               0        0        0        0 0d18:21:50
 
EFC Time            2907     4113     4114    27408 0d05:47:40
 
Other
 
name               1-min    5-min   60-min     peak peak age
 
Trace Cache%           0        0        0        0 0d18:21:50
 
Disabled Groups
 
Group                     Group                     Group
 
rs-web-clients                                      Duplicate Targets
 
Group                         Target                         Type  Rate   Port
 
netscreen-targets             67.21.230.64                   icmp  12/m   n/a
 
rw-home                       67.21.230.64                   icmp  4/m    n/a
 
Configured Target Diagnostics
 
         group           target          type       address
 
top-n-efc       (EFC)           icmp       12.2.41.18
 
VIP Definitions
 
Vip             Ustat (Address)
 
(default)       4 (64.254.162.201), 5 (64.254.162.202), 6 (64.254.162.203) 
 

 

• Start time is the last time the process was started,
• reconfig time is the last time it was reconfigured, and
• clear time shows the last time the clear statistics command was executed for the am-scheduler process.
• Last EFC Resp shows how long, in microseconds, it has been since the active measurement system has heard from the efc process.
• Configured Total Probes Per Second in the show command output will be the value entered into the configuration, not the scaled-back actual number of probes.
• Configured Max Probes Per Second value is the value which has been set in your configuration by the active-measurement max-probes-per-second command.
• Multiplying rates by scale factor shows.
• Expected DNS Lookups Per Second value is a calculated estimate of how many DNS lookups are required per second to support your configured active probing rate.

The next block “Normal Events (per minute)” shows rolling averages of per-minute rates of probes sent. The 1-min column shows average probes per minute during the previous 60 seconds; the 5-min column shows average per-minute rate during the previous five minutes, and the 60-min column shows average per-minute rate during the previous hour.

The rows show totals for the various types of probes attempted and sent (e.g., the number of TCP and ICMP probes attempted and sent).

• Req Att values (probe requests attempted) are incremented when the scheduled time for the probe arrives
• Req Snt values (probe requests sent) are incremented when the am-scheduler process hands the probe off to the am-measurer process. Normally, these values should be identical to the Rq Att values for a particular category.
• TCP Att and TCP Snt are the number of TCP probes attempted and sent respectively.
• ICMP Att and ICMP Snt are the number of ICMP probes attempted and sent respectively.
• Trace Att and Trace Snt are the number of traceprobes attempted and sent respectively.
• Trc Cache is the number of traceprobe results pulled from cached values rather than measured from the network.
• Trace Meas is the number of traceprobe measurements am-scheduler sends to the decision maker process.
• Trace No Conv is the number of traceprobes that failed to converge.
• Bifurcated Prov is the number of bifurcated provider networks that the systems has detected. A bifurcated provider is one whose network has portions that are internally isolated from each other within their network, but still reachable from different external routes.

The requests sent values should be matched by requests received values in the show statistics am-measurer output.

Possible causes for a mismatch between sent and received values are: DNS lookup of target’s host name failed, and an internal error. The average DNS lookup times should be short enough to handle the number of lookups expected.

• EFC Successes (internal statistic)
• Fail Rpts Rcvd shows the number of probe failures seen by the USTAT.
• Fail Rpts Sent shows the number of probe failures reported to the decision-maker process by the USTAT.
• Fail Rpts Supp shows the number of suppressed probe failures. This occurs when failures are detected across all links for a particular probe.

The block titled “Error Events (per minute)” has the following:

• EFC Failures (internal statistic)
• EFC Timeouts (internal statistic)
• DNS No Host indicates that the DNS server was not able to resolve a host name.
• DNS Timeouts shows the number of DNS server timeouts.
• DNS Error indicates some other DNS-related error different from the previous No Host and Timeouts errors (e.g., bind is not running).
• Unk Resolver (internal statistic)
• Req Connect Err indicates an internal communications error between the am-scheduler and am-measurer processes. This error can occur if the measurer process is not yet running when the process sends it a packet, such as during a reboot, or after a Medic restart of the am-scheduler process, or after a configuration change has triggered a restart of the am-measurer process.
• Runt Req Err this is packet that is below the minimum length for its type, a condition that should be extremely rare, and can be caused by a hardware problem.
• Req Send Err indicates a problem with communication between the am-scheduler and am-measurer processes (see Req Connect Err).
• Result Rcv Err indicates a problem with communication between the am-scheduler and am-measurer processes (see Req Connect Err).

The block titled “Times (in microseconds)” shows the following:

• DNS Time shows the average time, in microseconds, used to resolve DNS names.
• EFC Time shows the average time, in microseconds, used to resolve DNS names.

Miscellaneous items:

• Trc Cache% shows the percentage of traceprobe measurements reported out of cache rather than measured in the network.
• Disabled Groups show active measurement groups that have been disabled in the configuration (see the disable command)
• Duplicate Targets are those that have been duplicated in the configuration (same target definition in two separate groups, or one in a group and another not in a group). Two probes to the same IP address are not necessarily considered duplicate targets--DNS may have resolved a host name to the same IP address of another target. Addresses that differ only in syntax (1.2.3.4 and 001.002.003.004, for example) will not be flagged as duplicates. If more than one probe is configured with the same host name, the probes will be considered duplicates. This table is informational only. Probes will be sent as configured, even if duplicated. If the duplication is not desirable, you will need to correct it in the configuration yourself
• VIP Definitions section shows, for each VIP name, the IP address that each ustat has for that name.

If you have configured a greater number of probes per second than allowed by the probe-backoff command, the CNA system will scale back the number of probes to conform with the limit. See Measurement Frequency earlier in this chapter for more information.

See the active-measurement group command in the CNA Command Reference Guide for more information about configuring target parameters for probes that are defined in an active measurement group.)