31,703
edits
Changes
Template:Networking rutos manual routing (view source)
Revision as of 10:18, 20 October 2020
, 10:18, 20 October 2020no edit summary
<td>Enable</td>
<td>Enable</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Toggles the BGP protocol on or off</td>
<td>Turns BGP protocol usage on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Enable vty</td>
<td>Enable vty</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Toggles vty access on or off</td>
<td>Turns vty access on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Import config</td>
<td>Import config</td>
<td>-</td>
<td>-</td>
<td>Uploads an external BGP configuration</td>
<td>Uploads an external BGP configuration.</td>
</tr>
</tr>
</table>
</table>
<td>Enable</td>
<td>Enable</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Toggles the BGP instance on or off</td>
<td>Turns the BGP instance on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>AS</td>
<td>AS</td>
<td>default: <b>none</b></td>
<td>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. '''[Required]'''</td>
<td>AS number is an identification of an autonomous system. The BGP protocol uses the AS number for detecting whether the BGP connection is internal or an external one.</td>
</tr>
</tr>
<tr>
<tr>
<td>BGP router ID</td>
<td>BGP router ID</td>
<td>default: <b>none</b></td>
<td>default: <b>none</b></td>
<td>The router id is used by BGP to identify the routing device from which a packet originated. default router ID value is selected as the largest IP Address of the interface.</td>
<td>The router ID is used by BGP to identify the routing device from which a packet originated. Fefault router ID value is selected as the largest IP Address of the interface.</td>
</tr>
</tr>
<tr>
<tr>
<td>Network</td>
<td>Network</td>
<td>default: <b>none</b></td>
<td>default: <b>none</b></td>
<td>Add an announcement network(s)</td>
<td>Adds an announcement network(s).</td>
</tr>
</tr>
<tr>
<tr>
<td>Redistribution options</td>
<td>Redistribution options</td>
<td>default: <b>none</b></td>
<td>default: <b>none</b></td>
<td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol.</td>
<td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td>
</tr>
</tr>
<tr>
<tr>
<td>Deterministic</td>
<td>Deterministic MED</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Compare MED between same AS ignoring their age</td>
<td>Compares MEDs between same AS, while ignoring their age.</td>
</tr>
</tr>
</table>
</table>
====BGP Peers====
====BGP Peers====
----
----
<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.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:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]]
The newly added BGP Peer configuration should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_added.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<th>Value</th>
<th>Value</th>
<th>Description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>Remote AS</td>
<td>Remote AS</td>
<td>default: <b>none</b></td>
<td>default: <b>none</b></td>
<td>Neighbour's remote AS</td>
<td>Remote autonomous system number of this remote BGP Neighbour.</td>
</tr>
</tr>
<tr>
<tr>
<td>Remote address</td>
<td>Remote address</td>
<td>IP; default: <b>none</b></td>
<td>ip4; default: <b>none</b></td>
<td>Neighbour's remote IPv4 address</td>
<td>IPv4 address of this remote BGP Neighbour.</td>
</tr>
<tr>
<td>Enable</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Turns turns this BGP peer on or off.</td>
</tr>
</tr>
</table>
</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.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer.png|border|class=tlt-border]]
<td>Enable</td>
<td>Enable</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Toggles BGP Peer on or off</td>
<td>Turns this BGP peer on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Remote AS</td>
<td>Remote AS</td>
<td>default: <b>none</b></td>
<td>default: <b>none</b></td>
<td>Neighbour's remote AS</td>
<td>Remote autonomous system number of this remote BGP Neighbour.</td>
</tr>
</tr>
<tr>
<tr>
<td>Remote address</td>
<td>Remote address</td>
<td>IP; default: <b>none</b></td>
<td>ip4; default: <b>none</b></td>
<td>Neighbour's remote IPv4 address</td>
<td>IPv4 address of this remote BGP Neighbour.</td>
</tr>
</tr>
<tr>
<tr>
<td>Remote port</td>
<td>Remote port</td>
<td>default: <b>none</b></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Neighbour's remote port</td>
<td>Listening port number of the BGP Neighbour.</td>
</tr>
</tr>
<tr>
<tr>
<td>EBGP Multihop</td>
<td>EBGP Multihop</td>
<td>default: <b>none</b></td>
<td>integer; default: <b>none</b></td>
<td>Time to Live value</td>
<td>Time to Live value for packets associated with this remote BGP Neighbour.</td>
</tr>
</tr>
<tr>
<tr>
<td>default originate</td>
<td>Default originate</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Announce default routes to the peer</td>
<td>Announces default routes to this peer.</td>
</tr>
</tr>
<tr>
<tr>
<td>Description</td>
<td>Description</td>
<td>default: <b>none</b></td>
<td>string; default: <b>none</b></td>
<td>You can leave notes here</td>
<td>A custom description for this BGP peer. Used for easier management purposes.</td>
</tr>
</tr>
</table>
</table>
====BGP Peer Groups====
====BGP Peer Groups====
----
----
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.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:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]]
The newly added BGP Peer Group configuration should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_added.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<td>Remote AS</td>
<td>Remote AS</td>
<td>default: <b>none</b></td>
<td>default: <b>none</b></td>
<td>Neighbour's remote AS</td>
<td>Remote autonomous system number.</td>
</tr></table>
</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.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group.png|border|class=tlt-border]]
<td>Enable</td>
<td>Enable</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Toggles the BGP Peer-Group on or off</td>
<td>Turns the BGP Peer Group configuration on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Remote AS</td>
<td>Remote AS</td>
<td>default: <b>none</b></td>
<td>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>IP; 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 Neighbour.</td>
</tr>
</tr>
<tr>
<tr>
<td>Advertisement interval</td>
<td>Advertisement interval</td>
<td>default: <b>none</b></td>
<td>integer; default: <b>none</b></td>
<td>Delay between updates for a neighbor session</td>
<td>BGP advertisement frequency (in seconds).</td>
</tr>
</tr>
<tr>
<tr>
<td>Neighbor configuration</td>
<td>Neighbor configuration</td>
<td>default: '''None'''</td>
<td>None | Route Reflector client | Route Server client; default: <b>None</b></td>
<td>Configure a neighbor as Route Reflector or Route Server client.</td>
<td>Defines the role of a BGP Neighbour.
<ul>
<li><b>Route Reflector client</b> - redistributes received routes.</li>
<li><b>Route Server client</b> - distributes routes.</li>
</ul>
</td>
</tr>
</tr>
<tr>
<tr>
<td>Disable next hop calculation</td>
<td>Disable next hop calculation</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Disable the next hop calculation for this group</td>
<td>Turns next hop calculation for this BGP Peer Group on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Inbound soft-reconfiguration</td>
<td>Inbound soft-reconfiguration</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Allow inbound soft reconfiguration for this neighbor</td>
<td>Turns inbound soft-reconfiguration for this neighbor on or off.</td>
</tr>
</tr>
<tr>
<tr>
====Access List Filters====
====Access List Filters====
----
----
Below is an example of '''Access List Filters''' section.
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.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button.png|border|class=tlt-border]]
You can add a new list by simply pressing '''Add''' button.
You can add a new list by simply pressing '''Add''' button.
<th>Value</th>
<th>Value</th>
<th>Description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>Peer</td>
<td>Peer</td>
<td>bgp peer; default: '''first peer on list'''</td>
<td>bgp peer; default: <b>none</b></td>
<td>Applies the rule for the specified peer.</td>
<td>Applies the filter rule for the specified peer.</td>
</tr>
</tr>
<tr>
<tr>
<td>Action</td>
<td>Action</td>
<td>default: '''Permit'''</td>
<td>Permit | Deny; default: <b>Permit</b></td>
<td>Denies or permits matched entry.</td>
<td>When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
</tr>
</tr>
<tr>
<tr>
<td>Network</td>
<td>Network</td>
<td>default: '''Any'''</td>
<td>ip/netmask | Any; default: <b>none</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>default: '''Inbound'''</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>
<td>Enable</td>
<td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Turns an Access filter on or off.</td>
</tr>
</tr>
</table>
</table>
