Template:Networking tswos manual dynamic routes
The information in this page is updated in accordance with firmware version .
Dynamic Routes
Summary
The Routing page is used to set up static routes, routing tables and rules.
This manual page provides an overview of the Routing windows in {{{name}}} devices.
Dynamic Routing provides the possibility to route data based on current network or device state instead of relying on static entries in the routing table. The {{{name}}} device supports these dynamic routing protocols:
- BGP (Border Gateway Protocol)
- RIP (Routing Information Protocol)
- OSPF (Open Shortest Path First)
- EIGRP (Enhanced Interior Gateway Routing Protocol)
Each protocol is described in the sections below.
BGP
The Border Gateway Protocol (BGP) is a standardized exterior gateway protocol designed to exchange routing and reachability information among autonomous systems (AS) on the Internet. The protocol is often classified as a path vector protocol but is sometimes also classed as a distance-vector routing protocol. The Border Gateway Protocol makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator and is involved in making core routing decisions.
General Settings
The General Settings section is used to turn BGP protocol usage on or off or to upload an external BGP configuration. Below is an example of the BGP General Settings section.
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns BGP protocol usage on or off. |
| Enable vty | off | on; default: off | Turns vty access on or off. |
| Import config | - (interactive button) | Uploads an external BGP configuration. |
BGP Instance
User can edit BGP instance by clicking on edit button.
You will be redirected to general BGP instance settings:
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns the BGP instance on or off. |
| AS | integer [1..4294967295]; default: none | 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. |
| BGP router ID | 32-bit integer; default: none | 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. |
| Network | ip/netmask; default: none | Adds an announcement network(s). Routes to these networks will be shared over BGP. |
| VRF interface | VRF interface; default: Default | To create new VRF interface, please visit: [[{{{name}}} VRF|VRF]] |
| Redistribution options | Connected routes | Kernel added routes | NHRP routes | OSPF routes | Static routes | custom; default: none | 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. |
| Deterministic MED | off | on; default: off | Compares MEDs between same AS, while ignoring their age. |
| eBGP Requires Policy | off | on; default: on | Enable/Disable eBGP Import or Export policy requirement. Enabled by default as per RFC 8212. |
BGP Peers
BGP Peers 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.
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:
You will be redirected to general peer settings:
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns this BGP peer on or off. |
| Remote AS | integer [1..4294967295]; default: none | Remote autonomous system number of this remote BGP Neighbor. |
| Remote address | ip4; default: none | IPv4 address of this remote BGP Neighbor. This option is required. |
| Remote port | integer [0..65535]; default: none | Listening port number of the BGP Neighbor. |
| EBGP Multihop | integer; default: none | Time to Live value for packets associated with this remote BGP Neighbor. |
| Weight | integer [0..65535]; default: none | Specifies a default weight value for the neighbor’s routes. Higher weight is preferred. |
| Keepalive timer | integer [0..65535]; default: none | Frequency (in seconds) of keep alive messages. |
| Holdtime | integer [0..65535]; default: none | Max wait time (in seconds) for a response from this neighbor before considering the peer unreachable. |
| Connect timer | integer [1..65535]; default: none | Max time (in seconds) to make a connection to this peer. If a connection cannot be made in this time, connection to this peer is considered unsuccessful. |
| Default originate | off | on; default: off | Announces default routes to this peer. |
| Description | string; default: none | A custom description for this BGP peer. Used for easier management purposes only. |
| Password | string; default: none | Password for this BGP Neighbor. |
BGP Peer Groups
A BGP Peer Group 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.
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:
You will be redirected to general peer groups settings:
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns the BGP Peer Group configuration on or off. |
| Remote AS | integer [1..65535]; default: none | Neighbour's remote AS. |
| Neighbor address | ip4; default: none | Neighbour's remote IPv4 address. |
| Listen Range | ip4 with mask; default: none | Accept connections from any peers in the specified prefix. |
| Advertisement interval | integer; default: none | Delay between updates for a neighbor session (in seconds). |
| Neighbor configuration | None | Route Reflector client | Route Server client; default: None | Defines the role of a BGP Neighbor.
|
| Disable next hop calculation | off | on; default: off | Turns next hop calculation for this BGP Peer Group on or off. |
| Apply also to ibgp-learned routes | off | on; default: off | When acting as a route reflector, applies to ibgp-learned routes as well. This field becomes visible when 'Disable next hop calculation' is turned on. |
| Inbound soft-reconfiguration | off | on; default: off | Turns inbound soft-reconfiguration for this Neighbor on or off. |
| Disable connected check | off | on; default: off | When turned on, Disable connected check enables a directly connected eBGP Neighbor to peer using a loopback address without adjusting the default TTL of 1. |
Route Map Filters
The Route Map Filters 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
An Route Map Filters configuration for BGP should look similar to this:
| Field | Value | Description |
|---|---|---|
| Peer | bgp peer; default: - | Applies the filter rule for the specified peer. |
| Route map | route map; default: - | Route map filter to apply. |
| Direction | Inbound | Outbound; default: Inbound | If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes. |
| Enable | off | on; default: off | Turns an Route Map filter on or off. |
Access List Filters
The Access List Filters 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
An Access List Filter configuration for BGP should look similar to this:
| Field | Value | Description |
|---|---|---|
| Peer | bgp peer; default: - | Applies the filter rule for the specified peer. |
| Action | Permit | Deny; default: Permit | When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic. |
| Filter network | Any | custom; default: Any | Applies filter rule for this source network. |
| Direction | Inbound | Outbound; default: Inbound | If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes. |
| Enable | off | on; default: off | Turns an Access filter on or off. |
Route Maps
A Route Maps 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.
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:
You will be redirected to general route maps settings:
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns the Route Maps configuration on or off. |
| Action | Permit | Deny; default: Permit | IPv4 address of this remote BGP Neighbor. |
| Local preference | integer [0..4294967295]; default: none | Used to determine best route towards a certain destination. |
| Metric | ip4 with mask; default: none | Sets a metric value for determining the preferred path into an AS. |
RIP
The Routing Information Protocol (RIP) is one of the oldest distance-vector routing protocols which employ the hop count as a routing metric. RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from source to destination. The maximum number of hops allowed for RIP is 15, which limits the size of networks that RIP can support. A hop count of 16 is considered an infinite distance and the route is considered unreachable. RIP implements the split horizon, route poisoning and holddown mechanisms to prevent incorrect routing information from being propagated.
General Settings
The General Settings section is used to configure some of the main operating parameters of the RIP protocol. Below is an example of the RIP General Settings section.
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns RIP Protocol usage on or off. |
| Enable vty | off | on; default: off | Turns vty access on or off. |
| Import config | - (interactive button) | Upload a external RIP configuration. |
| Version | 2 | 1; default: 2 | Specifies the used version of the RIP protocol. |
| Neighbor | rip neighbor; default: none | Defines a RIP Neighbor(s). |
RIP Interfaces
The RIP Interfaces section is used to define which existing network interfaces can participate in RIP communication. Below is an example of the RIP Interfaces section which is empty by default.
To create a new RIP Interface, look to the Add New Interface section; enter a custom name and click the 'Add' button:
RIP Interface configuration should look similar to this:
| Field | Value | Description |
|---|---|---|
| Interface | network interface; default: loopback | Network interface that will be used with the RIP protocol. |
| Passive interface | off | on; default: off | Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and ripd does not send either multicast or unicast RIP packets. |
| Enable | off | on; default: off | Turns a RIP Interface on or off. |
| Delete | - (interactive button) | Deletes RIP inerfaces instance. |
Access list filters
The Access List Filters section is used to configure special filters that restrict or allow access to specified networks for RIP Neighbors. Below is an example of the Access List Filters section which is empty by default.
To add a new filter, look to the Add New Instance section; enter a custom name and select RIP interface then click the 'Add' button:
An Access List Filter configuration for RIP should look similar to this:
| Field | Value | Description |
|---|---|---|
| Name | string on; default: none | A custom name for a filter. Used for easier management purposes only. |
| Enable | off | on; default: off | Turns an Access filter on or off. |
| RIP interface | rip interface; default: none | Specifies the RIP interface to which the filter will apply to. |
| Action | Permit | Deny; default: Permit | When RIP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic. |
| Network | ip/netmask | Any; default: Any | Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field. |
| Direction | Inbound | Outbound; default: Inbound | Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound). |
OSPF
Open Shortest Path First (OSPF) is a routing protocol for Internet Protocol (IP) networks. It uses a link state routing (LSR) algorithm and falls into the group of interior gateway protocols (IGPs), operating within a single autonomous system (AS). It is defined as OSPF Version 2 in RFC 2328 for IPv4.
General Settings
The General Settings section is used to configure some of the main operating parameters of the OSPF protocol. Below is an example of the OSPF General Settings section.
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns OSPF Protocol usage on or off. |
| Enable vty | off | on; default: off | Turns vty access on or off. |
| Import | - (interactive) | Uploads a external OSPF configuration. |
| Router ID | 32-bit integer; default: none | Sets the router-ID in the OSPF network. |
| Passive interfaces | network interface(s); default: none | Network interfaces that should be considered as passive. OSPF hello packets are not sent on these interfaces. |
| Generate a default external route | off | default | always; default: off | Defines the behavior for advertising a default route over OSPF. Possible values are:
|
| Redistribution options | Connected routes | Kernel | NHRP | BGP | OSPF | RIP | EIGRP | Static; default: none | 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. |
OSPF Interface
The OSPF Interfaces section is used to define which existing network interfaces can participate in OSPF communication. Below is an example of the OSPF Interfaces section which is empty by default. To create a new OSPF Interface, simply click the 'Add' button:
OSPF Interface configuration should look similar to this:
| Field | Value | Description |
|---|---|---|
| Interface | network interface; default: loopback | Network interface that will be used with the OSPF protocol. |
| Enable | off | on; default: off | Turns an OSPF Interface on or off. |
To see more settings for an OSPF interface, click the 'Edit' button next to it:
You should directed to a window such as this:
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns the OSPF area on or off. |
| Cost | integer [1..65535]; default: none | The cost value is set to router-LSA’s metric field and used for SPF calculation. |
| Hello Interval | integer [1..65535]; default: 10 | Frequency (in seconds) at which a "Hello" packet is sent out on the specified interface. |
| Router Dead Interval | integer [1..65535]; default: 40 | This value must be the same for all routers attached to a common OSPF network. |
| Retransmit | integer [0..65535]; default: 5 | Used in Database Description and Link State Request packet re-transmission. |
| Priority | integer [0..255]; default: 1 | OSPF router priority. The router with the highest priority will be more eligible to become the "Designated Router". Setting the value to 0, makes the router ineligible to become a "Designated Router." |
| Type | Broadcast | Non-Broadcast | Point-to-point | Point-to-Multipoint; default: Broadcast | OSPF interface configuration type. |
| Authentication | None | Password | MD5 HMAC; default: None | Specifies the Authentication method. |
OSPF Neighbors
The OSPF Neighbors section can be used to configure other users ("neighbors") of the same OSPF network statically.
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns this OSPF neighbor configuration on or off. |
| Neighbor | ip4; default: none | IP address of the OSPF neighbor. |
| Neighbor Priority | integer [1..255]; default: none | Priority of this neighbor |
| Polling interval | integer [1..65535]; default: none | Check for dead neighbor interval (in seconds). |
OSPF Area
An OSPF Area is a collection of OSPF Networks that can serve each other. Below is an example of the OSPF Area section which is empty by default.
To add a new OSPF Area, look to the Add New Area section; enter a custom name and click the 'Add' button.
The newly added new Area will appear in the OSPF Area list.
| Field | Value | Description |
|---|---|---|
| Name | string on; default: none | A custom name for an OSPF Area. Used for easier management purposes only. |
| Area | 32-bit integer; default: none | OSPF Area ID. OSPF Networks that are meant to communicate with each other should belong to the same Area (have the Area ID). |
| STUB | off | on; default: off | A stub area is an area in which advertisements of external routes are not allowed, reducing the size of the database. |
| Enable | off | on; default: off | Turns an OSPF Area on or off. |
OSPF Networks
The OSPF Network section is used to add networks to OSPF areas that can later be shared (provide access to) with other OSPF routers.
Below is an example of the OSPF Area section which is empty by default.
To add a new OSPF Network, look to the Add New Network section; enter a custom name and click the 'Add' button.
Your new network will appear in the OSPF Networks list
| Field | Value | Description |
|---|---|---|
| Name | string on; default: none | A custom name for an OSPF Area. Used for easier management purposes only. |
| Network | ip/netmask; default: none | IP address/netmask of a network. OSPF Network locations are shared with other OSPF routers. |
| Area | OSPF area; default: none | ID of an OSPF Area (to which this network should belong to). |
| Enable | off | on; default: off | Turns the usage of this network (in OSPF) on or off. |
EIGRP
Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration.
General
The General Settings section is used to configure some of the main operating parameters of the EIGRP protocol. Below is an example of the EIGRP General Settings section.
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns EIGRP protocol usage on or off. |
| Enable logging | off | on; default: off | Turns logging of EIGRP traffic on or off. |
| AS | integer [1..65535]; default: none | EIGRP Autonomous System (AS) number. It is an identifier that represents a routing domain; EIGRP routers can exchange routes within the same Autonomous System. |
| Router ID | ip4; default: none | The router ID is used by EIGRP to identify the routing device from which a packet originated. Default router ID value is selected as the largest IP Address of the interface. |
| Network | ip/netmask; default: none | Adds an announcement network(s). Routes to these networks will be shared over EIGRP. |
| Redistribution options | Connected routes | Kernel added routes | NHRP routes | OSPF routes | Static routes | custom; default: none | 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. |
| Neighbors | ip4; default: none | Defines the EIGRP Neighbors (based on their IP addresses) that this device is meant to associate with. |
[[Category:{{{name}}} Network section]]