Difference between revisions of "Static Routes IPv6 Cisco IOS"

From Teknologisk videncenter
Jump to: navigation, search
m (Next Hop address)
m (Next Hop address)
 
(4 intermediate revisions by the same user not shown)
Line 5: Line 5:
  
 
=Next Hop address=
 
=Next Hop address=
When configuring static Routes in IPv6 it is not recommended to use ''global unicast'' addresses as next-hop address. Use Link-local adresses.
+
When configuring static Routes in IPv6 it is not recommended to use [[Global Unicast IPv6 Address|global unicast]] addresses as next-hop address. Use the [[Link-Local IPv6 Address|Link Local]] adresses.
  
 
{{Technote|heading=extract from {{rfc|rfc=2461}}
 
{{Technote|heading=extract from {{rfc|rfc=2461}}
|A router must be able to determine the link-local address of each of its neighboring routers in order to ensure that the target address of a Redirect message identifies the neighbor router by its link-local address.
+
|A router must be able to determine the [[Link-Local IPv6 Address|Link Local]] address of each of its neighboring routers in order to ensure that the target address of a Redirect message identifies the neighbor router by its [[Link-Local IPv6 Address|Link Local]] address.
 
}}
 
}}
Link-local addresses however uses [[EUI-64]] based on the Routers MAC-address. If the Router is replaced the neighboring Routers will have to be reconfigured with the new Link-local address. How to avoid this mess I do not know. When configuring IPv6 addresses on Router interfaces I set the Link-local IPv6 address to match the Global unique IPv6 address. See example below.
+
[[Link-Local IPv6 Address|Link Local]] addresses however uses [[EUI-64]] based on the Routers MAC-address. If the Router is replaced the neighboring Routers will have to be reconfigured with the new [[Link-Local IPv6 Address|Link Local]] address.
 +
 
 +
=Random Link-local=
 +
How to avoid this mess I do not know. When configuring IPv6 addresses on Router interfaces I set the [[Link-Local IPv6 Address|Link Local]] IPv6 address to match the [[Global Unicast IPv6 Address|global unicast]] address. See example below.
 
<source lang=cli>
 
<source lang=cli>
 
interface FastEthernet1/0
 
interface FastEthernet1/0
 
  ipv6 address 2001:16D8:DD85:B280::2/64
 
  ipv6 address 2001:16D8:DD85:B280::2/64
 
  ipv6 address FE80:16D8:DD85:B280::2 link-local
 
  ipv6 address FE80:16D8:DD85:B280::2 link-local
 +
</source>
 +
==Prefix Renumbering==
 +
The above method gives the problem when a site is renummbered having multiple IPv6  [[Global Unicast IPv6 Address|global unicast]] addresses for a period. There can be only one [[Link-Local IPv6 Address|Link Local]] IPv6 Address pr. Interface.
 +
==Default Gateway==
 +
If the Router is Default Gateway it's preferable to set the Router Preference to high
 +
<source lang=cli>
 +
interface FastEthernet1/0
 +
ipv6 nd router-preference High
 
</source>
 
</source>
  
Line 20: Line 31:
 
*[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-stat_routes.html Cisco IPv6 static Rotues]
 
*[http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-stat_routes.html Cisco IPv6 static Rotues]
 
*[http://www.6diss.org/workshops/see-2/routing-external.pdf 6DISS Workshop notes from 2007]
 
*[http://www.6diss.org/workshops/see-2/routing-external.pdf 6DISS Workshop notes from 2007]
 +
*{{rfc|rfc=2461}}
 
{{Source cli}}
 
{{Source cli}}
 
[[Category:IPv6]]
 
[[Category:IPv6]]

Latest revision as of 17:50, 18 December 2011

The basic syntax for configuring IPv6 statis routes is the same as in IPv4

IPv4
ip route [ipv4_prefix][ipv4_address_mask][ipv4_if_address]
IPv6
ipv6 route [ipv6_prefix/prefix_length][ipv6_if_address]
Ex: ipv6 route ::/0 FastEthernet0/1 FE80::206:2AFF:FEa0:ce84

Next Hop address

When configuring static Routes in IPv6 it is not recommended to use global unicast addresses as next-hop address. Use the Link Local adresses.

Clean.png
A router must be able to determine the Link Local address of each of its neighboring routers in order to ensure that the target address of a Redirect message identifies the neighbor router by its Link Local address.
extract from rfc2461

Link Local addresses however uses EUI-64 based on the Routers MAC-address. If the Router is replaced the neighboring Routers will have to be reconfigured with the new Link Local address.

Random Link-local

How to avoid this mess I do not know. When configuring IPv6 addresses on Router interfaces I set the Link Local IPv6 address to match the global unicast address. See example below.

interface FastEthernet1/0
 ipv6 address 2001:16D8:DD85:B280::2/64
 ipv6 address FE80:16D8:DD85:B280::2 link-local

Prefix Renumbering

The above method gives the problem when a site is renummbered having multiple IPv6 global unicast addresses for a period. There can be only one Link Local IPv6 Address pr. Interface.

Default Gateway

If the Router is Default Gateway it's preferable to set the Router Preference to high

interface FastEthernet1/0
ipv6 nd router-preference High

Links