Patton BODi rS 1000 Series, Руководство пользователя, Страница: 62 / 158

Creating Custom Rules for the Outbound Policy 62
BODi rS BD1000 User Manual 5 • Managing Outbound Traffic to the WAN
New Custom Rule Settings
Table 26. Outbound Policy: Custom Rule Settings
Field Description
Service Name Specifies the name of the custom rule.
Enable Specifies whether the outbound traffic rule takes effect.
Click
Yes to enable the outbound traffic rule. When enabled, the BD1000
matches traffic and takes action based on the other parameters of the rule.
Click
No
to disable the outbound traffic rule. When disabled, the BD1000
disregards the other parameters of the rule.
Source Specifies the source IP Address, IP Network or MAC Address for outbound
traffic that matches the rule.
Destination Specifies the destination IP Address or IP Network for outbound traffic that
matches the rule.
Protocol and Port Specifies the IP Protocol and Port of outbound traffic that matches this rule.
Click the drop-down menu for the
Protocol Selection Tool to choose a
common protocol.
Algorithm Specifies the behavior of the BD1000 for the custom rule. Available options:
• Weighted Balance (see “Algorithm: Weighted Balance” on page 63)
•
Persistence (see
“Algorithm: Persistence”
on page 63)
•
Enforced
(see “Algorithm: Enforced” on page 65)
•
Priority (see
“Algorithm: Priority”
on page 65)
• Overflow (see “Algorithm: Overflow” on page 66)
•
Least Used (see
“Algorithm: Least Used”
on page 66)
• Lowest Latency (see “Algorithm: Lowest Latency” on page 67)
Terminate Sessions on
Link Recovery Specifies whether to terminate existing IP sessions on a less preferred WAN
connection in the event that a more preferred WAN connection is recovered.
This setting only applies to the
Weighted Balance , Persistence and
Priority options.
By default, this option is disabled. When disabled, all existing IP sessions will
not be terminated or affected when any other WAN connection is recovered.
When enabled, existing IP sessions may be terminated when another WAN
connection is recovered, so that only the preferred healthy WAN connec-
tion(s) are used at any point in time.