NMC DOiT Vol.2 Scenario 1 Day 2


I still have teething issues in the lab rack. My R6 is not responding to console commands or pings to an interface I’m fairly sure I configured yesterday. I also found that my R3 cables are swapped, Fa0/0 with Fa0/1. R3 is an easy fix. But R6 is a little disconcerting; I’ll look at it in the morning when I’m back in the office.

Tonight I completed the frame relay and Cat 3550 configuration. I made as much headway as I could on the OSPF configuration, but had to stop because of my dead R6. In this scenario, I need R6 to do OSPF virtual links, among other things.

Teething issues aside, I am learning a lot of technical details, but nothing that’s completely new (so far). Putting the effort into studying for the written like I did is paying off big-time now. Here’s a list of technical topics I touched on tonight while working in the lab for about 1.5 hours:

  • Configuring OSPF in non-broadcast networks
    • Forcing DR with priorities to best leverage a hub and spoke frame design.
    • Manually assigning OSPF neighbors (required in a non-broadcast OSPF segment, unicast only).
  • General OSPF
    • Creating areas.
    • Advertising specific networks into areas.
  • Catalyst tasks
    • Creating VLANs.
    • Creating extended VLANs.
    • Coping with VTP when using extended range VLANs.
    • Manual VLAN pruning.
    • Configuring ISL and 802.1q trunks.

Most all of this was straightforward. There was only one task I ran into where I was scratching my head. The scenario wants me to advertise a particular /32 loopback interface into OSPF. You can’t use a network statement. You can’t redistribute connected. The route must show up in OSPF as an E2. So…I was making the incorrect assumption that you would be able to do this task with what had already been completed in the scenario, and thus my head-scratching. My assumption was wrong. I’ll be able to use one of the other IGP’s that I haven’t yet configured to redistribute into OSPF. So, no problem – I just have to remember to go back to that OSPF task I will have to leave behind for now.

Hopefully R6 will not be a big issue. If it continues to be a problem, I have a 2621XM sitting on a shelf I can use in the existing R6’s place. That 2621XM is my personal router – I think I’ll bring it with me tomorrow, just to be on the safe side. I don’t want to go all weekend with a dead R6. It’s going to hold up my schedule…

About the author

Ethan Banks

Most people know me because I write & podcast about IT on the Packet Pushers network. I also co-authored "Computer Networks Problems & Solutions" with Russ White.

Find out more on my about page.


  • R6 was just that flaky console port showing up again. I reseated the cable, and the console came back to life. The ethernet was unpingable because I haven’t yet provisioned the IPs. If I’d been paying closer to my CDP neighbors last night when I was all flustered, I would have noticed that the router was still up. Lesson learned.

  • Hi Ethan,

    Seems the googlebot found you and so did i. ;)
    You seem like a man with a plan, well focused and task oriented. Those two would help you tons when push comes to shove. In the words of Scott Morris
    Plan the Work and work the plan.
    Keep it up.

    Would it be too much asking for an RSS feed so we can syndicate your posts? Won’t take more than 5 minutes of your time to enable the wordpress plugin, promise.

  • The RSS feed is enabled, and has been since I started the blog. If you’re using Firefox, the orange syndication icon appears in the address bar. But to make it a little easier to find the RSS, I’ll put a couple of links in the page footer.


Most people know me because I write & podcast about IT on the Packet Pushers network. I also co-authored "Computer Networks Problems & Solutions" with Russ White.

Find out more on my about page.

Subscribe via Email

Receive complete, ad-free posts in your inbox as I publish them here.