# Network Device topology

**URL:** <https://community.dynatrace.com/t/network-device-topology/39628>\
**Category:** Open Q&A\
**Tags:** network-monitoring\
**Created:** [May 8, 2023, 10:11am UTC](https://community.dynatrace.com/t/network-device-topology/39628 "2023-05-08T10:11:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![y\_buccellato](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/y_buccellato/32/160_2.png) [@y\_buccellato](https://community.dynatrace.com/u/y_buccellato)\
**Post date:** [May 8, 2023, 10:11am UTC](https://community.dynatrace.com/t/network-device-topology/39628/1 "2023-05-08T10:11:12Z")

</div>

Does Dynatrace maps devices discovered via SNMP extensions on the smartscape topology or service flow?  
Is any relation created between a network device and other entities?

Regards

---

<div class="post-metadata">

**Author:** ![AntonPineiro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antonpineiro/32/49_2.png) [@AntonPineiro](https://community.dynatrace.com/u/AntonPineiro)\
**Post date:** [May 8, 2023, 12:06pm UTC](https://community.dynatrace.com/t/network-device-topology/39628/2 "2023-05-08T12:06:17Z")

</div>

Hi,

I have never tried it or explore it but looks like a use case for&nbsp;[Custom topology model](https://www.dynatrace.com/support/help/shortlink/topology-model).

Best regards

---

<div class="post-metadata">

**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\
**Post date:** [May 8, 2023, 2:57pm UTC](https://community.dynatrace.com/t/network-device-topology/39628/3 "2023-05-08T14:57:48Z")

</div>

[@y\_buccellato](https://community.dynatrace.com/user/4804),

Topology is included in the SNMP v2 extensions from Dynatrace. Basically, it associates interfaces with the respective devices.

I have not seen yet relationships between a network device and other entities. It would be great if interfaces could de joined/related when they are part of o point-to-point link, as they are in dedicated network monitoring solutions, but most of the times this is done with proprietary solutions, that only work for devices of a certain vendor.

I did see at Perform that a lot of work is being done at the network level. And I believe incorporating this information into the Dynatrace topology model might be something that me be coming in the future…

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [May 9, 2023, 6:44am UTC](https://community.dynatrace.com/t/network-device-topology/39628/4 "2023-05-09T06:44:24Z")

</div>

[@AntonioSousa](https://community.dynatrace.com/user/17213)&nbsp;relations between entities created using the custom topology model (Extensions 2.0) and built-in entities are not yet present and AFAIK are being worked on. With Custom Devices (Legacy Extenions 1.0) the relations are created based on opaque services and based on IP addresses - a service created on top of the custom device.
