mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-12 09:52:27 +00:00
doc: add extra information on bgp views and vrfs
Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
This commit is contained in:
parent
c8a5e5e190
commit
edde3ce9c2
@ -235,8 +235,10 @@ However, the same AS can be used with different VRFs.
|
|||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
The separated nature of VRFs makes it possible to peer a single *bgpd*
|
The separated nature of VRFs makes it possible to peer a single *bgpd*
|
||||||
process to itself, on one machine. This can be used for prototyping and
|
process to itself, on one machine. Note that this can be done fully within
|
||||||
other purposes.
|
BGP without a corresponding VRF in the kernel or Zebra, which enables some
|
||||||
|
practical use cases such as :ref:`route reflectors <bgp-route-reflector>`
|
||||||
|
and route servers.
|
||||||
|
|
||||||
Configuration of additional autonomous systems, or of a router that targets a
|
Configuration of additional autonomous systems, or of a router that targets a
|
||||||
specific VRF, is accomplished with the following command:
|
specific VRF, is accomplished with the following command:
|
||||||
@ -305,6 +307,8 @@ selected by BGP are not installed into the kernel routing table. The view
|
|||||||
functionality allows the exchange of BGP routing information without affecting
|
functionality allows the exchange of BGP routing information without affecting
|
||||||
the kernel routing tables.
|
the kernel routing tables.
|
||||||
|
|
||||||
|
Peers configured within a view and their traffic exist within the default VRF.
|
||||||
|
|
||||||
.. index:: router bgp AS-NUMBER view NAME
|
.. index:: router bgp AS-NUMBER view NAME
|
||||||
.. clicmd:: router bgp AS-NUMBER view NAME
|
.. clicmd:: router bgp AS-NUMBER view NAME
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user