VLAN & Subnet Inventory

See every VLAN, the ports that carry it, and the subnets behind it.

Scanopy reads VLAN tables from your switches over SNMP and links each VLAN to the subnets on it.

app.scanopy.net
Scanopy Physical (L2) view with an access point port selected, showing its speed, native VLAN, tagged VLANs, IP address, and neighbor port on the switch

Check a port’s VLANs without logging into the switch

Click any port to see the VLANs it carries and what’s on the other end.

app.scanopy.net
Scanopy Subnets list with each subnet’s type, site, CIDR, address utilization, and VLANs

Know which VLANs every subnet runs on

Each subnet lists the VLANs its hosts sit on, recalculated after every scan, and how many of its addresses are in use.

app.scanopy.net
Scanopy VLAN list grouped by site, with each VLAN’s number, subnets, last seen time, and tags

Every VLAN on every site, in one list

Each VLAN shows its number, the subnets on it, and when a scan last saw it. Filter by site or tag, and export the list to CSV or read it through the REST API.

Motala Kommun

IT department

Municipality - Sweden

"With over 800 switches in our network, keeping topology documentation up to date by hand is almost impossible. We needed automation, especially with NIS2 raising the documentation requirements. Scanopy keeps it current for us."
FAQ

Frequently asked questions

What does Scanopy need to discover VLANs?

SNMP read access (v1, v2c, or v3) to switches that support Q-BRIDGE-MIB, or Cisco VTP on Cisco switches. Add the SNMP credentials in Scanopy and the next scan reads the VLAN tables.

Does Scanopy change switch or VLAN configuration?

No. Scanopy is a documentation tool. It reads VLAN configuration from the switches and never writes to them.

Does the daemon need to sit on every VLAN?

Not for VLAN data, which comes from the switches over SNMP. To discover hosts on a subnet, the daemon needs to reach that subnet, either directly or through routing.

See it on your own network.

View live demo →