05-07-2019 11:00 PM
Hi all-
Could someone please point me to documents/configurations for a typical eBGP external peering scenario. The usecase is a non-vxlan, L3 eBGP leaf spine fabric, peering with an external router over eBGP using border leafs. What are the best practices and key design considerations?
Thanks!
08-09-2019 07:02 AM
I don't know,
But it may be worth researching "peer-type fabric-external"
router bgp 1 neighbor 1.1.1.1 remote-as 2 update-source loopback0 ebgp-multihop 2
peer-type fabric-external
08-09-2019 07:04 AM
To classify a neighbor as external to the Cisco Dynamic Fabric Automation (DFA) fabric and avoid advertising externally learned prefixes to fabric-internal neighbors, use the peer-type command. To return to the default, use the no form of this command.
peer-type { fabric-border-leaf | fabric-external }
no peer-type { fabric-border-leaf | fabric-external }
fabric-border-leaf | Specifies that all border leaf switches on the Cisco DFA fabric are peers to other border-leaf switches. |
fabric-external | Specifies that a neighbor is marked as fabric external |
A neighbor is classified as internal to the fabric.
BGP neighbor configuration (config-router-neighbor)
7.0(0)N1(1) | This command was introduced. |
A Cisco DFA border-leaf switch always advertises all learned prefixes outside the Cisco DFA fabric, even those that are host-routes.
An external route is not advertised to the fabric-internal neighbors unless there an internal route that is less specific than the external route.
Use the peer-type command to classify a Border Gateway Protocol (BGP) neighbor as external to the fabric. The border leaf must specifically classify external neighbors in order to apply the appropriate rules of route exchange between internal and external neighbors and avoid advertising externally learned prefixes to fabric-internal neighbors through internal BGP. For example, when an update from a fabric-internal neighbor goes to an external neighbor, the virtual network identifier (VNI) is stripped and the fabric site of origin (SoO) extended community value in the BGP update message is attached. For routes coming from external neighbors, the fabric SoO is used to check for loops and to perform the appropriate filtering of routes from external neighbors to internal neighbors.
This command applies only to border-leaf switches.
This command is required on the border-leaf switch for external neighbors.
This command is not supported on Cisco Nexus 5500 Series switches configured as DFA Layer 2-only leaf switches.
The following example shows how to configure the neighbor configuration on a border leaf-towards-Data Center Interconnect (DCI) node:
router bgp 1 neighbor 30.1.1.1 remote-as 2 description default vrf neighbor to DCI peer-type fabric-external send-community extended
Related Commands Related Information
Command | Description |
Configures the SoO for a fabric. |
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide