Device Management

Indicates an AFC issue with the selected device. Status options include Pending, Grace Period, and Spectrum Mismatch.

For more information, select the AFC status icon to open the AFC Wireless view of the selected 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.

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.

Device could not establish a connection to ExtremeCloud‌ IQ after the configuration update. Device configuration rolled back to the last known good connection and the Updated status column displays Device update failed.

Cause: This condition can arise when the indicators are ambiguous, unknown, 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.

Select the icon to open a pop-up window detailing the configuration changes that occurred since the last Update Devices operation.

• Audit tab — lists any modifications made since the previous configuration update.
• Delta tab — shows CLI commands that have changed since the previous update.
• Complete tab — shows all CLI commands (including the CLI commands in the Delta tab) that form a configuration file. ExtremeCloud IQ uses this file for the next configuration update. After a successful configuration update, the configuration in the Complete tab matches the 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.

Select the icon to open a pop-up window detailing the configuration changes that occurred since the last Update Devices operation. See the Configuration Audit Match icon description for details.

Cause: There are many reasons 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.

Select the icon to expand the device list view to include details for the switch stack members.

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.

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.

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.

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.

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.

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.

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.