Orion Platform Scalability Flashcards
A scalability option where APEs poll data locally in each region and the polled data are stored centrally on the database server in the primary region.
Centralized Deployment
Reference: https://documentation.solarwinds.com/en/success_center/orionplatform/content/orion_platform_scalability_engine_guidelines.htm
What must be the maximum latency between each additional polling engine and the database
200 ms
True or False
Additional polling engines (APEs) have the same port requirements as the main polling engine
True
True or False
Additional polling engines (APEs) have the same port requirements as the main polling engine
True
Reference: https://documentation.solarwinds.com/en/success_center/orionplatform/content/orion_platform_scalability_engine_guidelines.htm#CentralizedDepoloyment
In this scalability option, each region is licensed independently, and data are polled and stored locally in each region.
Distributed deployment
This solution must be installed and licensed if you want to view aggregated data from multiple Orion servers in a distributed deployment.
SolarWinds Enterprise Operations Console
This method allows EOC to display live, on-demand data from all monitored SolarWinds Sites. and does not store historical data.
SWIS federation
True or False
Remote Office Pollers do not need a direct connection to the database
False
ORCs do not need a direct connection to the database
Reference: https://documentation.solarwinds.com/en/success_center/orionplatform/content/orion_platform_scalability_engine_guidelines.htm#CentralizedDepoloyment
Orion Remote Collector (ORC) uses what technology to communicate with the Orion Platform
Agent Technology
Orion Platform products that support Orion Remote Collector
NAM 2020.2.1
SAM 2020.2.1
Reference: https://documentation.solarwinds.com/en/success_center/orionplatform/content/orion_platform_scalability_engine_guidelines.htm#CentralizedDepoloyment
ORC Scalability limits
Maximum of __ Remote Collectors per polling engine
Maximum ___ elements per Remote Collector
Maximum ___elements supported per polling engine by all Orion Remote Collectors.
100 ORCs/polling engine
1000 Elements per Remote Collector
48 000 elements per polling engine by all ORCs
For NTA Scalability limits:
WAN and/or bandwidth considerations
1.5% - 3% of total traffic seen by exporter
Reference: https://documentation.solarwinds.com/en/success_center/orionplatform/content/orion_platform_scalability_engine_guidelines.htm
Node statistics Polling interval
10 minutes
https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-polling-statistics-intervals-sw1829.htm
Interface Statistics Polling Interval
9 minutes
https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-polling-statistics-intervals-sw1829.htm
Main polling engine limits for Network Configuration Manager (NCM)
Maximum of 10k devices per polling engine
Maximum of 30K devices per Solarwinds instance
How many agents can a single polling engine support with default polling enabled?
1000 agents
Combining Agents with ORCs reduces the total number of Orion Agents supported per polling engine. For each ORC you use, the Agent scalability is reduced by __ Orion Agents
ten; 1 ORC = 10 Orion Agents
How many component monitors can you monitor per server at standard polling with SAM with node-based licensing,
48 000
How many component monitors can you monitor per server at standard polling with SAM with node-based licensing,
48 000
With component-based licensing, how many polling engines can be installed on a single SAM server
two, 2
With component-based licensing, how many component monitors can you monitor per polling engine.
~8-10K
User Device tracker’s Main polling engine and instance limits
maximum of 100k ports per polling engine
Maximum of 500K ports per Solarwinds instance
VoIP & Network Quality Manager (VNQM) Main polling engine and instance limits
Per Polling Engine
~5,000 IP SLA operations
~200k calls/day with 20k calls/hour spike capacity
Per instance
Maximum of 15K IP SLA operations and 200K call/day
At what polling rate if reached or exceeded of the server’s maximum polling rate, a Poller Status Warning is displayed in the Web Console.
85 %
True or False
High Availability supports failover to public cloud and Infrastructure as a Service (IaaS) solutions.
True
Reference: https://www.solarwinds.com/high-availability
IPAM Supported DHCP Servers
Cisco, Infoblox, ISC and Microsoft
Reference: https://documentation.solarwinds.com/en/success_center/ipam/content/ipam-dhcp-management.htm
What are the Scalability limits of LA/OLV in terms of the number of events per second?
1 000 Events per second
Based on Netpath scalability, How many paths can you add per polling engine
100 paths
According to the Netpath Scalability guide, How many paths can you add per Netpath probe?
10 paths per core
20 Paths/probe
100 paths per polling engine
Source: https://documentation.solarwinds.com/en/success_center/npm/content/npm-netpath-requirements.htm
Port used by NetPath™ to query BGP information about the discovered IP addresses.
Port 43, 443
SRM Scalability for the number of LUNs per poller and per Instance
Maximum of 40K LUNs per poller (main or additional)
Maximum of 160K LUNs per instance
Scalability Limit of NTA per poller
50K flows per second
WPM Scalability limit
12 WPM Recordings per player
Scalability Limit for Security Event Manager (SEM)
Up to 216 million events per day (2,500 events per second)
5,000 rule hits per day
Scalability Limit for (QoE)
A maximum number of nodes per sensor (NPAS):
50 nodes
Scalability options
Maximum number of sensors deployed on your network:
1000 sensors
You need to deploy this if you want to securely monitor offices over low bandwidth and high latency connections or small offices in remote locations
ORCs, Orion Remote Collector
You can deploy this if you want to deploy your SolarWinds platform product in numerous remote locations without scaling up your installation
Remote Office Poller (ROP, mini-poller)
True or False:
Agents installed on the SolarWinds platform server CANNOT be promoted to Remote Collectors.
TRUE
High Availability over a single subnet is provided for SolarWinds products released on which Orion Platform version?
High Availability on a single subnet is provided for SolarWinds products released on SolarWinds Platform version 2016.2 and later.
It is general term that refers to any server that extends the monitoring capacity of your SolarWinds installation, such as additional polling engines (APEs), additional polling engines (AWS), or High Availability (HA) backups.
Scalability Engine
