- Implementing IPv6 Addressing and Basic Connectivity
- Implementing ADSL and Deploying Dial Access for IPv6
- Implementing Bidirectional Forwarding Detection for IPv6
- Implementing Multiprotocol BGP for IPv6
- Implementing DHCP for IPv6
- Implementing Dynamic Multipoint VPN for IPv6
- Implementing EIGRP for IPv6
- Configuring First Hop Redundancy Protocols in IPv6
- Implementing First Hop Security in IPv6
- Implementing IPsec in IPv6 Security
- Implementing IS-IS for IPv6
- Implementing IPv6 for Network Management
- Implementing Mobile IPv6
- Implementing IPv6 Multicast
- Implementing NAT-PT for IPv6
- Netflow v9 for IPv6
- Implementing NTPv4 in IPv6
- Implementing OSPFv3
- Implementing IPv6 over MPLS
- Implementing IPv6 VPN over MPLS
- Implementing Policy-Based Routing for IPv6
- Implementing QoS for IPv6
- Implementing RIP for IPv6
- Implementing Traffic Filters and Firewalls for IPv6 Security
- Implementing Static Routes for IPv6
- Implementing Tunneling for IPv6
- Configuring an IPv6 BGP Routing Process and BGP Router ID
- Configuring IPv6 Multiprotocol BGP Between Two Peers
- Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
- Configuring an IPv6 Multiprotocol BGP Peer Group
- Advertising Routes into IPv6 Multiprotocol BGP
- Configuring a Route Map for IPv6 Multiprotocol BGP Prefixes
- Redistributing Prefixes into IPv6 Multiprotocol BGP
- Advertising IPv4 Routes Between IPv6 BGP Peers
- Assigning BGP Administrative Distance for Multicast BGP Routes
- Generating IPv6 Multicast BGP Updates
- Configuring the IPv6 BGP Graceful Restart Capability
- Resetting IPv6 BGP Sessions
- Clearing External BGP Peers
- Clearing IPv6 BGP Route Dampening Information
- Clearing IPv6 BGP Flap Statistics
- Verifying IPv6 Multiprotocol BGP Configuration and Operation
- Example: Configuring a BGP Process, BGP Router ID, and IPv6 Multiprotocol BGP Peer
- Example: Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
- Example: Configuring an IPv6 Multiprotocol BGP Peer Group
- Example: Advertising Routes into IPv6 Multiprotocol BGP
- Example: Configuring a Route Map for IPv6 Multiprotocol BGP Prefixes
- Example: Redistributing Prefixes into IPv6 Multiprotocol BGP
- Example: Advertising IPv4 Routes Between IPv6 Peers
Implementing Multiprotocol BGP for IPv6
This module describes how to configure multiprotocol Border Gateway Protocol (BGP) for IPv6. BGP is an Exterior Gateway Protocol (EGP) used mainly to connect separate routing domains that contain independent routing policies (autonomous systems). Connecting to a service provider for access to the Internet is a common use for BGP. BGP can also be used within an autonomous system, and this variation is referred to as internal BGP (iBGP). Multiprotocol BGP is an enhanced BGP that carries routing information for multiple network layer protocol address families; for example, the IPv6 address family and IP multicast routes. All BGP commands and routing policy capabilities can be used with multiprotocol BGP.
Finding Feature Information
Your 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 Implementing Multiprotocol BGP for IPv6
Multiprotocol BGP Extensions for IPv6
Multiprotocol BGP is the supported exterior gateway protocol (EGP) for IPv6. Multiprotocol BGP extensions for IPv6 supports many of the same features and functionality as IPv4 BGP. IPv6 enhancements to multiprotocol BGP include support for an IPv6 address family and network layer reachability information (NLRI) and next hop (the next router in the path to the destination) attributes that use IPv6 addresses.
IPv6 Multiprotocol BGP Peering Using a Link-Local Address
The 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.
Multiprotocol BGP for the IPv6 Multicast Address Family
The multiprotocol BGP for the IPv6 multicast address family feature provides multicast BGP extensions for IPv6 and supports the same features and functionality as IPv4 BGP. IPv6 enhancements to multicast BGP include support for an IPv6 multicast address family and network layer reachability information (NLRI) and next hop (the next router in the path to the destination) attributes that use IPv6 addresses.
Multicast BGP is an enhanced BGP that allows the deployment of interdomain IPv6 multicast. Multiprotocol BGP carries routing information for multiple network layer protocol address families; for example, IPv6 address family and for IPv6 multicast routes. The IPv6 multicast address family contains routes used for RPF lookup by the IPv6 PIM protocol, and multicast BGP IPv6 provides for interdomain transport of the same. Users must use multiprotocol BGP for IPv6 multicast when using IPv6 multicast with BGP because the unicast BGP learned routes will not be used for IPv6 multicast.
Multicast BGP functionality is provided through a separate address family context. A subsequent address family identifier (SAFI) provides information about the type of the network layer reachability information that is carried in the attribute. Multiprotocol BGP unicast uses SAFI 1 messages, and multiprotocol BGP multicast uses SAFI 2 messages. SAFI 1 messages indicate that the routes are usable only for IP unicast, not IP multicast. Because of this functionality, BGP routes in the IPv6 unicast RIB must be ignored in the IPv6 multicast RPF lookup.
A separate BGP routing table is maintained to configure incongruent policies and topologies (for example, IPv6 unicast and multicast) by using IPv6 multicast RPF lookup. Multicast RPF lookup is very similar to the IP unicast route lookup.
No MRIB is associated with the IPv6 multicast BGP table. However, IPv6 multicast BGP operates on the unicast IPv6 RIB when needed. Multicast BGP does not insert or update routes into the IPv6 unicast RIB.
Nonstop Forwarding and Graceful Restart for MP-BGP IPv6 Address Family
The graceful restart capability is supported for IPv6 BGP unicast, multicast, and VPNv6 address families, enabling Cisco nonstop forwarding (NSF) functionality for BGP IPv6. The BGP graceful restart capability allows the BGP routing table to be recovered from peers without keeping the TCP state.
NSF continues forwarding packets while routing protocols converge, therefore avoiding a route flap on switchover. Forwarding is maintained by synchronizing the FIB between the active and standby RP. On switchover, forwarding is maintained using the FIB. The RIB is not kept synchronized; therefore, the RIB is empty on switchover. The RIB is repopulated by the routing protocols and subsequently informs FIB about RIB convergence by using the NSF_RIB_CONVERGED registry call. The FIB tables are updated from the RIB, removing any stale entries. The RIB starts a failsafe timer during RP switchover, in case the routing protocols fail to notify the RIB of convergence.
The Cisco BGP address family identifier (AFI) model is designed to be modular and scalable, and to support multiple AFI and subsequent address family identifier (SAFI) configurations.
How to Implement Multiprotocol BGP for IPv6
When configuring multiprotocol BGP extensions for IPv6, you must create the BGP routing process, configure peering relationships, and customize BGP for your particular network.
- Configuring an IPv6 BGP Routing Process and BGP Router ID
- Configuring IPv6 Multiprotocol BGP Between Two Peers
- Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
- Configuring an IPv6 Multiprotocol BGP Peer Group
- Advertising Routes into IPv6 Multiprotocol BGP
- Configuring a Route Map for IPv6 Multiprotocol BGP Prefixes
- Redistributing Prefixes into IPv6 Multiprotocol BGP
- Advertising IPv4 Routes Between IPv6 BGP Peers
- Assigning BGP Administrative Distance for Multicast BGP Routes
- Generating IPv6 Multicast BGP Updates
- Configuring the IPv6 BGP Graceful Restart Capability
- Resetting IPv6 BGP Sessions
- Clearing External BGP Peers
- Clearing IPv6 BGP Route Dampening Information
- Clearing IPv6 BGP Flap Statistics
- Verifying IPv6 Multiprotocol BGP Configuration and Operation
Configuring an IPv6 BGP Routing Process and BGP Router ID
Perform this task to configure an IPv6 BGP routing process and an optional BGP router ID for a BGP-speaking device.
BGP uses a router ID to identify BGP-speaking peers. The BGP router ID is 32-bit value that is often represented by an IPv4 address. By default, the router ID is set to the IPv4 address of a loopback interface on the device. If no loopback interface is configured on the device, then the software chooses the highest IPv4 address configured to a physical interface on the device to represent the BGP router ID.
When configuring BGP on a device that is enabled only for IPv6 (the device does not have an IPv4 address), you must manually configure the BGP router ID for the device. The BGP router ID, which is represented as a 32-bit value using an IPv4 address syntax, must be unique to the BGP peers of the device.
DETAILED STEPS
Configuring IPv6 Multiprotocol BGP Between Two Peers
By default, neighbors that are defined using the neighbor remote-as command in router configuration mode exchange only IPv4 unicast address prefixes. To exchange other address prefix types, such as IPv6 prefixes, neighbors must also be activated using the neighbor activate command in address family configuration mode for the other prefix types, as shown for IPv6 prefixes.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Device(config-router)# neighbor 2001:DB8:0:CC00::1 remote-as 64600 |
Adds the IPv6 address of the neighbor in the specified autonomous system to the IPv6 multiprotocol BGP neighbor table of the local device. |
|
Example: Device(config-router)# address-family ipv6 |
Specifies the IPv6 address family and enters address family configuration mode. |
|
Example: Device(config-router-af)# neighbor 2001:DB8:0:CC00::1 activate |
Enables the neighbor to exchange prefixes for the IPv6 address family with the local device. |
Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
Configuring 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.
Note |
|
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Device(config-router)# neighbor FE80::1234:BFF:FE0E:A471% remote-as 64600 |
Adds the link-local IPv6 address of the neighbor in the specified remote autonomous system to the IPv6 multiprotocol BGP neighbor table of the local device. |
|
Example: Device(config-router)# neighbor FE80::1234:BFF:FE0E:A471% update-source fastethernet0 |
Specifies the link-local address over which the peering is to occur.
|
|
Example: Device(config-router)# address-family ipv6 |
Specifies the IPv6 address family, and enters address family configuration mode. |
|
Example: Device(config-router-af)# neighbor FE80::1234:BFF:FE0E:A471% activate |
Enables the neighbor to exchange prefixes for the IPv6 address family with the local device using the specified link-local addresses. |
|
Example: Device(config-router-af)# neighbor FE80::1234:BFF:FE0E:A471% route-map nh6 out |
Applies a route map to incoming or outgoing routes. |
|
Example: Device(config-router-af)# exit |
Exits address family configuration mode, and returns the device to router configuration mode. |
|
Example: Device(config-router)# exit |
Exits router configuration mode, and returns the device to global configuration mode. |
|
Example: Device(config)# route-map nh6 permit 10 |
Defines a route map and enters route-map configuration mode. |
|
Example: Device(config-route-map)# match ipv6 address prefix-list cisco |
Distributes any routes that have a destination IPv6 network number address permitted by a prefix list, or performs policy routing on packets. |
|
Example: Device(config-route-map)# set ipv6 next-hop 2001:DB8::1 |
Overrides the next hop advertised to the peer for IPv6 packets that pass a match clause of a route map for policy routing.
|
Troubleshooting Tips
If peering is not established by this task, it may be because of a missing route map set ipv6 next-hop command. Use the debug bgp ipv6 update command to display debugging information on the updates to help determine the state of the peering.
Configuring an IPv6 Multiprotocol BGP Peer Group
- By default, neighbors that are defined using the neighbor remote-as command in router configuration mode exchange only IPv4 unicast address prefixes. To exchange other address prefix types, such as IPv6 prefixes, neighbors must also be activated using the neighbor activate command in address family configuration mode for the other prefix types, as shown for IPv6 prefixes.
- By default, peer groups that are defined in router configuration mode using the neighbor peer-groupcommand exchange only IPv4 unicast address prefixes. To exchange other address prefix types, such as IPv6 prefixes, you must activate peer groups using the neighbor activate command in address family configuration mode for the other prefix types, as shown for IPv6 prefixes.
- Members of a peer group automatically inherit the address prefix configuration of the peer group.
- IPv4 active neighbors cannot exist in the same peer group as active IPv6 neighbors. Create separate peer groups for IPv4 peers and IPv6 peers.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# router bgp 65000 |
Enters router configuration mode for the specified BGP routing process. |
|
Example: Router(config-router)# neighbor group1 peer-group |
Creates a multiprotocol BGP peer group. |
|
Example: Router(config-router)# neighbor 2001:DB8:0:CC00::1 remote-as 64600 |
Adds the IPv6 address of the neighbor in the specified autonomous system to the IPv6 multiprotocol BGP neighbor table of the local router. |
|
Example: Router(config-router)# address-family ipv6 unicast |
Specifies the IPv6 address family, and enters address family configuration mode. |
|
Example: Router(config-router-af)# neighbor 2001:DB8:0:CC00::1 activate |
Enables the neighbor to exchange prefixes for the specified family type with the neighbor and the local router. |
|
Example: Router(config-router-af)# neighbor 192.168.99.70 send-label |
Advertises the capability of the router to send MPLS labels with BGP routes. |
|
Example: Router(config-router-af)# neighbor 2001:DB8:0:CC00::1 peer-group group1 |
Assigns the IPv6 address of a BGP neighbor to a peer group. |
|
Example: Router(config-router-af)# exit |
Exits address family configuration mode, and returns the router to router configuration mode. |
Advertising Routes into IPv6 Multiprotocol BGP
By default, networks that are defined in router configuration mode using the network command are injected into the IPv4 unicast database. To inject a network into another database, such as the IPv6 BGP database, you must define the network using the network command in address family configuration mode for the other database, as shown for the IPv6 BGP database.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified BGP routing process. |
|
Example: Device(config-router)# address-family ipv6 unicast |
Specifies the IPv6 address family, and enters address family configuration mode. |
|
Example: Device(config-router-af)# network 2001:DB8::/24 |
Advertises (injects) the specified prefix into the IPv6 BGP database. (The routes must first be found in the IPv6 unicast routing table.)
|
|
Example: Device(config-router-af)# exit |
Exits address family configuration mode, and returns the router to router configuration mode. |
Configuring a Route Map for IPv6 Multiprotocol BGP Prefixes
- By default, neighbors that are defined using the neighbor remote-as command in router configuration mode exchange only IPv4 unicast address prefixes. To exchange other address prefix types, such as IPv6 prefixes, neighbors must also be activated using the neighbor activate command in address family configuration mode for the other prefix types, as shown for IPv6 prefixes.
- By default, route maps that are applied in router configuration mode using the neighbor route-map command are applied to only IPv4 unicast address prefixes. Route maps for other address families must be applied in address family configuration mode using the neighbor route-map command, as shown for the IPv6 address family. The route maps are applied either as the inbound or outbound routing policy for neighbors under the specified address family. Configuring separate route maps under each address family type simplifies managing complicated or different policies for each address family.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Device(config-router)# neighbor 2001:DB8:0:cc00::1 remote-as 64600 |
Adds the link-local IPv6 address of the neighbor in the specified remote autonomous system to the IPv6 multiprotocol BGP neighbor table of the local device. |
|
Example: Device(config-router)# address-family ipv6 |
Specifies the IPv6 address family, and enters address family configuration mode. |
|
Example: Device(config-router-af)# neighbor 2001:DB8:0:cc00::1 activate |
Enables the neighbor to exchange prefixes for the IPv6 address family with the local device using the specified link-local addresses. |
|
Example: Device(config-router-af)# neighbor 2001:DB8:0:cc00::1 route-map rtp in |
Applies a route map to incoming or outgoing routes. |
|
Example: Device(config-router-af)# exit |
Exits address family configuration mode, and returns the device to router configuration mode. |
|
Example: Device(config-router)# exit |
Exits router configuration mode, and returns the device to global configuration mode. |
|
Example: Device(config)# route-map rtp permit 10 |
Defines a route map and enters route-map configuration mode. |
|
Example: Device(config-route-map)# match ipv6 address prefix-list cisco |
Distributes any routes that have a destination IPv6 network number address permitted by a prefix list, or performs policy routing on packets. |
Redistributing Prefixes into IPv6 Multiprotocol BGP
Redistribution is the process of redistributing, or injecting, prefixes from one routing protocol into another routing protocol. This task explains how to inject prefixes from a routing protocol into IPv6 multiprotocol BGP. Specifically, prefixes that are redistributed into IPv6 multiprotocol BGP using the redistribute router configuration command are injected into the IPv6 unicast database.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified BGP routing process. |
|
Example: Device(config-router)# address-family ipv6 |
Specifies the IPv6 address family, and enters address family configuration mode. |
|
Example: Device(config-router-af)# redistribute bgp 64500 metric 5 metric-type external |
Redistributes IPv6 routes from one routing domain into another routing domain. |
|
Example: Device(config-router-af)# exit |
Exits address family configuration mode, and returns the router to router configuration mode. |
Advertising IPv4 Routes Between IPv6 BGP Peers
If an IPv6 network is connecting two separate IPv4 networks, it is possible to use IPv6 to advertise the IPv4 routes. Configure the peering using the IPv6 addresses within the IPv4 address family. Set the next hop with a static route or with an inbound route map because the advertised next hop will usually be unreachable. Advertising IPv6 routes between two IPv4 peers is also possible using the same model.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Device(config-router)# neighbor 6peers peer-group |
Creates a multiprotocol BGP peer group. |
|
Example: Device(config-router)# neighbor 6peers remote-as 65002 |
Adds the IPv6 address of the neighbor in the specified autonomous system to the IPv6 multiprotocol BGP neighbor table of the local router. |
|
Example: Device(config-router)# address-family ipv4 |
Enters address family configuration mode to configure a routing session using standard IPv4 address prefixes. |
|
Example: Device(config-router-af)# neighbor 2001:DB8:1234::2 peer-group 6peers |
Assigns the IPv6 address of a BGP neighbor to a peer group. |
|
Example: Device(config-router-af)# neighbor 6peers route-map rmap out |
Applies a route map to incoming or outgoing routes. |
|
Example: Device(config-router-af)# exit |
Exits address family configuration mode, and returns the device to router configuration mode. |
|
Example: Device(config-router)# exit |
Exits router configuration mode, and returns the device to global configuration mode. |
|
Example: Device(config)# route-map rmap permit 10 |
Defines a route map and enters route-map configuration mode. |
|
Example: Device(config-route-map)# set ip next-hop 10.21.8.10 |
Overrides the next hop advertised to the peer for IPv4 packets. |
Assigning BGP Administrative Distance for Multicast BGP Routes
Perform this task to specify an administrative distance for multicast BGP routes to be used in RPF lookups for comparison with unicast routes.
Caution |
Changing the administrative distance of BGP internal routes is not recommended. One problem that can occur is the accumulation of routing table inconsistencies, which can break routing. |
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Router(config-router)# address-family ipv6 |
Specifies the IPv6 address family, and enters address family configuration mode. |
|
Example: Router(config-router-af)# distance bgp 10 50 100 |
Configures the administrative distance for BGP routes. |
Generating IPv6 Multicast BGP Updates
Perform this task to generate IPv6 multicast BGP updates that correspond to unicast IPv6 updates received from a peer.
The MBGP translate-update feature generally is used in an MBGP-capable router that peers with a customer site that has only a BGP-capable router; the customer site has not or cannot upgrade its router to an MBGP-capable image. Because the customer site cannot originate MBGP advertisements, the router with which it peers will translate the BGP prefixes into MBGP prefixes, which are used for multicast-source Reverse Path Forwarding (RPF) lookup.
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Router(config-router)# address-family ipv6 |
Specifies the IPv6 address family, and enters address family configuration mode.
|
|
Example: Router(config-router-af)# neighbor 7000::2 translate-update ipv6 multicast |
Generates multiprotocol IPv6 BGP updates that correspond to unicast IPv6 updates received from a peer. |
Configuring the IPv6 BGP Graceful Restart Capability
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# configure terminal |
Enters global configuration mode. |
|
Example: Device(config)# router bgp 65000 |
Enters router configuration mode for the specified routing process. |
|
Example: Device(config-router)# address-family ipv6 |
Specifies the IPv6 address family. |
|
Example: Device(config-router-af)# bgp graceful-restart |
Enables the BGP graceful restart capability. |
Resetting IPv6 BGP Sessions
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# clear bgp ipv6 unicast peer-group marketing soft out |
Resets IPv6 BGP sessions. |
Clearing External BGP Peers
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# clear bgp ipv6 unicast external soft in |
Clears external IPv6 BGP peers. |
|
Example: Device# clear bgp ipv6 unicast peer-group marketing |
Clears all members of an IPv6 BGP peer group. |
Clearing IPv6 BGP Route Dampening Information
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# clear bgp ipv6 unicast dampening 2001:DB8::/64 |
Clears IPv6 BGP route dampening information and unsuppresses the suppressed routes. |
Clearing IPv6 BGP Flap Statistics
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Device> enable |
Enables privileged EXEC mode. |
|
Example: Device# clear bgp ipv6 unicast flap-statistics filter-list 3 |
Clears IPv6 BGP flap statistics. |
Verifying IPv6 Multiprotocol BGP Configuration and Operation
DETAILED STEPS
Command or Action | Purpose | |
---|---|---|
|
Example: Router> show bgp ipv6 unicast |
(Optional) Displays entries in the IPv6 BGP routing table. |
|
Example: Router> show bgp ipv6 unicast summary |
(Optional) Displays the status of all IPv6 BGP connections. |
|
Example: Router> show bgp ipv6 unicast dampening dampened-paths |
(Optional) Displays IPv6 BGP dampened routes. |
|
Example: Router> enable |
Enables higher privilege levels, such as privileged EXEC mode. |
|
Example: Router# debug bgp ipv6 unicast dampening |
(Optional) Displays debugging messages for IPv6 BGP dampening packets. |
|
Example: Router# debug bgp ipv6 unicast updates |
(Optional) Displays debugging messages for IPv6 BGP update packets. |
Configuration Examples for Multiprotocol BGP for IPv6
- Example: Configuring a BGP Process, BGP Router ID, and IPv6 Multiprotocol BGP Peer
- Example: Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
- Example: Configuring an IPv6 Multiprotocol BGP Peer Group
- Example: Advertising Routes into IPv6 Multiprotocol BGP
- Example: Configuring a Route Map for IPv6 Multiprotocol BGP Prefixes
- Example: Redistributing Prefixes into IPv6 Multiprotocol BGP
- Example: Advertising IPv4 Routes Between IPv6 Peers
Example: Configuring a BGP Process, BGP Router ID, and IPv6 Multiprotocol BGP Peer
The following example enables IPv6 globally, configures a BGP process, and establishes a BGP router ID. Also, the IPv6 multiprotocol BGP peer 2001:DB8:0:CC00:: is configured and activated.
ipv6 unicast-routing ! router bgp 65000 no bgp default ipv4-unicast bgp router-id 192.168.99.70 neighbor 2001:DB8:0:CC00::1 remote-as 64600 address-family ipv6 unicast neighbor 2001:DB8:0:CC00::1 activate
Example: Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
The 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
Note |
If you specify only the global IPv6 next-hop address (the ipv6-address argument) with the set ipv6 next-hop command after specifying the neighbor interface (the interface-type argument) with the neighbor update-source command, the link-local address of the interface specified with the interface-type argument is included as the next hop in the BGP updates. Therefore, only one route map that sets the global IPv6 next-hop address in BGP updates is required for multiple BGP peers that use link-local addresses. |
Example: Configuring an IPv6 Multiprotocol BGP Peer Group
The following example configures the IPv6 multiprotocol BGP peer group named group1:
router bgp 65000 no bgp default ipv4-unicast neighbor group1 peer-group neighbor 2001:DB8:0:CC00::1 remote-as 64600 address-family ipv6 unicast neighbor group1 activate neighbor 2001:DB8:0:CC00::1 peer-group group1
Example: Advertising Routes into IPv6 Multiprotocol BGP
The following example injects the IPv6 network 2001:DB8::/24 into the IPv6 unicast database of the local router. (BGP checks that a route for the network exists in the IPv6 unicast database of the local router before advertising the network.)
router bgp 65000 no bgp default ipv4-unicast address-family ipv6 unicast network 2001:DB8::/24
Example: Configuring a Route Map for IPv6 Multiprotocol BGP Prefixes
The following example configures the route map named rtp to permit IPv6 unicast routes from network 2001:DB8::/24 if they match the prefix list named cisco:
router bgp 64900 no bgp default ipv4-unicast neighbor 2001:DB8:0:CC00::1 remote-as 64700 address-family ipv6 unicast neighbor 2001:DB8:0:CC00::1 activate neighbor 2001:DB8:0:CC00::1 route-map rtp in ipv6 prefix-list cisco seq 10 permit 2001:DB8::/24 route-map rtp permit 10 match ipv6 address prefix-list cisco
Example: Redistributing Prefixes into IPv6 Multiprotocol BGP
The following example redistributes RIP routes into the IPv6 unicast database of the local router:
router bgp 64900 no bgp default ipv4-unicast address-family ipv6 unicast redistribute rip
Example: Advertising IPv4 Routes Between IPv6 Peers
The following example advertises IPv4 routes between IPv6 peers when the IPv6 network is connecting two separate IPv4 networks. Peering is configured using IPv6 addresses in the IPv4 address family configuration mode. The inbound route map named rmap sets the next hop because the advertised next hop is likely to be unreachable.
router bgp 65000 ! neighbor 6peers peer-group neighbor 2001:DB8:1234::2 remote-as 65002 address-family ipv4 neighbor 6peers activate neighbor 6peers soft-reconfiguration inbound neighbor 2001:DB8:1234::2 peer-group 6peers neighbor 2001:DB8:1234::2 route-map rmap in ! route-map rmap permit 10 set ip next-hop 10.21.8.10
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
IPv4 BGP configuration tasks |
Cisco IOS IP Routing Protocols Configuration Guide |
Multiprotocol BGP configuration tasks |
Cisco IOS IP Routing Protocols Configuration Guide |
BGP and multiprotocol BGP commands: complete command syntax, command mode, defaults, usage guidelines, and examples |
"BGP Commands," Cisco IOS IP Routing Protocols Command Reference |
Cisco nonstop forwarding |
"Cisco Nonstop Forwarding," Cisco IOS High Availability Configuration Guide |
IPv6 supported feature list |
"Start Here: Cisco IOS Software Release Specifics for IPv6 Features," Cisco IOS IPv6 Configuration Guide |
IPv6 commands: complete command syntax, command mode, defaults, usage guidelines, and examples |
Cisco IOS IPv6 Command Reference |
Standards
Standards |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
MIBs |
MIBs Link |
---|---|
None |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
RFCs |
Title |
---|---|
RFC 2545 |
Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing |
RFC 2858 |
Multiprotocol Extensions for BGP-4 |
RFC 4007 |
IPv6 Scoped Address Architecture |
RFC 4364 |
BGP MPLS/IP Virtual Private Networks (VPNs) |
RFC 4382 |
MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base |
RFC 4659 |
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN |
RFC 4724 |
Graceful Restart Mechanism for BGP |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
http://www.cisco.com/cisco/web/support/index.html |
Feature Information for Implementing Multiprotocol BGPfor IPv6
The 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.
Table 1 | Feature Information for Implementing Multiprotocol BGP for IPv6 |
Feature Name |
Releases |
Feature Information |
---|---|---|
6PE Multipath |
12.2(25)S 12.2(28)SB 12.2(33)SRA 12.2(33)SXI1 12.4(6)T |
The 6PE multipath feature uses multiprotocol internal BGP (MP-iBGP) to distribute IPv6 routes over the MPLS IPv4 core network and to attach an MPLS label to each route. |
Advertising Routes into IPv6 Multiprotocol BGP |
12.0(22)S 12.2(14)S 12.2(28)SB 12.2(2)T 12.3 12.3(2)T 12.4 12.4(2)T |
Users advertise (inject) a prefix into IPv6 multiprotocol BGP. |
Configuring Route Maps for IPv6 Multiprotocol BGP Prefixes |
12.0(22)S 12.2(14)S 12.2(28)SB 12.2(2)T 12.3 12.3(2)T 12.4 12.4(2)T |
Users can configure route maps for IPv6 multiprotocol BGP prefixes. |
IPv6--NSF and Graceful Restart for MP-BGP IPv6 Address Family |
12.2(33)SRE 12.2(33)XNE 15.0(1)SY |
The graceful restart capability is supported for IPv6 BGP unicast, multicast, and VPNv6 address families, enabling Cisco nonstop forwarding (NSF) functionality for BGP IPv6. The BGP graceful restart capability allows the BGP routing table to be recovered from peers without keeping the TCP state. |
IPv6 Multicast Address Family Support for Multiprotocol BGP |
12.0(26)S 12.2(25)S 12.2(28)SB 12.2(25)SG 12.2(33)SRA 12.2(33)SXH 12.3(4)T 12.4 12.4(2)T |
The multiprotocol BGP for the IPv6 multicast address family feature provides multicast BGP extensions for IPv6 and supports the same features and functionality as IPv4 BGP. |
IPv6 Routing--Multiprotocol BGP Extensions for IPv6 |
12.0(22)S 12.2(14)S 12.2(28)SB 12.2(25)SG 12.2(33)SRA 12.2(17a)SX1 12.2(2)T 12.3 12.3(2)T 12.4 12.4(2)T 15.0(1)S |
Multiprotocol BGP extensions for IPv6 supports the same features and functionality as IPv4 BGP. |
IPv6 Routing--Multiprotocol BGP Link-Local Address Peering |
12.0(22)S 12.2(14)S 12.2(28)SB 12.2(25)SG 12.2(33)SRA 12.2(17a)SX112.2(4)T 12.3 12.3(2)T 12.4 12.4(2)T 15.0(1)S |
IPv6 supports multiprotocol BGP link-local address peering. |
Redistributing Prefixes into IPv6 Multiprotocol BGP |
12.0(22)S 12.2(14)S 12.2(28)SB 12.2(2)T 12.3 12.3(2)T 12.4 12.4(2)T |
Users can redistribute (inject) prefixes from another routing protocol into IPv6 multiprotocol BGP. |
VRF Lite Support for IPv6 |
12.2(58)SE |
This feature is supported. |
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.