# Supported Devices

> How to read the device reference, and what each field means.

This section is the reference catalog of every device, hypervisor, database, and cloud platform Visual One Intelligence can collect from. Each entry lists the device type used internally by Visual One, the minimum role or permissions needed, the default network ports, the collection method, and the connection parameters required to configure it.

It is a reference rather than a walkthrough. If you are setting up collection for the first time, start with [Quick Start](https://visualoneintelligence.com/docs/quick-start/), then come back here for the specifics of your hardware.

## How to read an entry

| Field | What it means |
| --- | --- |
| Device type | The identifier Visual One uses for this collector. Where a platform lists a primary and a legacy type, choose the primary one for new deployments. |
| User role | The minimum role or privilege the credential needs on the device. Named roles are given in the platform's own terminology. |
| Default ports | The ports the collector uses unless overridden. Where two collection methods exist, the alternate method's port is noted. |
| Collection method | How the data is retrieved: a device API, SSH or CLI, WMI, a vendor CLI tool, or a direct database query. |
| Required parameters | Values that must be supplied. Watch for platforms that reuse a standard field for something else, such as an API key held in the Password field. |
| Optional parameters | Values needed only in specific circumstances, such as a non-default port or an extra token for file data. |
| Notes | Prerequisites, version requirements, and platform-specific behavior worth knowing before you configure it. |

> **Note:** Some collectors require additional software on the data collection machine, such as a vendor CLI, an ODBC driver, or a Python SDK. Where that applies it is called out in the entry's Notes, and it is the most common reason a correctly configured device still fails to collect.

## The sections

- [Storage, Backup and Hyperconverged](https://visualoneintelligence.com/docs/supported-devices-storage/): arrays, backup platforms, and hyperconverged systems, from Cohesity through Veeam.
- [Virtualization](https://visualoneintelligence.com/docs/supported-devices-virtualization/): VMware and vSAN, Nutanix, Hyper-V and SCVMM, and IBM HMC.
- [Standalone Servers](https://visualoneintelligence.com/docs/supported-devices-servers/): Windows and Linux hosts.
- [Switches](https://visualoneintelligence.com/docs/supported-devices-switches/): Brocade and Cisco Fibre Channel switches.
- [Cloud](https://visualoneintelligence.com/docs/supported-devices-cloud/): AWS, Azure, and GCP.
- [Databases](https://visualoneintelligence.com/docs/supported-devices-databases/): Oracle, MSSQL, MSSQL over ODBC, and DB2.
- [File Analytics](https://visualoneintelligence.com/docs/supported-devices-file-analytics/): file system metadata collection.

## A note on collectors marked for consultation

A few entries carry a note asking you to contact Visual One before deploying that collector. Those are supported but lightly deployed, so they may need adjustment for your environment. It is worth a conversation before you build a reporting dependency on one.

---

Source: https://visualoneintelligence.com/docs/supported-devices-overview/