Annual Premium Equivalent


Your Orion Platkhung installation consists of a Main Polling Server (Orion Web Console and the Main Polling Engine), & the Orion Database Server. The polling engine gathers device statistics và stores the information on the Orion Database Server. The Main Polling VPS reads the stored information from the Orion Database Server.

Bạn đang xem: Annual Premium Equivalent

  Chechồng out this short đoạn Clip (0:58) on the Enterprise-class scalability of Orion products.

Your Main Polling Engine polls a definite number of elements depending on the Orion Platsize sản phẩm. Too many elements on a single polling engine can have a negative impact on your VPS. When the maximum polling throughput on a single polling engine is reached, the polling intervals are automatically increased lớn handle the higher load. To keep mặc định polling intervals, you need lớn add polling capađô thị.

What is a scalability engine?

"Scalability engine" is a general term that refers lớn any VPS that extends the monitoring capacity of your installation, such as Additional Polling Engines (APEs), Additional Web Servers (AWS), or High Availability (HA) backups.

How vì chưng I know that I need lớn scale my Orion Platform product?

When the polling capacity on a polling engine is getting cthảm bại khổng lồ the limit or is exceeded, Orion Platkhung products notify you about it.

See Notifications in the Orion Web Console.


Review your alerts. If the Polling rate limit exceeded out-of-the-box alert is enabled, the alert sends an tin nhắn & adds an entry to lớn All Active sầu Alerts.


Select the scalability option suitable for your environment and deployed Orion Platsize products

Reviews the scalability options và compare them with options available for Orion Platkhung products you have deployed.

Scalability Supported products When lớn select this option
Additional Polling Engine (APE) All Orion Platsize products

To increase the polling capađô thị of your deployment, deploy APEs.


An additional polling engine that does not require an extra license.

You cannot stack free poller licenses.

Additional Web Server All Orion Platsize products To improve the performance of your Orion Web Console by load-balancing a large number of users or in secured environments where you have your Orion Platkhung products behind a firewall, deploy Additional Web Servers. » Learn more
Stacking licenses NPM 12.2 & later SAM 6.9 & later with component-based licenses

If you have enough resources on your polling engine hệ thống, apply multiple licenses on the VPS lớn increase its polling capađô thị. » Learn more

Orion Remote Collector


NAM 20trăng tròn.2.1 SAM 20đôi mươi.2.1 with node-based licenses

To securely monitor offices over low bandwidth & high latency connections or small offices in remote locations, deploy an Orion Remote Collector. » Learn more

Remote Orion Poller for Additional Polling Engines



To deploy your Orion Platform sản phẩm in numerous remote locations without scaling up your installation, deploy a Remote Office Poller for Additional Polling Engine (ROPhường, mini-poller). » Learn more

High Availability All Orion Platsize products except for ETS

To implement failover protection for your Orion Server & additional polling engines, deploy High Availability.

Deploy the selected scalability option

review scalability requirements và find out more about scalability options.

Centralized Deployment with Additional Polling Engines

Centralized Deployment with APEs polls data locally in each region and the polled data are stored centrally on the database server in the primary region. All licenses are shared in a Centralized Deployment. Use this deployment if your organization requires centralized IT management & localized collection of monitoring data.

Why deploy APEs centrally?

Users can view all network data from the Orion Web Console in the Primary Region where the main Orion hệ thống is installed.

Users can log in to lớn a local Web Console if an Additional Web Server is installed in a secondary region.

With Centralized Deployment, you can:

Add, delete, & modify nodes, users, alerts và reports centrally, on the Main Orion Server. Scale all installed Orion Platkhung products. Scaling one Orion Platform product increases the capacity of the other Orion Platkhung products. For example, installing an APE for NPM also increases the polling capađô thị for SAM. Specify the polling engine that collects data for monitored nodes & reassign nodes between polling engines.

All Key Performance Indicators (KPIs), such as Node Response Times, are calculated from the perspective sầu of the polling engine. For example, the response time for a monitored node in Region 2 is equal lớn the round trip time from the APE in Region 2 khổng lồ that node.


For additional information on Centralized Deployment, see the Orion Platkhung Scalability Tech Tip.

Requirements for APEs

The latency (RTT) between each Additional Polling Engine and the database server should be below 200 ms. Degradation may begin around 100 ms, depending on your utilization. Ping the Orion SQL Server to lớn find the current latency. A reliable static connection between the VPS và the regions.

Make sure that your environment meets the requirements for Additional Polling Engines in Multi-module system guidelines. Extra large environment requirements include:

Amazon Web Service: m5.xlarge

Microsoft Azure: D4s_v3

On premise:

Quad core processor or better 32 GB RAM Storage: 150 GB, 15,000 RPM 1 x 1 Gb dedicated NIC Windows Server 2019, năm 2016 or 2012 R2, Standard or Datacenter Edition

Make sure that you have opened all necessary ports:

Additional Polling Engines have sầu the same port requirements as the Main Polling Engine. The following ports are the minimum required for an Additional Polling Engine to ensure the most basic functions.

Port Proto-col Service/Process Direction Description
161 UDP Job Engine Outbound The port used for sending & receiving SNMP information.
162 UDP Trap Service Inbound The port used for receiving trap messages.

Xem thêm:


TCP CollectorService Outbound The port used for communication between the APE and the Orion database.
1434 UDP Squốc lộ Browse Service Outbound The port used for communication with the Squốc lộ Server Browser Service lớn determine how khổng lồ communicate with certain non-standard SQL Server installations. Required only if your Squốc lộ Server is configured lớn use dynamic ports.



RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Main Polling Engine to the Additional Polling Engine.


TCP InformationService Bidirectional

The port used for communication between the Additional Polling Engine & the Main Polling Engine.

How to deploy?

Distributed Deployment with Main and Additional Polling Engines in regions

In a Distributed Deployment, each region is licensed independently, & data are polled and stored locally in each region. Scale each region independently by adding APEs. You can access monitoring data from each region in a central location with the Enterprise Operations Console (EOC). Enterprise Operations Console must be installed và licensed if you want to lớn view aggregated data from multiple Orion servers in a Distributed Deployment.

Why deploy Additional Polling Engines in a distributed environment?

With Distributed Deployment you can:

Use local administration lớn manage, administer, and upgrade each region independently. Create, modify, or delete nodes, users, alerts, và reports separately in each region. Export và import objects, such as alert definitions, Universal Device Pollers, và SAM application monitor templates between instances. Mix và match modules và license sizes as needed. For example:Region 1 has deployed NPM SL500, NTA for NPM SL500, UDT 2500, and 3 APEsRegion 2 has deployed NPM SLX, SAM500, UDT 50,000, và 3 APEsRegion 3 has deployed NPM SL100 only và 3 APEs

EOC 2.0 and later leverage a function called SWIS Federation lớn query for specific data only when needed. This method allows EOC khổng lồ display live sầu, on-demand data from all monitored Sites. & does not store historical data.


How to lớn deploy?

Additional Web Servers

Deploying an Additional Web Server might be helpful in the following cases:

The number of users logged in to the Orion Web Console at the same time is cthua khổng lồ 50.

How lớn deploy?

Make sure you have all ports required for Additional Web Servers open:

Port Protocol Service/Process Direction Description



World Wide Web Publishing Service Inbound

Default additional website VPS port. xuất hiện the port khổng lồ enable communication from your computers khổng lồ the Orion Web Console.

If you specify any port other than 80, you must include that port in the URL used to access the web console. For example, if you specify an IP. address of và port 8080, the URL used khổng lồ access the website console is

443 TCP IIS Inbound The default port for https binding.


TCP Information Service Outbound

The port used for communication between the VPS and the Squốc lộ Server. Open the port from your Orion Web Console khổng lồ the SQL Server.

5671 TCP RabbitMQ Outbound

The port used for SSL-encrypted RabbitMQ messaging from the Additional Web Server lớn the Main Polling Engine.


TCP Information Service Outbound

Orion module traffic. Open the port to enable communication from all polling engines (both Main or Additional) to lớn the Additional Web Server, & from the Additional Web Server lớn polling engines.

Learn more: Optimize the performance of Orion Web Console.

Remote Office Pollers

To deploy your Orion Platkhung sản phẩm in numerous, remote locations when you vày not need lớn scale up your installation, use a Remote Office Poller for Additional Polling Engine (ROPhường., mini-poller).

Select a Remote Office Poller by the number of elements you need to poll:

ROP250 polls up to 250 elements. ROP1000 polls up lớn 1000 elements. How khổng lồ deploy?

Orion Remote Collectors

Orion Remote Collector (ORC) is a lightweight distributed polling engine that you can use to lớn monitor devices in your environment agentlessly through WXiaoMI and SNMP..

Why deploy? ORCs use the Agent giải pháp công nghệ khổng lồ communicate with the Orion Platsize ORCs do not need a direct connection lớn the database ORCs are easy khổng lồ deploy in remote locations, thanks khổng lồ their simplified architecture ORCs can poll/cabít over unreliable networks (store up khổng lồ 24 hours with no connection lớn the polling engine) Requirements Requirement Description
Supported operating systems Windows Server 2012 R2 Windows Server năm 2016 Windows Server 2019 Windows 10 Not Supported on Linux và AIX The server where you deploy the agent must have a unique hostname.
Ports to lớn open

mở cửa only one port.

The ORC agent is NAT friendly, supports authenticated proxy traversal. You can thus easily deploy the Remote Collector in your DMZ, branch office locations, và even in the cloud, with very few or no firewall policy changes.

Orion Platkhung products that tư vấn Orion Remote Collector NAM 20đôi mươi.2.1
Other requirements Agents installed on the Orion Server CANNOT be promoted khổng lồ Remote Collectors. Only Agent-initiated mode is supported (Server-initiated mode is NOT supported). The Agent server must have sầu .NET 4.8 or later installed. Hardware requirements for Agent servers depkết thúc on the number of elements polled by the Orion Remote Collector.
What is supported?

Orion Remote Collector (ORC) does not provide full support for all metrics polled by Additional Polling Engines. For more details, see Orion Remote Collector tư vấn.

Xem thêm: Cách Làm Trứng Cút Rang Me Cực Ngon Lại Vừa Dễ Làm, Cách Làm Trứng Cút Lộn Xào Me Đơn Giản, Thơm Ngon

Product supporting ORC Supported features

NAM 20đôi mươi.2.1


Common Orion Platform metrics

Node CPU Node Memory Node Status Node Response Volumes


Device Studio Device View Duplex Mismatch FiberChannel Hardware Health Interfaces Multicast NEC Nexus Routing và VFR Switch Stachồng Topology UnDP VLANs Wireless Wireless Heatmaps
SAM (node-based licenses only) AppInsight for Active Directory AppInsight for IIS AppInsight for Squốc lộ AppInsight for Exchange Most application monitor templates Asset inventory Hardware Health
ORC Scalability limits

Maximum of 100 Remote Collectors per polling engine

Maximum 1000 elements per Remote Collector

Maximum 40,000 elements supported per polling engine by all Orion Remote Collectors.


Upgrade/migration details Upgrades occur over the same single port the Orion Remote Collector Uses to lớn Communicate khổng lồ the Orion Server Plugins are deployed automatically lớn Orion Remote Collector as new Orion Platkhung products are installed When you upgrade the main Orion Server, ORCs are upgraded automatically You can move sầu nodes between Orion Remote Collector and/or APEs How to lớn deploy?


Deploy an Orion Agent using the agent-initiated communication, for example using the Add node wizard or manually.