The System Settings window lets you configure these settings:
-
Default TCP acceleration
-
Static range translation
-
Configuration validation
You can define if TCP acceleration should be enabled by default for network rules.
-
For a description of acceleration in the Cato Cloud, see Accelerating and Optimizing Traffic.
-
For information on overriding the acceleration default setting in network rules, see Configuring Network Rules.
You always have the option to change the default acceleration settings for network rules.
Note
Note: TCP acceleration does not affect non-TCP traffic (UDP-based traffic) that is part of a network rule).
To enable TCP acceleration by default in network rules:
-
From the navigation menu, click Administration > System Settings.
-
In the Default Acceleration Settings section, select from these options:
-
TCP Proxy for Internet - Enables acceleration by default for new Internet network rules
-
TCP Proxy for WAN - Enable acceleration by default when WAN network rules are created.
-
-
Click Save.
In some networks, two or more sites may use identical IP address ranges. This is common in hub-and-spoke topologies where multiple branches need to access a shared data center but do not need to communicate with each other.
Since Cato "flattens" the network and eliminates inter-LAN NAT commonly used by older solutions, IP range duplication is, in principle, prohibited. However, you can keep duplicate IP ranges when needed by activating Static Range Translation. This performs a many-to-many translation for specific networks.
Note
Note: To enable overlapping networks to communicate with each other, they must be translated by activating and configuring Static Range Translation on all relevant networks.
In a translated network, the translation occurs at the Cato PoP to which the site is connected. This means that hosts within the network keep using their real IPs, but traffic between them and hosts outside this network uses their translated IPs.
If you define static hosts in this network, the Cato Management Application automatically displays the translated IP for these hosts, in case it needs to be reached from outside the local network.
Note
Note: All other configuration options in the Cato Management Application that are not specific to this network (such as groups, firewalls, network rules, and so on) are only aware of the translated IPs. All references (such as analytics and event logs) to this network and its hosts always use the translated IPs.
First enable static range translation for your account, and then configure the translated IPs for the relevant network ranges.
Note
Important:
-
Do not use static range translation on network ranges that include AD or DNS servers, or where FTP or SIP protocols are used
-
After enabling static range translation for your account, Alt. WAN recovery, Alt. WAN transport, and WAN recovery are automatically disabled for sites that define a static NAT for the native range
-
BGP isn't supported for accounts that use static range translation
After you enable static range translation for the account, configure the translated IP range for the network rules. The default translated IP range is the same as the real IP range.
-
The real and translated ranges must have the same CIDR notation
-
The translated range must be unique and you cannot use it in other places in the account
To define static range translation:
-
From the navigation menu, click Network > Sites.
-
From the list of sites, select the site you are defining the static range translation settings.
-
From the navigation menu, click Site Configuration > Networks.
-
Click the IP range Type to edit it. The Edit IP range panel opens.
-
In Static NAT, enter the translated IP address range for this network IP range.
-
Click Apply. The Edit IP Range panel closes.
-
Click Save.
If your organization uses public IP ranges inside your organization LAN, you need to disable the Prevent use of public IP addresses and ranges in sites option so that the IP address validation mechanism allows this.
Degraded connectivity status indicates when a Socket or port are experiencing some issues. You can also choose to display the Degraded status only for sites with issues that occurred within the past 30 days. Sites whose issues are older than 30 days will then appear as Connected.
When disabled, Degraded status is not shown on relevant pages.
To toggle the site Degraded status:
-
From the navigation menu, click Administration > System Settings.
-
In the Site Degraded Status section, use the toggle to enable or disable the Degraded status (green is enabled, grey is disabled).
-
(Optional) To make sure that Degraded status is only shown for recent issues, select Don't trigger a Degraded Status for failures that were detected more than 30 days ago.
-
Click Save.
0 comments
Please sign in to leave a comment.