Cisco CCNA ICND2 640-816

Cisco CCNA ICND2 640-816

Cisco CCNA certification proves your professional worth. It tells prospective employers that you can handle the day-to-day work of running a mid- to large-sized Cisco network....
show more

Cisco CCNA certification proves your professional worth. It tells prospective employers that you can handle the day-to-day work of running a mid- to large-sized Cisco network.

The two-exam CCNA process covers lots of innovative features, which better reflect the skills and knowledge you'll need on the job. Passing both exams is your first step towards higher-level Cisco certification, and trainer Jeremy Cioara has mapped these CCNA training videos to the 640-816 test. This CCNA training is not to be missed.

Here's how one user described Jeremy's training: "By the way, Jeremy Cioara has to be by far one of the BEST Cisco trainers I have ever had the privilege to learn from overall. He not only keeps your attention but his energy is contagious and he provides the information at a level where you grasp it rather easily."

The last day to take the 640-816 exam is Sept. 30, 2013. After that date, the only ICND2 exam available will be 200-101. CBT Nuggets has a training course for the 200-101 exam here.

All trademarks and copyrights are the property of their respective holders.

1.
Review: Rebuilding the Small Office Network, Part 1
(33 min)

Jeremy begins the ICND2 course by rebuilding much of the network that existed in ICND1 as a "cram-session" review of key concepts. This video focuses on the LAN (switch-based) environment.

2.
Review: Rebuilding the Small Office Network, Part 2
(28 min)

The ICND1 network rebuild continues. This video focuses on the key router concepts and configurations.

3.
Review: Rebuilding the Small Office Network, Part 3
(23 min)

The ICND1 review wraps up with a full implementation of RIP routing across the office network.

4.
Switch VLANs: Understanding VLANs
(16 min)

VLANs have absolutely changed the face of networks over the last decade; it is rare to walk into any large network that is not built upon a VLAN foundation. This video walks you through the definition of VLANs and discusses how to architect VLANs for your network.

5.
Switch VLANs: Understanding Trunks and VTP
(39 min)

The VLAN discussion continues through the ideas of VLAN Trunking and the VLAN Trunking Protocol (VTP). These allow VLANs to stretch through your entire organization rather than remaining on a single switch.

6.
Switch VLANs: Configuring VLANs and VTP, Part 1
(35 min)

The VLAN configuration wraps up as we assign the switchports to the necessary VLANs and implement Inter-VLAN routing using a router-on-a-stick configuration.

7.
Switch VLANs: Configuring VLANs and VTP, Part 2
(39 min)

Installing redundant switch links in a network environment is absolutely critical to a network's success. At the same time, installing redundant links in a network environment can cause the entire network to crumble in a few seconds. Interested? Join Jeremy as he discusses the place of the Spanning Tree Protocol (STP) in network environments.

8.
Switch STP: Understanding the Spanning-Tree Protocol
(28 min)

CCNA training continues with; good switching practices, what switch loos are and how to stop them and specifics of spanning tree protocol operation.

9.
Switch STP: Configuring Basic STP
(21 min)

While STP is operational on every Cisco switch by default, it needs to be modified to work optimally. This video walks you through the initial STP implementation and optimization.

10.
Switch STP: Enhancements to STP
(29 min)

Because STP was created many years ago, it is not optimized for the speedy convergence that networks require in our modern times. This video discusses the recent STP optimizations implemented through the Rapid STP protocol.

11.
General Switching: Troubleshooting and Security Best Practices
(29 min)

CCNA training continues with; To wrap up the LAN section of the ICND2 course, Jeremy walks you through switch troubleshooting best-practices and hits common trouble spots in a LAN environment.

12.
Subnetting: Understanding VLSM
(18 min)

If there's one concept everyone in the Cisco must know, it's IP subnetting. ICND2 expands on the subnetting foundations of ICND1 by introducing Variable Length Subnet Masking (VLSM). Keep in mind, the original subnetting videos from the ICND1 course are available as an appendix to this course.

13.
Routing Protocols: Distance Vector vs. Link State
(26 min)

The ICND1 course focused primarily on Distance Vector routing protocols such as RIP. The ICND2 course branches into the Link State and Hybrid routing protocols. This video explores the difference between these routing protocol categories and discusses the problems associated with Distance Vector routing loops.

14.
Routing Protocols: OSPF Concepts
(30 min)

OSPF is, by far, the most popular routing protocol in the world. Despite its popularity, it is also one of the most complex routing protocols in existence. In this video, Jeremy discusses the key concepts behind the OSPF routing protocol.

CCNA training continues with; It's now time to implement the OSPF concepts in our network. This video walks you through the conversion of the ICND2 office network from RIP to OSPF. Jeremy goes quite a bit beyond the standard CCNA curriculum to demonstrate a multi-area OSPF configuration that includes route summarization!

16.
Routing Protocols: EIGRP Concepts and Configuration
(32 min)

Cisco created EIGRP to combine the best features of Distance Vector (easy to configure) and Link State (many features) into a single routing protocol. This video discusses the concepts and configuration of the EIGRP routing protocol.

17.
Access-Lists: The Rules of the ACL
(27 min)

Cisco access-lists are used not only for security purposes, but for just about every major network configuration you will find on a Cisco router. This video discusses the key concepts behind access-lists and their configuration.

18.
Access-Lists: Configuring ACLs
(34 min)

CCNA training continues with; Access-lists in action! This video walks you through the configuration of standard access-lists in practical scenarios.

19.
Access-Lists: Configuring ACLs, Part 2
(48 min)

The access-list action continues! This video walks you through the configuration of extended access-lists in practical scenarios.

20.
NAT: Understanding the Three Styles of NAT
(20 min)

You'll be hard-pressed to find any network in operation that is not using Network Address Translation (NAT) in some form. In this video, Jeremy walks through the three forms of NAT implemented in today's networks.

21.
NAT: Command-line NAT Configuration
(35 min)

It's time to provide Internet access to our ICND2 office network. This video explores the configuration of each of the three forms of NAT.

22.
WAN Connections: Concepts of VPN Technology
(33 min)

It's time to turn our attention to the Wide Area Network (WAN). One of the fastest growing "WAN technologies" is not really a WAN technology at all: Virtual Private Networks (VPNs). VPNs use existing Internet connections to connect remote offices and users. In this video, Jeremy walks you through the place of VPNs in today's network and the basics of VPN security.

23.
WAN Connections: Implementing PPP Authentication
(34 min)

Leased Lines are one of the more conventional ways to interconnect office networks. There are two data link protocols used to operate leased line connections in the Cisco realm: HDLC and PPP. This video reviews the benefits of each and reconfigures the ICND2 office network to use PPP authentication.

24.
WAN Connections: Understanding Frame Relay
(28 min)

Packet Switched networks are still the darling of the WAN link industry, combining the best of two worlds: performance and price. Frame Relay continues to reign as one of the more popular Packet Switched network types. This video discusses the concepts, terminology and design of a Frame Relay network.

25.
WAN Connections: Configuring Frame Relay
(30 min)

There are two possible ways to configure a Frame Relay network: using a Multipoint or Point-to-Point configuration. In this video, Jeremy sets up both and offers some advice as to what is the best Frame Relay design.

26.
IPv6: Understanding Basic Concepts and Addressing
(34 min)

Welcome to the Next Generation: TCP/IP version 6 (IPv6). Everything is changing and changing fast. The Internet2 is growing with new networks every day. This video prepares you for the upcoming IPv6 transition by walking through the new addressing standards and communication types.

27.
IPv6: Configuring, Routing, and Interoperating
(23 min)

Cisco routers have begun to support TCP/IPv6 configurations. This video walks you through the configuration of IPv6 addresses on your routers and even shows the configuration of RIP Next Generation (RIPng)! Finally, Jeremy wraps up this video by discussing strategies to migrate your network from running IPv4 to IPv6.

28.
Certification: Some Last Words for Test Takers
(13 min)

To wrap up the CCNA course, Jeremy gives some last words to test-takers on how best to prepare for the ICND1, ICND2, and CCNA certification exams.

29.
Advanced TCP/IP: Working with Binary
(25 min)

This video begins the move to the world of advanced TCP/IP addressing. More specifically, you will learn the skill of IP subnetting. One of the most foundational skills in subnetting is converting from decimal to binary and back. This video carefully explains this skill and provides many examples to practice.

30.
Advanced TCP/IP: IP Subnetting, Part 1
(55 min)

The first style of subnetting you'll need to learn is the ability to separate IP addresses into subnets based on the number of networks an organization needs. This video walks through the initial style.

31.
Advanced TCP/IP: IP Subnetting, Part 2
(22 min)

The second style of subnetting you'll need to learn is the ability to separate IP addresses into subnets based on the number of hosts an organization needs in each network. This video explains this style.

32.
Advanced TCP/IP: IP Subnetting, Part 3
(19 min)

The final style of subnetting you'll need to learn is the ability to reverse engineer subnets based on the IP address and subnet mask that has been given. This video discusses this final style.

Review: Rebuilding the Small Office Network, Part 1

Review: Rebuilding the Small Office Network, Part 2

Review: Rebuilding the Small Office Network, Part 3

00:00:00

All right, we've moved in to rebuilding the small office network Part Three. Without any further delay, I'm going to pick up right where we left off, which was routing protocols. Let's just take a moment to get back up to speed with where we left off. In the previous video we set up the foundation

00:00:17

configuration in all these routers; the names, the passwords the IP addresses and the work environment that we were going to be working in for the rest of the series. And now we've got to a point where all the routers have IP addresses, but they can't really reach anything. Well I shouldn't say that, they can only reach

00:00:37

what they are directly connected to. Since we don't have routing turned on, the routers are able to ping local interfaces, because that's all they know about. So what we need to do is enable a routing protocol or static routes, a bunch of them or let's just use a routing protocol, RIP in this example, to get these routers to tell each other about what they know. Now we're going to

00:00:58

set up RIP and use RIP in our initial configurations and later on we're going to pull RIP out and put in some other routing protocols and see their advantages. Now you also see I've got the internet IP address up here, this is Rs, and this is the ISP that we're going to be routing to to get off to the internet, but I want to hold off on doing that until we set up RIP and I want to show you why once we get there. So let's start off on router one.

00:01:25

To set up a RIP, what i'm going to do is first off do, I've got my alias right, so S is for show IP interface brief, get a view of the interfaces, so I know exactly what network commands to type in. Now I also type in, show IP protocols just to make sure

00:01:41

there's no running protocols running; it's blank, that's good. So we get into the global configuration mode and I'll turn on RIP by typing in in router RIP. Now that enables RIP, it's like a light switch, I just turned on the routing protocol, but I turned it on in version one. Now

00:01:58

version one came out, the engine was developed in the late 60s, I am not kidding. The 1960s was when the the RIP engine was developed that we are running right now and we don't want to use that. We want the use version two, which came out in around the 80s which enhanced a lot of the features, it made it classless. So we can handle

00:02:16

different submit masks. It added authentication where we could have passwords between our routers, that sort of thing. So I want to turn on version 2 on all the different devices. Now comes the big command, network. We type in network followed by what network

00:02:31

we would like to run RIP on. Well this command does two major things and these are the two big ones I want to talk about. When I type in network and am going to follow it up with, let me type it in as I say it, 192.168.1.0. What that does is tell RIP to advertise this network to all of its neighbors. So when RIP starts forming neighbors

00:02:54

router one is going to send out advertisements saying, hello I know about 192.168.1.0. I know about this whole network and that's great because that is going to be the network that were advertising that we're able to reach. Now for router two that's not going to be much information

00:03:11

because it's going to think, oh well I'm connected to it, so I already know about that. I do not want to advertise this network, the public network, because I don't want any public routes going into my internal system. We're using private addressing inside of this company and if we start advertising public routes all throughout the system, it can be a bad system for security and again I will explain more of that as we get deeper into the running protocols. I only want these routers to know about

00:03:39

their private networks. So for router one I am done. Before I go on to router two, let me mention that was the first thing that network command does is advertise that network to everybody else. The second thing that it does is choose what interfaces to send advertisements out of. Now again,

00:03:58

bad English, but I think you get the point. When I type in network 192.168.1.0 that tells RIP send hello MS word or send advertisements updates out Ethernet 0/0, because it starts with 192.168.1.something It's not going to send advertisements out on this interface because it doesn't start with 192.168.1. 192.168.1.something Now final thing, remember in RIP and I know we're using classy addressing here, so it's not going to be is obvious, but remember in RIP it is still in its configuration class full. So for example, if I had

00:04:35

10.1.2 network over there to the left, I would advertise it into RIP by typing in network 10.0.0.0, because by default 10 is a class A address. So there's my cram session on RIP. So now that is configured on router one I can jump back and do a show IP protocols; the same command I typed right here in return nothing. To find out that RIP is

00:04:59

running, sending updates, broadcasts once every 30 seconds, the next one is due in eight seconds. So we start the count down and it's going to send another broadcasts. Now notice down here it doesn't see any other routing information sources. That's because no other routers

00:05:14

are running RIP. Once we get router two running, we should see router two as a source of information. We also see the networks it's running on and the Ethernet it's sending average, I should say the interface that it is sending advertisements out of, good.

00:05:29

So let's save the R config, hop over here to router two. I am going to go into global config mode; let's do that show IP interface brief command. Notice I did do space S to execute a show command from global config mode and I can see that I've got fast Ethernet 0/0 and serial 0/1/0, their my valid interfaces that will be valuable when I type in router RIP. I'll do version

00:05:55

two, get version two running and network 192.168.1.0, that will allow it to advertise and talk to router one. Then I'll type in the network 192.168.2.0, which allows it to advertise and communicate out the WAN link. So at this point I should be able to jump back here and do a show IP protocols on router two.

00:06:20

and see that we are running RIP were advertising for 192.168.1 and 2.0 out of these interfaces It hasn't heard from router one yet, because it waits 30 seconds before it sends the updates, router one is. So I'm sure if we hit the up arrow a few times, give it 30 seconds, we will actually see that. Let's hop back over router one.

00:06:43

Do a show IP protocols and you can see, there it is, router one has seen router two now as one of its sources. So I should be able to do a show IP router now on router one and see one of these networks that have been learned by RIP. Now remember it only knows about connected interfaces of the box so by running RIP we've now learned about 192.168.2.0 So at this point I should be able to ping, well let's ping everything, let's ping router two, two, ping 196.168.1.2, that's router two's IP address, of course we should be able to ping that. How

00:07:18

about its serial 0/1/0 over here, 192.168.2.1 Sure enough we are successful, because it knows about that RIP router. It can reach that network through this next hop IP address. Now let's try and ping router three over here, 192.168.2.0, oh sorry 2.2. It knows about the 2.0 network, right, so that should work, right? Ah, not so. The reason that it's failing and this is a

00:07:54

big void in a lot of people's minds when they're doing routing. You have to remember routing is always a to a two way street, it's a two way process. When router one is pinging router three, it's actually sending the packets because it knows how to reach that network, it's coming down here and remember the source addresses is, 192.168.1.1, it hits router two, because that's the next IP address. Router two knows how

00:08:18

to get to router three. So if it forwards the packet, ooh down over here router three. If we were able to put a packet sniffer around the line will actually see the ping request coming from router one and being received by router three. The problem is it's coming from a

00:08:35

source IP address of 192.168.1.1, and router three does not know about 192.168.1 network yet. So when it's getting those is looking at routing table for the return path to send a reply back and it' saying, I don't know how to get there. The routers aren't smart

00:08:53

enough to say, well I saw it come in this interface, so I will just go back out that interface, they rely on the routing table for everything. So in order to allow those pings to be successful to router three right here, we've got to set up RIP over there. So

00:09:08

I'll top over to router three. I'll do a show IP interface brief, I'm not used to my alias yet. I'll go into router RIP version two network 192.168.2.0 and 3.0. So it will both send advertisements out of and advertise these networks. So with that in place, lets see if it has happened yet, it may take a moment, oh wow that was fast, router three has now learned about 192.168.1.0 So if I go back to router one, notice all I did was set up RIP, go back to router one and try that ping command again, success, we are there, because router three now knows how to get back. We should be able to successfully

00:09:53

ping between everything; 3.1 that's the Ethernet interface of router three. As a matter of fact, let's go one step further let's do a trace route 192.168.3.1, enter. See right there we went through router two and then we were able to reach router three. Now you can see when you ping,

00:10:12

or when you do a trace route, it does three separate pings to each hop. For some reason and it's actually technically described on CISCO's website if you're interested enough, it will always drop the second ping of the final hop using a trace route. I can't

00:10:27

remember why that is, but that's the fact. So don't ever worry about losing the second ping on the final hop, that's just a known issue if you will. So at this point, I am going to hop around and save my config on all three of those routers just doing the right command. Also remembering that the CCNA approved method is copy

00:10:46

run start, but right is much easier. So we now have RIP configured, I would say we're halfway there, half a check on this step. step. Now the next step is the default route. Let me just clear off all the scribbles right here and give us a clean slate. Alright we're going to now move into this Ethernet

00:11:07

0/1 interface up here and get it configured and then we'll set up a default router to the internet. So move over to router one. Show IP interface brief, there's our Ethernet 0/1, it's currently shut down. So let's go in to global config mode interface Ethernet0/1 and how about I scrunch this down a little bit, there we go, so we can see what's going on.

00:11:31

on. I am going to do the IP address, 68.110.171.98. Now it's a slash 27 masks, so that will be, convert that to decimal, 255.255.255.224, enter, Got that up, sorry I am moving my window around as we go just so I can get my best possible view there. So did I do no shut, if

00:11:59

not there we go. So we've got the address that is set subnet mask, so I didn't do a no shut, so the interface has now come up and let's do a ping 68.110.171.97 which is our ISP, hit enter and there we go, we've got this successful ping that is now going through. We are able to reach the internet. Now with

00:12:21

that in place we have an internet connection, but we don't have any route to the internet, meaning if I were to ping some internet host, I always like pinging 4.2.2.2 that's a public DNS server. It's maintained by universities, it's the easiest address to remember in the world; great way to test internet access. So

00:12:41

if I try and ping them and I know that they allow pings, it is failing and the reason why is because if I do a show IP route, the only thing that this router knows about is the RIP route that it's learned about from inside our organization and the connected interface to the ISP. It doesn't know about the internet routes beyond the ISP. Now

00:13:01

there's no way RIP is going to manage to that size routing table, so what most organizations use and what we will use in here is a static default route. We do that by typing IP route, all zeros for the IP address, all zeros for the subnet mask and then our ISP address. So I'll just copy it and save myself some typing,

00:13:24

and put 97 in there. So that says to this router send everything that you don't know about over to the ISP. You can see automatically the routing table shows, gateway of last resort is 68.119.171.97 We also see the static route tagged with little star, which means it is the candidate default route.

00:13:44

So that is the default route for everything. Let's try pinging 4.2.2.2 again hit enter, glorious. We now have successful pings over to the DNS server, we are able to ping the internet. So our internet access is now up. Well at least it is from router one, because remember

00:14:03

all of the other routers in our organization can get to the internet, but they're coming from private addresses. As soon as they reach the ISP they're going to be blocked, because private addresses are not allowed, that's why we have NAT which is going to allow us to translate all of those addresses before they go. Now I'm not going to do NAT at this point, because that will be something

00:14:26

that we do later on via the command line. So with the last piece in place what I want to do is verify and backup our configuration. I want to use the CISCO discovery protocol just like we did on the switch to verify are connections. TFTP, that's where we can set it up.

00:14:41

up at this host right here as the TFTP server 1.50 and we will copy some of our configurations over there; do show IP router interfaces, just verify that everything looks good. I am going to start back on router one, because there is still one ultra cool thing I want to show you. Router one has the default

00:15:00

route to the internet, right. He knows how to get to the internet. The other routers are not able to reach the internet for two reasons, one was the NAT reason I just discussed, but number two is they don't have a default route. I would have to go on robert two and do the IP router 0.0.0 point it to router one and say send everything you don't know about router two to router one and I would have to do the same thing on router three.

00:15:23

That's known as putting in a default router. Now NAT would be the second piece of that to allow them to reach the internet. What I want to show you is a feature that CISCO has that is very cool. It can be done for just about any routing protocol and what I can do is go into, in this case, we are using RIP, router RIP and type in the command redistribute static.

00:15:47

Now just by looking at that command it should in your mind trigger okay I'm going to send, I am going to redistribute, I am going to send some static routes into the RIP process. Now if I do a show IP route, the only static route that we have is that default route. So I am advertising that

00:16:04

route into RIP. So what it's done is kept me from having to go to all these other routers and give them them a default route. Let me show you. I'll hop over to router two and do a show IP route. And look at this, a default route learned via RIP it's not a static route anymore, that automatically adjusts itself sending everything to 192.168.1.1, which is router one that picture. If I were to hop over to router three show IP route,

00:16:35

I can see that this one has a default route as well, sending everything to router two. So that will save you a lot of work of having to type in static routes or default routes on every router in your organization. Now I should also mention at this point,

00:16:48

that that is something that is not truly discussed until you get to the CCNP video series, so that's bonus info, it's good stuff. So we've got verify and back sitting on router one; let's do a show CDP neighbors, just to verify our connections. Now you can see that I have two connections to CBT switch two. I'm

00:17:10

actually using the same switch to reach the internet going through the internet from that switch and that same which is connecting me to the LAN. so I'm able to verify my connections there and I am going to now back up my configuration on router one. Now TFTP

00:17:29

this was something that we didn't do in the initial video. I just backed up my configuration through notepad, because TFTP is useful for backing a bunch of configurations up to a centralized server. First things first, TFTP server of choice, this one right here.

00:17:45

TFTPD 32, by I think it's Ph. Jounin, just do a google search for TFTPD32, it's free you can download and install it on Windows and it is a great TFTP server platform. So just by installing this on Windows, double clicking the icon poof my local 192.168.1.50. This guy right here has become a TFTP server. So if I jump

00:18:12

on over to my router one, let's make sure that I can ping before I do the copy, 192.168.1.50, we are able to ping it. I can type in copy config to TFTP, enter. What is the address of the host, it's 1.50. What do you want to name that file when you copy it over; by default it is going to name it R1 config. I'll actually keep that name, but I'll put R1 config.text And actually before I do anything I'm going to change my directory that's is the TFTPs point to a folder on my desktop called TFTP, otherwise it just throws files all over my desktop.

00:18:58

So I've got TFTP as my destination folder, that's what I'll name it, enter, and not much action happened there. I can look at the log and you see that it received a file from that host in what you received the right request for that. Good, so now I'm able to go over to router two,

00:19:17

I always ping the host before you try and TFTP so it doesn't hang there forever if it can't reach it; good, copy running config TFTP. I'll actually show you another way to do it, I could say, tftp://192.168.1.50/ we'll do do r2-c-, what did I name it up there, config.text enter and it will automatically have all these things filled in for me. So that's a matter of preference if you

00:19:45

like doing the URL style or just letting it walk through the wizard you can you can do either or. So I hit enter, see if I can pop this up in time. Oh, we saw it flash. These running configs are very small, so you don't see too much copy time and then finally let's go over to router three. Since we have RIP set up, router three

00:20:04

should be able to reach over here to this LAN and be able to get it's config over. So do copy running config, wait a sec I almost broke my own rule, let's first ping the TFTP server and make sure we're able to reach it, sure enough. Now will do a see cut and paste is so great, copy running config TFTP ping, we will name it router three enter, enter, enter and poof, success. We have now copied that over. Now if I,

00:20:35

see if I can find it, alright I am going to display my desktop, which is an empty black hole, where is that TFTP folder, there it is, right there. TFTP and bring it up. There is all of the configuration files that I have now copied over. Looks like I copied router two configure at some point, but config without the eye all three of them. If I double click, it opens

00:21:02

in notepad, which is brutal because note pad does not understand return characters, so everything is all in one line here, nice. So what I prefer to do if you're using Windows is open with word pad, where we will format it much better. So that is creating a true

00:21:17

backup of all the configurations of our routers. Now one last thing I'd like to do and that is backup our IOS. Let me just get my network diagram back in place. There we go. I want to back up a copy of the IOS just so that we can review how to do that. I am sitting on router

00:21:39

one and I am going to do a show flash, because the IOS is stored in flash. There is a 2,600 router, I can see the IOS file name right there; so I can type copy flash TFTP, let the wizard guide me. This is one you definitely want to copy and paste for, because this is so prone to miss types. So I just

00:21:58

copy that name in there, that's the source, the address of the TFTP server still, 192.168.50. It will keep the same file as the destination. I hit enter and now you can see it's copying that IOS version over. If I grab my TFTP server, jump over here you can see that is receiving that file from that host. So that is our way that we can backup our

00:22:23

IOS and also how we upgrade our IOS, we could just reverse this command and type copy TFTP flash to copy the IOS from the TFTP server into flash. So this is a great way to review Rebuilding the Small Office Network. Let me get back to my objective slide here. I am hoping that acted as

00:22:45

a great dive in with both feet sort of review to lay that networks foundation before we get into the new stuff. Everything from here on out will be building on top of this infrastructure, it is going to kind of add the features that we're looking for to enhance and grow this network into instead of a small office network, move into a medium large even, you could say enterprise class some of the enterprise style features will be talked about as we go throughout this series. So we're in

00:23:13

these last two videos, we walked through a review of key router concepts; things like running protocol, static routes, assigning IP addresses, based configurations and we did a review of the key configurations; that's all we did was walk through a complete set up of a small office network. I hope this has been informative

Switch VLANs: Understanding VLANs

Switch VLANs: Understanding Trunks and VTP

Switch VLANs: Configuring VLANs and VTP, Part 1

Switch VLANs: Configuring VLANs and VTP, Part 2

Switch STP: Understanding the Spanning-Tree Protocol

Switch STP: Configuring Basic STP

Switch STP: Enhancements to STP

General Switching: Troubleshooting and Security Best Practices

Subnetting: Understanding VLSM

Routing Protocols: Distance Vector vs. Link State

Routing Protocols: OSPF Concepts

Routing Protocols: OSPF Configuration and Troubleshooting

Routing Protocols: EIGRP Concepts and Configuration

Access-Lists: The Rules of the ACL

Access-Lists: Configuring ACLs

Access-Lists: Configuring ACLs, Part 2

NAT: Understanding the Three Styles of NAT

NAT: Command-line NAT Configuration

WAN Connections: Concepts of VPN Technology

WAN Connections: Implementing PPP Authentication

WAN Connections: Understanding Frame Relay

WAN Connections: Configuring Frame Relay

IPv6: Understanding Basic Concepts and Addressing

IPv6: Configuring, Routing, and Interoperating

Certification: Some Last Words for Test Takers

Advanced TCP/IP: Working with Binary

Advanced TCP/IP: IP Subnetting, Part 1

Advanced TCP/IP: IP Subnetting, Part 2

Advanced TCP/IP: IP Subnetting, Part 3

Please help us improve by sharing your feedback on training courses and videos. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

Community Standards

We encourage you to share your wisdom, opinions, and questions with the CBT Nuggets community. To keep things civil, we have established the following policy.

We reserve the right not to post comments that:
contain obscene, indecent, or profane language; contain threats or defamatory statements; contain personal attacks; contain hate speech directed at race, color, sex, sexual orientation, national origin, ethnicity, age, religion, or disability;
contributes to a hostile atmosphere; or promotes or endorses services or products. Non-commercial links, if relevant to the topic, are acceptable.
Comments are not moderated, however, all comments will automatically be filtered for content that might violate our comment policies. If your comment is flagged by our filter, it will not be published.

We will be continually monitoring published comments and any content that violates our policies will be removed. Users who repeatedly violate our comments policy may be prohibited from commenting.

16

Hours

32

Videos

16 hrs32 videos

COURSE RATING

Basic Plan Features

Speed Control

Included in this course

Play videos at a faster or slower pace.

Bookmarks

Included in this course

Pick up where you left off watching a video.

Notes

Included in this course

Jot down information to refer back to at a later time.

Closed Captions

Included in this course

Follow what the trainers are saying with ease.

NuggetLab

Files/materials that supplement the video training

Premium Plan Features

Practice Exams

These practice tests help you review your knowledge and prepare you for exams.

Virtual Lab

Use a virtual environment to reinforce what you are learning and get hands-on experience.

Unless otherwise stated all references in this License Agreement to “training videos” or to "videos" includes both individual videos within a series, entire series, series packages, and streaming subscription access to CBT Nuggets content. All references to CBT or CBT Nuggets shall mean CBT Nuggets, LLC, a Delaware limited liability company located at 44 Country Club Road, Ste. 150, Eugene, Oregon.

A CBT Nuggets Learner is defined as a single user license and the single user license must be connected to a named user. The email address attached to the single user license must be specifically associated solely with that individual CBT Nuggets Learner. Accounts may purchase multiple learners, and each learner is assigned a single license. Each single user license is considered a CBT Nuggets Learner, and is expressly governed by the terms of this License Agreement.

GRANT OF LICENSE. CBT Nuggets grants you a non-transferable, non-exclusive license to use the training videos contained in this package or streaming subscription access to CBT content (the "Products"), solely for internal use by your business or for your own personal use. You may not copy, reproduce, reverse engineer, translate, port, modify or make derivative works of the Products without the express consent of CBT. You may not rent, disclose, publish, sell, assign, lease, sublicense, market, distribute, or transfer the Products or use them in any manner not expressly authorized by this Agreement without the express consent of CBT. You shall not derive or attempt to derive the source code, source files or structure of all or any portion of the Products by reverse engineering, disassembly, decompilation or any other means. You do not receive any, and CBT Nuggets retains all exclusive ownership rights, title and interests in the Products, including, but not limited to ownership rights in all copyrights, trademarks, service marks, or trade secrets. The Products are copyrighted and may not be copied, distributed or reproduced in any form, in whole or in part even if modified or merged with other Products. You shall not alter or remove any copyright notice or proprietary notice or legend contained in or on the Products. You shall take all reasonable steps and precautions to ensure that your use of the Products is in strict compliance with this License Agreement. Upon your discovery and/or the request of CBT, you agree to promptly remedy any violation of this License Agreement and to provide CBT with sufficient evidence that you are in compliance with this License Agreement.

TERMINATION OF LICENSE. Once any applicable subscription period has concluded, the license granted by this Agreement shall immediately terminate and you shall have no further right to access, review or use in any manner any CBT Nuggets content. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you are in violation of this License Agreement or if CBT believes you have exceeded reasonable usage. Upon the occurrence of any of these termination events, no refund will be made of any amounts previously paid to CBT.

DISCLAIMER OF WARRANTY AND LIABILITY. The Products are provided to you on an "as is" and "with all faults" basis. You assume the entire risk of loss in using the products. The Products are complex and may contain some nonconformities, defects or errors. CBT Nuggets does not warrant that the Products will meet your needs, "expectations or intended use," that operations of the products will be error-free or uninterrupted, or that all nonconformities can or will be corrected. CBT Nuggets makes and user receives no warranty, whether express or implied, and all warranties of merchantability, title, and fitness for any particular purpose are expressly excluded. In no event shall CBT Nuggets be liable to you or any third party for any damages, claims, losses, expenses, liabilities or costs arising out of, incurred because of, or related to the Products and/or this License Agreement (including, without limitation, compensatory, incidental, indirect, special, consequential or exemplary damages, lost profits, lost sales or business, expenditures, investments, or commitments in connection with any business, loss of any goodwill, or damages resulting from lost data or inability to use data), including attorney fees, irrespective of whether CBT Nuggets has been informed of, knew of, or should have known of the likelihood of such damages. This limitation applies to all causes of action in the aggregate including without limitation breach of contract, breach of warranty, negligence, strict liability, misrepresentation, and other torts. In no event shall CBT Nuggets' liability to you or any third party exceed $100.00.

REMEDIES. In the event of any breach of the terms of the Agreement CBT reserves the right to seek and recover damages for such breach, including but not limited to damages for copyright infringement, trademark infringement and for unauthorized use of CBT content. CBT also reserves the right to seek and obtain injunctive relief in addition to all other remedies at law or in equity.

APPLICABILITY. The provisions of this License Agreement will prevail over any conflicting provisions in any purchase order or other document issued by you in connection with your use of the Products.

MISCELLANEOUS. This is the exclusive Agreement between CBT Nuggets and you regarding its subject matter. You may not assign any part of this Agreement without CBT Nuggets' prior written consent. This Agreement shall be governed by the laws of the State of Oregon and venue of any legal proceeding shall be in Lane County, Oregon. In any proceeding to enforce or interpret this Agreement, the prevailing party shall be entitled to recover from the losing party reasonable attorney fees, costs and expenses incurred by the prevailing party before and at any trial, arbitration, bankruptcy or other proceeding and in any appeal or review. You are fully responsible for determining whether any form of tax is due relating to the Products or transactions, and you shall pay any sales tax, use tax, excise, duty or any other form of tax relating to the Products or transactions. If any provision of this Agreement is declared invalid or unenforceable, the remaining provisions of this Agreement shall remain in effect. Any notice to CBT under this Agreement shall be delivered by U.S. certified mail, return receipt requested, or by overnight courier to CBT Nuggets at the following address: Attn: Matthew L. Bromley, 44 Club Rd Suite 150, Eugene, OR 97401 or such other address as CBT may designate.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the License Agreement at any time, with or without notice.

CBT Nuggets Billing Agreement

By entering into a Billing Agreement with CBT Nuggets, you authorize CBT Nuggets to use automatic billing and to charge your credit card on a recurring basis.

You agree to pay subscription charges on a monthly, semi-annual or annual term based on your subscription, under the following terms and conditions:

All payments are non-refundable and charges made to the credit card or payment method under this agreement will constitute in effect a "sales receipt" and confirmation that services were rendered and received;

To terminate the recurring billing process and/or arrange for an alternative method of payment, you must notify CBT Nuggets at least 24 hours prior to the end of the billing cycle;

You will not dispute CBT Nugget’s recurring billing charges with your credit card issuer so long as the amount in question was for periods prior to the receipt and acknowledgement of a written request to cancel your account or cancel individual licenses on your account.

You guarantee and warrant that you are the legal cardholder for the credit card associated with the account, and that you are legally authorized to enter into this recurring billing agreement.

You agree to indemnify, defend and hold CBT Nuggets harmless, against any liability pursuant to this authorization.

You agree that CBT Nuggets is not obligated to verify or confirm the amount for the purpose of processing these types of payments. You acknowledge and agree that Recurring Payments may be variable and scheduled to occur at certain times.

If your payment requires a currency conversion by us, the amount of the currency conversion fee will be determined at the time of your payment. You acknowledge that the exchange rate determined at the time of each payment transaction will differ and you agree to the future execution of payments being based on fluctuating exchange rates.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the Billing Agreement at any time, with or without notice.

CBT Nuggets Privacy Policy

Data Collection

P3P policies declare the data they collect in groups (also referred to as "statements"). This policy contains 4 data groups. The data practices of each group will be explained separately.

Group "Access log information"

We collect the following information:

Click-stream data

Search terms

Last URI requested by the user

User agent information

This data will be used for the following purposes:

Completion and support of the current activity.

Web site and system administration.

Research and development.

This data will be used only by ourselves.

The following explanation is provided for why this data is collected:

Our Web server collects access logs containing this information.

Group "Cookies"

We collect the following information:

HTTP cookies

Unique identifiers

This data will be used for the following purposes:

Research and development.

One-time tailoring.

This data will be used only by ourselves.

The following explanation is provided for why this data is collected:

Cookies are used to track visitors to our site, so we can better understand what portions of our site best serve you. We also use cookies to allow our server to maintain information about the contents of your shopping cart.

Group "Transaction info (required)"

We collect the following information:

Physical contact information

Online contact information

Purchase information

Search terms

User's Name

Name of User's Employer

Transaction history

Computer information

This data will be used for the following purposes:

Completion and support of the current activity.

Research and development.

This data will be used only by ourselves. In addition, the following types of entities will receive this information:

Delivery services.

The following explanation is provided for why this data is collected:

Information we collect in order to process your purchase.

Group "Transaction info (optional)"

We collect the following information:

Name of User's Employer

User's Home Contact Information

User's Business Contact Information

Contact Information for the Organization

Organization Name

Department or division of organization

This data will be used for the following purposes:

Contacting visitors for marketing of services or products.

This data will be used only by ourselves. In addition, the following types of entities will receive this information:

Delivery services.

The following explanation is provided for why this data is collected:

Information we collect in order to process your purchase.

Cookies

Cookies are a technology which can be used to provide you with tailored information from a Web site. A cookie is an element of data that a Web site can send to your browser, which may then store it on your system. You can set your browser to notify you when you receive a cookie, giving you the chance to decide whether to accept it.

In some cases we may collect cookies from 3rd parties, such as Google or DoubleClick.

Compact Policy Summary

The following table explains the meaning of each field in the compact policy.

Field

Meaning

CP=

This is the compact policy header; it indicates that what follows is a P3P compact policy.

CAO

Access is available to contact and other information.

CURa

The data is used for completion of the current activity.

ADMa

The data is used for site administration.

DEVa

The data is used for research and development.

TAIa

The data is used for tailoring the site.

CONa

The data is used for contacting the user.

OUR

The data is given only to ourselves.

DELa

The data is given to delivery services.

BUS

Our business practices specify how long the data will be kept.

IND

The data will be kept indefinitely.

PHY

Physical contact information is collected.

ONL

Online contact information is collected.

UNI

Unique identifiers are collected.

PUR

Purchase information is collected.

COM

Computer information is collected.

NAV

Navigation and clickstream data is collected.

INT

Interactive data is collected.

DEM

Demographic and socioeconomic data is collected.

STA

State-management data is collected

The compact policy is sent by the Web server along with the cookies it describes. For more information, see the P3P deployment guide at http://www.w3.org/TR/p3pdeployment.

Policy Evaluation

Microsoft Internet Explorer 6 will evaluate this policy's compact policy whenever it is used with a cookie. The actions IE will take depend on what privacy level the user has selected in their browser (Low, Medium, Medium High, or High; the default is Medium. In addition, IE will examine whether the cookie's policy is considered satisfactory or unsatisfactory, whether the cookie is a session cookie or a persistent cookie, and whether the cookie is used in a first-party or third-party context. This section will attempt to evaluate this policy's compact policy against Microsoft's stated behavior for IE6.

Note: this evaluation is currently experimental and should not be considered a substitute for testing with a real Web browser.

Unsatisfactory policy: this compact policy is considered unsatisfactory according to the rules defined by Internet Explorer 6. The behavior of Internet Explorer 6 regarding cookies set under this compact policy is as follows:

First-party usage

Third-party usage

Persistent Cookies

Low: Policy satisfactory at this level; cookies will be accepted.

Medium: Opt-out is not provided for all unsatisfactory purposes and recipients, so the cookie will be downgraded to a session cookie.

Medium High: No opt-out is provided, so the cookie will be blocked.

High: Since opt-in is not required, the cookie will be blocked.

Low: Opt-out is not provided for all unsatisfactory purposes and recipients, so the cookie will be downgraded to a session cookie.

Medium: Opt-out is not provided for all unsatisfactory purposes and recipients, so the cookie will be blocked.

Medium High: Since opt-in is not required, the cookie will be blocked.

High: Since opt-in is not required, the cookie will be blocked.

Session Cookies

Low: Policy satisfactory at this level; cookies will be accepted.

Medium: Policy satisfactory at this level; cookies will be accepted.

Medium High: Policy satisfactory at this level; cookies will be accepted.

High: Since opt-in is not required, the cookie will be blocked.

Low: Policy satisfactory at this level; cookies will be accepted.

Medium: Opt-out is not provided for all unsatisfactory purposes and recipients, so the cookie will be blocked.

Medium High: Since opt-in is not required, the cookie will be blocked.

High: Since opt-in is not required, the cookie will be blocked.

A policy which is considered unsatisfactory by Internet Explorer 6 contains certain categories of data which are used or shared in a particular manner. This policy is placed in the unsatisfactory category, because the following categories of data are associated with this policy's cookies:

Physical contact information is collected.

Online contact information is collected.

In addition, the data is used in the following manner, marking the policy as unsatisfactory:

The data is used for contacting the user.

Note that allowing an opt-out will make this policy acceptable under the Low and Medium settings, and under Medium High for first-party cookie usage. At the High setting, and at the Medium High setting for third-party cookies, all of these data uses must be opt-in for the policy to be considered satisfactory.

Social Media

Opinions expressed on this website and in any corresponding comments are the personal
opinions of the original contributing authors, not of CBT Nuggets, LLC. The content is
provided for entertainment, educational, or informational purposes only and is not meant
to be an endorsement or representation by CBT Nuggets, LLC or any other party. Visitors
may post reviews, comments, photos and other content, submit suggestions, questions, or
other information, so long as the content is not illegal, obscene, threatening, defamatory,
invasive of privacy, infringing of intellectual property rights, or other injurious to
third parties. You may not use a false email address, impersonate any person or entity,
or otherwise mislead as to the origin of your content and/or your identity.

This site is available to the public. No information you consider confidential or desire
to remain private should be posted to this site. By posting you agree to be solely responsible
for the content of all information you contribute, link to, or otherwise upload to the website
and release CBT Nuggets, LLC from any liability related to your use of the posting in its entirety.
If you choose to post, you grant CBT Nuggets a non-exclusive, royalty-free, perpetual, irrevocable
and fully sub-licensable right to use, reproduce, modify adapt, publish, translate, distribute,
and display such content throughout the world in any media. This includes, but is not limited to,
use of website url, links, pictures, movies, and commentary.

Posts are moderated for relevance and suitability and are approved at the discretion of the moderator.