| Neale Ranns | c9e4b30 | 2020-01-03 00:16:12 +0000 | [diff] [blame^] | 1 | --- |
| 2 | name: Adjacency |
| 3 | maintainer: Neale Ranns <nranns@cisco.com> |
| 4 | features: |
| 5 | - An adjacency represents how to send different traffic types to a peer |
| 6 | - The principles properties of an adjacency are the interface and rewrite. |
| 7 | The rewrite will be prepended to the packet as it is forward through the |
| 8 | interface. |
| 9 | - The rewrite is provided either by the interface type. It can be constructed |
| 10 | either from fixed interface properties (i.e. src,dst IP address on a P2P |
| 11 | tunnel) or from a resolution protocol (like ARP on an Ethernet link). |
| 12 | - An Adjacency is said to be complete when the rewrite is present and |
| 13 | incomplete when it is not, |
| 14 | - An adjacency that is a leaf in the DPO graph is terminal/normal (i.e on |
| 15 | a physical interface). When not terminal it is termed a midchain (i.e. |
| 16 | one on a virtual interface, e.g. GRE tunnel). Midchain adjacencies can be |
| 17 | stacked/joined onto the the DPO graph that described subsequent forwarding |
| 18 | (i.e. how to send the the GRE tunnel's destination address). |
| 19 | - Glean adjacencies describe how to broadcast packets onto a subnet |
| 20 | |
| 21 | |
| 22 | description: "Adjacency" |
| 23 | state: production |
| 24 | properties: [API, CLI, MULTITHREAD] |