-
Cisco IOS IPv6 Command Reference
-
Introduction
-
aaa accounting multicast default through clear ipv6 mobile home-agents
-
clear ipv6 mobile traffic through debug bgp vpnv6 unicast
-
debug crypto ipv6 ipsec through debug ipv6 pim
-
debug ipv6 pim df-election through ip http server
-
ip name-server through ipv6 general-prefix
-
ipv6 hello-interval eigrp through ipv6 mld static-group
-
ipv6 mobile home-agent (global configuration) through ipv6 ospf database-filter all out
-
ipv6 ospf dead-interval through ipv6 split-horizon eigrp
-
ipv6 summary-address eigrp through mpls ldp router-id
-
mpls traffic-eng auto-bw timers through route-map
-
router-id (IPv6) through show bgp ipv6 labels
-
show bgp ipv6 neighbors through show crypto isakmp peers
-
show crypto isakmp policy through show ipv6 eigrp neighbors
-
show ipv6 eigrp topology through show ipv6 nat statistics
-
show ipv6 nat translations through show ipv6 protocols
-
show ipv6 rip through snmp-server host
-
snmp-server user through vrf forwarding
-
Table Of Contents
ipv6 mobile home-agent (global configuration)
ipv6 mobile home-agent (interface configuration)
ipv6 mobile router-service roam
ipv6 multicast aaa account receive
ipv6 nd advertisement-interval
ipv6 nd prefix framed-ipv6-prefix
ipv6 nhrp map multicast dynamic
ipv6 ospf database-filter all out
ipv6 mobile home-agent (global configuration)
To enter home agent configuration mode, use the ipv6 mobile home-agent command in global configuration mode. To reset to the default settings of the command, use the no form of this command.
ipv6 mobile home-agent
no ipv6 mobile home-agent
Syntax Description
This command has no arguments or keywords.
Command Default
Mobile IPv6 home agent is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ipv6 mobile home-agent command to enter home agent configuration mode. Once in home agent configuration mode, you can configure binding parameters using the binding command. Once an interface is configured to provide the home-agent service, the ipv6 mobile home-agent global configuration command automatically appears in the global configuration.
The home agent service needs to be started on each interface using the ipv6 mobile home-agent command in interface configuration mode. The ipv6 mobile home-agent command in global configuration mode does not start home agent service on an interface.
Examples
In the following example, the user enters home agent configuration mode:
Router(config)# ipv6 mobile home-agentRouter(config-ha)#Related Commands
ipv6 mobile home-agent (interface configuration)
To initialize and start the Mobile IPv6 home agent on a specific interface, use the ipv6 mobile home-agent command in interface configuration mode. To discard bindings and any interface parameter settings, and to terminate home agent operation on a specific interface, use the no form of this command.
ipv6 mobile home-agent [preference preference-value]
no ipv6 mobile home-agent
Syntax Description
Command Default
Mobile IPv6 home agent is disabled.
The default preference value is 0.Command Modes
Interface configuration
Command History
Usage Guidelines
Before you enable the ipv6 mobile home-agent (interface configuration) command on an interface, you should configure common parameters using the binding command. Once an interface is configured to run the home agent feature, the ipv6 mobile home-agent command in global configuration mode automatically appears in the global configuration.
Once enabled, the ipv6 mobile home-agent (interface configuration) command cannot be disabled if there is a home agent configured on at least one of the interfaces. If there is no home agent service on any interfaces, the no form of the command disables home agent capability from the router.
To configure the home agent preference value, use the optional preference preference-value keyword and argument. A preference value is a 16-bit signed integer used by the home agent sending a router advertisement. The preference value orders the addresses returned to the mobile node in the home agent addresses field of a home agent address discovery reply message. The higher the preference value, the more preferable is the home agent.
If a preference value is not included in a router advertisement, the default value is 0. Values greater than 0 indicate a home agent more preferable than this default value.
Examples
In the following example, the user initializes and starts Mobile IPv6 agent on Ethernet interface 2:
Router(config)# interface Ethernet 2
Router(config-if)# ipv6 mobile home-agentIn the following example, the home agent preference value is set to 10:
Router(config-if)# ipv6 mobile home-agent preference 10Related Commands
ipv6 mobile router
To enable IPv6 network mobility (NEMO) functionality on a router and place the router in IPv6 mobile router configuration mode, use the ipv6 mobile router command in global configuration mode. To disable NEMO functionality on the router, use the no form of the command.
ipv6 mobile router
no ipv6 mobile router
Syntax Description
This command has no arguments or keywords.
Command Default
NEMO functionality is not enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The mobile router is a router that operates as a mobile node. The mobile router can roam from its home network and still provide connectivity for devices on its networks. The mobile networks are locally attached to the router.
Examples
In the following example, the mobile router is enabled:
Router(config)# ipv6 mobile routeripv6 mobile router-service roam
To enable the IPv6 mobile router interface to roam, use the ipv6 mobile router-service roam command in interface configuration mode. To disable roaming, use the no form if this command.
ipv6 mobile router-service roam [bandwidth-efficient | cost-efficient | optimistic | semi-optimistic | priority value]
no ipv6 mobile router-service roam
Syntax Description
Command Default
Roaming is not enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The mobile router discovers home agents and foreign agents by receiving agent advertisements.
The bandwidth-efficient keyword enables the mobile router to use the largest configured lifetime value, even when the home agent recommends a shorter lifetime in a binding refresh advice message. This option can be used when the bandwidth is expensive.
Examples
The following example shows how to enable roaming for the IPv6 mobile router interface:
Router(config-if)# ipv6 mobile router-service roamRelated Commands
show ipv6 mobile router
Displays configuration information and monitoring statistics about the IPv6 mobile router.
ipv6 mtu
To set the maximum transmission unit (MTU) size of IPv6 packets sent on an interface, use the ipv6 mtu command in interface configuration mode. To restore the default MTU size, use the no form of this command.
ipv6 mtu bytes
no ipv6 mtu bytes
Syntax Description
Command Default
The default value depends on the interface medium, but the minimum for any interface is 1280 bytes.
Command Modes
Interface configuration
Command History
Usage Guidelines
If a nondefault value is configured for an interface, an MTU option is included in router advertisements.
IPv6 routers do not fragment forwarded IPv6 packets. Traffic originating from IPv6 routers may be fragmented.
All devices on a physical medium must have the same protocol MTU in order to operate.
In addition to the "IPv6 MTU value" (set by using the ipv6 mtu command), interfaces also have a nonprotocol specific "MTU value," which is set by using the mtu interface configuration command.
Note
The "MTU value" configured by using the mtu interface configuration command must not be less than 1280 bytes.
Examples
The following example sets the maximum IPv6 packet size for serial interface 0/1 to 2000 bytes:
Router(config)# interface serial 0/1Router(config-if)# ipv6 mtu 2000Related Commands
ipv6 multicast aaa account receive
To enable authentication, authorization, and accounting (AAA) accounting on specified groups or channels, use the ipv6 multicast aaa account receive command in interface configuration mode. To disable AAA accounting, use the no form of this command.
ipv6 multicast aaa account receive access-list-name [throttle throttle-number]
no ipv6 multicast aaa account receive
Syntax Description
Command Default
No AAA accounting is performed on any groups or channels.
Command Modes
Interface configuration
Command History
Usage Guidelines
Note
Use the ipv6 multicast aaa account receive command to enable AAA accounting on specific groups or channels and to set throttle interval limits on records sent during channel surfing.
Examples
The following example enables AAA accounting using an access list named list1:
Router(config-if)# ipv6 multicast aaa account receive list1Related Commands
aaa accounting multicast default
Enables AAA accounting of IPv6 multicast services for billing or security purposes when you use RADIUS.
ipv6 multicast boundary scope
To configure a multicast boundary on the interface for a specified scope, use the ipv6 multicast boundary scope command in interface configuration mode. To disable this feature, use the no form of this command.
ipv6 multicast boundary scope scope-value
no ipv6 multicast boundary scope scope-value
Syntax Description
Command Default
Multicast boundary is not configured on the interface.
Command Modes
Interface configuration
Command History
12.3(14)T
This command was introduced.
12.2(18)SXE
This command was integrated into Cisco IOS Release 12.2(18)SXE.
Usage Guidelines
If the ipv6 multicast boundary scope command is configured for a particular scope on the Reverse Path Forwarding (RPF) interface, then packets are not accepted on that interface for groups that belong to scopes that are less than or equal to the one configured. Protocol Independent Multicast (PIM) join/prune messages for those groups are not sent on the RPF interface. The effect of the scope can be verified by checking the output of the show ipv6 mrib route command. The output will not show the RPF interface with Accept flag.
If the ipv6 multicast boundary scope command is configured for a particular scope on an interface in the outgoing interface list, packets are not forwarded for groups that belong to scopes that are less than or equal to the one configured.
Protocol Independent Multicast (PIM) join/prune (J/P) messages are not processed when received on the interface for groups that belong to scopes that are less than or equal to the one configured. Registers and bootstrap router (BSR) messages are also filtered on the boundary.
Examples
The following example sets the scope value to be a scope number of 6:
ipv6 multicast boundary scope 6Related Commands
ipv6 multicast group-range
To disable multicast protocol actions and traffic forwarding for unauthorized groups or channels on all the interfaces in a router, use the ipv6 multicast group-range command in global configuration mode. To return to the command's default settings, use the no form of this command.
ipv6 multicast group-range [access-list-name]
no ipv6 multicast group-range [access-list-name]
Syntax Description
access-list-name
(Optional) Name of an access list that contains authenticated subscriber groups and authorized channels that can send traffic to the router.
Command Default
Multicast is enabled for groups and channels permitted by a specified access list and disabled for groups and channels denied by a specified access list.
Command Modes
Global configuration
Command History
Usage Guidelines
The ipv6 multicast group-range command provides an access control mechanism for IPv6 multicast edge routing. The access list specified by the access-list-name argument specifies the multicast groups or channels that are to be permitted or denied. For denied groups or channels, the router ignores protocol traffic and actions (for example, no Multicast Listener Discovery (MLD) states are created, no mroute states are created, no Protocol Independent Multicast (PIM) joins are forwarded), and drops data traffic on all interfaces in the system, thus disabling multicast for denied groups or channels.
Using the ipv6 multicast group-range global configuration command is equivalent to configuring the MLD access control and multicast boundary commands on all interfaces in the system. However, the ipv6 multicast group-range command can be overridden on selected interfaces by using the following interface configuration commands:
•
•
Because the no ipv6 multicast group-range command returns the router to its default configuration, existing multicast deployments are not broken.
Examples
The following example ensures that the router disables multicast for groups or channels denied by an access list named list2:
Router(config)# ipv6 multicast group-range list2The following example shows that the command in the previous example is overridden on an interface specified by int2:
Router(config)# interface int2Router(config-if)# ipv6 mld access-group int-list2On int2, MLD states are created for groups or channels permitted by int-list2 but are not created for groups or channels denied by int-list2. On all other interfaces, the access-list named list2 is used for access control.
In this example, list2 can be specified to deny all or most multicast groups or channels, and int-list2 can be specified to permit authorized groups or channels only for interface int2.
Related Commands
ipv6 mld access-group
Performs IPv6 multicast receiver access control.
ipv6 multicast boundary scope
Configures a multicast boundary on the interface for a specified scope.
ipv6 multicast multipath
To enable load splitting of IPv6 multicast traffic across multiple equal-cost paths, use the ipv6 multicast multipath command in global configuration mode. To disable this function, use the no form of this command.
ipv6 multicast multipath
no ipv6 multicast multipath
Syntax Description
This command has no arguments or keywords.
Command Default
This command is enabled.
Command Modes
Global configuration
Command History
12.3(7)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
Usage Guidelines
The ipv6 multicast multipath command is enabled by default. In the default scenario, the reverse path forwarding (RPF) neighbor is selected randomly from the available equal-cost RPF neighbors, resulting in the load splitting of traffic from different sources among the available equal cost paths. All traffic from a single source is still received from a single neighbor.
When the no ipv6 multicast multipath command is configured, the RPF neighbor with the highest IPv6 address is chosen for all sources with the same prefix, even when there are other available equal-cost paths.
Because the ipv6 multicast multipath command changes the way an RPF neighbor is selected, it must be configured consistently on all routers in a redundant topology to avoid looping.
Examples
The following example enables load splitting of IPv6 traffic:
Router(config)# ipv6 multicast multipathRelated Commands
show ipv6 rpf
Checks RPF information for a given unicast host address and prefix.
ipv6 multicast-routing
To enable multicast routing using Protocol Independent Multicast (PIM) and Multicast Listener Discovery (MLD) on all IPv6-enabled interfaces of the router and to enable multicast forwarding, use the ipv6 multicast-routing command in global configuration mode. To stop multicast routing and forwarding, use the no form of this command.
ipv6 multicast-routing
no ipv6 multicast-routing
Syntax Description
This command has no arguments or keywords.
Command Default
Multicast routing is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Enabling IPv6 multicast on all interfaces also includes enabling PIM and MLD protocol processing on the interfaces. Users may configure specific interfaces before multicast is enabled, so that they can then disable PIM and MLD protocol processing on interfaces, as needed.
Examples
The following example enables multicast routing and turns on PIM and MLD on all interfaces:
ipv6 multicast-routingRelated Commands
ipv6 multicast rpf use-bgp
To enable multicast reverse path forwarding (RPF) check to use Border Gateway Protocol (BGP) unicast routes in the routing information base (RIB), use the ipv6 multicast rpf use-bgp command in global configuration mode. To disable this function, use the no form of this command.
ipv6 multicast rpf use-bgp
no ipv6 multicast rpf use-bgp
Syntax Description
This command has no arguments or keywords.
Command Default
Multicast RPF check does not use BGP unicast routes.
Command Modes
Global configuration
Command History
Usage Guidelines
When configured, multicast RPF check uses BGP unicast routes in the RIB. By default, this is not done.
Examples
The following example enables the multicast RPF check function:
ipv6 multicast rpf use-bgpipv6 nat
To designate that traffic originating from or destined for the interface is subject to Network Address Translation—Protocol Translation (NAT-PT), use the ipv6 nat command in interface configuration mode. To prevent the interface from being able to translate, use the no form of this command.
ipv6 nat
no ipv6 nat
Syntax Description
This command has no keywords or arguments.
Command Default
Traffic leaving or arriving at this interface is not subject to NAT-PT.
Command Modes
Interface configuration
Command History
Usage Guidelines
The ipv6 nat command is usually specified on at least one IPv4 interface and one IPv6 interface at the networking device where you intend to use NAT-PT.
Examples
The following example assigns the IPv4 address 192.168.30.1 to Fast Ethernet interface 1/0 and the IPv6 address 2001:0DB8:0:1::1 to Fast Ethernet interface 2/0. IPv6 routing is globally enabled and both interfaces are configured to run IPv6 and enable NAT-PT translations.
interface fastethernet 1/0ip address 192.168.30.1 255.255.255.0ipv6 nat!interface fastethernet 2/0ipv6 address 2001:0DB8:0:1::1/64ipv6 natRelated Commands
ipv6 nat max-entries
To specify the maximum number of Network Address Translation—Protocol Translation (NAT-PT) translation entries stored by the router, use the ipv6 nat max-entries command in global configuration mode. To restore the default number of NAT-PT entries, use the no form of this command.
ipv6 nat max-entries number
no ipv6 nat max-entries
Syntax Description
number
(Optional) Specifies the maximum number (1-2147483647) of NAT-PT translation entries. Default is unlimited.
Command Default
Unlimited number of NAT-PT entries.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ipv6 nat max-entries command to set the maximum number of NAT-PT translation entries stored by the router when the router memory is limited, or the actual number of translations is important.
Examples
The following example sets the maximum number of NAT-PT translation entries to 1000:
ipv6 nat max-entries 1000Related Commands
clear ipv6 nat translation
Clears dynamic NAT-PT translations from the translation table.
show ipv6 nat translations
Displays active NAT-PT translations.
ipv6 nat prefix
To assign an IPv6 prefix where matching IPv6 packets will be translated using Network Address Translation—Protocol Translation (NAT-PT), use the ipv6 nat prefix command in global configuration or interface configuration mode. To prevent the IPv6 prefix from being used by NAT-PT, use the no form of this command.
ipv6 nat prefix ipv6-prefix/prefix-length
no ipv6 nat prefix ipv6-prefix/prefix-length
Syntax Description
Command Default
No IPv6 prefixes are used by NAT-PT.
Command Modes
Global configuration
Interface configurationCommand History
Usage Guidelines
The ipv6 nat prefix command is used to specify an IPv6 address prefix against which the destination prefix in an IPv6 packet is matched. If the match is successful, NAT-PT will translate the IPv6 packet to an IPv4 packet using the configured mapping rules.
Use the ipv6 nat prefix command in global configuration mode to assign a global NAT-PTNAT-PT prefix, or in interface configuration mode to assign a different NAT-PT prefix for each interface. Using a different NAT-PT prefix on several interfaces allows the NAT-PT router to support an IPv6 network with multiple exit points to IPv4 networks.
Examples
The following example assigns the IPv6 prefix 2001:0DB8:1::/96 as the global NAT-PT prefix:
ipv6 nat prefix 2001:0DB8:1::/96The following example assigns the IPv6 prefix 2001:0DB8:2::/96 as the NAT-PT prefix for the Fast Ethernet interface 1/0, and the IPv6 prefix 2001:0DB8:4::/96 as the NAT-PT prefix for the Fast Ethernet interface 2/0:
interface fastethernet 1/0ipv6 address 2001:0DB8:2:1::1/64ipv6 nat prefix 2001:0DB8:2::/96!interface fastethernet 2/0ipv6 address 2001:0DB8:4:1::1/64ipv6 nat prefix 2001:0DB8:4::/96Related Commands
ipv6 nat prefix v4-mapped
To enable customers to send traffic from their IPv6 network to an IPv4 network without configuring IPv6 destination address mapping, use the ipv6 nat prefix v4-mapped command in global configuration or interface configuration mode. To disable this feature, use the no form of this command.
ipv6 nat prefix ipv6-prefix v4-mapped {access-list-name | ipv6-prefix}
no ipv6 nat prefix ipv6-prefix v4-mapped {access-list-name | ipv6-prefix}
Syntax Description
Command Default
This command is not enabled.
Command Modes
Global configuration
Interface configurationCommand History
Usage Guidelines
The IPv6 target address of a packet arriving at an interface is checked to discover if it has a NAT-PT prefix that was configured with the ipv6 nat prefix v4-mapped command. If the prefix does match, then an access-list check is performed to discover if the source address matches the access list or prefix list. If the prefix does not match, the packet is dropped.
If the prefix matches, source address translation is performed. If a rule has been configured for the source address translation, the last 32 bits of the destination IPv6 address is used as the IPv4 destination and a flow entry is created.
Examples
In the following example, the access list permits any IPv6 source address with the prefix 2001::/96 to go to the destination with a 2000::/96 prefix. The destination is then translated to the last 32 bit of its IPv6 address; for example: source address = 2001::1, destination address = 2000::192.168.1.1. The destination then becomes 192.168.1.1 in the IPv4 network:
ipv6 nat prefix 2000::/96 v4-mapped v4map_aclipv6 access-list v4map_aclpermit ipv6 2001::/96 2000::/96ipv6 nat translation
To change the amount of time after which Network Address Translation—Protocol Translation (NAT-PT) translations time out, use the ipv6 nat translation command in global configuration mode. To disable the timeout, use the no form of this command.
ipv6 nat translation {timeout | udp-timeout | dns-timeout | tcp-timeout | finrst-timeout | icmp-timeout | syn-timeout} {seconds | never}
no ipv6 nat translation {timeout | udp-timeout | dns-timeout | tcp-timeout | finrst-timeout | icmp-timeout | syn-timeout}
Syntax Description
Command Default
timeout: 86400 seconds (24 hours)
udp-timeout: 300 seconds (5 minutes)
dns-timeout: 60 seconds (1 minute)
tcp-timeout: 86400 seconds (24 hours)
finrst-timeout: 60 seconds (1 minute)
icmp-timeout: 60 seconds (1 minute)Command Modes
Global configuration
Command History
Usage Guidelines
Dynamic translations time out after a period of time without any translations. The default timeout period is 24 hours. When port translation is configured, there is finer control over translation entry timeouts because each entry contains more context about the traffic that is using it. Non-DNS UDP translations time out after 5 minutes, and DNS times out in 1 minute. TCP translations time out in 24 hours, unless an RST or FIN flag is seen on the stream, in which case they will time out in 1 minute.
Examples
The following example causes UDP port translation entries to time out after 10 minutes:
ipv6 nat translation udp-timeout 600Related Commands
clear ipv6 nat translation
Clears dynamic NAT-PT translations from the translation table.
show ipv6 nat translations
Displays active NAT-PT translations.
ipv6 nat v4v6 pool
To define a pool of IPv6 addresses for Network Address Translation—Protocol Translation (NAT-PT), use the ipv6 nat v4v6 pool command in global configuration mode. To remove one or more addresses from the pool, use the no form of this command.
ipv6 nat v4v6 pool name start-ipv6 end-ipv6 prefix-length prefix-length
no ipv6 nat v4v6 pool name start-ipv6 end-ipv6 prefix-length prefix-length
Syntax Description
Command Default
No pool of addresses is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines a pool of IPv6 addresses using start address, end address, and prefix length. The pool is used when NAT-PT needs a dynamic mapping of an IPv6 address to translate an IPv4 address.
Examples
The following example configures a dynamic NAT-PT mapping to translate IPv4 addresses to IPv6 addresses using a pool of IPv6 addresses named v6pool. The packets to be translated by NAT-PT are filtered using an access list named pt-list2. One static NAT-PT mapping is configured to access a Domain Naming System (DNS) server. Ethernet interface 3/1 is an IPv6-only host and Ethernet interface 3/3 is an IPv4-only host.
interface Ethernet3/1ipv6 address 2001:0DB8:AABB:1::9/64ipv6 enableipv6 nat!interface Ethernet3/3ip address 192.168.30.9 255.255.255.0ipv6 nat!ipv6 nat v4v6 source list pt-list2 pool v6poolipv6 nat v4v6 pool v6pool 2001:0DB8:EEFF::1 2001:0DB8:EEFF::2 prefix-length 128ipv6 nat v6v4 source 2001:0DB8:AABB:1::1 10.21.8.0ipv6 nat prefix 2001:0DB8:EEFF::/96!access-list pt-list2 permit 192.168.30.0 0.0.0.255Related Commands
clear ipv6 nat translations
Clears dynamic NAT-PT translations from the translation table.
show ipv6 nat translations
Displays active NAT-PT translations.
ipv6 nat v4v6 source
To configure IPv4 to IPv6 address translation using Network Address Translation—Protocol Translation (NAT-PT), use the ipv6 nat v4v6 source command in global configuration mode. To remove the static translation or remove the dynamic association to a pool, use the no form of this command.
ipv6 nat v4v6 source {list {access-list-number | name} pool name | ipv4-address ipv6-address}
no ipv6 nat v4v6 source {list {access-list-number | name} pool name | ipv4-address ipv6-address}
Syntax Description
Command Default
No NAT-PT translation of IPv4 to IPv6 addresses occurs.
Command Modes
Global configuration
Command History
Usage Guidelines
This command has two forms: dynamic and static address translation. The form with an IPv6 access list establishes dynamic translation. Packets from IPv4 addresses that match the standard access list are translated using IPv6 addresses allocated from the pool named with the ipv6 nat v4v6 pool command. The access list is used to specify which traffic is to be translated.
Alternatively, the syntax form using the ipv4-address and ipv6-address arguments establishes a single static translation.
Examples
The following example configures a dynamic NAT-PT mapping to translate IPv4 addresses to IPv6 addresses using a pool of IPv6 addresses named v6pool. The packets to be translated by NAT-PT are filtered using an access list named pt-list2. Ethernet interface 3/1 is an IPv6-only host and Ethernet interface 3/3 is an IPv4-only host.
interface Ethernet3/1ipv6 address 2001:0DB8:AABB:1::9/64ipv6 enableipv6 nat!interface Ethernet3/3ip address 192.168.30.9 255.255.255.0ipv6 nat!ipv6 nat v4v6 source list pt-list2 pool v6poolipv6 nat v4v6 pool v6pool 2001:0DB8:EEFF::1 2001:0DB8:EEFF::2 prefix-length 128ipv6 nat prefix 3ffe:c00:yyyy::/96!access-list pt-list2 permit 192.168.30.0 0.0.0.255The following example shows a static translation where the IPv4 address 192.168.30.1 is translated into the IPv6 address 2001:0DB8:EEFF::2:
ipv6 nat v4v6 source 192.168.30.1 2001:0DB8:EEFF::2Related Commands
ipv6 nat v6v4 pool
To define a pool of IPv4 addresses for Network Address Translation—Protocol Translation (NAT-PT), use the ipv6 nat v6v4 pool global configuration command. To remove one or more addresses from the pool, use the no form of this command.
ipv6 nat v6v4 pool name start-ipv4 end-ipv4 prefix-length prefix-length
no ipv6 nat v6v4 pool name start-ipv4 end-ipv4 prefix-length prefix-length
Syntax Description
Command Default
No pool of addresses is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines a pool of IPv4 addresses using start address, end address, and prefix length.
