Supervision Alarms by Layer
The table below lists the SD-WAN Orchestrator alarms by layer and briefly describes the recovery procedure to use when an alarm condition occurs.
As a reminder, layers are the following:
| • | Underlay: physical connection between devices (LAN, WAN), VRRP or HA state change, appliance configuration |
| • | Overlay: connection between appliances or external gateways through IPsec tunnels |
| • | Services: services provided with the appliances such as application visibility, application control, WAN optimization, firewall |
| • | EQS: site EQS for applications and site connectivity |
| • | Resources: device local resources, i.e. hardware monitoring |
| • | Management: connection to Azure components (Orchestrator, ZTP Server, etc.) |
Underlay
|
Alarm |
Severiy |
Troubleshooting |
|---|---|---|
|
Network interface down [interface name] |
Critical |
Check physical connections with the device. |
|
Bad network interface configuration [interface name] |
Critical |
Check the interface configuration parameters. |
|
No IP address [Transport Network Identifier name] |
Critical |
Define a correct IP address for the configured WAN interface. |
|
No default gateway [Transport Network Identifier name] |
Critical |
Define a default gateway for the configured WAN interface. |
|
VRRP state change |
Information |
Status change alarm. |
|
HA state change |
Information |
Status change alarm. |
|
Configuration mismatch |
Critical |
There is a configuration version mismatch between the SD-WAN Orchestrator and the appliances. Contact ExtremeCloud SD-WAN Support. |
|
HA Configuration mismatch |
Critical |
Check the information of the Event History window to identify the issue. Check the Routing section of the Troubleshooting window (by clicking the Fix your HA configuration. |
|
HA Peer unreachable |
Critical |
The HA connection may be broken due to an appliance reboot, an unplugged cable, a power failure or an incident on another client device (for example, port down on a switch). Contact ExtremeCloud SD-WAN Support. |
icon on the Network -> Configuration window) and verify the status of the HA appliances.Overlay
|
Alarm |
Severiy |
Troubleshooting |
|---|---|---|
|
Disconnected from the overlay |
Warning |
The specified site is fully isolated from the rest of the network (zero overlay tunnel). Check your appliance configuration and define at least one IPsec tunnel. |
|
Tunnel failure (appliance) |
Critical |
Refer to the Event History window to identify the issue. Check the Tunnels section of the Troubleshooting window (by clicking the Fix your appliance configuration. |
|
External tunnel failure (External Gateway) |
Critical |
Check the configuration of the external gateway connection. |
|
CloudMesh failure |
Critical |
Contact ExtremeCloud SD-WAN Support. |
|
EdgeSentry failure |
Critical |
Contact ExtremeCloud SD-WAN Support. |
|
LAN BGP peering failure |
Warning |
Check the Local Peer IP address in the LAN and the Site AS number. |
|
Connection to AWS failure |
Warning/Critical |
May be raised when the connection is being created. If the issue persists, check that the corresponding AWS resources (Customer Gateway and VPN connection) still exist and contact ExtremeCloud SD-WAN Support. |
|
Connection to Azure failure |
Warning/Critical |
May be raised when the connection is being created. If the issue persists, check that the corresponding Azure resources (local network gateway and vnet gateway connection or VPN sites and connections for Virtual WAN) still exist. Contact ExtremeCloud SD-WAN Support. |
|
Cloud gateway failure |
Critical |
Check that the cloud gateway still exists and prerequisites are met. |
|
Cloud account failure |
Critical |
Check the Cloud Access definition and contact your cloud account administrator. |
Services
|
Alarm |
Severiy |
Troubleshooting |
|---|---|---|
|
Visibility down |
Warning |
Contact ExtremeCloud SD-WAN Support. |
|
Control down |
Warning |
Contact ExtremeCloud SD-WAN Support. |
|
WAN Optimization down |
Warning |
Contact ExtremeCloud SD-WAN Support. |
|
Synchronization lost |
Warning |
Contact ExtremeCloud SD-WAN Support. |
|
DTI traffic overload |
Warning |
The number of DTI connections exceeds 95% of the maximum threshold of authorized connections. The alarm is cleared when this value decreases. |
|
Connection to the SYSLOG server is lost |
Warning |
Check network connectivity between the SYSLOG server and the appliance. |
EQS
|
Alarm |
Severiy |
Troubleshooting |
|---|---|---|
|
Site EQS for Top Applications dropped below 5 |
Warning |
The alarm is cleared when this value increases. |
|
Site EQS for High Applications dropped below 5 |
Warning |
The alarm is cleared when this value increases. |
|
End-to-end connectivity lost |
Warning |
Check end-to-end connectivity between Site A and Site B for the specified Transport Network (broken NAP). |
Resources
|
Alarm |
Severiy |
Troubleshooting |
|---|---|---|
|
Disk is almost full (<5% left) on the volume [volume name] |
Warning |
For hardware resource alarms, contact ExtremeCloud SD-WAN Support. |
|
Disk failure |
Warning |
|
|
Reboot |
Information |
|
|
Traffic overload |
Warning |
Throughput or the number of flows exceeds the capacity of the appliance, or packet loss occurs on Ethernet interfaces. Contact Extreme Networks Support. They will determine whether a more powerful appliance needs to be installed. |
Management
|
Alarm |
Severiy |
Troubleshooting |
|---|---|---|
|
Disconnected from Orchestrator |
Critical |
One or several SD-WAN platform components are disconnected (either never connected or not recently connected) from the Orchestrator. Contact ExtremeCloud SD-WAN Support. |
|
Connectivity with Orchestrator impaired |
Warning |
One or several SD-WAN platform components are disconnected (either never connected or not recently connected) from ZTP (Zero Touch Provisioning server). Contact ExtremeCloud SD-WAN Support. |