magnify
CCENT STUDY GUIDE

CCENT Study GuideHave you been wanting to get your Cisco Certification for some time now?

Are you just starting out on your Cisco path and need some direction?

Well, I can help! I have over 7 years of networking experience and personally know what it takes to get your CCENT.

Testimonials

This is by far the best ICND1 Study Guide out there

"This is by far the best ICND1 Study Guide out there. Does not require people to invest time in topics that aren’t even covered in the ICND1 exam. Topics are well put together and really detailed. Easy to follow.” - Martin Lora

“I got my CCENT after passing my ICND1 Exam and I am looking at getting my ICND2 out of the way soon. I’m going to pick up your other book and plan to tell others to use your materials.  Thanks.”  - Travis Applebaum

Free Bonus GIft

Subnetting is probably one of the most important topics on the ICND1 Exam

I’m throwing in for free my Complete Guide To Mastering How to Subnet!

Subnetting is probably one of the most important topics on the ICND1 Exam and just to make sure you will master how to subnet I’m throwing in for free my Complete Guide To Mastering How to Subnet! My subnetting ebook is over 50 pages long and contains everything you could possible want to know about subnetting and is guaranteed to make you ready for the ICND1 Exam. You seriously are getting a great book here and I’m throwing it in for FREE!

100% Guarantee

CCENT Study Guide GuaranteeAbsolutely ZERO Risk, 100% Guarantee

I know that you will learn everything you need to know to pass your ICND1 exam with my book

I’m going to give you 30 days to read and study it to your hearts content 

On Sale Now!

You can’t really afford not to invest in The Complete ICND1 Exam Study Guide.

It’s easy to get started. Just click the button to the right.

 

Networkcraft – CCNA Lab 08: Using RIP Instead of Static Routes

Welcome to my 8th lab in guiding you toward your CCNA Certification where you are going to learn how to configure RIP which is a routing protocol that keeps you from having to use static routes everywhere. Don’t get me wrong, in some cases it is important to have static routes, configuring a routing protocol can save you a lot of time and can auto adjust to failures if they occur.

If you haven’t read any of the previous labs I suggest you start there. This lab builds off of lab 07 where we configured three routers with ip address and set up static routes so that we could ping between them.

This tutorial uses Networkcraft – The Online Network Simulator, which consists of the three terminal windows shown below. You can type in them to configure each of the routers, just like you would to configure an actual cisco router.

Router 1

Router 2

Router 3

And in the image below is the topology layout of the three routers that we will be using in this tutorial. The first thing that we are going to do is configure each of the ip address on each of the interfaces just like they are marked in the topology.

CCNA Lab 07: 3 Router Topology

*NOTE: If you want to follow along with the tutorial and still type in each of the terminal windows of each of the routers without having to scroll up and down all the time it might be easier to open this page in another window and arrange them on the screen so that you can look at them side by side.

Step 1: Configure the e0 interface on Router 1

I’m going to go a little faster through these steps because we’ve already done these steps multiple times in the previous tutorials.

Here are the commands to configure the e0 interface on r1:

Router>enable
Router#config t
Router(config)#hostname r1
r1(config)#interface e0
r1(config-if)#ip address 10.10.1.2 255.255.255.0
r1(config-if)#no shutdown
r1(config-if)#exit
r1(config)#exit
r1#

Step 2: Configure the e0 and e1 interface on Router 2

We are going to configure two interfaces this time, e0 and e1. Here are the commands:

Router>enable
Router#config t
Router(config)#hostname r2
r2(config)#interface e0
r2(config-if)#ip address 10.10.1.1 255.255.255.0
r2(config-if)#no shutdown
r2(config-if)#interface e1
r2(config-if)#ip address 10.10.2.1 255.255.255.0
r2(config-if)#no shutdown
r2(config-if)#exit
r2(config)#exit
r2#

Notice that we can go straight from interface e0 mode to interface e1 mode without having to exit down to configuration mode first.

Step 3: Configure the e0 interface on Router 3

Just like we did for r1 let’s configure an ip address on the e0 interface but in the ’10.10.2.0′ network:

Router>enable
Router#config t
Router(config)#hostname r3
r3(config)#interface e0
r3(config-if)#ip address 10.10.2.2 255.255.255.0
r3(config-if)#no shutdown
r3(config-if)#exit
r3(config)#exit
r3#

Step 4: Test our connection from r1 to r2

Now, let’s try and see if things are working correctly and see if we can communicate with r2 from r1:

r1#ping 10.10.1.1

If everything is working correctly you should get output printed to the terminal similar to this one: (don’t forget to scroll down)

Step 5: Try to ping from r1 to r3 (crazy!)

Now, let’s try something crazy and see if we can talk to r3 all the way from r1. Type in the following command in r1:

r1#ping 10.10.2.2

This should fail and you should get a 0% success rate. Remember from lab 07 that this doesn’t work because we don’t have an entry in our routing table for the ’10.10.2.0′ network.

If you want to look at our routing table you can with the ‘sh ip route’ command. You will see that there is only one entry.

Step 6: Configure RIP on each of the routers

Now we are going to configure RIP on each of the routers. RIP is a routing protocol which allows each of the routers to talk to each other and give updates about how each one is doing. Follow these commands to configure RIP on each router.

Configure RIP on r1:

r1#
r1#config t
r1(config)#router rip
r1(config-router)#network 10.10.1.0
r1(config-router)#network 10.10.2.0
r1(config-router)#exit
r1(config)#exit
r1#

Configure RIP on r2:

r2#
r2#config t
r2(config)#router rip
r2(config-router)#network 10.10.1.0
r2(config-router)#network 10.10.2.0
r2(config-router)#exit
r2(config)#exit
r2#

Configure RIP on r3:

r3#
r3#config t
r3(config)#router rip
r3(config-router)#network 10.10.2.0
r3(config-router)#network 10.10.1.0
r3(config-router)#exit
r3(config)#exit
r3#

Step 7: Look at our routing table

Now that we have RIP set up let’s look at our routing table on r1:

r1#sh ip route

After you type in the ‘sh ip route’ command you should get the following output after you scroll down:

As you can see from the last line of the output we now have a route for the 10.10.2.0 network.

Step 8: Now we can ping from r1 to r3

Now that we have RIP setup on each of the routers we should be able to ping from r1 to r3:

r1#ping 10.10.2.2

After you ping r3 from r1 you should get the following output:

Look it worked this time!

Congratulations you just completed Lab 08. Where you learned how to set up RIP instead of using static routes like you did in the previous lab.

Video Walkthrough

I know that sometimes it’s nice to watch some one go through the whole process and can help clear up any spots you got stuck on.

Thanks for taking the time to go through this lab and I hope that it can help further you a long in your pursuit of your CCENT or CCNA Certification. Please leave a comment below with any suggestions or questions that you may have.

Thanks,
-Blake Erickson

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
2 Comments  comments 

Networkcraft – CCNA Lab 07: Static Routes and Pinging Between 3 Routers

This is Lab 07 where we are going to learn about using the routing table, how to set up static routes, and verifying that everything works by pinging between all three routers. This tutorial uses Networkcraft – The Online Network Simulator to walk you through this tutorial and so that you can practice programming the routers yourself without having to install or purchasing your own equipment.

Networkcraft uses a command line interface just like what you will find in an actual Cisco router or switch. If you haven’t already worked through the previous tutorials I suggest you do so before moving on if none of this is familiar to you. Let’s begin!

This is the topology that we are going to use for this lab. We have 3 routers connected to each other. Router 2 is connect to both Router 1 and Router 2.

CCNA Lab 07: 3 Router Topology

Below you will find the terminal windows for the 3 routers that we are going to use in this lab. Inside of these terminal windows is where you are going to be typing in the commands to configure each router. The rest of the tutorial is shown below after these terminal windows.

Router 1

Router 2

Router 3

Before we officially begin the tutorial you will most likely need to click on the “restart” link under each router to clear out any settings that still might be saved from previous tutorials.

Step 1: Configuring Router 1

The first thing we are going to do is rename the router so that we don’t confuse it with any of our other routers. To rename your router follow these steps:

Router>enable
Router#config t
Router(config)#hostname r1
r1(config)#

To rename the router we entered enable mode and then entered configuration mode. Once in configuration mode we typed in ‘hostname’ followed by the name we want to call our router, in this case ‘r1′.

Now let’s configure Router 1 with an ip address on its e0 interface.

r1(config)#interface e0
r1(config-if)#ip address 10.10.1.2 255.255.255.0
r1(config-if)#no shutdown
r1(config-if)#exit
r1(config)#exit
r1#

What we did here was enter interface mode for ‘e0′, then we typed in the ip address followed by the subnet mask, then we turned on the interface with the ‘no shutdown’ command, then we exited out of interface and configuration mode.

Step 2: Configure Router 2

We are going to do almost the exact same thing that we did for Router 1, but change the hostname to ‘r2′ and use the ip address ’10.10.1.1′. Here are the commands to do this:

Router>enable
Router#config t
Router(config)#hostname r2
r2(config)#interface e0
r2(config-if)#ip address 10.10.1.1 255.255.255.0
r2(config-if)#no shutdown
r2(config-if)#exit
r2(config)#exit
r2#

Step 3: Test Connection Between Router 1 to Router 2

To test the connection between Router 1 and Router 2 go to Router 1 and type in this ping command:

r1#ping 10.10.1.1

If everything is configured correctly your output on the command line after you scroll down should like like this:

Step 4: Test Connection Between Router 2 to Router 1

Just do double check let’s go ahead and test the connection from Router 2 to Router 1:

r2#ping 10.10.1.2

Here is a screen shot of the output that you should get after typing in the above command on Router 2:

Step 5: Configure e1 Interface on Router 2

Just like we did in step 2 we are going to configure Router 2 again, but this time we are going to configure the e1 interface instead of the e0 interface.

Follow these commands to configure the e1 interface:

r2#config t
r2(config)#interface e1
r2(config-if)#ip address 10.10.2.1 255.255.255.0
r2(config-if)#no shutdown
r2(config-if)#

The above commands configured the e1 interface with the ip address of ’10.10.2.1′.

Step 6: Configure e0 Interface on Router 3

Just like we did in the step 1 we are going to do almost the exact same thing but use interface e0 on router 3 and give it the ip address of ’10.10.2.2′. Follow these steps to configure router 3:

Router>enable
Router#config t
Router(config)#hostname r3
r3(config)#interface e0
r3(config-if)#ip address 10.10.2.2 255.255.255.0
r3(config-if)#no shutdown
r3(config-if)#exit
r3(config)#exit
r3#

Step 7: Test Connection Between Router 2 to Router 3

Now let’s ping from Router 2 to Router 3 using the ping command and the ip address ’10.10.2.2′:

r2#ping 10.10.2.2

The output of your ping command should look like the screen shot below:

Step 8: Test Connection Between Router 3 to Router 2

To double check that everything is work correctly let’s try the connection in the other direction:

r3#ping 10.10.2.1

The output of your ping command from Router 3 should look like the screen shot below:

Step 9: Try to Ping from Router 1 to Router 3

Since we have been able to verify that we can ping between r1 and r2, and from r2 to r3, let’s see if we can ping from r1 to r3.

r1#ping 10.10.2.2

This should NOT work and you should get out put like the screen shot below:

So, why doesn’t it work? Let’s take a look at our routing table to see.

Step 10: Looking at the Routing Table

To look at the routing table of one of our routers we will use the ‘sh ip route command’ which will show you the contents of your routing table.

So, on r1 type in the ‘sh ip route’ command

r1#sh ip route

The output of this command should like the screen shot below:

Please don’t get overwhelmed with the above output because we really only need to look at the very last line. The first part of the ‘sh ip route’ output just displays a list of codes. Go ahead and look for code ‘C’ and code ‘S’ because those are the codes that we are going to be using in the rest of this tutorial.

No if you look at the last line of this output you see that it begins with a ‘C’. The ‘C’ means that this is a directly connected route. The next part of this output shows the network address ’10.10.1.0′.

As you can see there is only route entry and there is no entry for the ’10.10.2.0′ network where r3 resides. To add an entry to the routing table for the ’10.10.2.0′ network perform the following command which we will cover in the next step.

Step 11: Creating a Static Route

To create a static route on r1 for the ’10.10.2.0′ network so that you will be able to ping from r1 to r3 use the ‘ip route’ command:

r1#config t
r1(config)#ip route 10.10.2.0 255.255.255.0 10.10.1.1
r1(config)#exit

There are 3 parts to the ip route command. The first part is the network you want use. The second part is the subnet mask for that network. The third part is the ip address of the next hop router, in this case this is the ip address of e0 on r2.

Now type in the ‘sh ip route’ command again:

r1#sh ip route

Now if you look at the last line of the output you will see that our static route has been added.

Now let’s configure the other static route on r3 to finish our configuration.

Step 12: Create a Static Route on Router 3

Follow these steps, just like the ones in Step 11, to set up a static route on r3 to the ’10.10.1.0′ network.

r3(config)#
r3(config)#ip route 10.10.1.0 255.255.255.0 10.10.2.1
r3(config)#exit
r3#sh ip route

Now let’s see the output of the sh ip route command that we just typed in:

As you can see from the last line of the output we now have a static route set up that goes to the ’10.10.1.0′ network via the ’10.10.2.1′ interface.

Step 13: Ping from r3 to r1

Now that we have our static routes set up we can ping all the through from r3 to r1 and from r1 to r3.

Let’s go ahead now and ping r1 from r3:

r3#ping 10.10.1.2

This is the output that you should see now:

Summary

Congratulations you just finished lab 07! Remember that we learned how to set up 3 routers and configured them to used two different networks. Since the routers were in two different networks we couldn’t ping between them until after we set up a static route.

Thanks for completing this tutorial and I hope it helps prepare you for your CCENT/CCNA Exam.

I invite you to leave a comment below if you have any questions or ideas about future labs.

Thanks,
-Blake Erickson

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

The 4 Commonalities in Every Single Network

A lot of my posts lately have been about configuring Cisco routers and I wanted to go back and talk about some big picture things as well as some foundational topics that will help lay the ground work to learning the rest of the things you need to know to get your CCNA Certification. In short, you will be tested on this material and it will help you become a great network administrator.

This post gives a broad description of four things you will find in every network. This is the big picture view from 50,000 feet looking down on what we will be learning about networks in preparation for your CCENT/CCNA Exam and what you will be working with in the networking industry. Later on we will dive much more indepth on each of these topics: rules, messages, medium, and devices.

The nice thing about these commonalities is that they will apply to every single type of network you will be dealing with. Large networks, small networks, wireless networks, old networks, new networks, or even satellite networks so that you can talk to the mars rover.

1. Rules

Every network has rules that determine how the message can be sent, received, passed on, and interpreted.

Networking standards have been devopled that define a lot of these rules so that devices from different venders can still communicate with each other.
Without these rules we wouldn’t be able to have networks. Computers wouldn’t know how to talk to each other and you wouldn’t have the future opportunity to be a networking engineer because the field wouldn’t exist.

Lucky for us though we do have rules regarding network communication. Having rules in some cases might seem restrictive, but in networking these rules are vitaly important in increasing network efficiency and making sure things just work.

2. Messages

Every network has data traveling across it (that is the whole point of building networks in the first place). Networks pass on information, whither it be messages, video, voice, files, the devices in the network don’t really care because all they see are the tiny packets that make up those data types that we are passing back and forth.

I say that the networking devices don’t really care about the data traversing the network, which is probably the case in smaller networks, but as your network becomes more soffisticated it will have the ability to priorities different types of traffic or “messages”. And an example benifit of this is the ability to make sure voice packets from your IP network get first priority so that the telephone calls don’t become choppy just because someone is downloading a large file.

3. Medium

Every network has a way to connect to different devices in order to pass the message from the source all the way to the destination. Medium can be many different types of cabling or even wireless. The most common medium that you will find today is most likely Fast Ethernet which oberates at 100 Mbit/s. However Gigabit or 1000Mbit/s is becoming the new standard.

As a networking engineer you are going to deal with a lot of different kinds of mediums. You will have some type of connection from your Internet Service Provider (ISP), such as several T1 lines or a broadband connection of some sort like DSL. You might have to work with fiber connections if you are connected buildings together that are far apart that exceeds the range of copper ethernet cables.
Especially today with everyone bringing tablets, cell phones, and laptops you are going to need to be experienced in wireless networking. You will have to make sure you have full coverage in the buildings you are in and can support the needed bandwidth of all the potential devices.

4. Devices

A network has devices that are used to pass on data from the source to the destination. For smaller networks and for the ICND1 Exam we are going to focus on just two devices, routers and switches, but you will experience other equipment like modems, hubs, bridges, and repeaters.

You will also need to keep in mind that all of these different kinds of devices come from several different vendors, and sometimes from many different time periods, but they all need to work together.

Having a varied array of devices all needing to talk to each other can sometimes cause quite a few headaches and problems, but if you can understand the big picture as well as all the tiny details of how each device works you can build a solid network.

Chances are you aren’t going to be in charge of designing and building a brand new network for someone (in some cases you will), but you will be hired on to work in an existing environment that will be a mix of old and new hardware and probably has a lot of growing pains. That’s okay though, it makes are jobs that much more fun and our knowledge and skill that much more valuable.

Real World Example

Just as an example of what you might be dealing with is I used to work on a network that had CNC machines that were connected to a serial network hub, but they also had to connect to our 100 Mbit/s network so that the engineers to send jobs to them and check on their status. There was also many other types of legacy equipment that used old networking technology, but they still worked fine, so it didn’t quite justify paying $20,000+ to replace some machines.

I wanted to share with you this information because when I was going through my Cisco training I thought it was such a waste of time to learn about old technology and protocols that I thought no one could possibly be using today. And the truth is that some companies can’t justify upgrading equipment just to support newer networking technology when everything is working fine and they won’t see a big enough increase in productivity or profits. And besides at this point in your career you could be thrown into any situation and you’ll be glad you took the time to establish a solid foundation of network knowledge so that you can get yourself out of any tough situation.

###

Photo Credit: Paul Fisher

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

Networkcraft – CCNA Lab 06: Ping Between Two Routers

Welcome to another CCNA lab using Networkcraft – The Online Network Simulator. I’ve been excited to write this lab for some time now because it involves setting up two routers and getting them to talk to each other, which is what networking is all about. In all the previous labs up to this point all we did was configure a single router, which is an important step in the learning process, but networking becomes a lot more fun when you start adding more routers and other devices.

Below you will find two routers that we can configure. Remember that Networkcraft uses a command line interface just like most actual Cisco routers. And you will also find something similar during the simulation portions of your CCENT or CCNA Exam. To configure these two routers you can follow the steps below.

Router 1

Router 2

Here is the topology of the two routers that we are going to configure. They are connected together with a cross-over cable to both of their ethernet-0 interfaces:

Step 1: Configure Interface e0 on Router 1

The first thing that we need to do is configure the interfaces on each router to be in the same subnet. What this means is that the ip address we assign on router 1 and the ip address that we assign on router 2 both need to be in the same network specified by the subnet mask. Let’s start by configuring the interface e0 on Router 1. To do this follow these commands:


Router>enable
Router#config t
Router(config)#hostname r1
r1(config)#

The first step that we did above was to get into configuration mode and then change the hostname to “r1″ so that we don’t get our two routers confused. Now lets configure the e0 interface:


r1(config)#interface e0
r1(config-if)#ip address 192.168.1.1 255.255.255.0
r1(config-if)#no shutdown
r1(config-if)#

The commands above got us into interface configuration mode for e0. We then assigned the ip address 192.168.1.1 followed by the subnetmask 255.255.255.0. We then typed in the ‘no shutdown’ command to turn the interface on.

Step 2: Configure Interface e0 on Router 2

We are going to do exactly the same steps as Router 1 except use “r2″ for the hostname and change the ip address to “192.168.1.2″.
Here are the commands that you will need to type in to Router 2 (make sure you use the second terminal window on this page):


Router>enable
Router#config t
Router(config)#hostname r2
r2(config)#interface e0
r2(config-if)#ip address 192.168.1.2 255.255.255.0
r2(config-if)#no shutdown
r2(config-if)#

Step 3: Ping Router 2 from Router 1

Now that we have both routers configured with an ip address on the same subnet we should be able to ping between them. To test this, let’s start by going to Router 1 and pinging the ip address on Router 2:


r1(config-if)#exit
r1(config)#exit
r1#ping 192.168.1.2

After you get out of interface configuration mode and configuration mode by typing in exit twice you can type ‘ping 192.168.1.2′.
You will now need to scroll down and you should get something just like the output below. You should see 5 exclamation points and a success rate of 100 percent.

sample output:

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5). round-trip min/avg/max = 1/2/4 ms
r1#

If you see 5 periods “…..” instead of 5 exclamation points “!!!!!” then you will need to see if the ip address are both in the same network and if both of the interfaces are turned on.

Step 3: Ping Router 1 from Router 2

Since we can ping Router 2 from Router 1 we should be able to ping Router 1 from Router 2. Let’s try it just to be sure:


r2(config-if)#exit
r2(config)#exit
r2#ping 192.168.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5). round-trip min/avg/max = 1/2/4 ms
r2#

You should get a ping confirmation with a 100 percent success rate just like you did from Router 1. If you didn’t something could either be wrong with the ip addresses or the interfaces could be turned off. You can also check your running configuration to see how things are configured.

While taking the CCENT or CCNA Exam the simulation isn’t going to tell you when you are done or not. It is up to you to check that everything works and to make sure everything is configured correctly before moving on to the next question.

Video Tutorial

Below is a video tutorial showing pretty much the exact same steps as above just using different ip addresses. Hopefully the video can help clarify steps you weren’t sure of.

This concludes lab 06 – Pinging between two different routers. If you have any questions, comments, or suggestions I invite you to post them below. I would love to hear from you and good luck with your studies.

-Blake Erickson

###

Photo Credit: Dave

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

Networkcraft – CCNA Lab 05: Configuring Ethernet Interface


Welcome back to another tutorial on learning how how to configure a Cisco router to help prepare you for the CCENT and CCNA Exams.

In the previous labs we learned how to use the command line interface to name your router, add a password, configure telnet and encrypt passwords. In this lab we are going to go over how to configure your ethernet interface.

Just below this paragraph you will see a terminal window for Networkcraft – The Online Network Simulator. It uses a command line interface to make configurations just like an actual Cisco Router. You will also find something simular during your simulation sections of the CCENT and CCNA Exams. Now lets get started!

Step 1: Get into interface configuration mode

Most routers have at least a couple of different interfaces on them so that they can connect to an ISP and other devices in your network like a switch. In this tutorial we are going to configure the Ethernet 0 interface. Before you can configure an interface you need to be in “interface configuration mode”. To get there, follow these commands:


Router>enable
Router#config t
Router(config)#interface e0
Router(config-if)#

Once you get into configuration mode you can type in the interface command followed by the name of the interface. For this tutorial our ethernet interface is called “e0″. Once you get into interface configuration mode you will see that the name of the prompt changed to: “Router(config-if)#”. The “if” part stands for InterFace.

Step 2: Configure The Ethernet Interface

Before the interface can be used in an actual network it needs to be configured. The interface needs to have an ip addressed with a subnet mask attached to it, and it also needs to be turned on.

Follow the step below to configure the ip address ’192.168.1.1′ with the subnet mask ’255.255.255.0′.


Router(config-if)#ip address 192.168.1.1 255.255.255.0

Step 3: Turn on the Ethernet Interface

To turn on the ethernet interface make sure you are still in interface configuration mode and type: ‘no shutdown’. If you type just ‘shutdown’ then the interface will be turned off. And so to turn it on you will type ‘no shutdown as shown below:


Router(config-if)#no shutdown

Step 4: Verify Configuration

It’s always a good habit to verify your configuration. To do this let’s look at our running configuration by typing in the following commands. Typing exit twice takes you out of interface configuration mode and then configuration mode. Typing in ‘sh run’ prints out the running configuration of your router.


Router(config-if)#exit
Router(config)#exit
Router#sh run

Your console screen should now be filled up with your running configuration. If you scroll down through it you should see a line that starts with “Interface Ethernet 0″ followed by the settings we just configured. Below is an example screen shot of what your running configuration should look like:

That concludes this lab. I’m not completely sure yet, but the next lab that I want to do will show you how to configure interfaces on two different routers and ping between them.

Thanks for going through this lab and if you have any questions, comments, or requests please comment below. I would love to hear from you!

Thanks,
-Blake Erickson

###
Photo Credit: Denby Jorgensen

 
Tags: , , ,
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
1 Comment  comments 

Networkcraft – CCNA Lab 04: Using the Service Password-Encryption Command

Welcome to CCNA Lab 04: Using the Service Password-Encryption Command.

Each lab that I write is geared to help you learn and establish a foundation of networking skills that will not only help you pass the CCNA Exam, but will help you make a knowledgable network administrator.

These labs use Networkcraft – The Online Network Simulator to walk you through the process of configuring Cisco routers. Networkcraft was created to help those who didn’t have easy access to Cisco equipment learn what is needed to get certified. However, if you do have actual Cisco equipment that you can use, you are welcome to use that as well to complete this lab.

Let’s Begin CCNA Lab 04

In the previous lab we learned how to configure passwords for line con 0, line aux 0, and line vty 0 4. As you will see in this lab if you go and look at your running configuration those passwords appear in plain text. This means that if anyone is looking over your shoulder or has access to the running configuration they will be able to see all of your passwords.

Today we are going to learn a new command that will encrypt those passwords so that you can’t just read them by looking at the running config.

Below you will find the Networkcraft terminal window that you can use to follow along with this lab.

Initial Setup of Line Interfaces

Let’s go ahead and set up our router how we left it in lab 03 so that we can look at a running configuration with some data in it. To get our router set up like in the previous lab type in the following commands.


Router#config t
Router(config)#line con 0
Router(config-line)#password icnd1
Router(config-line)#login
Router(config-line)#line aux 0
Router(config-line)#password icnd2
Router(config-line)#login
Router(config-line)#line vty 0 4
Router(config-line)#password ccna
Router(config-line)#login
Router(config-line)#exit
Router(config)#exit
Router#sh run

If we take a look at the first part of the running configuration first, it should say “no service password-encryption”:

If you now scroll all the way down to the bottom of your running configuration, you should see the passwords listed in plain text for line con 0, line aux 0, and line vty 0 4:

Using The Service Password-Encryption Command

By following the commands listed below, get back into configuration mode and type in the “service password-encryption” command:


Router#config t
Router(config)#service password-encryption
Router(config)#exit
Router#sh run

Now if we look at our running configuration again we should see “service password-encryption” at the top instead of “no service password-encryption”:

And if we scroll all the way down to the bottom of our running configuration we should see the the passwords are now encrypted:

Congratulations!

You just completed CCNA Lab 04: Using the Service Password-Encryption Command.

If you have any questions or input please leave a comment below. Thanks for working through these labs and I hope they can help prepare you to get your CCENT or CCNA Certification. Thanks for your support!

-Blake Erickson

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
2 Comments  comments 

Networkcraft – CCNA Lab 03: Securing Your Routers Incoming Lines

Networkcraft - CCNA Lab 03: Securing-your-routers-incoming-linesJust like I talked about in Lab 01 and Lab 02 the importance of these labs is to get you familiar with learning the command line interface on Cisco Routers and Switches. On the CCNA Exam Cisco will have at least two complete labs where you have to know many different commands and configuration settings before you can complete the lab. One of the difficulties of the labs is that they don’t tell you when you have completed that lab. You just have to rely on testing and making sure everything works and then move on to the next question on the test. Of course the idea behind these labs is to get you to pass the CCNA Exam, but more importantly I’m working on these labs and Networkcraft – The Online Network Simulator, so that you can learn how to administer Cisco Networking equipment properly and apply these skills directly into the work force.

Below are links to the previous two labs. If you haven’t completed them yet I recommend you start there.

Below is the Networkcraft terminal window and is what you will use to complete the lab as described in the rest of this tutorial. In this lab we are going to cover how to secure the auxiliary port, the console port, and the telnet (vty) lines.

 

Step 1: Getting into configuration mode

Before we can begin to configure the auxilary port, console port, and the telnet (vty) lines we need to get into router configuration mode. To do this type in the following commands in the above terminal.


Router>enable
Router#config t
Router(config)#

Step 2: Securing the console port

The console port is used to login to the router when you have physical access to it. Usually you will use the light blue console cable to login. It is always recommended that you set a console password. To set the console password type in the following commands:


Router(config)#line con 0
Router(config-line)#password ccna
Router(config-line)#login
Router(config-line)#exit
Router(config)#

Step 3: Securing the auxiliary port


Router(config)#line aux 0
Router(config-line)#password ccna
Router(config-line)#login
Router(config-line)#exit
Router(config)#

Step 4: Securing the telnet (vty) lines

Cisco routers typically can have 5 telnet sessions open, so unlike the console and auxiliary ports where there is only one port to configure, we need to configure 5 ports for all the telnet sessions. Luckily we don’t have to configure each telnet session separately.

By typing in the ‘line vty 0 4′ command we are telling the router to configure the lines 0 through 4 at the same time.


Router(config)#line vty 0 4
Router(config-line)#password ccna
Router(config-line)#login
Router(config-line)#exit
Router(config)#

Step 5: Verify the configuration.

To verify the passwords we just set for all the interfaces exit out of configuration mode and look at the running config, then scroll all the way to the bottom to look at the console, auxiliary, and vty lines.


Router(config)#exit
Router#sh run

... output ommitted ...

!
!
line con 0
password ccna
login
line 1 8
line aux 0
password ccna
login
line vty 0 4
password ccna
login
!
end
Router#

Congradulations!

You just finished the CCNA Lab 03: Securing Your Routers Incoming Lines. Stay tuned for the next lab so that you can continue to prepare for your CCNA Exam.

If you have any questions about the lab please post a commend below or feel free to email me using my email listed on the about page. I wish you success in your CCNA studies and thanks for your support!

-Blake Erickson

Photo credit: Greg McMullin

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

Networkcraft – CCNA Lab 02: Securing Your Router with the Enable Secret Password Command

CCNA Lab02 Securing Your Router with the Enable Secret Command

The CCNA Exam focuses on making sure you really understand how to configure Cisco routers and switches and not just memorize answers to multiple choice questions. So in order to help you understand how to configure Cisco Equipment I built Networkcraft – The Online Network Simulator along with these labs that I’m writing to walk you through the process. Feel free to use the terminal window below to complete this lab or if you have an actual Cisco router you can use that as well (just make sure it isn’t currently being used in a live environment).

In the previous lab we learned about how to change the name of your router so that you don’t confuse it with another router on your network and we also learned how to set the enable password.
If you have not done Lab 01 yet, or are not familiar with setting the hostname, I recommend you start there first.

In this lab we are going to learn how to set the “Enable Secret Password”. Unlike the “Enable Password” the “Enable Secret Password” is not stored in plain text. What this means is that someone looking at the configuration of your router will not be able to visually see what your password is because it is encrypted.

Using the “Enable Secret” command is the proper way to set the password on your router and should always be used over the “Enable Password” command. As you will see later in this lab if you already have an “Enable Password” set and you also set an “Enable Secret” password the “Enable Secret” password will always take precedence.

In the above terminal window you should have a fresh configuration, if not go ahead and click on the “restart” link above to clear out any of the configuration data.

Step 1: Get Into Configuration Mode

Before we can set the “Enable Secret” password we need to get into configuration mode. To do this type the following two commands:


Router>enable
Router#config t

Step 2: Using the Enable Secret Command

Now that we are in configuration mode we are going to set the “Enable Secret” password by typing in: ‘enable secret’ followed by the password of your choice. In this example we are going to set the password to: ‘ccna’. Here is how your terminal should look:


Router>enable
Router#config t
Router(config)#enable secret ccna
Router(config)#

Step 3: Testing our password

To test that our password works type in the following two commands to back out of enable mode:


Router(config)#exit
Router#disable
Router>

Your terminal prompt should now look like ‘Router>’. Now let’s go back into enable mode and type in the password we just set (hint: ccna):


Router>enable
password: ccna
Router#

Step 4: Look at The Running Configuration

Now that we are back into enable mode let’s go ahead and look at our running configuration. To do this type in the ‘sh run’ command:


Router#sh run
Current configuration:
!
version 0.0.1
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
enable secret 5 dfeaf10390e560aea745ccba53e044ed
enable password
!
!

The above output shows part of your running configuration currently on your router. If you look at the line that starts with “enable secret” you will see that it shows the encrypted version of the password we just set. This means that anybody who has access to your router configuration won’t be able to see what the enable secret password is.

Step 5: The “enable secret” password will always take precedence

The “enable secret” password will always take precedence over the “enable password” password. To test this out let’s set the “enable password” and then try and login again. Type in the following commands to test this theory:


Router#config t
Router(config)#enable password cisco
Router(config)#exit
Router#disable
Router>
Router>enable
password: cisco
password: ccna
Router#

As you can see from the above commands and output the ‘cisco’ password didn’t work and we had to use the ‘ccna’ password to get into enable mode.

Enable Secret Command Video Tutorial

This concludes the CCNA Lab 02: Securing Your Router with the Enable Secret Command and stay tuned for the next lab where we will configure the telnet and console passwords.

If you have any questions about the lab please post a commend below or feel free to email me using my email listed on the about page. I wish you success in your CCNA studies and thanks for your support!

-Blake Erickson

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
1 Comment  comments 

Networkcraft – CCNA Lab 01: Naming Your Router and Setting The Enable Password

Networkcraft - CCNA Lab 01: Naming Your Router and Setting the Enable Password

I released Networkcraft – The Online Network Simulator a while ago, but never included in labs or tutorials to go with it. Since Cisco routers use a command line interface there is a pretty heavy learning curve if you don’t have experience working with the command line. Networkcraft also uses a command line interface and for the CCNA exam you will also be required to know how to use the command line interface of a Cisco Router and Switch. This first lab and all the subsequent labs are to help you become familiar with learning how to how to configure Cisco Equipment, not only so that you can pass the CCNA Exam, but so that you can become an experienced network administrator.

Below is the Networkcraft terminal window for a sample router. You can type commands into it to configure the router. This first lab is going to show you how to name your router and how to set a password on it. The following labs will teach you many more things that you will need to know to pass the CCNA Exam. Let’s begin!

Step 1: Change the name of your router

You always want to give your router a descriptive name. Chances are that you will be configuring more than one router at a time and have two terminal windows open on your screen. If both of the routers your are configuring both have the same name like “router”, then it might be really easy to start configuring the wrong one.
In this step we are going to change the name of our router from “router” to “r1″. Sometimes people use the city that the router is in like, “Seattle” or “Portland”. Follow these steps to change your routers name to “r1″:


Router>enable
Router#config t
Router(config)#hostname r1
r1(config)#exit
r1#

See how the prompt changes from “Router>” to “Router#” to “Router(config)#”. Once we are in router configuration mode we can use the ‘hostname’ command followed by the new name of the router: r1. Notice when you press enter the name changes from “Router” to “r1″.

Congratulations! You have no successfully changed the name of your router.

Step 2: Configure the Enable Password

We want to make sure that your router is secure so that unauthorized people can’t make any changes. To set a password for the enable mode follow the steps below:


r1>enable
r1#config t
r1(config)#enable password cisco

Now that we have the enable password set, let’s back all the way out and try and get back into enable mode. Typing ‘exit’ will take us out of configuration mode. Then by typing ‘disable’ we will back out of enable mode.


r1(config)#exit
r1#exit
r1#disable
r1>

Now you can get back into enable mode and notice that it asks you for your password this time:


r1>enable
password: cisco
r1#

Now let’s see what happens when we type in the wrong password. Go ahead and back out of enable mode with the ‘disable’ command and then go back into enable mode with the ‘enable’ command. This time though type in a bogus password like “asdf”. It shouldn’t let you in. Now type in your real password.


r1#disable
r1>
r1>enable
password: asdf
password: cisco
r1#

Now let me show you why we typically don’t use the enable password command to secure your router. I’ll show you a better way in the next section. Let’s go ahead and looking at our running configuration by typing in the ‘sh run’ command. You then should get an output similar to the trunkcated output I have below. You might need to scroll up inside of the simulator to view the beginning of the ‘sh run’ output.
See where it says “enable password cisco”. It is showing your password in plain text. This usually isn’t a good thing to have your password exposed like that. Let’s go on to the next lab to see how you can encrypt your password instead.


r1#sh run
Current configuration:
!
version 0.0.1
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname r1
!
enable secret 5
enable password cisco
!
!
!

Video Demo

Below is a video showing you how to set the enable password. Sometimes it is easier to learn by watching someone else.

Congratulations!

You have completed the first lab

If you have any questions about the lab please post a commend below or feel free to email me using my email listed on the about page. I wish you success in your CCNA studies and thanks for your support!

-Blake Erickson

Click here to move onto CCNA Lab 02: Securing Your Router with the Enable Secret Password Command

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
5 Comments  comments 

Cisco backpedals after uproar, drops cloud from default router setting

Published on July 6, 2012 by in Uncategorized

ars technica:

Cisco has backpedaled tonight, with a blog post saying the service—Cisco Connect Cloud—will no longer be the default management tool. “In response to our customers’ concerns, we have simplified the process for opting-out of the Cisco Connect Cloud service and have changed the default setting back to traditional router set-up and management,” Cisco home network VP Brett Wingo wrote.

The company also said it “will not arbitrarily disconnect customers from the Cisco Connect Cloud service based on how they are using the Internet,” and that the “Cisco Connect Cloud service has never monitored customers’ Internet usage, nor was it designed to do so, and we will clarify this in an update to the terms of service.”

The bottom line is router administrators should be able to turn automatic updating back on without having to worry about losing router administration features. We’d still keep a close eye on it, though, because the blog post leaves some room for doubt.

It’s nice to know Cisco is trying to make things right, but I still don’t think automatically updating people’s routers with such a huge change was the best way to roll out this new “feature”.

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments