{"id":56,"date":"2014-06-02T12:10:55","date_gmt":"2014-06-02T12:10:55","guid":{"rendered":"http:\/\/feralpacket.org\/?p=56"},"modified":"2015-01-03T11:20:55","modified_gmt":"2015-01-03T11:20:55","slug":"v5-written-and-lab-rip-notes","status":"publish","type":"post","link":"https:\/\/feralpacket.org\/?p=56","title":{"rendered":"v5 Written and Lab: RIP Notes"},"content":{"rendered":"

v5 Written:
\n3.4 RIP (v2 and v6)
\n3.4.a Implement and troubleshoot RIPv2
\n3.4.b Describe RIPv6 (RIPng)<\/code><\/p>\n

v5 Lab:
\n2.4 RIPv2
\n2.4.a Implement and troubleshoot RIPv2<\/p>\n

http:\/\/docwiki.cisco.com\/wiki\/Routing_Information_Protocol<\/p>\n

http:\/\/www.cisco.com\/c\/en\/us\/tech\/ip\/routing-information-protocol-rip\/index.html<\/p>\n

http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/ios-xml\/ios\/iproute_rip\/configuration\/15-mt\/irr-15-<\/p>\n

mt-book.html<\/p>\n

http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/lan\/catalyst3750x_3560x\/software\/release\/15<\/p>\n

-0_2_se\/configuration\/guide\/3750x_cg\/swiprout.html#wp1028241<\/p>\n

http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/ios-xml\/ios\/iproute_rip\/command\/irr-cr-book\/irr-cr-<\/p>\n

rip.html<\/p>\n

Routing TCP \/ IP Volume I – Chapter 5: Routing Information Protocol (RIP)
\nRouting TCP \/ IP Volume I – Chapter 6: RIPv2, RIPng, and Classless Routing<\/p>\n

Troubleshooting IP Routing Protocols – Chapter 2: Understanding Routing Information<\/p>\n

Protocol (RIP)
\nTroubleshooting IP Routing Protocols – Chapter 3: Troubleshooting RIP<\/p>\n

IP Routing Fundamentals – Chapter 8: Routing Information Protocol
\nIP Routing Fundamentals – Chapter 9: Routing Information Protocol Version 2<\/p>\n

Troubleshooting IP Routing Protocols – Chapter 2: Routing Information Protocol (RIP)
\nTroubleshooting IP Routing Protocols – Chapter 3: Troubleshooting RIP<\/p>\n

INE R%S Workbook I, Section 4 – RIP<\/p>\n

Router-Bits Handbook – Chapter 5: RIP<\/p>\n

INE Advanced Technologies videos:<\/p>\n

43 RIP Overview, RIP Versions, RIP Auto-Summary 0h 48m
\n44 RIP Split-Horizon, RIP Timers 0h 22m
\n45 RIP Broadcast Updates, IP Directed Broadcast, IP Broadcast-Address, Smurf
\nAttacks, Fraggle Attacks 0h 16m
\n46 RIP Unicast Updates 0h 03m
\n47 RIP Offset-List 0h 18m
\n48 RIP Authentication 0h 11m
\n49 RIP Summarization 0h 10m
\n50 Prefix-Lists, RIP Distribute-List Filtering, RIP Administrative Distance
\nFiltering 0h 48m
\n51 RIP Default Routing, RIP Conditional Default Routing 0h 18m
\n52 RIP Triggered, RIP Validate Update Source, 0h 12m<\/p>\n

RFCs:<\/p>\n

RFC 1058 – Routing Informaiton Protocol
\nRFC 2082 – RIP-2 MD5 Authentication
\nRFC 2091 – Triggered Extensions to RIP to SUpport Demand Circuits
\nRFC 2453 – RIP Version 2
\nRFC 2080 – RIPng for IPv6
\nRFC 1724 – RIP Version 2 MIB Extension Plain Text Authentication<\/p>\n

RIP Decision Tree:
\n1. Assign internal RIP network
\n– network command without wildcard mask
\n2. Link type
\n– point-to-point
\n– broadcast
\n– non-broadcast (frame-relay)
\n– hub and spoke
\n– check for split-horizon issues
\n3. Determine what interfaces advertise RIP updates
\n– passive-interface default
\n– no passive-interface
\n4. Destination address used
\n– multicast – 224.0.0.10
\n– broadcast – ip rip v2-broadcast
\n– unicast – neighbor statement with passive-interface – sets TTL =2
\n5. Version 2
\n– version 2
\n6. Verify
\n– show ip rip database
\n– debug ip rip
\n– debug ip routing<\/p>\n

Example:<\/p>\n

router rip
\nnetwork 172.16.0.0
\npassive-interface default
\nno passive-interface fa0\/0
\nno auto-summary
\nversion 2<\/p>\n

RIPv2 has no neighbor relationship requirement<\/p>\n

Prerequisites for RIP
\n– “ip routing” configured<\/p>\n

Restriction for RIP
\n– hop count is used as the metric to rate the value of different routes
\n– directly connected network has a metric of zero
\n– an unreachable network has a metric of 16
\n– the limited metric range makes it unsuitable for large networks<\/p>\n

RIPv1 uses broadcast UDP packets to exchange routing information
\n– port 520
\n– sends routing update information every 30 seconds
\n– if an update has not been received in 180 seconds, the routes are marked as unusable
\n– if an update has not been received in 240 seconds, the routes are removed from the<\/p>\n

routing table<\/p>\n

A default network can be received or advertised with RIP<\/p>\n

RIPv2 features
\n– plain text authentication
\n– MD5 authentication
\n– route summarization
\n– classless interdomain routing (CIDR)
\n– variable-length subnet masks (VLSM)<\/p>\n

Routing updates are sent at regular intervals and when the network topology changes<\/p>\n

Routing update
\n– receiving device adds 1 to the metric value and adds the network to the routing table
\n– the IP address of the sender of the routing update is used as next-hop
\n– only the best route to a destination is maintained (the route with the lowest metric)<\/p>\n

By default, devices can receive both RIPv1 and RIPv2 packets
\n– configure the RIP version to override the default<\/p>\n

Authentication in RIP is performed only if a key chain is configured<\/p>\n

RIP is normally a broadcast protocol
\n– can be configured for non-broadcast networks<\/p>\n

To control the interfaces that exchange routing updates, configure passive-interface<\/p>\n

Offset lists can be used to increase the metric of incoming or outgoing routes<\/p>\n

The following timers can be adjusted
\n– Update: the rate routing updates are sent (in seconds) (default 30)
\n– Invalid: the interval of time after which a route is declared invalid (default 180)
\n– Flush: the amount of time that must pass before a route is removed from the routing<\/p>\n

table (default 240)
\n– Hold-down: the amount of time of which routing updates are postponed (default 240)<\/p>\n

VRFs use the system default timers unless the timers-basic command is configured;<\/p>\n

Summary IP address functions:
\n– Summary routes in the RIP database are processed first
\n– Associated child routes are skipped as RIP looks through the database
\n– Auto summary is enabled by default<\/p>\n

RIP is a distance-vector routing algorithm<\/p>\n

Distance-vector algorithms are sometimes referred to as Bellman-Ford or Ford-Fulkerson algorithms<\/p>\n

RIP was the first successful implementation of a distance-vector protocol<\/p>\n

Split-horizon is not disabled by default for interfaces using any of the X.25 encapsulations
\n– for all other encapsulations, split-horizon is enabled by default<\/p>\n

By default, no delay is added between packets in a multipacket RIP update. When a high-
\nend router sends updates to a low-speed router, interpacket delay may be needed;<\/p>\n

router rip
\noutput-delay<\/p>\n

RIP performs a source-validation check. The source IP address of the incoming routing<\/p>\n

updates must be on the same IP network of one of the IP addresses of the receiving<\/p>\n

interface.
\n– It can be disabled, such as when the local IP address is a \/32, but the source is a \/24.<\/p>\n

router rip
\nno validate-update source<\/p>\n

RIPv1 Packet Format<\/p>\n

0………8………16……………….31
\n| Command | Version | Must be zero |
\n——————————————
\n| Address Family | Must be zero |
\n| Identifier | |
\n——————————————
\n| IP Address |
\n——————————————
\n| Must be zero |
\n——————————————
\n| Must be zero |
\n——————————————
\n| Metric |
\n——————————————<\/p>\n

The Address Family Identifier through the Metric can be repeated 25 times in a single<\/p>\n

packets
\n– Max RIP packet size of 512 bytes<\/p>\n

The Address Family Identifier is set to 2 for IP<\/p>\n

RIPv1
\n– Classful
\n– Updates as broadcast<\/p>\n

RIPv2 Packet Format<\/p>\n

0………8………16……………….31
\n| Command | Version | Route Tag |
\n——————————————
\n| Address Family | Must be zero |
\n| Identifier | |
\n——————————————
\n| IP Address |
\n——————————————
\n| Subnet Mask |
\n——————————————
\n| Next Hoop |
\n——————————————
\n| Metric |
\n——————————————<\/p>\n

RIPv2
\n– Classless
\n– Updates as multicast 224.0.0.9<\/p>\n

Example configuration:<\/p>\n

router rip
\nnetwork 10.1.1.0
\nneighbor 10.1.1.2
\noffset-list 98 in 1 fa0\/0
\ntimers-basic 1 2 3 4
\nversion 2
\nno auto-summary
\nno validate-update-source
\noutput-delay 8<\/p>\n

int fa0\/0
\nip rip send version 2
\nip rip receive version 2
\nip rip authentication key-chain rip-md5
\nip rip authentication mode md5
\nip summary-address rip 10.2.0.0 255.255.0.0
\nno ip split-horizon
\nip rip triggered
\nip rip initial-delay 45<\/p>\n

key-chaing rip-md5
\nkey 123456
\nkey-string abcde<\/p>\n

Address Family Timers Example configuration:<\/p>\n

router rip
\nversion 2
\ntimers-basic 5 10 15 20
\nredistribute connected
\nnetwork 5.0.0.0
\ndefault-metric 10
\nno auto-summary
\naddress-family ipv4 vrf abc
\ntimers-basic 10 20 20 30
\nredistribute connected
\nnetwork 10.0.0.0
\nno auto-summary
\nversion 2
\naddress-family ipv4 vrf xyz
\ntimers-basic 20 40 60 80
\nredistribute connected
\nnetwork 20.0.0.0
\ndefault-metric 2
\nno auto-summary
\nversion 2<\/p>\n

Verify RIP
\n– debug ip rip
\n– show ip route rip
\n– show key chain
\n– sh ip protocols | in sec<\/p>\n

RIP for IPV6<\/p>\n

IPv6 RIP functions the same and offers the same benefits as RIP in IPv4
\n– Enhancements include:
\n– support for IPv6 address and prefixes
\n– use of the all-RIP-devices multicast group address FF02::9 as a destination address<\/p>\n

for RIP update messages<\/p>\n

Enabling IPv6 RIP:<\/p>\n

ipv6 unicast-routing
\nint fa0\/0
\nipv6 enable
\nipv6 rip enable<\/p>\n

Optional:<\/p>\n

ipv6 router rip<\/p>\n

Maixmum number of equal-cost routes in IPv6 RIP
\n– default is 4<\/p>\n

ipv6 router rip maximum-paths<\/p>\n

Originate the IPv6 default route (::\/0)<\/p>\n

int fa0\/0
\nipv6 rip default-information {originate|only}<\/p>\n

– originate: originates the default route (::\/0) in addition to all other routes in the updates sent on this interface
\n– only: originates the default route (::\/0) but surpresses all other routes in the updates sent on the interface<\/p>\n

Verify IPv6 RIP:
\n– show ipv6 rip {database|next-hops}
\n– show ipv6 route
\n– debug ipv6 rip
\n– show ipv6 rip<\/p>\n

Nonstop forwarding for IPv6 RIP
\n– Cisco Nonstop Forwarding (NSF) continues forwarding packets while routing protocols converge
\n– this avoids route flapping<\/p>\n

IPv6 RIP supports the use of a route map to select routes for redistribution
\n– route may be specified by:
\n– prefix
\n– route-map prefix list
\n– tag<\/p>\n

Configuring route tags:<\/p>\n

route-map bgp-to-rip permit 10
\nmatch ipv6 address prefix-list bgp-rip-list
\nset tag 4<\/p>\n

Route filtering using distribute lists provides control over the routes RIP receives and advertises
\n– this may be done globally or per interface<\/p>\n

Input distribute lists control route reception
\n– input filtering is applied to advertisements received from neighbors
\n– only routes that pass input filtering will be inserted in the RIP local routing table and become a candidate for insertion into the IPv6 routing table<\/p>\n

Output distribute lists control route advertisement<\/p>\n

An interface distribute list always takes precedence<\/p>\n

An IPv6 prefix list range can be specified with the keywords “le” (less than) and “ge” (greater than)
\n– an exact match is assumed when “le” and “ge” are not specified<\/p>\n

ipv6 prefix list seq {deny | |description } ge le<\/p>\n

Example:<\/p>\n

ipv6 prefix-list abc permit 2001:DB8::\/16
\nipv6 prefix-list abc deny ::\/0<\/p>\n

ipv6 router rip process1
\ndistribute-list prefix-list abc in fa0\/0<\/p>\n

Example:<\/p>\n

ipv6 router rip process1
\nmaximum-paths 1
\nredistribute bgp 65001 route-map bgp-to-rip
\ndistribute-list prefix-list eht0\/0-in-flt in Ethernet0\/0<\/p>\n

int e0\/0
\nipv6 address 2001:DB8::\/64 eui-64
\nipv6 rip process1 enable
\nipv6 rip process1 default-information originate<\/p>\n

ipv6 prefix-list bgp-to-rip-flt seq 10 deny 2001:DB8:3::\/16 le 128
\nipv6 prefix-list bgp-to-rip-flt seq 20 permit 2001:DB8:1::\/8 le 128<\/p>\n

ipv6 prefix-list eth0\/0-in-flt seq 10 deny ::\/0
\nipv6 prefix-list eth0\/0-in-flt seq 20 permit ::\/0 le 128<\/p>\n

route-map bgp-to-rip permit 10
\nmatch ipv6 address prefix-list bgp-to-rip-flt<\/p>\n

Bidirectional Forward Detection (BFD) for RIPv2 support feature is used to facilitate an alternate path selection when a neighboring router is inactive<\/p>\n

BFD is a protocol that provides subsecond failure detection using a single, common standardized mechanism that is independent of media and routing protocols<\/p>\n

Configuring BFD for RIPv2 neighbors:<\/p>\n

router rip
\nversion 2
\nbfd all-interfaces<\/p>\n

Enable BFD for a specific RIP neighbor<\/p>\n

router rip
\nversion 2
\nneighbor 10.10.20.2 bfd<\/p>\n

BFD for RIPv2 Support was introduced in 15.3(2)T<\/p>\n

Key chain authentication pitfall
\n– white space counts as a valid character
\n– use “show key chain” command to ensure that a space is not at the end of the<\/p>\n

authentication key
\n– for RIP and EIGRP authentication<\/p>\n

ip rip advertise (0 – 429466>
\n– interface command to specify the periodic advertisement interval
\n– the command overrides the default global periodic advertisement interval or the<\/p>\n

“timers-basic” settings<\/p>\n","protected":false},"excerpt":{"rendered":"

v5 Written: 3.4 RIP (v2 and v6) 3.4.a Implement and troubleshoot RIPv2 3.4.b Describe RIPv6 (RIPng) v5 Lab: 2.4 RIPv2 2.4.a Implement and troubleshoot RIPv2 http:\/\/docwiki.cisco.com\/wiki\/Routing_Information_Protocol http:\/\/www.cisco.com\/c\/en\/us\/tech\/ip\/routing-information-protocol-rip\/index.html http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/ios-xml\/ios\/iproute_rip\/configuration\/15-mt\/irr-15- mt-book.html http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/lan\/catalyst3750x_3560x\/software\/release\/15 -0_2_se\/configuration\/guide\/3750x_cg\/swiprout.html#wp1028241 http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/ios-xml\/ios\/iproute_rip\/command\/irr-cr-book\/irr-cr- rip.html Routing TCP \/ IP Volume I – Chapter 5: Routing Information Protocol (RIP) Routing TCP \/ IP Volume I – Chapter 6: […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[30,21,11],"class_list":["post-56","post","type-post","status-publish","format-standard","hentry","category-ccie","tag-ccie","tag-rip","tag-route-switch"],"_links":{"self":[{"href":"https:\/\/feralpacket.org\/index.php?rest_route=\/wp\/v2\/posts\/56","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/feralpacket.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/feralpacket.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/feralpacket.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/feralpacket.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=56"}],"version-history":[{"count":3,"href":"https:\/\/feralpacket.org\/index.php?rest_route=\/wp\/v2\/posts\/56\/revisions"}],"predecessor-version":[{"id":233,"href":"https:\/\/feralpacket.org\/index.php?rest_route=\/wp\/v2\/posts\/56\/revisions\/233"}],"wp:attachment":[{"href":"https:\/\/feralpacket.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=56"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/feralpacket.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=56"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/feralpacket.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=56"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}