Traffic Health Monitoring

GigaVUE-FM allows you to monitor the traffic health status of the entire monitoring session and also the individual V Series Nodes for which the monitoring session is configured. Traffic health monitoring focuses on identifying any discrepancies (packet drop or overflow etc) in the traffic flow. When any such discrepancies are identified, GigaVUE-FM propagates the health status to corresponding monitoring session. GigaVUE-FM monitors the traffic health status in near real-time. GigaVUE V Series Node monitors the traffic, when the traffic limit goes beyond the upper or lower threshold values that is configured, it notifies GigaVUE-FM, based on which traffic health is computed.

Note:  When GigaVUE-FM and GigaVUE V Series Nodes are deployed in different cloud platforms, then the GigaVUE-FM public IP address must be added to the Data Notification Interface as the Target Address in the Event Notifications page. Refer to Configuration Settings section for configuration details.

This feature is supported for GigaVUE V Series Nodes on the respective cloud platforms:

For V Series Nodes:

  • AWS
  • Azure
  • OpenStack
  • VMware
  • Third Party Orchestration

The following section gives step-by-step instructions on creating, applying, and editing threshold templates across a monitoring session or an application, and viewing the traffic health status. Refer to the following section for more detailed information:

Keep in mind the following points when configuring a threshold template:

  • By default Threshold Template is not configured to any monitoring session. If you wish to monitor the traffic health status, then create and apply threshold template to the monitoring session.
  • Editing or redeploying the monitoring session will reapply all the threshold policies associated with that monitoring session.
  • Deleting or undeploying the monitoring session will clear all the threshold policies associated with that monitoring session.
  • After applying threshold template to a particular application, you need not deploy the monitoring session again.

Supported Resources and Metrics

The following table lists the resources and the respective metrics supported for traffic health monitoring

Resource

Metrics

Threshold types

TriggerCondition

Tunnel End Point
  1. Tx Packets
  2. Rx Packets
  3. Tx Bytes
  4. Rx Bytes
  5. Tx Dropped
  6. Rx Dropped
  7. Tx Errors
  8. Rx Errors
  1. Difference
  2. Derivative
  1. Over
  2. Under

RawEnd Point

  1. Tx Packets
  2. Rx Packets
  3. Tx Bytes
  4. Rx Bytes
  5. Tx Dropped
  6. Rx Dropped
  7. Tx Errors
  8. Rx Errors
  1. Difference
  2. Derivative
  1. Over
  2. Under

Map
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

Slicing
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

Masking
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

Dedup
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

HeaderStripping

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

TunnelEncapsulation

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

LoadBalancing

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

SSLDecryption

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

Application Metadata

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

AMI Exporter

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

Geneve
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

5G-SBI

  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

SBIPOE
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

PCAPNG
  1. Tx Packets
  2. Rx Packets
  3. Packets Dropped
  1. Difference
  2. Derivative
  1. Over
  2. Under

Create Threshold Template

To create threshold templates:

  1. There are two ways to navigate to the Threshold Template page, they are:
    1. Go to Traffic > Virtual > Orchestrated Flows and select your cloud platform. Then, click on the Threshold Template tab in the top navigation bar.
    2. Go to Traffic > Virtual > Orchestrated Flows and select your cloud platform. Select a Monitoring Session and click Actions > Edit. In the Edit Monitoring Session page, click Options > Threshold.
  2. The Threshold Template page appears. Click Create to open the New Threshold Template page.
  3. Enter the appropriate information for the threshold template as described in the following table.

    Field

    Description

    Threshold Template Name

    The name of the threshold template.

    Thresholds

    Monitored ObjectsSelect the resource for which you wish to apply the threshold template. Eg: TEP, REP, Maps, Applications like Slicing, Dedup etc
    Time IntervalFrequency at which the traffic flow needs to be monitored.
    MetricMetrics that need to be monitored. For example: Tx Packets, Rx Packets.
    Type

    Difference: The difference between the stats counter at the start and end time of an interval, for a given metric.

    Derivative: Average value of the statistics counter in a time interval, for a given metric.

    Condition

    Over: Checks if the statistics counter value is greater than the 'Set Trigger Value'.

    Under: Checks if the statistics counter value is lower than the 'Set Trigger Value'.

    Set Trigger ValueValue at which a traffic health event is raised, if the statistics counter goes below or above this value, based on the condition configured.
    Clear Trigger ValueValue at which a traffic health event is cleared, if the statistics counter goes below or above this value, based on the condition configured.
  4. Click Save. The newly created threshold template is saved, and it appears on the Threshold Template page.

Apply Threshold Template

You can apply your threshold template across the entire monitoring session and also to a particular application.

Apply Threshold Template to Monitoring Session

To apply the threshold template across a monitoring session, follow the steps given below:

  1. In GigaVUE‑FM, on the left navigation pane, select Traffic > Virtual > Orchestrated Flows and select your cloud platform. The Monitoring Session page appears.
  2. Select the monitoring session and click Actions > Apply Thresholds.
  3. The Apply Thresholds page appears. To apply a threshold template across a Monitoring Session, select the template you wish to apply across the Monitoring Session from the Threshold Template drop-down menu.
  4. Click Done.

Apply Threshold Template to Applications

To apply the threshold template to a particular application in the Monitoring Session follow the steps given below:

Note:  Applying the threshold template across Monitoring Session will not over write the threshold value applied specifically for an application. When a threshold value is applied to a particular application, it over writes the existing threshold value for that particular application.

  1. On the Monitoring Session page. Click Actions > Edit. The Edit Monitoring Session page with the canvas page appears.
  2. Click on the application for which you wish to apply or change a threshold template and click Details. The Application quick view opens.
  3. Click on the Thresholds tab. Select the template you wish to apply from the Threshold Template drop-down menu or enter the threshold values manually.
  4. Click Save.

Edit Threshold Template

To edit a particular threshold template follow the steps given below:

  1. On the Threshold Template page, Click Edit. The Edit Threshold Template page appears.
  2. The existing threshold templates will be listed here. Edit the templates you wish to modify.
  3. Click Save.

Note:  Editing a threshold template does not automatically apply the template to Monitoring Session. You must apply the edited template to Monitoring Session for the changes to take effect.

Clear Thresholds

You can clear the thresholds across the entire Monitoring Session and also to a particular application.

Clear Thresholds for Applications

To clear the thresholds of a particular application in the Monitoring Session follow the steps given below:

  1. On the Monitoring Session page. Click Actions > Edit. The Edit Monitoring Session page with canvas page appears.
  2. Click on the application for which you wish to clear the thresholds and click Details. The Application quick view opens.
  3. Click on the Thresholds tab. Click Clear All and then Click Save.

Clear Thresholds across the Monitoring Session

To clear the applied thresholds across a Monitoring Session follow the steps given below:

  1. In GigaVUE‑FM, on the left navigation pane, select Traffic > Virtual > Orchestrated Flows and select your cloud platform. The Monitoring Sessions page appears.
  2. Select the Monitoring Session and click Actions > Apply Thresholds.
  3. The Apply Thresholds page appears. Click Clear.

Note:  Clearing thresholds at Monitoring Session level does not clear the thresholds that were applied specifically at the application level. To clear thresholds for a particular application refer to Clear Thresholds for Applications