https:\/\/learn.microsoft.com\/en-us\/troubleshoot\/azure\/virtual-machines\/windows\/serial-console-overview<\/a><\/p>\n\n\n\nIt is convenient and helpful for troubleshooting in the console of the virtual VCE is usable. However, in order to use the console, a password must be set, which means the authentication cannot be key-based only. In this article, a password is set to demonstrate the possibility of using the console port. If your security requirement does not allow a static password, you need to adjust the configuration accordingly.<\/p>\n\n\n\n\n\n\n\n
Procedure of how to manually deploy the VCE in Azure<\/h2>\n\n\n\n Let’s see the steps to deploy the VCE in Azure manually.<\/p>\n\n\n\n
Create Storage account and container<\/h2>\n\n\n\n If there is already existing storage account and container in your VNET, you can skip this step. To create the storage account, in the Azure portal, go to “Storage accounts” and select “Create a storage account”, in this example, a storage account called “accountea2” is created:<\/p>\n\n\n\nFigure 1 – create a storage account called “accountea2”<\/figcaption><\/figure>\n\n\n\nAfter the storage account is created, go to the corresponding “Storage Browser”, and select “Blob containers”:<\/p>\n\n\n\nFigure 2 – Blob containers at Storage browser<\/figcaption><\/figure>\n\n\n\nAdd a container, the container is the location to store the VCE image. In this article, a container called “images” is created:<\/p>\n\n\n\nFigure 3 – Add container called images<\/figcaption><\/figure>\n\n\n\nFigure 4 – a container call images created<\/figcaption><\/figure>\n\n\n\n\n\n\n\nUpload and Create VCE images<\/h2>\n\n\n\n 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:<\/p>\n\n\n\nFigure 5 – upload the VCE vhd to the blob container<\/figcaption><\/figure>\n\n\n\nFigure 6 – upload vhd in progress<\/figcaption><\/figure>\n\n\n\nFigure 7 – when vhd image upload completed<\/figcaption><\/figure>\n\n\n\nThe 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:<\/p>\n\n\n\n
d09b9158af749bb7a08841c08d6675e2 .\/edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd<\/code><\/pre>\n\n\n\nCreate the VCE image<\/h2>\n\n\n\n Go to “Images” in Azure portal, select “Custom Images”:<\/p>\n\n\n\nFigure 8 – Location to create the custom image<\/figcaption><\/figure>\n\n\n\nClick Create, name the image as “Velocloud-5015-Image”, select OS as Linux with “Gen 1”:<\/p>\n\n\n\nFigure 9 – Create image Velocloud-5015-Image, Linux Gen 1<\/figcaption><\/figure>\n\n\n\nIn 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.<\/p>\n\n\n\nFigure 10 – select “edge-VC_XEN_AWS-x86_64-5.0.1.5-66-R5015-20230929-GA-112911-c3310b7f05-updatable-ext4.vhd”<\/figcaption><\/figure>\n\n\n\nIn 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:<\/p>\n\n\n\nFigure 11 – remaining parameters for create image Velocloud-5015-Image<\/figcaption><\/figure>\n\n\n\nAfter click “Review + create”<\/p>\n\n\n\nFigure 11 – Validation passed for image creation<\/figcaption><\/figure>\n\n\n\n and then click “Create”. An image called “Velocloud-5015-Image” is created:<\/p>\n\n\n\nFigure 12 – Velocloud-5015-Image created successfully<\/figcaption><\/figure>\n\n\n\n\n\n\n\nNetwork Diagram of the VCE in Azure<\/h2>\n\n\n\n A network diagram will be helpful for understanding how the VCE deployment looks like.<\/p>\n\n\n\nFigure 13 – Network Diagram<\/figcaption><\/figure>\n\n\n\nNetwork Security Groups<\/h2>\n\n\n\n On both WAN side (GE1) and LAN side (GE2), a network security group is required. The purpose of this article is not about how the security groups should be configured. Sample security groups are being show here, administrator should adjust them to fit their own requirements.<\/p>\n\n\n\n
The following is the sample WAN side Network Security Group with name “VELO_vVCE_SG”:<\/p>\n\n\n\nFigure 14 – inbound and outbound rules for VELO_vVCE_SG security group<\/figcaption><\/figure>\n\n\n\nThe following is the sample LAN side Network Security Group with name “VELO_vVCE_LAN_SG”:<\/p>\n\n\n\nFigure 15 – inbound and outbound rules for VELO_vVCE_LAN_SG security group<\/figcaption><\/figure>\n\n\n\n\n\n\n\nCreate Network Interface(s)<\/h2>\n\n\n\n For the virtual VCE in Azure, GE1 will be WAN (overlay enabled) and GE2 will be LAN (overlay disabled). In the Azure side, that means the first interface is WAN (subnet can access Internet), and the second interface is LAN (the interface accept traffic from other client\/server located in the VNET)<\/p>\n\n\n\n
Since the manual deployment is not using a template, the VM initially will only have a single NIC and the setting of that NIC is not what we need. As a result, here will manually create the two NICs and they will be associated to the VM (the virtual VCE) later.<\/p>\n\n\n\n
Firstly, let’s create the GE1 (WAN). Go to Network Interface, give it a name “Demo-Azure01-GE1”, select the Region and Subnet match your environment. For the IP address assignment, since this is WAN side, dynamic is fine.<\/p>\n\n\n\nFigure 15 – Review + create WAN (GE1) interface<\/figcaption><\/figure>\n\n\n\nAfter click “Review + create” and with Validation passed, click “Create”:<\/p>\n\n\n\nFigure 16 – Create WAN (GE1) interface<\/figcaption><\/figure>\n\n\n\nSecondly, create the GE2 (LAN). Give the interface name “Demo-Azure01-GE2”, for the private IPv4 address, it is recommended to use a static IP because this will be the default gateway of the route table which accept the traffic to go through SD-WAN. In this article, the NIC “Demo-Azure01-GE2” will be using 172.30.1.13 as the IP address. Let’s see the screen capture:<\/p>\n\n\n\nFigure 17 – “Review + create” of the LAN (GE2) interface<\/figcaption><\/figure>\n\n\n\nFigure 18 – Create LAN (GE2) interface<\/figcaption><\/figure>\n\n\n\nAssign the Network Security Group to the NIC<\/h2>\n\n\n\n Assign the corresponding Network Security Group to the NIC. For Demo-Azure01-GE1 (WAN side), assign “VELO_vVCE_SG”<\/p>\n\n\n\nFigure 19 – Assign GE1 to security group VELO_vVCE_SG<\/figcaption><\/figure>\n\n\n\nFor Demo-Azure02-GE2 (LAN side) , assign “VELO_vVCE_LAN_SG”:<\/p>\n\n\n\nFigure 20 – Assign GE2 to security group VELO_vVCE_LAN_SG<\/figcaption><\/figure>\n\n\n\n\n\n\n\nPublic IP Address<\/h2>\n\n\n\n The WAN interface which is Demo-Azure01-GE1 requires a public IP address. Go to “Public IP addresses” and click “Create”. Give a name to the public IP, here is “Demo-Azure01-PublicIP”. Select IPv4, Standard SKU, Zone-redundant and Regional Tier, click “Review + create”<\/p>\n\n\n\nFigure 21 – Create Public IP address, upper part<\/figcaption><\/figure>\n\n\n\nFigure 22 – Create Public IP address, lower part<\/figcaption><\/figure>\n\n\n\nClick Create after Validation passed.<\/p>\n\n\n\nFigure 23 – Validation passed and create public IP address<\/figcaption><\/figure>\n\n\n\nAssociate the public IP address to NIC Demo-Azure01-GE1 (GE1 is WAN). Click on the NIC Demo-Azure01-GE1, go to “IP configurations” -> “IP Settings” -> “ipv4config”<\/p>\n\n\n\nFigure 24 – “IP configurations” -> “IP Settings” -> “ipv4config” of Demo-Azure01-GE1<\/figcaption><\/figure>\n\n\n\nEnable “Associate public IP address”, in the Public IP address drop down menu, select the IP created in the previous step, in this case is demo-azure01-publicip:<\/p>\n\n\n\nFigure 25 – Associate the public IP address to NIC Demo-Azure01-GE1<\/figcaption><\/figure>\n\n\n\nAfter associate public IP address to NIC Demo-Azure01-GE1:<\/p>\n\n\n\nFigure 26 – After associate public IP address to Demo-Azure01-GE1<\/figcaption><\/figure>\n\n\n\nEnable IP Forwarding<\/h2>\n\n\n\n On GE2 (LAN side), IP Forwarding needs to be enabled. Click on NIC Demo-Azure01-GE2, go to “IP configurations” -> “IP Settings”, check the “Enable IP forwarding” checkbox and click Apply:<\/p>\n\n\n\nFigure 27 – Enable IP forwarding for Demo-Azure01-GE2 (LAN)<\/figcaption><\/figure>\n\n\n\nAfter enabled “Enable IP forwarding”:<\/p>\n\n\n\nFigure 28 – After enable “Enable IP forwarding”<\/figcaption><\/figure>\n\n\n\n\n\n\n\nCreate the Virtual VCE VM<\/h2>\n\n\n\n NOTE: Please make sure you understand the “Custom data” configuration before create the VM<\/mark>. Go to “Images” and click on the “Velocloud-5015-Image” created in this article. Next, select “Create VM”<\/p>\n\n\n\nFigure 29 – Create VM from image Velocloud-5015-Image<\/figcaption><\/figure>\n\n\n\nFor the VM name, in this article will call Demo-Azure01<\/p>\n\n\n\nFigure 30 – Create VM and call it Demo-Azure01<\/figcaption><\/figure>\n\n\n\nThe image should already selected as Velocloud-5015-Image x64 Gen1. For the Size, you need to select the size suitable for your environment and requirement. For this demonstration, Standard_D2s_v5 is selected:<\/p>\n\n\n\nFigure 31 – Create VM from image Velocloud-5015-Image – continue<\/figcaption><\/figure>\n\n\n\nFor the Authentication type, as mentioned at the beginning, since we want to able to login with serial console, so select “Password” as Authentication type. In this article, the username is “azureuser” and the password is “Velocloudsdwan2”.<\/p>\n\n\n\nFigure 32 – Create VM from image Velocloud-5015-Image, Authentication Setting<\/figcaption><\/figure>\n\n\n\nDo NOT click “Review + create” at this point. Instead click “Next: Disks >”, no need to change the Disks setting, that is use default for Disks. Then click “Next: Networking >”, In the networking section, do not assign a new Public IP. The NIC created here is going to unbind and deleted at the end (remember we created two NICs previously).<\/p>\n\n\n\nFigure 33 – Networking setting when create VM from image Velocloud-5015-Image<\/figcaption><\/figure>\n\n\n\nThen click “Next: Management >”. Use default and click “Next: Monitoring >”, again use default and click “Next: Advanced >”. And here we arrive at the “Advanced” tab which is the very important part<\/strong><\/mark>. There is a Custom data box, which allow us to input the cloud-init data. The following code box is the cloud-init configuration:<\/p>\n\n\n\n#cloud-config\nvelocloud:\n vce:\n management_interface:\n false\nwrite_files:\n - content: |\n # User rules for azureuser\n azureuser ALL=(ALL) NOPASSWD:ALL\n owner: root:root\n path: \/etc\/sudoers.d\/azureuser\n permissions: '0644'<\/code><\/pre>\n\n\n\nThere are two configurations and hence two purposes will be achieved. Firstly, line #2 to line #5, which configured the management interface as false. Thus, the first interface will not be acting as a management interface, which means it can be work as a WAN interface. As a result, a 2-ARM deployment is possible by disable the management interface.<\/p>\n\n\n\n
Secondly is about line #6 to line #12. These 6 lines write a file called \/etc\/sudoers.d\/azureuser, such that azureuser will be able to sudo. This is a kind of workaround. By default, if the user is using key-based authentication, the user will be put into the sudoer list. But if the user is using password (in this article), the user will not be in the sudoer list. Thus, we use this trick to make the user azureuser use password for authentication but still able to sudo. If we do not use this workaround, none of the user can perform sudo and make the VCE not possible to perform necessary troubleshooting in the shell.<\/p>\n\n\n\nFigure 34 – Custom data (upper part of the box)<\/figcaption><\/figure>\n\n\n\nFigure 35 – Custom data (lower part of the box)<\/figcaption><\/figure>\n\n\n\nAt this point, can click “Review + create”, click the “Create” after Validation passed.<\/p>\n\n\n\nFigure 36 – Create the VM Demo-Azure01<\/figcaption><\/figure>\n\n\n\nThe VM Demo-Azure01 will be created and running like this after the creation:<\/p>\n\n\n\nFigure 37 – VM Demo-Azure01 right after create<\/figcaption><\/figure>\n\n\n\n\n\n\n\nDetach and Attach Network Interface<\/h2>\n\n\n\n In previous section, network interface Demo-Azure01-GE1 and Demo-Azure01-GE2 are created. We need to attach them to the VM Demo-Azure01. To perform network interface attach and detach, the VM Demo-Azure01 needs to be power off first. NOTE: When the virtual VCE VM is created in first time, wait for 10 minutes before doing this power off, this allow the VM completely initialized.<\/p>\n\n\n\n
Click Stop to power off the VM Demo-Azure01. After the VM Demo-Azure01 is off, the status is “Stopped (deallocated)” as follow:<\/p>\n\n\n\nFigure 38 – VM Demo-Azure01 powered off<\/figcaption><\/figure>\n\n\n\nGo to “Networking” -> “Network settings” and click “Attach network interface”, see the highlight of the following screen.<\/p>\n\n\n\nFigure 39 – Attach network interface (1st time)<\/figcaption><\/figure>\n\n\n\nSelect Demo-Azure01-GE1 from the drop-down menu and click “Ok”<\/p>\n\n\n\nFigure 40 – Select Demo-Azure01-GE1 and click Ok<\/figcaption><\/figure>\n\n\n\nAfter the Demo-Azure01-GE1, select Detach network interface like the following screen capture:<\/p>\n\n\n\nFigure 41 – Detach network interface<\/figcaption><\/figure>\n\n\n\nIn the drop down menu, select the interface created with the VMs. The interface name should be with prefix of the VM name, in this example is demo-azure01 and following with some random characters. In the other words, detach the interface which is not created by us manually in previous step. Click “Ok” after selected the interface to detach.<\/p>\n\n\n\nFigure 42 – detach the interface not manually created by us<\/figcaption><\/figure>\n\n\n\nAfter detached the interface not created by us, click Attach network interface again, and select the Demo-Azure01-GE2 interface, and click Ok.<\/p>\n\n\n\nFigure 43 – Attach interface Demo-Azure01-GE2<\/figcaption><\/figure>\n\n\n\nAfter attach network interface GE2, the VM Demo-Azure01 is now with 2 network interfaces as follow:<\/p>\n\n\n\nFigure 44 – VM Demo-Azure01 comes with two interfaces Demo-Azure01-GE1 and Demo-Azure01-GE2<\/figcaption><\/figure>\n\n\n\nThe network interface detach and attach are completed, power on (start) the VM Demo-Azure01.<\/p>\n\n\n\n\n\n\n\n
Route Table<\/h2>\n\n\n\n The VM is now ready to login and activate. For completeness, I capture the route table of the public subnet, which is where the GE1 located at, and also the route table of the server subnet, which is where the servers are located.<\/p>\n\n\n\n
The public subnet comes with a default route (0.0.0.0\/0) to Internet.<\/p>\n\n\n\nFigure 45 – public subnet route table<\/figcaption><\/figure>\n\n\n\nThe server subnet in this example has two routes. The first one is default route pointing to 172.20.1.13 which is Demo-Azure01-GE2. The second route is to a subnet 10.11.1.0\/24, this subnet is at the LAN side of a remote VCE acting as a spoke site. Have two routes so the private destination and Internet are separated. And administrator can adjust the route table to their own need.<\/p>\n\n\n\nFigure 46 – server subnet route table<\/figcaption><\/figure>\n\n\n\n\n\n\n\nLogin to the VCE Demo-Azure01 at the serial console<\/h2>\n\n\n\n At the VM Demo-Azure01, go to “Connect” -> “Connect” -> “More ways to connect” -> “Serial console” and click on the “Go to serial console”:<\/p>\n\n\n\nFigure 47 – Go to serial console<\/figcaption><\/figure>\n\n\n\nPress enter and the login prompt like the following appear:<\/p>\n\n\n\nFigure 48 – serial console login prompt<\/figcaption><\/figure>\n\n\n\nLogin with the corresponding username and password, in this article, the username is “azureuser”, password is “velocloudsdwan2”. After login, can issue a command “sudo ls -l \/etc\/sudoers.d\/” to confirm the sudo is allowed.<\/p>\n\n\n\nFigure 49 – logged in the serial console, sudo is successful<\/figcaption><\/figure>\n\n\n\nNow, create the VCE at the VCO, so this Demo-Azure01 can be activated.<\/p>\n\n\n\n\n\n\n\n
Create the VCE Demo-Azure01 in the VCO<\/h2>\n\n\n\n The purpose of this article is not to show how to configure the VCE in the VCO when the VCE is a virtual VCE in Azure. Thus, here will not capture the entire configuration, only four screen captures will be shown which are the area I would like to make a reminder.<\/p>\n\n\n\n
Firstly, when create the edge, the mode is “Virtual Edge”, do NOT select “Cloud Edge”.<\/p>\n\n\n\nFigure 50 – Use model Virtual Edge, not Cloud Edge<\/figcaption><\/figure>\n\n\n\nFor the interface, make sure GE1 and GE2 are both routed. and GE1 is WAN (overlay enabled) while GE2 is LAN (overlay disabled). And the GE2 (LAN) needs to have NAT Direct disabled.<\/p>\n\n\n\nFigure 51 – Demo-Azure01 interface settings<\/figcaption><\/figure>\n\n\n\nThirdly, configure the static routes to the server subnet (or any other static routes required in your Azure environment).<\/p>\n\n\n\nFigure 52 – static route for Azure server subnet<\/figcaption><\/figure>\n\n\n\nLastly, by default the console port access is disabled. Go to the “Firewall” -> “Edge Security” -> “Edge Access” -> “Console Access” and select Allow. Otherwise, the serial console cannot be used after activation.<\/p>\n\n\n\nFigure 53 – Set the console access to allow<\/figcaption><\/figure>\n\n\n\nAt this point, it is ready to activate the VCE Demo-Azure01.<\/p>\n\n\n\n
Activate the VCE Demo-Azure01<\/h2>\n\n\n\n Login to the serial console, issue command in the code block below (you need to adjust the activation key and VCO URL to suit your own environment):<\/p>\n\n\n\n
sudo \/opt\/vc\/bin\/activate.py -s vco7-sin1.velocloud.net -i ABCD-ABCD-ABCD-ABCD<\/code><\/pre>\n\n\n\nThe following is a sample screen capture when the activation is success<\/p>\n\n\n\nFigure 54 – activation success (VCE update the software)<\/figcaption><\/figure>\n\n\n\nAfter the activation is success, the VCE needs to update the software, establish tunnel to the controller, etc, etc. If things go right, wait for about 10 minutes, the VCO monitor section should see the VCE is at “Connected” status and the WAN link is at stable status similar to the following screen capture.<\/p>\n\n\n\n
<\/p>\n\n\n\nFigure 55 – The Demo-Azure01 VCE is at connected status, the WAN link is showing as up<\/figcaption><\/figure>\n\n\n\nWhen I write this article, the software version the Demo-Azure01 is R5241-20241112-GA-5008849603<\/strong>. Since the vhd image is version 5.0.1, I assume there will be no issue if your target version is newer tan 5.0.1. But if you are going to downgrade, then you need to test it by yourself whether it will work or not.<\/p>\n\n\n\nThis conclude the manual deployment (without using template) of virtual VCE in Azure is successful.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n This article demonstrates how to deploy virtual VCE in Azure manually, which can be useful in situation such as Azure China where the Velocloud image is not available in the marketplace.<\/p>\n","protected":false},"excerpt":{"rendered":"
About VCE in Azure – the background To deploy a virtual Velocloud Edge (VCE) at Azure, typically, you will use the “Template specs” in Azure, which you upload a JSON file as template (There is one of the template by Velocloud: https:\/\/community.broadcom.com\/communities\/community-home\/librarydocuments\/viewdocument?DocumentKey=04598214-527e-46b1-9fa9-4e30bdba4da0). In the backend, the template will utilize the VCE image in the Azure […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"zakra_sidebar_layout":"customizer","zakra_remove_content_margin":false,"zakra_sidebar":"customizer","zakra_transparent_header":"customizer","zakra_logo":0,"zakra_main_header_style":"default","zakra_menu_item_color":"","zakra_menu_item_hover_color":"","zakra_menu_item_active_color":"","zakra_menu_active_style":"","zakra_page_header":true,"footnotes":""},"categories":[11,5],"tags":[],"class_list":["post-840","post","type-post","status-publish","format-standard","hentry","category-public-cloud","category-velocloud"],"_links":{"self":[{"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/posts\/840","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/comments?post=840"}],"version-history":[{"count":77,"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/posts\/840\/revisions"}],"predecessor-version":[{"id":980,"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/posts\/840\/revisions\/980"}],"wp:attachment":[{"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/media?parent=840"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/categories?post=840"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sdwan2.com\/index.php\/wp-json\/wp\/v2\/tags?post=840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/create-storage-account.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/storage-browser-container.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/add-container-images.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/image.png\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/upload-image-to-blob-1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/upload-in-progress.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/image-upload-complete.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/custom-image-1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/create-image-screen1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/select-blob.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/create-image-remaining.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/after-review-and-create.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/created-Velocloud-5015-Image.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/network-diagram.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/inbound-VELO-vVCE-SG.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/inbound-and-outbound-VELO_vVCE_LAN_SG.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-WAN-Interface1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-WAN-Interface2-validate.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-LAN-Interface1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/image-1.png\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/GE1-Security-Group11.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/GE2-Security-Group222.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/R-and-Create-Screen1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/R-and-Create-Screen2.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-Public-IP-111.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/ip-config-ip-settings.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Associate-GE1-public.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/After-assigned-pub-ip.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/enable-ipforward-1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/enable-ipforward-2.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-VM-from-images.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-VM-Screen1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-VM-Screen2.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-VM-Screen-n3.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/networking1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/custom-data-1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/custom-data-2.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Create-after-validation-pass-VM.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/VM-Created.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/VM-Powered-Off.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/attach-network-interface01.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/selec-GE1-click-ok.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Detach-interface1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/detach-interface-create-with-vm4.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/attach-ge2.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/two-interfaces.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/public-route-table.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/server-subnet-route-table.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/serial-console8.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/serial-login-prompt.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/logged-in-to-serial-console.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Model-Virtual.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Interface-setting1.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/vce-route-table-4444.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/console-access-firewall.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/activate-success4.jpg\")
![\"\"](\"https:\/\/www.sdwan2.com\/wp-content\/uploads\/2025\/05\/Monitor-page.jpg\")