Basic Ripv2

This is a basic RIPv2 topology using GNS3. GNS3 is a great program if you get a chance to use it, I like all the functionality it has to it.

So some facts/updates about RIPv2

  •     Distance Vector Protocol 
  •     Routing updates sent via multicast at 224.0.0.9  as opposed to RIPv1 which uses broadcast
  •     You must enable version 2 when configuring !  " version 2" ( You will see the configuration down the page)
  • Administrative Distance of 120

So now that we have a couple updates on RIPv2 we are going to configure a basic RIP topology and when you're done you should be able to go to R1 and see the following "show ip route":

   1.0.0.0/32 is subnetted, 1 subnets
C       1.1.1.1 is directly connected, Loopback0
     2.0.0.0/32 is subnetted, 1 subnets
R       2.2.2.2 [120/2] via 172.19.33.2, 00:00:20, FastEthernet0/0
     3.0.0.0/32 is subnetted, 1 subnets
R       3.3.3.3 [120/1] via 172.19.33.2, 00:00:20, FastEthernet0/0
     172.19.0.0/30 is subnetted, 2 subnets
R       172.19.38.0 [120/1] via 172.19.33.2, 00:00:20, FastEthernet0/0
C       172.19.33.0 is directly connected, FastEthernet0/0


As you can see above we see all of the routes for the loopback interfaces that we made as the potential networks behind the router.

Network Configuration:

R1

interface loopback 0 
ip add 1.1.1.1 255.255.255.255 ( All 255's is the same as a /32 )
no shut
description R1 Fake Network


interface fa0/0
ip add 172.19.33.1 255.255.255.252 ( We make it a /30 for the two IP's needed on both ends of the connection)
no shut
description Link to R3 ( Whenever you can always use descriptions ! )

router rip  ( Enable RIP Routing Protocol)
version 2  ( This enables RIPv2 otherwise we would have version 1)
network 1.1.1.1 
network 172.19.33.0
no auto-summary ( This configuration allows you to have classless networks being advertised instead of classful so if we only want to advertise 1.1.1.1/32 we use "no auto summary" but naturally 1.1.1.1 is a class A so we would see if advertised as 1.0.0.0)


R3

interface loopback 0
ip add 3.3.3.3 255.255.255.255
no shut
description R3 Fake Network


interface fa0/0
ip add 172.19.33.2 255.255.255.252
no shut 
description Link to R1

interface fa0/1
ip add 172.19.38.2 255.255.255.252
no shut
description Link to R2


router rip 
version 2
network 3.3.3.3
network 172.19.33.0
network 172.19.38.0
 (  RIP Routing Table will automatically make the 172.19.X.X addresses into 172.19.0.0 which we could configure as well but for an example to see both network configurations we will configure both) 
network 172.19.38.0 and 172.19.33.0)
no auto-summary



R2


interface loopback 0
ip add 2.2.2.2 255.255.255.255
no shut
description R2 Fake Network


interface fa0/1
 description Link to R3
 ip address 172.19.38.1 255.255.255.252
no shut

router rip 
version 2
network 2.2.2.2
network 172.19.38.0
no auto-summary 






















Comments

Post a Comment

Popular posts from this blog

HULC LED PROCESS - 3750 High CPU

Image
If you're looking at a switch and you see the HULC LED Process running high. The HULC LED process does some of the following tasks: 1. Check link status on every port 2. If the switch supports POE, it checks to see if there is a power device 3. Transceiver checks 4. Fan status updates 5. Set LED ports 6. Check on temperature status Overall the HULC LED Process is a monitoring process running. During looking into this I turned off all non-used ports since it checks the link status. Then I made sure the environment was good. Two Cisco Bugs: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsi78581 http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn42790
Read more

%PLATFORM_UCAST-4-PREFIX: --------- TCAM 3750 Switch

Image
 %PLATFORM_UCAST-4-PREFIX:  One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefix, and the packets may be software forwarded So what is TCAM ? Ternary Content Addressable Memory is used in multi-layer switching also know as Layer 3 switching. The switches forward the packets and frames at the speed of the line by using ASIC hardware. Normally switches make there forwarding decisions based on Layer 2. TCAM is used for Layer 3 components and other features such as QOS and ACES ( Access List ).  Check TCAM and usage of templates being used in the device.  show sdm prefer ? ! This will show us the templates that can be used in the device to give more resources to one feature or the other. For example the default is the equal resource distribution while the routing gives more resources to Layer 3 routing. show sdm prefer ! The command without the "?" will show us what we are currently r
Read more