Cato launched a second PoP location in Tokyo in early May and in Osaka in mid-June. With the introduction of these new PoPs, we recommend the following configuration changes for your customers.

These recommendations are designed to improve redundancy and resiliency of the solution through optimal configuration.

Changes to Site Configuration

• Our best practice configuration is to always let Cato decide the best PoP and so we recommend that you change preferred Primary and Secondary PoP location to Automatic. This lets Cato always decide the optimal connection for each site, which takes into account various parameters, such as: proximity to the site and load condition on the PoP.
• If that’s not an option for you, we recommend changing the Primary and Secondary location for customers based in
  • Eastern Japan, as follows:
    • Primary Location – Tokyo_DC2
    • Secondary Location – Tokyo
  • Western Japan, as follows
    • Primary Location – Osaka_DC2
    • Secondary Location – Osaka
  • Finally, if you prefer to have a secondary location that is geographically distant from your primary location (for example for natural disaster resiliency), we recommend changing the Primary and Secondary location for customers based in
    • Eastern Japan, as follows:
      • Primary Location – Tokyo_DC2
      • Secondary Location – Osaka_DC2 (or Osaka)
    • Western Japan, as follows
      • Primary Location – Osaka_DC2
      • Secondary Location – Tokyo_DC2 (or Tokyo)

Changes to Egress Settings for Network Rules

• If you are using Route via egress Network Rules with egress in either Tokyo or Osaka, we recommend adding the Tokyo_DC2 and/or Osaka_DC2 location to the rule. This is because, should there be an issue with the PoP from which you’re egressing, Cato would have options to automatically route via other PoPs. In addition, SDP users connecting to a given POP will be able to take advantage of a more direct egress route, by avoiding an unnecessary hop to another PoP.
• If you are using the NAT option with a public IP address from the Tokyo or Osaka PoP, we recommend allocating a public IP from the Tokyo_DC2 and/or Osaka_DC2 PoP and adding it to the rule. This is because, should there be an issue with the PoP hosting the egress IP, Cato would have options to automatically route via IP addresses hosted in other PoPs. In addition, SDP users connecting to a given PoP will take advantage of a more direct egress route, by avoiding an unnecessary hop to another PoP. If you need incremental IP addresses, please reach out to your Cato representative.

Who Do I Talk to If I Have Questions?

Please contact Support, or your authorized Cato representative.