From the SonicWALL side, you will however see the familiar green circle indicating the VPN is live and you will be able to pass traffic over the tunnel. If you want to see the status from the USG, you can log into the CLI and type the command “show vpn ipsec status” which will indicate if the IPsec tunnel is active.

Cisco ASA running Cisco ASA 9.7.1+ Cisco IOS running Cisco IOS 12.4+ F5 Networks BIG-IP running v12.0.0+ Fortinet Fortigate 40+ Generic configuration for dynamic routing. H3C MSR800 running version 5.20. IIJ SEIL/B1 running SEIL/B1 3.70+ Juniper J-Series running JunOS 9.5+ Juniper SRX running JunOS 11.0+ Cisco ASA running Cisco ASA 8.2+ Cisco ASA running Cisco ASA 9.7.1+ Cisco IOS running Cisco IOS. Cisco Meraki MX Series running 9.0+ Citrix Netscaler CloudBridge running NS 11+ Cyberoam CR15iNG running V 10.6.5 MR-1. F5 Networks BIG-IP running v12.0.0+ Fortinet Fortigate 40+ Series running FortiOS 4.0+ Generic configuration for static routing In this article, we configure the IPSec tunnel between the Cisco ASA Firewall and Palo Alto Next-Generation Firewall. We also discussed the Encryption and Authentication algorithms. However, you must need static routable IP addresses to configure the IPSec VPN between two remote networks. Update 12/03/11 Feedback from Wajma Omari: I would like to add that this configuration will build the Tunnel but one more step needed to enable the Traffic between the two networks and that is by adding ACL from Inside network to the Remote Site Configuration – Firewall – Advanced – ACL Manager – Add – Add ACL and then ADD ACE IPsec VPN issues - Cisco ASA to Dell Sonicwall I work as an integrator for a customer that is wanting to set up a site to site, ipsec ikev1 tunnel between their ASA 5515x and another companies Dell Sonicwall. WE have a situation where we manage site to site vpns between Meraki devices and Cisco ASA devices. WE can establish a site to site VPN fine but after a undetermined / random amount of time the tunnel will stop passing traffic and we have to force a rekey on the ASA side or force the vpn down and ba

Cisco ASA running Cisco ASA 8.2+ Cisco ASA running Cisco ASA 9.7.1+ Cisco IOS running Cisco IOS. Cisco Meraki MX Series running 9.0+ Citrix Netscaler CloudBridge running NS 11+ Cyberoam CR15iNG running V 10.6.5 MR-1. F5 Networks BIG-IP running v12.0.0+ Fortinet Fortigate 40+ Series running FortiOS 4.0+ Generic configuration for static routing

Cisco VPN :: ASA 5510 - Internal IP From Sonicwall LAN / Setup A VPN Tunnel? Nov 5, 2011. I am trying to setup a VPN tunnel between a Cisco ASA 5510 (Version 8.2(2)) and Sonicwall TZ200. I got tunnel up and going and I am able to ping the Cisco ASA internal IP from the Sonicwall LAN but nothing else works.

I love to work on CLI (command line) and cisco Firewall is my favorite and have successfully created vpn tunnels including Cisco ASA, SonicWALL, Cyberoam, Checkpoint, Palo-Alto and lots more. As a network engineer, it doesn’t matter what vpn device you are using at each end of the vpn site.

Select Enable Keep Alive to use heartbeat messages between peers on this VPN tunnel. If one end of the tunnel fails, using Keepalives will allow for the automatic renegotiation of the tunnel once both sides become available again without having to wait for the proposed Life Time to expire.