| jdenisco | 0923a23 | 2018-08-29 13:19:43 -0400 | [diff] [blame] | 1 | .. _controlplane: |
| 2 | |
| 3 | The Control Plane |
| 4 | ----------------- |
| 5 | |
| 6 | The control plane follows a layered data representation. This document describes the |
| 7 | model starting from the lowest layer. The description uses IPv4 addresses and |
| 8 | protocols, but all concepts apply equally to the IPv6 equivalents. The diagrams |
| 9 | all portray the CLI command to install the information in VPP and an |
| 10 | [approximation of] a UML diagram [#f1]_ of the data structures used to represent that |
| 11 | information. |
| 12 | |
| 13 | .. toctree:: |
| 14 | |
| 15 | arpentries |
| 16 | routes |
| 17 | attachedexport |
| 18 | graphwalks |
| 19 | |
| 20 | .. rubric:: Footnotes: |
| 21 | |
| 22 | .. [#f1] The arrow indicates a ‘has-a’ relationship. The object attached to the arrow head ‘has-a’ instance of the other. The numbers next to the arrows indicate the multiplicity, i.e. object A has n to m instances of object B. The difference between a UML association and aggregation is not conveyed in any diagrams. To UML aficionados, I apologize. Word is not the best drawing tool. |