RIP

The following command sequences create a logical IP interface. The logical interface can associate attributes like an IP address, port, Link Aggregation Group (LAG), or the system. For more information about configuring interfaces, see the 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide.

The CLI syntax, to configure a network interface is shown below.

CLI syntax

config router
  interface ip-int-name
    address ip-addr{/mask-length | mask} [broadcast
       {all-ones | host-ones}]
    port port-id

The following example displays router interface configuration command usage.

Example

config>router> interface “to-ALA-4”
config>router>if$ address 10.10.12.1/24
config>router>if# port 1/1/1
config>router>if# exit

The following example displays the IP configuration output showing the interface information.

ALA-3>config>router# info
#------------------------------------------
echo "IP Configuration "
#------------------------------------------
        interface "system"
            address 10.10.10.103/32
        exit
        interface "to-ALA-4"
            address 10.10.12.1/24
            port 1/1/1
        exit
#------------------------------------------
ALA-3>config>router#

Use the import route policy to filter routes imported by the local router from its neighbors. If no match is found, the local router does not import any routes.

Use the export route policy to determine which routes are exported from the route table to RIP. By default, RIP does not export learned routes to its neighbors. If no export policy is specified, non-RIP routes are not exported from the routing table manager to RIP.

If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered overrides the previous command. A maximum of five policy names can be specified.

This section only provides brief instructions to configure route policies. For more details, see the Route policy configuration overview chapter.

To enter the mode to create or edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include:

• the commit command saves and enables changes made to route policies during a session

• the abort command discards changes that have been made to route policies during a session

Use the following CLI syntax to configure a policy to use for the RIP global, group, and neighbor import and export commands.

CLI syntax

config>router>policy-options
  begin
  commit
  abort
  policy-statement name
    description text
    default-action {accept|next-entry|nextpolicy|drop|reject}
    entry entry-id
      description text
      action {accept|next-entry|nextpolicy|drop|reject}
       from
       to

Use the following CLI syntax to enter the edit mode:

CLI syntax

config>router>policy-options
  begin

The following example displays some commands to configure a policy statement. Policy option commands are configured in the config>router context. Use the commit command to save the changes.

Example

config>router>policy-options# begin
policy-options# policy-statement “RIP policy”
policy-options>policy-statement$ description "this is a test RIP policy”
policy-options>policy-statement>default# entry 1
policy-options>policy-statement>entry$ action accept
policy-options>policy-statement>entry# exit
policy-options>policy-statement# default-action reject
policy-options>policy-statement# exit
policy-options# commit

ALA-A>config>router>policy-options# info
----------------------------------------------
policy-statement "RIP-policy"
description "this is a test RIP policy"
entry 1
action accept
exit
exit
default-action reject
exit
----------------------------------------------
ALA-A>config>router>policy-options>policy-statement#

Use the CLI syntax described in this section to configure RIP parameters at the global, group, and neighbor level.

CLI syntax

config>router
  rip
  authentication-key [authentication-key | hash-key [hash|hash2|custom]
  authentication-type {none | password | message-digest | message-digest-20}
  check-zero {enable | disable}
  description string
  export policy-name [policy-name ...up to 5 max]
  import policy-name [policy-name ...up to 5 max]
  message-size number 
  metric-in metric
  metric-out metric
  preference number
  receive {both | none | version-1 | version-2}
  send {broadcast | multicast | none | version-1 | both}
  no shutdown
  split-horizon {enable | disable}
  timers update timeout flush 

  group group-name 
    authentication-key [authentication-key | hash-key [hash | hash2| custom]
    authentication-type {none | password | message-digest | message-digest-20}
    check-zero {enable | disable}
    description string
    export policy-name [policy-name ...up to 5 max]]
    import policy-name [policy-name ...up to 5 max]]
    message-size number 
    metric-in metric
    metric-out metric
    preference number
    receive {both | none | version-1 | version-2}
    send {broadcast | multicast | none | version-1}
    no shutdown
    split-horizon {enable | disable}
    timers update timeout flush

    neighbor ip-int-name 
      authentication-key [authentication-key | hash-key [hash | hash2| custom]
      authentication-type {none | password | message-digest | message-digest-20}
      check-zero {enable | disable}
      description string
      export policy-name [policy-name ...up to 5 max]]
      import policy-name [policy-name ...up to 5 max]]
      message-size number 
      metric-in metric
      metric-out metric
      preference number
      receive {both | none | version-1 | version-2}
      send {broadcast | multicast | none | version-1}
      split-horizon {enable | disable}
      timers update timeout flush
      no shutdown

After the RIP protocol instance is created, the no shutdown command is not required because RIP is administratively enabled upon creation. To enable RIP on a router, at least one group and one neighbor must be configured. There are no default groups or neighbors. Each group and neighbor must be explicitly configured.

Use the following CLI syntax to configure global-level RIP parameters.

CLI syntax

config>router
  rip
    authentication-key [authentication-key | hash-key [hash | hash2| custom]
    authentication-type {password | message-digest}
    check-zero {enable | disable}
    export policy-name [policy-name ...up to 5 max]
    import policy-name [policy-name ...up to 5 max]
    message-size number
    metric-in metric
    metric-out metric
    preference number
    receive {both | none | version-1 | version-2}
    send {broadcast | multicast | none | version-1 | both}
    no shutdown
    split-horizon {enable | disable}
    timers update timeout flush

The following example displays global RIP configuration command usage.

Example

config>router# rip
config>router>rip# authentication-type password
config>router>rip# authentication-key test123
config>router>rip# receive both
config>router>rip# split-horizon enable
config>router>rip# timers 300 600 600
config>router>rip>group# exit

The following example displays the RIP group configuration:

ALA-A>config>router>rip# info
----------------------------------------------
            authentication-type simple
            authentication-key "ac1865lvz1d" hash
            timers 300 600 600
----------------------------------------------
ALA-A>config>router>rip#

A group is a collection of related RIP peers. The group name should be a descriptive name for the group. Follow your group, name, and ID naming conventions for consistency and to help when troubleshooting faults.

All parameters configured for a group are applied to the group and are inherited by each peer (neighbor), but a group parameter can be overridden on a specific neighbor-level basis. Use the following CLI syntax to configure a group.

CLI syntax

config>router# rip
  group group-name
    authentication-key[authentication-key|hash-key [hash|hash2|custom]
    authentication-type {password|message-digest}
    check-zero {enable|disable}
    description string
    export policy-name [policy-name …]
    import policy-name [policy-name …]
    message-size number
    metric-in metric
    metric-out metric
    preference number
    receive {both|none|version-1|version-2}
      send {broadcast|multicast|none|version-1|both}
      no shutdown
      split-horizon {enable|disable}
      timers update timeout flush

The following example displays group configuration command usage.

Example

config>router# rip
config>router>rip# group headquarters
config>router>rip>group$ description "Mt. View"
config>router>rip>group# no shutdown

The following example displays the RIP group configuration:

ALA-A>config>router>rip# info
----------------------------------------------
            authentication-type simple
            authentication-key "ac1865lvz1d" hash
            timers 300 600 600
            group "headquarters"
                description "Mt. View"
            exit
----------------------------------------------
ALA-A>config>router>rip#

After you create a group name and assign options, add neighbor interfaces within the same group. All parameters configured for the peer group level are applied to each neighbor, but a group parameter can be overridden on a specific neighbor basis.

Use the following CLI syntax to add a neighbor to a group and define options that override the same group-level command value.

CLI syntax

config>router# rip
  group group-name
    neighbor ip-int-name
      authentication-key [authentication-key|hash-key [hash|hash2|custom]
      authentication-type {password|message-digest}
      check-zero {enable|disable}
      description string
      export policy-name [policy-name …]
      import policy-name [policy-name …]
      message-size number
      metric-in metric
      metric-out metric
      preference number
      receive {both|none|version-1|version-2}
      send {broadcast|multicast|none|version-1}
      split-horizon {enable|disable}
      timers update timeout flush
      no shutdown

The following example displays neighbor configuration command usage.

Example

config>router# rip
config>router>rip# group headquarters1
config>router>rip>group# neighbor ferguson-274
config>router>rip>group>neighbor$ preference 255
config>router>rip>group>neighbor# send both
config>router>rip>group>neighbor# split-horizon enable
config>router>rip>group>neighbor# message-size 255

The following example displays the neighbor configured in group ‟headquarters”.

ALA-A>config>router>rip>group>neighbor# info
----------------------------------------------
                    message-size 255
                    preference 255
                    split-horizon enable
                    no timers
----------------------------------------------
ALA-A>config>router>rip>group>neighbor#