JUST QUICK RECAP OF RIPv1 & RIPv2 :
The Routing Information Protocol (RIP) Is A Distance-Vector Routing Protocol, Which Employs The Hop Count As A Routing Metric. RIP Prevents Routing Loops By Implementing A Limit On The Number Of Hops Allowed In A Path From The Source To A Destination. The Maximum Number Of Hops Allowed For RIP Is 15. This Hop Limit, However, Also Limits The Size Of Networks That RIP Can Support. A Hop Count Of 16 Is Considered An Infinite Distance And Used To Deprecate Inaccessible, Inoperable, Or Otherwise Undesirable Routes In The Selection Process.
RIP Implements The Split Horizon, Route Poisoning And Hold down Mechanisms To Prevent Incorrect Routing Information From Being Propagated. These Are Some Of The Stability Features Of RIP.
Routing Information Protocol (RIP) Is The Simplest Routing Protocol That Uses A "Distance Vector" Algorithm To Determine The Best Routing Path. It Uses The Number Of Hops, Or Hop Count (Also Referred As The Metric) To Determine The Best Possible Route To A Host Or Network. RIP Is Designed As An Interior Gateway Protocol (IGP), A Protocol For Exchanging Routing Information Within An Autonomous System (AS).
RIP Version1:
Which Was Defined In RFC 1058, Is A Classfull Distance-Vector Routing Protocol That Uses Router Hop Count As A Metric And Uses UDP Port 520. Because Ripv1 Is A Classfull Protocol, It Does Not Support VLSMS OR CIDR. Furthermore, The Subnet Mask For The Entire IP Network Must Be The Same. Ripv1 Messages Are Encapsulated With UDP.
A RIP ROUTER SENDS ITS ROUTING TABLE TO ITS NEIGHBOR ROUTERS EVERY 30 SECOND. RIP Uses The Split Horizon With Poison Reverse. Thus, Route Updates Are Sent From The Interface With An Infinite Metric For Learned Routes Received From The Same Interface. RIP Transmits Triggered Updates When A Route's Metric Has A Change. RIP Only Performs Load Balancing When The Paths Have Equal Costs. The Administrative Distance For RIP Is 120.
RIP AUTOMATICALLY SUMMARIZES IP Networks At The Network Boundary, Which Occurs On A Router That Has One Or More Interfaces Without An Ip Address That Is Part Of The Network Number. The Networks Are Summarized To Their Ip Class. You Can Disable Automatic Summarization By Issuing The No Auto-Summary Command. Ripv1 Maintains Information On The Ip Addresses Of The Destination Host/Network, The Initial Gateway In The Path/Route To The Destination, The Physical Network To The Destination; The Hop Count Metric To The Destination Host/Network, And The Time Lapsed Since Previous Update. Rip Transmits Its Entire Routing Table As Periodic Broadcasts From All Rip Configured Interfaces To Every Host. A Maximum Of 25 Routes Can Be Included In Each Rip Message.
RIP Version2 :
RIPv2, Which Was First Defined In RFC 1388 And Was Updated In RFC 1723 (1994) And RFC 2453 (1998), Is A Classless Distance-Vector Routing Protocol That Also Uses UDP Port 520. Ripv2 Improves Upon Ripv1 By Adding VLSM And CIDR Support, As Well As Support For Route Authentication And Multicasts Route Updates. Thus, Ripv2 Does Send The Subnet Mask With Route Updates. Whereas Ripv1 Uses IP Address 255.255.255.255 To Broadcast Its Route Updates To Other RIP Routers, Ripv2 Uses IP Address 224.0.09 To Multicast The Route Updates.
As With RIPv1, Updates Are Sent Every 30 Seconds And The Hop Limit Is 15. Triggered Updates Are Also Used, As Is UDP Port 520. Split Horizon With Poison Reverse Is Used For Loop Prevention And Counting To Infinity Is Retained. In Addition, Ripv2 Has The Same Administrative Distance As Ripv1, Which Is 120 On Cisco Routes.
RIPv2 Also Summarizes IP Networks At Network Boundaries. As With Ripv1, You Can Disable Automatic Summarization By Using The No Auto-Summary Command.
You Can Use RIPv2 In Small Networks Where VLSM Is Required, Or At The Edge Of The Larger Networks. You Can Use Authentication To Ensure That Communication Only Takes Place With RIP Routers That Are Part Of The Network. RIP Routers Will Only Process The Route Updates That Hold The Authentication Password. RFC 1723 Describes Plain Text Passwords For Ripv2. A More Secure Method, Message Digest 5 (MD5) As Defined In RFC 1321, Can Be Used For Authentication.
A Maximum Of 25 Routes Are Contained in Ripv2 Message. When Authentication Is Used.
RIPv1 Vs RIPv2:
LIMITATIONS OF RIPv1:
1.Hop Count Limit: More Than 15 Hops Away Is Considered Unreachable By Ripv1.
2. Classful Routing Only: RIP Is A Classful Routing Protocol. Ripv1 Doesn't Support Classless Routing. RIP V1 Advertises All Networks It Knows As Classful Networks, So It Is Not Possible To Subnet A Network Using RIP v1.
3.Metric Limitation: The Best Route In RIP Is Determined By Counting The Number Of Hops Required To Reach The Destination. A Lower Hop Count Route Is Always Preferred Over A Higher Hop Count Route. One Disadvantage Of Using Hop Count As Metric Is That If There Is A Route With One Additional Hop, But With Significantly Higher Bandwidth, The Route With Smaller Bandwidth Is Taken.
The RIP Routed Packets Take The Path Through 56KBPS Link Since The Destination Can Be Reached In One Hop. Though, The Alternative Provides A Minimum Bandwidth Of 1MBPS (Though Using Two Links Of 1MBPS, And 2MBPS Each), It Represents 2 Hops And Not Preferred By The RIP Protocol.
FEATURES OF RIP v2:
RIP v2 Is A Revised Version Of Its Predecessor RIP v1. The Following Are The Important Feature Enhancements Provided In RIPv2:
1.RIPv2 Packets Carry The Subnet Mask In Each Route Entry, Making RIPv2 A Classless Routing Protocol. It Provides Support For Variable-Length Subnet Masking (VLSM) And Classless Addressing (CIDR).
2. Next Hop Specification: In RIPv2, Each RIP Entry Includes A Space Where An Explicit IP Address Can Be Entered As The Next Hop Router For Datagrams Intended For The Network In That Entry.
For Example: This Field Can Be Used When The Most Efficient Route To A Network Is Through A Router That Is Not Running RIP. Since, That A Router Will Not Exchange RIP Messages, Explicit Next Hop Field Allows The Router To Be Selected As The Next Hop Router.
3. Authentication: RIPv1 Does Not Support Authentication. This Loophole May Be Used Maliciously By Hackers, That May Resulting In Delivering The Data Packets To A Fictitious Destination As Determined By The Hacker. RIPv2 Provides A Basic Authentication Scheme, So That A Router Can Accept RIP Messages From A Neighboring Router Only After Ascertaining Its Authenticity.
4.Route Tag: Each RIPv2 Entry Includes A Route Tag Field, Where Additional Information About A Route Can Be Stored. It Provides A Method For Distinguishing Between Internal Routes (Learned By RIP) And External Routes (Learned From Other Protocols).
LIMITATIONS OF RIP v2:
One Of The Biggest Limitations Of RIPv1 Still Remains With RIPv2. It Is Hop Count Limitation, And Metric. The Hop Count Of 16 Still Remains As Unreachable, And The Metric Still Remains Hop Count. A Smaller Hop Count Limits The Network Diameter That Is The Number Of Routers That Can Participate In The RIP Network.
Go For More Details about RIP - = >>>
http://premji-schoolofcisconetworking.blogspot.com/search/label/CISCO%20-%20RIP%3ARIPng (RIP Next Generation Routing Protocol For IPv6):
The Presentation In This Document Is Closely Based On RIPng.
One Of The Most Widely Used Interior Gateway Protocols Is The Routing Information Protocol (RIP). RIPng (Routing Information Protocol - Next Generation) Is An Ipv6 Implementation Of This Distance-Vector, Or Bellman-Ford, Routing Protocol For Local Networks. RIPng Is Based On The RIP Protocol And Inherits The Limitations And Constraints That Are In RIP.
This RIPng Functionality Includes A Separate RIB For The Ipv6 Address Family, ICMP For Ipv6, And Ipv6 Neighbor Discovery.
This Memo Describes One Protocol In A Series Of Routing Protocols Based On The Bellman-Ford (Or Distance Vector) Algorithm.
RIPng Is One Of A Class Of Algorithms Known As Distance Vector Algorithms. The Earliest Description Of This Class Of Algorithms Known To The Author Is In Ford And Fulkerson. Because Of This, They Are Sometimes Known As Ford-Fulkerson Algorithms. The Term Bellman-Ford Is Also Used, And Derives From The Fact That The Formulation Is Based On Bellman's Equation .
RIPng Is Intended To Allow Routers To Exchange Information For Computing Routes Through An IPv6-Based Network.
RFC 2080 Describes RIPngv1,
INTRODUCTION
This Report Describes How Ripng May Be Useful Within The New Ipv6 Internet. In Essence, The Environments In Which Ripng Is The IGP Of Choice Is Comparable To The Environments In Which RIP-2 (RFC 1723) Is Used In The Ipv4 Internet. It Is Important To Remember That RIPng Is A Simple Extrapolation Of RIP-2; RIPng Has Nothing Conceptually New. Thus, The Operational Aspects Of Distance-Vector Routing Protocols, And RIP-2 In Particular, Within An Autonomous System Are Well Understood.
It Should Be Noted That RIPng Is Not Intended To Be A Substitute For OSPFng In Large Autonomous Systems; The Restrictions On AS Diameter And Complexity Which Applied To RIP-2 Also Apply To RIPng. Rather, RIPng Allows The Smaller, Simpler, Distance-Vector Protocol To Be Used In Environments Which Require Authentication Or The Use Of Variable Length Subnet Masks, But Are Not Of A Size Or Complexity Which Require The Use Of The Larger, More Complex, Link-State Protocol.
A Goal In Developing RIPng Was To Make The Minimum Necessary Change To RIP-2 To Produce RIPng. In Essence, The Ipv4 Address Was Expanded Into An IPv6 Address, The Ipv4 Subnet Mask Was Replaced With An Ipv6 Prefix Length, The Next-Hop Field Was Eliminated But The Functionality Has Been Preserved, And Authentication Was Removed. The Route Tag Field Has Been Preserved. The Maximum Diameter Of The Network (The Maximum Metric Value) Is 15; 16 Still Means Infinity (Unreachable).
The Basic RIP Header Is Unchanged. However, The Size Of A Routing Packet Is No Longer Arbitrarily Limited. Because Routing Updates Are Never Forwarded, The Routing Packet Size Is Now Determined By The Physical Media And The Sizes Of The Headers Which Precede The Routing Data (I.E., Media MTU Minus The Combined Header Lengths). The Number Routes Which May Be Included In A Routing Update Is The Routing Data Length Divided By The Size Of A Routing Entry.
Each Router That Implements RIPng Is Assumed To Have A Routing Table. This Table Has One Entry For Every Destination That Is Reachable Throughout The System Operating RIPng.
PREFIX:
The Address Field Of A Routing Entry Is 128 Bits In Length, Expanded From The 32 Bits Available In RIP-2. This Allows The RIP Entry To Carry An Ipv6 Prefix.
THE IPv6 PREFIX OF THE DESTINATION:
- A Metric, Which Represents The Total Cost Of Getting A Datagram From The Router To That Destination. This Metric Is The Sum Of The Costs Associated With The Networks That Would Be Traversed To Get To The Destination.
- The Ipv6 Address Of The Next Router Along The Path To The Destination (I.E., The Next Hop). If The Destination Is On One Of The Directly-Connected Networks, This Item Is Not Needed.
- A Flag To Indicate That Information About The Route Has Changed Recently. This Will Be Referred To As The "Route Change Flag."
- Various Timers Associated With The Route. See Section 2.3 For More Details On Timers.
MESSAGE FORMAT:
RIPng IS ACTUALLY SIMILAR TO RIP FOR IPv4, WITH THESE CHARACTERISTICS :
RFC 2081 The Internal Routers (Ir1 And Ir2) Are Only Running Ripng. The External Routers (Xr1 And Xr2) Are Both Running Bgp, For Example; However, Only Xr1 Is Running Bgp And Ripng. Since Xr2 Is Not Running Ripng, The Irs Will Not Know Of Its Existance And Will Never Use It As A Next Hop, Even If It Is A Better Next Hop Than Xr1. Of Course, Xr1 Knows This And Can Indicate, Via The Next Hop Mechanism, That Xr2 Is The Better Next Hop For Some Routes. AUTHENTICATION Authentication, Which Was Added To Rip-2 Because Rip-1 Did Not Have It, Has Been Dropped From Ripng. This Is Safe To Do Because Ipv6, Which Carries The Ripng Packets, Has Build In Security Which Ipv4 Did Not Have.
THE MAIN DIFFERENCES BETWEEN RIPv2 AND RIPng ARE:
RIPng Is, Therefore, No More Or Less Powerful Than RIP. However, It Provides A Simple Way To Bring Up An IPv6 Network Without Having To Build A Reliable Or Manageable Routing Protocol First. Our Interoperability Demo In The labs Uses Ripng To Distribute Routing Information.
The Main Difference Is That The IPv6 Router Is Looking At 128 Bits When Making A Routing Decision Instead Of 32 Bits.
RIPng FEATURES :
RIPng BENEFITS ;
THESE ARE THE ENHANCEMENTS IN RIPng :
Notice: That This Is The Route That Ripng Does Not Advertise. Ripng Will Advertise Any Other Ipv6 Addresses Configured On The Common Link Between Neighbours.
IMPLEMENTING RIP FOR IPv6:
In The Cisco IOS Software Implementation Of Ipv6 RIP Each Ipv6 RIP Process Maintains A Local Routing Table, Referred To As A Routing Information Database (RIB). The Ipv6 RIP RIB Contains A Set Of Best-Cost Ipv6 RIP Routes Learned From All Its Neighboring Networking Devices. If Ipv6 RIP Learns The Same Route From Two Different Neighbors, But With Different Costs, It Will Store Only The Lowest Cost Route In The Local RIB. The RIB Also Stores Any Expired Routes That The RIP Process Is Advertising To Its Neighbors Running RIP. Ipv6 RIP Will Try To Insert Every Non-Expired Route From Its Local RIB Into The Master Ipv6 RIB. If The Same Route Has Been Learned From A Different Routing Protocol With A Better Administrative Distance Than Ipv6 RIP, The RIP Route Will Not Be Added To The Ipv6 RIB But The RIP Route Will Still Exist In The Ipv6 RIP RIB.
ENABLING IPV6 RIP:
This Task Explains How To Create An Ipv6 RIP Process And Enable The Specified Ipv6 RIP Process On An Interface.
PREREQUISITES:
Before Configuring The Router To Run Ipv6 RIP, Globally Enable Ipv6 Using The Ipv6 Unicast-Routing Global Configuration Command, And Enable Ipv6 On Any Interfaces On Which Ipv6 RIP Is To Be Enabled.
For Details On Basic Ipv6 Connectivity Tasks, Refer To The Implementing Basic Connectivity For Ipv6 Module.
SUMMARY STEPS
1. Enable
2. Configure Terminal
3. Interface Type Number
4. Ipv6 Rip Name Enable
RIPng CONFIGURATION EXAMPLE :
Router(Config)#Interface Serial 0/0 - > Moves To Interface Configuration Mode.
Router(Config-If)#Ipv6 Rip Tower Enable - > Creates The Ripng Process Named Tower And Enables Ripng On The Interface.
NOTE: Unlike Ripv1 And Ripv2, Where You Needed To Create The Rip Routing Process With The Router Rip Command And Then Use The Network Command To Specify The Interfaces On Which To Run Rip, The Ripng Process Is Created Automatically When Ripng Is Enabled On An Interface With The Ipv6 Rip Name Enable Command.
NOTE: Cisco Ios Software Automatically Creates An Entry In The Configuration For The Ripng Routing Process When It Is Enabled On An Interface.
NOTE: The Ipv6 Router Rip Process-Name Command Is Still Needed When Configuring Optional Features Of Ripng.
Router(Config)#Ipv6 Router Rip Tower - > Creates The Ripng Process Named Tower If It Has Not Already Been Created, And Moves To Router Configuration Mode.
Router(Config-Router)#Maximum-Paths 2 - > Defines The Maximum Number Of Equal-Cost Routes That Ripng Can Support.
NOTE: The Number Of Paths That Can Be Used Is A Number From 1 To 64. The Default Is 4.
NOTE:Enabling RIPng Is A Little Bit Different Than Enabling Rip For Ipv4.
RIPng IPv6 COMMAND(S):
SHOW IPv6 RIP NAME – This Command When Executed In Interface Configuration Mode Will Configure That Paticular Interface To Participate In The Specified Ripng Process Name.
SHOW IPv6 RIP NAME – This Command When Executed In User Or Privileged Mode Will Display Current RIPng Timers And Statistics Of The Specified RIPng Process Name.
SHOW IPv6 RIP NAME DATABASE – This Command When Executed In User Or Privileged Mode Will Display The RIPng Data Base Of The Specified RIPng Process Name.
SHOW IPv6 RIP NAME NEXT-HOPS – This Command When Executed In User Or Privileged Mode Will Display A Summary Of RIPng Routes Per RIPng Process Name Based On Their Next-Hop.
SHOW IPv6 ROUTE – This Command When Executed In User Or Privileged Mode Will Display The Routing Table On That Particular Device.
FIRST, YOU USE THE IPV6 ROUTER RIP TAG COMMAND TO ENABLE RIPNG GLOBALLY :
Router(Config)# Ipv6 Router Rip Tag
This Takes You Into A Subcommand Mode, Where You Can Change Some Of The Global Values For RIPng, Such As Disabling Split Horizon, The Administrative Distance, And Timers. The Tag Is A Locally Significant Identifier Used To Differentiate Between Multiple RIP Processes Running On The Router.
IPv6 RIP TAG ENABLE COMMAND :
Router(Config)# Interface Type [Slot/Port]
Router(Config-If)# Ipv6 Rip Tag Enable
The Tag Parameter Associates The Interface With The Correct RIPng Routing Process. To View The Routing Protocol Configuration, Use The Show IPv6 Rip Command:
Router# Show Ipv6 Rip
RIP Process "RIPPROC1", Port 521, Multicast-Group FF02::9,
Pid 187
Administrative Distance Is 120. Maximum Paths Is 16
Updates Every 30 Seconds, Expire After 180
Holddown Lasts 0 Seconds, Garbage Collect After 120
Split Horizon Is On; Poison Reverse Is Off
Default Routes Are Not Generated
Periodic Updates 2, Trigger Updates 0
Interfaces:
Fastethernet0/0
Redistribution:
None
IN THIS EXAMPLE, The Tag Is RIP PROC1 For The Name Of The RIPng Routing Process And RIPng Is Enabled On Fastethernet0/0. To View The IPv6 Routing Table For RIPng, Use The Show IPv6 Route RIP Command.
ENABLE RIPng EXAMPLE :
Router#Conf T
Router(Config)#Ipv6 Router Rip ?
WORD User Selected String Identifying This Process
Router(Config)#Ipv6 Router Rip Test
Router(Config-Rtr)#Exit
Router(Config)#
Router(Config)#Int Fa 0/0
Router(Config-If)#
Router(Config-If)#Ipv6 Rip Test Enable
Router(Config-If)#
As You See, Now We Can Have Multiple RIPng Processes Running. When You Confiure Them, You Need To Specify The Identifyer For The Process, So When You Configuring The Interfaces, You Must Choose The Routing Process In Which That Interface Is Part Of.
BEFOURE GOING TO RIPng LAB, QUICK RECAP OF IPv6 CONFIGURATION :
IPv6 ADDRESSING :
When The IPv4 Address Has 32 Bits, The IPv6 Address Is Represented By A (Hopefully) Inexhaustible 128-Bit Number. The Full Ipv6 Address Is Written As Eight Blocks, Each Containing Four Hexadecimal Numbers. These Blocks Are Separated By Colons ":". A Hex Number Represents A 4-Bit Field, So A Group Of 4 Hex Numbers Represents 16 Bits.
So We Must Have 8 Such Groups Of Numbers To Make Up The Full 128 Bits Of The Ipv6 Address:
x:x:x:x:x:x:x:x
As We Will Discuss In A Moment, Many Types Of Standard Ipv6 Address Implementations Involve A Lot Of Sequential Zeroes In The Address. When This Happens, There Are Some Useful Rules That Allow Us To Simplify The Address. It's Easiest To Understand These Rules With A Concrete Example.
Suppose We Have This Address:
FEC0:0000:0000:0001:0000:0000:0000:0001/64
We Can First Delete All Of The High Order Zeroes In Each Group Of Four Hex Numbers.
FEC0:0:0:1:0:0:0:1/64
Then We Can Replace The Longest Set Of Consecutive Zeroes With Simply "::":
FEC0:0:0:1::1/64
This Object Is Now Much Easier To Work With.
Also Note That In The Example, We Have Included The Prefix Size /64, At The End Of The Address. This Convention Is Identical To The Prefix Size Bit Count Used In Ipv4 Addresses. This Is Not Only Similar In Appearance To The Ipv4 CIDR Representation Of Addresses, But It Has The Same Function, Allowing Routers To Establish Multiple Hierarchical Address Summarizations In The Network.
ADDRESSING STANDARDS :
The IANA Has Allocated Several Ranges Of Ipv6 Addresses For Different Purposes. RFC 4294 Defines These Rules, Updating The Earlier RFC 3513 Document. This Document Defines Three General Classes Of Addressesunicast, Multicast And Anycast. In Addition, The Standard Defines Several Different Types Of Unicast Address. As With Ipv4, These Different Address Types Are Uniquely Identified By The First Few Bits Of The Address.
IPV6 ADDRESS TYPES :
128-Bit IPv6 Address And Padding All Of The Higher Order Bits With Zeroes. For Example, The Address 192.168.11.1 Would Be Written As 0:0:0:0:0:0:C0A8:0B01 Or ::C0A8:B01, Or Following Another Convenient Standard For Representing Ipv6 Address That Contain Ipv4 Address, ::192.168.11.1. Once Again, This Method Is Also Deprecated Because It Doesn't Match Well With Newer Methods For Interoperating Ipv4 And Ipv6 Networks. However, You Will Sometimes See It In Use In Older Ipv6 Implementations.
Another Common Method For Writing Ipv4 Addresses Inside Of Ipv6 Addresses Is Called "Ipv4-Mapped Addressing", And It Follows A Similar Strategy. Once Again, The Last 32 Bits Encapsulate The Ipv4 Address, But In This Method, The Ipv4 Address Is Padded By 16 Binary Ones And 80 Zeroes. So This Time The Address 192.168.11.1 Becomes 0:0:0:0:0:FFFF:C0A8:0B01, Or ::FFFF:C0A8:B01.
Finally, Some Cisco Documentation Talks About So-Called Site-Local Addressing, Which Has A Binary Prefix Of 1111 1110 11, Or FEC0::/10 In Hex. The Site-Local Addressing Concept Has Now Been Deprecated And Removed From The Ipv6 Standard. While Individual Sites Are Free To Continue Using This Addressing Scheme And Manually Block These Addresses From Leaking Out Of A Particular Administrative Area By Means Of Access-Lists, These Addresses Are Now Considered To Be Standard Unicast Addresses.
IEEE EUI-64 IDENTIFIERS :
One Thing That You Will Run Into Quickly In Working With Ipv6 Is The EUI-64 Identifier For An Interface. The EUI-64 Identifier Is Essentially An Extension Of The Already Familiar 48-Bit MAC Address Commonly Used On Ethernet Interfaces. RFC 4291 Defines A Way Of Using This EUI-64 Address To Build A Unique Ipv6 Address Automatically For An Interface.
There Are Two Methods For Generating IPv6 Addresses Automatically. The First Uses The Autoconfig Command:
Router1#Configure Terminal
Enter Configuration Commands, One Per Line. End With CNTL/Z.
Router1(Config)#Ipv6 Unicast-Routing
Router1(Config)#Interface Fastethernet0/0
Router1(Config-If)#Ipv6 Address Autoconfig
Router1(Config-If)#End
Router1#
The Second Method Uses The EUI-64 Method To Automatically Generate Only The Host Part Of The Ipv6 Address, Combined With A Defined Network Portion:
Router1#Configure Terminal
Enter Configuration Commands, One Per Line. End With CNTL/Z.
Router1(Config)#Ipv6 Unicast-Routing
Router1(Config)#Interface Fastethernet0/0
Router1(Config-If)#Ipv6 Address AAAA::/64 Eui-64
Router1(Config-If)#End
Router1#
Throughout This Chapter You Will See The Following Command Frequently: Router1(Config)#Ipv6 Unicast-Routing
By Default, The Router Will Not Route IPv6 Packets. You Can Configure Interfaces With Ipv6 Addresses, And You Can Even Use Ipv6 Applications Such As PING And TELNET To Communicate To And From These Routers.
TO VIEW IPv6 CONFIGURATION:
Router1#Show Ipv6 Interface Fastethernet0/0
Fastethernet0/0 Is Up, Line Protocol Is Up
Ipv6 Is Enabled, Link-Local Address Is FE80::20E:D7FF:FED6:4D80
No Global Unicast Address Is Configured
Joined Group Address(Es):
FF02::1
FF02::1:FFD6:4D80
MTU Is 1500 Bytes
ICMP Error Messages Limited To One Every 100 Milliseconds
ICMP Redirects Are Enabled
ND DAD Is Enabled, Number Of DAD Attempts: 1
ND Reachable Time Is 30000 Milliseconds
Router1#
NOTE:The Address That The Router Generates This Way Uses The Standard Link-Local Prefix FE80::/10 And The EUI-64 Version Of The MAC Address For The Last 64 Bits. We Will Discuss The EUI-64 Encoding In A Moment.
Examples :
The Ipv6 Route For Configuring The Various Types Of Static Routes.
The Following Example Shows How To Configure A Directly Attached Static Route Through A Point-To-Point Interface.
Router(Config)# Ipv6 Route 2001:0db8::/32 Serial 0
The Following Example Shows How To Configure A Directly Attached Static Route On A Broadcast Interface.
Router(Config)# Ipv6 Route 2001:0db8::1/32 Ethernet1/0
The Following Example Shows How To Configure A Fully Specified Static Route On A Broadcast Interface.
Router(Config)# Ipv6 Route 2001:0db8::1/32 Ethernet1/0 Fe80::1
In The Following Example, A Static Route Is Being Configured To A Specified Next-Hop Address, From Which.
The Output Interface Is Automatically Derived.
Router(Config)# Ipv6 Route 2001:0db8::/32 2001:0db8:2002:1
TO ENABLE RIPNG:
Router(Config)# Ipv6 Router Rip
TO ENABLE RIPNG ON AN INTERFACE:
Router(Config-If)# Ipv6 Rip
TO ORIGINATE THE DEFAULT ROUTER (::/0) OUT AN INTERFACE:
Router(Config-If)# Ipv6 Rip
Router(Config-Rtr)# Distance <#>
Router(Config-Rtr)# Distribute-List Prefix-List
Router(Config-Rtr)# Metric-Offset <#>
Router(Config-Rtr)# Poison-Reverse
Router(Config-Rtr)# Split-Horizon
Router(Config-Rtr)# Port
Router(Config-Rtr)# Timers
Router(Config-Rtr)# Redistribute [ Connected | Isis | Ospf | Static | Bgp | Rip
RIPng SHOW COMMANDS:
Show Ipv6 Route
Show Ipv6 Rip [Database] [Next-Hops]
Show Ipv6 Protocols
RIPng DEBUG COMMANDS:
Debug Ipv6 Rip
Debug Ipv6 Routing
Clear Ipv6 Rip
EXAMPLE - 1 FOR ENABLING RIPng ON A CISCO ROUTER:
CONFIGURATION ON FOLLOWING INSTRUCTIONS :
STEP1 :Enter Into Privileged Mode On Router - 1.
STEP2 : Enter Into Global Configuration Mode.
STEP3 : Enter The Command "IPv6 Unicast-Routing" That Enables The Forwarding Of IPv6 Unicast Datagrams Globally On The Router.
STEP4 : Enter Into Interface Configuration Mode And Then Use The Command "IPv6 Rip
STEP5 : Issue "Show IPv6 Rip" Command That Displays Information About The Configured Rip Routing Processes.
STEP1 :
Router>enable
Change The Host Name Of The Router To “Router – 1” Using The Following Command :
Router(Config)#Hostname Router - 1
STEP2 :
Router - 1#Configure Terminal
Router - 1(Config)#
Enter Configuration Commands, One Per Line. End With Cntl/Z.
STEP3 :
Router - 1(Config)#IPv6 Unicast-Routing
Router - 1(Config)#Interface Serial 0
STEP4 :
Router - 1(Config-If)#Ipv6 Rip Pname1 Enable
Router - 1(Config-If)#Exit
Router - 1(Config)#Exit
STEP :
TO DISPLAY CURENT CONFIGURATION :
R1#Show Ipv6 Rip
R1#Show Ipv6 Protocols
NOTE :
EXAMPLE - 2 FOR ENABLING RIPng ON A CISCO ROUTER :
Two Routers Connected To Each Other With Their Loopbacks (Logical Interfaces) Enabled On Each Router.
CONFIGURATION ON ROUTER - 1
Router1>Enable
Router1#Conf Terminal
Router1(Config)#Int S1/ 0
Router1(Config)#IPv6 Unicast-Routing (To Enable IPv6 In Routers)
Router1(Config-If)IPv6 Address 2001::1:1:1:1:1/64
Router1(Config-If)#No Shutdown
Router1(Config-If)Exit
Router1(Config)#Interface Loopback 0
Router1(Config-If)#IP Adress 2001::2:1:1:1:1/64
Router1(Config-If)#No Shutdown
Router1(Config)#Exit
CONFIGURATION ON ROUTER - 2
Router2>Enable
Router2#Conf Terminal
Router2(Config)#Int S1/ 0
Router2(Config)#IPv6 Unicast-Routing (To Enable IPv6 In Routers)
Router2(Config-If)IPv6 Address 2001::1:1:1:1:2/64
Router2(Config-If)#No Shutdown
Router2(Config-If)Exit
Router2(Config)#Interface Loopback 1
Router2(Config-If)#IP Adress 2001::3:1:1:1:1/64
Router2(Config-If)#No Shutdown
Router2(Config)#Exit
CONFIGURING RIPng ON ROUTER - 1:
Router1(Config)#Interface S1/ 0
Router1(Config-If)#IPv6 Rip 1234 Enable
Router1(Config-If)#Exit
Router1(Config)#Interface Loopback 0
Router1(Config-If)#IPv6 Rip 1234 Enable
Router1(Config-If)#Exit
CONFIGURING RIPng ON ROUTER - 2:
Router2(Config)#Interface S1/ 0
Router2(Config-If)#IPv6 Rip 1234 Enable
Router2(Config-If)#Exit
Router2(Config)#Interface Loopback 1
Router2(Config-If)#IPv6 Rip 1234 Enable
Router2(Config-If)#Exit
TO CHECK THE ROUTING TABLE:
Router1#Show IPv6 Route
TO DISPLAY CURENT CONFIGURATION ON ROUTER – 1 & ROUTER - 2:
Router1#Show IPv6 Rip
Router1#Show IPv6 Protocols
THE IPV6-SPECIFIC CISCO COMMANDS YOU CAN TRY:
Show IPv6 Interface (To See The Ethernet Interfaces Which Are Configured For IPv6)
Show IPv6 Neighbor (To See The IPv6 Equivalent Of The ARP Cache)
Show IPv6 Route (To See The IPv6 Routing Table)
Show IPv6 Routers (To See The Neighbor Routers On The LAN)
Show IPv6 Traffic (To See The Ipv6 Traffic Statistics).
RIPng LAB EXAMPLE - 1:
LAB CONFIGURATION :
On Router1:
Ipv6 Unicast-Routing
Ipv6 Cef
!
Interface Fastethernet 0/0
Ipv6 Enable
Ipv6 Address 2001:Abab::/64 Eui-64
Ipv6 Rip Rip Enable
!
Ipv6 Router Rip Rip
Maximum-Paths 3
!
On Router2:
Ipv6 Unicast-Routing
Ipv6 Cef
!
Interface Fastethernet 0/0
Ipv6 Enable
Ipv6 Address 2002:ABAB::/64 Eui-64
Ipv6 Rip RIP Enable
!
Interface Loopback 0
Ipv6 Enable
Ipv6 Address 2003:ABAB::/64 Eui-64
Ipv6 Rip RIP Enable
!
Ipv6 Router Rip RIP
Maximum-Paths 3
The Ipv6 Address Eui-64 Command Assigns An Ipv6 Address To The Interface With Interface Identifier I.E. The EUI-64 Format Interface Identifier In The Lower-Order 64-Bits.
Router1# Show Ipv6 Interface Brief
Fastethernet0/0 [Up/Up]
FE80::D202:14FF:FE70:0
2001:ABAB::D202:14FF:FE70:0
Router2# Show Ipv6 Interface Brief
Fastethernet0/0 [Up/Up]
FE80::D203:14FF:FE70:0
2002:ABAB::D203:14FF:FE70:0
Loopback0 [Up/Up]
FE80::D203:14FF:FE70:0
2003:ABAB::D203:14FF:FE70:0
NOTE: The IP Addresses Of R2's And R3's Fastethernet Interfaces Does Not Belong To The Same Subnet Since It Is Not A Requirement In Ipv6 Routing.
As Soon As Interface F 0/0 Is Up And Enabled For RIPng, It Requests Triggered Updates From Its Neighbors And Starts Sending Ripng Updates To Multicast Address Ff02::9 And Source Address As Its Link-Local Address, And Source And Destination Port 521. It Includes The Prefix Of The Interfaces For Which RIPng Is Enabled.
Debug Ipv6 Rip Output Is Taken From Router1.
Router1# Debug Ipv6 Rip
*Mar 1 00:05:35.263: %LINK-3-UPDOWN: Interface Fastethernet0/0, Changed State To Up
*Mar 1 00:05:35.275: Ripng: Link-Local FE80::D203:12FF:FEF0:0/10 Added
*Mar 1 00:05:35.275: Ripng: Full Advertisement Required
*Mar 1 00:05:35.279: Ripng: Sending Multicast Update On Fastethernet0/0 For RIP
*Mar 1 00:05:35.279: Src=FE80::D203:12FF:FEF0:0
*Mar 1 00:05:35.279: Dst=FF02::9 (Fastethernet0/0)
*Mar 1 00:05:35.279: Sport=521, Dport=521, Length=32
*Mar 1 00:05:35.279: Command=2, Version=1, Mbz=0, #Rte=1
*Mar 1 00:05:35.279: Tag=0, Metric=1, Prefix=2001:ABAB::/64
Router1#
*Mar 1 00:05:35.287: Ripng: Sending Multicast Request On Fastethernet0/0 For RIP
*Mar 1 00:05:35.287: Src=FE80::D203:12FF:FEF0:0
*Mar 1 00:05:35.291: Dst=FF02::9 (Fastethernet0/0)
*Mar 1 00:05:35.291: Sport=521, Dport=521, Length=32
*Mar 1 00:05:35.291: Command=1, Version=1, Mbz=0, #Rte=1
*Mar 1 00:05:35.291: Tag=0, Metric=16, Prefix=::/0
*Mar 1 00:05:35.291: Ripng: Triggered Update Requested, In Hold-Down
*Mar 1 00:05:36.263: %LINEPROTO-5-UPDOWN: Line Protocol On Interface
Fastethernet0/0, Changed State To Up
Router1 Continues To Send Periodic Updates To Multicast Address FF02::9 Every 30 Seconds.
Router1#
*Mar 1 00:06:04.171: Ripng: Sending Multicast Update On Fastethernet0/0 For RIP
*Mar 1 00:06:04.171: Src=FE80::D203:12FF:FEF0:0
*Mar 1 00:06:04.171: Dst=FF02::9 (Fastethernet0/0)
*Mar 1 00:06:04.171: Sport=521, Dport=521, Length=32
*Mar 1 00:06:04.175: Command=2, Version=1, Mbz=0, #Rte=1
*Mar 1 00:06:04.175: Tag=0, Metric=1, Prefix=2001:ABAB::/64
When Router2's Fastethernet 0/0 Interface Is Enabled For Ripng, It Responds To Router1 Request Messages.
Router1#
*Mar 1 00:07:42.527: Ripng: Response Received From FE80::D204:12FF:FEF0:0 On Fastethernet0/0 For RIP
*Mar 1 00:07:42.531: Src=FE80::D204:12FF:FEF0:0 (Fastethernet0/0)
*Mar 1 00:07:42.531: Dst=FF02::9
*Mar 1 00:07:42.531: Sport=521, Dport=521, Length=32
*Mar 1 00:07:42.531: Command=2, Version=1, Mbz=0, #Rte=1
*Mar 1 00:07:42.535: Tag=0, Metric=1, Prefix=2002:ABAB::/64
*Mar 1 00:07:42.535: Ripng: Added Neighbor FE80::D204:12FF:FEF0:0/Fastethernet0/0
*Mar 1 00:07:42.535: Ripng: Inserted 2002:ABAB::/64, Nexthop FE80::D204:12FF:FEF0:0,
Metric 2, Tag 0
*Mar 1 00:07:42.535: Ripng: Ripv6 Ager Started, 180000
When Router2's Loopback0 Interface Is Also Enabled For Ripng, Another Update Message Is Sent By Router2.
Router1#
*Mar 1 00:07:58.367: Ripng: Response Received From FE80::D204:12FF:FEF0:0 On
Fastethernet0/0 For RIP
*Mar 1 00:07:58.371: Src=FE80::D204:12FF:FEF0:0 (Fastethernet0/0)
*Mar 1 00:07:58.371: Dst=FF02::9
*Mar 1 00:07:58.371: Sport=521, Dport=521, Length=32
*Mar 1 00:07:58.371: Command=2, Version=1, Mbz=0, #Rte=1
*Mar 1 00:07:58.371: Tag=0, Metric=1, Prefix=2003:ABAB::/64
*Mar 1 00:07:58.375: Ripng: Inserted 2003:ABAB::/64, Nexthop
FE80::D204:12FF:FEF0:0, Metric 2, Tag 0
*Mar 1 00:07:58.375: Ripng: Triggered Update Requested, In Hold-Down
As Seen Above, Router1 Installs Both Prefixes 2002:ABAB::/64 And 2003:ABAB::/64 In Its Routing Table With Next-Hop As Router2's Fastethernet 0/0 Link-Local Address.
Also, Router2Advertises Both Prefixes With Metric 1, However, Router1 Installs Them With Metric 2 Indicating It Takes Him Metric 1 To Reach To Router2.
Router2 Also Continues To Send Periodic Updates Every 30 Seconds To All Its Interfaces, Including Loopback 0, With All Its Ripng Enabled Prefixes.
Router2#
*Mar 1 00:04:21.995: Ripng: Sending Multicast Update On Loopback0 For RIP
*Mar 1 00:04:21.995: Src=FE80::D203:14FF:FE70:0
*Mar 1 00:04:21.995: Dst=FF02::9 (Loopback0)
*Mar 1 00:04:21.999: Sport=521, Dport=521, Length=72
*Mar 1 00:04:21.999: Command=2, Version=1, Mbz=0, #Rte=3
*Mar 1 00:04:21.999: Tag=0, Metric=1, Prefix=2002:ABAB::/64
*Mar 1 00:04:21.999: Tag=0, Metric=1, Prefix=2003:ABAB::/64
*Mar 1 00:04:21.999: Tag=0, Metric=2, Prefix=2001:ABAB::/64
*Mar 1 00:04:22.003: Ripng: Sending Multicast Update On Fastethernet0/0 For RIP
*Mar 1 00:04:22.003: Src=FE80::D203:14FF:FE70:0
*Mar 1 00:04:22.003: Dst=FF02::9 (Fastethernet0/0)
*Mar 1 00:04:22.007: Sport=521, Dport=521, Length=52
*Mar 1 00:04:22.007: Command=2, Version=1, Mbz=0, #Rte=2
*Mar 1 00:04:22.007: Tag=0, Metric=1, Prefix=2002:ABAB::/64
*Mar 1 00:04:22.007: Tag=0, Metric=1, Prefix=2003:ABAB::/64
*Mar 1 00:04:22.011: Ripng: Process RIP Received Own Response On Loopback0
When Router2 Router's Loopback0 Interface Is Shut Down Manually, Router2 Tries To Send A Final Update To Loopback 0 Interface With Metric 16 And Then Updates Its Neighbors With A Single RTE Containing Loopback0 Prefix With Metric 16.
Router2(Config)# Interface Loopback 0
Router2(Config-If)# Shutdown
*Mar 1 00:05:05.407: Ripng: Loopback0 Down
*Mar 1 00:05:05.411:Ripng: Sending Final Update On Loopback0 For RIP
*Mar 1 00:05:05.411: Src=FE80::D203:14FF:FE70:0
*Mar 1 00:05:05.411: Dst=FF02::9 (Loopback0)
*Mar 1 00:05:05.411: Sport=521, Dport=521, Length=72
*Mar 1 00:05:05.415:Command=2, Version=1, Mbz=0, #Rte=3
*Mar 1 00:05:05.415: Tag=0, Metric=16, Prefix=2001:ABAB::/64
*Mar 1 00:05:05.415: Tag=0, Metric=16, Prefix=2002:ABAB::/64
*Mar 1 00:05:05.415: Tag=0, Metric=16, Prefix=2003:ABAB::/64
*Mar 1 00:05:05.423: Ripng: Triggered Update Requested
Router2#
*Mar 1 00:05:05.427: Ripng: Link-Local FE80::D203:14FF:FE70:0/10 Deleted
*Mar 1 00:05:05.431: Ripng: IDB Down, 2003:ABAB::D203:14FF:FE70:0/64
*Mar 1 00:05:05.435: Ripng: Inserted 2003:ABAB::/64, Nexthop ::, Metric 16, Tag 0
*Mar 1 00:05:05.435: Ripng: Triggered Update Requested, Delaying
*Mar 1 00:05:05.439: Ripng: Process RIP Received Own Response On Loopback0
*Mar 1 00:05:06.423: Ripng: Generating Triggered Update For RIP
*Mar 1 00:05:06.423: Ripng: Sending Multicast Update On Fastethernet0/0 For RIP
*Mar 1 00:05:06.423: Src=FE80::D203:14FF:FE70:0
*Mar 1 00:05:06.423: Dst=FF02::9 (Fastethernet0/0)
*Mar 1 00:05:06.427: Sport=521, Dport=521, Length=32
*Mar 1 00:05:06.427: Command=2, Version=1, Mbz=0, #Rte=1
*Mar 1 00:05:06.427: Tag=0, Metric=16, Prefix=2003:ABAB::/64
Router1 Router Receives This Update For Router2’s Loopback 0 And Immediately Generates A Triggered Update For Its Neighbors. It Also Initiates The Garbage-Collection-Timer Of 120 Seconds Since The Holddown Timer Is Set To 0 Seconds By Default.
*Mar 1 00:26:54.551: Ripng: Response Received From FE80::D203:14FF:FE70:0 On
Fastethernet0/0 For RIP
*Mar 1 00:26:54.555: Src=FE80::D203:14FF:FE70:0 (Fastethernet0/0)
*Mar 1 00:26:54.555: Dst=FF02::9
*Mar 1 00:26:54.555: Sport=521, Dport=521, Length=32
*Mar 1 00:26:54.555: Command=2, Version=1, Mbz=0, #Rte=1
*Mar 1 00:26:54.555: Tag=0, Metric=16, Prefix=2003:ABAB::/64
*Mar 1 00:26:54.559: Ripng: 2003:ABAB::/64, Path
FE80::D203:14FF:FE70:0/Fastethernet0/0 Unreachable
*Mar 1 00:26:54.559: Ripng: 2003:ABAB::/64, Expired, Ttg Is 120
*Mar 1 00:26:54.559: Ripng: Triggered Update Requested
Router1#
*Mar 1 00:26:55.559: Ripng: Generating Triggered Update For RIP
*Mar 1 00:26:55.559: Ripng: Suppressed Null Multicast Update On Fastethernet0/0 For RIP
Router2#
*Mar 1 00:27:07.299: Ripng: Response Received From FE80::D203:14FF:FE70:0 On Fastethernet0/0 For RIP
*Mar 1 00:27:07.299: Src=FE80::D203:14FF:FE70:0 (Fastethernet0/0)
*Mar 1 00:27:07.299: Dst=FF02::9
*Mar 1 00:27:07.303: Sport=521, Dport=521, Length=52
*Mar 1 00:27:07.303: Command=2, Version=1, Mbz=0, #Rte=2
*Mar 1 00:27:07.303: Tag=0, Metric=1, Prefix=2002:ABAB::/64
*Mar 1 00:27:07.303: Tag=0, Metric=16, Prefix=2003:ABAB::/64
After 120 Seconds (Garbage-Collection-Timer), R2 Router Deletes The Prefix From Its Database.
Router1#
*Mar 1 00:28:54.559: Ripng: Deleting 2003:ABAB::/64
The Ripng Database Can Be Viewed Using Show Ipv6 Rip RIP Database Command On R2
And R3 Routers.
Router1# Show Ipv6 Rip RIP Database
RIP Process "RIP", Local RIB
2002:ABAB::/64, Metric 2, Installed
Fastethernet0/0/FE80::D203:14FF:FE70:0, Expires In 169 Secs
2003:ABAB::/64, Metric 2, Installed
Fastethernet0/0/FE80::D203:14FF:FE70:0, Expires In 169 Secs
The RIPng Timers Related Information Can Be Viewed Using Show IPv6 Rip Command.
Router1# Show Ipv6 Rip
RIP Process "RIP", Port 521, Multicast-Group FF02::9, Pid 153
Administrative Distance Is 120. Maximum Paths Is 3
Updates Every 30 Seconds, Expire After 180
Holddown Lasts 0 Seconds, Garbage Collect After 120
Split Horizon Is On; Poison Reverse Is Off
Default Routes Are Not Generated
Periodic Updates 63, Trigger Updates 12
Interfaces:
Fastethernet0/0
Redistribution:
None
Updates Timer Is The Periodic Update Timer. Expire Timer Is The Time In Which Updates Expire. It Is Reinitialized To 180 Whenever An Update Is Received. Holddown Timer Is The Time For Which A Router Will Not Accept Any New Updates For The Router. It Is Set To 0 By Default. Garbage Collect Timer Is Set To 120 Seconds By Default. It Is The Time During Which The Route Will Be Continued To Advertise But If No Updates Are Received, The Route Will Be Removed From The Database.
It Is Very Interesting To See That During Holddown Timer, A Router Will Not Accept Any Updates From Its Neighbor For That Prefix. Once The Holddown Timer Expires And New Update Is Received For The Route As Reachable, It Is Immediately Placed Into The Routing Table. However, If The New Update Still Indicates That The Route Is Unreachable, The Route Is Deleted From The Database When The Garbage Collection Timer Expires Which Starts With The Holddown Timer.
CONCLUSION:
The Goal Of This Article Is To Give An Easy Way To Understand The “Cisco – RIPng Configuration.” Hope This Article Will Help Every Beginners Who Are Going To Start Cisco Lab Practice Without Any Doubts. Thank You And Best Of Luck.
This Article Written Author By: Premakumar Thevathasan. CCNA, CCNP, CCIP, MCSE, MCSA, MCSA - MSG, CIW Security Analyst, CompTIA Certified A+.
DISCLAIMER:
This Document Carries No Explicit Or Implied Warranty. Nor Is There Any Guarantee That The Information Contained In This Document Is Accurate. Every Effort Has Been Made To Make All Articles As Complete And As Accurate As Possible.
It Is Offered In The Hopes Of Helping Others, But You Use It At Your Own Risk. The Author Will Not Be Liable For Any Special, Incidental, Consequential Or Indirect Any Damages Due To Loss Of Data Or Any Other Reason That Occur As A Result Of Using This Document. But No Warranty Or Fitness Is Implied. The Information Provided Is On An "As Is" Basic. All Use Is Completely At Your Own Risk.
The School Of Cisco Networking (SCN)
No comments:
Post a Comment