Multi-Vendor Network Operations

Transport networks are built from many vendors, but they still have to be run as one. EvoNET unifies discovery, monitoring, fault management, and provisioning across Nokia, Infinera, Eltex, the Evollabs EVO MR series, and any generic SNMP device — giving operations teams a single view and a single toolset, with open integration into the wider OSS/BSS estate.

Book a Consultation

Download Brochure

One System to Monitor, Manage, and Assure Every Vendor

About Evollabs

EvoNET by Evollabs is a unified network operations platform that simplifies the management of multi-vendor transport networks. It enables operators to monitor, manage, and provision services across Nokia, Infinera, Eltex, the Evollabs EVO MR series, and other SNMP-enabled devices from a single interface. With consolidated monitoring, fault management, automation, and open API integration, EvoNET helps reduce operational complexity, improve service visibility, and streamline network operations across the entire infrastructure.

THE CHALLENGE

Transport networks are multi-vendor by necessity. Growth, acquisitions, and best-of-breed procurement leave Nokia in one place, Infinera in another, Eltex and the Evollabs EVO MR series elsewhere, plus a long tail of generic SNMP devices. Each vendor ships its own element manager, its own CLI, and its own alarm formats — so operations teams end up running a patchwork of consoles, correlating faults by hand, and switching between tools just to understand what the network is doing.

The cost shows up as time. When something breaks, the first job is working out where — and with alarms arriving in different formats from different systems, a single fibre cut can generate hundreds of events across several element managers with no common view. Duplicate and flapping alarms bury the root cause, and mean time to repair stretches because the network's state is scattered across tools that were never designed to talk to each other.

Day-to-day operations are just as fragmented. Backups, software updates, configuration changes, and service provisioning each work differently per vendor, so automation is hard to build and harder to trust. As the network grows, operational headcount grows with it — and the proprietary umbrella managers that promise to unify everything arrive with price tags and lock-in of their own.

THE SOLUTION

EvoNET replaces the patchwork with one system. It auto-discovers equipment from defined IP pools, identifies each device's type and vendor through a flexible driver model, and places it in a single hierarchical inventory — Nokia, Infinera, Eltex, the Evollabs EVO MR series, and any generic SNMP device, side by side.

From that single inventory, EvoNET runs the whole operational cycle the same way across every vendor: continuous monitoring with a live topology and network-load heat map; remote configuration of system, AAA, NTP, and interfaces; scheduled backups, software updates, and discovery; and provisioning of L3VPN, VPLS, and VPWS services.

Fault handling is unified too. EvoNET collects events over SNMP Traps, Syslog, and NETCONF, protects itself with Storm Control, and passes everything through the Fault Management Module — correlation rules, user-defined Alarm IDs, duplicate and flap suppression, severity classification, and an acknowledge / clear / comment workflow — so the NOC works one prioritised alarm list instead of several raw streams.
And because EvoNET is open, it fits the wider OSS/BSS estate. A REST API (OpenAPI/Swagger) with token authentication exposes inventory, alarms, and services to upstream systems, while RBAC, LDAP authentication, audit logging, and an Active/Standby (1+1) architecture with automatic failover keep it carrier-grade.

Supported Networks & Vendors

EvoNET reaches equipment through a flexible driver model, so coverage extends per deployment. Access parameters — protocol, credentials, encryption, and priority — are set per equipment pool through connection profiles.

Vendor / Platform	What EvoNET manages	Connects via
Vendor / Platform Evollabs EVO MR series	What EvoNET manages Native driver — NETCONF (YANG), SNMP, CLI	Connects via Monitoring, configuration, backup, and service provisioning
Vendor / Platform Nokia	What EvoNET manages Third-party adapter — SSH (CLI), NETCONF, SNMP	Connects via Monitoring, faults, configuration, and services
Vendor / Platform Infinera	What EvoNET manages Third-party adapter — SNMP, NETCONF	Connects via Monitoring, faults, and inventory
Vendor / Platform Eltex	What EvoNET manages Third-party adapter — SNMP, SSH, NETCONF	Connects via Monitoring, faults, and configuration
Vendor / Platform Generic SNMP devices	What EvoNET manages Generic driver — SNMP v2c / v3	Connects via Availability, statistics, and trap collection

Vendor / Platform	What EvoNET manages	Connects via
Evollabs EVO MR series	Native driver — NETCONF (YANG), SNMP, CLI	Monitoring, configuration, backup, and service provisioning
Nokia	Third-party adapter — SSH (CLI), NETCONF, SNMP	Monitoring, faults, configuration, and services
Infinera	Third-party adapter — SNMP, NETCONF	Monitoring, faults, and inventory
Eltex	Third-party adapter — SNMP, SSH, NETCONF	Monitoring, faults, and configuration
Generic SNMP devices	Generic driver — SNMP v2c / v3	Availability, statistics, and trap collection

DEPLOYMENT TOPOLOGY

EvoNET Multi-Vendor Management Topology

Components:

EvoNET server pair — Active/Standby (1+1) with streaming database replication and a single virtual IP for transparent operator access.
OSS/BSS integration — upstream systems connect to EvoNET over the REST API (OpenAPI/Swagger).
Management-protocol layer — SNMP, NETCONF, Syslog, SSH, Telnet, and LLDP between EvoNET and the network.
Managed multi-vendor network — Nokia at aggregation, with Eltex, Infinera, EVO MR series, and generic SNMP elements.

Management & data flows:

Discovery and polling — EvoNET scans IP pools, identifies vendor and type, and polls availability, utilisation, and performance at configurable intervals.
Fault events — network elements send SNMP Traps, Syslog, and NETCONF notifications; Storm Control and the FMS correlate and classify them.
Configuration & provisioning — EvoNET pushes configuration, backups, and L3VPN/VPLS/VPWS services down to the elements.
Northbound — inventory, alarms, and service status are exposed to OSS/BSS via the REST API.

Scale: EvoNET manages heterogeneous networks from a single pair of servers; licensing scales by managed device count, vendor drivers, users, and sessions, so the same deployment grows with the network without changing the operations model.

Request A Demo

Use Cases

Use Case Scenarios

A carrier runs separate element managers for Nokia, Infinera, and Eltex domains. The NOC swivel-chairs between consoles, faults are correlated by hand, and there is no single inventory or topology across the network.

Deployment: EvoNET auto-discovers all three domains through its driver model into one hierarchical inventory and live topology. SNMP Traps, Syslog, and NETCONF events flow into the Fault Management Module, where correlation rules, duplicate/flap suppression, and severity classification produce a single prioritised alarm list with an acknowledge / clear / comment workflow.

Result: One NOC view across every vendor, faster fault isolation, and fewer tools to license and maintain — without replacing the underlying equipment.

POWERED BY EvoNET

Key capabilities for multi-vendor operations

EvoNET is a powerful network management platform that ensures full visibility, automation, and control across multi-vendor transport networks — one system for discovery, monitoring, fault management, provisioning, and open integration.

EvoNET

Complex System for Monitoring and Managing Transport Networks

Book a Consultation

Real-time monitoring, a live topology with a network-load heat map, alarms, and analytics.