Cisco Cisco ASA 5525-X Adaptive Security Appliance - No Payload Encryption Manual Técnica

Descargar
Página de 18
Introduction
This document describes how to configure the Cisco Adaptive Security Appliance (ASA) in order to pass
Internet Protocol Version 6 (IPv6) traffic in ASA Versions 7.0(1) and later.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on the Cisco ASA Versions 7.0(1) and later.
The information in this document was created from the devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.
Background Information
Currently, IPv6 is still relatively new in terms of market penetration. However, IPv6 configuration assistance
and troubleshooting requests have steadily increased. The purpose of this document is to address those needs
and provide:
A general overview of IPv6 usage
• 
The basic IPv6 configurations on the ASA
• 
Information about how to troubleshoot IPv6 connectivity through the ASA
• 
A list of the most common IPv6 problems and solutions, as identified by the Cisco Technical
Assistance Center (TAC)
• 
Note: Given that IPv6 is still in the early stages as an IPv4 replacement globally, this document will be
periodically updated in order to maintain accuracy and relevance.
IPv6 Feature Information
Here is some important information about the IPv6 functionality:
The IPv6 protocol was first introduced in ASA Version 7.0(1).
• 
Support for IPv6 in transparent mode was introduced in ASA Version 8.2(1).
• 
IPv6 Overview
The IPv6 protocol was developed in the mid to late 1990s, primarily due to the fact that the public IPv4
address space moved quickly towards depletion. Although Network Address Translation (NAT) dramatically
helped IPv4 and delayed this problem, it became undeniable that a replacement protocol would eventually be
needed. The IPv6 protocol was officially detailed in RFC 2460 in December 1998. You can read more about