auvik-networks

# Auvik Networks and Interfaces A `network` in Auvik is an IP scope - typically a subnet that Auvik has discovered devices on. An `interface` is a port on a device. Both are distinct entity types with their own list endpoints. This skill clarifies the data model and the relationships. ## Anti-triggers - **A Meraki "network"** — in the Meraki Dashboard a network is a site container holding devices, not an IP scope. The word collides completely; use `meraki-devices`. - **Scanning a subnet, mapping topology, or chasing an IP conflict** — those run from a collector inside the LAN, not from Auvik's polled read model; use `domotz-network`. - **Changing a VLAN or shutting a port** — Auvik reads `adminStatus` and never sets it. On Meraki switches that write lives in `meraki-devices`. ## Tools | Tool | Use For | |------|---------| | `auvik_networks_list` | List networks for a tenant | | `auvik_networks_get` | Detail for one network | | `auvik_interfaces_list` | List interfaces for a tenant | ## Network Entity Fields you'll see: - `networkName` - usually the subnet in CIDR form - `networkType` - `private`, `internet`, `unknown` - `scanStatus` - whether discovery scans for this network are healthy - `gatewayIp`, `dhcpEnabled` - `description` - free-form, often blank Networks are not VLANs in the Auvik model - VLAN information lives on interface records and switch configurations. A single VLAN typically maps to a single network, but the network entity is keyed on sub...