- play_arrow Get Started
- play_arrow Organization Management
- Organization and Sites Overview
- Add an Organization
- Delete an Organization
- Manage Organization Settings
- Authentication Methods Overview
- Manage Identity Providers
- Manage Roles
- Manage API Tokens
- Configure Webhooks to Receive Event Notifications in Third-Party Applications
- Integrate Your Juniper Support Resources to Your Organization
- play_arrow Site Management
- play_arrow User Management
- play_arrow Inventory Management
- play_arrow Audit Logs
- play_arrow Licensing
- play_arrow Marvis VNA for Data Center
- play_arrow Monitor and Troubleshoot Data Center Events
- play_arrow Service Awareness
- play_arrow Service Level Expectations
- play_arrow Alerts
- play_arrow Help & Support
Key Anomalies in Impact Analysis
Understand the key anomalies listed in Impact Analysis.
The Impact Analysis feature displays anomalies that are detected within the Data Center network with the help of predefined IBA probes. On a Juniper Apstra instance, an IBA probe takes a set of data from the network, performs aggregations and calculations on it, and raises an anomaly if specific conditions are not met. This information is sent to the Juniper Apstra Edge device which further passes on the data to Juniper Apstra Cloud Services. The Impact Analysis feature determines the key anomaly and its associated anomalies from this data. It also pulls reports on the services and clients affected by the key anomaly and displays comprehensive information in the Impact Analysis page of the Juniper Apstra Cloud Services UI. This feature enables the network administrator to quickly identify and resolve the root cause of an anomaly, thus reducing the impact on the network.
You must enable IBA probes on the Juniper Apstra instance in order to detect anomalies in the network. For more information, see Instantiate Predefined Probe in the Juniper Apstra User Guide.
The tables below list key anomalies displayed in the Anomalies tab on the ACS UI and the IBA probes that raise the anomalies detected in the network.
Table 1 lists key anomalies that are detected on the devices in the network.
Table 2 lists key anomalies that are detected on the interfaces of any given device in the network.
Table 3 lists key anomalies that you can create and enable if required in your organization.
| Key Anomaly | Description | IBA Probe |
|---|---|---|
Fan Missing | Indicates that the number of fan trays for a device is less than expected. | Device Environmental Checks |
Fan Status | Indicates that the fan state is not as expected. | Device Environmental Checks |
Power Supply Missing | Indicates that the number of operational power supplies (PSUs) on a device is less than expected. | Device Environmental Checks |
Power Supply Status | Indicates that the power supply status is not as expected. | Device Environmental Checks |
Device CPU | Indicates that the CPU usage has exceeded the specified threshold for the specified duration. | Device System Health |
Device Disk | Indicates that the disk usage has exceeded the specified threshold for the specified duration. | Device System Health |
Device Memory | Indicates that the memory usage has exceeded the specified threshold for the specified duration. | Device System Health |
Drain Node | Indicates excess traffic on a node that is being drained. | Drain Traffic Anomaly |
| Key Anomaly | Description | IBA Probe |
|---|---|---|
Cold Leaf Interface | Indicates that the traffic average for each spine-facing interface on a leaf is less than the acceptable range. | Hot/Cold Interface Counters (Fabric Interface) |
Hot Leaf Interface | Indicates that the traffic average for each spine-facing interface on each leaf is higher than the acceptable range. | Hot/Cold Interface Counters (Fabric Interface) |
Cold Specific Interface | Indicates that the average counter value of the specific interface is lower than the threshold value. | Hot/Cold Interface Counters (Specific Interface) |
Hot Specific Interface | Indicates that the average counter value of the specific interface is higher than the threshold value. | Hot/Cold Interface Counters (Specific Interface) |
Fabric Interface | Indicates that the interface has changed states (flapped) more than the configured threshold. | Interface Flapping (Fabric Interface) |
Host Facing Interface | Indicates that the specific host-facing interface has changed states (flapped) more than the configured threshold number in recent history. | Interface Flapping (Specific Interface) |
Optical Transceiver | Indicates that the optical interface has crossed at least one threshold. | Optical Transceivers |
Cabling Problem | Indicates an error with cabling. | Service Anomaly |
L2 Interface to Server | Indicates a service anomaly in the L2 external server-facing interfaces. | Service Anomaly |
L3 Interface to Server | Indicates a service anomaly in the L3 external server-facing interfaces. | Service Anomaly |
Link Status Mismatch | Indicates a discrepancy in the link status. | Service Anomaly |
| Key Anomaly | Description | IBA Probe |
|---|---|---|
Device Cold Anomalous | Indicates that the percentage of cold interfaces on a specific device is higher than the acceptable range. | Hot/Cold Interface Counters (Fabric Interface) Hot/Cold Interface Counters (Specific Interface) |
Device Hot Anomalous | Indicates that the percentage of hot interfaces on a specific device is higher than the acceptable range. | Hot/Cold Interface Counters (Fabric Interface) Hot/Cold Interface Counters (Specific Interface) |
