Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Apstra 5.1.0 User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Interface Flapping (Specific Interfaces) Probe

Release: Juniper Apstra 5.1
{}
Change Release
date_range 21-Mar-25

The Interface Flapping (Specific Interfaces) probe determines if specific interfaces are flapping and raises anomalies accordingly.

Probe Overview

If the number of times that the operational state of a specified interface changes is greater than a specified number (Threshold) over a specified amount of time (Duration), then the interface is flapping and an anomaly is raised. Also, if the percentage of flapping interfaces exceeds the specified percentage (Max Flapping Interfaces Percentage), then an anomaly is raised for that device. You can select individual interfaces by system and link names, or (as of Apstra version 5.1.0) you can take advantage of tags and select multiple interfaces simultaneously based on system and link tags. Any interfaces with those tags will be subject to the probe.

Probe Parameters

When you instantiate the predefined Interface Flapping (Specific Interfaces) probe you can customize the above mentioned parameters or leave default values as is, as shown in the screenshot below. Of course, you'll need to add at least one interface before the probe can collect data; you can add it during instantiation or after.

Probe Stages

The following stages are used in the interface flapping probe for specific fabric interfaces:

The sections below discuss the stages in detail.

Device Interface Status Processor

Device Interface Status Service Collector (Input)

We begin with the source processor (no inputs), which is a Service Collector configured to collect interface status telemetry for selected device interfaces, as shown in the screenshot below.

Device Interface Status (Output)

This processor keeps track of when the operational state (up, down) of the interface changes. It collects and outputs this information as device interface status (device_if_status). Each interface is identified by its system ID and interface name. Operational state and a few other details are included in the output as shown in the list below:

  • System ID - ID of the leaf device, usually the serial number

  • Interface - name of the interface

  • Remote Interface - interface name on the other end (new in Apstra version 5.1.0)

  • Remote System Label - the device name on the other end (new in Apstra version 5.1.0)

  • Value - operational state of the device (up, down)

  • Updated - when the state was last updated

The following screenshot is an example of the details that are collected from this processor.

Device Interface Status History Processor

Device Interface Status History Collector (Input)

For this stage, the Accumulate processor is configured for collecting device interface status history as shown in the screenshot below.

Device Interface Status History (Output)

Device Interface Flapping Processor

Device Interface Flapping Collector (Input)

Interface Status Flapping (Output)

Percentage Flapping per Device Interfaces Processor

Percentage Flapping per Device Interfaces Collector (Input)

Flapping Device Interface Percentage (Output)

System Anomalous Flapping Processor

System Anomalous Flapping Collector (Input)

System Flapping(Output)

footer-navigation