> 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/network-discovery.md).

# Network Discovery

The Network Discovery page allows you to configure and initiate discovery for supported network devices such as routers, switches, hubs, modems, printers, bridges, and access points. The discovery process uses supported network protocols, including SNMP, to identify devices and collect inventory, availability, performance, and monitoring information.

## **Initiate Network Discovery**&#x20;

The Network Discovery page has three tabs.&#x20;

**Discovery Details | Filters | Schedule**

### **Discovery**

The Discovery Details section provides the discovery profile, device information, credentials, agent details, and data collector details settings.

Discovery Details | **Profile and Discovery Information**

<table data-header-hidden><thead><tr><th width="128.44439697265625" valign="top"></th><th width="168.22216796875" 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. The profile name helps identify and track the discovery configuration.</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 Network discovery process.</p><ul><li>The Data Collector is installed within the customer's network and communicates with the target environment using the configured protocols and credentials.</li><li>It collects the required inventory, availability, and performance information and sends the data to Infraon for monitoring.</li></ul></td></tr><tr><td valign="top">Discovery Options</td><td valign="top">Select an option</td><td valign="top"><ol><li>Discover inventory with availability and performance monitoring. </li><li>Discover only Inventory Information.</li><li>Discover inventory with availability and performance monitoring.</li></ol></td></tr><tr><td valign="top">Discover only Inventory Information</td><td valign="top">Select an option</td><td valign="top">Discovers and collects basic inventory information about the selected devices or resources, such as device details, configuration, and hardware/software information. Availability and performance monitoring are not enabled.</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></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.</p><p> </p><p><strong>Example</strong>: For network devices, Routers &#x26; Switches only.</p></td></tr><tr><td valign="top">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">Import from CSV</td><td valign="top">Import a file</td><td valign="top">Import a device list from a CSV file instead of manually entering the IP address, IP range, or subnet. This option is optional.</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 Network Discovery.</p><p> </p><p>The credential contains the authentication and connection details IMS needs to communicate with network devices during discovery.</p><p>Select a credential that matches the protocol supported by the target device.</p><p> </p><p>For Network Discovery, the supported protocols are SNMP, SSH, and TELNET. The selected credential establishes connectivity and enables IMS to discover and collect information from network devices.</p></td></tr></tbody></table>

{% hint style="info" %}
Note: Fields marked with an asterisk (\*) are mandatory. Import from CSV and Device Credentials are optional.
{% 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%2FLyVsEhGI9dKDmM3PkWaJ%2Fimage.png?alt=media&amp;token=292b30e9-6aef-421f-ac9e-3e66a0247a24" alt=""><figcaption></figcaption></figure>

### Filters

The Filters section allows you to control which devices are included or excluded from discovery and which network components are monitored.

The Filters section contains four areas:

* Default Filters
* Device Filters
* Network Component Filters
* Port Monitoring

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

Filters | **Default Filters**

<table data-header-hidden><thead><tr><th width="146.22222900390625" valign="top"></th><th width="151.22222900390625" 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">Default Filters</td><td valign="top">View selected filters</td><td valign="top"><p>Displays the default filters selected for the discovery process.</p><p></p><p><strong>Example</strong>: 2 filters selected.</p></td></tr><tr><td valign="top">Filter By Ping</td><td valign="top">Enable or disable</td><td valign="top">Filters devices 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">Uses ping monitoring to check whether a device is reachable.</td></tr></tbody></table>

Filters | **Device Filters**

<table data-header-hidden><thead><tr><th width="204" valign="top"></th><th width="168.5555419921875" 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">Device Filters</td><td valign="top">Select a condition</td><td valign="top">Configure conditions to include or exclude devices 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">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 devices.</td></tr></tbody></table>

&#x20;The filter condition follows:

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

You can click the + icon to add additional filter conditions.

Network Component Filters

The Network Component Filters section allows you to select the network components and technologies that should be monitored for the discovered devices.

Filters | **Network Component Filters**

<table data-header-hidden><thead><tr><th width="145.33331298828125"></th><th width="170.888916015625"></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description / Example</strong></td></tr><tr><td>Interface</td><td>Enable or disable</td><td>Enables monitoring of network interfaces to view interface status and monitor network traffic, including incoming and outgoing data.</td></tr><tr><td>Interface Type</td><td>Select an option</td><td>Select the interface category to be monitored from the available dropdown options.</td></tr><tr><td>Interface Name</td><td>Select an option</td><td>Choose the specific network interface for which monitoring needs to be configured.</td></tr><tr><td>Sub Interface</td><td>Enable or disable</td><td>Includes sub-interfaces in monitoring to track their individual status and network activity.</td></tr><tr><td>Sub Interface Monitoring</td><td>Select an option</td><td>Select the required sub-interface monitoring option to specify which sub-interface details should be collected.</td></tr><tr><td>STP</td><td>Enable or disable</td><td>Monitors Spanning Tree Protocol (STP) information, helping track spanning tree status and topology changes in the network.</td></tr><tr><td>BGP</td><td>Enable or disable</td><td>Monitors Border Gateway Protocol (BGP) information, including peer status and routing details exchanged between network devices.</td></tr><tr><td>OSPF</td><td>Enable or disable</td><td>Monitors Open Shortest Path First (OSPF) information, including neighbor status and routing information.</td></tr><tr><td>EIGRP</td><td>Enable or disable</td><td>Monitors Enhanced Interior Gateway Routing Protocol (EIGRP) information, including neighbor relationships and routing details.</td></tr><tr><td>QoS</td><td>Enable or disable</td><td>Monitors Quality of Service (QoS) information to provide visibility into traffic prioritization and network service performance.</td></tr><tr><td>Jitter</td><td>Enable or disable</td><td>Tracks variations in packet delivery time, helping identify network instability that can affect real-time applications.</td></tr><tr><td>VRF</td><td>Enable or disable</td><td>Monitors Virtual Routing and Forwarding (VRF) instances to provide visibility into separate routing tables and their associated network details.</td></tr><tr><td>VLAN</td><td>Enable or disable</td><td>Monitors Virtual Local Area Networks (VLANs), including their configuration and operational details.</td></tr><tr><td>IPSec</td><td>Enable or disable</td><td>Monitors IPSec information, including tunnel status and related details, to help track secure network connections.</td></tr><tr><td>Wireless Controller</td><td>Enable or disable</td><td>Monitors wireless controller information, providing visibility into controller status and associated wireless network components.</td></tr><tr><td>VPC &#x26; VDC</td><td>Enable or disable</td><td>Monitors Virtual Private Cloud (VPC) and Virtual Data Center (VDC) information to provide visibility into their associated network resources.</td></tr><tr><td>Host</td><td>Enable or disable</td><td>Monitors host-related information, including host status and associated resource details.</td></tr></tbody></table>

&#x20;Filters | **Port Monitoring**

<table data-header-hidden><thead><tr><th width="113.3333740234375" valign="top"></th><th width="181.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">Port</td><td valign="top">Enable or disable</td><td valign="top">Enables monitoring of specific network ports during the discovery process. When enabled, IMS checks the configured ports to verify whether the associated services are reachable and available on the discovered device.</td></tr><tr><td valign="top">Port Monitoring</td><td valign="top">Select or enter the port to monitor</td><td valign="top"><p>Specifies the network port that IMS should monitor for the selected device or service. The selected port is checked during discovery to determine whether the corresponding service is reachable.</p><p></p><p><strong>Example</strong>: Port 80 for HTTP, 443 for HTTPS, or 22 for SSH.</p></td></tr></tbody></table>

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FmrzKZRFAYJGWdq0AGhip%2Fimage.png?alt=media&amp;token=6cdc40ee-55fd-4eb2-972b-15175b6baa34" alt=""><figcaption></figcaption></figure>

### Schedule

The Schedule section determines when the Network 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/network-discovery.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.
