Specifications

Send document comments to nexus3k-docfeedback@cisco.com.
6-2
Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, Release 5.0(3)U2(2)
OL-25782-02
Chapter 6 Configuring Advanced BGP
Information About Advanced BGP
Capabilities Negotiation, page 6-5
Route Dampening, page 6-6
Load Sharing and Multipath, page 6-6
Route Aggregation, page 6-7
BGP Conditional Advertisement, page 6-7
BGP Next-Hop Address Tracking, page 6-7
Route Redistribution, page 6-8
BFD, page 6-8
Tuning BGP, page 6-8
Multiprotocol BGP, page 6-9
Virtualization Support, page 6-9
Peer Templates
BGP peer templates allow you to create blocks of common configuration that you can reuse across
similar BGP peers. Each block allows you to define a set of attributes that a peer then inherits. You can
choose to override some of the inherited attributes as well, making it a very flexible scheme for
simplifying the repetitive nature of BGP configurations.
Cisco NX-OS implements three types of peer templates:
The peer-session template defines BGP peer session attributes, such as the transport details, remote
autonomous system number of the peer, and session timers. A peer-session template can also inherit
attributes from another peer-session template (with locally defined attributes that override the
attributes from an inherited peer-session).
A peer-policy template defines the address-family dependent policy aspects for a peer including the
inbound and outbound policy, filter-lists, and prefix-lists. A peer-policy template can inherit from a
set of peer-policy templates. Cisco NX-OS evaluates these peer-policy templates in the order
specified by the preference value in the inherit configuration. The lowest number is preferred over
higher numbers.
The peer template can inherit the peer-session and peer-policy templates to allow for simplified peer
definitions. It is not mandatory to use a peer template but it can simplify the BGP configuration by
providing reusable blocks of configuration.
Authentication
You can configure authentication for a BGP neighbor session. This authentication method adds an MD5
authentication digest to each TCP segment sent to the neighbor to protect BGP against unauthorized
messages and TCP security attacks.
Note The MD5 password must be identical between BGP peers.