McAfee EPOLICY ORCHESTRATOR 4.5 - Guía de instalación descargar pdf (Pagina 33)

Scaling your ePolicy Orchestrator

infrastructure with Agent Handlers

Agent Handlers co-ordinate work between themselves and the ePolicy Orchestrator server.

You can place multiple remote Agent Handlers throughout your network. Once in place, your remote

Agent Handlers use a work queue in the SQL database as their primary communication method. The

Agent Handlers check the work queue frequently and perform the requested action.

What are Agent Handlers

Agent Handlers are a component, introduced with ePolicy Orchestrator software version 4.5, that can

be distributed throughout your environment to help you manage and scale your managed network.

In ePolicy Orchestrator 4.0 and earlier versions, there was a single McAfee ePO server that agents

could connect to and receive policy and task updates. Since the McAfee ePO server was responsible for

handling every agent connecting to it, there was a limitation on the deployment size single server

could handle. A single McAfee ePO server could scale:

• Vertically using bigger and faster hardware

• Horizontally using more servers to distribute the load

Beginning with version 4.5 of the software, Agent Handlers were introduced to allow you to grow your

logical ePolicy Orchestrator infrastructure horizontally. This is accomplished by adding multiple Agent

Handlers to scale agent connectivity.

Agent Handlers allow you:

• To scale your McAfee ePO server if it is overloaded handling the agent request volume

• Fail-over protection if you want agents to fail over between multiple physical servers and you do

not want to cluster the McAfee ePO server

• To use topology features to manage your systems behind a Network Address Translation (NAT) or

in an external network

The Agent Handler must have a high bandwidth connection to the central

ePolicy Orchestrator database.

To understand what Agent Handlers do, it's important that you also understand their limitations. Agent

Handlers require constant communication back to the SQL database that ePolicy Orchestrator uses.

They check the McAfee ePO server database work queue approximately every ten seconds to find what

tasks they need to perform. This is one of the reasons that each Agent Handler needs a relatively high

speed, low latency connection to the database.

McAfee

ePolicy Orchestrator

Best Practices Guide for use with ePolicy Orchestrator versions 4.5.0 and 4.0.0

1 2 ... 28 29 30 31 32 33 34 35 36 37 38 ... 109 110

Sin comentarios

McAfee EPOLICY ORCHESTRATOR 4.5 - Guía de instalación Pagina 33