Discussion Locked

Cisco PIX to PIX VPN config

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Help me out here, I am configuring a PIX-PIX VPN I have performed the VPN wizard on both Pixii (is that plural for Pix). Can ping Pix to Pix. The monitors show packets being decrypted and encrypted on the boxes. We will be using a terminal emulation client on the the remote PC's to access and RS6000 box. All configs are correct at the host site as the emulation is working there.

What have I missed at the remote site. The emulation software times out while connecting.
The model for my configs is the White paper from Cisco called "configuring Pix-toPix-to-Pix IPsec (hub and spoke)" Do I need to open some ports on the Pix to allow connection with the emulator or will "IP ANY" Work?

6 replies

by acattr

http://tinyurl.com/348e

I used the link above to setup pix to pix ipsec VPNs many times. One thing you should make note is that every single device/pc needs to have the pix as the default gateway(or atleast have a route pointing to the pix for that other network), otherwise they won't talk to other pcs across the vpn and you'll get a timeout.

I would tell you to check your accesslists but you said the monitor shows decrypting of traffic.

ex.
access-list 101 permit ip 10.1.1.0 255.255.255.0 172.16.1.0 255.255.255.0

by acattr

simply put, make sure the RS6000 uses the PIX as the router to the other network over the vpn.

by joshg

That was it, the AIX box was using the CISCO 2600 for its gateway. I couldn't change that since it runs 8 frame circuits so I added a static route in the 2600 with the PIX as the gate for the remote site.

by colin p. mcnamara

Ok, 1st thing, without posting your configs, (omiting passwords and keys) it makes it hard to help) but here we go.
There are a few things that generaly cludge up an IPsec tunnel, and the only way to fix them is to do some debugs on your pix.
1. tunnel traffic is being translated by your NAT overload. - execute "sho xlate" while trying to connect into the core site, and note if you see your source address in the tranlations. If so make sure there is a NAT 0 (inside) "your access list" statement with your traffic specified.
2. Traffic is not being matched by your crypto maps - look through your config, there will be a section down at the bottom where it will say crypto map xxxxx and it will reference an access-list. Note that access-list and then execute "show access-list" while pinging the remote site, look for incrimenting numbers.
3. Isakmp Security Associations. execute "show crypto isakmp sa" and note if it says anything other then QM_IDLE.
4. if you have gotten to this point, break down and Call Cisco Tac, they are pretty good guys for the most part, and come as a service with your SMARTnet contract.

Cheers,
Colin McNamara

by joshg

Sorry, all of that checks out. The server was sending its traffic to its gateway which was as 2600 router. see the response above.

Thanks

This discussion is closed to new replies.