Deploy the VM-Series Firewall from Google Cloud Platform Marketplace

1. Choose a Bootstrap Method.
2. Locate the VM-Series firewall listing in the Marketplace.
   1. Log in to the Google Cloud Console.
   2. From the Products and Services menu, select Marketplace.
   3. Search for VM-Series.
   4. Select one of the VM-Series firewall licensing options.
3. Click Launch on Compute Engine.
4. Name the instance and choose resources.
   1. Enter the Deployment Name (this name is displayed in the Deployment Manager). The name must be unique and cannot conflict with any other deployment in the project.
   2. Select a Zone. See Regions and Zones for a list of supported zones.
   3. Select a Machine Type based on the VM-Series System Requirements for your license and the Minimum System Requirements for the VM-Series Firewall on Google Cloud Platform.
5. Specify instance metadata.
   The options Bootstrap Bucket and Interface Swap affect the initial configuration the first time the VM-Series firewall boots.
   1. Bootstrap Bucket (Optional)—If you plan to use a bootstrap file, enter the name of a storage bucket, or the path to a folder within the storage bucket, that contains the bootstrap package. You need permission to access the storage bucket. For example:

      vmseries-bootstrap-gce-storagebucket=<bucketname>

      or

      vmseries-bootstrap-gce-storagebucket=<bucketname/directoryname>

      If you choose to bootstrap with custom metadata, continue to Step 6.
   2. Interface Swap (Optional)—Swap the Management interface (eth0) and the first dataplane interface (eth1) at deployment time. Interface swap is only necessary when you deploy the VM-Series firewall behind Google Cloud Platform HTTP(S) Load Balancing. For details, see Management Interface Swap for Google Cloud Platform Load Balancing.
   3. SSH key—Paste in the public key from an SSH key pair. Follow the instructions for your OS in SSH Key Pair, to create, copy, and paste the key. Windows users must view the key in PuTTY, copy from the user interface, and paste into Marketplace deployment.
      If the key is not formatted properly, the VM-Series firewall does not allow you to log in. You must delete the deployment and start over.
   4. Click More to reveal additional metadata options. The options blockProjectKeys, and enableSerialConsole are properties of the instance; you can change these metadata values after a successful deployment.
      • blockProjectKeys (Optional)—If you Block Project Keys, you can use only the public SSH key you supply to access the instance.
      • enableSerialConsole (Optional)—Interacting with the Serial Console enables you to monitor instance creation and perform interactive debugging tasks.
6. Specify custom metadata.
   If you choose to bootstrap with custom metadata, add any key-value pairs that you did not add in Step 5. See init-cfg.txt File Components for the list of key-value pairs. For example:

7. Configure the boot disk.
   1. Boot disk type—Select from SSD Persistent disk or Standard Persistent Disk. See Storage Options.
   2. Enter the Boot disk size—60GB is the minimum size. You can edit the disk size later but you must stop the VM to do so.
8. Configure the management interface.
   1. Management VPC Network name—Choose an existing network
   2. Management Subnet name—Choose an existing subnet.
   3. Enable External IP for Management interface (Optional)—If you enable this option, you can use the IP address assigned to the VM-Series firewall management interface to use SSH to access the VM-Series firewall web interface.
   4. Enable GCP Firewall rule for connections to Management interface (Optional)—This option automatically creates a GCP firewall Allow rule for an external source IP address that you supply.
   5. Source IP in GCP Firewall rule for connections to Management Interface—If you Enable GCP Firewall rule for connections to Management interface, enter a source IP address or a CIDR block.
      • Do not use 0.0.0.0/0. Supply an IP address or a CIDR block that corresponds to your dedicated management IP addresses or network. Do not make the source network range larger than necessary.
      • Verify the address to ensure that you do not lock yourself out.
9. Configure the Untrust dataplane interface.
   1. Untrust VPC Network name—Choose an existing network.
   2. Untrust Subnet name—Choose an existing subnet.
   3. Enable External IP for Untrust—Enable GCP to provide an ephemeral IP address to act as the external IP address.
10. Configure the Trust dataplane interface.
    1. Trust VPC Network name—Choose an existing network.
    2. Trust Subnet name—Choose an existing network.
    3. Enable External IP for Trust—Enable GCP to provide an ephemeral IP address to act as the external IP address.
11. Configure additional interfaces. You must enter the number of dataplane interfaces you want to add; the default is 0 (none). The deployment page always displays fields for five additional dataplanes numbered 4 through 8.
    1. Additional Dataplane interfaces—Enter the number of additional dataplane instances.
       If this number is 0 (default), dataplane numbers 4 through 8 are ignored even if you fill out the interface fields. If, for example, you specify 2 and then fill out information for three interfaces, only the first two are created.
    2. Additional Dataplane # VPC name—Choose an existing network.
    3. Dataplane # Subnet name—Choose a subnet that exists.
    4. Enable External IP for dataplane # interface—Enable GCP to provide an ephemeral IP address to act as the external IP address.
12. Deploy the instance.
13. Use Google Cloud Deployment Manager to view and manage your deployment.
14. Use the CLI to change the administrator password on the firewall.
    1. Log in to the VM-Series firewall from the command line. In your SSH tool, connect to the External IP for the management interface, and specify the path to your private key.
       Windows users: Use PuTTY to connect to the VM-Series firewall and issue command line instructions. To specify the path to the private key, select ConnectionSSHAuth. In Private key file for authentication: click Browse to select your private key.
    2. Enter configuration mode:
       VMfirewall> configure
    3. Enter the following command:
       VMfirewall# set mgt-config users admin password
    4. Enter and confirm a new password for the administrator.
    5. Commit your new password:
       VMfirewall# commit
    6. Return to command mode:
       VMfirewall# exit
    7. (Optional) If you used a bootstrap file for interface swap, use the following command to view the interface mapping:
       VMfirewall> debug show vm-series interfaces all
15. Access the VM-Series firewall web interface.
    1. In a browser, create a secure (https) connection to the IP address for the management interface.
       If you get a network error, check to see that you have a GCP firewall rule that allows the connection.
    2. When prompted, enter the username (admin) and the administrator password you specified from the CLI.
    3. (Optional) If you bootstrapped, then Verify Bootstrap Completion.
       If you see problems, search the log information on the VM-Series firewall. Choose MonitorSystem and, in the manual search field, enter  description contains 'bootstrap' and look for a message in the results that indicates that the bootstrap was successful.
    After you log in to the firewall, you can add administrators and create interfaces, zones, NAT rules, and policy rules, just as you would on a physical firewall.