Feedback
|
Table Of Contents
Information About BGP Next Hop Unchanged
How to Configure BGP Next Hop Unchanged
Configuring the BGP Next Hop Unchanged for an eBGP Peer
Configuration Example for BGP Next Hop Unchanged
Example: BGP Next Hop Unchanged for an eBGP Peer
Feature Information for BGP Next Hop Unchanged
BGP Next Hop Unchanged
Last Updated: May 19, 2011
In an external BGP (eBGP) session, by default, the router changes the next hop attribute of a BGP route (to its own address) when the router sends out a route. The BGP Next Hop Unchanged feature allows BGP to send an update to an eBGP multihop peer with the next hop attribute unchanged.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see 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 for BGP Next Hop Unchanged" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Information About BGP Next Hop Unchanged
•
How to Configure BGP Next Hop Unchanged
•
Configuration Example for BGP Next Hop Unchanged
•
Feature Information for BGP Next Hop Unchanged
Information About BGP Next Hop Unchanged
BGP Next Hop Unchanged
In an external BGP (eBGP) session, by default, the router changes the next hop attribute of a BGP route (to its own address) when the router sends out a route. If the BGP Next Hop Unchanged feature is configured, BGP will send routes to an eBGP multihop peer without modifying the next hop attribute. The next hop attribute is unchanged.
Note
There is an exception to the default behavior of the router changing the next hop attribute of a BGP route when the router sends out a route. When the next hop is in the same subnet as the peering address of the eBGP peer, the next hop is not modified. This is referred to as third party next-hop.
The BGP Next Hop Unchanged feature provides flexibility when designing and migrating networks. It can be used only between eBGP peers configured as multihop. It can be used in a variety of scenarios between two autonomous systems. One scenario is when multiple autonomous systems are connected that share the same IGP, or at least the routers have another way to reach each other's next hops (which is why the next hop can remain unchanged).
A common use of this feature is to configure Multiprotocol Label Switching (MPLS) inter-AS with multihop MP-eBGP for VPNv4 between RRs.
Another common use of this feature is a VPNv4 inter-AS Option C configuration, as defined in RFC4364, Section 10. In this configuration, VPNv4 routes are passed among autonomous systems between RR of different autonomous systems. The RRs are several hops apart, and have neighbor next-hop unchanged configured. PEs of different autonomous systems establish an LSP between them (via a common IGP or by advertising the next-hops—that lead to the PEs—via labeled routes among the ASBRs—routes from different autonomous systems separated by one hop). PEs are able to reach the next hops of the PEs in another AS via the LSPs, and can therefore install the VPNv4 routes in the VRF RIB.
Restriction
The BGP Next Hop Unchanged feature can be configured only between multihop eBGP peers. The following error message will be displayed if you try to configure this feature for a directly connected neighbor:
%BGP: Can propagate the nexthop only to multi-hop EBGP neighborHow to Configure BGP Next Hop Unchanged
•
Configuring the BGP Next Hop Unchanged for an eBGP Peer
Configuring the BGP Next Hop Unchanged for an eBGP Peer
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router bgp as-number
4.
address-family {ipv4 [unicast] | vpnv4 [unicast]}
5.
neighbor ip-address remote-as
6.
neighbor ip-address activate
7.
neighbor ip-address ebgp-multihop ttl
8.
neighbor ip-address next-hop-unchanged
9.
end
10.
show ip bgp
DETAILED STEPS
Configuration Example for BGP Next Hop Unchanged
•
Example: BGP Next Hop Unchanged for an eBGP Peer
Example: BGP Next Hop Unchanged for an eBGP Peer
The following example configures a multihop eBGP peer at 10.0.0.100 in a remote AS. When the local router sends updates to that peer, it will send them without modifying the next hop attribute.
router bgp 65535address-family ipv4neighbor 10.0.0.100 remote-as 65600neighbor 10.0.0.100 activateneighbor 10.0.0.100 ebgp-multihop 255neighbor 10.0.0.100 next-hop-unchangedendAdditional References
Related Documents
Related Topic Document TitleCisco IOS commands
BGP commands
BGP configuration tasks
IP Routing: BGP Configuration Guide, Cisco IOS Release 15.1M&T
MPLS configuration tasks
MPLS Configuration Guide, Cisco IOS Release 15.1M&T
BGP Outbound Route Map on Route Reflector to Set IP Next Hop for iBGP Peer
Technical Assistance
Feature Information for BGP Next Hop Unchanged
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 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.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2005-2011 Cisco Systems, Inc. All rights reserved.
Feedback