A defense group identifies a collection of AntiDDoS devices and their networking relationship. If an AntiDDoS is deployed in out-of-path mode, traffic diversion can be implemented only after the detecting device and cleaning device are added to the same defense group. By default, all detecting and cleaning devices are added to the same defense group.
If a detecting device not in any defense group detects abnormal traffic, the device will divert the traffic to cleaning devices that do not belong to any defense group.
Create |
Click |
Modify |
Click |
Delete |
|
View |
|
Devices that serve as cleaning devices or detecting devices have been discovered and synchronized.
.
Parameter |
Description |
Value |
|---|---|---|
Name |
Indicates the name of the defense group. |
The collector name contains a maximum of 64 characters. It can contain letters, digits and special characters _ - * ? ! = + @. The value cannot be null (case insensitive). |
Detecting Mode |
Indicates the detecting mode when two or more detecting devices work together. |
If two or more detecting devices are adopted for collaboration, you need to select the value of this parameter. In other cases, skip this item. The following detecting modes are available:
|
Description |
Indicates remarks information for identifying a defense group. |
The value contains a maximum of 255 characters. |
.After successfully added, the device is displayed in the device list on the Create Defense Group page.
to delete the device; you can select the check box on the title bar and click
to delete all devices.When multiple layers of defense groups are deployed on various locations of the network, you can associate downstream defense groups with upstream ones for coordinated traffic diversion. After coordinated traffic diversion is enabled, once the downstream defense groups detect traffic anomalies, the ATIC can enable the upstream defense groups to perform traffic diversion and defense.
.