Routing Options

This chapter describes routing options that apply to all dynamic routing protocols.

Routing Options (Apply, Reset and Reload) - Gaia Portal

In the Advanced Routing > Routing Options page of the Portal, clicking these buttons has this effect:

• Apply - Save changes in this page.
• Reload - Discard unsaved changes. This is the same as navigating away from the page, discarding changes, and returning to the page.
• Reset - Restart the routed routing daemon on the Gaia appliance or computer.

Equal Cost Path Splitting

You can configure the maximal number of equal‑cost paths that will be used when there is more than one equal‑cost path to a destination. You can specify a value for the maximal number of equal‑cost paths that will be used when there is more than one equal‑cost path to a destination. Only OSPF routes and Static routes are able to use more than one "next hop"

• Range: 1 to 8
• Default: 8

The "next hop" algorithm that is used for forwarding when there is more than one "next hop" to a destination is Source/destination hash: A hash function is performed on the source and destination IP address of each packet that is forwarded to a multipath destination. This result is used to determine which next hop to use.

Configuring Equal Cost Path Splitting - Gaia Portal

1. In the tree view, click Advanced Routing > Routing Options.
2. In the Equal Cost Multipath section, select the Maximum Paths.
3. Click Apply.

Configuring Equal Cost Path Splitting - Gaia Clish (max-path-splits)

1. Run: set max-path-splits <1—8>

   For example: set max-path-splits 2

2. Run: save config

Kernel Options - Kernel Routes

Route Injection Mechanism (RIM) enables a Security Gateway to use dynamic routing protocols to propagate the encryption domain of a VPN peer Security Gateway to the internal network and then initiate back connections. When a VPN tunnel is created, RIM updates the local routing table of the Security Gateway to include the encryption domain of the VPN peer.

In Gaia, the Route Injection Mechanism adds routes directly to the kernel. For the routes to remain in the Kernel, you must configure this option.

For more about configuring RIM, see the R77 Site to Site VPN Administration Guide.

Configuring Kernel Routes - Gaia Portal

1. In the tree view, click Advanced Routing > Routing Options.
2. In the Kernel Options area, select the Kernel Routes option.
3. Click Apply.

Configuring Kernel Routes - Gaia Clish (kernel-routes)

1. Run: set kernel-routes on
2. Run: save config

Protocol Rank

Rank is used by the routing system when there are routes from different protocols to the same destination. For each route, the route from the protocol with lowest rank number is used.

The protocol rank is the value that the routing daemon uses to order routes from different protocols to the same destination. It is an arbitrarily assigned value used to determine the order of routes to the same destination. Each route has only one rank associated with it, even though rank can be set at many places in the configuration. The route derives its rank from the most specific route match among all configurations.

The active route is the route installed into the kernel forwarding table by the routing daemon. In the case where the same route is contributed by more than one protocol, the one with the lowest rank becomes the active route.

Rank cannot be used to control the selection of routes within a dynamic interior gateway protocol (IGP); this is accomplished automatically by the protocol and is based on the protocol metric. Instead, rank is used to select routes from the same external gateway protocol (EGP) learned from different peers or autonomous systems.

Some protocols - BGP and aggregates - allow for routes with the same rank. To choose the active route in these cases, a separate tie breaker is used. This tie breaker is called LocalPref for BGP and weight for aggregates.

Default Ranks

A default rank is assigned to each protocol. Rank values range from 0 to 255, with the lowest number indicating the most preferred route.

The default rank values are:

These numbers do not generally need to be changed from their defaults. Use caution when modifying the default route ranks. Rank affects the route selection process, so unexpected consequences may occur throughout the network. Such a change should be planned carefully and take into account both the protocols being used and the location of the router in the network.

Configuring Protocol Rank - Gaia Portal

To set route rank in the Gaia Portal:

1. Go to Advanced Routing > Routing Options.
2. In the Protocol Rank section, enter the route rank for each protocol.
3. Click Apply.

Configuring Protocol Rank - Gaia Clish (protocol-rank)

Rank is used by the routing system when there are routes from different protocols to the same destination. For each route, the route from the protocol with lowest rank number is used.

Syntax

set protocol-rank protocol

	bgp rank <0—255> | default

	rip rank <0—255> | default

	ospf rank <0—255> | default

	ospfase rank <0—255> | default

	ospf3 rank <1—255> | default

	ospf3ase rank <1—255> | default

Advanced Routing Options - Wait for Clustering

In a clustering environment, Wait for Clustering has this effect:

Configuring Wait for Clustering - Gaia Portal

To set the Wait for Clustering routing option in the Gaia Portal:

1. Go to Advanced Routing > Routing Options.
2. In the Router Options area, select Wait for Clustering.
3. Click Apply.

Configuring Wait for clustering - Gaia Clish (router-options)

To turn on Wait for Clustering:

1. Run: set router-options wait-for-clustering on
2. Run: save config

To turn off Wait for Clustering:

1. Run: set router-options wait-for-clustering off
2. Run: save config

To show the state of the Wait for Clustering option:

Run: show router-options

Advanced Routing Options - Auto Restore of Interface Routes

An interface route may be automatically deleted in error from the router kernel when it becomes reachable from another interface. The command show route in Clish shows the route, but the Expert mode command ip route does not show the route. A scenario where this can happen is when the same route is learned via OSPF and BGP.

You can avoid losing the interface routes by enabling the Automatic Restoration of Interface Routes option. By default, this option is Off.

Note: If the interface route was deleted and the option was not enabled, bring the interface DOWN and then bring it UP again using Clish, the Portal or, in Expert mode, using ifconfig.

To Automatically Restore Routes - Gaia Portal:

1. In the Gaia Portal, go to the Advanced Routing > Routing Options page.
2. In the Advanced Router Options area, select Auto Restore of Iface Routes.
3. Click Apply.

To turn on Auto Restore of Interface Routes - Gaia Clish:

1. Run: set router-options Auto-restore-iface-routes on
2. Run: save config

To turn off Auto Restore of Interface Routes - Gaia Clish:

1. Run: set router-options Auto-restore-iface-routes off
2. Run: save config

To show the state of the Auto Restore of Interface Routes option - Gaia Clish:

Run: show router-options

Trace Options

The routing system can optionally log information about errors and events. Logging is configured for each protocol or globally. Logging is not generally turned on during normal operations, as it can decrease performance. Log messages are saved in the /var/log/routed.log.* files.

Configuring Trace Options - Gaia Portal

To enable Trace options:

1. In the tree view, click Advanced Routing > Routing Options.
2. Click the Configuration tab.
3. In the Trace Options section, configure:
   • Maximum Trace File Size - enter a value between 1 to 2047 MB (the default is 1)

     Note - When the trace file reaches the specified size, it is renamed to routed.log.0, then routed.log.1, routed.log.2

   • Number of Trace Files - enter a number between 1 to 4294967295 (the default is 10)
   • Filter Visible Tables Below - select trace options tables - Show All, Global, BGP, Bootp / DHCP Relay, ICMP, IGMP, IP Broadcast Helper, Kernel, MFC, OSPF, Policy Based Routing, PIM, RIP, Router Discovery, VRRP, IPv6 OSPF (in R77.30 only), IPv6 Router Discovery (in R77.30 only), IPv6 VRRP (in R77.30 only)
   • In each trace options table, select options (to select multiple options, hold down Shift and click the options)
   • Click Add.
4. Click Apply at the top of the page

If you want to enable tracing of a specific routing option for all protocols, in the Global options table, select that option. If you want to enable tracing of all routing options for all protocols, in the Global options table, select All.

For an explanation of each trace option, see the Description of Trace Options.

You can see the most recent trace log messages in the /var/log/routed.log log file.

To monitor a Trace options:

1. In the Monitoring tab of the Advanced Routing > Routing Options view, configure the Number of lines that you want to show at the end (the "tail") of the log file -minimum is 5, maximum is 100.
2. Click Get Tail.

   The log messages show.

Configuring Trace Options - Gaia Clish

Before you configure the routing trace options, you can configure the log file size and the maximal number of log files.

To configure the log file options:

Run these commands:

set tracefile maxnum {<num> | default}

set tracefile size {<size_MB> | default}

Command parameters:

To configure the routing trace options:

Run this command:

set trace {bgp | bootp | cluster | global | icmp | igmp | iphelper | kernel | mfc | ospf | ospf3 | pbr | pim | rip | router-discovery | router-discovery6 | vrrp | vrrp6} <protocol-specific event option> {on | off}

To configure the protocol-specific event options:

• To configure Global routing trace options, run the command:

  set trace global {adv | all | cluster | general | normal | parse | policy | route | state | task | timer} {on | off}

• To configure Kernel trace options, run the command:

  set trace kernel {all | cluster | iflist | interface | general | normal | packets | policy | remnants | request | route | routes | state | task | timer} {on | off}

• To configure OSPFv2 for IPv4 trace options, run the command:

  set trace ospf {ack | all| cluster | dd | dr | general | hello | lsa | normal | packets | policy | request | route | spf | state | task | timer | trap | update} {on | off}

• To configure OSPFv3 for IPv6 trace options (available in R77.30), run the command:

  set trace ospf3 {ack | all | cluster | dd | dr | general | hello | lsa | normal | packets | policy | request | route | spf | state | task | timer | trap | update} {on | off}

• To configure BGP trace options, run the command:

  set trace bgp {all | cluster | general | keepalive | normal | open | packets | policy | route | state | task | timer | update} {on | off}

• To configure Cluster trace options, run the command:

  set trace cluster all {on | off}

• To configure PIM trace options, run the command:

  set trace pim {all | assert | bootstrap | cluster | crp | general | graft | hello | join | normal | mfc | mrt | packets | policy| refresh | register | route | rp | state | task | timer | trap} {on | off}

• To configure IGMP trace options, run the command:

  set trace igmp {all | cluster | general | group | leave | mtrace | normal | packets | policy | query | report | request | route | state | task | timer} {on | off}

• To configure Bootp / DHCP Relay for IPv4 trace options, run the command:

  set trace bootp {all | cluster | general | normal | packets | policy | request | response | route | state | task | timer} {on | off}

• To configure ICMP trace options, run the command:

  set trace icmp {all | cluster | error | general | info | normal | packets | policy | route | router-discovery | state | task | timer} {on | off}

• To configure ICMP Router Discovery for IPv4 trace options, run the command:

  set trace router-discovery {all | cluster | general | normal | policy | route | state | task | timer} {on | off}

• To configure ICMP Router Discovery for IPv6 trace options, run the command:

  set trace router-discovery6 {all | cluster | general | normal | policy | route | state | task | timer} {on | off}

• To configure IP Broadcast Helper trace options, run the command:

  set trace iphelper {all | cluster | general | normal | packets | policy | route | state | task | timer} {on | off}

• To configure VRRP for IPv4 trace options, run the command:

  set trace vrrp {advertise | all | cluster | general | normal | policy | route | state | task | timer} {on | off}

• To configure VRRP for IPv6 trace options (available in R77.30), run the command:

  set trace vrrp6 {advertise | all | cluster | general | normal | policy | route | state | task | timer}{on | off}

• To configure Policy Based Routing (PBR) trace options, run the command:

  set trace pbr {all | general | normal | policy | route | rule | state | table | task | timer | cluster} {on | off}

• To configure Multicast Forwarding Cache (MFC) trace options, run the command:

  set trace mfc {all | alerts | cache | cluster | general | interface | mcastdist | normal | packets | policy | resolve | route | state | task | timer | wrongif} {on | off}

• To configure RIP for IPv4 trace options, run the command:

  set trace rip {all | general | normal | packets | policy |route | state | task | timer | cluster} {on | off}

Notes:

• To add several trace options, run the command once for every trace option.
• For an explanation of each trace option, see the Description of Trace Options.

Description of Trace Options

This section shows descriptions of all trace options.

Common Trace options

These event options are common among all protocol option tables:

For options that are unique to each protocol, see relevant protocol sections below.

Global Trace options

These event options are specific to Global options table:

Kernel Trace Options

These event options are specific to Kernel options table:

OSPFv2 for IPv4 Trace Options

These event options are specific to OSPFv2 for IPv4 options table:

OSPFv3 for IPv6 Trace Options

These event options are specific to OSPFv3 for IPv6 options table (available in R77.30):

BGP Trace Options

These event options are specific to BGP options table:

Cluster Trace Options

There are no event options that are specific to Cluster options table.
Use options that are common for all protocols. See Common Trace options.

PIM Trace Options

These event options are specific to PIM options table and apply to Dense-Mode and Sparse-Mode implementations:

These event options are specific to PIM options table and apply to Sparse-Mode implementation only:

This event option is specific to PIM options table and applies to Dense-Mode implementation only:

IGMP Trace Options

These event options are specific to IGMP options table:

Bootp / DHCP Relay Trace Options

These event options are specific to Bootp / DHCP Relay for IPv4 options table:

ICMP Trace Options

These event options are specific to ICMP options table:

ICMP Router Discovery for IPv4 Trace Options

There are no event options that are specific to ICMP Router Discovery for IPv4 options table.
Use options that are common for all protocols. See Common Trace options.

ICMP Router Discovery for IPv6 Trace Options

There are no event options that are specific to ICMP Router Discovery for IPv6 options table (available in R77.30).
Use options that are common for all protocols. See Common Trace options.

IP Broadcast Helper Trace Options

These event options are specific to IP Broadcast Helper options table:

VRRPv2 for IPv4 Trace Options

This event option is specific to VRRPv2 for IPv4 options table:

VRRPv3 for IPv6 Trace Options

This event option is specific to VRRPv3 for IPv6 options table (available in R77.30):

Policy Based Routing Trace Options

These event options are specific to Policy Based Routing (PBR) options table:

MFC Trace Options

These event options are specific to Multicast Forwarding Cache (MFC) options table:

RIP Trace Options

This event option is specific to RIP for IPv4 options table: