Example Interface Health Report shows an example health report output for an interface that was above an 80% utilization threshold 70.28% of the time, during which time there were 3 operating status changes. The graph visually shows that one of the peaks in utilization occurred on October 6. Moving the cursor over that point gives the exact date and utilization values.

• For Object, Filter, and Time Range, see Configuring and Running Reports.

• Utilization Threshold—Threshold interface traffic must surpass to be included in the report.

One use case is to determine if interface queues traffic is exceeding thresholds or trending upward, which might trigger a QoS policy modification or a traffic engineering exercise. An interface queues health report shows threshold definitions, including traffic and utilization based on the overall interface capacity.

An interface queues health report shows the percentage of time an object's property exceeds a threshold, shows a trend line against traffic, and extrapolates traffic according to the observed trend.

• For Object, Filter, and Time Range, see Configuring and Running Reports.

• Utilization Threshold—Threshold interface queues traffic must surpass to be included in the report.

The LAG Imbalance/Risk graph shows the imbalance and risk compared to the high- and medium-risk thresholds, as well as whether and when the LAG passes these thresholds. The difference between risk and imbalance measurements is that risk calculations consider only positive differences, whereas imbalance calculations consider both negative and positive differences. For example, Example LAG Imbalance and LAG Risk Graph shows that a LAG’s utilization was significantly imbalanced for several days, while it was only minimally at risk.

• Risk—Highest Util Out of Any Member - Average Util Out of All LAG Members

• Imbalance—Higher of these two values:

  • Risk

  • Average Util Out of All LAG Members - Lowest Util Out of Any Member

Example: This example LAG has four members.

• Util Out values are 0.10, 0.35, 0.55, and 0.40

• Highest Util Out of Any Member = 0.55

• Lowest Util Out of Any Member = 0.10

• Average Util Out of All LAG Members = (0.10 + 0.35 + 0.55 + 0.40)/4 = 0.35

• Risk = 0.55 - 0.35 = 0.20

• Imbalance = 0.25 because it is the higher of the following two values:

  • Risk, which is 0.20

  • 0.35 - 0.10 = 0.25

The Util Out graph shows the Util Out percentage of all of the LAG’s members over the report period (Example LAG Member Util Out Graph). If you see that a LAG is imbalanced or at risk, this graph is helpful in determining which of the members is causing these effects.

In addition to these graphs, the report output includes the following utilization, imbalance, and risk values:

• Number of LAG members, which are viewable individually by clicking the blue number in the LAG Members column.

• Peak member utilization.

• Peak aggregated risk.

• Peak aggregated imbalance.

• Most recent aggregated risk.

• Most recent aggregated imbalance.

• Percentage of time the LAG was over the high-risk threshold.

• Percentage of time the LAG was over the medium-risk threshold.

This example compares two scenarios to demonstrate how you could interpret the data.

• LAG A: Nine LAG members are at 60% utilization and one LAG member is at 0%.

  While LAG A is imbalanced, it does not appear to be at high risk. Traffic coming into this LAG will likely not pose a problem since the data suggests that even if one member fails, the other nine members can handle the traffic.

• LAG B: Nine LAG members are at 60% utilization and one LAG member is at 90%.

  LAG B is imbalanced and likely at high risk. One particular member is receiving much more traffic than the other members. If this happens when traffic is coming into LAG B and if that traffic is assigned to the member with 90% utilization, there might not be sufficient bandwidth left to handle the traffic, resulting in dropped packets.

• For Filter and Time Range, see Configuring and Running Reports.

• LAG Imbalance

  • Include LAGs with members exceeding __%—Specify the percentage of Util Out threshold used in determining which LAGs are included in the report. If any LAG member surpasses it, then the LAG is included in the report.

  • High- and Medium-risk threshold—Specify the thresholds used to determine whether a LAG is imbalanced or at risk. The value must be between 0 and 1.

• For Object, Filter, and Time Range, see Configuring and Running Reports.

• SetupBW Threshold—Setup bandwidth threshold that LSPs must surpass to be included in the report.

• For Filter and Time Range, see Configuring and Running Reports.

• CPU Threshold—CPU threshold that nodes must surpass to be included in the report.

• Memory Threshold—Memory threshold that nodes must surpass to be included in the report.