From 1f7b6961b9e9093ebad8bcf611c073d978733ec1 Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Wed, 27 Apr 2022 15:49:19 -0400 Subject: [PATCH] Updated Data Model Limitations (markdown) --- Data-Model-Limitations.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/Data-Model-Limitations.md b/Data-Model-Limitations.md index d0bfc21..9d453c8 100644 --- a/Data-Model-Limitations.md +++ b/Data-Model-Limitations.md @@ -64,13 +64,3 @@ This concept is difficult to model because it requires a layer of abstraction to ### 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. - -# 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.