> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/wireless-controller.md).

# Wireless Controller

The Wireless Controller discovery feature allows Infraon to discover wireless controllers and the access points they manage using the SNMP protocol. It collects controller and associated access-point information and can enable inventory, availability, and performance monitoring based on the selected discovery configuration.

The selected Data Collector uses the configured SNMP credentials to connect to the wireless controller and retrieve information through SNMP. After successful communication, Infraon collects details about the controller and the access points it manages, such as device identity, status, interfaces, and available performance metrics. Infraon then adds the discovered controller and associated access points to the inventory, applying availability and performance monitoring based on the selected discovery options.

## Initiate Wireless Controller Discovery

There are three tabs on the Wireless Controller page:

Discovery Details | Filters | Schedule

### Discovery Details

The Discovery Details section is used to provide the discovery profile, discovery options, device information, credentials, and agent details.

Discovery Details | **Profile and Discovery Information**

<table data-header-hidden><thead><tr><th width="166.66668701171875" valign="top"></th><th width="156.33331298828125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Profile Name*</td><td valign="top">Enter a name</td><td valign="top">Enter a name for the Discovery Profile. Discovery Profiles are used to save discovery preferences and identify profiles for tracking and periodic discovery.</td></tr><tr><td valign="top">Data Collector Details</td><td valign="top">Configure details</td><td valign="top"><p>Select the Data Collector to be used for the Wireless Controller discovery process.</p><p>The Data Collector is installed within the customer's network and communicates with the target environment using the configured protocols and credentials.</p><p>It collects the required inventory, availability, and performance information and sends the data to Infraon for monitoring.</p></td></tr><tr><td valign="top">Discovery Options</td><td valign="top">Select an option</td><td valign="top"><p>1.   Discover inventory with availability and performance monitoring. </p><p>2.   Discover only Inventory Information.</p><p>3.   Discover inventory with availability and performance monitoring.</p></td></tr><tr><td valign="top">Discover only Inventory Information</td><td valign="top">Select an option</td><td valign="top"><p>Discovers and collects basic inventory information about the selected devices or resources, such as device details, configuration, and hardware/software information.</p><p>Availability and performance monitoring are not enabled.</p></td></tr><tr><td valign="top">Discover inventory with availability monitoring</td><td valign="top">Select an option</td><td valign="top">Discovers inventory information and enables availability monitoring to check whether the device or resource is reachable and operational.</td></tr><tr><td valign="top">Discover inventory with availability and performance monitoring</td><td valign="top">Select an option</td><td valign="top"><p>Discovers inventory information and enables both availability and performance monitoring.</p><p>IMS checks device availability and collects performance metrics for ongoing monitoring.</p></td></tr><tr><td valign="top">Provide Profile Details</td><td valign="top">Enter details</td><td valign="top"><p>Add a brief description of the discovery profile and the Wireless Controllers to be discovered.</p><p>Example: Corporate Wireless Controllers.</p></td></tr><tr><td valign="top">Primary IP Address*</td><td valign="top">Enter IP details</td><td valign="top">Enter an IP address, IP range, or subnet to be discovered.</td></tr><tr><td valign="top">Secondary IP Address</td><td valign="top">Enter IP details</td><td valign="top">Enter the secondary IP address, if applicable, for the SD-WAN device or environment.</td></tr><tr><td valign="top">Device Credentials</td><td valign="top">Select a credential</td><td valign="top"><p>Create device credentials before performing Wireless Controller Discovery.</p><p>Select an SNMP credential containing the required authentication and connection details.</p><p>The selected credential enables IMS to communicate with the wireless controller and collect device and network information.</p></td></tr></tbody></table>

{% hint style="info" %}
Note: Import from CSV and Device Credentials are optional. Fields marked with an asterisk (\*) are mandatory.
{% endhint %}

Click Next to configure Filters.

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FYfKN9qMAMl2t7A2g1Z2C%2Fimage.png?alt=media&amp;token=458ab748-455a-4146-bf40-93f8582f052c" alt=""><figcaption></figcaption></figure>

### Filters

The Filters section allows you to control which Wireless Controllers are included or excluded from discovery and configure monitoring for specific network components.

The Filters section contains three areas:

* Default Filters
* Device Filters
* Network Component Filters

The Filters section is optional. You can click Next without configuring any filters.

Filters | **Default Filters**

<table data-header-hidden><thead><tr><th width="148" valign="top"></th><th width="177" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Filter By Ping</td><td valign="top">Enable or disable</td><td valign="top">Filters Wireless Controllers based on their response to a ping check.</td></tr><tr><td valign="top">Ping Monitor</td><td valign="top">Enable or disable</td><td valign="top">Enables ping monitoring to check whether the Wireless Controller is reachable.</td></tr></tbody></table>

Filters | **Device Filters**

<table data-header-hidden><thead><tr><th width="155.111083984375" valign="top"></th><th width="169.44439697265625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Label</td><td valign="top">Action</td><td valign="top">Description / Example</td></tr><tr><td valign="top">Device Filters</td><td valign="top">Select a condition</td><td valign="top">Configure conditions to include or exclude specific Wireless Controllers from discovery.</td></tr><tr><td valign="top">Include Devices / Exclude Devices</td><td valign="top">Select an option</td><td valign="top">Specify whether matching devices should be included in or excluded from discovery.</td></tr><tr><td valign="top">Filter Type</td><td valign="top">Select an option</td><td valign="top">Select the required filter type, such as IP Address, Device Type, or Device Name.</td></tr><tr><td valign="top">Equals / Contains</td><td valign="top">Select an operator</td><td valign="top">Select the operator used to match the specified value.</td></tr><tr><td valign="top">Number or Device Name</td><td valign="top">Enter a value</td><td valign="top">Enter the value used to identify the Wireless Controller.</td></tr><tr><td valign="top">+</td><td valign="top">Add a condition</td><td valign="top">Add additional filter conditions as required.</td></tr></tbody></table>

The filter condition follows:

Include Devices / Exclude Devices → IP Address / Device Type / Device Name → Equals / Contains → Number or Device Name

Filters | **Network Component Filters**

<table data-header-hidden><thead><tr><th width="144.44451904296875" valign="top"></th><th width="178" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Access Points</td><td valign="top">Enable or disable</td><td valign="top">Enables or disables Access Point Monitoring for access points managed by the Wireless Controller.</td></tr><tr><td valign="top">Host</td><td valign="top">Enable or disable</td><td valign="top">Enables or disables Host Monitoring for the Wireless Controller host.</td></tr></tbody></table>

Click Next to configure the Schedule.

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FK7M0kTU4xaAJHfA8U0Qn%2Fimage.png?alt=media&amp;token=5ad0e2cb-69b6-47a5-8cf1-ddc579d94aab" alt=""><figcaption></figcaption></figure>

### Schedule

The Schedule section determines when the Wireless Controller Discovery should be initiated. You can start the discovery immediately using Discover Now or configure a Discovery Schedule to run it at a specified date and time. To learn more, [click here](broken://pages/i6SE7zM6h63y3lyABGzq#schedule).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/wireless-controller.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
