Navigate to Configuration -> Site-to-Site-VPN -> Advanced -> IPSEC Proposals (Transformation Sets).Shared key (PSK): Pick as suitably complex string and make a note of it for laterĬonnect to your ASA using ASDM.Local network gateway: Select the previously created local network gateway.Virtual network gateway: Should be pre-filled with you Virtual network gateway.Navigate back into your previously created Virtual network gateway and click Connections.Location: Typically your virtual networks location.Resource Group: Your desired resource group.Address space: This where you add you om premise subnets/vlan’s using the networks CIDR for example 10.0.100.0/24.IP Address: This is the outside public IP address of your ASA.Under “Create a resource” in the top left search for and select “Local network gateway”.Next, we need a Local Network Gateway to define our ASA public IP address and the list of on-premise network(s) we want over the VPN. Location: Typically your virtual networks location.Public IP: Create new unless you already have a space and give it a name.Virtual Network: Whatever Azure network we are joining over the VPN.SKU: VpnGW1 (or higher, basic doesn’t support IKEv2).Name: Whatever matches your naming convention.Under “Create a resource” in the top left search for and select “Virtual network gateways”.If your Virtual Network already has a “Virtual network gateway” check your settings match then you can skip this section. You will need ASDM, I will be using 7.9 The Azure Side Virtual network gateway.You ASA needs to be running at least 9.7 but 9.8 or higher is preferred.I am going to assume you are already using Azure and you already have a Virtual Network in place.
#CISCO ASA ASDM AND REMOTE ACCESS VPN HOW TO#
We are also going to focus on how to achieve this using ASDM. We will be creating a route-based connection using IKEv2 and a VTI interface. In this post, we are going to link an Azure Virtual Network to an on-premise network via a Cisco ASA.
0 kommentar(er)
