Feature Overview

The Client Connectivity Troubleshooting Sub-agent is an AI-driven troubleshooting component in RUCKUS One that analyzes wireless client connectivity issues and provides root cause analysis with recommended actions. It evaluates telemetry, configuration logs, and packet capture (PCAP) data to identify potential causes of client failures and generate diagnostic reports.

You interact with the agent through the Digital System Engineer (DSE) chat interface by submitting a query that includes the client MAC address and the relevant time range for the issue. The system processes the request, performs data analysis, and returns a report that includes likely causes, diagnostic details, and recommended actions.

The troubleshooting process uses multiple data sources to analyze client behavior and supports common failure scenarios such as authentication, association, DHCP, EAP, and RADIUS issues. The agent groups failures into clusters and evaluates them to identify patterns and probable root causes.

This feature streamlines troubleshooting workflows by eliminating the need to manually review logs, historical records, and packet captures. Reports are generated automatically and can be accessed within the DSE interface after processing is complete.

Requirements

The following conditions are required to use the Client Connectivity Troubleshooting Sub-agent:

• Access to RUCKUS One and the Digital System Engineer (DSE) interface is required.
• Your RUCKUS One tenant account must have the Professional subscription tier. You can check this on theAdministration > Account Management > Subscriptions page.
• Your RUCKUS One user account must be assigned to one of the following system-defined privilege groups: Prime Admin or Administrator. Custom groups are not supported.

Considerations

Consider the following when using the Client Connectivity Troubleshooting Sub-agent:

• Troubleshooting is limited to events that occurred within the supported analysis time window.
• Processing involves large data evaluation and may take additional time to generate results.

Limitations

The following are limitations of the Client Connectivity Troubleshooting Sub-agent:

• The agent requires a client MAC address and cannot initiate troubleshooting without it.
• Analysis is limited to supported event types, including authentication, association, DHCP, EAP, and RADIUS scenarios.
• The agent can analyze issues that occurred only within the last 24 hours.

Best Practices

Consider the following recommendations when using the Client Connectivity Troubleshooting Sub-agent:

• Provide an accurate client MAC address and time range to improve analysis accuracy.
• Use narrower time ranges to focus on specific failure clusters.
• Review the generated RCA report to understand causes and recommended actions.
• Use the agent to complement, rather than replace, detailed troubleshooting workflows when required.

Prerequisites

The following prerequisites apply before you use the Client Connectivity Troubleshooting Sub-agent:

• Ensure access to RUCKUS One and the DSE chat interface.

• Ensure your RUCKUS One user account is assigned to one of the following system-defined privilege groups: Prime Admin or Administrator. Custom groups are not supported.

• Ensure availability of client identifier (MAC address) and relevant incident time range.