Tasks
-------------------------------------
* Make R1 the DR and R2 the BDR for the 172.16.123.0/24 network.
* R1-R2-R3 will be using their default OSPF network type of broadcast.
* R1-R4 link is frame-relay and the OSPF network type is point-to-multipoint.
* R1-R4 link is using MD5 authentication for peering.
* R1-R5 link is frame-relay and the OSPF network type is the default of non-broadcast.
* R1-R5 link is using simple authentication for peering.
* R1-R12 link is using its default OSPF network area type of point-to-point.
* R1, R2, R3, R4, R5, and R12 are all in OSPF area 0.
* R2-R8 will serve as a virtual link for OSPF area 4.
* R3-R9 link is using frame-relay and OSPF network type is point-to-multipoint nonbroadcast.
* R3 OSPF process number will be different than all other routers OSPF process numbers to demonstrate that OSPF process number in unimportant in peering establishment.
* R3-R9 OSPF area 5 is a NSSA with a default route advertised back into it
* R4-R11 will be using a GREoIPSEC tunnel for all traffic including routing protocols.
* R4-R6 OSPF area 2 is a stub area.
* R4 will have all OSPF network statements use a 4 octet area identifier(i.e. network 2.2.2.1 0.0.0.0 area 0.0.0.50).
* R4-R11 OSPF area 50 will be a different OSPF process so that R4 becomes an ASBR between OSPF process for area 50 and the OSPF process that area 2 and area 0 are in.
* R4 will use a different OSPF router-ID for each OSPF process. This is to demonstrate that there can be multiple router-IDs on one router.
* Mutually redistribute routes between OSPF area 50 process and OSPF area 0/area 2 process on R4.
* Routes redistributed from OPSF area 50 process into OSPF area0/area 2 process will be made external type 1 OSPF routes.
* Mutually redistribute routes between EIGRP and OSPF at R5 and R12.
* Prevent any redistribution loops that might be caused with mutual redistribution at R5 and R12.
* R5-R7 OSPF area 1 is a totally stubby area.
* Mutually redistribute routes between OSPF area 5 and RIP on R9.
* R9 and R14 will use RIP version 2.
* Manually assign router IDs to all OSPF routers and use the format 0.0.0.x where x=Router#.
* All other links will be their default OSPF network type.
* Summarize networks at ABRs and ASBRs when possible.
* Summarized routes should be prevented from being redistributed back into source areas.
* Network addresses displayed on network diagram near a router are loopbacks. The loopback interfaces used for OSPF should be set to a OSPF network type of point-to-point.

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

What? No .net file?

_________________
blog.brokennetwork.ca

Added.

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Looks good wirerat.

_________________
blog.brokennetwork.ca

I'm going to do this just for fun tomorrow

_________________
www.mellowd.co.uk/ccie/

Would be nice to have initial configs for all the routers with the .net file

_________________
www.mellowd.co.uk/ccie/

I can do that. You want just the interfaces set up?

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Ideally yes.

In my initial configs I usually add the following:



With the initial configs it'll make it a lot easier and quicker for people to start and tackle it

_________________
www.mellowd.co.uk/ccie/

Will do. I'll try to get them up in the next 30 minutes or so.

Thanks for the advice.

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Updated original post with init-config.zip file containing dynamips .net files.

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Go to bed!

That's some excellent work..

I just got out of bed. I am one of those "morning" people you hear so many stories and rumors about.

Thanks.

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Quarter way through, so far so good. The different types of authentication in the same area were tricky, but now done

_________________
www.mellowd.co.uk/ccie/

All done.

One or two things threw me off, but got there in the end.

Only thing I could not do is the GRE/IPSEC tunnel as my IOS had no crypto capability. I used a regular GRE tunnel instead.



I don't recommended anyone look at my configs until you've at least tried this yourself first.

_________________
www.mellowd.co.uk/ccie/

I had the same problem. I ended up going back to an older 3640 image that had IPSec and such in it about 3/4's of the way through the configs.

I am now debating between making an EIGRP lab similar to this one or another OSPF one with more advanced topics(if I can get enough topics together to make a similar sized lab).

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Aye.

A couple of things I would change though

1. No need to make ALL the loopbacks point to point. A lot of redundancy there. As long as the engineer knows how to make a few point to point it should be good enough
2. Make sure at least 1 router forms an adjacency with NO network statements under the OSPF process. I used this method for a lot of the loopbacks, but loopbacks aren't actually sending hellos

_________________
www.mellowd.co.uk/ccie/

Good practice. Here's my crack at it.

**Edit**

I screwed up saving the config files... Here's the complete configs now.

_________________
blog.brokennetwork.ca

don't forget linking 2 discontiguous area 0's over an OSPF superbackbone...
(was reading about this last night...phew)

Forgot to put these up.

_________________
"See packet, be packet, you are packet. Ignore all else!" -The Networker
packetsdropped.wordpress.com

Thanks for the lab...and just found the EIGRP one.

Ever made or seen any break/fix type labs?
e.g. Here's the problem/symptom..now fix it w/out doing XYZ (static routes, show run, etc.)