From 4371640d5c4a23478c2cb9f8dd75ecb7ffd2ddb5 Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Wed, 30 Dec 2020 10:58:34 -0500 Subject: [PATCH] Updated Data Model Limitations (markdown) --- Data-Model-Limitations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Data-Model-Limitations.md b/Data-Model-Limitations.md index 84fb28e..d0bfc21 100644 --- a/Data-Model-Limitations.md +++ b/Data-Model-Limitations.md @@ -38,9 +38,9 @@ The recommended approach for modeling breakout cables is to create a separate ca ``` Device A [xe-0/0/0:0] ---(Cable 1)--- [eth0] Device B -Device A [xe-0/0/0:1] ---(Cable 1)--- [eth0] Device C -Device A [xe-0/0/0:2] ---(Cable 1)--- [eth0] Device D -Device A [xe-0/0/0:3] ---(Cable 1)--- [eth0] Device E +Device A [xe-0/0/0:1] ---(Cable 2)--- [eth0] Device C +Device A [xe-0/0/0:2] ---(Cable 3)--- [eth0] Device D +Device A [xe-0/0/0:3] ---(Cable 4)--- [eth0] Device E ``` ## Combo Ports @@ -73,4 +73,4 @@ A common solution when multiple default gateways serve a common prefix is to adv ### 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 for further discussion on potential solutions. +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.