Ape Là Gì

 - 

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

Bạn đang xem: Ape là gì

*
  Check out this short video (0:58) on the Enterprise-class scalability of Orion products.

Your Main Polling Engine polls a definite number of elements depending on the Orion Platform product. Too many elements on a single polling engine can have a negative impact on your vmvc.com.vn server. When the maximum polling throughput on a single polling engine is reached, the polling intervals are automatically increased to handle the higher load. To keep default polling intervals, you need to add polling capacity.

What is a scalability engine?

"Scalability engine" is a general term that refers to any server that extends the monitoring capacity of your vmvc.com.vn installation, such as Additional Polling Engines (APEs), Additional Web Servers (AWS), or High Availability (HA) backups.

How do I know that I need to scale my Orion Platform product?

When the polling capacity on a polling engine is getting close to the limit or is exceeded, Orion Platform 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 email and adds an entry to All Active Alerts.

*

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

Review the scalability options and compare them with options available for Orion Platform products you have deployed.

Scalability Supported products When to select this option
Additional Polling Engine (APE) All Orion Platform products

To increase the polling capacity of your deployment, deploy APEs.

Free Poller LA SCM SRM VMAN

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

You cannot stack free poller licenses.

Additional Web Server All Orion Platform 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 Platform products behind a firewall, deploy Additional Web Servers. » Learn more
Stacking licenses NPM 12.2 and later SAM 6.9 and later with component-based licenses

If you have enough resources on your polling engine server, apply multiple licenses on the server to increase its polling capacity. » Learn more

Orion Remote Collector

(ORC)

NAM 2020.2.1 SAM 2020.2.1 with node-based licenses

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

Remote Orion Poller for Additional Polling Engines

(ROP)

IPAM NCM NPM SAM SRM UDT VMAN VNQM WPM

To deploy your Orion Platform product in numerous remote locations without scaling up your installation, deploy a Remote Office Poller for Additional Polling Engine (ROP, mini-poller). » Learn more

High Availability All Orion Platform products except for ETS

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

Deploy the selected scalability option

Review scalability requirements and 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 and 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 vmvc.com.vn Orion server is installed.

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

With Centralized Deployment, you can:

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

All Key Performance Indicators (KPIs), such as Node Response Times, are calculated from the perspective of the polling engine. For example, the response time for a monitored node in Region 2 is equal to the round trip time from the APE in Region 2 to that node.

*

For additional information on Centralized Deployment, see the vmvc.com.vn Orion Platform 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 find the current latency. A reliable static connection between the server and 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, 2016 or 2012 R2, Standard or Datacenter Edition

Make sure that you have opened all necessary ports:

Additional Polling Engines have 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 vmvc.com.vn Job Engine Outbound The port used for sending and receiving SNMP information.
162 UDP vmvc.com.vn Trap Service Inbound The port used for receiving trap messages.

Xem thêm: Món Dạ Dày Xào Thập Cẩm Giòn Dai Hấp Dẫn » Thế Giới Ẩm Thực, Dạ Dày Xào Thập Cẩm Dai Dai Thơm Thơm Cực Hấp Dẫn

1433

TCP

vmvc.com.vn CollectorService Outbound The port used for communication between the APE and the Orion database.
1434 UDP SQL Browse Service Outbound The port used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports.

5671

TCP

RabbitMQ Outbound

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

17777

TCP

vmvc.com.vn InformationService Bidirectional

The port used for communication between the Additional Polling Engine and 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, and 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).

vmvc.com.vn Enterprise Operations Console must be installed and licensed if you want to view aggregated data from multiple vmvc.com.vn Orion servers in a Distributed Deployment.

Why deploy Additional Polling Engines in a distributed environment?

With Distributed Deployment you can:

Use local administration to manage, administer, and upgrade each region independently. Create, modify, or delete nodes, users, alerts, and reports separately in each region. Export and import objects, such as alert definitions, Universal Device Pollers, and SAM application monitor templates between instances. Mix and match modules and 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, and 3 APEsRegion 3 has deployed NPM SL100 only and 3 APEs

EOC 2.0 and later leverage a function called SWIS Federation to query for specific data only when needed. This method allows EOC to display live, on-demand data from all monitored vmvc.com.vn Sites. and does not store historical data.

*

How to 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 close to 50.

How to deploy?

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

Port Protocol Service/Process Direction Description

80

TCP

World Wide Web Publishing Service Inbound

Default additional web server port. Open the port to enable communication from your computers to 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 192.168.0.3 and port 8080, the URL used to access the web console is http://192.168.0.3:8080.

443 TCP IIS Inbound The default port for https binding.

1433

TCP

vmvc.com.vn Information Service Outbound

The port used for communication between the vmvc.com.vn server and the SQL Server. Open the port from your Orion Web Console to the SQL Server.

5671 TCP RabbitMQ Outbound

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

17777

TCP

vmvc.com.vn Information Service Outbound

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

Learn more: Optimize the performance of Orion Web Console.

Remote Office Pollers

To deploy your Orion Platform product in numerous, remote locations when you do not need to scale up your installation, use a Remote Office Poller for Additional Polling Engine (ROP, 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 to 1000 elements. How to deploy?

Orion Remote Collectors

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

Why deploy? ORCs use the Agent technology to communicate with the Orion Platform ORCs do not need a direct connection to the database ORCs are easy to deploy in remote locations, thanks to their simplified architecture ORCs can poll/cache over unreliable networks (store up to 24 hours with no connection to the polling engine) Requirements Requirement Description
Supported operating systems Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows 10 Not Supported on Linux and AIX The server where you deploy the agent must have a unique hostname.
Ports to open

Open 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, and even in the cloud, with very few or no firewall policy changes.

Orion Platform products that support Orion Remote Collector NAM 2020.2.1
Other requirements Agents installed on the Orion Server CANNOT be promoted to Remote Collectors. Only Agent-initiated mode is supported (Server-initiated mode is NOT supported). The Agent server must have .NET 4.8 or later installed. Hardware requirements for Agent servers depend 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 support.

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 2020.2.1

(IPAM, NCM, NPM, NTA, UDT, VNQM)

Common Orion Platform metrics

Node CPU Node Memory Node Status Node Response Volumes

NPM

Device Studio Device View Duplex Mismatch FiberChannel Hardware Health Interfaces Multicast NEC Nexus Routing & VFR Switch Stack Topology UnDP VLANs Wireless Wireless Heatmaps
SAM (node-based licenses only) AppInsight for Active Directory AppInsight for IIS AppInsight for SQL 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 Communicate to the Orion Server Plugins are deployed automatically to Orion Remote Collector as new Orion Platform products are installed When you upgrade the main Orion Server, ORCs are upgraded automatically You can move nodes between Orion Remote Collector and/or APEs How to deploy?

*

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