Correct approach to testing VPNs

Hi there,

I'm in the process of upgrading some old firewalls to some new ones. There are some VPNs setup already. The config from the old fw's has been copied to the new ones. I'm going to swap the cables from the relevant interfaces. I'm looking for a way to verify that the VPNs are up and are passing traffic on the new firewalls after I swap the cables. I'm used to having an object-group of hosts. I wanted to develop a list of tests for example ping some host (on the other side of the VPN) or telnet to it on port 22 or 3389. However the VPNs configured on these firewalls match traffic from network to network. I'm not sure what is used across the VPNs as they are customer systems.

What I've come up with so far:
Use "sh crypto isakmp sa" before and after (but that counts on something generating VPN traffic to bring the tunnel up)
Use the ping command to source the ping from the correct network
Use "sh crypto map"

I'm not sure what the correct approach is here.
jackface_oAsked:
Who is Participating?
 
rauenpcConnect With a Mentor Commented:
Without being able to pass traffic to/from the specified networks, this may be a difficult task.

"show crypto ipsec sa peer x.x.x.x" will show all the network to network tunnels and packet counters so that might help, but if no traffic is going across there won't be anything to look at. In the past, I sent out a notification to all my customers asking that they have someone willing to test the link after the changes.
0
 
jackface_oAuthor Commented:
Where we knew we could pass traffic we wrote up some tests. Where we do not know we are asking the customer and their 3rd parties to confirm.
0
All Courses

From novice to tech pro — start learning today.