Creating App Connectors in Azure

To create an app connector

1. In the Access > App Connector page, click New.

2. Enter the information in the General section, such as name and location.

3. Under Type, click Virtual.

4. In the Connector Group section, select an existing group from the list or enter a name to create a new group.

5. Under Preferred PoPs, use the toggle to determine if you want the connector to use the preferred PoPs configured for the account (default), or manually enter the PoPs to which the connector should attempt to connect.

6. Click Apply.

To deploy an app connector in Azure

1. From the Azure Marketplace, search for Cato, and select the Cato App Connector.

2. In the Overview screen, select the Plan and Subscription for the Azure resources, and then click Create.

3. In the Basics screen, define the following settings for the resources and costs:

   • Subscription - Billing account for the Azure resources

   • Resource group - Azure resource group that the app connector resources are associated to

   • Region - Azure region for the app connector resource

   • Resource prefix - optional prefix to add to each of the app connector resources

4. In the Networking screen, first determine if you want to work with 2 or 3 NICs.

   

   • 2 NIC deployments use the Standard_D2s_v5 instance type

   • 3 NIC deployments use the Standard_D8ls_v5 instance type

     Note

     Note: By default, 3 NIC vSockets support up to 2Gb throughput with the Azure Accelerated Networking option enabled.

   These are the app connector subnets (minimum subnet address space of /28):

   • MGMT subnet (3 NIC deployments, only) – Management communication between the app connector and the Azure API

   • WAN subnet - External WAN traffic for the app connector (Internet and Cato Cloud)

   • LAN subnet - Internal Azure resources and traffic that are connected to the app connector

5. In the Cato AppConnector Configuration screen, define the following settings for the app connector based on the app connector that you created in the Cato Management Application, above.

   

   • AppConnector Serial Number (S/N) - Paste the S/N that you copied from the Access > App Connectors page.

   • AppConnector Name - Enter the name for the VM that hosts the app connector.

     The AppConnector Name can't include spaces or Azure-restricted characters.

   • WAN interface IP allocation – Select a Dynamic or Static internal IP address for the WAN interface. For Static IP allocation, you can allocate any IP address.

   • MGMT interface IP allocation (3 NIC deployments, only) – Select a Dynamic or Static internal IP address for the MGMT interface. For Static IP allocation, you can allocate any IP address.

6. In the Optional Configuration screen, you can choose to define these settings:

   

   • Public IP addresses for the WAN and/or MGMT (3 NIC deployments, only) interfaces

   • Network Security Groups for the WAN, MGMT (3 NIC deployments, only), and/or LAN interfaces

   • Availability Options for the app connector:

     • Azure Availability Set - Create new or use an existing one

       Note: The Availability Set must be in the same Resource Group as the app connector

     • Azure Availability Zone - Select an Availability Zone in the range of 1 - 3

   For more information about these settings, see above ???.

7. In the Review + create screen, review the app connector settings and then click Create.

   After the app connector resources are deployed, it automatically connects to the Cato Cloud and checks if it's necessary to upgrade to the newest version. The Cato Management Application notification area shows messages regarding the status of connecting the app connector.

   You can see your app connectors in the Access > App Connectors page.