current topology and current focus

I think I’ve figured out part of the problem I’ve been having.  I haven’t been entirely focused on my studies, and I don’t really have a set goal right now.  I’ve been dancing with the idea of skipping the CCNP and going straight to the IE written.  Because of that, I’ve been reading chapters in the IE written exam certification guide, chapters in the BCMSN gook, and still reviewing notes, videos, and chapters from the BSCI studies.

With the way work has been going, I haven’t had as much time to study at work, and I don’t have the office space/time to study at home.  I live in a small apartment, and my rack is sitting in my living room.  I may need to bit the bullet and pay for the power consumption to leave the rack running at night.  I can stay an extra hour or so at work after hours to study quietly and access the rack from work.

Either way, I AM going to go for the NP.  I’m spending the next week or so going back through my written notes, watching videos again, and reading chapters in the BSCI book over the next week or so.  I bought the BSCI Lab Portfolio a month or so ago, so I’ll spend the next week going through those labs at night.

The physical topology for the bulk of the labs has four routers and one switch.

These are the routers and switch that I’ve added to the mix.  At some point, I know the lab guide will add the frame switch and possibly another router.  I need to pick up a few extra WIC-1T cards soon.

I made it through the first few EIGRP labs, tonight.  The objectives were pretty basic…

1.  Configure EIGRP on an interface.  simple

r1# configure terminal

r1(config)# int eth fa 0/0

r1(config-if)# ip addr

r1(config-if)# router eigrp 1

r1(config-router)# network

2.  Configure the bandwidth command to limit EIGRP bandwidth

r1(config-if)# bandwidth 64 ! bandwidth in kbps

3.  Verify EIGRP adjacencies

r1# show ip eigrp neighbors

or the alternative and more verbose

r1# show ip eigrp neighbors detail

4.  Utilize debugging commands for troubleshooting EIGRP

r1#  debug eigrp packets ! don’t forget to issue no debug all afterwords.

5.  Challenge:  test convergence for EIGRP when a topology change occurs.

This one was kinda weird.  The preferred path from R3 to a loopback on R1 is going to be via fast ethernet.  The lab has you ping from R3 to lo 3 on R1 with 100,000 pings(this is done using the ping $ip repeat 100000 command).  During these pings, you are to kill R1’s FA interface.  We haven’t modified the variance in EIGRP, and the AD through R2’s serial interface to R1 is more than the FD to lo 3, so the route doesn’t exist in the topology table.

When we killed FA 0/0 on R1, we obviously lost six pings while EIGRP discovered the new route through R2.  What confused me, was when I brought FA 0/0 back up on R1, we lost 33 or 34 pings while while the route through R1’s FA port came back up.

I’ll make it through the remaining EIGRP labs tomorrow night, and hopefully I’ll get through the OSPF labs.  I know there is going to be some slight re-cabling to bring the frame switch back into the mix.  I just hope I have enough WIC-1T interfaces to cover the physical topology change.


One Response

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: