Relationship Between address and network Commands

If you use the network command to configure a RIP network, use the ip rip commands to configure the RIP attributes for that network. Do not use the address commands.

If you use the address command to configure a RIP network, use the address commands to configure the RIP attributes for that network. Do not use the ip rip commands.

Note: The network and ip rip commands are maintained for industry compatibility. You can configure all your RIP interfaces with the address commands. You cannot configure unnumbered interfaces with the network and ip rip commands.

address

• Use to configure RIP to run on the interface specified by the IP address or on an unnumbered interface. Use the address commands to configure RIP attributes on the network.
• Configures RIP with the default values: Send version is RIPv1, receive version is RIPv1 and RIPv2, authentication is not enabled.
• Example

  host1(config-router)#address 10.2.1.1

• Use the no version to delete the RIP interface.
• See address

address authentication key

• Use to specify either the simple password for text authentication or the encryption/decryption key for MD5 authentication. The key is a string of up to 16 alphanumeric characters and can be mixed uppercase and lowercase.
• You can specify whether the key is entered in unencrypted or encrypted format. If you do not specify which, the string is assumed to be unencrypted.
• Example

  host1(config-router)#address 10.2.1.1 authentication key ke6G72mV

• Use the no version to clear all authentication keys.
• See address authentication key

address authentication mode

• Use to specify the authentication mode.
• Specify text to send a simple text password to neighbors. If a neighbor does not have the same password, requests and updates from this router are rejected.
• Specify md5 keyID to send an MD5 hash to neighbors. Neighbors must share the MD5 key to decrypt the message and encrypt the response.
• Example

  host1(config-router)#address 10.2.1.1 authentication mode text

• Use the no version to remove authentication from all RIP interfaces.
• See address authentication mode

address receive version

• Use to restrict the RIP version that the router can receive on an interface. The default is to receive both RIPv1 and RIPv2.
• Example

  host1(config-router)#address 10.2.1.1 receive version 1

• Use the no version to restore the default value, 1 2.
• See address receive version

address send version

• Use to restrict the RIP version that the router can send on an interface. The default is to send only RIPv1.
• Example

  host1(config-router)#address 10.2.1.1 send version 2

• Use the no version to restore the default value, 1.
• See address send version

clear ip rip redistribution

• Use to clear all the routes that have previously been redistributed into RIP.
• Example

  host1#clear ip rip redistribution

• There is no no version.
• See clear ip rip redistribution

debounce-time

• Use to control the interval RIP waits before bringing back up an interface that was brought down by some event.
• The interval can be in the range 0–60 seconds.
• Example

  host1(config-router)#debounce-time 30

• Use the no version to restore the default value, 10 seconds.
• See debounce-time

default-information originate

• Use to enable RIP to advertise a default route (0.0.0.0/0) if the default route exists in the IP routing table.
• If the default route does not exist, you must configure it using the ip route command, or specify the always keyword. The always keyword causes RIP to always advertise the default route, and creates it if it is not present in the IP routing table.
• Example

  host1(config-router)#default-information originate

• Use the no version to disable advertisement of the default route.
• See default-information originate

default-metric

• Use to configure RIP to apply this metric for redistributed routes on all subsequently created interfaces.
• Configuring a default metric lowers the priority of the routes.
• Use a metric in the range 1 – 16.
• Example

  host1(config-router)#default-metric 5

• Use the no version to restore the default value, 0.
• See default-metric

disable

• Use to disable RIP processing.
• Example

  host1(config-router)#disable

• Use the no version to enable RIP processing.
• See disable

disable-dynamic-redistribute

• Use to halt the dynamic redistribution of routes that are initiated by changes to a route map.
• Dynamic redistribution is enabled by default.
• Example

  host1(config-router)#disable-dynamic-redistribute

• Use the no version to reenable dynamic redistribution.
• See disable-dynamic-redistribute

distance

• Use to set the administrative distances for routes.
• Example

  host1(config-router)#distance 150

• Use the no version to restore the default value, 120.
• See distance

distribute-list

• Use to apply a specific access list to incoming or outgoing RIP route updates.
• An IP access list acts as a filter. Refer to access-list in the JUNOSe Command Reference Guide for more information.
• Example

  host1(config-router)#distribute-list 5 incoming

• Use the no version to stop application of the distribute list.
• See distribute-list

interface-event-disable

• Use to configure RIP to purge the routing table for interfaces that were brought down by some event.
• Example

  host1(config-router)#interface-event-disable

• Use the no version to restore the default condition, wherein RIP does not automatically purge the routing table for down interfaces.
• See interface-event-disable

ip rip

• Use to configure RIP on the network interface specified with the network command.
• Configures RIP with the default values: Send version is RIPv1, receive version is RIPv1 and RIPv2, authentication is not enabled.
• Example

  host1(config-if)#ip rip

• Use the no version to delete the RIP interface.
• See ip rip

ip rip authentication key

• Use to specify either the simple password for text authentication or the encryption/decryption key for MD5 authentication. The key is a string of up to 16 alphanumeric characters and can be mixed uppercase and lowercase.
• You can specify whether the key is entered in unencrypted or encrypted format. If you do not specify which, the string is assumed to be unencrypted.
• Example

  host1(config-if)#ip rip authentication key ke6G72mV

• Use the no version to clear all authentication keys.
• See ip rip authentication key

ip rip authentication mode

• Use to specify the authentication mode.
• Specify text to send a simple text password to neighbors. If a neighbor does not have the same password, requests and updates from this router are rejected.
• Specify md5 keyID to send an MD5 hash to neighbors. Neighbors must share the MD5 key to decrypt the message and encrypt the response.
• Example

  host1(config-if)#ip rip authentication mode text

• Use the no version to remove authentication from all RIP interfaces.
• See ip rip authentication mode

ip rip receive version

• Use to restrict the RIP version that the router can receive on an interface. The default is both RIPv1 and RIPv2.
• Example

  host1(config-if)#ip rip receive version 1

• Use the no version to restore the default value, 1 2.
• See ip rip receive version

ip rip send version

• Use to restrict the RIP version that the router can send on an interface. The default is RIPv1.
• Example

  host1(config-if)#ip rip send version 2

• Use the no version to restore the default value, 1.
• See ip rip send version

ip split-horizon

• Use to configure the split horizon feature and poison reverse features for the interface. Enabled by default, split horizon prevents the RIP router from advertising routes from the originating interface.
• Poison reverse routing updates are disabled by default; when enabled, they set the metric for routes originating on the interface to infinity, thus explicitly advertising that the network is not reachable. This helps to prevent routing loops.
• In most configurations, you will want to accept the default condition.
• Example

  host1(config-if)#no ip split-horizon

• Use the no version to disable split horizon and enable poison reverse routing updates.
• See ip split-horizon

ip summary-address

• Use to specify an IP address and network mask to identify which routes to summarize.
• You can optionally specify a metric associated with the summary address. The default metric is 1.
• Example

  host1(config-router)#ip summary-address 4.4.0.0 255.255.0.0 5

  host1(config-router)#ip summary-address 4.3.0.0 255.255.0.0 6

• Use the no version to stop summarization for the specified routes.
• See ip summary-address

match-set summary prefix-tree

• Use to specify a prefix tree that summarizes routes for a particular route map.
• Use the ip prefix-tree command to set the conditions of the prefix tree, including which routes to summarize and how many bits of the network address to preserve.
• Example

  host1(config-route-map)#match-set summary prefix-tree boston

• Use the no version to disable the use of the prefix tree by the route map.
• See match-set summary prefix-tree

maximum-paths

• Use to control the maximum number of parallel routes that RIP can support.
• RIP installs multiple equal-cost paths to a given destination only if each has a different next hop.
• The maximum number of routes can be in the range 1–16.
• Example

  host1(config-router)#maximum-paths 2

• Use the no version to restore the default value, 4.
• See maximum-paths

neighbor

• Use to specify a RIP neighbor to which the router sends unicast messages.
• You must also use the passive-interface command to specify the interface as passive, thereby restricting the interface to unicast RIP messages.
• Example

  host1(config-router)#neighbor 10.10.21.100

• Use the no version to remove the neighbor.
• See neighbor

network

• Use to associate a network with a RIP routing process. Use the ip rip commands to configure RIP attributes on the network.
• You supply a network mask to the new address so that RIP runs on that specific network.
• If you do not specify an interface’s network, the network is not advertised in any RIP updates.
• You can specify either the standard subnet mask or the inverse subnet mask.
• Example 1—standard subnet mask

  host1(config-router)#network 10.2.1.0 255.255.255.0

• Example 2—inverse subnet mask

  host1(config-router)#network 10.2.1.0 0.0.0.255

• Use the no version to disable RIP on the specified interface.
• See network

passive-interface

• Use to disable the transmission of multicast RIP messages on the interface.
• RIP messages are unicast to a RIP neighbor on the interface if the interface is present in the IP routing table as the next-hop interface to the configured neighbor.
• Example

  host1(config-router)#passive-interface atm atm 2/0.16

• Use the no version to reenable the transmission of RIP multicast messages on the specified interface.
• See passive-interface

redistribute

• Use to redistribute information from a routing domain other than RIP into the RIP domain.
• Specify the source protocol from which routes are being redistributed. It can be one of the following keywords: bgp, isis, ospf, static [ip], and connected. Use the static keyword to redistribute IP static routes; optionally add the ip keyword when redistributing into IS-IS. The keyword connected refers to routes that are established automatically by virtue of having enabled IP on an interface. For routing protocols such as OSPF and IS-IS, these routes will be redistributed as external to the AS.
• Use the route-map keyword to interrogate the route map to filter the importation of routes from the source routing protocol to the current routing protocol. If you do not specify the route-map option, all routes are redistributed. If you specify the route-map option, but no route map tags are listed, no routes will be imported.
• Use to redistribute routes from RIP into other non-RIP routing domains.
• Example 1

  host1(config)#router rip 5

  host1(config-router)#redistribute bgp 100 route-map 4

• Example 2

  host1(config)#router bgp 100

  host1(config-router)#redistribute rip 5

• Use the no version to disable redistribution.
• See redistribute.

route-map

• Use to specify a route map for RIP.
• Example

  host1(config)#router rip

  host1(config-router)#route-map 4

• Use the no version to delete the route map. If you do not specify an interface, it removes the global route map if it exists.
• See route-map

router rip

• Use to enable RIP routing protocol and specify a RIP process for IP, or to access Router Configuration mode.
• Specify only one RIP process per router.
• Example

  host1(config)#router rip

• Use the no version to delete the RIP process and removes the configuration from your router.
• See router rip

send-more-specific-routes-disable

• Use to configure RIP to send a less-specific route in preference to a more-specific route if the less-specific route has a metric.
• Example

  host1(config-router)#send-more-specific-routes-disable

• Use the no version to restore the default condition, wherein RIP always sends a more-specific route in preference to a less-specific route, even if the less-specific route has a metric.
• See send-more-specific-routes-disable

table-map

• Use to apply a policy to modify distance, metric, or tag values of RIP routes about to be added to the IP routing table.
• The new route map is applied to all routes currently in and those subsequently placed in the forwarding table. Previously redistributed routes are redistributed with the changes caused by the route map.
• To remove from the forwarding table any old routes that are now disallowed by the specified route map, you must refresh the IP routing table with the clear ip routes * command.
• Example

  host1(config)#route-map dist1 permit 5

  host1(config-route-map)#match community boston42

  host1(config-route-map)#set distance 33

  host1(config-route-map)#exit

  host1(config)#router rip 100

  host1(config-router)#table-map dist1

  host1(config-router)#exit

  host1(config)#exit

  host1#clear ip routes *

• Use the no version to halt application of the route map.
• See table-map

timers

• Use to configure RIP timers.
• The router supports the following RIP timers:
  • update—Interval in seconds at which routing updates are sent. The default is 30 seconds.
  • invalid—Interval in seconds after which a route is declared invalid (null). Set this value to at least three times the update value. The default is 180 seconds.
  • holddown—Interval in seconds during which routing information about better paths is suppressed. Set this value to at least three times the update value. The default is 120 seconds.
  • flush—Interval in seconds that must pass before a route is removed from the routing table. Set this value greater than the invalid value. The default is 300 seconds.
• Example

  host1(config-router)#timers update 20

  host1(config-router)#timers invalid 60

  host1(config-router)#timers holddown 60

  host1(config-router)#timers flush 90

• Use the no version to restore the default values, 30 180 120 300.
• See timers

triggered-update-disable

• Use to prevent RIP from sending triggered routing updates.
• Example

  host1(config-router)#triggered-update-disable

• Use the no version to restore the default condition, wherein RIP does sends triggered routing updates.
• See triggered-update-disable

version

• Use to specify the global RIP version. The default is RIPv1.
• To change the RIP version on a specific interface, use the ip rip receive version and the ip rip send version commands, or the address receive version and address send version commands.
• Example

  host1(config-router)#version 2

• Use the no version to revert to the default value, 1.
• See version

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.