NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-23 04:22:01 -06:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

Updated Data Model Limitations (markdown)

Jeremy Stretch 2022-04-27 15:49:19 -04:00
parent c49b0ab309
commit 1f7b6961b9
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Data-Model-Limitations.md

@ -64,13 +64,3 @@ This concept is difficult to model because it requires a layer of abstraction to
### Suggested Approach ### Suggested Approach
The recommended approach is to create all of the parent and child devices as physical devices, and then create a virtual chassis to group them in NetBox as a single logical entity. You'll probably still want to create the physical connections between parents and children to ensure the cables are modeled appropriately, although currently there's no mechanism for designating these as intra-chassis links. The recommended approach is to create all of the parent and child devices as physical devices, and then create a virtual chassis to group them in NetBox as a single logical entity. You'll probably still want to create the physical connections between parents and children to ensure the cables are modeled appropriately, although currently there's no mechanism for designating these as intra-chassis links.
# Logical Modeling
## NHRP IP Addressing
A common solution when multiple default gateways serve a common prefix is to advertise a virtual IP address using a next-hop resolution such as VRRP, HSRP, or GLBP. This IP is "shared" by two or more devices. Because NetBox requires each IP address be assigned to a specific interface, there's not currently a precise way to model this concept.
### Suggested Approach
On each interface which participates in the NHRP group, assign both its own normal, unique IP address as well as a copy of the shared IP address, with the later having its role designated as the appropriate NHRP protocol. (Use "VIP" when no dynamic protocol is in use.) See feature request [#2456](https://github.com/netbox-community/netbox/issues/2456) for further discussion on potential solutions.