![aruba bluecross cisco vpn setup aruba bluecross cisco vpn setup](https://s2.studylib.net/store/data/012410140_1-dfb75fddecab24daad3cec2667f81ecf-300x300.png)
Scrolling through it, you should be able to see your AS number is populated, and you can see that the IP information and the VRF has been populated as well. The Config Preview shows the configuration of the device itself. Now your device template has been configured. The dot1Q-tag-c-tag-01 here represents the VLAN you used in the Microsoft portal for your ExpressRoute.For the dot1Q-tag-s-tag-01, I want to use the same value as the interface tag.The interface tag is actually the VLAN you created for your Megaport connection earlier.Put the IP Address sub interface of my MVE with my subnet mask.Now I’ve added my feature templates to my device template, and next, I want to edit the device template. Read more about Megaport Virtual Edge with Cisco SD-WAN Cloud Interconnect. Next, scroll down to the CLI Add-On template and add your CLI template.Let’s find our device template, and now we want to add our feature templates. So I’ve now created my three templates, the VPN, BGP, and CLI. Add the name and description of the template.Paste in a standard configuration for this interface.Scroll down to other templates and choose CLI Add-On Template.Type in “C8000v” to find the right Cisco SD-WAN router.Last but not least, we need to create the Command Line Interface (CLI) template. Now we’ve done the VPN and BGP templates. Once the status goes from In Progress to Success, you’re well on our way to finishing this connection.And as you can see, we are now configuring the devices and in an In Progress state. So now it’s just giving me a configuration preview of the device that’s attached to my device template. So now my default template actually has a device attached to it. Click on the ellipsis at the end of the Device Template row.Okay, and what I need to do is attach a device to that template. The next thing I need to do is to grab templates, and I’ve got a default template that I have set up already. So that’s how you can find the device that you’ve configured in the Megaport Portal and in the Cisco SD-WAN vManage console. I’ll populate the device that I configured earlier today: tdw-MVE. Turn up the MVE you created in Cisco SD-WAN’s vManage consoleĪ couple of things I wanted to show you first is, if I select on the Configuration tab and go to Devices, this will show a list of the devices that we currently have configured. Want cost-effective private connectivity to Azure? Read When to Use ExpressRoute Local for Microsoft Azure Private Peering. So the next step is to swivel on over to Cisco SD-WAN’s vManage console. You should see that the IPs you’ve configured have been updated to your ExpressRoute. Enter the VLAN ID for this ExpressRoute.Enter the IP subnet for your secondary connection.Enter the IP subnet for your primary connection.NOTE: With any ExpressRoute connection, it is a requirement that you have a primary and a secondary subnet, even if you only decide to use a primary connection.
![aruba bluecross cisco vpn setup aruba bluecross cisco vpn setup](https://help.central.arubanetworks.com/latest/documentation/online_help/content/resources/images/hub_spoke.png)
Next to Provider status: Check that Microsoft ExpressRoute is in Provisioned status.Now it’s time to check your Microsoft Azure console and add Private Peering. Once your status has changed to Deployable, you’ll know the layer 2 connection has been provisioned within the Microsoft system. Let us break it down for you in Microsoft Azure ExpressRoute Pricing, Explained. Microsoft Azure ExpressRoute Pricing can be complicated. Now you’re deploying a connection between Megaport and Microsoft Azure. Next to Configure single Azure peering VLAN, slide the toggle to the left, as an Azure peering VLAN isn’t necessary in this instance.For Preferred A-End VLAN, enter the VLAN you want to face your MVE.We’ll put 50 Mbps for Rate Limit, set when I set up my ExpressRoute. Choose between a Primary and Secondary path.Paste your Service Key generated by the API integration between Megaport and Microsoft.Choose your Cloud–in this case, Microsoft Azure.On the Megaport portal, turning up a VXC from an MVE to your Azure ExpressRoute is just like turning up any Megaport service.