cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3845
Views
1
Helpful
1
Replies

Third Party Device in DNA Topology

EDUARD LAYRITZ
Level 1
Level 1

We are integrating a third party device (AnyRover from AnyWeb). The AnyRover appears in the inventory and in the topology. However, in the topology the link between the AnyRover and the connecting Switch isn't shown. LLDP is turned on on both devices. What are the prerequisites for DNA-C to recognize a connections between two devices and show it in topology?

 

Thanks for your help

1 Reply 1

Mike.Cifelli
VIP Alumni
VIP Alumni

View this link for the SDA Compatibility matrix: https://www.cisco.com/c/en/us/solutions/enterprise-networks/software-defined-access/compatibility-matrix.html

 

LLDP is a layer 2 technology.  In SDA your underlay network is established via the use of a routing protocol (OSPF, ISIS, etc.).  Let's say you have two nodes that are SDA capable, one acting as an edge node (access sw) & one acting as an intermediary node (distro like).  You would need to create a L3 point to point routed link for the device connection to show inside the DNAC fabric.

 

There is a solution, which is to implement an internal border node (IBN) inside your network that would basically sit between your fabric (SDA capable devices) & your legacy non-SDA capable devices.  This IBN would then basically do the translations between legacy and the fabric.  The IBN would be an iBGP peer to your EBNs.  Your legacy switch would then be a different private eBGP AS that peers with the IBN, and you would redistribute whatever networks you want accessible between fabric & non-fabric.  Basically at this point your fabric would have two different eBGP peers (fusion routers & legacy device connected to IBN).  

 

Hope this helps.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: