Changes

no edit summary
Line 369: Line 369:  
====BGP Instance====
 
====BGP Instance====
 
----
 
----
 +
The <b>BGP Instance</b> section is used to configure some of the main operating parameters of the BGP protocol. Below is an example of the BGP Instance section.
   −
To create a new BGP instance, look to the Add New Instance section under BGP instances; type in a custom name for the BGP instance and click the 'Add' button or you can `Edit` a general instance:
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v1.png|border|class=tlt-border]]
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_edit.png|border|class=tlt-border]]
  −
 
  −
Below is an example of the BGP Instance section:
  −
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v2.png|border|class=tlt-border]]
      
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 391: Line 386:  
     <tr>
 
     <tr>
 
       <td>AS</td>
 
       <td>AS</td>
       <td>integer [1..4294967295]; default: <b>none</b></td>
+
       <td>integer [1..65535]default: <b>none</b></td>
         <td>AS number is an identification of an autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is an internal one or external one.</td>
+
         <td>BGP Autonomous System (AS) number. It is an identifier that represents a routing domain; BGP routers can exchange routes within the same Autonomous System.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 403: Line 398:  
         <td>ip/netmask; default: <b>none</b></td>
 
         <td>ip/netmask; default: <b>none</b></td>
 
         <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
 
         <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
    </tr>
  −
    <tr>
  −
    <td>VRF interface</td>
  −
        <td>VRF interface; default: <b>Default</b></td>
  −
        <td>To create new VRF interface, please visit: [[{{{name}}} VRF|VRF]] </td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 430: Line 420:  
<b>BGP Peers</b> are routers in the same BGP Peer Group that can redistribute routes among other BGP Peers. Below is an example of the BGP Peers section, which is empty by default.
 
<b>BGP Peers</b> are routers in the same BGP Peer Group that can redistribute routes among other BGP Peers. Below is an example of the BGP Peers section, which is empty by default.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers.png|border|class=tlt-border]]
    
To create a new Peer, look to the Add New Instance section under BGP Peer; type in a custom name for the BGP Peer and click the 'Add' button:
 
To create a new Peer, look to the Add New Instance section under BGP Peer; type in a custom name for the BGP Peer and click the 'Add' button:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]]
   −
You will be redirected to general peer settings:
+
The newly added BGP Peer configuration should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v4.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_added.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Remote AS</td>
 +
      <td>integer [1..65535]; default: <b>none</b></td>
 +
      <td>Remote autonomous system number of this remote BGP Neighbor.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Remote address</td>
 +
        <td>ip4; default: <b>none</b></td>
 +
        <td>IPv4 address of this remote BGP Neighbor.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>Turns turns this BGP peer on or off.</td>
 +
    </tr>
 +
</table>
 +
 
 +
To see more settings for a BGP Peer, click the 'Edit' button next to it:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_edit_button.png|border|class=tlt-border]]
 +
 
 +
The full BGP Peer configuration page should look similar to this:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v3.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 453: Line 474:  
     <tr>
 
     <tr>
 
       <td>Remote AS</td>
 
       <td>Remote AS</td>
       <td>integer [1..4294967295]; default: <b>none</b></td>
+
       <td>integer [1..65535]; default: <b>none</b></td>
 
       <td>Remote autonomous system number of this remote BGP Neighbor.</td>
 
       <td>Remote autonomous system number of this remote BGP Neighbor.</td>
 
     </tr>
 
     </tr>
Line 459: Line 480:  
     <td>Remote address</td>
 
     <td>Remote address</td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
         <td>IPv4 address of this remote BGP Neighbor. This option is required.</td>
+
         <td>IPv4 address of this remote BGP Neighbor.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 512: Line 533:  
A <b>BGP Peer Group</b> is a collection of routers that use the BGP protocol to dynamically redistribute routes among peers (other routers). The figure below is an example of the BGP Peer Groups section, which is empty by default.
 
A <b>BGP Peer Group</b> is a collection of routers that use the BGP protocol to dynamically redistribute routes among peers (other routers). The figure below is an example of the BGP Peer Groups section, which is empty by default.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups.png|border|class=tlt-border]]
    
To create a new Peer Group, look to the Add New Instance section under BGP Peer Groups; type in a custom name for the BGP Peer Group and click the 'Add' button:
 
To create a new Peer Group, look to the Add New Instance section under BGP Peer Groups; type in a custom name for the BGP Peer Group and click the 'Add' button:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_groups_add_button_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]]
   −
You will be redirected to general peer groups settings:
+
The newly added BGP Peer Group configuration should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_added.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Remote AS</td>
 +
      <td>integer [1..65535]; default: <b>none</b></td>
 +
      <td>Remote autonomous system number.</td>
 +
    </tr>
 +
</table>
 +
 
 +
To see more settings for a BGP Peer Group, click the 'Edit' button next to it:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_edit_button.png|border|class=tlt-border]]
 +
 
 +
The full BGP Peer Group configuration page should look similar to this:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 536: Line 578:  
       <td>Remote AS</td>
 
       <td>Remote AS</td>
 
       <td>integer [1..65535]; default: <b>none</b></td>
 
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Neighbour's remote AS.</td>
+
       <td>Remote autonomous system number.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Neighbor address</td>
 
     <td>Neighbor address</td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
         <td>Neighbour's remote IPv4 address.</td>
+
         <td>IPv4 address(es) of a remote BGP Neighbor.</td>
 
     </tr>
 
     </tr>
 
         <tr>
 
         <tr>
Line 551: Line 593:  
         <td>Advertisement interval</td>
 
         <td>Advertisement interval</td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>integer; default: <b>none</b></td>
         <td>Delay between updates for a neighbor session (in seconds).</td>
+
         <td>BGP advertisement frequency (in seconds).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 589: Line 631:  
The <b>Access List Filters</b> section is used to configure special filters that restrict or allow access to specified networks for BGP Peers. Below is an example of the Access List Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
 
The <b>Access List Filters</b> section is used to configure special filters that restrict or allow access to specified networks for BGP Peers. Below is an example of the Access List Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button.png|border|class=tlt-border]]
    
An Access List Filter configuration for BGP should look similar to this:
 
An Access List Filter configuration for BGP should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 603: Line 645:  
     <tr>
 
     <tr>
 
       <td>Peer</td>
 
       <td>Peer</td>
       <td>bgp peer; default: <b>-</b></td>
+
       <td>bgp peer; default: <b>none</b></td>
 
       <td>Applies the filter rule for the specified peer.</td>
 
       <td>Applies the filter rule for the specified peer.</td>
 
     </tr>
 
     </tr>
Line 612: Line 654:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
     <td>Filter network</td>
+
     <td>Network</td>
         <td>Any {{!}} custom; default: <b>Any</b></td>
+
         <td>ip/netmask {{!}} Any; default: <b>Any</b></td>
         <td>Applies filter rule for this source network.</td>
+
         <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Direction</td>
 
     <td>Direction</td>
 
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
 
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
         <td>If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes.</td>
+
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 632: Line 674:  
A <b>Route Maps</b>  allow you to configure a filtering criteria by defining a set of rules or match statements with a permit or deny condition. It includes a series of match statements to determine if a route matches the criteria defined in the statement and then apply the permit or deny rule accordingly.
 
A <b>Route Maps</b>  allow you to configure a filtering criteria by defining a set of rules or match statements with a permit or deny condition. It includes a series of match statements to determine if a route matches the criteria defined in the statement and then apply the permit or deny rule accordingly.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps.png|border|class=tlt-border]]
    
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
 
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button.png|border|class=tlt-border]]
 +
 
 +
The newly added Route Map configuration should look similar to this:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_added.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Drag-cursor</td>
 +
      <td>- (interactive button)</td>
 +
      <td>Changes the priority(metric) of the route maps.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Action</td>
 +
        <td>Permit {{!}} Deny; default: <b>Permit</b></td>
 +
        <td>IPv4 address of this remote BGP Neighbor.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>Turns this Route Map on or off.</td>
 +
    </tr>
 +
</table>
 +
 
 +
To see more settings for a Route Maps, click the 'Edit' button next to it:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_button.png|border|class=tlt-border]]
   −
You will be redirected to general route maps settings:
+
The full Route Maps configuration page should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 674: Line 747:  
The <b>Route Map Filters</b> section is used to configure special filters that changes direction for BGP Peers. Below is an example of the Route Map Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
 
The <b>Route Map Filters</b> section is used to configure special filters that changes direction for BGP Peers. Below is an example of the Route Map Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_add_button_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_add_button.png|border|class=tlt-border]]
    
An Route Map Filters configuration for BGP should look similar to this:
 
An Route Map Filters configuration for BGP should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 688: Line 761:  
     <tr>
 
     <tr>
 
       <td>Peer</td>
 
       <td>Peer</td>
       <td>bgp peer; default: <b>-</b></td>
+
       <td>bgp peer; default: <b>none</b></td>
 
       <td>Applies the filter rule for the specified peer.</td>
 
       <td>Applies the filter rule for the specified peer.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Route map</td>
 
       <td>Route map</td>
       <td>route map; default: <b>-</b></td>
+
       <td>route map; default: <b>none</b></td>
 
       <td>Route map filter to apply.</td>
 
       <td>Route map filter to apply.</td>
 
     </tr>
 
     </tr>