Transit FireNet Workflow for GCP

You use Aviatrix Transit FireNet to deploy firewall functions for the Aviatrix Multi-Cloud transit architecture. With Transit FireNet feature, the Firewall Network (FireNet) function is integrated into the Aviatrix Transit gateway.

To learn about Transit FireNet, see Transit FireNet FAQ.

If you want to deploy firewall networks in AWS Transit Gateway (TGW) environment, your starting point is here..

In this example, Transit VPC with Aviatrix Gateways is deployed, and two Spoke Gateways (DEV and PROD) are attached.

A firewall of supported vendors (Checkpoint, Palo Alto Networks and Fortinet etc.) will be deployed within the Transit VPC. See the diagram below for more details.

Once the infrastructure is in place the policy to inspect the east-west and north-south traffic will be created.

avx_tr_firenet_topology

Step 1 : Create VPCs

VPCs can be created manually on GCP or directly from Aviatrix Controller.

See Create a VPC for guidelines on how to use the Aviatrix Controller to create VPCs.

  1. Login to the Aviatrix Controller with username and password.
  2. Navigate to Useful Tools -> Create A VPC
  3. Add one VPC for Transit FireNet Gateway and provide Aviatrix FireNet VPC Subnet as shown below.
  4. Add three more VPCs as shown in Topology i.e Egress VPC, LAN VPC and Management VPC.
  5. Create two more VPCs for Spoke Gateways.

create_vpc

Step 2: Deploy the Transit Aviatrix Gateway

Transit Aviatrix Gateway can be deployed using the Transit Gateway Workflow

Procedure

  1. Navigate to MULTI-CLOUD TRANSIT -> Setup -> #1 Launch an Aviatrix Transit Gateway
  2. Select the Cloud Type Gcloud
  3. Select VPC ID Transit FireNet VPC
  4. Choose instance size n1-standard-1
  5. Enable ActiveMesh Mode (Mandatory)
  6. Check Enable Transit FireNet Function checkbox and provide LAN VPC ID Transit FireNet LAN VPC
  7. Enable InsaneMode for higher throughputs (optional)
  8. Choose correct Account, Public Subnet and click Create
  9. Enable Transit Gateway HA by navigating to MULTI-CLOUD TRANSIT -> Setup -> #2 (Optional) Enable HA to an Aviatrix Transit Gateway

Please see an example below for Transit FireNet GW:

tr_firenet_gw

Step 3: Deploy Spoke Gateways

Now that we have set up an Aviatrix Transit Gateway, we can deploy Aviatrix Spoke Gateways in the spoke VPCs using Aviatrix Spoke Gateway Workflow.

  1. Navigate to MULTI-CLOUD TRANSIT -> Setup -> #4 Launch an Aviatrix Spoke Gateway
  2. Deploy a Spoke Gateway (GW) in each of the spoke VPCs using defaults while choose correct Account and VPC info
  3. Choose the Public Subnet
  4. Enable Spoke Gateway HA by navigating to MULTI-CLOUD TRANSIT -> Setup -> #5 (Optional) Enable/Disable HA at Spoke GW

launch_spk_gw

Step 4: Attach Spoke Gateways to Transit Network

The transit and spoke gateways are now deployed. To connect them:

  1. Navigate to MULTI-CLOUD TRANSIT -> Setup -> #6a Attach Spoke Gateway to Transit Network
  2. Select one spoke at a time and attach to the Transit Gateway.

attach_spk_trgw

Note

Although the Transit Gateway is now attached to the Spoke Gateways, it will not route traffic between Spoke Gateways.

Step 5: Enable Connected Transit

By default, spoke VPCs are in isolated mode where the Transit will not route traffic between them. To allow the Spoke VPCs to communicate with each other, you must enable Connected Transit:

  1. Navigate to MULTI-CLOUD TRANSIT -> Advanced Config, select the right Transit Gateway and enable “Connected Transit”

connected_transit

Step 6: Configure Transit Firewall Network

Transit and Spoke Gateways have now been deployed. You must now deploy and enable the Firewall for traffic inspection.

To enable the firewall function and configure the FireNet policy:

  1. Navigate to MULTI-CLOUD TRANSIT -> Transit FireNet -> #1 Enable Transit FireNet on Aviatrix Transit Gateway
  2. Choose the Aviatrix Transit Gateway and Click “Enable”

Note

In a GCP deployment, Transit FireNet function is enabled when launching the gateway. You can skip this step.

  1. Navigate to MULTI-CLOUD TRANSIT -> Transit FireNet -> #2 Manage FireNet Policy
  2. Add spokes to the Inspected box for traffic inspection

Note

By default, FireNet inspects ingress (INET to VPC) and east-west traffic (VPC to VPC) only.

tr_firenet_policy

Step 7a: Launch and Associate Firewall Instance

This approach is recommended if this is the first Firewall instance being attached to the gateway.

This step launches a Firewall instance and associates it with one of the FireNet gateways.

Important

The Firewall instance and the associated Aviatrix FireNet gateway above must be in the same AZ (Availability Zone), and, the Management Interface Subnet and Egress (untrust dataplane) Interface Subnet should not be in the same subnet.

7a.1 Launch and Attach

From the Aviatrix Controller console, navigate to Firewall Network -> Setup -> Step 7a and provide all the required input as shown in a table. Click “Launch”.

Important

The vendor firewall may take some time to become available.

Setting Value
VPC ID The Security VPC created in Step 1.
Gateway Name The primary FireNet gateway.
Firewall Instance Name The name that will be displayed on GCP Console.
Firewall Image The AWS AMI that you subscribed to in Step 2.
Firewall Image Version Firewall instance current supported software versions.
Firewall Instance Size Firewall instance type.
Management Interface VPC ID Select the Firewall Management VPC
Management Interface Subnet Select the subnet for Firewall Management
Egress Interface VPC ID Select the Firewall Egress VPC.
Egress Interface Subnet Select the subnet for Firewall Egress.
Attach (Optional) By selecting this option, the firewall instance is inserted in the data path to receive the packet. If this is the second firewall instance for the same gateway and you have an operational FireNet deployment, you should not select this option as the firewall is not configured yet. You can attach the firewall instance later at the Firewall Network -> Advanced page.
Advanced (Optional) Click this selection to allow Palo Alto firewall bootstrap files to be specified.
Bootstrap Bucket Name In advanced mode, specify a bootstrap bucket name where the initial configuration and policy file is stored.

1. Check Point Specification

Check Point support for Google Cloud will be available in a future release.

2. Palo Alto VM-Series Specifications

Palo instance has three interfaces as described below.

Palo Alto VM instance interfaces Description Inbound Security Group Rule
nic0 Egress or Untrusted interface Allow ALL
nic1 Management interface Allow SSH, HTTPS, ICMP, TCP 3978
nic2 LAN or Trusted interface Allow ALL (Do not change)

Note that firewall instance nic2 is on the same subnet as the FireNet gateway nic1 interface.

Important

For Panorama managed firewalls, you need to prepare Panorama first and then launch a firewall. See Setup Panorama. When a VM-Series instance is launched and connected with Panorama, you need to apply a one time “commit and push” from the Panorama console to sync Panorama and the firewall instance.

Tip

If VM-Series are individually managed and integrated with the Controller, you can still use Bootstrap to save initial configuration time. Export the first firewall’s configuration to bootstrap.xml, create an IAM role and Bootstrap bucket structure as indicated above, then launch additional firewalls with IAM role and the S3 bucket name.

Follow Palo Alto Network (VM Series) GCP Example to launch VM Series firewall in GCP and for more details.

3. Fortigate Specifications

For details on how to configure Transit FireNet for GCP see <https://docs.aviatrix.com/HowTos/transit_firenet_workflow_gcp.html>`_.

Step 7b: Associate an Existing Firewall Instance

This step is the alternative step to Step 8a. If you already launched the firewall (Check Point, Palo Alto Network or Fortinet) instance from AWS Console, you can still associate it with the FireNet gateway.

Go to the Aviatrix Controller console and navigate to Firewall Network -> Setup -> Step 7b and associate a firewall with right FireNet Gateway.

Step 8: Vendor Firewall Integration

Vendor integration programs RFC 1918 and non-RFC 1918 routes in firewall appliance.

  1. Login to Aviatrix Controller’s console
  2. Go to Firewall Network -> Vendor Integration -> Select Firewall, fill in the details of your Firewall instance.
  3. Click Save, Show and Sync.

Step 9: Example Setup for “Allow All” Policy

After a firewall instance is launched, wait for 5 to 15 minutes for it to become available. Time varies for each firewall vendor. In addition, please follow the example configuration guides as indicated below to build a simple policy on the firewall instance, to validate that traffic is indeed being routed to firewall instance.

Palo Alto Network (PAN)

For basic configuration, please see example Palo Alto Network configuration guide.

For implementation details on using Bootstrap to launch and initiate VM-Series, see Bootstrap Configuration Example.

Step 10: Verification

There are multiple ways to verify if Transit FireNet is configured properly:

  1. Aviatrix Flightpath - Control-plane Test
  2. SSH, SCP or Telnet Test between Spoke VPCs (East-West) - Data-plane Test

Note

ICMP is blocked on Google Cloud Load balancer

Flight Path Test for FireNet Control-Plane Verification:

Flight Path is a very powerful troubleshooting Aviatrix tool which allows users to validate the control plane and gives end to end visibility of packet flow.

  1. Navigate to Troubleshoot-> Flight Path
  2. Provide the Source and Destination Region and VPC information
  3. Select SSH and Private subnet, and Run the test

Note

A VM instance will be required in GCP, and SSH/Telnet port should be allowed in firewall rules for Spoke VPCs.

SSH/Telnet Test for FireNet Data-Plane Verification:

Once the control plane is established and no problem is found in the security and routing polices, data plane validation needs to be verified to make sure traffic is flowing and not blocked anywhere.

There are multiple ways to check the data-plane. One way is to SSH to Spoke instance (e.g. DEV1-VM) and telnet other Spoke instance (e.g PROD1-VM) to make sure no traffic loss in the path.