I got to thinking one day how nice it would be to have a dynamips lab I could turn up real quick to validate information or test out theories seen in posts from one of the best networking forums ever. I finally got around to getting it all together. I ended up creating a task-based list for all the stuff I had configured on it so if other people wanted to use it as a study/fun lab. In this post I am just posting up the diagram, dynamips .net file, and the initial router configs. Over the next few days I will be going through a portion of the tasks and show how I configured each task. Enjoy.
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 is 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 in that R4 becomes an ASBR between the OSPF process for area 50 and the other 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 OSPF 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.
Dynamips .net file (replace .doc extension with .net when saving): ospf.net
Initial router configs (replace .doc extension with .zip when saving): init-config.zip
