Symantec 10521146 Administration Guide - Page 174

Maximum IPv4 Fragment Reassembly Table Elements, TCP Maximum Flow Table Elements (Fast Ethernet)

Page 174 highlights

174 Detecting Configuring sensor detection Maximum IPv4 Fragment Reassembly Table Elements Maximum IPv4 Fragment Reassembly Table Elements regulates the size of IP fragment tables by controlling the number of simultaneous IP fragments that the sensor handles. It directly impacts memory consumption. Each fragment table entry can consume slightly more than 64K of memory. The default is set to 2,048 for optimum performance and sensitivity, and does not need to be changed under most circumstances. Valid values range from 32 to 32,768, inclusive. If you receive an operational log message indicating that the IPv4 Fragment Reassembly Table is full, you can eliminate the message by increasing this value, at the cost of greater memory consumption. If the system is running low on RAM, you can decrease this value, at the cost of reducing detection sensitivity because sensors have less traffic to inspect. Consider changing it only if you have a thorough understanding of its functionality. TCP Maximum Flow Table Elements (Fast Ethernet) TCP Maximum Flow Table Elements (Fast Ethernet) regulates the size of the TCP flow table by controlling the number of simultaneous flows that the fast Ethernet sensor handles. It has a direct impact on memory consumption. The default is set to 32,768 for optimum performance and sensitivity, and does not need to be changed under most circumstances. Valid values range from 16,384 (16K) to 262,144 (256K). If you receive an operational log message indicating that the TCP Flow Table is full, you can eliminate the message by increasing this value, at the cost of greater memory consumption. Consider changing it only if you have a thorough understanding of its functionality. TCP Maximum Flow Table Elements (Gigabit) TCP Maximum Flow Table Elements (Gigabit) regulates the size of the TCP flow table by controlling the number of simultaneous flows that the gigabit sensor handles. It has a direct impact on memory consumption. The default is set to 131,072 for optimum performance and sensitivity, and does not need to be changed under most circumstances. Valid values range from 32,768 (32K) to 1,048,576 (1M), inclusive. If you receive an operational log message indicating that the TCP Flow Table is full, you can eliminate the message by increasing this value, at the cost of greater memory consumption. Consider changing it only if you have a thorough understanding of its functionality.

  • 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
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392

174
Detecting
Configuring sensor detection
Maximum IPv4 Fragment Reassembly Table Elements
Maximum IPv4 Fragment Reassembly Table Elements
regulates the size of IP
fragment tables by controlling the number of simultaneous IP fragments that
the sensor handles. It directly impacts memory consumption. Each fragment
table entry can consume slightly more than 64K of memory.
The default is set to 2,048 for optimum performance and sensitivity, and does
not need to be changed under most circumstances. Valid values range from 32 to
32,768, inclusive. If you receive an operational log message indicating that the
IPv4 Fragment Reassembly Table is full, you can eliminate the message by
increasing this value, at the cost of greater memory consumption. If the system
is running low on RAM, you can decrease this value, at the cost of reducing
detection sensitivity because sensors have less traffic to inspect. Consider
changing it only if you have a thorough understanding of its functionality.
TCP Maximum Flow Table Elements (Fast Ethernet)
TCP Maximum Flow Table Elements (Fast Ethernet)
regulates the size of the TCP
flow table by controlling the number of simultaneous flows that the fast
Ethernet sensor handles. It has a direct impact on memory consumption.
The default is set to 32,768 for optimum performance and sensitivity, and does
not need to be changed under most circumstances. Valid values range from
16,384 (16K) to 262,144 (256K). If you receive an operational log message
indicating that the TCP Flow Table is full, you can eliminate the message by
increasing this value, at the cost of greater memory consumption. Consider
changing it only if you have a thorough understanding of its functionality.
TCP Maximum Flow Table Elements (Gigabit)
TCP Maximum Flow Table Elements (Gigabit)
regulates the size of the TCP flow
table by controlling the number of simultaneous flows that the gigabit sensor
handles. It has a direct impact on memory consumption.
The default is set to 131,072 for optimum performance and sensitivity, and does
not need to be changed under most circumstances. Valid values range from
32,768 (32K) to 1,048,576 (1M), inclusive. If you receive an operational log
message indicating that the TCP Flow Table is full, you can eliminate the
message by increasing this value, at the cost of greater memory consumption.
Consider changing it only if you have a thorough understanding of its
functionality.