Security Basics mailing list archives
RE: Cisco Workaround
From: "Dozal, Tim" <tdozal () cisco com>
Date: Thu, 31 Jul 2003 16:40:57 -0700
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml Cisco TAC I'm sure could also help. The link above has all of the #'s world wide for 24/7 support. Tim -----Original Message----- From: Vachon, Scott [mailto:Scott.Vachon () paymentech com] Sent: Thursday, July 31, 2003 10:52 AM To: security-basics () securityfocus com Subject: RE: Cisco Workaround
Background: We have a Cisco 827 router and a PIX 506e locally. Router being in
front of
the PIX. We also have a co-location facility that we are connected via
a
constant VPN tunnel. There we have a PIX 515e. The two pixes are what control the VPN/encryption.
<snip>
So we upgraded the router to the latest version. Everything worked ok, except, the VPN tunnel. That got knocked out.
Keep
in mind that I am no Cisco expert. ...So after a little messing around we reverted back to the old IOS and everything was peachy. A couple days later they sent us another
version to
upgrade with and that did the same thing. Needless to say, we are
still
upgradeless. If there are any suggestions out there, I would really appreciate it.
If I
didn't give enough info, please let me know, and I will get you
whatever you
need (within my power of course).
There are 3 different varieties of the 827 (827, 827-4V, and 827H) . There are also 3 different IOS version for the 827 (assuming you chose 12.3 line for the 827 only) IP, IP Plus, and IP/FW. I think the IP/FW is the version you want. The image is: c820-oy6-mz.123-1a.bin . If you don't have this, you may not have the VPN tunnel ability (I haven't worked with the 800 line ) . Why not post to us the IOS image name that you use currently and we can help you find the correct upgrade version. ~S~ Disclaimer: My 2 cents. Learn more about Paymentech's payment processing services at www.paymentech.com THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. ------------------------------------------------------------------------ --- ------------------------------------------------------------------------ ---- --------------------------------------------------------------------------- ----------------------------------------------------------------------------
Current thread:
- RE: Cisco Workaround Dozal, Tim (Jul 31)
- <Possible follow-ups>
- RE: Cisco Workaround Douglas Gullett (Aug 04)
- RE: Cisco Workaround Adam Overlin (Aug 04)
- RE: Cisco Workaround David Gillett (Aug 04)
- RE: Cisco Workaround stephen at unix dot za dot net (Aug 11)
- RE: Cisco Workaround David Gillett (Aug 11)
- RE: Cisco Workaround Cesar Osorio (Aug 12)
- RE: Cisco Workaround Cesar Osorio (Aug 12)