starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Multi-Site Topology Maps #449

New Issue
Closed
opened 2025-12-29 16:22:18 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:22:18 +01:00
Owner
Copy Link

Originally created by @sp0rus on GitHub (Sep 27, 2016).

Having a way to view a multi-site topology map would be fantastic. We have multiple connections going to different sites for different networks. We are a small ISP, and we have each hub and building around town as a separate site. Being able to see all of our connections between sites would be fantastic.

Originally created by @sp0rus on GitHub (Sep 27, 2016). Having a way to view a multi-site topology map would be fantastic. We have multiple connections going to different sites for different networks. We are a small ISP, and we have each hub and building around town as a separate site. Being able to see all of our connections between sites would be fantastic.
adam added the type: feature label 2025-12-29 16:22:18 +01:00
adam closed this issue 2025-12-29 16:22:18 +01:00
adam commented 2025-12-29 16:22:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 23, 2017):

Site assignment is optional for topology maps. In theory, you could create a topology map which includes devices from multiple sites and it will be rendered. There are two issues that we need to address, however:

  • Topology maps without a site assignment are not currently referenced anywhere. This is easily remedied by linking to them on the NetBox home view.
  • Topology maps do not render circuits (#430). It should be fairly easy to extend the rendering logic to include circuits (which are now modeled very similar to interface connections).
@jeremystretch commented on GitHub (Mar 23, 2017): Site assignment is optional for topology maps. In theory, you could create a topology map which includes devices from multiple sites and it will be rendered. There are two issues that we need to address, however: * Topology maps without a site assignment are not currently referenced anywhere. This is easily remedied by linking to them on the NetBox home view. * Topology maps do not render circuits (#430). It should be fairly easy to extend the rendering logic to include circuits (which are now modeled very similar to interface connections).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#449
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?