Devices
Supported vendors
The vendors ITVA supports, and the protocol and port ITVA uses to connect to each one.
ITVA connects to each device with the protocol that the device's vendor supports. Use this page to find the protocol and port for your device before you add it.
Protocols at a glance
| Protocol | Default port | Used by |
|---|---|---|
| SSH | 22 | Switches, routers, Linux servers, and SonicWall firewalls |
| HTTPS (web management API) | 443 | Fortigate, Palo Alto, and Infoblox |
| Remote PowerShell (WinRM) | 5986 (HTTPS, recommended) or 5985 (HTTP) | Windows Server |
| SNMP | 161 | Cisco Business |
| Controller API key | None | Cisco Meraki and Ubiquiti |
For every protocol except the controller API, the probe connects to the device. Make sure the probe host can reach the device on the port in the table.
Supported vendors
The names in this table are the options in the Vendor list when you add a device.
| Vendor | Protocol | Default port |
|---|---|---|
| Arista | SSH | 22 |
| ArubaOS-CX | SSH | 22 |
| Brocade NOS | SSH | 22 |
| Cisco Business | SNMP | 161 |
| Cisco IOS-XE | SSH | 22 |
| Cisco IOS-XR | SSH | 22 |
| Cisco Meraki AP | Controller API key | None |
| Cisco Meraki Switch | Controller API key | None |
| Cisco NX-OS | SSH | 22 |
| Dell EMC | SSH | 22 |
| D-Link | SSH | 22 |
| Fortigate | HTTPS | 443 |
| HP ProCurve | SSH | 22 |
| Infoblox | HTTPS | 443 |
| Juniper | SSH | 22 |
| Linux Debian | SSH | 22 |
| Linux RHEL | SSH | 22 |
| Linux Ubuntu | SSH | 22 |
| MikroTik RouterOS | SSH | 22 |
| Nvidia Onyx | SSH | 22 |
| Palo Alto | HTTPS and SSH | 443 (SSH: 22) |
| Ruckus FastIron | SSH | 22 |
| SonicOS6 (SonicWall) | SSH | 22 |
| SonicOS7 (SonicWall) | SSH | 22 |
| Windows Server | Remote PowerShell | 5986 |
Set the management port
ITVA connects on the port in the device's Management Port field. The default is 22. If the device uses a different protocol or port, change this field when you add the device.
- SSH: Use 22, or the port that you set for SSH on the device.
- HTTPS: Use 443, or the port of the device's web management interface.
- Remote PowerShell: Use 5986 for HTTPS (recommended) or 5985 for HTTP. The probe uses HTTPS only when the port is 5986.
- SNMP: Use 161, or the SNMP port that you set on the device.
Controller-based vendors
Cisco Meraki and Ubiquiti devices are managed through a cloud controller. ITVA connects to the controller's API with an API key, not to each device. The ITVA platform makes these calls directly, not through the probe.
When you add a controller, ITVA adds all of the controller's devices for you, so you do not add them one at a time.
Cisco Meraki
- In the portal, go to Inventory > Controllers.
- Add a controller, and enter a Name for it.
- In Vendor, select Cisco Meraki.
- In Credential, select or create an API Key credential with your Meraki API key.
- In Metadata, add the key
organization_idwith your Meraki organization ID. - Select Save.
Ubiquiti
- In the portal, go to Inventory > Controllers.
- Add a controller, and enter a Name for it.
- In Vendor, select Ubiquiti.
- In Credential, select or create an API Key credential with your Ubiquiti API key.
- Select Save.