Red Hat LINUX VIRTUAL SERVER 4.6 - ADMINISTRATION Guide de l'utilisateur Page 71
- Page / 92
- Table des matières
- DEPANNAGE
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
• If the Checking new repository content interval has expired since the last time updates were requested, the
SuperAgent downloads updates from the Master Repository, processes them, and completely
flushes the cache if any new content is available.
• When a global update occurs, SuperAgents receive a wake‑up call that flushes all content in the
cache.
• SuperAgents are flushed every 30 minutes by default. When the SuperAgent flushes its
cache, it deletes every file in its repository not listed in Replica.log. This includes any
personal files you might have put in that folder.
• SuperAgent caching in conjunction with repository replication is not recommended.
How communication interruptions are handled
When a SuperAgent receives a request for content that might be outdated, the SuperAgent attempts
to contact the McAfee ePO server to see if new content is available. If the connection attempts time
out, the SuperAgent distributes content from its own repository instead. This is done to ensure the
requester receives content even if that content might be outdated.
SuperAgent Caching should not be used in conjunction with global updating. Both of these features
serve the same function in your managed environment; keeping your distributed repositories
up‑to‑date. However, they are not complementary features. Use SuperAgent caching when limiting
bandwidth usage is your primary consideration. Use Global Updating when quick enterprise updating is
your primary consideration.
SuperAgent and its hierarchy
A hierarchy of SuperAgent can serve agents in the same network with minimum network traffic
utilization.
A SuperAgent caches the content updates from the ePolicy Orchestrator server or distributed
repository and distributes it to the agents in the network reducing the wide area network traffic. It is
always ideal to have more than one SuperAgent to balance the network load.
Ensure that you enable Lazy caching before you setting the SuperAgent hierarchy.
Creating a hierarchy of SuperAgents
You can use the Repository policy to create the hierarchy. It is recommended to have a three level
hierarchy of SuperAgents in your network.
Creating a hierarchy of SuperAgent avoids repetitive download of the content update from the ePolicy
Orchestrator server or distributed repository. For example, in a client network with two SuperAgents
(SuperAgent 1 and SuperAgent 2) and a distributed repository, configure the hierarchy in such a way
that the client systems receives the content updates from the SuperAgent 1. The SuperAgent 1
receives and caches updates from SuperAgent 2, then the SuperAgent 2 receives and caches updates
from the distributed repository.
The SuperAgents cannot cache content from McAfee HTTP or FTP repositories.
When creating a hierarchy, ensure that the hierarchy doesn't form a cycle of SuperAgent; for example
SuperAgent 1 is configured to pull updates from SuperAgent 2, SuperAgent 2 is configured to pull
updates from SuperAgent 3, and SuperAgent 3 in turn is configured to pull updates from SuperAgent
1.
Working with the agent from the McAfee ePO server
SuperAgents and how they work
7
McAfee
®
Agent 4.8.0 Product Guide
71
- Agent 4.8.0 1
- COPYRIGHT 2
- TRADEMARK ATTRIBUTIONS 2
- LICENSE INFORMATION 2
- License Agreement 2
- Contents 3
- Using the agent 4
- 9 Agent activity logs 87 5
- Index 89 5
- About this guide 7
- Find product documentation 8
- Introducing McAfee Agent 9
- Agent 4.8.0 Product Guide 10
- About the McAfee Agent 11
- SuperAgent 12
- Agent Handler 12
- Installing, upgrading, and 13
- Installing the agent 15
- Supported languages 17
- Installation vs. deployment 18
- Deploying the agent 19
- Default requiretty 21
- PermitRootLogin Yes 21
- Agent installation folder 22
- Orchestrator 24
- Install the help extension 25
- Agent installation package 25
- Manage Agent Deployment URLs 27
- Install on Windows systems 33
- Install on Windows manually 35
- $chmod +x ./installdeb.sh 40
- $sudo ./installdeb.sh ‑i 40
- Correct duplicate agent GUIDs 41
- Upgrading vs. updating 43
- Macintosh systems 46
- Removing the McAfee Agent 51
- Configuring agent policies 57
- Repository policies 58
- Troubleshooting policies 58
- Priority event forwarding 59
- Retrieve system properties 59
- Select a repository 60
- Proxy settings for the agent 61
- Repository Package Management 62
- Wake-up calls and tasks 67
- SuperAgents and how they work 68
- Convert agents to SuperAgents 69
- How the cache works 70
- When the cache is flushed 70
- SuperAgent and its hierarchy 71
- Agent relay capability 73
- Respond to policy events 75
- Run client tasks immediately 76
- Locate inactive agents 77
- Agent properties 78
- Using the system tray icon 81
- Run a manual update 83
- Enforce policies 83
- Update policies and tasks 83
- Agent command-line options 85
- Command‑line options 86
- Agent activity logs 87
Produits connexes et manuels pour Logiciel Red Hat LINUX VIRTUAL SERVER 4.6 - ADMINISTRATION
(29 pages)© 2020, manymanuals.fr. Tous droits réservés | 0.017 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels