[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring a RIP Network with a Configuration Editor

To configure the Juniper Networks device as a node in a RIP network, you must perform the following task marked (Required).

For information about using the J-Web and CLI configuration editors, see the J-Web Interface User Guide and the JUNOS CLI User Guide.

Configuring a Basic RIP Network (Required)

To use RIP on the device, you must configure RIP on all the RIP interfaces within a network like the one shown in Figure 73.

Figure 73: Typical RIP Network Topology

Image g015025.gif

By default, RIP does not advertise the subnets that are directly connected through the device's interfaces. For traffic to pass through a RIP network, you must create a routing policy to export these routes. Advertising only the direct routes propagates the routes to the immediately adjacent RIP-enabled router only. To propagate all routes through the entire RIP network, you must configure the routing policy to export the routes learned through RIP.

To configure a RIP network like the one in Figure 73, with a routing policy, perform these steps on each device in the network:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 154.
  3. If you are finished configuring the router, commit the configuration.

    After you add the appropriate interfaces to the RIP group, RIP begins sending routing information. No additional configuration is required to enable RIP traffic on the network.

  4. Go on to one of the following procedures:

Table 154: Configuring a RIP Network

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Rip level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Configure or Edit.
  3. Next to Rip, click Configure or Edit.

From the [edit] hierarchy level, enter

edit protocols rip

Create the RIP group alpha1.

  1. Next to Group, click Add new entry.
  2. In the Group name box, type alpha1.
  1. Create the RIP group alpha1, and add an interface:

    set group alpha1 neighbor ge-0/0/0.0

  2. Repeat Step 1 for each interface on this device that you are adding to the RIP group. Only one interface is required.

Add interfaces to the RIP group alpha1.

For information about interface names, see Network Interface Naming.

  1. Next to Neighbor, click Add new entry.
  2. In the Neighbor name box, type the name of an interface on the device—for example, ge-0/0/0.0—and click OK.
  3. Repeat Step 2 for each interface on this device that you are adding to the RIP group. Only one interface is required.

Configure a routing policy to advertise directly connected routes.

  1. On the main Configuration page next to Policy options, click Configure or Edit.
  2. Next to Policy statement, click Add new entry.
  3. In the Policy name box, type the name of the policy statement—for example, advertise-rip-routes.
  4. Next to Term, click Add new entry.
  5. In the Term name box, type the name of the policy statement—for example, from-direct.
  6. Next to From, click Configure.
  7. Next to Protocol, click Add new entry.
  8. From the Value list, select Direct.
  9. Click OK until you return to the Policy statement page.
  10. Next to Then, click Configure.
  11. From the Accept reject list, select Accept.
  12. Click OK.
  1. From the [edit] hierarchy level, enter

    edit policy-options

  2. Set the match condition to match on direct routes:

    set policy-statement advertise-rip-routes term from-direct from protocol direct

  3. Set the match action to accept these routes:

    set policy-statement advertise-rip-routes term from-direct then accept

Configure the previous routing policy to advertise routes learned from RIP.

  1. On the main Configuration page next to Policy options, click Configure or Edit.
  2. Next to Policy statement, click advertise-rip-routes.
  3. Next to Term, click Add new entry.
  4. In the Term name box, type the name of the policy statement—for example, from-rip.
  5. Next to From, click Configure.
  6. Next to Protocol, click Add new entry.
  7. From the Value list, select rip.
  8. Click OK until you return to the Policy statement page.
  9. Next to Then, click Configure.
  10. From the Accept reject list, select Accept.
  11. Click OK.
  1. From the [edit] hierarchy level, enter

    edit policy-options

  2. Set the match condition to match on direct routes:

    set policy-statement advertise-rip-routes term from-rip from protocol rip

  3. Set the match action to accept these routes:

    set policy-statement advertise-rip-routes term from-rip then accept

Controlling Traffic in a RIP Network (Optional)

There are two primary means for controlling traffic in a RIP network: the incoming metric and the outgoing metric. To modify these attributes, see the following sections:

Controlling Traffic with the Incoming Metric

Depending on the RIP network topology and the links between nodes in the network, you might want to control traffic flow through the network to maximize flow across higher-bandwidth links. Figure 74 shows a network with alternate routes between Routers A and D.

Figure 74: Controlling Traffic in a RIP Network with the Incoming Metric

Image g015026.gif

In this example, routes to Router D are received by Router A across both of its RIP-enabled interfaces. Because the route through Router B and the route through Router C have the same number of hops, both routes are imported into the forwarding table. However, because the T3 link from Router B to Router D has a higher bandwidth than the T1 link from Router C to Router D, you want traffic to flow from A through B to D.

To force this flow, you can modify the route metrics as they are imported into Router A's routing table. By setting the incoming metric on the interface from Router A to Router C, you modify the metric on all routes received through that interface. Setting the incoming route metric on Router A changes only the routes in Router A's routing table, and affects only how Router A sends traffic to Router D. Router D's route selection is based on its own routing table, which, by default, includes no adjusted metric values.

In the example, Router C receives a route advertisement from Router D and readvertises the route to Router A. When Router A receives the route, it applies the incoming metric on the interface. Instead of incrementing the metric by 1 (the default), Router A increments it by 3 (the configured incoming metric), giving the route from Router A to Router D through Router C a total path metric of 4. Because the route through Router B has a metric of 2, it becomes the preferred route for all traffic from Router A to Router D.

To modify the incoming metric on all routes learned on the link between Router A and Router C and force traffic through Router B:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 155.
  3. If you are finished configuring the router, commit the configuration.
  4. Go on to one of the following procedures:

Table 155: Modifying the Incoming Metric

Task

J-Web Configuration Editor

CLI Configuration Editor

In the configuration hierarchy, navigate to the level of an interface in the alpha1 RIP group.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Edit.
  3. Next to Rip, click Edit.
  4. Under Group name, click alpha1.
  5. Under Neighbor name, click the interface name—for example, ge-0/0/0.0.

From the [edit] hierarchy level, enter

edit protocols rip group alpha1 neighbor ge-0/0/0

Increase the incoming metric to 3.

In the Metric in box, type 3, and click OK.

Set the incoming metric to 3:

set metric-in 3

Controlling Traffic with the Outgoing Metric

If an exported route was learned from a member of the same RIP group, the metric associated with that route is the normal RIP metric. For example, a RIP route with a metric of 5 learned from a neighbor configured with an incoming metric of 2 is advertised with a combined metric of 7 when advertised to neighbors in the same group. However, if this route was learned from a RIP neighbor in a different group or from a different protocol, the route is advertised with the metric value configured in the outgoing metric for that group. Figure 75 shows a network with alternate routes between Routers A and D.

Figure 75: Controlling Traffic in a RIP Network with the Outgoing Metric

Image g015027.gif

In this example, each route from Router A to Router D has two hops. However, because the link from Router A to Router B in RIP group Beta 1 has a higher bandwidth than the link from Router A to Router C in RIP group Alpha 1, you want traffic from Router D to Router A to flow through Router B. To control the way Router D sends traffic to Router A, you can alter the routes that Router D receives by configuring the outgoing metric on Router A's interfaces in the Alpha 1 RIP group.

If the outgoing metric for the Alpha 1 RIP group—the A-to-C link—is changed to 3, Router D calculates the total path metric from to A through C as 4. In contrast, the unchanged default total path metric to A through B in the Beta 1 RIP group is 2. The fact that Router A's interfaces belong to two different RIP groups allows you to configure two different outgoing metrics on its interfaces, because you configure path metrics at the group level.

By configuring the incoming metric, you control the way Router A sends traffic to Router D. By configuring the outgoing metric on the same router, you control the way Router D sends traffic to Router A.

To modify the outgoing metric on Router A and force traffic through Router B:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 156.
  3. If you are finished configuring the router, commit the configuration.
  4. Go on to one of the following procedures:

Table 156: Modifying the Outgoing Metric

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the alpha1 level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Edit.
  3. Next to Rip, click Edit.
  4. Under Group name, click alpha1.

From the [edit] hierarchy level, enter

edit protocols rip group alpha1

Increase the outgoing metric to 3.

In the Metric out box, type 3, and click OK.

Set the outgoing metric to 3:

set metric-out 3

Enabling Authentication for RIP Exchanges (Optional)

All RIPv2 protocol exchanges can be authenticated to guarantee that only trusted routers participate in the AS's routing. By default, this authentication is disabled. Authentication requires all routers within the RIP network or subnetwork to have the same authentication type and key (password) configured.

You can enable RIP authentication exchanges by either of the following methods:

Enabling Authentication with Plain-Text Passwords

To configure authentication that requires a plain-text password to be included in the transmitted packet, enable simple authentication by performing these steps on all RIP devices in the network:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 157.
  3. If you are finished configuring the router, commit the configuration.
  4. To check the configuration, see Verifying the RIP Configuration.

Table 157: Configuring Simple RIP Authentication

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to Rip level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Edit.
  3. Next to Rip, click Edit.

From the [edit] hierarchy level, enter

edit protocols rip

Set the authentication type to simple.

From the Authentication type list, select simple.

Set the authentication type to simple:

set authentication-type simple

Set the authentication key to a simple-text password.

The password can be from 1 through 16 contiguous characters long and can include any ASCII strings.

In the Authentication key box, type a simple-text password, and click OK.

Set the authentication key to a simple-text password:

set authentication-key password

Enabling Authentication with MD5 Authentication

To configure authentication that requires an MD5 password to be included in the transmitted packet, enable MD5 authentication by performing these steps on all RIP devices in the network:

  1. Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 158.
  3. If you are finished configuring the router, commit the configuration.
  4. To check the configuration, see Verifying the RIP Configuration.

Table 158: Configuring MD5 RIP Authentication

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to Rip level in the configuration hierarchy.

  1. In the J-Web interface, select Configure>CLI Tools>Point and Click CLI.
  2. Next to Protocols, click Edit.
  3. Next to Rip, click Edit.

From the [edit] hierarchy level, enter

edit protocols rip

Set the authentication type to MD5.

From the Authentication type list, select md5.

Set the authentication type to md5:

set authentication-type md5

Set the MD5 authentication key (password).

The key can be from 1 through 16 contiguous characters long and can include any ASCII strings.

In the Authentication key box, type an MD5 authentication key, and click OK.

Set the MD5 authentication key:

set authentication-key password

[Contents] [Prev] [Next] [Index] [Report an Error]


[an error occurred while processing this directive]