I hope everyone is doing well and is stomping out all of certification exams 1-by-1. As for me, I’m moving slow, but with great momentum – if that even makes sense. I haven’t posted in a long long while, but since then all you need to know is I failed my SWITCH exam on my first attempt this past September Boooo! But it’s OK and now I know exactly what I need to work on to ace it next time!

So this lab below is fairly easy, not much involved. In fact you could consider it an advanced CCNA switching lab. Call it what you like, but similar questions, labs and scenarios came up on the SWITCH exam.

Why am I posting it? Simple – as always to share labs! This is the first lab I’ve taken the time to save and compile with tasks and solutions in a long time. So I’m starting out with what is more or less the basic labs and hopefully I can keep that going with the more advanced labs as I complete them.

The lab below is a hybrid of GNS3 and real switches in my lab. I was able to scoop up some 3560 and 2960 switches which are perfect for my studies. Haven’t really looked at any routers cause I’m not doing TSHOOT labs yet. Either way, I believe that the same way I’m linking routers from GNS3 onto my hardware switches is actually enough for the TSHOOT as well. I do this using some USB to ethernet plugs from Rocketfishand these things are awesome! They also support dot1q encapsulation! I’ve been able to do massive labs with these things. For hosts I use VPCS – It’s something I’m just very use to and comfortable with using right now.

This lab consists of a combination of real Catalyst 3560 switches and GNS3. The hosts involved in this lab are emulated using VPCS. I know GNS3 has a similar feature, but the small VPCS features work well for me right now.

Switches used: 3560

IOS:c3560-ipbase-mz.122-25.SEE3

Feature of Topology: Inter-VLAN Rouing & Routing, 802.1q, ISL, VLANs, Trunking

Image:

Lab Objectives: A Jr. Network Engineer on your team was tasked with configuring Inter-VLAN routing using a 3560 switch. He wasn’t exactly sure how to configure it, made a big mess and decided to erase all of his configs and leave it up to you to do. Your Manager would like you to configure ISL encapsulation first to perform some testing before implementing Inter-VLAN routing and then enable 802.1q encapsulation between the switch trunks.

Task 1

Create VLANs 2 & 3 on SW1 & SW2.

Name VLAN 2 Sales

Name VLAN 3 Finance

Assign VLAN 2 to ports F0/1 on SW1 & SW2

Assign VLAN 3 to ports F0/2 on SW1 & SW2

Task 2

Configure ISL trunk between SW1 (fa0/11) and SW 2 (fa0/11)

Task 3

Review the configurations changes applied and ensure they are as expected:

Task 4

Check connectivity between PC1 and PC3 – they are in the same VLAN.

Task 5

Check connectivity between PC1 and PC4 – they are in different VLANs

Task 6

Configure Inter-VLAN communication between VLANs2 & 3 using SW1 as the route processing switch

Task 7

Create and Assign the .1 address to the SVI used for Inter-VLAN communication on SW1 for VLAN 2 & 3

Task 8

Change the encapsulation type between SW1 & SW2 to use 802.1q

Task 9

Check connectivity between PC1 and PC3 – they are in the same VLAN.

Task 10

Check connectivity between PC1 and PC4 – they are in different VLANs

Download Tasks and Solutions: GNS3-Labs-Inter-VLAN-Routing-SWITCH

(including VPCS config, GNS3 .net file to hardware switch configs)

Cheers and Happy Labbing!

LBS

Disclaimer:

I perform all of these labs on my own using my own knowledge and experience (warning and disclaimer). They may very well be implemented differently than a method you might choose. So long as it meets the requirements and works, essentially it’s acceptable (In my feeble opinion). But if you notice a terribly or complicated method used by me to achieve the goals and you feel yours is much easier, makes sense or is the standard; please do share – I’m always open to learning

P.S. If you would like to donate for the time it takes to do all of this, feel free to use the link below. Thank you in advance for any contribution you make

SW1#ping 10.0.0.2 source 10.0.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
Packet sent with a source address of 10.0.10.1
…..
Success rate is 0 percent (0/5)

R1#ping 10.0.10.1 source 10.0.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.10.1, timeout is 2 seconds:
Packet sent with a source address of 10.0.0.2
…..
Success rate is 0 percent (0/5)

Find out why without looking into initial configuration files, all IOS commands are allowed.

Routers Used: Cisco C3745
IOS: (C3745-ADVENTERPRISEK9-M), Version 12.4(23)
Feature of Topology: VPN, IPSEC, ISAKMP,RIP
Download GNS3 files: http://www.uploadhookup.com/index.php/files/get/YA4jjABr6Z/vpn-troubleshooting.rar

Solution:

Looking into initial configuration file will help !

1) 1:1, traffic equally distributed between R0-R2 and R0-R3

2) 1:2, twice as much traffic on R0-R2 as on R0-R3

Traffic distribution has to be proven by test with ICMP traffic

Routers Used: Cisco 3640

IOS: c3640-ik9o3s-mz.124-25b, (C3640-IK9O3S-M), Version 12.4(25)

Feature of Topology: EIGRP Metric Weights, EIGRP unequal cost load balancing

Download GNS3 files: http://www.uploadhookup.com/index.php/files/get/luHPhnCS40/load-sharing.zip plus setup vlan 100 as shown below:

SW1#vlan database
SW1(vlan)#vlan 100
VLAN 100 added:
Name: VLAN0100
SW1(vlan)#apply
APPLY completed.
SW1(vlan)#exit
APPLY completed.

Solution:

1) 1:1, traffic equally distributed between R0-R2 and R0-R3
If DS3 between R0-R1 has not be broken traffic would go through this link

R0#sh ip route 1.1.1.1
Routing entry for 1.1.1.0/24
Known via “eigrp 1″, distance 90, metric 2297856, type internal
Redistributing via eigrp 1
Last update from 10.1.1.1 on Serial1/1, 00:05:49 ago
Routing Descriptor Blocks:
* 10.1.1.1, from 10.1.1.1, 00:05:49 ago, via Serial1/1
Route metric is 2297856, traffic share count is 1
Total delay is 25000 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1

But the scenario says that DS3 R0-R1 is broken:

R0#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R0(config)#int s1/1
R0(config-if)#sh
R0(config-if)#
*Mar 1 00:18:54.611: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.1.1.1 (Serial1/1) is down: interface down
*Mar 1 00:18:56.487: %LINK-5-CHANGED: Interface Serial1/1, changed state to administratively down
*Mar 1 00:18:57.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/1, changed state to down

Traffic is momentarily distributed between R0-R2 and R0-R3 DS3s (metric 2300416)

R0#sh ip route 1.1.1.1
Routing entry for 1.1.1.0/24
Known via “eigrp 1″, distance 90, metric 2300416, type internal
Redistributing via eigrp 1
Last update from 10.3.3.3 on Serial1/3, 00:00:28 ago
Routing Descriptor Blocks:
10.3.3.3, from 10.3.3.3, 00:00:28 ago, via Serial1/3
Route metric is 2300416, traffic share count is 1
Total delay is 25100 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2
* 10.2.2.2, from 10.2.2.2, 00:00:28 ago, via Serial1/2
Route metric is 2300416, traffic share count is 1
Total delay is 25100 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2

As you can see traffic is distributed equally between R2 and R3 (traffic share count is 1). In order to test it let’s configure access list on input s1/0 interfaces of R2 and R3

access-list 100 permit icmp any host 1.1.1.1 log
access-list 100 permit ip any any
interface Serial1/0
ip address 10.3.3.3 255.255.255.0
ip access-group 100 in

Let’s ping from R0 to 1.1.1.1 (ping 1.1.1.1 repeat 300) and display traffic count on R2 and R3 (don’t forget to do ‘clear access-list counters’ on R2 and R3):

R2#sh ip access-lists 100 | inc icmp
Extended IP access list 100
10 permit icmp any host 1.1.1.1 log (300 matches)

R3#sh ip access-lists 100 | inc icmp
Extended IP access list 100
10 permit icmp any host 1.1.1.1 log

Traffic is not distributed, goes only through one DS3. Why is that? The reason is that traffic is CEF cached on R0 and by default distribution is per-destination.

R0(config-if)#ip load-sharing ?
per-destination Deterministic distribution
per-packet Random distribution

According to Cisco per-packet load balancing allows the router to send data packets over successive equal-cost paths without regard to individual destination hosts or user sessions. Path utilization is good, but packets destined for a given destination host might take different paths and might arrive out of order (could be very risky, not all application like it) . Per-destination load balancing allows the router to use multiple, equal-cost paths to achieve load sharing. Packets for a given source-destination host pair are guaranteed to take the same path, even if multiple, equal-cost paths are available. Traffic for different source-destination host pairs tend to take different paths. So let’s change default distribution to per-packet and switch-off CEF caching on R0 interfaces S1/2 and S1/3:

R0#sh run int s1/2
interface Serial1/2
ip address 10.2.2.100 255.255.255.0
ip load-sharing per-packet
no ip route-cache cef
no ip route-cache

R0#sh run int s1/3
interface Serial1/3
ip address 10.3.3.100 255.255.255.0
ip load-sharing per-packet
no ip route-cache cef
no ip route-cache

After ‘clear access-list counters’ do ‘ping 1.1.1.1 repeat 300′ on R0:

R2#sh ip access-lists 100 | inc icmp
Extended IP access list 100
10 permit icmp any host 1.1.1.1 log (150 matches)

R3#sh ip access-lists 100 | inc icmp
Extended IP access list 100
10 permit icmp any host 1.1.1.1 log (150 matches)

Bingo !

2) 1:2, twice as much traffic on R0-R2 comparing to R0-R3
Traffic distribution depends on metrics. In the first scenario traffic is distributed equally because metric on both links is the same (2300416). By default metric is calculated using bandwidth and delay (could include also load and reliability).

metric=k1*bandwidth + k3*delay, if k2 & k4 are zero ( k1=k2=1)

To make this task easier I will configure all routers so that only delay is used in the composite metric calculation (will use command ‘metric weights tos k1 k2 k3 k4 k5′)

R0,R1,R2and R3 (the metric must much on all routers in order for EIGRP adjacency to form) :

router eigrp 1
metric weights 0 0 0 1 0 0

On R0
R0#sh ip prot | inc weight
EIGRP metric weight K1=0, K2=0, K3=1, K4=0, K5=0

R0#sh ip route 1.1.1.1
Routing entry for 1.1.1.0/24
Known via “eigrp 1″, distance 90, metric 642560, type internal
Redistributing via eigrp 1
Last update from 10.3.3.3 on Serial1/3, 00:00:00 ago
Routing Descriptor Blocks:
* 10.3.3.3, from 10.3.3.3, 00:00:00 ago, via Serial1/3
Route metric is 642560, traffic share count is 1
Total delay is 25100 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2
10.2.2.2, from 10.2.2.2, 00:00:00 ago, via Serial1/2
Route metric is 642560, traffic share count is 1
Total delay is 25100 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2

Delay is 10s of microseconds scaled by 256, so if delay is 25100, metric=2510 * 256=642560
In order to have twice as much traffic between R0-R2 the metric on S1/2 should be 642560/2=321280. To get this metric delay has to be changed to 745, because:

642560/2=321280=(x+510) x256 -> x=745

Total delay is 25100, with 20000 on R0-R2, see below

R0#sh int s1/2 | inc DLY
MTU 1500 bytes, BW 1544 Kbit/sec, DLY 20000 usec,

So after changing delay on R0-R2 to 745 the new metric will be:

metric=(745+510)*256=321280 and new delay=12550

Variance has to be configured to any value as long as the link metric times the variance is greater than the total composite metric
On R0 configure the following:

interface Serial1/2
ip address 10.2.2.100 255.255.255.0
ip load-sharing per-packet
no ip route-cache cef
no ip route-cache
delay 745
router eigrp 1
variance 123

See how the traffic is distributed:

R0#sh ip route 1.1.1.0
Routing entry for 1.1.1.0/24
Known via “eigrp 1″, distance 90, metric 321280, type internal
Redistributing via eigrp 1
Last update from 10.3.3.3 on Serial1/3, 00:02:00 ago
Routing Descriptor Blocks:
10.3.3.3, from 10.3.3.3, 00:02:00 ago, via Serial1/3
Route metric is 642560, traffic share count is 1
Total delay is 25100 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2
* 10.2.2.2, from 10.2.2.2, 00:02:00 ago, via Serial1/2
Route metric is 321280, traffic share count is 2
Total delay is 12550 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2

As we can see below twice as much traffic went through R2 (clear counters and ‘ping 1.1.1.1 repeat 300′ from R0):

R0#ping 1.1.1.1 repeat 300
Type escape sequence to abort.
Sending 300, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (300/300), round-trip min/avg/max = 4/12/80 ms

R3#sh ip access-lists 100 | inc icmp
Extended IP access list 100
10 permit icmp any host 1.1.1.1 log (100 matches)

R2#sh ip access-lists 100 | inc icmp
Extended IP access list 100
10 permit icmp any host 1.1.1.1 log (200 matches)

Load sharing could be also achieved with OSPF (by default it supports four equal cost paths to a destination – use the maximum-paths command under OSPF). OSPF allows only equal cost load balancing

There is a new site online that took the idea of this site (though they say they didn’t know this site existed) and is doing it 100 times better. If I could redo what I started here, I’d definitely do it a little differently today. But hey, at the time I was the only site. Anyway – the new GNS3 lab site dedicated and full of GNS3 labs is called GNS3-Vault and you can check it out at http://www.gns3vault.com .. Go check it out – they are doing a far better job with current labs than I can.

As for me, I’m studying very hard with the SWITCH studies and a new technical/study/personal blog at http://echoreplypackets.net. I’m sure I’ll be even more busy when I hit TSHOOT. I’m not saying I’m taking the site down or stopping labs, but this will end up becoming the site where I upload labs that I’ve used my own as well as labs that you guys contribute more than a lab supplying site.

GNS3 Vault is a great site! Go over and support it! Plenty of good labs.

Now onto the lab!

This labs come from below. If you use the link below and purchase this book – you help me pay hosting bills

CCNP Building Scalable Internetworks (BSCI 642-901) Lab Portfolio (Cisco Networking Academy)

Instructions
Plan, design, and implement the International Travel Agency (ITA) network
shown in the diagram and described below. Verify that all configurations are
operational and functioning according to the guidelines.

Scenario

The ITA needs its core network set up for OSPF with the following
specifications. Use the addressing scheme shown in the diagram.

• Configure the OSPF backbone area on the Ethernet connection between R1and R5.
• Configure the Frame Relay subnet as a point-to-multipoint network in area 100.
• Configure R2’s loopback interfaces to be in area 200. Summarize this area with the most efficient summary.
• Configure the Ethernet connection between R3 and R4 to be in area 300.
• Add the loopback on R3 to area 300.
• Make area 300 a totally NSSA area.
• Redistribute the loopback networks on R4 that do not belong in any OSPF area.
• Create virtual links as necessary for full connectivity.
• Make sure that all loopback interfaces get advertised with the correct subnet mask.

Routers Used:3640 (Any type should be fine)

IOS: c3640-ik9o3s-mz.124-25b

Feature of Topology: OSPF, Redistribution, Summarization, NSSA, Point-To-Point, Sub-interfaces, Virtual-links

Image:

Download: Gns3-Labs:: OSPF-Case-Study-Lab-Scenario-3

Enjoy .. LBS

P.S. If you would like to donate for the time it takes to do all of this, feel free to use the link below. Thank you in advance for any contribution you make

Here is a read from an article published by Dan Hughes on etherealmind.com

However this week marked the beginning of the end for this old friend, with the announcement of the supported hardware platforms for IOS 15.1, we see that only ISR and ISR2 routers are supported. For architectural reasons, it’s never been possible to emulate these platforms in dynamips, so we’ve reached a place where new IOS software won’t be usable in dynamips. We can run 12.4 on the existing range of platforms, and 15.0 on the 7200 platform, and thats it.

Today, it doesn’t really affect anything, unless you want to try the new hold music feature in 15.1, but over the months, as we head into 15.2 and 15.3, then the software we can run in dynamips will become too old to matter any more. Exam blueprints will move on, features we want to use will only exist in the new versions, we’ll update our production and test networks, and slowly, dynamips will become a thing of the past.

For those of us who have invested heavily in our own training and lab equipment, it won’t make a huge difference. Adding a few second hand 1841′s won’t cost a fortune, although will use a lot more power and cooling than the single dynamips box does. But for the ordinary CCNA and CCNP student, it’ll be too much to buy, too much room taken up, and too much power and noise. They can use remote labs, but they really don’t give the flexibility of your own kit.

So Greg Ferro put up a petetion off of an idea Wendel Odom came up with regarding an educational copy of IOS.

Do us all a favor and lets give it a shot and support and sign this electronic petition!

Ask Cisco to Consider an IOS for Certifcation Self Study – Sign the petition now!

Here is another one of the final Cisco Network Academy labs. This one involves BGP and EIGRP. A lot of good tasks in this case scenario. I wish that they would have had many more lab scenarios since they are exactly whats on the lab. There definitely needs to be a new lab book developed – Maybe I’ll create one? Kidding!

Anyway … Onto the lab!

This is a lab from the Cisco Networking Academy Lab Portfolio.

CCNP Building Scalable Internetworks (BSCI 642-901) Lab Portfolio (Cisco Networking Academy)

Routers Used:3640

IOS:c3640-ik9o3s-mz.124-17a

Feature of Topology: EIGRP, BGP, eBGP, Full Mesh iBGP, Summarization, MED, Local-Preference

Image:

Lab Objectives: Plan, design, and implement the International Travel Agency (ITA) core network
as well as the Travel Data Providers (TDP) network and allow the networks to
communicate via BGP. Verify that all implementations are operational and
functional according to guidelines.

Download: GNS3-Labs – BGP & EIGRP Case Study 4

Cheers and Happy Labbing!

LBS

Disclaimer:

I perform all of these labs on my own using my own knowledge and experience (warning and disclaimer). They may very well be implemented differently than a method you might choose. So long as it meets the requirements and works, essentially it’s acceptable (In my feeble opinion). But if you notice a terribly or complicated method used by me to achieve the goals and you feel yours is much easier, makes sense or is the standard; please do share – I’m always open to learning

P.S. If you would like to donate for the time it takes to do all of this, feel free to use the link below. Thank you in advance for any contribution you make

This is basically a simple route redistribution and route manipulation lab. Simple, but requires a few steps that will test your ability to adapt to an already deployed network while implementing a new routing protocol.

Hope you enjoy!

Scenario

Company Tapan wants to enable EIGRP AS 1 on R1, R2 and R3. They would like to connectivity between all routers and subnets with the exception of the loopback interface on R1. R3 should NOT be able to communicate with R1′s Loopback interface. Unfortunately Tapan cannot eliminate advertisement of R1′s Loopback interface due to other network dependecies on the other side of R1 (unseen here).

Additionally Tapan is planning to segment the networks between R1, R2 and R3 using OSPF. They would like 2 OSPF areas. The OSPF area between R1 and R2 will be the core (Area 0). The area between R2 and R3 will be Area 1.

Tapan has determined that they’d like to reach R1′s loopback via OPSF. Tapan would like that R1′s Loopback interface be reachable via OSPF ONLY.

Tapan has hired you as the network consultant to configure their required network scenario.

When R3 can communicate with R1′s Loopback using the scenario above, your job is done.

Because R1 is a bit inflexible, the IP and EIGRP configuration is already in place and CANNOT be changed. Only OSPF can be configured on R1 to R2.

Routers Used: 3640

IOS: c3640-ik9o3s-mz.124-25b

Feature of Topology: EIGRP, OSPF, Route Redistribution

Image:

Download: GNS3-Labs – EIGRP & OSPF Route Manipulation.zip

Enjoy .. LBS

Disclaimer:

I perform all of these labs on my own using my own knowledge and experience (warning and disclaimer). They may very well be implemented differently than a method you might choose. So long as it meets the requirements and works, essentially it’s acceptable (In my feeble opinion). But if you notice a terribly or complicated method used by me to achieve the goals and you feel yours is much easier, makes sense or is the standard; please do share – I’m always open to learning

P.S. If you would like to donate for the time it takes to do all of this, feel free to use the link below. Thank you in advance for any contribution you make

There is no other agenda to these podcasts except talking about the topics. There is no vendor target, no advertisements, no bias – though we are all Cisco minded They cover subjects such as DDoS, IOS Licensing concerns, Dynamips, MPLS basics, Technical interview tips, datacenter switching and the list goes on!

Overall it’s a great show to listen to and best of all, you may know all the guests on the show from Twitter. So it feels even more realistic since you may have tweeted with these folks for some time now.

I enjoy the show very much and I enjoy the guests even more! I recommend you check out the Packet Pushers Podcasts! Trust me, you will love it!

Cheers guys!

Packet Pushers Podcasts – Listen In!!!

Using Microcore Linux in GNS3 To Simulate PC/Workstations/Computers

Thanks Kage!

Any assistance you need RE the use of Microcore should be directed to the GNS3 forums, NOT here I’m no expert..

If you have a hard time getting Microcore working – you can always try vpcs – Documentation can be found here -> How to simulate PC/Workstations/Hosts/Computers using vpcs

Cheers!

LB

This is another OSPF related lab from the Cisco Networking Academy Lab Portfolio. No EIGRP or other protocols involved. This lab involves the use of sub-interfaces, which changes your frame-relay statements – watch out and don’t get too confused

I perform all of these labs on my own using my own knowledge and experience (warning and disclaimer). They may very well be implemented differently than a method you might choose. So long as it meets the requirements and works, essentially it’s acceptable (In my feeble opinion). But if you notice a terribly or complicated method used by me to achieve the goals and you feel yours is much easier, makes sense or is the standard; please do share – I’m always open to learning

As mentioned before, these labs come from below. If you use the link below and purchase this book – you help me pay hosting bills

CCNP Building Scalable Internetworks (BSCI 642-901) Lab Portfolio (Cisco Networking Academy)

Instructions
Plan, design and implement the International Travel Agency network shown in
the diagram, and described below. Verify that all configurations are operational
and functioning according to the guidelines.

Scenario

The International Travel Agency needs its core network set up for OSPF with
the specifications indicated in the diagram and shown below.

• Use the addressing scheme shown in the diagram.
• Use OSPF with various networks shown in the diagram.
• Configure the OSPF backbone area to be on Loopback0 on Headquarters.
• Configure the Frame Relay subnets as point-to-point subinterfaces. The link between Headquarters and East should be in area 100, and the link between headquarters and West should be in area 300.
• Area 300 should be configured as an NSSA.
• Configure East’s loopback interfaces to be in area 200. Summarize this area with the most efficient summary.
• Redistribute the loopback network on West into OSPF.
• Create virtual links as necessary for full connectivity.
• Make sure that all loopback interfaces get advertised with the correct subnet mask.

Routers Used:2691(Any router type should be fine)

IOS: c2691-adventerprisek9_sna-mz.124-13b

Feature of Topology: OSPF, Redistribution, Summarization, NSSA, Point-To-Point, Sub-interfaces, Virtual-links

Image:

Download: GNS3-Labs:: OSPF Case Study Lab Scenario 2

Enjoy .. LBS

P.S. If you would like to donate for the time it takes to do all of this, feel free to use the link below. Thank you in advance for any contribution you make