Configuring Juniper Networks Routers

Module 4: Routing Information Protocol

Copyright © 2006, Juniper Networks, Inc. CJNR-M-7.a.7.6.1

 Module Objectives
 After successfully completing this module, you will be
able to:
– Describe the basic operation of RIP
– Configure RIP
– Monitor and troubleshoot the operation of RIP

Copyright © 2006, Juniper Networks, Inc.

 Routing Information Protocol
 Where we are going…
– What is RIP?
– RIP characteristics
– RIP message types
– RIPv2 features
– RIP limitations
– JUNOS software RIP support
– Configuring RIP—incoming
– Configuring RIP— outgoing
– Useful commands

Copyright © 2006, Juniper Networks, Inc.

 What Is RIP?
 RIP is an IGP
– Used within an autonomous system
 Two versions:
– RIPv1 (RFC 1058)
– RIPv2 (RFC 2453)

Copyright © 2006, Juniper Networks, Inc.

 RIP Characteristics
 Distance-vector routing protocol
 Hop count is used as the metric for path selection,
based on Bellman-Ford distance-vector routing
algorithm
– Maximum allowable hop count is 15
 Routing updates are broadcast every 30 seconds

Copyright © 2006, Juniper Networks, Inc.

 RIP Message Types
 Two message types
– Request message
 Asks neighbors to send routes
– Response message
 Carries route updates
 Advertises 25 routes per update
 Router decides how to handle routes in update
– Add, modify, or delete

Copyright © 2006, Juniper Networks, Inc.

 RIPv2 Features
 Backward compatible with RIPv1
 Authentication on a per-message basis
– Simple password or MD5 authentication
 Multicast updates
– Multicast address of 224.0.0.9
– You can enable broadcast
 Update includes prefix length
– Allows VLSM
 Update includes next-hop address
– Similar function as ICMP redirect
 RIPv1/v2 interoperability

Copyright © 2006, Juniper Networks, Inc.

 RIP Limitations
 Limitations:
– Maximum network diameter = 15
– Regular updates include entire routing table approximately
every 30 seconds
– Poison reverse increases size of routing updates
– Count to infinity slows route-loop prevention
– Metrics only involve hop count
– Broadcasts between neighbors (RIPv1 only)
– Classful routing means no prefix length carried in route
updates (RIPv1 only)
– No authentication mechanism (RIPv1 only)
– Poor convergence

Copyright © 2006, Juniper Networks, Inc.

 JUNOS Software RIP Support
 JUNOS software supports:
– RIPv1
– RIPv2
– Peer groups
 Neighbors defined in peer group
– Default setting of no route export
 Need export policy to readvertise RIP or to advertise other routes
– Default preference of 100
– Modification of metrics in or out

Copyright © 2006, Juniper Networks, Inc.

 Configuring RIP—Incoming
Minimum RIP configuration
protocols {
rip {
group group-name {
neighbor interface-name;
}
}
}

Copyright © 2006, Juniper Networks, Inc.

 Configuring RIP Advertisements
 Determine which routes to advertise and create export
policy
policy-options {
policy-statement statics-to-rip {
from protocol static;
then accept;
}
}

 Apply export policy to RIP neighbors

protocols {
rip {
group rip-neighbors {
export statics-to-rip;
neighbor fe-0/0/0.0;
neighbor fe-0/0/1.0;
}
}
}

Copyright © 2006, Juniper Networks, Inc.

 Monitoring RIP (1 of 4)
 Show the state of your RIP interfaces using the show
rip neighbor command
Source Destination Send Receive In
Neighbor State Address Address Mode Mode Met
-------- ----- ------- ----------- ---- ------- ---
fe-0/0/1.0 Up 10.0.31.2 224.0.0.9 mcast both 1
fe-0/0/0.0 Up 10.0.13.2 224.0.0.9 mcast both 1

 Show all routes learned via RIP using the show route
protocol rip command
inet.0: 15 destinations, 15 routes (15 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.16.0.0/16 [RIP/100] 00:07:02, metric 2

> to 10.0.13.1 via fe-0/0/0.0
192.168.8.1/32 *[RIP/100] 00:07:02, metric 2
> to 10.0.13.1 via fe-0/0/0.0
224.0.0.9/32 *[RIP/100] 00:11:25, metric 1
…

Copyright © 2006, Juniper Networks, Inc.

 Monitoring RIP (2 of 4)
 Display routes that a RIP interface sends using the show
route advertising-protocol rip neighbor
command
– neighbor is the IP address of local RIP interface
– Watch for poison reverse behavior when making policy changes!

user@host> show route advertising-protocol rip 10.0.21.1

inet.0: 12 destinations, 12 routes (11 active, 1 holddown, 0

hidden)
+ = Active Route, - = Last Active, * = Both

3.0.0.0/8 *[Static/5] 00:10:56

Reject
30.0.0.0/16 *[Static/5] 00:12:20
Reject

Copyright © 2006, Juniper Networks, Inc.

 Monitoring RIP (3 of 4)
 Show routes that a RIP interface receives using
the show route receive-protocol rip
neighbor command
– neighbor is the IP address of remote RIP neighbor
user@host> show route receive-protocol rip 10.100.3.2

inet.0: 17 destinations, 18 routes (17 active, 0

holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.20.4.0/24 *[RIP/100] 00:01:01, metric 2

> to 10.100.3.2 via fe-0/0/0.0
192.168.28.0/24 *[RIP/100] 00:01:01, metric 2
> to 10.100.3.2 via fe-0/0/0.0

Copyright © 2006, Juniper Networks, Inc.

 Monitoring RIP (4 of 4)
Use the show rip statistics command to display
various statistics
user@host> show rip statistics

RIP info: port 520; update interval 30s; holddown 180s; timeout 120s.
rts learned rts held down rqsts dropped resps dropped
1 1 0 0

fe-0/0/0.0: 1 routes learned; 3 routes advertised

Counter Total Last 5 min Last minute
------- ----------- ----------- -----------
Updates Sent 28 11 2
Triggered Updates Sent 1 0 0
Responses Sent 0 0 0
Bad Messages 0 0 0
RIPv1 Updates Received 0 0 0
RIPv1 Bad Route Entries 0 0 0
RIPv1 Updates Ignored 0 0 0
RIPv2 Updates Received 14 11 3
RIPv2 Bad Route Entries 0 0 0
RIPv2 Updates Ignored 0 0 0
Authentication Failures 0 0 0
RIP Requests Received 0 0 0
RIP Requests Ignored 0 0 0

Copyright © 2006, Juniper Networks, Inc.

 Tracing RIP
 A typical RIP tracing configuration:

[edit protocols rip]

user@host# show
traceoptions {
file rip-trace;
flag error detail;
flag update detail;
}

– Monitor the resulting rip-trace log file using monitor

start log-file-name or the show log log-file-name
commands

Copyright © 2006, Juniper Networks, Inc.

 Review Questions
1. By default, what RIP version does JUNOS software
use?
2. Do you need export policy to have RIP export RIP
routes learned from other neighbors?
3. Which version of RIP supports VLSM?
4. What command would you use to verify that your
router is sending and receiving RIP updates?

Copyright © 2006, Juniper Networks, Inc.

 Lab 4: RIP Configuration

Lab Objective:

Configure a Juniper Networks M-series router

to run RIP, and monitor its operation

Copyright © 2006, Juniper Networks, Inc.