IPv6 Routing: Multiprotocol BGP Link-Local Address Peering
|
|||||||||||||||||||||||
Contents
IPv6 Routing: Multiprotocol BGP Link-Local Address PeeringLast Updated: November 30, 2012
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About IPv6 Routing: Multiprotocol BGP Link-Local Address PeeringIPv6 Multiprotocol BGP Peering Using a Link-Local AddressThe IPv6 multiprotocol BGP can be configured between two IPv6 devices (peers) using link-local addresses. For this function to work, the interface for the neighbor must be identified by using the neighbor update-source command, and a route map must be configured to set an IPv6 global next hop. How to Configure IPv6 Routing: Multiprotocol BGP Link-Local Address PeeringConfiguring an IPv6 Multiprotocol BGP Peer Using a Link-Local AddressConfiguring IPv6 multiprotocol BGP between two IPv6 devices (peers) using link-local addresses requires that the interface for the neighbor be identified by using the neighbor update-source command and that a route map be configured to set an IPv6 global next hop. DETAILED STEPS Configuration Examples for IPv6 Routing: Multiprotocol BGP Link-Local Address PeeringExample: Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local AddressThe following example configures the IPv6 multiprotocol BGP peer FE80::1234:BFF:FE0E:A471 over Fast Ethernet interface 0 and sets the route map named nh6 to include the IPv6 next-hop global address of Fast Ethernet interface 0 in BGP updates. The IPv6 next-hop link-local address can be set by the nh6 route map (not shown in the following example) or from the interface specified by the neighbor update-source command (as shown in the following example). router bgp 65000 neighbor FE80::1234:BFF:FE0E:A471 remote-as 64600 neighbor FE80::1234:BFF:FE0E:A471 update-source fastethernet 0 address-family ipv6 neighbor FE80::1234:BFF:FE0E:A471 activate neighbor FE80::1234:BFF:FE0E:A471 route-map nh6 out route-map nh6 permit 10 match ipv6 address prefix-list cisco set ipv6 next-hop 2001:DB8:526::1 ipv6 prefix-list cisco permit 2001:DB8:2F22::/48 le 128 ipv6 prefix-list cisco deny ::/0 Additional ReferencesRelated Documents
MIBsTechnical Assistance
Feature Information for IPv6 Routing: Multiprotocol BGP Link-Local Address PeeringThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||