Deploy Velocloud virtual Edge in Azure (the manual way) – Page 3

Upload and Create VCE images

Click on the Blob container called “images”. Upload the file “edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd” to the images container:

Figure 5 – upload the VCE vhd to the blob container

Figure 7 – when vhd image upload completed

The reason for selecting this “edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd” is this is the current version in market place as of May-2025. If you don’t have this file, ask your Velocloud SE. And this is the md5sum:

d09b9158af749bb7a08841c08d6675e2  ./edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd

Create the VCE image

Go to “Images” in Azure portal, select “Custom Images”:

Figure 8 – Location to create the custom image

Click Create, name the image as “Velocloud-5015-Image”, select OS as Linux with “Gen 1”:

Figure 9 – Create image Velocloud-5015-Image, Linux Gen 1

In the Storage blob field, select the “edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd” uploaded in the previous step.

Figure 10 – select “edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd”

In the Account type, Standard SSD is select in this article. For Host caching, select “Read/write”. The following screen capture shows the remaining parameters for VCE image creation:

Figure 11 – remaining parameters for create image Velocloud-5015-Image

After click “Review + create”

Figure 11 – Validation passed for image creation

and then click “Create”. An image called “Velocloud-5015-Image” is created:

Figure 12 – Velocloud-5015-Image created successfully

Deploy Velocloud virtual Edge in Azure (the manual way)

Post Views: 3,022

Pages: 1 2 3 4 5 6 7 8 9 10 11