--- title: "Virtual Service Router deployment on GCP" slug: "virtual-service-router-deployment-on-gcp" updated: 2025-04-17T15:02:00Z published: 2025-04-17T15:02:00Z canonical: "docs.zpesystems.com/virtual-service-router-deployment-on-gcp" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zpesystems.com/llms.txt > Use this file to discover all available pages before exploring further. # Virtual Service Router (vSR) deployment on GCP # Nodegrid VSR on Google GCP This documentation details creation of a Virtual Service Router VM instance on [Google Cloud Platform GCP](https://cloud.google.com/). The objective is to create a ZPE vSR instance that can act as a concentrator/hub to interconnect with other ZPE Systems Nodegrid appliances (e.g., Hive SR, Bold SR, or Mini SR). The following diagram, *Diagram-1*, shows the expected result: ![Diagram-1](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcpinstance.svg) This guide structure is as follows: 1. Licensing and Instance requirements 2. GCP Credentials 3. Nodegrid vSR AMI image 4. Create a Nodegrid vSR instance 5. Web Access to the Nodegrid vSR ## 1. Licensing The Nodegrid vSR product has five hardware license tiers for different use cases. The vSR VM can run for 30 days with no restraints, but after 30 days uploadedwithout a license, the software restricts the software restricts use after 30 days without a license use. | Tier | CPU | RAM | Equivalent | | --- | --- | --- | --- | | 1 | 2vCPU | 4GiB | GCP e2.median | | 2 | 4vCPU | 8GiB | GCP Custom | | 3 | 4vCPU | 16GiB | GCP e2-standard-4 | | 4 | 8vCPU | 32GiB | GCP e2-standard-8 | | 5 | 16vCPU | 64GiB | GCP e2-standard-16 | ## 2.GCP Credentials This guide assumes the following: - GCP user with privileges to create the following resources in a [GCP Project](https://cloud.google.com/resource-manager/docs/creating-managing-projects): - [GCP Cloud Storage](https://cloud.google.com/storage) - [GCP VM Instances](https://cloud.google.com/compute/docs/instances) - [GCP VPC](https://cloud.google.com/vpc) - [GCP Region and Zone](https://cloud.google.com/about/locations) selected to deploy the instance ## 3. Nodegrid vSR AMI image The Nodegrid vSR AMI creation for GCP consists of two steps: 1) upload the vSR image file (e.g., *Nodegrid_Platform_GCP_v5.8.2_20230114.tar.gz*) into a **GCP bucket**, and 2) create the GCP AMI based on the uploadedThe default file. Below are the details. > The vSR *.tar.gz* image file for GCP is distributed by ZPE Systems directly. It is available to all customers via the support portal and is not publicly available in the *GCP Public Images*. Please contact support@zpesystems.com. ### GCP Bucket These steps are an example of how to configure a GCP Bucket. Adapt accordingly to your security requirements. 1. Access to [GCP Storage > Buckets](https://console.cloud.google.com/storage/) 2. Select **Create** and enter the required information: - On **Name your bucket**: insert a unique, permanent name, e.g., `vsr-images` - For **Choose where to store your data**: consider *Multi-region > us (multiple regions in United States)* - For **Choose a storage class for your data**: select *Set a default class > Standard* - For **Choose how to control access to objects**: select both *Enforce public access prevention on this bucket* and *Access control > Uniform* - For **Choose how to protect object data**: select *None* 1. Click **Create** ![gcp-bucket-create.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcp-bucket-create.png) ### Upload the Nodegrid vSR `tar.gz` image 1. Access to [GCP Storage > Buckets](https://console.cloud.google.com/storage/) 2. Select a bucket, e.g., `vsr-images` 3. Click **Upload Files** 4. Select the Nodegrid vSR `tar.gz` image file, e.g., *Nodegrid_Platform_GCP_v5.8.2_20230114.tar.gz* 5. Verify the image file successfully uploaded ![gcp-bucket-list.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcp-bucket-list.png) ### Create a Nodegrid vSR Image for GCP This creates the Nodegrid vSR AMI image based on the previously uploaded tarball file to the bucket. > This step is required to be executed **gcloud cli**. This document considers the Web Cloud Shell option! ![gcloud-shell-cli.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcloud-shell-cli%282%29.png) Before executing the command on gcloud cli `gcloud compute images create ...`, the following information is required: - **AMI name**: e.g., *vsr-v5-8-2-20230114* - **Project ID**: global GCP project identification - **Storage Location**: GCP region where the image is deployed, e.g., *us-west1* - **Source URI**: google api endpoint for the image file, in the form: `https://storage.googleapis.com/<YOUR-BUCKET>/<NODEGRID_ISO>` Execute the following command: ``` gcloud compute images create vsr-v5-8-2-20230114 \ --project=clexxxxxxxxxxx420 \ --family=ng-instance \ --source-uri=https://storage.googleapis.com/vsr-images/Nodegrid_Platform_GCP_v5.8.2_20230114.tar.gz \ --storage-location=us-west1 \ --guest-os-features=UEFI_COMPATIBLE ``` ![gcloud-chell-cli-exec.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcloud-chell-cli-exec.png) To verify Image access, go to [https://console.cloud.google.com/compute/images](https://console.cloud.google.com/compute/images) ![gcp-images.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcp-images.png) ## 4. Create a Nodegrid vSR instance The following steps are a simplified deployment of a VM instance in GCP. Some of the resources in *Diagram-1* are automatically created with pre-established GCP default configurations. ### GCP VPC network 1. Go to [https://console.cloud.google.com/networking/](https://console.cloud.google.com/networking) 2. Select **VPC networks > Create VPC Network** 3. Enter the required information: - **Name**: e.g., *vsr-vpc* - Select **Add subnet** and enter a name, e.g., *vsr-subnet-1* - Select **subnet Region** - Enter **IPv4 range**: e.g., 10.1.0.0/24 1. On **Firewall rules**: select the following: - *vsr-vpc-allow-icmp* - *vsr-vpc-allow-ssh* 1. Click **Create** ![gcp-vpc.jpg](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcp-vpc.jpg) ### GCP Create VM 1. Go to [https://console.cloud.google.com/compute/images](https://console.cloud.google.com/compute/images) 2. Find the Nodegrid vSR image, e.g., *vsr-v5-8-2-20230114*, and select **Actions > Create instance** 3. Enter **Instance Name**, e.g., *vsr-gcp-1* 4. Select **Region** and **Zone**, e.g., *us-west1 (Oregon)* and *us-west1-b* 5. On **Machine configuration**: select a General-Purpose E2 medium machine type 6. On **Firewall**: select **Allow HTTP** and **HTTPS traffic***. 7. On **Networking** - Select **Enable IP forwarding** - On **Network interface**: select a network interface in the VPC and Subnetwork previously created - On **Network Service Tier**: select *Standard* 1. On **Security** - Select **Turn on vTPM** - Select **Turn on Integrity Monitoring** 1. Click **Create** ![gcp-vm.jpg](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/gcp-vm.jpg) 1. On the **Compute Engine > VM instances**: select the created instance and look for the assigned public IP. ## 5. Web Access to the Nodegrid vSR 1. In a browser, open **https://Public-GCP-IP** 2. Log in to the Nodegrid vSR WebUI. Default credentials are: - user: admin - password: admin 1. Follow the steps to change the password 2. **Congratulations!** You have successfully deployed a Nodegrid vSR instance. ![web-ui](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/web-ui.png) ## 6. Enroll vSR to ZPE Cloud A Nodegrid vSR is managed through ZPE Cloud. The new deployed unit must be enrolled to the customers ZPE Cloud instance. 1. Login to your ZPE Cloud account [Global](https://zpecloud.com) , [EU](https://zpecloud.eu) or onPrem 2. Go to **SETTINGS :: ENROLLMENT :: CLOUD** 3. Copy the **Customer Code** and **Enrollment Key** (required to claim the vSR) ![settings-enrolment-cloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/settings-enrolment-cloud.png) 4. In a browser, login to vSR by with the link **https://Public-AWS-IP** 5. Go to **Security :: Services** and enable ZPE Cloud service ![security-zpecloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/security-zpecloud.png) 6. Go to **System :: Toolkit :: Cloud Enrollment** ![system-toolkit](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/system-toolkit.png) 7. Enter the following information 1. **URL**: URL of the zpecloud instance, default https://zpecloud.com 2. **Customer Code**: Use the copied Customer Code from the Cloud Instance 3. **Enrollment Key**: Use the copied Enrollment Key ![settings-enrolment-cloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/settings-enrolment-cloud.png) 8. Click on Enroll ![system-toolkit-cloud-enrolment-success](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/system-toolkit-cloud-enrolment-success.png) 9. This enrolls the unit to ZPE Cloud and be available in ZPE Cloud under **DEVICES :: AVAILABLE** ![devices-available](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/devices-available.png) 10. To start managment of the vSR, select and click on **ENROLL**. 11. When enrolled, the vSR is managed on ZPE Cloud like any other Nodegrid device.