You're right Paul. This is a great resource. One thing that I believe is very useful along with this document is to lab up a VPN and then once its up and working... break it. This document gives some good ideas in the "Sample Error Messages" section. Actually locating the error in a live output is invaluable. -- Regards,
Brandon Carroll - CCIE #23837 Senior Technical Instructor - IPexpert Mailto: [email protected] Telephone: +1.810.326.1444 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Classroom and Self-Study Cisco CCNA (R&S, Voice & Security), CCNP, CCVP, CCSP and CCIE (R&S, Voice, Security & Service Provider) Certification Training with locations throughout the United States, Europe and Australia. Be sure to check out our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com. > From: Paul Stewart <[email protected]> > Date: Thu, 4 Mar 2010 20:38:27 -0500 > To: <[email protected]> > Subject: [OSL | CCIE_Security] DocCD Link Recomendation > > Okay, I know it is really important to know IPSEC debugging front to > back. However, I think it is still worth it to make a mental note of > how to get to the following document. > > IPsec Troubleshooting: Understanding and Using debug Commands-- > http://www.cisco.com/en/US/tech/tk583/tk372/technologies_tech_note09186a008009 > 49c5.shtml > > To find this using the DocCD go to the following-- > > DocCD > Technology > Security AND VPN > IPSec Negotiation/IKE > Protocols > Troubleshooting TechNotes > > > Search for Debug > > Click on article > > There is some good stuff here. Most should be known prior to your lab > attempt, but still valuable in a pinch IMO. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
