D-Link DES-3828 Product Manual - Page 351

Safeguard Engine, config safeguard_engine

Page 351 highlights

xStack DES-3800 Series Layer 3 Stackable Fast Ethernet Managed Switch CLI Manual 50 SAFEGUARD ENGINE Periodically, malicious hosts on the network will attack the Switch by utilizing packet flooding (ARP Storm) or other methods. These attacks may increase the CPU utilization beyond its capability. To alleviate this problem, the Safeguard Engine function was added to the Switch's software. The Safeguard Engine can help the overall operability of the Switch by minimizing the workload of the Switch while the attack is ongoing, thus making it capable to forward essential packets over its network in a limited bandwidth. When the Switch either (a) receives too many packets to process or (b) exerts too much memory, it will enter an Exhausted mode. When in this mode, the Switch only receives a small amount of ARP and IP broadcast packets for a calculated time interval. Every five seconds, the Switch will check to see if there are too many packets flooding the Switch. If the threshold has been crossed, the Switch will initially limit and accept a small amount of ingress ARP and IP broadcast packets for five seconds. After another five-second checking interval arrives, the Switch will again check the ingress flow of packets. If the flooding has stopped, the Switch will again begin accepting all packets. Yet, if the checking shows that there continues to be too many packets flooding the Switch, it will still accept a small amount of ARP and IP broadcast packets for double the time of the previous stop period. This doubling of time for limiting ingress ARP and IP broadcast packets will continue until the maximum time has been reached, which is 320 seconds and every stop from this point until a return to normal ingress flow would be 320 seconds. Once in Exhausted mode, the packet flow will decrease by half of the level that caused the Switch to enter Exhausted mode. After the packet flow has stabilized, the rate will initially increase by 25% and then return to a normal packet flow. The Safeguard Engine commands in the Command Line Interface (CLI) are listed (along with the appropriate parameters) in the following table. Command config safeguard_engine show safeguard_engine Parameters {state [enable | disable] | cpu_utilization {rising_threshold | falling_threshold } | trap_log [enable | disable]} Each command is listed, in detail, in the following sections. config safeguard_engine Purpose Syntax Description Parameters Restrictions Used to configure the Safeguard Engine for the Switch. config safeguard_engine {state [enable | disable] | cpu_utilization {rising_threshold | falling_threshold } | trap_log [enable | disable]} This command is used to configure the settings for the CPU Safeguard Engine function of this Switch, based on CPU utilization. state [enable | disable] - Select the running state of the Safeguard Engine function as enable or disable. cpu_utilization - Select this option to trigger the Safeguard Engine function to enable based on the following determinates: • rising - The user can set a percentage value of the rising CPU utilization which will trigger the CPU protection function. Once the CPU utilization rises to this percentage, the Safeguard Engine mechanism will initiate. • falling - The user can set a percentage value of the falling CPU utilization which will trigger the CPU protection function to cease. Once the CPU utilization falls to this percentage, the Safeguard Engine mechanism will shut down. trap_log [enable | disable] - Choose whether to enable or disable the sending of messages to the device's SNMP agent and switch log once the Safeguard Engine has been activated by a high CPU utilization rate. Only Administrator or Operator-level users can issue this command. Example usage: 347

  • 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
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452

xStack DES-3800 Series Layer 3 Stackable Fast Ethernet Managed Switch CLI Manual
347
50
S
AFEGUARD
E
NGINE
Periodically, malicious hosts on the network will attack the Switch by utilizing packet flooding (ARP Storm) or other methods. These
attacks may increase the CPU utilization beyond its capability. To alleviate this problem, the Safeguard Engine function was added to
the Switch’s software.
The Safeguard Engine can help the overall operability of the Switch by minimizing the workload of the Switch while the attack is
ongoing, thus making it capable to forward essential packets over its network in a limited bandwidth. When the Switch either (a)
receives too many packets to process or (b) exerts too much memory, it will enter an
Exhausted
mode. When in this mode, the
Switch only receives a small amount of ARP and IP broadcast packets for a calculated time interval. Every five seconds, the Switch
will check to see if there are too many packets flooding the Switch. If the threshold has been crossed, the Switch will initially limit
and accept a small amount of ingress ARP and IP broadcast packets for five seconds. After another five-second checking interval
arrives, the Switch will again check the ingress flow of packets. If the flooding has stopped, the Switch will again begin accepting all
packets. Yet, if the checking shows that there continues to be too many packets flooding the Switch, it will still accept a small amount
of ARP and IP broadcast packets for double the time of the previous stop period. This doubling of time for limiting ingress ARP and
IP broadcast packets will continue until the maximum time has been reached, which is 320 seconds and every stop from this point
until a return to normal ingress flow would be 320 seconds.
Once in Exhausted mode, the packet flow will decrease by half of the level that caused the Switch to enter Exhausted mode. After the
packet flow has stabilized, the rate will initially increase by 25% and then return to a normal packet flow.
The Safeguard Engine commands in the Command Line Interface (CLI) are listed (along with the appropriate parameters) in the
following table.
Command
Parameters
config safeguard_engine
{state [enable | disable] | cpu_utilization {rising_threshold <value 20-100> |
falling_threshold <value 20-100>} | trap_log [enable | disable]}
show safeguard_engine
Each command is listed, in detail, in the following sections.
config safeguard_engine
Purpose
Used to configure the Safeguard Engine for the Switch.
Syntax
config safeguard_engine {state [enable | disable] | cpu_utilization
{rising_threshold <value 20-100> | falling_threshold <value 20-100>} |
trap_log [enable | disable]}
Description
This command is used to configure the settings for the CPU Safeguard Engine
function of this Switch, based on CPU utilization.
Parameters
state [enable | disable]
– Select the running state of the Safeguard Engine function
as enable or disable.
cpu_utilization
– Select this option to trigger the Safeguard Engine function to
enable based on the following determinates:
rising <value 20-100>
- The user can set a percentage value of the rising
CPU utilization which will trigger the CPU protection function. Once the
CPU utilization rises to this percentage, the Safeguard Engine
mechanism will initiate.
falling <value 20-100>
- The user can set a percentage value of the
falling CPU utilization which will trigger the CPU protection function to
cease. Once the CPU utilization falls to this percentage, the Safeguard
Engine mechanism will shut down.
trap_log [enable | disable]
– Choose whether to enable or disable the sending of
messages to the device’s SNMP agent and switch log once the Safeguard Engine
has been activated by a high CPU utilization rate.
Restrictions
Only Administrator or Operator-level users can issue this command.
Example usage: