Skip to main content
Versa Networks

Install on Google Cloud Platform without CMS

Versa-logo-release-icon.png For supported software information, click here.

This article describes how to install a Versa branch device on Google Cloud Platform.

To obtain the Versa Operating SystemTM (VOSTM) software image for Google Cloud Platform so that you can perform the installation, contact Versa Networks Customer Support.

Before you install a Versa branch device on Google Cloud Platform, ensure that you have done the following on the branch device:

  • Create three subnets for the VOS instance. Note that you must place the three subnets in three different private clouds (VPCs).
    • Management subnet
    • WAN subnet, to communicate with the SD-WAN Controller node
    • LAN subnet, to communicate with the LAN side
  • Create firewall rules and associate them with the VPC and subnet. For more information, see Firewall Requirements.

Create a VM Instance

To create a VM instance on Google Cloud Platform:

  1. Log in to the Google Cloud Platform account.
  2. In the left navigation bar, select Compute Engine, and then select VM Instances.

    google-cloud-platform.jpg
     
  3. In the left navigation bar, select VM Instances, and then click the Create Instance icon. The Create an Instance page displays.

    vm-instances.jpg
     
  4. In the left navigation bar, select New VM Instance and enter the following information:
    1. In the Name field, enter a name for the VM instance.
    2. In the Labels field, click Add Label to enter a label.
    3. In the Region field, select the region in which you are creating the VOS instance.
    4. In the Zone field, select the zone in which you are creating the VOS instance.
    5. In the Machine Configuration Group, select the machine family and series types for common workloads. For more information, see Qualified AWS and Azure Instances.
    6. In the Machine type field, select the machine type as n1-standard-4.

      create-an-instance.jpg
       
  5. In the Boot disk section, click Change to select the VOS images.

    boot-disk-change.jpg
     
  6. Select the Custom Images tab, and then select the VOS image.
    1. Select Versa in the Show Images From field.
    2. Select the image in the Image field.

      boot-disk.jpg
       
  7. Click the Management, Security, Disks, Networking, Sole Tenancy field to add network interfaces.

    management.jpg
     
  8. Select the Networking tab to view the network interfaces.

    management-tab.jpg
     
  9. In the Networking tab, select the three VPCs and subnets to attach three NICs on the VOS instance.
  10. In the Network Interface table, enter the network details.
    1. In the Network field, select the VPC network that contains the subnet that you created.
    2. In the Subnetwork field, select the subnet for the instance to use.
    3. In the External IP field, select the external IP address.
      • For the WAN subnet, select the external IP address if the Controller node is reachable using public IP address.
      • For the LAN subnet, an external IP address is not required.
    4. In the IP Forwarding field, select On to enable IP forwarding for the management subnet.

      network-interface.jpg
       
  11. Select the Security tab and add the SSH key, which is the public RSA key. The admin user uses this key to log in to the VOS instance.

    security-tab.jpg
     
  12. Click Create.

Prepare the VOS Instance To Be Activated

You activate the VOS instance automatically and remotely using zero-touch provisioning (ZTP).

To prepare the VOS instance to be activated:

  1. Log in to VOS instance using the following command.
ssh -i id_rsa admin@external-IP-address

For example:

% ssh -i id_rsa admin@35.230.47.165

             .---.,
            (      ``.
       _     \        )    __      ________ _____   _____
      (  `.   \      /     \ \    / /  ____|  __ \ / ____|  /\
       \    `. )    /       \ \  / /| |__  | |__) | (___   /  \
        \     |    /         \ \/ / |  __| |  _  / \___ \ / /\ \
         \    |   /           \  /  | |____| | \ \ ____) / ____ \
          \   |  /             \/   |______|_|  \_\_____/_/    \_\
           \  | /
            \_|/                     ___ _    _____  ___   ___  _ ___
                                    | __| |  | __\ \/ | \ / / \| | __|
                                    | _|| |__| _| >  < \ V /| .` | _|
                                    |_| |____|___/_/\_\ \_/ |_|\_|_|
 
 
Versa FlexVNF software
Release     :   21.1.1 (GA)
Release date:   20200822
Package ID  :   6e4e455
 
Last login: Mon Sep 28 01:22:22 2020
[admin@vos-gcp-instance-1: ~] $  
  1. At the end of the sshd_config file, add the IP addresses of the Versa Director northbound and southbound interfaces as match address exceptions. Doing so allows the Director node to log in to the node using a password and to perform the ZTP process by using the staging.py script. For example:
$ sudo vi /etc/ssh/sshd_config

Match address 10.192.220.193/32,192.168.220.193/32
  PasswordAuthentication yes
Match all
  1. Restart the SSH service:
$ sudo service ssh restart
  1. In Google Cloud Platform, add a custom route to pass the traffic from VOS interface instead of Google backbone network after ZTP has completed.

    vpc-network.jpg

Supported Software Information

Releases 20.2 and later support all content described in this article.

  • Was this article helpful?