AnvesionTech Book a demo

SNMP network monitoring · NMS See the network behind your endpoints.

DeviceManager's network device monitoring watches routers, switches, firewalls, access points, printers, UPS units, cameras and storage — agentless over SNMP, in the same self-hosted console as your endpoints, without using a licence seat.

Book a demo How discovery works
  • SNMP v1 · v2c · v3
  • Agentless
  • No licence seat
  • Self-hosted

Coverage

Everything that can't run an agent, in one inventory.

Network devices sit beside your managed endpoints in DeviceManager, but never on the Devices page and never on your licence count. Each one gets a NET number, a live status and a full history.

60 sstatus poll interval
65,536IPv4 addresses per scan
50config versions kept per device
0licence seats used by network devices
dm.yourcompany.local/network-devices
DeviceManager Network Devices list for SNMP network monitoring: stat cards for total, up and credential failures, filters by type, vendor and subnet, and a router and firewall with NET IDs, uptime and High identity 12 of 14 up NET-01062 · identity High
  • Routers
  • Switches
  • Firewalls
  • Access points
  • Wireless controllers
  • Printers
  • UPS units
  • PDUs
  • IP cameras
  • Storage systems

Discovery

Scan once. Know exactly what answered.

Scans probe your ranges with SNMP credential profiles, then recognise each device by its hardware — never by its address.

01 · Targets

Point it at your ranges.

CIDR blocks, ranges and single IPv4 addresses — up to 65,536 per scan, with exclusions. Run it now or on a schedule from every 15 minutes to weekly.

02 · Credentials

Tried in order, never sent out of scope.

SNMP v1, v2c and v3 profiles are tried by priority. A scoped profile is only ever sent inside its subnets, so nobody can aim a scan at a laptop to harvest community strings.

03 · Identity

Known by what it is, not where it sits.

Every device is recognised by chassis serial, base MAC or SNMP engine ID and gets a NET number. The IP is never identity, so a device that moves keeps its record.

04 · Change

Conflicts flagged. Replacements caught.

Matching identifiers on two records are flagged, never merged automatically. New hardware at an old address is marked “possibly replaced by”, with asset and open incidents ready to transfer.

Topology map

A network topology map drawn by the network itself.

Enable LLDP — or CDP on Cisco equipment — and re-scan. The Map tab draws your network from the neighbour tables it read.

01 · LLDP & CDP

Links come from the devices themselves.

Each scan reads the LLDP and CDP neighbour tables of your switches and routers. Every adjacency becomes a link, with port labels when you want them.

02 · Layout

Routers on top, or however you think.

Choose Auto, Hierarchical or By connections, then drag nodes where you like — positions are remembered in your browser. Fit, refresh or export the map as PNG.

03 · Status

Trouble is coloured in.

Down devices and links are coloured, refreshed every 30 seconds. Unmanaged neighbours show what they advertise, with Scan this IP to bring them under management.

04 · In the console

One click from map to details.

Select any device to open its details: interfaces, neighbours, recent traps, configuration backups and status history.

Status & incidents

Polled every minute. Tickets that open and close themselves.

Every device with working credentials is polled over SNMP every 60 seconds. Each change lands in its status history — and, with automatic incident sources on, in your incident queue.

FL2-SW-01NET-01064 · 10.30.2.10 · SNMP poll every 60 s
Up Down

Sixteen status polls, one per minute from 13:00 to 13:15: the polls from 13:05 to 13:13 were missed and the device answered again at 13:14.

Status history

  • Missed poll 1 of 3
  • Down — no answer to three polls
  • Down 5 min — incident opened
  • Back up — answered the poll

Automatic incident

Network Device Down WatchingOpenClosed automatically

Opens when a device misses polls for 5 minutes (default) and closes when it answers again.

Also: Network Interface Down · Printer Supply Low

Up
Answered the poll
Down
Three missed polls in a row
Rebooted
Uptime went backwards
Credential failure
SNMPv3 login rejected, still listed

Watch the ports that matter

Watched uplinks, server and firewall ports raise an interface-down event when they drop while administratively up. Access ports stay unwatched — they flap all day.

  • Gi1/0/1Uplinkup
  • Gi1/0/14Server portdown · event
  • Gi1/0/22Access portdown · ignored

Printer supplies

Printer toner monitoring, before the tray runs dry.

Every toner, drum, ink and waste container is read by scans and refreshed hourly. With Printer Supply Low switched on, a ticket opens at 10% by default — and closes itself when the supply is replaced.

  • Above 20%
  • 10 – 20%
  • Below 10% or empty
FL2-PRN-01NET-01066 · Floor 2 · Supplies
Up
  • Black toner8%
  • Cyan toner72%
  • Magenta toner17%
  • Yellow toner54%
  • Drum unit81%
Watching · ticket opens at 10% Printer Supply Low · Black toner · ticket open Toner replaced · ticket closed automatically

Configuration backup

Network configuration backup, every change in view.

Back up running configurations over SSH — or Telnet, where you allow it — on demand or daily. A new version is stored only when the configuration really changed; time stamps and counters are ignored.

Changes · 07 Oct → 14 Oct+4 −2 lines
11 hostname CORE-SW-01
22 !
33 snmp-server location Data Centre, Rack A2
44 ntp server 10.20.0.10
5-logging host 10.20.0.14
5+logging host 10.20.0.15
6+logging trap informational
67 !
78 interface GigabitEthernet1/0/14
8- description CAM-FL2
9+ description CAM-FL2-LOBBY
10+ power inline static
911 !
1012 end

Command sets

  • Cisco IOS · IOS-XE · NX-OS
  • Cisco ASA
  • HPE Aruba / ProCurve
  • Juniper Junos
  • MikroTik RouterOS
  • Fortinet FortiOS
  • Others: show running-config
  • Changes view compares any version with the one before it.
  • Encrypted in the database; every view and download audited.
  • Pinned host keys — an unattended backup never trusts a new key.
  • Config-change traps queue a backup for scheduled devices.

Secure terminal

SSH and Telnet in the browser, on the record.

Open a terminal from any device's row or details. It connects from the DeviceManager server to the device's management IP, after you re-enter your DeviceManager password.

  • Host keys pinned on first use

    Compare the fingerprint, trust it once, and a changed key is refused from then on.

  • Every session recorded

    Who, which login, when and for how long — with an encrypted transcript where typed passwords are stored as [redacted].

5
sessions per user
50
sessions per server
15 min
idle timeout
60 min
maximum session
SSH session · CORE-SW-01 · 10.30.0.10REC

Host key ssh-ed25519 SHA256:q7Vd3kR0Lx9pWmN2cT8sYf…

✓ Trusted & pinned on first connection

CORE-SW-01> enable

Password: ••••••••••

CORE-SW-01# show version | include uptime

CORE-SW-01 uptime is 63 days, 0 hours

CORE-SW-01# exit

Stored transcript · encrypted

Password: [redacted]

CORE-SW-01# show version | include uptime

Traps & tools

An SNMP trap receiver that acts on what it hears.

Receive SNMP v1 and v2c traps and v2c informs on UDP 162. Common traps are named and summarised — and the ones that matter trigger work straight away.

Trap receiver · this server v1 · v2c · informskept 30 days
  • DC-UPS-01upsOnBatteryCriticalUPS running on battery
  • CORE-SW-01linkDownWarningGi1/0/14 down → re-poll now
  • CORE-SW-01linkUpInfoGi1/0/14 back up
  • EDGE-RTR-01ciscoConfigManEventInfoConfiguration changed → backup queued
  • FIN-SW-01authenticationFailureWarningSNMP authentication failure
  • FL2-PRN-01printerV2AlertWarningPrinter alert raised
  • FL1-SW-01coldStartWarningDevice restarted → re-poll now
  • FL2-AP-01warmStartInfoWarm start → re-poll now

Traps that trigger work

Link and restart traps trigger an instant re-poll; config-change traps queue a backup.

Only known sources

Only inventoried devices or added sources. Floods over 120 a minute per source are dropped.

Network tools, from the server

Ping, traceroute and a port check of common management ports — every run audited.

  • SSH
  • Telnet
  • HTTP
  • HTTPS
  • SNMP
  • NETCONF
  • RDP
  • VNC
  • JetDirect
  • IPP

The trap receiver is off by default and runs per server; it is switched on in the server configuration. SNMPv3 traps and traps from ignored devices are dropped.

Security by design

Secure by design, down to the community string.

Encrypted, never shown again

Community strings, SNMPv3 keys and logins are encrypted and hidden after saving.

Scoped to subnets

A scoped credential is only ever sent to addresses inside its subnets.

Password re-confirmation

Terminals, merges, deletes, backups and credential changes ask for your password again.

Web logins on a timer

Revealed after re-confirmation, recorded, and hidden again after 60 seconds.

Audited by default

Web-UI launches, config views, transcript views and tool runs are all logged.

Granular permissions

Seven permissions, from View and Scan to Connect and View Config.

Part of DeviceManager

Network devices work with the rest of the self-hosted console.

Hardware assets

Link a device to an asset record; it carries a NET badge.

Incidents

Create incidents from any device, or let them open and close automatically.

AI Assistant

Ask about network devices: “Which printers keep giving problems?”

Vulnerability assessment

Pair network visibility with agent-based vulnerability assessment of endpoints.

FAQ

Network monitoring, answered.

Does network device monitoring need an agent on the devices?
No. Routers, switches, firewalls, printers and other equipment are monitored agentless over SNMP v1, v2c or v3 from your DeviceManager server. SSH or Telnet is used only for the in-browser terminal and configuration backup. Machines that already run a DeviceManager agent are hidden from this module automatically.
Do network devices use DeviceManager licence seats?
No. Network devices are kept separate from managed endpoints and never take a licence seat. The Network Devices module itself is enabled through your DeviceManager entitlements.
Is SNMPv3 supported?
Yes. SNMPv3 profiles support authPriv, authNoPriv and noAuthNoPriv, with MD5, SHA1, SHA256, SHA384 or SHA512 authentication and DES, 3DES, AES128, AES192 or AES256 privacy. Because v1 and v2c send the community string in clear text, we recommend SNMPv3 with authentication and privacy wherever the device supports it.
Which vendors does configuration backup support?
Configuration backup has command sets for Cisco IOS, IOS-XE, NX-OS and ASA, HPE Aruba and ProCurve, Juniper Junos, MikroTik RouterOS and Fortinet FortiOS. Other devices are tried with show running-config. Vendor behaviour varies, so start by backing up one known switch and checking the result before rolling it out widely.
What network access does the DeviceManager server need?
The server reaches devices on UDP 161 for SNMP and on TCP 22 for the terminal and configuration backup (TCP 23 only if you allow Telnet). The trap receiver listens for inbound UDP 162. Open web UI links open in the operator's own browser, so the operator's computer must reach the device's web ports.
Does it support IPv6?
Scan targets are IPv4 only: CIDR blocks, ranges and single addresses, up to 65,536 addresses per scan.

Let's talk

Bring the network into the same console as your endpoints.

See discovery, the topology map and configuration backup in a tailored demo, then plan a pilot that starts with one known switch and one printer.

Book a live demo
Call us+91 93244 18175 Email usinfo@anvesiontech.com

Sales sales@anvesiontech.comSupport support@anvesiontech.com