NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-20 02:06:42 -06:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

Updated Data Model Limitations (markdown)

Jeremy Stretch 2020-12-30 10:58:34 -05:00
parent 266e585fae
commit 4371640d5c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
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.