Riverbed NetIM Architecture – Component Roles Explained

Categories:
Solution Number:
S39023
Last Modified:
2026-02-09
Description

Overview

Riverbed NetIM uses a distributed, multi-component architecture to efficiently discover, collect, process, and store network monitoring data at scale.
Each component has a specific responsibility, allowing NetIM to be flexible, scalable, and resilient in enterprise environments.

The main NetIM components are:

  • Core

  • Worker

  • Manager

  • Data Manager

The sections below explain the role of each component and how they work together.

Issue

1. NetIM Core

Role

The Core is the central coordination and control layer of NetIM.

Key Responsibilities

  • Maintains the overall system configuration

  • Coordinates communication between all NetIM components

  • Controls discovery, polling schedules, and task distribution

  • Provides the main user interface (UI) and API access

  • Manages system health and component registration

Summary

Think of the Core as the “brain” of NetIM. It does not perform heavy data collection itself but orchestrates how and when other components do their work.


2. NetIM Worker

Role

The Worker is responsible for performing data collection and processing tasks.

Key Responsibilities

  • Executes device discovery tasks

  • Polls devices using SNMP, CLI, APIs, etc.

  • Collects performance, availability, and configuration data

  • Processes raw data before forwarding it to the Data Manager

  • Can be deployed in multiple instances for scalability and load distribution

Summary

Workers are the “hands” of NetIM, doing the actual work of communicating with network devices. Adding more Workers increases monitoring capacity and supports distributed environments.


3. NetIM Manager

Role

The Manager handles monitoring logic and operational intelligence.

Key Responsibilities

  • Evaluates collected data against thresholds and policies

  • Generates alerts, events, and incidents

  • Manages device state, relationships, and topology awareness

  • Applies monitoring rules and correlation logic

  • Supports high availability when deployed redundantly

Summary

The Manager acts as the “decision-maker”, determining what the collected data means and when action or notification is required.


4. NetIM Data Manager

Role

The Data Manager is responsible for data storage and retrieval.

Key Responsibilities

  • Stores performance metrics, events, and historical data

  • Optimizes data for reporting and trend analysis

  • Handles data retention and aggregation policies

  • Responds to data queries from the Core, Manager, and UI

Summary

The Data Manager is the “memory” of NetIM, ensuring monitoring data is reliably stored and quickly accessible for dashboards, reports, and troubleshooting.

Solution

Solution

Riverbed NetIM uses a distributed architecture where each component has a defined role to ensure scalability, performance, and reliability. To achieve optimal results, NetIM components should be deployed and used as designed:

  • Core should be deployed as the central control and user access point. It manages configuration, coordination, and system-wide communication.

  • Workers should be deployed based on the size and distribution of the network to handle discovery and data collection efficiently. Additional Workers can be added to scale monitoring capacity.

  • Managers should be configured to process monitoring data, apply thresholds, and generate alerts and events. For high availability, multiple Managers may be deployed.

  • Data Managers should be sized appropriately to store performance metrics, events, and historical data, ensuring efficient reporting and long-term analysis.

By deploying each NetIM component according to its intended role, customers can ensure accurate data collection, timely alerting, and reliable performance monitoring across their network infrastructure.

Duplicate?
Y
Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case