Netriva Network Monitoring & Operations
Menu

Device & service compatibility

Check your equipment before the pilot.

Compatibility depends on your equipment, firmware, available measurements and the monitoring profiles included in your Netriva and collector versions. The profiles below describe their scope and access requirements for customer networks.

SNMP access on your network

You can use SNMPv3 on your own devices. Your administrator creates a read-only account with authentication and encryption (authPriv), permits access from your collector and saves the credentials in your Netriva workspace. Read-only describes the permissions Netriva uses to monitor the device.

The interface-monitoring profile also supports restricted SNMPv2c for approved legacy devices. The routing, wireless-controller, firewall-resource and IPsec profiles described here use SNMPv3.

Preview profiles have additional release and device-compatibility requirements. Confirm that the profile is included in your Netriva and collector versions before planning deployment.

Switches and routers · IF-MIB

Port inventory, interface status and traffic counters over SNMP.

Requires the device to expose IF-MIB. CPU and temperature are not part of this profile.

Routing · BGP4-MIB

IPv4 BGP neighbour sessions and message counters.

Uses read-only SNMPv3 and BGP4-MIB support on your router. BGP and OSPF use separate monitoring profiles.

Routing · OSPFv2 preview

Preview profile for IPv4 neighbour state, state-change/error counters and retransmission queues.

Requires a Netriva and collector version containing this profile, OSPF-MIB support and read-only SNMPv3 on your router. Covers OSPFv2 non-virtual neighbours. OSPFv3 uses a separate preview profile; virtual-link monitoring is not included.

Routing · OSPFv3 preview

Preview profile for IPv6 OSPF neighbour state, state-change/error counters, retransmission queues and counter-discontinuity information.

Requires a Netriva and collector version containing this profile, RFC 5643 OSPFV3-MIB support and read-only SNMPv3 on your router. Covers non-virtual neighbours in the default SNMP context. Multiple routing-process or VRF contexts and virtual links are not included. Confirm your Cisco IOS model and firmware before deployment.

Wireless controllers · CAPWAP

Controller access-point sessions, client sessions and access-point state.

Uses read-only SNMPv3 and the CAPWAP counters exposed by your controller model and firmware. Radio channel utilisation is not included.

Firewall resources · SNMP

Processor, memory and interface error/discard information where exposed.

Uses read-only SNMPv3. Counters vary by model and firmware. Session capacity is not included; the profile does not modify firewall rules.

Linux hosts · node_exporter

CPU, available memory, filesystem capacity and disk I/O on compatible Linux servers, VMs, workstations and appliances.

Requires node_exporter 1.12.1 on the monitored device, with a compatible operating system, architecture and access to the required metrics. Your administrator or ITES installs it with your approval; the collector reads its endpoint. Linux-based network equipment may need an SNMP or API profile instead.

Windows servers · windows_exporter

Server resource measurements through an approved exporter.

Requires an approved, reachable windows_exporter 0.31.8 installation. Validate the enabled collectors and operating system.

Proxmox VE 9 · read-only API

Virtual machine resource listings, power state, CPU, memory and disk information.

Requires a read-only PVEAuditor API token and verified TLS. Monitors VM resources; it does not start or stop VMs or monitor host hardware health.

Cisco IOS · IPsec preview

Preview profile for active IKE/IPsec counts, security-association rows, traffic and authentication-failure counters.

Requires a Netriva and collector version containing this profile, the Cisco IPsec MIB and read-only SNMPv3 on a compatible IOS image. Active counts and reported rows are not a complete tunnel-health assessment; a separate service check tests traffic across the VPN.

VPN endpoints · reachability

Connectivity checks to an approved VPN endpoint.

A VPN gateway can respond even when its tunnel is down. Add a check to a protected service across the VPN; tunnel and encryption-session status need a supported device integration.

Check the services your team relies on

Service checks: DNS, TCP, HTTP and TLS.

Choose the condition that matters for each service. Each result describes that check; it does not prove every part of an application is working.

DNS responses

Confirm that a name resolves as configured.

TCP connections

Check whether the approved service port accepts a connection.

HTTP responses

Check the expected status and optional response fingerprint.

TLS certificates

Track certificate validity and expiry for the approved endpoint.

Checking a service across a VPN?

Use a collector whose route to the approved private service crosses the VPN. This tests that service path separately from the gateway response. It does not report the tunnel’s encryption-session state.

Plan your pilot

Share your device types, models, firmware and service-check goals. Keep passwords and detailed network addresses out of the public form; ITES will arrange a secure setup review.

Start Free Pilot →
See how Linux metrics are connected →