Cisco VPN Services Port Adapter Configuration Guide
Preface
Downloads: This chapterpdf (PDF - 146.0KB) The complete bookPDF (PDF - 8.37MB) | Feedback

Preface

Table Of Contents

Preface

Objectives

Audience

Document Revision History

Organization

Document Conventions

Related Documentation

Obtaining Documentation and Submitting a Service Request

Notices

OpenSSL/Open SSL Project

License Issues


Preface


This preface describes the objectives and organization of this document and explains how to find additional information on related products and services. This preface contains the following sections:

Objectives

Audience

Document Revision History

Organization

Document Conventions

Related Documentation

Obtaining Documentation and Submitting a Service Request

Notices

Objectives

This document describes the configuration and troubleshooting of the VPN Services Port Adapter (VSPA) and its associated Services SPA Carrier-600 (SSC-600) in the Catalyst 6500 Series switch.

This document does not contain the instructions to install the VSPA in the Catalyst 6500 Series switch. For information on installing the module, refer to the Cisco VPN Services Port Adapter Hardware Installation Guide.

Audience

This publication is for experienced network administrators who configure and maintain VPN systems and the Catalyst 6500 Series switch.

Document Revision History

records technical changes to this document. The table shows the Cisco IOS software release number and document revision number for the change, the date of the change, and a brief summary of the change.

Table 1 Document Revision History

Cisco IOS Release No.
Revision
Date
Change Summary

12.2(33)SXI

OL-16406-01

November 2008

First release.


Organization

This document contains the following chapters:

Chapter
Title
Description

Chapter 1

Overview of the VPN Services Port Adapter

Provides an introduction to the VSPA and the command-line interface (CLI).

Chapter 2

Overview of the IPsec Features

Provides a summary of the IPsec modes and features supported by the VSPA.

Chapter 3

Configuring VPNs in Crypto-Connect Mode

Describes the general configuration of the VSPA in crypto-connect mode.

Chapter 4

Configuring VPNs in VRF Mode

Describes the general configuration of the VSPA in VRF mode.

Chapter 5

Configuring IPsec VPN Fragmentation and MTU

Describes the general configuration of IPSec VPN fragmentation and MTU for the VSPA.

Chapter 6

Configuring Quality of Service

Describes the configuration of the Quality of Service (QoS) features of the VSPA.

Chapter 7

Configuring IKE Features

Describes the configuration of the Internet Key Exchange (IKE) features of the VSPA.

Chapter 8

Configuring Enhanced IPsec Features

Describes the configuration of enhanced security and performance features of the VSPA.

Chapter 9

Configuring PKI

Describes the configuration of the Public Key Infrastructure (PKI) features of the VSPA.

Chapter 10

Configuring Advanced VPNs

Describes the configuration of the DMVPN and EasyVPN advanced features of the VSPA.

Chapter 11

Configuring Duplicate Hardware and IPsec Failover

Describes the configuration of IPsec failover using the duplicate hardware capabilities of the VSPA.

Chapter 12

Configuring Monitoring and Accounting

Describes the configuration of the monitoring and accounting features of the VSPA.

Chapter 13

Troubleshooting

Describes techniques that you can use to troubleshoot the operation of the VSPA.


Document Conventions

This document uses the following conventions:


Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.



Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.


Tip Means the following information will help you solve a problem.


Command descriptions use these conventions:

Convention
Description

boldface font

Commands and keywords are in boldface.

italic font

Arguments for which you supply values are in italics.

[ ]

Elements in square brackets are optional.

[ x | y | z ]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.


Screen examples use these conventions:

screen font

Terminal sessions and information that the switch displays are in screen font.

boldface screen font

Information that you must enter is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

< >

Non-printing characters, such as passwords, are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or number sign (#) at the beginning of a line of code indicates a comment line.


Related Documentation

Additional information related to the VSPA can be found in the following resources:

For VSPA hardware installation instructions and guidelines, see the Cisco VPN Services Port Adapter Hardware Installation Guide at this URL:

http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/vspa/hardware/ivmhw_book.html

For detailed information about the security configuration concepts described in this guide, see the Cisco IOS Security Configuration Guide, Release 12.2 at this URL:

http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html

For detailed information about the cryptographic commands used in this guide, see the Cisco IOS Security Command Reference at this URL:

http://www.cisco.com/en/US/docs/ios/security/command/reference/sec_book.html

For information about configuring the Catalyst 6500 Series switch, see the Catalyst 6500 Series Switch Software Configuration Guide, Release 12.2SXH at this URL:

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/book.html

For information about managing your system images and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 at this URL:

http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html

To understand the Cisco IOS command-line interface and Cisco IOS command modes, see the Cisco IOS Configuration Fundamentals Command Reference at this URL:

http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_book.html

To determine whether a feature is supported by a Cisco IOS release, or to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS software with the hardware installed on your switch, Cisco maintains the Software Advisor tool on Cisco.com. You must be a registered user on Cisco.com to access this tool. To access Software Advisor, click Login at Cisco.com, type "Software Advisor" in the SEARCH box, and click GO. Click the link for the Software Advisor tool.


Note You can access Cisco IOS software configuration and hardware installation and maintenance documentation on the World Wide Web at http://www.cisco.com. Translated documentation is available at the following URL: http://www.cisco.com/web/siteassets/locator/index.html.


Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].