A cloud-deployed collector requires a private, routable connection to the internal networks and devices it monitors.
Recommended connectivity
Use a site-to-site VPN or private link between the collector’s network and the on-premises network.
The connection must allow the collector to reach the management IP addresses of the devices being monitored.
Required traffic
Allow traffic from the collector to managed devices as required by the monitoring services in use:
- ICMP for reachability and path testing.
- UDP 161 for SNMP polling.
- TCP 22 for SSH.
- TCP 23 for Telnet, if used.
- TCP 80 or 443 for HTTP or HTTPS polling, if used.
Restrict access where possible:
- Source: the collector’s IP address or subnet.
- Destination: the IP addresses of managed devices.
- Services: only the protocols required for monitoring.
Ensure return traffic is permitted and that the device management IP addresses remain stable.
SNMP configuration
- Configure valid SNMPv2c or SNMPv3 credentials on the devices.
- Add the matching SNMP credentials in Auvik.
- Allow the collector’s source IP in the devices’ SNMP access lists.
- Confirm UDP 161 is permitted between the collector and the devices.
- Test SNMP reachability from the collector.
- Run a discovery scan or SNMP credential test in Auvik.
NAT and port forwarding
Direct private connectivity is recommended for internal discovery.
NAT, proxy devices, and port-forwarding configurations can:
- Prevent the collector from reaching the device’s actual management IP.
- Cause multiple devices to appear behind one address.
- Interfere with device identification and topology mapping.
- Produce incomplete or inconsistent SNMP data.
If NAT cannot be avoided, confirm the design with Auvik Support before configuring discovery. Do not assume that forwarding a unique external port to UDP 161 will provide the same results as direct private connectivity.
Topology discovery
For the most complete topology information, ensure the collector can retrieve the required data from managed switches and network devices, including:
- LLDP or CDP neighbor information.
- Forwarding database or MAC-table information.
- Interface and VLAN data.
Missing or restricted SNMP views may result in incomplete topology information even when basic SNMP polling succeeds.
Troubleshooting
If devices are not discovered or are identified incorrectly:
- Verify the VPN or private-link path.
- Check firewall and ACL rules for UDP 161 and other required polling protocols.
- Confirm the device responds to SNMP from the collector.
- Check for packet loss, MTU issues, or asymmetric routing.
- Confirm intermediate firewalls are not rewriting or blocking SNMP traffic.
- Verify that the collector’s source IP is the address allowed by the device.
SNMP traps are not required for this discovery workflow.
Network routing, VPNs, NAT, firewall rules, ACLs, and device SNMP configuration may require assistance from a network administrator.