home

Supported platforms

Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers
Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Show On this page:

thumbnailSupported platforms

Configuring BGP

Originating a route to eBGP neighbors

One of the main requirements for BGP configurations is to originate network prefixes to BGP peers. On the Vyatta router this is accomplished using the network option within the BGP configuration.

In this section, you originate the network prefix from both the R1 and R4 routers. This is shown in the following figure.

Note: We assume that the routers in AS200 and AS300 are configured appropriately as eBGP peers and have routes to advertise as well.
Note: The example in this section assumes that the desired network to originate to our BGP peers is 172.16.0.0/24, which is a private RFC 1918 network address. Typically, the router would be originating a public IP network assigned by an Internet routing registry such as the American Registry for Internet Numbers (ARIN).
Figure 1. Originating a route to eBGP neighbors

This example assumes that the configurations in previous sections have been performed. For more information about configuring an eBGP connection, refer to Basic eBGP configuration and for more information about configuring an iBGP connection, refer to Basic iBGP configuration.

To originate a route to eBGP neighbors, perform the following steps in configuration mode.

Table 1. Originating routes to eBGP neighbors

Router

Step

Commands

R1

Advertise the local network to BGP. 

vyatta@R1# set protocols bgp 100 address-family ipv4-unicast network 172.16.0.0/24

R1

Commit the configuration. 

vyatta@R1# commit

R1

Verify the configuration. 

vyatta@R1# show protocols bgp 
 bgp 100 {
     neighbor 172.16.0.2 {
         address-family {
             ipv4-unicast {
             }
         }
         remote-as 100
         update-source 172.16.0.1
     }
     neighbor 172.16.0.3 {
         address-family {
             ipv4-unicast {
             }
         }
         remote-as 100
         update-source 172.16.0.1
     }
     neighbor 172.16.0.4 {
         address-family {
             ipv4-unicast {
             }
         }
         remote-as 100
         update-source 172.16.0.1
     }
 }

V1: AS-200

Advertise the remote -as AS-200 to BGP. 

vyatta@V1# set protocols bgp 200 neighbor 88.88.88.1 remote-as 100
 vyatta@V1# set protocols bgp 200 neighbor 88.88.88.1 address-family ipv4-unicast

V1

Commit the configuration 

vyatta@V1# commit

V1

Verify the RA configuration. 

vyatta@V1# show protocols bgp
 bgp 200 {
     address-family {
         ipv4-unicast {
             network 12.0.0.0/8 {
             }
         }
     }
     neighbor 88.88.88.1 {
         address-family {
             ipv4-unicast {
             }
         }
         ebgp-multihop 1
     }
 }
[edit]

V2: AS-300

Advertise remote-as AS-300 to BGP. 

vyatta@V2# set protocols bgp 300 neighbor 99.99.99.1 remote-as 100 
vyatta@V2# set protocols bgp 300 neighbor 99.99.99.1 address-family ipv4-unicast

V2

Commit the configuration 

vyatta@V2## commit

V2

Verify the configuration 

vyatta@V2# show protocols bgp
 bgp 300 {
     address-family {
         ipv4-unicast {
         }
     }
     neighbor 99.99.99.1 {
         address-family {
             ipv4-unicast {
             }
         }
         remote-as 100
     }
 }

Last updated: February 18, 2022