McAfee EPOCDE-AA-BA Product Guide - Page 152

SuperAgent caching and communication interruptions, SuperAgent deployment tips, How the cache works

Page 152 highlights

13 Working with the agent from the McAfee ePO server Agent-server communication SuperAgent deployment tips To deploy enough SuperAgents to the appropriate locations, first determine the broadcast segments in your environment and select a system (preferably a server) in each segment to host a SuperAgent. Be aware that agents in broadcast segments without SuperAgents do not receive the broadcast wake-up call, so they do not call in to the server in response to a wake-up call. If you use SuperAgents, make sure all agents are assigned a SuperAgent. Agent and SuperAgent wake-up calls use the same secure channels. Make sure the following ports are not blocked by a firewall on the client: • The agent wake-up communication port (8081 by default). • The agent broadcast communication port (8082 by default). SuperAgent caching and communication interruptions The SuperAgent caches the contents of its repository in a specific manner designed to minimize wide-area network (WAN) usage. If an agent has been converted to a SuperAgent, it can cache content from its McAfee ePO server to distribute locally to other agents, reducing WAN bandwidth. To activate this, turn on LazyCaching in the McAfee Agent | General policy options page which you access from Menu | Policy | Policy Catalog. How the cache works When a client system first requests content, the SuperAgent assigned to that system caches that content. From that point on, the cache is updated whenever a newer version of the package requested is available in the Master Repository. The SuperAgent is guaranteed only to store content required by the agents assigned to it because it does not pull any content from the McAfee ePO server until requested from a client. This minimizes traffic between the SuperAgent and the McAfee ePO server. While the SuperAgent is retrieving content from the Master Repository, client system requests for that content are paused. The SuperAgent must have access to the Master Repository. Without this access, agents receiving updates from the SuperAgent never receive new content. Make sure your SuperAgent policy includes access to the Master Repository. Agents configured to use the SuperAgent as their repository receive the content cached in the SuperAgent repository instead of directly from the McAfee ePO server. This improves agent system performance by keeping the majority of network traffic local to the SuperAgent and its clients. If the SuperAgent is reconfigured to use a new repository, the cache is updated to reflect the new repository. When the cache is flushed SuperAgents flush content from their cache in two situations. • 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 fushes the cache if any new content is available. • When a global update occurs, SuperAgents receive a wakeup call that flushes all content in the cache. 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. 152 McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

SuperAgent deployment tips
To deploy enough SuperAgents to the appropriate locations, first determine the broadcast segments in
your environment and select a system (preferably a server) in each segment to host a SuperAgent. Be
aware that agents in broadcast segments without SuperAgents do not receive the broadcast wake-up
call, so they do not call in to the server in response to a wake-up call. If you use SuperAgents, make
sure all agents are assigned a SuperAgent.
Agent and SuperAgent wake-up calls use the same secure channels. Make sure the following ports are
not blocked by a firewall on the client:
The agent wake-up communication port (8081 by default).
The agent broadcast communication port (8082 by default).
SuperAgent caching and communication interruptions
The SuperAgent caches the contents of its repository in a specific manner designed to minimize
wide-area network (WAN) usage.
If an agent has been converted to a SuperAgent, it can cache content from its McAfee ePO server to
distribute locally to other agents, reducing WAN bandwidth. To activate this, turn on
LazyCaching
in the
McAfee Agent
|
General
policy options page which you access from
Menu
|
Policy
|
Policy Catalog
.
How the cache works
When a client system first requests content, the SuperAgent assigned to that system caches that
content. From that point on, the cache is updated whenever a newer version of the package requested
is available in the Master Repository.
The SuperAgent is guaranteed only to store content required by the agents assigned to it because it
does not pull any content from the McAfee ePO server until requested from a client. This minimizes
traffic between the SuperAgent and the McAfee ePO server. While the SuperAgent is retrieving content
from the Master Repository, client system requests for that content are paused.
The SuperAgent must have access to the Master Repository. Without this
access, agents receiving updates from the SuperAgent never receive
new content. Make sure your SuperAgent policy includes access to the
Master Repository.
Agents configured to use the SuperAgent as their repository receive the content cached in the
SuperAgent repository instead of directly from the McAfee ePO server. This improves agent system
performance by keeping the majority of network traffic local to the SuperAgent and its clients.
If the SuperAgent is reconfigured to use a new repository, the cache is updated to reflect the new
repository.
When the cache is flushed
SuperAgents flush content from their cache in two situations.
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
fushes the cache if any new content is available.
When a global update occurs, SuperAgents receive a wakeup call that flushes all content in the cache.
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.
13
Working with the agent from the McAfee ePO server
Agent-server communication
152
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide