Documentation forNetwork Performance Monitor
Monitoring network performance is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Essentials edition. Network Performance Monitor (NPM) is also available in a standalone module.

Monitor Ruckus One wireless infrastructure

Add Ruckus One orchestrator nodes for monitoring access points with interfaces, rogue access points, and clients for the wireless controller.

What does NPM monitor for Ruckus One infrastructure?

Monitored entity Metrics
Wireless Controller
  • Controller name
  • IP address
Access Point
  • Access point name
  • IP address
  • SSID
  • Channels (interface property)
  • MAC (interface property)
  • Radio type (interface property)
  • Clients count
  • Bandwidth utilization
Client
  • Client name
  • SSID
  • IP Address
  • MAC
  • Signal strength
  • Connected
  • Data transmitted/received
Rogue Access Point
  • SSID
  • MAC

Requirements

Limitations

  • Performance metrics, such as response time or availability, are polled via REST API authorization requests. As a result, the response times are longer than for other nodes, and thus using default thresholds might result in marking the node status as critical. To address this, customize the Response Time thresholds when adding the nodes.

Request frequency and limits

As of June 2024, the APIs used below have no rate limiting defined. See Ruckus One APIs.

API calls used for polling wireless access points

  API request Purpose
1 /oauth2/token/{Tenant} Login
2 /tenants/self Status poller (when all venues were selected)
3 /venues/{VenueIdentifier} Status poller (when a specific venue was selected)
4 /venues/aps Statistics collection poller - gets information on APs.
5 /venues/aps/{AccessPointIdentifier}/radioSettings Statistics collection poller - gets information on wireless interfaces.
6 /venues Statistics collection poller - gets a list of venues to get rogue APs when rogue APIs in all venues should be obtained.
7 /venues/{VenueIdentifier}/rogueAps/query Statistics collection poller - gets information on rogue APs.
8 /clients Statistics collection poller - gets information on clients.

Before you begin

Prepare your Ruckus One customer and client details. You will need this information when adding your Ruckus One infrastructure for monitoring.

Log in to the Ruckus One management console and gather the following details:

  • Region
  • Tenant ID
  • Client ID
  • Client Secret

See Ruckus One API for details about where to find the details.

Add Ruckus One wireless infrastructure to NPM

  1. Log in to the SolarWinds Platform Web Console as an administrator.

  2. Click Settings > Manage Nodes and click Add a Node.

  3. In Polling Method, select Orchestrators: API.

    The Polling Hostname or IP Address is disabled and Ruckus.com is used as the default host name.

  4. Select Ruckus One Devices and provide the following details:

    • Region - select an option from the dropdown
    • Tenant ID
    • Client ID
    • Client Secret
    • Base URL - filled in automatically, based on the selected region.

    When you fill in details, the Get Venues button becomes enabled.

  5. Click Get Venues and select a venue.

    • To monitor a particular venue, select it in the drop-down.
    • To monitor devices in all venues, select All venues.

    Polling Ruckus One uses the global HTTP proxy settings. To change the defaults, click the Configure your HTTP proxy link.

  6. Review and adjust the device properties.

    1. Review your Ruckus One user details, client details, and proxy settings.

    2. To edit how often the node status, or monitored statistics are updated, change the values in the Polling area.

      By default, Node Status is polled every 120 seconds and requires two requests - an authentication request and the status request. Statistics are polled every 10 minutes and require one authentication request and the following requests.

      • 1 request to get all APs and 1 request per AP to get radios
      • 1 request to get all rogue APs for a selected venue and 1 additional request if All venues are selected
      • 1 request to get all clients and 1 request per client to get additional details.

    3. Enter values for custom properties for the node.

      The Custom Properties area is empty if you have not defined any custom properties for the monitored nodes. See "Add custom properties to nodes" in the SolarWinds Platform Administrator Guide.

    4. To adjust when the status of the node changes to Warning or Critical, edit alerting thresholds for the metric. Select the Override box and set thresholds for the node.

      Response times for Ruckus One nodes might be 1-2 seconds. Consider adjusting the thresholds accordingly.

  7. Click OK, Add Node.

The Ruckus One device is now added as a node. After the first poll, you can see the data from the device in the SolarWinds Platform Web Console.

On the Manage Nodes view, click the added node to see the node details in the Wireless Controller view, or drill down into thin access points listed on the view. Check Node Details to verify that the Machine Type of the new device is RuckusOne Cloud Orchestrator.