VPNs And Network Tools
Choose where private routes and trap listeners run.
VPN Connections and SNMP Trap Listeners run on a managed Go network agent or a compatibility Site Collector; Panel Server execution is available only when your organization has that capability. Choose the host that can reach the target network. Configure profiles in Sysavia; saving a profile does not start it. Open the saved profile to start it and review its reported state. Stop it before editing or deleting it.
For a managed agent, open Agents → Configure, choose This Network or Both, and enable VPN management or trap listeners. Add each destination device or trap source to Permitted Network Devices. A collector must explicitly allow the relevant capability. If VPN management or trap receiving is disabled for that collector, the profile reports the capability denial instead of attempting a connection. An offline collector cannot apply a requested change until it reconnects.
VPN Connections
- Open VPN Connections and choose + VPN Connection.
- Name the connection and choose Run On.
- Select WireGuard or OpenVPN and paste the connection profile supplied by your VPN administrator.
- For OpenVPN, supply any required username/password and the private networks to route.
- Save, open the profile and start it. Review the status before assigning monitoring through that execution host.
Private keys, imported profile contents and passwords are encrypted at rest and omitted from editor responses. Leave the profile/password fields blank to retain saved values; paste replacement values when changing them. Native-agent VPN execution requires Linux. The execution host must have the selected VPN tooling installed and permission to manage network interfaces. VPN configuration is performed by Sysavia after that platform prerequisite.
Management VPNs accept private network routes only. Default routes, arbitrary scripts, plugins, executable hooks and external credential file references are rejected. OpenVPN credentials and certificates must be supplied through the panel/profile rather than referencing server filesystem paths. This is a constrained management tunnel feature, not a general-purpose importer for every vendor-specific VPN profile.
SNMP Trap Listeners
- Open SNMP Trap Listeners and choose + Trap Listener.
- Name the listener, choose Run On, and enter its bind address and UDP port.
- Add the exact sender IP addresses the listener should accept.
- Configure communities for SNMPv1/v2c or authenticated SNMPv3 users.
- Add event mappings for the trap OIDs you need. A mapping can set a Trap State Check, emit a named custom event, and publish selected numeric varbinds as metrics.
- Save and start the listener. Configure the equipment to send traps to that host's reachable address and selected port.
Use a separate recovery mapping to return a check to Up. Silence does not prove recovery; a trap check retains its last received state. For periodic health confirmation, combine trap events with a polling check. Unmapped accepted traps expose their source and OID, allowing you to identify which mapping is needed without publishing arbitrary payload text.
The listener defaults to port 1162. If equipment sends to the conventional port 162, change the equipment destination port or configure an appropriately permitted listener on 162. Status shows accepted, rejected, unmapped and dropped counts. A port already in use produces an explicit error. See SNMP Trap Receivers for protocol support, mapping semantics and resource limits.
Persistence And Conflicting Edits
Profiles are stored separately from the workspace, encrypted with the same server key used for private connection data. Sysavia manages storage and backups for the hosted service. Reopening an editor retrieves ordinary settings and secret-presence indicators, not stored secrets. Editing an outdated version is rejected; reopen it to load current settings. Active profiles cannot be edited or removed until stopped.
Verify Agent Access
Check the agent’s capability report before starting. VPN tools or ipmitool marked unavailable must be installed on the execution host. Applied configuration confirms receipt, not device reachability. Use a real check through the agent to verify the route. For native agents, loss of panel contact for 30 seconds begins shutdown of managed network resources. See Install The Native Agent for platform requirements and lifecycle details.