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. ## 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 subnet, not VLAN ID. ## Interface Entity Fields you'll see: - `interfaceName` - e.g. `GigabitEthernet1/0/24` - `interfaceType` - `ethernet`, `wireless`, `virtual`, `loopback`, `tunnel`, etc. - `adminStatus` - `up` or `down` - operator-set - `operStatus` - `up` or `down` - actual current state - `linkSpeed` - in bps - `parentDeviceId` - the device that owns the interface - `description` - administrator-set port description (when populated) ### adminStatus vs operStatus | adminStatus | operStatus | Meaning | |...