Configuring RIP in Gaia Clish

Important - In a ClusterClosed Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing., you must configure all the Cluster Members in the same way.

set rip

      auto-summary {off | on}

      expire-interval {<1-65535. | default}

      export-routemap <Name of RouteMap>

            off

            preference <Preference> on

      import-routemap <Name of RouteMap>

            off

            preference <Preference> on

      interface <Name of Interface>

            [version {1 | 2} on]

            accept-updates {off | on}

            authtype

                  md5 secret <Password> [cisco-compatibility {off | on}]

                  none

                  simple <Password>

            metric {<0-16> | default}

            {off | on}

            send-updates {off | on}

            transport {multicast | broadcast}

            virtual-address {off | on}

      update-interval {<1-65535> | default}

The mandatory parameters are marked Mandatory. All other parameters are optional.

Parameter

Description

auto-summary {off | on}

Applies only to RIP v1.

Controls whether to aggregate and redistribute automatically the non-classful RIP v1 into RIP v2.

Important:

  • If you do not enable this option, you must use route aggregation and route redistribution and configure the aggregation and redistribution manually.

  • Be careful when you configure this option, because RIP protocol has no mechanism to detect misconfiguration.

Range: off, or on

Default: off

expire-interval {<1-65535. | default}

The amount of time that must pass with no update for a given route before the route is considered to have timed out.

Note - This value must be 6 times the Update Interval before the network drops packets, which contain an update.

Range: 1-65535 seconds

Default: 180 seconds

export-routemap <Name of RouteMap> off

Disables the configured Route Map for export policy.

See Configuring Route Maps in Gaia Clish.

export-routemap <Name of RouteMap> preference <Preference> on

Configures preference the configured export Route Map.

Route Maps are applied in order of increasing preference value.

Warning - Configuring an export Route Map for RIP disables any route-redistribution configurations for export to RIP. To ensure that RIP continues to advertise routes according to prior redistribution policy, add another Route Map to redistribute them.

See Configuring Route Maps in Gaia Clish.

import-routemap <Name of RouteMap> off

Disables the configured Route Map for import policy.

See Configuring Route Maps in Gaia Clish.

import-routemap <Name of RouteMap> preference <Preference> on

Configures preference the configured import Route Map.

Route Maps are applied in order of increasing preference value.

Warning - Configuring an import Route Map for RIP disables any inbound-route-filter configurations for import into RIP. To ensure that RIP continues to learn routes according to prior redistribution policy, add another Route Map to redistribute them.

See Configuring Route Maps in Gaia Clish.

interface <Name of Interface> {off | on}

Disables (off) or enables (on) RIP on the specified interface.

version {1 | 2} on]

Configures the RIP version.

If you configure RIP v2, the default is to send full RIP v2 packets on the RIP multicast address.

  • Range: 1, or 2

  • Default: 1

accept-updates {off | on}

Controls if RIP packets from other routers, which use the interface, are accepted or ignored.

Ignoring an update may result in suboptimal routing.

Range: off, or on

Default: on

authtype ...

Applies only to RIP v2.

The type of authentication scheme to use for the link.

In general, routers on a given link must agree on the authentication configuration in order to form neighbor adjacencies.

This is used to guarantee that routing information is accepted only from trusted routers.

  • authtype md5 secret <Password> [cisco-compatibility {off | on}]

    Implements an authentication scheme that uses an MD5 algorithm for the interface to accept routing information from neighboring routers.

    Password must contain from 1 to 16 characters.

    These characters are supported:

    • a-z

    • A-Z

    • 0-9

    • ` ~ ! @ # % ^ & * ( ) { } [ ] : ; , . _ - + =

  • authtype none

    There is no authentication scheme for the interface to accept routing information from neighboring routers.

  • authtype simple <Password>

    Implements a simple authentication scheme for the interface to accept routing information from neighboring routers.

    Password must contain from 1 to 16 characters.

    These characters are supported:

    • a-z

    • A-Z

    • 0-9

metric {<0-16> | default}

The RIP metric to add to routes that are sent with the specified interface(s).

This is used to make other routers prefer other sources of RIP routes over this router.

A higher metric means routes appear more expensive.

Setting the metric to 0 or default removes the stored value.

  • Range: default, or 1-16

  • Default: default (none)

send-updates {off | on}

Controls if RIP packets are sent through the interface.

If you do not enable this option, the interface becomes a passive RIP listener.

Range: off, or on

Default: on

transport {multicast | broadcast}

Controls how to send the RIP packets.

In the Multicast mode, RIP v2 packets are sent as multicast on this interface.

  • Range: multicast, or broadcast

  • Default: multicast

virtual-address {off | on}

Applies only to VRRP Cluster.

Makes RIP run only on the VRRP Virtual IP address related to this interface.

If this router is not a VRRP Master, then RIP does not run, if this option is selected. It only runs on the VRRP Master.

Make sure that VRRP is configured to accept connections to VRRP IP addresses.

Note - You must use VRRP Monitored Circuit mode, when you configure VRRP to work with Virtual IP addresses, and when you configure Virtual IP support for a dynamic routing protocol, including RIP.

Range: off, or on

Default: off

update-interval {<1-65535> | default}

The amount of time between regularly scheduled RIP updates.

To prevent synchronization of periodic updates, RIP updates are actually sent at a time from the uniform distribution on the interval (0.5*"Update Interval value", 1.5*"Update Interval value").

Important - Be careful when you set this parameter, because RIP has no protocol mechanism to detect misconfiguration.

Range: 1-65535 seconds

Default: 30 seconds