Wendell's CCENT Skills Blog

Today we’ll wrap up this lab (hoorah!) with a discussion of the last major task for this lab. As with tasks 1 and 2, this lab task starts with an initial config as stated back in the 3rd post for this lab. However, in this case, I tell you one change – R3 gets a [...]

Today we’ll move on to the 2nd major task for this lab. As with Task 1, we’ll start with a look at the connected routes, and then chase a few subnets around the topology to find out if the routers appear to be missing any network, auto-summary, and passive-interface commands.

This is post 5I’ll list links to the first four posts after the fold. Today’s post: I’ll wrap up the analysis of task 1, specifically chasing many of the route advertisements so reverse engineer whether the config includes the network, auto-summary, and passive-interface commands.

This is post 4 so far in this lab. Check out the first three posts (post 1, post 2, and post 3) for the proper background. Today’s post: some analysis of major task 1, in which you predict why the routing tables on R1, R2, and R3 look like they were shown to be in [...]

Post 1 and Post 2 in this lab essentially set us up for today’s post. Today’s post gives you three big tasks, each of which assumes the same topology, IP addresses, and routing protocol (RIP-2) shown in the first two posts. In two of the tasks, your job is to figure out the specific configuration [...]

If you can’t predict what should be in the routing tables when you know the topology and the config (as shown in lab 3 post 1), then you’re not going to be able to predict the config based on the topology and some show command output. Today’s post completes the part of the initial part [...]

Today’s post begins a new CCENT lab, but with a very specific goal: to build troubleshooting skills for the exam. A little later, I may take the time to do a whole post just on the theory behind why I think this style of lab can help you learn some troubleshooting skills. The short version [...]

Today’s post wraps up CCENT Lab 2. I’ll likely extend this lab as lab number 3 as time goes on, because it sets up a nice discussion of auto-summary and maximum-paths. But as promised, today’s post looks at R3’s routing table, again using the configuration as shown in answer part 1, with emphasis on two [...]

Today’s post is really an attempt to get you to think about how RIP-2 works in the context of the lab exercise I started last week. To predict the contents of the IP routing table, you have to think about how routers add connected routes, how RIP advertises those routes, how RIP adds 1 to [...]

Today’s post gets the most basic part of the lab out of the way: the IP addressing and RIP-2 configuration. The lab problem statement tells you the interfaces, IP addresses, and masks, so the IP address configuration should be relatively straightforward, unless you just haven’t gotten to that topic in your reading so far. Today’s [...]