Ubuntu basic guidelines  

Thursday, November 27, 2008

simple steps to follow ..

* those who want to install ubuntu linux can order their copy for free at

http://www.ubuntu.com/getubuntu

you can either download or request it .. i would ask you to do both of them ....

* check the compatability with your system most of the desktops should not have problems what so ever .. even all of the laptops are covered well except some of the wifi part

* as linux ships with many of the non commercial softwares you cant even play mp3 files .. for that you need enable repositories .. you can find the entire guide here

http://ubuntuguide.org/wiki/Ubuntu:Hardy

* downloading and installing is straight foreward for gns3 ... it should work well other wise browse any of the docs or blindhog ..

after you could install gns3 its all same from there on .... there is a package called compiz fusion which is rocking for eyes .. the guis effects are to bee seen by everyone who hadnt

any help let me know via mail wink.gif

regards
raaki

Linux flavor  

my health is not supporting me these days as there is a climate change .. neverthless .. i have made some advancements ...

i have got craze for linux and installed a red hat 9 in my school days on a old compaq computer .. from then on there was some thing or other which was poking at me .. coming back ..

as i have already told you that i would increase my ram for gns3 soft run . but now i have changed my mind to postpone it .. the reason is linux

beleive me or not .. linux has a better management of ram and memory than windows which i used to use for previous labs ..

i have installed ubuntu 8.04 64 bit edition .. had some problems with wifi and vga stuff fixed all of the issues in these two days .. installed gns3 .. obviously not successful in my first attempt due to some of the mistakes but saw it now and posting it immediately ..

i could start upto 17 routers in gns3 with linux in hand .. dint done any lab on it though ... and observed memory ...

firstly the memory was at 919mb out of total 1.7gb availabe ram memory .. and swap memory was around 3.8 which is double the ram ofcourse ..

now i have installed 4 of routers and ram increased to 1100mb and from there on it stopped increasing even though i have increased the number of routers .. the reason being swap memory is taking over it now .

yes the ram memory increase stopped at 1100 mb and virtual memory began to increase . virtual memory = swap memory and so i could increase number of routers to greater extend without any system hang .

so i would recommend ubuntu for users who has a memory hang experiences with their pc's . also tried with dynamips .. but i couldnt do it for long ... as i am used to gns3 ..

so all in all instruments are sharper again for me ...

guday

done with the shit  

Monday, November 24, 2008

today as mentioned went to prometric partner for the scheduled exam 70-113 which was offered free by microsoft and discovered that information cannot be retrieved from the server for this exam . i am dissapointed as i had put some quality time for the past 4 days and effort .. ne ways got to get down with cisco ... my apologies for giving you the advise to take the exam .. meet you redistribution lab

regards
rakesh

UPDATE ON MY STAT  

Saturday, November 22, 2008

few updates from my side my university exams for this sem have been completed by today and still 3 more sems to go ... ;( and i have paused cisco side a little bit just because of one reasoni got a mail from microsoft website stating that there is a free exam on 70-113 if passed and present in first 3000 would walk away with 3 vouchers .. of course iam not that lucky nor in need of microsoft certs .. but just to attempt a international cert for free .. i have installed windows server 2008 and i must agree its rocking fast .. yes, it is running like dream ... superb effort from microsoft i should say .. i have scheculed from microsoft exam this monday so as i would prepare these two days and leave it off instead of wasting holidays as i need to concentrate on cisco stuff ... and also from the hardware part iam trying to upgrade my ram to 4gb for smooth gns3 run ... this is it . i will let you know how exam went .. i would recommend any one having free time to take this exam as it is of free of cost .. just a small advice .. for further details you can search for 70-113 and you will get to know everything .. guday

Thursday, November 20, 2008

you can reach Mr.darby Weaver at darbylogs.blogspot.com

Setting the Clock and Timezone
------------------------------------

Given the last tip this one goes without saying. Set it as close to real time as possible and use GMT if you have multiple timezones for devices you manage or use the local timezone otherwise.

Very helpful.

Darby# clock set 1:18:00 November 18 2008
Darby# conf t
Darby# clock timezone EST -5
Darby# clock summer-time EDT recurring

Use show clock to verify.

Display an Interface Config
-------------------------------

sh run int f0/0

Now you can do even more:

sh run section router


Erasing an Interface Config
-------------------------------

Simple one but that may not be known about or easily forgotten in a pinch:

default interface f0/0

Works great it just wiped all configuration from that interace. Ready to start again. Kinda like Play-Do or Silly Putty but in a Router or Switch.

Setting the Terminal Length of a Router, Switch, or Firewall.
--------------------------------------------------------------------

24 lines ain't enough sometimes.

I backup configs a lot before and after I am doing things so... I don't like the page breaks that are arbitrarily assumed.

So...

term length 0 works on a router or switch and pager length 0 works on a PIX/ASA.

The default is 24, so...

"term len 24" sets it back to normal on a router/switch or pager length 24 on a PIX/ASA.

I find that a full screen is about 36 lines... but it may vary based on your screen's resolution.

Filtering the Output of commands
--------------------------------------

This is cool but gets even cooler once you begin to master regular expressions.

Here's some simple examples:

sh run begin route eigrp

sh run include ip route

sh ip interface brief exclude Down

I also use it alot when I'm hunting down a mac or ip address... Kewl stuff.

You can use regular expressions to get make if more grep-like...


Also remember show run section XXX works great too.

Do Command
----------------

This command allows us to "execute" commands while we are in configuration mode.

Darby(config-if) do sh run interface f0/0

We can use aliases and emulate the "Do Command's" functionality as well.

Alias Commands
-------------------

We can use this command feature to create our own commands.

alias exec s sh ip interface brief
alias configure s sh ip int brief (note this is so the same shortcuts will work in other modes on the device as well).

Only cause I find myself typing do out of context after I've been using it for a while.

Privilege Levels
------------------

This is a very useful tool for network management. By default all commands are either privilege level 0 or 15.

You are either poor or rich...

The privilege level command allows us the ability to create a few middle classes....


privilege level <0-15>

Darby(config)# privilege exec level 2 show
Darby(config)# privilege exec level 2 show ip route

line vty 0 15
privilege level 2

Assigns the default privilege level of 2 to vty sessions 0-15 for an example.

username Darby privilege level 2 password Darby

line vty 0 15
login local

Assigns the user Darby with a privilege level of 2 for another example. We also ensure that vty logins use the local database in this case.


Stopping "The Runaway Debug"

Plenty of ways to help solve this issue.

1. undebug all - make an alias for it like this

alias exec u undebug all

2. Use conditional debugging

debug interface f0/0

3. Filter the debug

access-list 1 permit ip 10.1.1.1 0.0.0.0

debug ip packet 1

Editing Access-lists
----------------------

Alway try to document when possible - use descriptions and remarks and names that are self-documenting.

Extended Access-lists permit us to edit the acl by line number.

No Service Configuration
-----------------------------

Speaks for itself.

Sometimes you'll find a device that is booting really slow and later find it is trying to boot from tftp somewhere...

Maybe you don't want your device to do this.

This can slow you down a lot. Really. A whole lot.

Hope these tips help you a bit.

CISCO IOS TRICKS AND TIPS  

This is not my work . The entire credit goes to Mr.Darby Weaver . you can reach him at darbylogs.blogspot.com

Cisco IOS Tips and Tricks..

You probably know these by now but jus in case you don't:

- Auto-completing commands
- Disabling DNS server lookup
- Limiting EXEC interruptions
- Setting console speed
- Deprecated commands
- Time-stamping messages
- Setting the clock and time zone
- Displaying the interface of a config
- Filtering the output of commands
- Erasing an interface config
- Setting the Terminal Length of a Router, Switch, or Firewall
- The DO command
- Alias Commands
- Privilege levels
- Changing the TCP timeout
- Stopping "The Runaway Debug"
- Editing access-lists
- No service config



Auto-Completion of commands
-----------------------------------

It's only necessary to type enough letters of any given command to make the command unique at the current configuration mode.

Then use the key to autocomplete.

I normally use this method daily and accompany it with the character to help me remember options or to learn whatever options are available to me just beyond the prompt.

Note: The ? is very helpful since you are probably like me and work with a wide array of devices and IOS versions.

Disable DNS Server Lookups
--------------------------------

When you type something at the prompt that is not a command the IOS tries to telnet to it. It's a smart tool like that and I really appreciate it on my Access Server, example R1, R2, R3, etc.

I do not like what it does to my day to day typos and if you read my posts I make a lot of typos.

"no ip domain lookup" in global configuration mode and this little pesky time-consuming issue is resolved.

Limit EXEC Interruptions
----------------------------

This is a great little tool for me. I love it and use it everywhere. Basically it ensures that no matter how many messages I receive at the prompt while I'm typing I never lose my place. So I do not get "interrupted". Put it in your toolbag. It's very helpful.

conf t
line vty 0 15
no logging synchronous

Setting the Console Speed
------------------------------

This is great just to get access to a Cisco device. But did you ever consider using it as a security tool? I mean if you have junior admins and who doesn't or "helpful peeps" from other departments...

This is priceless. BTW - It has saved me on some otherwise priceless pieces of gear bought on ebay. Note: I always look for the sh ver on "junk" that is sold to be non-working... Some folks never heard of a config register before.

Hah!

Anyway here you go:

line console 0
speed 115200

This also saved me in a pinch when I needed to transfer IOS over the Serial line... It's happened to me and could happen to you. 115200 may not be speeding in some countries, but it beats 9600 bps.

Deprecated Commands
---------------------------

Some very helpful commands are no longer supported by Cisco, but I love em anyway.

OLD Command New Command
wr (write) copy run start
wr er (write erase) erase start
who show users
whe (where) show users

Oh yes... who = "w" for those who don't like to type much.

show alias will show you others...

"p" = ping

How about that for a time saver.


Timestamping Messages
----------------------------

I once worked with a hot-shot Security guy... who... started configuring his Mars and other Logging devices and did not seem to recognize the importance of setting and synchonizing his time servers first...

I even took the time to draw it out in Visio. But since it was his job to make me look like the village idiot... it fell of deaf ears...

True story by the way...

So I did not both finishing my tail about Timestamping with our super-star.

For the rest of the world...

Ever get timestamps with the wrong date or time?
How about debugs too?

Yep... I hate non-timestamped logs...

I love time-stamped logs and debugs.
I love time-stampted loge and debugs with sequence numbers even better.

service timestamps (log|debug) datetime localtime
service sequence-numbers

Use them to your heart's content.

Look like a hero to your boss and coworkers.

My best advice is use them everywhere. Then you can track things when they happen even across an entire enterprise.

Cool huh?

PLAN  

Monday, November 17, 2008


* this completed the eigrp revision and i will be back on redistribution lab 2 very soon ..or may start of with the revision of ospf or bgp depending upon my time availability .. after 24 th i will be surely after redistribution and will knock it off in two days

EIGRP REVISION CONTINUED 2  

Eigrp Authentication:

* 3 parts to remember while configuring Authentication

* key creation and management

* Authentication mode

* assigning key to an interface

* key chain should be configured first and this is done under global configuration mode

* Create key

* Create key string , send lifetime , accept lifetime

* Info configured can be seen by issuing the command SHOW KEY CHAIN

* Next step is to apply it to an interface

* ip authentication eigrp 1 mode md5 ---> this is the authentication mode

* all constructed elements should be relevant and also they must and should be case sensitive with key strings and authentication modes being equal

Default Information originate and How to avoid it :

* In order to suppress the default routes , we can go into the router config mode of eigrp and issue the command as follows

* ROUTER EIGRP 1 ---> NO DEFAULT-INFORMATION IN


CREATION OF DEFAULT ROTUE:

* If we want to have a default route , we have more than one way to do it

* If we have a static route configured , redistribute the static route with a some of the default metric value

* Another way is to use the summary address in the interface level config mode to accomplish this task

* INT FA0/0 ---> IP SUMMARY-ADDRESS 0.0.0.0 0.0.0.0


Eigrp Load Balancing:

* By default eigrp loadbalances across 4 equal cost paths

* We can change the number of paths any where between 0-6 with the issue of MAXIMUM PATH command in router config mode

* For unequal load balancing we can use the VARIANCE COMMAND which ranges from 0-128

* This is done under router config mode
VARIANCE X --->it load balances between the routes which are x times more than the best one

* This is cost based load balancing sharing 1:x(will be done based on the variance level ) ratio of packet traffic

* If we want to alter this , this can be done under router configuration mode

* ROUTER EIGRP 1 ---> TRAFFIC SHARE MIN

* In this way the minimum cost will be preffered

* If we want to revert back to normal behaviour it should be done again in the router config mode
ROUTER EIGRP 1 ----> TRAFFIC SHARE BALANCED ----> defaults will be applied

* As a side note route tagging can also be used to acheive this task


EIGRP TIMERS :

* Update timer : rate at which updates are being sent

* Invalid timer: the time interval after which a route is declared as invalid

* Hold timer: how long the route is holded on depending on the other routes received

* Flush timer: the time after which the route is removed from the routing table

* Hello timer: hello interval defines how often hello packets are sentout which are used to establish neighbouring relationships

* On t1 or faster interfaces the dafault value being 5 secs and on nbma or slower links the timer value being 60 seconds

* If we want to change the timers , it should be done both ends and also this behaviour also applies to bandwidth command

* SHOW IP PROTOCOLS can be used to check the values

* The change should be done across the interface level
IP HELLO-INTERVAL EIGRP 100 15 --> this sets the interval to 15

* The same confiuration can be done for the HOLD time changes

* By default the hold time will be 3 times more than the hello timer

* Changing one timer will not change the other timer

* ACTIVE TIMER : this is used to minimize the effect of STUCK IN ACTIVE problem

* THIS CAN BE DONE ---> ROUTER CONFIG MODE ---> ROUTER EIGRP 1 ---> TIMERS ACTIVE TIME 180

SPLIT HORIZON:

* May arise with secondary/multipoint situations

* can be closed down under interface level configuration mode

* INT FA0/0 ---> NO IP SPLIT HORIZON EIGRP 100 ---> this disable split horizon

* We can also use VALIDATE UPDATE SOURCE command mostly done with secondary address in place

* ROUTER EIGRP 1 ---> NO VALIDATE UPADTE SOURCE

* you may land up with an error in times "ROUTER NOT ON COMMON SUBNET"


EIGRP STUB ROUTING:

* CONFIGURATION IS DONE UNDER ROUTER MODE

* EIGRP STUB ---> can have different parameters

* receive-only , connected , static , summary all of them being obvious and the point is to redistribute



* also not all the config commands are from console line so of them may have hifuns (-) between them or not i just used them


regards
rakesh


EIGRP REVISION CONTINUED 1  

Offset lists:

* Another way to adjust metrics

* No need to modify K-values

* Can be used to manipulate metric for one of the multiple routes pointing to the same destination

Configuration:

* Create an access-list

* Create an offset-list

* ACCESS-LIST 10 PERMIT X.X.X.X Y.Y.Y.Y

* ROUTER EIGRP 4
OFFSET-LIST 13 IN 160000 FA0/0

A metric of 16000 would be added and will replace the old metric which is calculated
Route-summaraisation:

* Turn-off summaraisation with no auto-summary command

* Done under the router eigrp process ROUTER EIGRP 1 ---> NO AUTO

* Interface level summaraisation (this is what we do when we go for manual summaraisation and should be done at interface level)

* INT FA0/0 IP --> IP SUMMARY-ADDRESS EIGRP 1 NETWORK MASK

* Immediately a routing update is sent out

* On local router a summary-address for null0 interface will be generated

* In newer ios images a D route will be generated


Bandwidth:

* Eigrp uses 50% of bandwidth by default

* This may lead to some of the miscalculations which are to be considered crucial in qos and traffic-shaping

* Serial-interface which is t1 line or greater will be considered as 1.5megs as default

* This should be modified with the help of the bandwidth command in the interface level

* Also bandwidth percentage can be controlled with the interface level ip bandwidth-percent command

* ip bandwidth percent eigrp 1 10 to modify the percentage to 10% under as 1



EIGRP REVISION  

Friday, November 14, 2008

the points are scattered so please dont mind

* Eigrp may be termed as enhanced igrp . defined as hybrid with both distance vector and link state .. but to be precise may be termed as advance distance vector routing protocol out there

* It works on on local link multicast exchange 224.0.0.10

* Neighbor process or discovery is done with the help of exchange of hello exchage . neighbours are alive till hellos are exchanged

* For multicast exchange , all of the interfaces must be of multicast capable .. this includes atm / frame - relay concepts

* The neighbor discovery process is done via hello packets that are exchanged via multicast

* Eigrp offers multiprotocol support ip , ipx , appletalk

* Eigrp provides RTP RELIABLE TRANSPORT PROTOCOL . through this packets can be exchanged via unicast / multicast

* The point to remember is that Hello packets are not needed to be reliable

On to the algorithm and routing proc

* DUAL - diffusing update algorithm . responsible for processing , installing and maintaining routes

* Also has to offer list of routes for feasible successors and successors via next hop

* If no feasible successor is present , or route goes down Recomputation is done

* Recomputation is processor intensive and uses dual to see the neig relationships again

* Table in eigrp include NEIGHBOR TABLE , TOPOLOGY TABLE , ROUTING TABLE

* Neighbor table contains adjacent neighbors , how neighbors has been discovered , interfaces , hold time , neighbor id , transmissions

* Topology table . this is done by the protocol module .. ie if we are running eigrp under ip , the table will be populated by ip protocol

* This is the backbone . it contains all destination routes advertised by neigh , metrics , perfixed , list of neigh , and for each route there will be metric which is advertised

* The route with best metric will be forewarded to the routing table . it is termed as successor ie primary path

* Feasible successor more or less like a back up path . one path can have multiple feasible successors . if successor goes down it will replace by fs and for replacement no recomputation is necessary

NEIGHBOR OPTIONS IN EIGRP

* Neighbor table is dynamically built as it receives hellos from different neighbors

* SHOW IP EIGRP NEIGH can be used for viewing neigh , addr , int , neigh

* NEIGHBOR COMMAND is to statically specify neighbors and also should be specified with the interface with which it can be reached . this is used to establish unicast routing

neig 100.0.0.10 fa0/0

* The results can be seen by the SHOW RUN , SHOW IP PROTOCOLS

* SHOW IP EIGRP NEIGHBORS will not list it because you need to have neighbor command done on both neig routers

* PASSIVE INTERFACE cannot be done on eigrp as it uses multicast hellos and hellos are to be sent in order to have a neigbor relation ship

* If we are asked to configure a passive interface in eigrp a simple way to do is to configure DISTRIBUTE LISTS .

* Create an access-list denying all traffic and place in the router process with the help of distribute list

ACCESS-LIST 30 DENY ANY

DISTRIBUTE-LIST 30 OUT


MORE INTO SIMPLE CONFIS AND METRICS

* METRICS OR K VALUES bandwidth , load ,delay , reiablilty , mtu .

* SIA ERROR stuck in active . this is where when mentioned no fs can be found for the topology table . the problem is that it wont have any timeout period and sia packet goes on and on till it gets a yes or no reply from neigh . if the router is busy to respond to this sia packet more time will be taken for recomputation

* Three simple steps

enabling routing protocol

defining as number

giving network command

* ROUTER EIGRP 125
NETWORK X.X.X.X
NO AUTO ------------ to turn off auto summaraisation

* SHOW IP PROTOCOLS can be used to see timers , neigh , metrics

k-values can be seen here .

* A K VALUE IS A 32 BIT NUMBER / MODIFIER .. SO IF YOU CHANGE VALUE OF K OR INCREASE A K VALUE BY ONE IT WILL AFFECT HUGELY

* metric can be best viewed with show ip route command

* K-values can be modified with the help of metric weights command

METRIC WEIGHTS ALWAYS START WITH ZER0 AND FOLLOWED BY K1 . K2 , K3 , K4 , K5

DEFAULT VALUES ARE 1 0 1 0 0

BANDWIDTH , LOAD , DELAY , RELIABILITY , MTU


these are few of the updates from me .. need to update blog ..it is lagging like hell lol smile.gif ... i will continue with the eigrp revision part ..

good luck at what ever you do and also wish me

regards
RAKESH





A SMALL CHANGE IN PROGRAM  


left with 3 of the redistribution labs but my time sucks and the factor is due to my external exams which are going on in my coll .. my bad .. iam after big some thing and i will keep it as a surprise till 24th of this month ..so after 24th probably you may expect me to do the labbing again .... just a zeal for the things which are going or which can be grabbed free of cost officially wink.gif

so i have decided not to go off the track and started revising the router core technologies from various parts of the world wink.gif including both the experts out there

here are some of the points worth noting about eigrp .. and do you know one thing ? it is damn easy to hear a audio boot camp ..but try like this .. try writing down the important points and you will soon see the play and sport in it ..it real hard to jot down the important points ..because of two reasons .one every point in a audio boot camp is important and other you need to revise it for atleast 4 times ... for a 15 min audio i took nearly 1 hr do jot a rough note how horrible my writing and learning speeds are any ways it improves me ..

so i would be highlighting some of the points from eigrp which i found important in my self study

good luck

regards
RAKESH

TWO WAY REDISTRIBUTION  


or use a two way redistribution

CODE
r2(config-router)#redistribute rip subnets ?
metric Metric for redistributed routes
metric-type OSPF/IS-IS exterior metric type for redistributed routes
route-map Route map reference
tag Set tag for routes redistributed into OSPF


r2(config-router)#redistribute rip subnets metric-type ?
1 Set OSPF External Type 1 metrics
2 Set OSPF External Type 2 metrics

r2(config-router)#redistribute rip subnets metric-type 1 metric 1000
r2(config-router)#end
r2#
*Mar 1 01:10:28.123: %SYS-5-CONFIG_I: Configured from console by console
r2#
as#2
[Resuming connection 2 to r3 ... ]

r3#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

C 192.168.30.0/24 is directly connected, Loopback30
C 192.168.25.0/24 is directly connected, Loopback25
C 192.168.40.0/24 is directly connected, Loopback40
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
O E1 172.16.12.0/24 [110/1064] via 172.16.23.2, 00:00:05, Serial2/1
O E1 172.16.1.0/24 [110/1064] via 172.16.23.2, 00:00:05, Serial2/1
C 172.16.3.0/24 is directly connected, Loopback0
O 172.16.2.1/32 [110/65] via 172.16.23.2, 00:04:35, Serial2/1
C 192.168.20.0/24 is directly connected, Loopback20
C 192.168.35.0/24 is directly connected, Loopback35
O E1 192.168.70.0/24 [110/1064] via 172.16.23.2, 00:00:05, Serial2/1
O E1 192.168.48.0/22 [110/1064] via 172.16.23.2, 00:00:05, Serial2/1
r3#

r3#ping 192.168.70.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.70.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 52/79/120 ms
r3#


this is with the redistribution lab 5-1 and all of the redistribution labs are relatively big ...

guday

regards
raaki

SETTING DEFAULT ROUTE  

setting a default route will do the trick

CODE
r2#config t
Enter configuration commands, one per line. End with CNTL/Z.
r2(config)#router ospf 1
r2(config-router)#default-information originate always
r2(config-router)#end
r2#

r1#ping 192.168.30.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/72/124 ms
r1#


CODE
r3#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 172.16.23.2 to network 0.0.0.0

C 192.168.30.0/24 is directly connected, Loopback30
C 192.168.25.0/24 is directly connected, Loopback25
C 192.168.40.0/24 is directly connected, Loopback40
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
C 172.16.3.0/24 is directly connected, Loopback0
O 172.16.2.1/32 [110/65] via 172.16.23.2, 00:02:54, Serial2/1
C 192.168.20.0/24 is directly connected, Loopback20
C 192.168.35.0/24 is directly connected, Loopback35
O*E2 0.0.0.0/0 [110/1] via 172.16.23.2, 00:02:54, Serial2/1 -------*
r3#

REDISTRIBUTION OF PROTOCOLS  

next step is to redistribute two of the protocols for full connectivity

CODE
r2(config-router)#redistribute ospf 1 metric 4
r2(config-router)#end
r2#
*Mar 1 01:01:54.671: %SYS-5-CONFIG_I: Configured from console by console
r2#
as#1
[Resuming connection 1 to r1 ... ]

r1#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

192.168.30.0/32 is subnetted, 1 subnets
R 192.168.30.1 [120/4] via 172.16.12.2, 00:00:07, Serial2/0
192.168.25.0/32 is subnetted, 1 subnets
R 192.168.25.1 [120/4] via 172.16.12.2, 00:00:07, Serial2/0
192.168.40.0/32 is subnetted, 1 subnets
R 192.168.40.1 [120/4] via 172.16.12.2, 00:00:07, Serial2/0
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
R 172.16.23.0/24 [120/1] via 172.16.12.2, 00:00:07, Serial2/0
C 172.16.12.0/24 is directly connected, Serial2/0
C 172.16.1.0/24 is directly connected, Loopback0
R 172.16.3.1/32 [120/4] via 172.16.12.2, 00:00:07, Serial2/0
R 172.16.2.0/24 [120/1] via 172.16.12.2, 00:00:07, Serial2/0
192.168.20.0/32 is subnetted, 1 subnets
R 192.168.20.1 [120/4] via 172.16.12.2, 00:00:08, Serial2/0
C 192.168.51.0/24 is directly connected, Loopback51
C 192.168.50.0/24 is directly connected, Loopback50
192.168.35.0/32 is subnetted, 1 subnets
R 192.168.35.1 [120/4] via 172.16.12.2, 00:00:08, Serial2/0
C 192.168.49.0/24 is directly connected, Loopback49
C 192.168.70.0/24 is directly connected, Loopback70
192.168.48.0/24 is subnetted, 1 subnets
C 192.168.48.0 is directly connected, Loopback48
S 192.168.48.0/22 is directly connected, Null0


r1#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 192.168.30.1 [120/4] via 172.16.12.2, 00:00:19, Serial2/0
R 192.168.25.1 [120/4] via 172.16.12.2, 00:00:19, Serial2/0
R 192.168.40.1 [120/4] via 172.16.12.2, 00:00:19, Serial2/0
R 172.16.23.0/24 [120/1] via 172.16.12.2, 00:00:19, Serial2/0
R 172.16.3.1/32 [120/4] via 172.16.12.2, 00:00:19, Serial2/0
R 172.16.2.0/24 [120/1] via 172.16.12.2, 00:00:19, Serial2/0
R 192.168.20.1 [120/4] via 172.16.12.2, 00:00:19, Serial2/0
R 192.168.35.1 [120/4] via 172.16.12.2, 00:00:19, Serial2/0
r1#ping 192.168.30.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
r1#traceroute 192.168.30.1

Type escape sequence to abort.
Tracing the route to 192.168.30.1

1 172.16.12.2 56 msec 72 msec 28 msec
2 * *
r1#

could you see the problem ?

CONFIGURING PASSIVE INTERFACES  

configuring passive interfaces in ospf

CODE
r3#

r3#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

C 192.168.30.0/24 is directly connected, Loopback30
C 192.168.25.0/24 is directly connected, Loopback25
C 192.168.40.0/24 is directly connected, Loopback40
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
C 172.16.3.0/24 is directly connected, Loopback0
O 172.16.2.1/32 [110/65] via 172.16.23.2, 00:34:42, Serial2/1
C 192.168.20.0/24 is directly connected, Loopback20
C 192.168.35.0/24 is directly connected, Loopback35
r3#config t
Enter configuration commands, one per line. End with CNTL/Z.
r3(config)#do siib
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 unassigned YES NVRAM administratively down down
FastEthernet0/1 unassigned YES NVRAM administratively down down
Ethernet1/0 unassigned YES NVRAM administratively down down
Ethernet1/1 unassigned YES NVRAM administratively down down
Ethernet1/2 unassigned YES NVRAM administratively down down
Ethernet1/3 unassigned YES NVRAM administratively down down
Serial2/0 unassigned YES NVRAM administratively down down
Serial2/1 172.16.23.3 YES NVRAM up up
Serial2/2 unassigned YES NVRAM administratively down down
Serial2/3 unassigned YES NVRAM administratively down down
Loopback0 172.16.3.1 YES NVRAM up up
Loopback20 192.168.20.1 YES NVRAM up up
Loopback25 192.168.25.1 YES NVRAM up up
Loopback30 192.168.30.1 YES NVRAM up up
Loopback35 192.168.35.1 YES NVRAM up up
Loopback40 192.168.40.1 YES NVRAM up up


r3(config)#router ospf 1
r3(config-router)#passive-interface default
r3(config-router)#
*Mar 1 00:57:38.575: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.2.1 on Serial2/1 from FULL to DOWN, Neighbor Down: Interface down or detached
r3(config-router)#no passive-interface s2/1
r3(config-router)#
*Mar 1 00:57:47.591: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.2.1 on Serial2/1 from LOADING to FULL, Loading Done

-----------------------------------------------------------------------

r3(config-router)#do show ip proto
Routing Protocol is "ospf 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 192.168.40.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
172.16.3.1 0.0.0.0 area 0
172.16.23.3 0.0.0.0 area 0
192.168.20.1 0.0.0.0 area 0
192.168.25.1 0.0.0.0 area 0
192.168.30.1 0.0.0.0 area 0
192.168.35.1 0.0.0.0 area 0
192.168.40.1 0.0.0.0 area 0
Reference bandwidth unit is 100 mbps
Passive Interface(s):
FastEthernet0/0
FastEthernet0/1
Ethernet1/0
Ethernet1/1
Ethernet1/2
Ethernet1/3
Serial2/0
Passive Interface(s):
Serial2/2
Serial2/3
Loopback0
Loopback20
Loopback25
Loopback30
Loopback35
Loopback40
Routing Information Sources:
Gateway Distance Last Update
172.16.2.1 110 00:00:19
Distance: (default is 110)

r3(config-router)#

INTERMEDIATE STAGES  


intermediate stage

CODE
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:08, Serial2/0
R 192.168.51.0/24 is possibly down, routing via 172.16.12.1, Serial2/0 ----------> ****
R 192.168.50.0/24 is possibly down, routing via 172.16.12.1, Serial2/0
R 192.168.49.0/24 is possibly down, routing via 172.16.12.1, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:08, Serial2/0
R 192.168.48.0/24 is possibly down,
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:08, Serial2/0
r2#



final stage after filtering and flushing the routes

CODE
r2#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

192.168.30.0/32 is subnetted, 1 subnets
O 192.168.30.1 [110/65] via 172.16.23.3, 00:32:59, Serial2/1
192.168.25.0/32 is subnetted, 1 subnets
O 192.168.25.1 [110/65] via 172.16.23.3, 00:32:59, Serial2/1
192.168.40.0/32 is subnetted, 1 subnets
O 192.168.40.1 [110/65] via 172.16.23.3, 00:32:59, Serial2/1
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
C 172.16.12.0/24 is directly connected, Serial2/0
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:14, Serial2/0
O 172.16.3.1/32 [110/65] via 172.16.23.3, 00:32:59, Serial2/1
C 172.16.2.0/24 is directly connected, Loopback0
192.168.20.0/32 is subnetted, 1 subnets
O 192.168.20.1 [110/65] via 172.16.23.3, 00:33:00, Serial2/1
192.168.35.0/32 is subnetted, 1 subnets
O 192.168.35.1 [110/65] via 172.16.23.3, 00:33:00, Serial2/1
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:15, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:15, Serial2/0

------------------------------------------------------------------------------------------------
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:21, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:21, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:21, Serial2/0
r2#



IMLEMENTING DISTRIBUTE LIST  


implementing disribute lists

CODE
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
R 192.168.48.0 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:26, Serial2/0
r2#
as#1
[Resuming connection 1 to r1 ... ]

r1#config t
Enter configuration commands, one per line. End with CNTL/Z.
r1(config)#ip prefix-list ?
WORD Name of a prefix list
sequence-number Include/exclude sequence numbers in NVGEN

r1(config)#ip prefix-list rakesh ?
deny Specify packets to reject
description Prefix-list specific description
permit Specify packets to forward
seq sequence number of an entry

r1(config)#ip prefix-list rakesh permit ?
A.B.C.D IP prefix /, e.g., 35.0.0.0/8

r1(config)#ip prefix-list rakesh permit 192.168.48.0/22
r1(config)#ip prefix-list rakesh deny 192.168.48.0/22 ?
ge Minimum prefix length to be matched
le Maximum prefix length to be matched


r1(config)#ip prefix-list rakesh deny 192.168.48.0/22 le ?
<1-32> Maximum prefix length

r1(config)#ip prefix-list rakesh deny 192.168.48.0/22 le 24
r1(config)#ip prefix-list rakesh permit 0.0.0.0/0 le 32
r1(config)#router rip
r1(config-router)#distribute-list ?
<1-199> IP access list number
<1300-2699> IP expanded access list number
WORD Access-list name
gateway Filtering incoming updates based on gateway
prefix Filter prefixes in routing updates

r1(config-router)#distribute-list prefix ?
WORD Name of an IP prefix-list

r1(config-router)#distribute-list prefix rakesh ?
gateway Filtering incoming updates based on gateway
in Filter incoming routing updates
out Filter outgoing routing updates

r1(config-router)#distribute-list prefix rakesh out serial 2/0
r1(config-router)#
as#3
[Resuming connection 3 to r5 ... ]


r2#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

192.168.30.0/32 is subnetted, 1 subnets
O 192.168.30.1 [110/65] via 172.16.23.3, 00:28:44, Serial2/1
192.168.25.0/32 is subnetted, 1 subnets
O 192.168.25.1 [110/65] via 172.16.23.3, 00:28:44, Serial2/1
192.168.40.0/32 is subnetted, 1 subnets
O 192.168.40.1 [110/65] via 172.16.23.3, 00:28:44, Serial2/1
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
C 172.16.12.0/24 is directly connected, Serial2/0
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
O 172.16.3.1/32 [110/65] via 172.16.23.3, 00:28:44, Serial2/1
C 172.16.2.0/24 is directly connected, Loopback0
192.168.20.0/32 is subnetted, 1 subnets
O 192.168.20.1 [110/65] via 172.16.23.3, 00:28:45, Serial2/1
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:37, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:37, Serial2/0
192.168.35.0/32 is subnetted, 1 subnets
O 192.168.35.1 [110/65] via 172.16.23.3, 00:28:45, Serial2/1
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:37, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:11, Serial2/0
192.168.48.0/24 is subnetted, 1 subnets
R 192.168.48.0 [120/1] via 172.16.12.1, 00:00:37, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:11, Serial2/0
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:54, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:54, Serial2/0
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:54, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.48.0 [120/1] via 172.16.12.1, 00:00:54, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:09, Serial2/0
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:01:03, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:01:03, Serial2/0
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:01:03, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:09, Serial2/0
R 192.168.48.0 [120/1] via 172.16.12.1, 00:01:03, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:09, Serial2/0
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:12, Serial2/0
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:01:06, Serial2/0 *
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:01:06, Serial2/0 *
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:01:06, Serial2/0 * ----> their timers should be expired first
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:12, Serial2/0
R 192.168.48.0 [120/1] via 172.16.12.1, 00:01:06, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:12, Serial2/0
r2#

SEEING THE TABLES  


now see this

CODE
r1#config t
Enter configuration commands, one per line. End with CNTL/Z.
r1(config)#router rip
r1(config-router)#do siib
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 unassigned YES NVRAM administratively down down
FastEthernet0/1 unassigned YES NVRAM administratively down down
Ethernet1/0 unassigned YES NVRAM administratively down down
Ethernet1/1 unassigned YES NVRAM administratively down down
Ethernet1/2 unassigned YES NVRAM administratively down down
Ethernet1/3 unassigned YES NVRAM administratively down down
Serial2/0 172.16.12.1 YES NVRAM up up
Serial2/1 unassigned YES NVRAM administratively down down
Serial2/2 unassigned YES NVRAM administratively down down
Serial2/3 unassigned YES NVRAM administratively down down
Loopback0 172.16.1.1 YES NVRAM up up
Loopback48 192.168.48.1 YES NVRAM up up
Loopback49 192.168.49.1 YES NVRAM up up
Loopback50 192.168.50.1 YES NVRAM up up
Loopback51 192.168.51.1 YES NVRAM up up
Loopback70 192.168.70.1 YES NVRAM up up
r1(config-router)#passive-interface l0
r1(config-router)#passive-interface l48
r1(config-router)#passive-interface l49
r1(config-router)#passive-interface l50
r1(config-router)#passive-interface l51
r1(config-router)#passive-interface l70
r1(config-router)#end
r1#
*Mar 1 00:47:28.363: %SYS-5-CONFIG_I: Configured from console by console
r1#debug ip rip events
RIP event debugging is on
r1#
*Mar 1 00:47:43.311: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1) its now using only serial 2/0 for the updates and it reduces cpu cyc
*Mar 1 00:47:43.319: RIP: Update contains 7 routes
*Mar 1 00:47:43.319: RIP: Update queued
*Mar 1 00:47:43.323: RIP: Update sent via Serial2/0
r1#
*Mar 1 00:47:59.655: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:47:59.659: RIP: Update contains 2 routes
r1#

A DEBUG OUTPUT  

before that lets see a debug out put of rip

CODE
r1#debug ip rip events
RIP event debugging is on
r1#
*Mar 1 00:44:13.367: RIP: sending v2 update to 224.0.0.9 via Loopback50 (192.168.50.1)
*Mar 1 00:44:13.371: RIP: Update contains 9 routes ---------> *
*Mar 1 00:44:13.375: RIP: Update queued
*Mar 1 00:44:13.375: RIP: Update sent via Loopback50
*Mar 1 00:44:13.379: RIP: ignored v2 packet from 192.168.50.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:19.699: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:44:19.703: RIP: Update contains 2 routes
*Mar 1 00:44:20.151: RIP: sending v2 update to 224.0.0.9 via Loopback48 (192.168.48.1) -------->*
*Mar 1 00:44:20.155: RIP: Update contains 9 routes------>*
*Mar 1 00:44:20.159: RIP: Update queued
*Mar 1 00:44:20.159: RIP: Update sent via Loopback48----------->*
*Mar 1 00:44:20.163: RIP: ignored v2 packet from 192.168.48.1 (sourced from one of our addresses)
*Mar 1 00:44:20.527: RIP: sending v2 update to 224.0.0.9 via Loopback51 (192.168.51.1)
*Mar 1 00:44:20.531: RIP: Update contains 9 routes----------->*
*Mar 1 00:44:20.535: RIP: Update queued
r1#
*Mar 1 00:44:20.535: RIP: Update sent via Loopback51
*Mar 1 00:44:20.543: RIP: ignored v2 packet from 192.168.51.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:26.395: RIP: sending v2 update to 224.0.0.9 via Loopback49 (192.168.49.1)
*Mar 1 00:44:26.399: RIP: Update contains 9 routes
*Mar 1 00:44:26.403: RIP: Update queued
*Mar 1 00:44:26.403: RIP: Update sent via Loopback49
*Mar 1 00:44:26.411: RIP: ignored v2 packet from 192.168.49.1 (sourced from one of our addresses)
*Mar 1 00:44:27.175: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1)
*Mar 1 00:44:27.179: RIP: Update contains 7 routes
*Mar 1 00:44:27.183: RIP: Update queued
*Mar 1 00:44:27.183: RIP: Update sent via Serial2/0
*Mar 1 00:44:27.319: RIP: sending v2 update to 224.0.0.9 via Loopback70 (192.168.70.1)
r1#
*Mar 1 00:44:27.323: RIP: Update contains 9 routes
*Mar 1 00:44:27.327: RIP: Update queued
*Mar 1 00:44:27.327: RIP: Update sent via Loopback70
*Mar 1 00:44:27.335: RIP: ignored v2 packet from 192.168.70.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:34.667: RIP: sending v2 update to 224.0.0.9 via Loopback0 (172.16.1.1)
*Mar 1 00:44:34.671: RIP: Update contains 9 routes
*Mar 1 00:44:34.675: RIP: Update queued
*Mar 1 00:44:34.675: RIP: Update sent via Loopback0
*Mar 1 00:44:34.679: RIP: ignored v2 packet from 172.16.1.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:40.635: RIP: sending v2 update to 224.0.0.9 via Loopback50 (192.168.50.1)
*Mar 1 00:44:40.639: RIP: Update contains 9 routes
*Mar 1 00:44:40.643: RIP: Update queued
*Mar 1 00:44:40.643: RIP: Update sent via Loopback50
*Mar 1 00:44:40.651: RIP: ignored v2 packet from 192.168.50.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:46.279: RIP: received v2 update from 172.16.12.2 on Serial2/0
*Mar 1 00:44:46.283: RIP: Update contains 2 routes
*Mar 1 00:44:47.087: RIP: sending v2 update to 224.0.0.9 via Loopback51 (192.168.51.1)
*Mar 1 00:44:47.091: RIP: Update contains 9 routes
*Mar 1 00:44:47.095: RIP: Update queued
*Mar 1 00:44:47.095: RIP: Update sent via Loopback51
*Mar 1 00:44:47.099: RIP: ignored v2 packet from 192.168.51.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:50.135: RIP: sending v2 update to 224.0.0.9 via Loopback48 (192.168.48.1)
*Mar 1 00:44:50.139: RIP: Update contains 9 routes
*Mar 1 00:44:50.143: RIP: Update queued
*Mar 1 00:44:50.143: RIP: Update sent via Loopback48
*Mar 1 00:44:50.151: RIP: ignored v2 packet from 192.168.48.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:54.911: RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.12.1)
*Mar 1 00:44:54.915: RIP: Update contains 7 routes
*Mar 1 00:44:54.919: RIP: Update queued
*Mar 1 00:44:54.919: RIP: Update sent via Serial2/0
*Mar 1 00:44:55.431: RIP: sending v2 update to 224.0.0.9 via Loopback49 (192.168.49.1)
*Mar 1 00:44:55.435: RIP: Update contains 9 routes
*Mar 1 00:44:55.439: RIP: Update queued
*Mar 1 00:44:55.439: RIP: Update sent via Loopback49
*Mar 1 00:44:55.443: RIP: ignored v2 packet from 192.168.49.1 (sourced from one of our addresses)
r1#
*Mar 1 00:44:56.467: RIP: sending v2 update to 224.0.0.9 via Loopback70 (192.168.70.1)
*Mar 1 00:44:56.467: RIP: Update contains 9 routes
*Mar 1 00:44:56.467: RIP: Update queued
*Mar 1 00:44:56.467: RIP: Update sent via Loopback70
*Mar 1 00:44:56.467: RIP: ignored v2 packet from 192.168.70.1 (sourced from one of our addresses)
r1#u all
All possible debugging has been turned off
r1#
*Mar 1 00:45:03.159: RIP: sending v2 update to 224.0.0.9 via Loopback0 (172.16.1.1)
*Mar 1 00:45:03.163: RIP: Update contains 9 routes
*Mar 1 00:45:03.167: RIP: Update queued
*Mar 1 00:45:03.167: RIP: Update sent via Loopback0
*Mar 1 00:45:03.175: RIP: ignored v2 packet from 172.16.1.1 (sourced from one of our addresses)
r1#


so as we can see updates are being sent vigorously by rip . do we really need those updates ... we dont ..? so lets shut them ?

THE WAY TO DO IT  

this is how we do it

CODE
r1(config)#

r1(config)#ip route 192.168.48.0 255.255.252.0 null0
r1(config)#router rip
r1(config-router)#redistribute static
r1(config-router)#
as#3
[Resuming connection 3 to r5 ... ]


r2#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

192.168.30.0/32 is subnetted, 1 subnets
O 192.168.30.1 [110/65] via 172.16.23.3, 00:17:58, Serial2/1
192.168.25.0/32 is subnetted, 1 subnets
O 192.168.25.1 [110/65] via 172.16.23.3, 00:17:58, Serial2/1
192.168.40.0/32 is subnetted, 1 subnets
O 192.168.40.1 [110/65] via 172.16.23.3, 00:17:58, Serial2/1
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
C 172.16.12.0/24 is directly connected, Serial2/0
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:05, Serial2/0
O 172.16.3.1/32 [110/65] via 172.16.23.3, 00:17:58, Serial2/1
C 172.16.2.0/24 is directly connected, Loopback0
192.168.20.0/32 is subnetted, 1 subnets
O 192.168.20.1 [110/65] via 172.16.23.3, 00:17:59, Serial2/1
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:06, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:06, Serial2/0
192.168.35.0/32 is subnetted, 1 subnets
O 192.168.35.1 [110/65] via 172.16.23.3, 00:17:59, Serial2/1
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:06, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:06, Serial2/0
192.168.48.0/24 is subnetted, 1 subnets
R 192.168.48.0 [120/1] via 172.16.12.1, 00:00:06, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:06, Serial2/0
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
R 192.168.48.0 [120/1] via 172.16.12.1, 00:00:10, Serial2/0
R 192.168.48.0/22 [120/1] via 172.16.12.1, 00:00:10, Serial2/0 -------------------- ***********
r2#


we see no use for this as more specific routes are obviously preffered over /22 mask ... so lets use distribute list to accomplish it

IMPLENTATION  

leaving the networks 172.16.1.0 and 192.168.70.0 we can summarize all of 48 , 49 , 50 , 51



our summary is 192.168.48.0/22

lets implement our summary addr at r1

CODE
r1#config t
Enter configuration commands, one per line. End with CNTL/Z.
r1(config)#int s2/0
r1(config-if)#ip summary-address ?
eigrp Enhanced Interior Gateway Routing Protocol (EIGRP)
rip Routing Information Protocol (RIP)

r1(config-if)#ip summary-address rip ?
A.B.C.D IP address

r1(config-if)#ip summary-address rip 192.168.48.0 255.255.252.0
Summary mask must be greater or equal to major net ----------------------> this is obvious ? now do we have any solution?
r1(config-if)#

LOOK AT ROUTING TABLES  

take a look at the routing table of r2

CODE
as#3
[Resuming connection 3 to r5 ... ]

r2#sir
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

192.168.30.0/32 is subnetted, 1 subnets
O 192.168.30.1 [110/65] via 172.16.23.3, 00:03:56, Serial2/1
192.168.25.0/32 is subnetted, 1 subnets
O 192.168.25.1 [110/65] via 172.16.23.3, 00:03:56, Serial2/1
192.168.40.0/32 is subnetted, 1 subnets
O 192.168.40.1 [110/65] via 172.16.23.3, 00:03:56, Serial2/1
172.16.0.0/16 is variably subnetted, 5 subnets, 2 masks
C 172.16.23.0/24 is directly connected, Serial2/1
C 172.16.12.0/24 is directly connected, Serial2/0
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:19, Serial2/0
O 172.16.3.1/32 [110/65] via 172.16.23.3, 00:03:56, Serial2/1
C 172.16.2.0/24 is directly connected, Loopback0
192.168.20.0/32 is subnetted, 1 subnets
O 192.168.20.1 [110/65] via 172.16.23.3, 00:03:57, Serial2/1
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:20, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:20, Serial2/0
192.168.35.0/32 is subnetted, 1 subnets
O 192.168.35.1 [110/65] via 172.16.23.3, 00:03:57, Serial2/1
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:20, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:20, Serial2/0
R 192.168.48.0/24 [120/1] via 172.16.12.1, 00:00:20, Serial2/0
r2#



now for clarity see this

CODE
r2#sir | i R
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
o - ODR, P - periodic downloaded static route
R 172.16.1.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.51.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.50.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.49.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.70.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
R 192.168.48.0/24 [120/1] via 172.16.12.1, 00:00:00, Serial2/0
r2#


dont you think we require summaraisation ? yes we do lets implement

STARTING OSPF PROC  


starting ospf proc

CODE
r2(config-router)#do u all
All possible debugging has been turned off
r2(config-router)#do debug ip ospf events
OSPF events debugging is on
r2(config-router)#router ospf 1
r2(config-router)#network 172.16.23.2 0.0.0.0 area 0
r2(config-router)#net
*Mar 1 00:20:47.943: OSPF: Interface Serial2/1 going Up
*Mar 1 00:20:47.943: OSPF: Send hello to 224.0.0.5 area 0 on Serial2/1 from 172.16.23.2
*Mar 1 00:20:48.055: OSPF: Rcv hello from 192.168.40.1 area 0 from Serial2/1 172.16.23.3
*Mar 1 00:20:48.055: OSPF: 2 Way Communication to 192.168.40.1 on Serial2/1, state 2WAY
*Mar 1 00:20:48.059: OSPF: Send DBD to 192.168.40.1 on Serial2/1 seq 0x4DB opt 0x52 flag 0x7 len 32
*Mar 1 00:20:48.059: OSPF: Send immediate hello to nbr 192.168.40.1, src address 172.16.23.3, on Serial2/1
*Mar 1 00:20:48.059: OSPF: Send hello to 224.0.0.5 area 0 on Serial2/1 from 172.16.23.2
*Mar 1 00:20:48.063: OSPF: End of hello processing
*Mar 1 00:20:48.107: OSPF: Rcv DBD from 192.168.40.1 on Serial2/1 seq 0x1E46 opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART
*Mar 1 00:20:48.107: OSPF: NBR Negotiation Done. We are the SLAVE
*Mar 1 00:20:48.111: OSPF: Send DBD to 192.168.40.1 on Serial2/1 seq 0x1E46 opt 0x52 flag 0x0 len 32
*Mar 1 00:20:4
r2(config-router)#network 8.167: OSPF: Rcv DBD from 192.168.40.1 on Serial2/1 seq 0x1E47 opt 0x52 flag 0x3 len 52 mtu 1500 state EXCHANGE
*Mar 1 00:20:48.167: OSPF: Send DBD to 192.168.40.1 on Serial2/1 seq 0x1E47 opt 0x52 flag 0x0 len 32
*Mar 1 00:20:48.183: OSPF: Rcv DBD from 192.168.40.1 on Serial2/1 seq 0x1E48 opt 0x52 flag 0x1 len 32 mtu 1500 state EXCHANGE
*Mar 1 00:20:48.183: OSPF: Exchange Done with 192.168.40.1 on Serial2/1
*Mar 1 00:20:48.187: OSPF: Send LS REQ to 192.168.40.1 length 12 LSA count 1
*Mar 1 00:20:48.187: OSPF: Send DBD to 192.168.40.1 on Serial2/1 seq 0x1E48 opt 0x52 flag 0x0 len 32
*Mar 1 00:20:48.207: OSPF: Rcv LS UPD from 192.168.40.1 on Serial2/1 length 136 LSA count 1
*Mar 1 00:20:48.211: OSPF: Synchronized with 192.168.40.1 on Serial2/1, state FULL
*Mar 1 00:20:48.211: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.40.1 on Serial2/1 from LOADING to FULL, Loading Done
*Mar 1 00:20:48.723: OSPF: Rcv LS UPD from 192.168.40.1 on Serial2/1 length 148 LSA count 1
r2(config-router)#network 172.1
*Mar 1 00:20:51.135: OSPF: Rcv hello from 192.168.40.1 area 0 from Serial2/1 172.16.23.3
*Mar 1 00:20:51.135: OSPF: End of hello processing
r2(config-router)#network 172.16.2.1 0.0.0.0 area 0
*Mar 1 00:20:57.943: OSPF: Send hello to 224.0.0.5 area 0 on Serial2/1 from 172.16.23.2
r2(config-router)#network 172.16.2.1 0.0.0.0 area 0
r2(config-router)#
*Mar 1 00:21:00.391: OSPF: Interface Loopback0 going Up -------------> saw this as soon as network is advertised interface goes .. so this is the use of c network command

*Mar 1 00:21:01.167: OSPF: Rcv hello from 192.168.40.1 area 0 from Serial2/1 172.16.23.3
*Mar 1 00:21:01.167: OSPF: End of hello processing
r2(config-router)#
*Mar 1 00:21:07.943: OSPF: Send hello to 224.0.0.5 area 0 on Serial2/1 from 172.16.23.2
r2(config-router)#
*Mar 1 00:21:11.151: OSPF: Rcv hello from 192.168.40.1 area 0 from Serial2/1 172.16.23.3
*Mar 1 00:21:11.151: OSPF: End of hello processing
r2(config-router)#do u all
All possible debugging has been turned off
r2(config-router)#

CONFIGURING OSPF  

on r2 lets configure s2/0 in rip and l0 and s2/1 in ospf

CODE
r2(config-router)#do siib
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 unassigned YES unset administratively down down
FastEthernet0/1 unassigned YES unset administratively down down
Ethernet1/0 unassigned YES unset administratively down down
Ethernet1/1 unassigned YES unset administratively down down
Ethernet1/2 unassigned YES unset administratively down down
Ethernet1/3 unassigned YES unset administratively down down
Serial2/0 172.16.12.2 YES manual up up
Serial2/1 172.16.23.2 YES manual up up
Serial2/2 unassigned YES unset administratively down down
Serial2/3 unassigned YES unset administratively down down
Loopback0 172.16.2.1 YES manual up up
r2(config-router)#do debug ip rip events
RIP event debugging is on
r2(config-router)#network 172.16.0.0
r2(config-router)#netwo
*Mar 1 00:18:08.503: RIP: add Serial2/0 to RIP idb list
*Mar 1 00:18:08.507: RIP: add Serial2/1 to RIP idb list
*Mar 1 00:18:08.507: RIP: add Loopback0 to RIP idb list
*Mar 1 00:18:08.535: RIP: sending request on Loopback0 to 224.0.0.9
*Mar 1 00:18:08.539: RIP: sending request on Serial2/0 to 224.0.0.9
*Mar 1 00:18:08.539: RIP: sending request on Serial2/1 to 224.0.0.9-------------------------------------------remember this
*Mar 1 00:18:08.543: RIP: ignored v2 packet from 172.16.2.1 (sourced from one of our addresses)
*Mar 1 00:18:08.691: RIP: received v2 update from 172.16.12.1 on Serial2/0
*Mar 1 00:18:08.699: RIP: Update contains 6 routes
*Mar 1 00:18:09.419: RIP: received v2 update from 172.16.12.1 on Serial2/0
r2(config-router)#network
*Mar 1 00:18:09.423: RIP: Update contains 6 routes
*Mar 1 00:18:10.531: RIP: sending v2 flash update to 224.0.0.9 via Serial2/0 (172.16.12.2)
*Mar 1 00:18:10.531: RIP: Update contains 2 routes
*Mar 1 00:18:10.531: RIP: Update queued
*Mar 1 00:18:10.535: RIP: sending v2 flash update to 224.0.0.9 via Serial2/1 (172.16.23.2)
*Mar 1 00:18:10.535: RIP: Update contains 8 routes
*Mar 1 00:18:10.535: RIP: Update queued
*Mar 1 00:18:10.539: RIP: sending v2 flash update to 224.0.0.9 via Loopback0 (172.16.2.1)
*Mar 1 00:18:10.539: RIP: Update contains 8 routes
*Mar 1 00:18:10.539: RIP: Update queued
*Mar 1 00:18:10.543: RIP: Update sent via Serial2/0
*Mar 1 00:18:10.543: RIP: Update sent via Serial2/1
r2(config-router)#network
*Mar 1 00:18:10.543: RIP: Update sent via Loopback0
*Mar 1 00:18:10.547: RIP: ignored v2 packet from 172.16.2.1 (sourced from one of our addresses)
r2(config-router)#

CONFIG FOR R3  


config for r3

CODE
r3>

r3>en
r3#show run
Building configuration...

Current configuration : 1994 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname r3
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
ip cef
!
!
!
!
!
!
!
interface Loopback0
ip address 172.16.3.1 255.255.255.0
!
interface Loopback20
ip address 192.168.20.1 255.255.255.0
!
interface Loopback25
ip address 192.168.25.1 255.255.255.0
!
interface Loopback30
ip address 192.168.30.1 255.255.255.0
!
interface Loopback35
ip address 192.168.35.1 255.255.255.0
!
interface Loopback40
ip address 192.168.40.1 255.255.255.0
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Ethernet1/0
no ip address
shutdown
half-duplex
!
interface Ethernet1/1
no ip address
shutdown
half-duplex
!
interface Ethernet1/2
no ip address
shutdown
half-duplex
!
interface Ethernet1/3
no ip address
shutdown
half-duplex
!
interface Serial2/0
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/1
ip address 172.16.23.3 255.255.255.0
serial restart-delay 0
!
interface Serial2/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 1
log-adjacency-changes
passive-interface default
no passive-interface Serial2/1
network 172.16.3.1 0.0.0.0 area 0
network 172.16.23.3 0.0.0.0 area 0
network 192.168.20.1 0.0.0.0 area 0
network 192.168.25.1 0.0.0.0 area 0
network 192.168.30.1 0.0.0.0 area 0
network 192.168.35.1 0.0.0.0 area 0
network 192.168.40.1 0.0.0.0 area 0
!
ip http server
!
!
!
!
control-plane
!
alias exec sir show ip route
alias exec siib show ip int brief
alias exec sird show ip rip database
alias exec sio show ip ospf
alias exec siod show ip ospf database
alias exec sioi show ip int brief
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
login
!
!
end

r3#

CONFIG FOR R2  

config for r2

CODE
r2#

r2#show run
Building configuration...

Current configuration : 1423 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname r2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
ip cef
!
!
!
!
!
!
!
interface Loopback0
ip address 172.16.2.1 255.255.255.0
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Ethernet1/0
no ip address
shutdown
half-duplex
!
interface Ethernet1/1
no ip address
shutdown
half-duplex
!
interface Ethernet1/2
no ip address
shutdown
half-duplex
!
interface Ethernet1/3
no ip address
shutdown
half-duplex
!
interface Serial2/0
ip address 172.16.12.2 255.255.255.0
serial restart-delay 0
!
interface Serial2/1
ip address 172.16.23.2 255.255.255.0
serial restart-delay 0
!
interface Serial2/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/3
no ip address
shutdown
serial restart-delay 0
!
ip http server
!
!
!
!
control-plane
!
alias exec sir show ip route
alias exec siib show ip int brief
alias exec sip show ip proto
alias exec sird show ip rip data
alias exec sio show ip ospf
alias exec sioi show ip ospf int
alias exec sion show ip ospf nei
alias exec siod show ip ospf data
alias exec siot show ip ospf topo
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
!
!
end

r2#

INTO CONFIGS  

CONFIG FOR R1

my gns3 messed up so i had to reconfigure one of the routers in topology ..

router 1 and router 3 will have full configs and router 2 will have initial configs

CODE
config for r1

r1>en
r1#show run
Building configuration...

Current configuration : 2393 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname r1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
!
!
ip cef
!
!
!
!
!
!
!
interface Loopback0
ip address 172.16.1.1 255.255.255.0
!
interface Loopback48
ip address 192.168.48.1 255.255.255.0
!
interface Loopback49
ip address 192.168.49.1 255.255.255.0
!
interface Loopback50
ip address 192.168.50.1 255.255.255.0
!
interface Loopback51
ip address 192.168.51.1 255.255.255.0
!
interface Loopback70
ip address 192.168.70.1 255.255.255.0
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Ethernet1/0
no ip address
shutdown
half-duplex
!
interface Ethernet1/1
no ip address
shutdown
half-duplex
!
interface Ethernet1/2
no ip address
shutdown
half-duplex
!
interface Ethernet1/3
no ip address
shutdown
half-duplex
!
interface Serial2/0
ip address 172.16.12.1 255.255.255.0
serial restart-delay 0
!
interface Serial2/1
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial2/3
no ip address
shutdown
serial restart-delay 0
!
router rip
version 2
redistribute static
passive-interface Loopback0
passive-interface Loopback48
passive-interface Loopback49
passive-interface Loopback50
passive-interface Loopback51
passive-interface Loopback70
network 172.16.0.0
network 192.168.48.0
network 192.168.49.0
network 192.168.50.0
network 192.168.51.0
network 192.168.70.0
distribute-list prefix rakesh out Serial2/0
distribute-list prefix rakesh1 in Serial2/0
no auto-summary
!
ip http server
!
ip route 192.168.48.0 255.255.252.0 Null0
!
!
!
ip prefix-list rakesh seq 5 permit 192.168.48.0/22
ip prefix-list rakesh seq 10 deny 192.168.48.0/22 le 24
ip prefix-list rakesh seq 15 permit 0.0.0.0/0 le 32
!
ip prefix-list rakesh1 seq 5 deny 192.168.20.0/24
ip prefix-list rakesh1 seq 10 deny 192.168.25.0/27
ip prefix-list rakesh1 seq 15 permit 0.0.0.0/0 le 32
!
ip access-list standard rakesh1
!
control-plane
!
alias exec sir show ip route
alias exec siib show ip int brief
alias exec sird show ip rip database
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
login
!
!
end

r1#

Design by Blogger Buster | Distributed by Blogging Tips