SolarWind- Orion Plateform (On-Premises SolarWinds/ Self-Hosted SolarWinds)

-

 Note: On-Premises doesn't mean the servers must be physically in your own data center. The classification depends on who manages the SolarWinds application, not where the VM is hosted.

What is SolaWinds?

SolarWinds Orion Platform is the SolarWinds framework that provides common functionality such as web access, alerting, reporting, discovery, user management, API services, and database connectivity. Monitoring modules such as NPM, NCM, and SAM use these functions to perform their specific monitoring tasks.

Key Components of SolarWinds Architecture

1. Orion Platform

The Orion Platform is the central software framework that provides:

  • Web Console
  • Alerting Engine
  • Reporting Engine
  • Discovery Services
  • API Services
  • User Authentication and Authorization
  • Database Connectivity
  • Job Scheduling

The Orion Platform itself does not perform monitoring. It provides the infrastructure required by SolarWinds modules.

2. Main Polling Engine (MPE)

Definition

The Main Polling Engine is the primary SolarWinds server responsible for collecting monitoring data from devices and applications.

Functions

  • Polls devices using SNMP, WMI, ICMP, APIs, and agents
  • Processes monitoring data
  • Generates alerts
  • Executes discovery jobs
  • Hosts Orion Platform services
  • Communicates with the SQL database

Note

The Orion Platform is typically installed on the Main Polling Engine server.


3. SolarWinds Database Server

Definition

A Microsoft SQL Server database that stores all SolarWinds monitoring information.

Stores

  • Device inventory
  • Performance statistics
  • Alerts and events
  • User information
  • Configuration backups (NCM)
  • Historical monitoring data

Important

The database is not part of the Orion Platform but is required for Orion Platform operation.


4. Additional Polling Engine (APE)

Definition

An Additional Polling Engine is an extra polling server used to distribute monitoring load in large environments.

Functions

  • Polls devices
  • Sends collected data to the central database
  • Extends monitoring capacity

Use Cases

  • Large environments
  • Remote sites
  • Thousands of monitored devices


5. Web Console

Definition

The web-based user interface used to access SolarWinds monitoring data.

Functions

  • Dashboards
  • Alerts
  • Reports
  • Device Management
  • Configuration Management


SolarWinds Modules

NPM (Network Performance Monitor)

Purpose

Network monitoring and performance management.

Monitors

  • Routers
  • Switches
  • Firewalls
  • Load Balancers

Metrics

  • Availability
  • CPU Utilization
  • Memory Utilization
  • Interface Traffic
  • Packet Loss
  • Latency

NCM (Network Configuration Manager)

Purpose

Network configuration management.

Features

  • Configuration backup
  • Change tracking
  • Configuration comparison
  • Compliance auditing
  • Bulk configuration deployment
  • Configuration rollback

SAM (Server & Application Monitor)

Purpose

Server and application monitoring.

Monitors

  • Windows Servers
  • Linux Servers
  • VMware
  • Hyper-V
  • Databases
  • Web Servers

Metrics

  • CPU
  • Memory
  • Disk Usage
  • Services
  • Processes
  • Application Availability
_______________________________________________________________________________

Note:
Main Polling Engine Server
    |
    +-- Orion Platform
           |
           +-- Web Console
           +-- Alerting
           +-- Reporting
           +-- Discovery
           +-- API Services
           +-- Database Connectivity
    |
    +-- NPM
    +-- NCM
    +-- SAM

What happens?

  1. Orion Platform is installed on the Main Polling Engine.
  2. Orion Platform provides:
    • Web UI
    • Alert engine
    • Reporting
    • Discovery
    • API
    • Database connection
  3. NPM, NCM, and SAM use these capabilities to perform monitoring and management tasks.

Note: "Orion" is simply the product/platform name chosen by SolarWinds

Comments

Post a Comment

Popular posts from this blog

How to enable the syslog monitoring-Zabbix

-
Steps need to be performed:  On the Syslog server side:  1. Install the rsyslog sudo yum install rsyslog 2.  Enable rsyslog service: Start and enable the rsyslog service if it’s not already running: sudo systemctl start rsyslog sudo systemctl enable rsyslog 3.  Configure rsyslog to accept remote logs: Open the rsyslog configuration file: vi /etc/rsyslog.conf Uncomment or add the following lines to enable UDP or TCP log reception: # Provides UDP syslog reception module(load="imudp") input(type="imudp" port="514") # Provides TCP syslog reception module(load="imtcp") input(type="imtcp" port="514") 4.  Restart the rsyslog service: After saving the configuration file, restart rsyslog to apply the changes: sudo systemctl restart rsyslog 5. Ensure the firewall is configured to allow the TCP/UDP port 514 or disable the firewall service. 6. Ensure that SELinux is disable if not disable it Check the status of SELinux sestatus Disa...
Read more

Zabbix installation: Distribution setup

-
  On Zabbix core server: Step1:   Install Zabbix repository rpm -Uvh https://repo.zabbix.com/zabbix/6.0/rhel/8/x86_64/zabbix-release-latest-6.0.el8.noarch.rpm dnf clean all Step2: Install Zabbix server, frontend, agent dnf install zabbix-server-mysql zabbix-web-mysql zabbix-apache-conf zabbix-selinux-policy zabbix-agent Step3:   Configure the database for Zabbix server Edit file /etc/zabbix/zabbix_server.conf DBHost= DBserver_ip DBName= DBUser= DBPassword= DBPort=3306 Step4:  Start Zabbix server and agent processes systemctl restart zabbix-server zabbix-agent httpd php-fpm systemctl enable zabbix-server zabbix-agent httpd php-fpm On Zabbix Database Server: Step1:   Install Zabbix repository rpm -Uvh https://repo.zabbix.com/zabbix/6.0/rhel/8/x86_64/zabbix-release-latest-6.0.el8.noarch.rpm dnf clean all Step2: Install the sql script, zabbix agent  dnf install zabbix-sql-scripts zabbix-selinux-policy zabbix-agent Step3: Install the mysql server yum install my...
Read more

SNMP OID: Full Insight

-
 SNMP uses OIDs to uniquely identify pieces of data (like CPU usage, interface status, etc.). Standard OIDs (defined by IETF) are common across all devices , e.g.: 1.3.6.1.2.1.1.1.0 → sysDescr (system description) 1.3.6.1.2.1.2.2.1.10 → ifInOctets (interface input bytes) Vendor-specific OIDs: For example: Vendor Enterprise OID Base Example Cisco 1.3.6.1.4.1.9 1.3.6.1.4.1.9.1.516 (Cisco 2960 model) Juniper 1.3.6.1.4.1.2636 Juniper-specific OIDs HP 1.3.6.1.4.1.11 HP printer/router OIDs Fortinet 1.3.6.1.4.1.12356 FortiGate device OIDs Part 1: Standard SNMP OID – .1.3.6.1.2.1.1.1.0 This is used for system description , and it works on all SNMP-supported devices (routers, switches, servers, etc.). Let’s break this path: 🔹 .1 → iso International Organization for Standardization This is the root of the SNMP OID tree. Every OID begins from here. 🔹 .3 → org Organization This level is used for organizations that are registered under ISO. 🔹 .6 → dod Depart...
Read more