| Icon | Icon Name | Full Description |
|---|---|---|
 |
Provisioned Device |
An administrator has provisioned the device, but the device has not yet communicated with ExtremeCloud IQ. This is an administrative state and does not reflect the actual connection status. To view the actual connection status, you must manually change the management state using the Actions > Change Manage Status > Managed Devices menu option. |
 |
Connected Device | Device is actively communicating with ExtremeCloud IQ. |
 |
Disconnected Device |
Device is not actively communicating with ExtremeCloud IQ. Cause: The device might be physically disconnected from the network or powered off. This condition also occurs if there are interruptions in the network between the device and ExtremeCloud IQ or when there are misconfigured firewalls or ACL rules. Action: Ensure the device is connected to the network and powered on, and ensure that communication can occur through logical barriers such as firewalls. |
 |
Simulated Device | Device is a simulated device, which possesses only simulated configurations, conditions, and traffic. By contrast, a real device has a physical presence on the network and consumes power and network resources. |
 |
Unknown State |
Device is in an unknown state. Cause: This condition can arise when the indicators are ambiguous, indeterminate, or appear contradictory due to other factors. Action: Begin general troubleshooting procedures to ensure that the device is powered, connected, and is responding to traffic and CLI commands. Ensure that the device is communicating appropriately with network services, such as NTP, DHCP, etc. |
 |
Old OS Personality (Inactive) | Device formerly used another OS persona, which is no longer active. The information in this record pertains to the device when it ran using this OS persona. |
 |
Configuration Audit Match | The network policy configuration matches the current running configuration. |
 |
Configuration Audit Mismatch |
The network policy configuration does not match the current running configuration. Cause: The Configuration Audit Mismatch icon is visible on devices between the time that network policy changes are saved and the time that the altered network policy is uploaded to the device. Action: Upload the network policy to the device. |
 |
Configured at Device Level | Device possesses a device-level configuration that is different from the configuration defined in the network policy. This is not an error condition, but this information can be useful when troubleshooting network behavior because device-level configurations supersede device templates and network policy configurations. |
 |
Device Update Unsuccessful |
Device did not accept the OS or configuration upload. Cause: There are many reason for an unsuccessful update, but the most common include network connectivity or connection status changes, or the device rejected the command it received. Action: Hover over the update message in the Updated column to view the reason message describing the likely error condition. Ensure that the device is properly powered, that there is appropriate network connectivity, and that common causes listed here are not the issue. |
 |
Managed by ExtremeIoT | Device is provisioned to function with ExtremeIoT. |
 |
Thread Commissioner Running | The AP is designated Commissioner in the IoT Thread network. |
 |
Monitoring Unassociated Clients | Device is using presence analytics to monitor client devices that are not associated to the network, such as passers by. |
 |
Switch Stack (Closed) | Device is a switch stack, but the stack is collapsed visually and displays as a single device. |
 |
Switch Stack (Open) | Device is a switch stack, and the stack is expanded visually to reveal stack members. |
 |
Switch Stack Warning |
One or more stack member switches is not associated to the master stack node. Cause: One or more member switches within a stack has lost connectivity to the master stack node. This can happen if the member switch is powered off, physically disconnected from the stack, or if there is an issue with the switch itself. Action: Ensure that the switch slot has power and that the stacking cables are properly connected. |
 |
RadSec Proxy Server | Device is acting as a RadSec proxy server. This service optimizes some authentication functions, especially for cloud authentication, such as cloud PPSK and cloud RADIUS. |
 |
Rogue AP Mitigation On | Device is actively mitigating a rogue access point. Refer to the information provided by your security management platform. |
 |
Sensor Mode - Interface Active | Device is functioning as a sensor and the monitoring interface is active and monitoring the RF environment. |
 |
Sensor Mode - Interface Inactive | Device is functioning as a sensor, but the monitoring interface is not active and is not monitoring the RF environment. |
 |
Swap for Real Device | Device is a simulated device that you can exchange for a real device. |
 |
Spectrum Intelligence | Device is functioning as a Spectrum Intelligence monitor, which monitors the RF environment and provides frequency and time domain graphs and heat maps. |
 |
VPN Server - Tunnel Up | Device is functioning as a VPN server and the VPN tunnel is up, healthy, and operating properly. |
 |
VPN Server - Tunnel Down |
Device is functioning as a VPN server, but the VPN tunnel is down. If the tunnel is administratively down, then this is not an error condition. Cause: If not administratively down, issues on the client side can cause the tunnel to go down. Additionally, if the client- and server-side configuration do not agree, then a tunnel cannot be built. Action: Consult the VPN troubleshooting tools in ExtremeCloud IQ. You can also ensure that the client device is connected to the network and that the tunnel configurations agree on both ends of the tunnel. |
 |
VPN Server - Tunnels Up and Down |
Some of the VPN server tunnels are administratively up but operationally down. Cause: VPN client might be down, or unreachable. Action: Ensure that the VPN clients are powered on, connected to the network, and communicating with ExtremeCloud IQ. In addition, ensure that there is connectivity and communication between the VPN server and clients. |
 |
VPN Client - Tunnels Up | Device is functioning as a VPN client and the VPN tunnel is up, healthy, and operating properly. |
 |
VPN Client - Tunnels Down |
Device is functioning as a VPN client, but the VPN tunnel is down. If the tunnel is administratively down, then this is not an error condition. Cause: If not administratively down, issues on the server side can cause the tunnel to go down. Additionally, if the client- and server-side configuration do not agree, then a tunnel cannot be built. Action: Consult the VPN troubleshooting tools in ExtremeCloud IQ. You can also ensure that the server device is connected to the network and that the tunnel configurations agree on both ends of the tunnel. |
 |
VPN Client - Tunnels Up and Down |
Some of the VPN client tunnels are administratively up but operationally down. Cause: VPN server might be down, or unreachable. Action: Ensure that the VPN server is powered on, connected to the network, and communicating with ExtremeCloud IQ. In addition, ensure that there is connectivity and communication between the VPN server and client. |
 |
Locally Managed (ExtremeCloud IQ) | Device is managed by a platform that is visible in ExtremeCloud IQ. |
 |
Locally Managed (No ExtremeCloud IQ) |
Device or its management platform are not visible in ExtremeCloud IQ. Cause: This is not always an error condition, but it can indicate a status communication problem. In this case, the device is functioning properly, so there is no disruption in network performance; instead, the status communication is disrupted so that ExtremeCloud IQ is unaware of the status. Action: First, ensure that the device is functioning properly to rule out problems with the device. Next, ensure that there are no logical barriers between the device and ExtremeCloud IQ. Afterward, ensure that any applications that lie in the communication path are receiving, processing, and sending data appropriately. |
 |
Extreme Cloud Appliance Cluster (Closed) | Device is a logical cluster of appliances, but the cluster is collapsed visually to appear as a single device. |
 |
Extreme Cloud Appliance Cluster (Open) | Device is a logical cluster of appliances, but the cluster is expanded visually to reveal the cluster members. |
 |
Fabric Attach | Device is a member of the Fabric Attach Connect Automation environment and is functioning properly in that context. |
 |
Fabric Attach Issue |
Device is Fabric Attach capable, but the Fabric Attach (FA) session to the FA server is not established. Cause: This can occur if the communication link between the FA device and server is disrupted or if FA is disabled on the peer switch. Action: Ensure that there is connectivity between FA device and server, and that FA server functionality is enabled on the peer switch. |
  |
Digital Twin | Device is a simulated device. |