SDA Border Edge

[dm2020]

Hi All,

Is it supported for a fabric edge to also operate as a fabric internal border? We have a router that needs to connect to our network and based on its location the easiest place to connect it will be fabric edge. The router has a couple of networks behind it that need to be accessible to the fabric. I dont think that this is possible unless the edge is also a border and we can add and redistribute routes into the fabric control plane

[jalejand]

Depending on the DNAC version and the Edge model, you could make it a Border+Edge:

[dm2020]

What version of DNAC is required for this?

For the handoff to the external device that is connected to the border edge, what routing protocols are supported? Do we have to use BGP with the external device or can we use OSPF/static routes?

[jalejand]

Starting from 1.3.1.0:

https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/1-3-1/release_notes/b_cisco_dna_center_rn_1_3_1.html

Cisco Catalyst 9000 Switches (C9300, C9400, and C9500 series) have the capability to host border node, edge node, and embedded wireless functionalities on a single switch (single or stacked), with a non-colocated control plane node.

For the handoff protocol, it must be BGP, Internal Borders can only import BGP route into LISP DB via the "route-import database bgp.." command under "service ipv4" on the targeted VRF, changing this behavior is not supported.

[Jonathan Cuthbert]

Is there a specific reason you want to use LISP routing logic (internal border node) to reach these destinations rather than using default forwarding logic?  Can you describe your topology? What you say "the easiest place connect it will be the fabric edge" can you expand on this?  Where is this router connected today?