Set up Instant On discovery
Connect an HPE Networking Instant On site so Scanopy can discover the switches and access points it manages, along with their ports and the links between them.
An Instant On site's portal holds an inventory of the devices it manages, including their ports and the uplinks between them. Pointing Scanopy at the site is how that inventory becomes hosts, interfaces, and physical links.
Beta
The Instant On integration is in beta. Data collection may be incomplete and the credential fields may change in a future release. Please report anything that looks wrong.
Unofficial API
Instant On has no published API. Scanopy reads the same endpoints the vendor's own application uses. They are unsupported and can change or stop working without notice, so Scanopy tracks them on a best-effort basis. Nothing here modifies your devices — it only reads.
Before you start
Instant On credentials are created under Assets > Credentials and can be pointed at Remote hosts.
Creating a credential, assigning it, and overriding it on an individual host work the same way for every integration — see Creating a credential, Where a credential applies, and Auto-assignment. This guide covers only what is specific to Instant On.
One credential covers a whole site, so assign it to one of the Instant On devices on that site. Scanopy reads the site through that device and creates the rest from what the site reports.
What gets discovered
On each scan, the daemon reads the site's inventory and client list:
| From the portal | Becomes |
|---|---|
| Site inventory (switches, access points, gateways) | Hosts, matched against existing hosts by IP |
| Each device's ports | Interfaces, with names, speeds and link state |
| Uplinks between devices | Physical links in L2 Physical |
Device class (SWITCH, ACCESS_POINT, …) | An Instant On Switch or Instant On Access Point service |
| Wired clients | The MAC on the port it is connected to |
A link the portal reports and the same link reported by a switch at its other end describe one cable rather than two.
Prerequisites
- The daemon host can reach
portal.instant-on.hpe.comandsso.arubainstanton.comover HTTPS. The devices themselves are not contacted for this data - A portal account with multi-factor authentication disabled — see below
Choosing a credential type
| Credential type | How it connects | Can be targeted at | Requires daemon |
|---|---|---|---|
| Instant On Portal AccountBeta | Connects to the Instant On cloud portal with a site account. | Remote hosts | 0.17.11 or later |
Instant On Portal Account
The daemon signs in to the cloud portal as a site account and reads the site's inventory through it.
Creating an account for Scanopy
Add a dedicated account for Scanopy with the read-only Viewer role rather than using your own administrator login:
- In the Instant On app or portal, open the site and go to Site management → Accounts managing this site
- Choose Add account, enter an email address for the Scanopy account, and assign the Viewer role
- Complete the invitation from that mailbox to activate the account
- Make sure multi-factor authentication is not enabled on it
Scanopy submits the account credentials directly and has nowhere to answer a second-factor challenge, so an account with MFA enabled cannot sign in.
| Field | Required | Default | Description |
|---|---|---|---|
| Authentication | |||
| Portal Account | Required | None | Email address of an Instant On portal account with access to the site. Add a dedicated account with the read-only Viewer role (Site management → Accounts managing this site) rather than using your own administrator login, and make sure multi-factor authentication is disabled on it — the sign-in cannot answer an MFA prompt. |
| PasswordSecret | Required | None | Password for that portal account. |
| Scope | |||
| Site | Optional | None | Limit the fetch to one Instant On site by name. Leave blank to read every site this account can see. Assign this credential to a single switch — each host it is assigned to fetches the whole site again. |
Leave Site blank to read every site the account can see. Setting it restricts the fetch to one site.
Verifying it works
- Run a discovery from Discover > Scan > Scheduled
- Open the scan session — the credential appears in the session's credential summary
- Check Assets > Hosts for the site's other devices, each carrying its model, serial and firmware
- Open L2 Physical and confirm the switches now show what they connect to
Troubleshooting
Sign-in fails with the right password
Multi-factor authentication on the account blocks it. Scanopy submits the credentials directly and cannot answer a challenge. Create a dedicated Viewer account with MFA disabled and use that.
The scan reports that the host is not in any site this account manages
The credential is assigned to a host that is not one of the site's Instant On devices. Reassign it to a switch or access point the portal lists.
Devices appear but have no ports
Access points report no port table — only switches do. If a switch shows no ports, the portal may have changed the shape of its response; please report it.
Duplicate work on a large site
Each host the credential is assigned to fetches the whole site independently. Assign it to one device per site.
For diagnosing credential loading and assignment from daemon logs, see Credential troubleshooting.
Set up UniFi discovery
Connect a UniFi Network Application controller so Scanopy can discover the switches, access points and gateways it manages, along with their ports and LLDP neighbors.
Set up Docker discovery
How Scanopy discovers Docker containers — the default local socket, plus using a socket proxy for restricted access or remote hosts.