Saturday, May 28, 2011

Capstone One Blog

This is an exploratory blog to discuss questions as the rise during Paul Browning's 60 Day to a CCNA crash course with two friends, Dave and Matt as we each tackle the class. The long term goal is to narrow the field of choices for my capstone project as well by tying together the two emphasizes--psychology and computer networking.


  1. One topic Dave topic Dave brought up is the rapid progression towards IPv6 from IPv4 and the numerous devices that require a network address that were nonexistent jet over a decade or so ago especially portable devices; smart phones, Ipads,

  2. OSPF timers allow a router to verify a link before advertising the network to make sure the link is not "flapping" (state in which the newly found link might be going up and down)

  3. I'm reading about OSPF, and wondering what determines which Autonomous System a router is part of. I.E. set manually my admin, or does OSPF detect it, etc.

  4. Steve,
    glad to see the first thoughts here.
    The key, I think, to pulling this off will be lots and lots of notes, a continuous and comprehensive journal of various aspects of the project, including, perhaps, your own personal feelings and fears and triumphs and progress.

    There will also be the technical aspects that these comments address.

    If you'll make a set of posts, as opposed to sets of comments, it will be easier to see the progression.

  5. Dave,

    The Autonomous System (AS) is also called the process id in OSPF. It is configured by the admin when defining the routes or subnets that OSPF will share with other routers that are in the same OSPF area. The AS or process id does NOT have to match with the process id of another router to become neighbors. In eigrp they do.

    For example: R1 R2 and R3. All in area 0. R1 has a process id of 1 as does R2 but R3 has a process id of 5. therefore because all three are in the SAME area (assuming everything else is configured correctly) all three routers will share their databases with their neighbors.

  6. This comment has been removed by the author.

  7. Guys,

    After our discussion on redistributing static routes I realized that I might have mislead you both in the explanation. Let me try to rephrase what I told you.

    R1 has a static route to the ISP. However this route is not known by R2. Instead of typing "redistribute connected" which will yes in a way share the route to the ISP you could type "redistribute static" as well. This will specifically redistribute only static routes. I think this would work better in this case.