
Perform the following steps to create a new zone:
Expand the Overview section and enter the following information:
|
Fields |
Purpose |
| Zone Name |
Enter the name of the zone. Once a zone name is set, it cannot be modified. A zone name must contain only the alphanumeric characters (a-z, A-Z, 0-9) and the special characters such as period (.), hyphen (-), and underscore (_). |
| Description | Enter a description to the zone name. |
| IP Address(es) | Enter the IPv4 or IPv6 address and subnet for the zone. To enter multiple IPs, enter one IP per line. |
| Use Config Profile | Select a zone configuration profile. |
| Operational Mode | Select an operational mode to use with the zone. |
| Operational Policy | Select an operational policy to use with the zone. |
| Mitigator Group | Select a group of mitigation devices that acts as a mitigator. |
| Detector Group | Select a group of detection devices. To create a detection group, see Device Groups. |
| Use Config Profile |
Select a Zone Config Profile. Zone Config Profile is a configuration profile that contains the common DDoS protection configurations at the zone and zone service levels. It allows user to define common countermeasure profile once and reuse it in multiple zones. |
Expand the Mitigation section and enter the following information:
| NOTE: | Hardware-assisted Traffic Blocking leverages the hardware chipset for traffic that goes beyond a threshold limit. When the packet drop rate exceeds the default threshold, for example—during a volumetric attack, packets get dropped in hardware rather than the CPU, this feature allows TPS to drop packets at a higher rate. It enables the CPU to focus exclusively on packets requiring further processing. This feature has some limitations. For detailed information about this feature and its limitations, see ACOS 3.2.5-P1 TPS New Features and Enhancements. |
Expand the Detection section and enter the following:
Expand the Source Ports section, click the Plus (+) sign to see further options:
|
Fields |
Purpose |
|---|---|
|
Protocol |
Select TCP or UDP as a protocol. |
|
Port/Range |
Enter a port or port range. When a port range is entered, specify the lower port number followed by a Hyphen (-) and then the highest port number. |
|
GLID |
Select a Configure a GLID for rate limiting. |
|
Template |
Select a template from the list. |
|
Deny |
Select Deny to drop and black-list matching inbound traffic. The black-list setting is permanent and static, and changes only if this configuration changes. |
| NOTE: | You can either perform step 8 or step 11. They are mutually exclusive. |
Expand the Services section, configure the protocol services and the designated ports for such services in the appropriate fields.
Click the Plus (+) sign to configure the additional services. Some standard protocols are pre-configured with the appropriate port number. The following is the list of Services supported:
| NOTE: | SIP over TCP is only supported in asymmetric mode. |
| NOTE: | For more information about the threshold indicators available for the protocol services, see Indicator Settings. |
Depending upon the type of Zone Service, click Edit for a configured service to edit a Zone Service.
The Edit Zone Service for the selected protocol appears. For more information, see Configure a Zone Service Protection Profile.
If Protocol Num 50 is configured as the zone service, ESP Inspect is available to allow configuration of ESP payload parameters with one of the following Auth Algorithms.
Under Pattern Recognition (ZAPR):
|
Fields |
Purpose |
|---|---|
|
Start Pattern Recognition |
|
|
Apply Extracted Filters |
Select a zone service level at which the extracted signature extraction filters are applied on the incoming traffic and the packets that match the filters are dropped. To monitor the dropped packets and packet rates, go to Mitigation > Zone Mitigation Console. |
|
Triggered By |
Select from the following options:
You can trigger the pattern recognition when a packet rate threshold exceeds a global limit ID (GLID) or when there is zone escalation. If the option is not specified, by default the trigger is when a rate threshold exceeds a GLID. |
|
Capture Traffic |
Select from the following options:
You can capture all traffic or capture only the dropped traffic for the purpose of extracting a ZAPR filter. If the option is not specified, the default behavior will capture only the dropped traffic. |
| NOTE: | The Triggered By and Capture Traffic options are applicable only when the TPS v5.0.2 device is used. |
Depending on the protocol selected, policy levels are configurable. A zone service configuration can have up to 5 levels that start at zero and escalate to 4. Click on the downward arrow on the Level 0 row if it exists.
Click on Plus (+) sign to add further indicator configuration for the zone service. To enter the appropriate information in the indicator configuration, see Configure a Zone Service Protection Profile.
Perform one of the following actions:
After a zone is created, the edit zone configuration page displays the Zone Charts button, which navigates you to the Zone Charts page in a new browser tab.
Depending on your topology, operational mode may be used to build a baseline for traffic thresholds for your zone services. To access the operational mode functions, go to the Configuration > Protected Objects > Zones and then select Learn from Operational Mode drop-down to get a traffic baseline for your zone. For more information see Operational Mode - Learning.