Start with 7 free days of training.

Gain instant access to our entire IT training library, free for your first week.
Train anytime on your desktop, tablet, or mobile devices.

Interconnecting Cisco Networking Devices Part 2

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....
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.
 show less
1. Review: Rebuilding the Small Office Network, Part 1 (33 min)
2. Review: Rebuilding the Small Office Network, Part 2 (28 min)
3. Review: Rebuilding the Small Office Network, Part 3 (23 min)
4. Switch VLANs: Understanding VLANs (16 min)
5. Switch VLANs: Understanding Trunks and VTP (39 min)
6. Switch VLANs: Configuring VLANs and VTP, Part 1 (35 min)
7. Switch VLANs: Configuring VLANs and VTP, Part 2 (39 min)
8. Switch STP: Understanding the Spanning-Tree Protocol (28 min)
9. Switch STP: Configuring Basic STP (21 min)
10. Switch STP: Enhancements to STP (29 min)
11. General Switching: Troubleshooting and Security Best Practices (29 min)
12. Subnetting: Understanding VLSM (18 min)
13. Routing Protocols: Distance Vector vs. Link State (26 min)
14. Routing Protocols: OSPF Concepts (30 min)
15. Routing Protocols: OSPF Configuration and Troubleshooting (39 min)
16. Routing Protocols: EIGRP Concepts and Configuration (32 min)
17. Access-Lists: The Rules of the ACL (27 min)
18. Access-Lists: Configuring ACLs (34 min)
19. Access-Lists: Configuring ACLs, Part 2 (48 min)
20. NAT: Understanding the Three Styles of NAT (20 min)
21. NAT: Command-line NAT Configuration (35 min)
22. WAN Connections: Concepts of VPN Technology (33 min)
23. WAN Connections: Implementing PPP Authentication (34 min)
24. WAN Connections: Understanding Frame Relay (28 min)
25. WAN Connections: Configuring Frame Relay (30 min)
26. IPv6: Understanding Basic Concepts and Addressing (34 min)
27. IPv6: Configuring, Routing, and Interoperating (23 min)
28. Certification: Some Last Words for Test Takers (13 min)
29. Advanced TCP/IP: Working with Binary (25 min)
30. Advanced TCP/IP: IP Subnetting, Part 1 (55 min)
31. Advanced TCP/IP: IP Subnetting, Part 2 (22 min)
32. Advanced TCP/IP: IP Subnetting, Part 3 (19 min)

Review: Rebuilding the Small Office Network, Part 1


Hello and welcome to the CBT nuggets ICND2 video series. My name is Jeremy Cioara. And I'm extremely excited to get going into this ICND part 2. I don't mean to set your expectation high or anything like that, but this series is going to be awesome. It's-I'm looking-I was-I put-I-Look at me, I can't even talk, that's how awesome it going to be. I just got finished recording the CCENT or ICND1 which is really good. I'm really happy with it. It is kind of an intro to networking, an introduction to CISCO. It talks about some of the key configuration of LAN switches and of routers and you know, it was really good package. But the reason I'm so excited to get into this is because this is where the technology really, you know, hits the road and starts running. I guess the best way I can describe this is, have you ever seen the movie Aladdin? It's an old Disney movie; cartoon for kids. And there's a part in that movie where this evil sorcerer, it's near the end, this evil sorcerer kind to moves up to the next level of his power. He becomes a genie and you just see him explode out of this building and it goes "Laughter The world is mine to control", you know, he got this evil villain kind of voice. Not that I'm an evil sorcerer or anything, but that's kind of what I feel like. When I was going through, ICND1 or CCENT, you know it-you know I would go to the configurations and then start going, it's like you start on a, you know kind of a smooth jog and you're going and going and all of a sudden, you get to a point and I stop. My mind would say wait you want to take them there but I couldn't because that it was way beyond the scope the ICND1 exam. But now, we can go there. It's almost like, we can start with this jog, and that what the initial videos are going to be about. I'll explain those in just a moment. And we can just go into this full sprint into this technology that will just blow your mind, it's awesome.


So, let me talk about what we're going to do as we begin this series. I'm starting of by rebuilding the small office network. It may have been some time between the CCENT series and the series for you so I intend these first few videos to be sort of a refresher in a very practical cram session sort of way. Just about everything that we do in these videos, first few videos, are going to be all live demonstration. Meaning you're going to see a network topology and we're going to build it. We're going to be walking through configuration after configuration and I'm going to go through and review the key LAN concepts as we're configuring them and the key LAN configurations is just to get your blood flowing again. Even if it hasn't been a while since the CCENT series, even if you just got certified, I would still say this is still good for you to go through because it's going to relay that foundation that as we get into the series I'm going to assume we're all on the same page and get us all ready to go. So, what we're going to start of with is LAN concepts, meaning the switch as usually where most networks began is all the PCs and servers connecting to a local area network switch. We're going to get that switch configured and then move into the routers and begin configuring our internet connections and wide area connections between offices. This is where we'll begin. This is our network that we're going to rebuild as we begin this series and then begin enhancing as we go through. We have three routers that we're going to be configuring in the upcoming videos. One that is connected in the internet, two of them that are between offices, essentially this over here represents one office and then we a have WAN link over here to another small office over here.


So we'll configure those routers but what we're going to focus on right now is that the orange halo right around it, the switch. We're going to work through the LAN configurations beginning with wiping out old configs. We're going to clear the switch out, get it back to its base configuration and then begin by configuring the security, the cosmetics of the switch meaning the name of the switch, the working environment that we're going to be working in. We will get management set up for the switch where we can telnet to it remotely and manage it. We're working on configuring the interfaces. Hard coding speed and duplex and assigning description where we see appropriate. Then finally, we'll verify our configuration using sup-many of the show commands and show CDP to make sure what we're connected to that CISCO discovered protocol and then we'll back up our configurations to a TFTP server.


So, let me go in and slide our window in here. This is our switch that we actually used in the CCENT series and I want to begin by eliminating everything that we did; log-on banners, passwords, everything like that. It's all wiped out when you do one of two things. One, the old way, we can type in write/erase, hit enter, says erase and view, run o file system or remove all configurations, we hit enter and we are good. That will wipe out them NVRAM.


Now, depending on the device that you are on, the newer way, is either erase and you can do a and you can do start up config or some different devices namely routers and some switches will be delete sort of configs, so erase or delete, either one works and does the same thing as the write or erase. It's just-write or erase is considered legacy. Now that kills the NVRAM. There's our concept to review non-volatile RAM. That's the RAM that will remain when the powers goes out. But the configuration is still active on the switch in the RAM. So to truly flush it out, we need to do a reload of the switch. Now be careful. I've done this plenty of times just on instinct. It comes up and says, "System configuration has been modified. Do you want to save?" And you think, "oh yeah", because you always save, right? But if you save, you just undid everything that you just did because this going to write everything from RAM, meaning the stuff that we're trying to erase, back to NVRAM and it's going to boot up with its same old configuration. So I'm going to say, "No, I do not want to save", and then it says, "Proceed with reload?" Sure thing. So this will reload the switch. It's going to the boot process and I'll pause the video as it does that, but once it comes back up, it will have no configuration and should give us that ever so lovely question, "Do you want to enter initial config dialogue?" So let me the pause the video here.


Alright we've made it to the boot process and just to review what the boot process looks like, we rate about there, did the reload and it went through, boot it up. All of these pound symbols action is capping the IOS out of flash into RAM so it can run faster and decompressing it as it does that because it's compressed and flashed, you can see right there. Uncompress and installed, gives some copyright information, etc. Runs through and test all the core components, some cryptography warnings about exporting to countries that don't allow that.


There's our model number of switch. This is our memory installed inside of the switch, it's a RAM. Shows the image that is running, it's a layer 2/3 image all the controllers that are inside of it that actually managed the interfaces. Down below, you can see system's serial number and so on but this is just some of the status messages now that it's up and running, we can hit enter and see, "Do you want to enter the initial config dialogue?". Now that you have graduated to the ICND2 level, we always answer no to that. We went through it in ICND1 just to see what it look like but it just get a few question into that and you realize, that's not where you want to be. You want to be at the command line where we can manually configure things because that's where we can do things much faster and more efficiently.


So, I'm sitting at the switch little right angle bracket lets me know I'm in user mode. Now let us look our objective. We've wiped up our configurations, let me grab my pen here, and we are good to go on that. Now we can do the passwords and banner to lock it down. Now, there's a lot more to that than meets the eye. We have not just password for the privilege mode but passwords for telnet and things like that. So, let's walk through it. First of, to move into the privilege mode, we type in "enable", "tab key" finishes the command. Moving to global configuration mode and set the most important password of all first, the privilege mode password. We can do it one of two ways, we can type in "enable password" and whatever we want our password to be, right there, I could put CISCO as my password. But the problem with the enable password command is that it stores it in the running config in clear text. Most people if not all, use nowadays the enable secret which will hash the password in the running config. It's a pretty sophisticated form of encryption that makes it virtually unbreakable.


So I'm going to choose the enable secret CISCO which is the worst password you could ever use in the real world but in lab environments, it's great because you'll never forget it. So we've now protected our privilege mode. Just to test, I'll type in "disable" and "enable" one more time and now it's prompting me for password which I type in CISCO. Now let's lock down the telnet ports.


We do that by typing in "line vty0 4" where 0 is the first vty port number and 4 is the last. So it's kind of like typing line vty0 through 4. So I'm configuring all of them at the same time. Now remember the vty stands for virtual terminal. And-virtual-hang-on.


Virtual tel-ah so here's your tech fact for the day. Lot of the documentations say its virtual terminal but it's actually not. It's virtual teletype. That was one of the, you know what-hang on, hang on. Okay sorry. I just had to go to my web browser and verify that. It is virtual teletype which is an old system that we had of communicating and now we use telnet to connect to our virtual teletype port. So I'll underline "vty0 4", I'll type in "log in". What that does is require log-ins to those ports.


If I were to negate that, type in "no log in". Oh that is so dangerous because at that point people can telnet into the router and there's no log-in required. It's not saying, no log ins allowed. It's no log in required so they can log in without a password.


So we typed in and log in, you noticed it says "log in will be disabled" until you set a password because you told me the require log-ins but haven't told me what password to use, so I'll type in password off CISCO and hit enter. I've now secured my telnet ports with a password of CISCO and jump type out "line console 0", we're going to lock down the console port. We'll say log in and the password on the console port is also CISCO, and finally "line aux 0". Right, I'm on the switch (laughing). Switches don't have aux ports. A router, routers have the auxiliary ports where you can attach a modem and that's one of the common thing that people do on routers but switches don't have it. So we've got the vty passwords configured, the enabled secret password configured and the console password configured. I would say we're good to go on passwords. Now let's set on the log-in banner. We do that by typing in "banner motd" which is "message of the day" and then we type in a delimiting character. Now that context since its develop isn't to helpful because it's kind of confusing.


Says, c banner text c" where c is delimiting character. That means type in whatever number or symbol you want. I'll use a enter. Soon as I do that it started to log on banner and I can be you know nice and creative. "Do not log on", put my "*" as well. Now I believe I've mentioned this in the part one of the series but if you haven't seen that one, I do want to mention that don't-its, its, let me say this, it's not a good practice to make this log on banner excessively long.


I've seen people that will put the entire disclaimers and the acceptable users policies and everything in here, even ask key art little picture on their of you know, men with guns that has, you know, do not log in, well that's fun. It will slow your router down. Meaning the running config will be larger, it's more to process but more so, when you go to "save your configuration" it's just takes forever. So short and sweet, I'll end with my and now I have a log on banner. With that, I'll exit the router.


It says, "console ports available". I'll hit "enter", says "do not log in". My log on banner successful. I also see my console password is successful because I'm prompted immediately for password. I'm in user mode, privilege mode, password, good. So we've now got the passwords and the log on banner configured. Now let's move on to the cosmetics. We need to configure the name of the switch and our general work environment.


Let's start of with the name of the switch. I'll jump in to global config mode, really simple command, host name, and we can name it whatever we'd like. Let's call it, well this is what I named it before but we'll call it that again, "cv switch", we'll make it unique "2" (cv switch 2). Creativity at its best. So "cvt switch 2" is now the name of the switch. Now what I mean when I say work environment in the second half, it's just the things that makes the switch or router easier to work with. The first of those things is the synchronize logging. Meaning if you're making changes and you know, bump and you round, so on, let's say we exit back to privilege mode and say oh I want to do show-oh I hate that. You get this message right here, right? It says "configure from console by console." It's a status message and you'll get tons of those. Those interfaces go up and go down and all kinds things that happen on the switch. Status messages will abound but the problem they cut what you're typing in half.


You can see S-H right there and O-W ow over there. And I'm typing at the end of this message over here which it will still work if I can keep my wits about me and keep on typing it in but it's just it's difficult. So what I prefer to do is go under the console port and type in the command "logging synchronize", enter. I'll also go under the vty lines because you can actually watch those messages from there so I'll do the same thing over there. Telnet ports will now have synchronized log in. Now watch will happens when I exit back out. I do a "show running" there it goes. We got the message and it repainted what I was typing below it. It's such a simple feature. I don't know why it's not on by default but it's so helpful not to have these messages interrupting you. Good. Now one thing I'll show you for a lab environment that will be very handy is go on to the console port and type in "no exec time out" or you can type in "exec time out 0 0", it does the same thing. It keeps the router from kicking you of after five minutes of vital time by default.


Lot of times we'll be working on our devices. We'll look at the book or we'll look at the website or you know, we're configuring things and getting it set up and we'll get kicked of so and we have to log back in, get back to where we were. So this will keep it from kicking you out. Now I want to emphasize this is in a lab environment. In the real world, this is a huge security vulnerability because if you forget to log out, that means the next person that comes in after you is going to be logged in because it never kicks him out. Maybe just for your own wits, you could type in something like exact time out. We'll say something like 800 where at 800 minute of vital time, it will log you out.


But it-for me, I'd prefer just to keep it there all the time. Now, the last command for the work environment that I like to do on all my devices is type in "no IP domain-look up". From global configuration mode, what that command does is keep you from getting hung up on mistypes. Meaning, I didn't want to demonstrate it because it would hang there for about 60 seconds but when you mistyped something from privilege mode, it will typically sit there and go translating to 255255255255 and just hang there. There is now way to really break out of it except on some of the newer devices, you can use "control+shift+6" to break it but on a lot of them older and modern devices, they you are just stuck there and you have to wait there for 60 seconds.


What it's trying to do when it's translating that is telnet to a device named ASDF or whatever you're mistyped is. Meaning the router thinks or the switch thinks that you're trying to telnet to something name that. If you don't have DNS set up on your switch o router it's just going to send out broadcast to the network saying, "Hello is anyone out there named ASDF? Anyone?


Bueller? Come on. Let me know". And it will just hang there and wait. And meanwhile, you're staring at the prompt just going, "Come on. Come on." So no IP domain look up immediately says I'm not even going to bother looking at that name because it's probably just invalid anyway. So that is setting up the name of the switch in the work environment. Now let's get to the big one. Management. Assigning a switch, an IP address and the default gateway will allow you to manage it remotely. So you don't have to stand on those cold IT rooms and you know, hook into the console port and shiver your way through the configuration. So let me expose a little bit more of this diagram. We have this IP addresses that I plan on assigning at least initially. It gives us enough information to give the switch its IP address 192168.1.10 with a class c on that mask. And its default gateway which will be this router that is connected to the internet. Now on modern CISCO switches, CISCO used to have many different ways to give a switch on IP address. Sometimes in the older ones, it was even from global configuration mode. But on modern CISCO switches, they prefer to give them to VLAN interfaces. Now without getting too deep into the VLAN world which will be a huge part of this series later on. By default, all switches have this interface known as VLAN1, all CISCO switches. And VLAN1 represents the VLAN that all the ports of your switch are assigned to. Now again, we haven't really discussed VLANs too much. Up to this point, it's one of the new concepts we'll talk about in this series. But it's a way of managing-how do I summarize VLAN in a single statement. Let's just say it the way of managing the ports on your switch and what networks they belong to. By default they all belong to VLAN1. So to give this switch a management IP address, we need to move into the global configuration mode. Get under the interface VLAN1 and give it the IP address. 192168.1.10 which is the IP we just saw in the diagram. And it's going to ask us for the subnet mask someday. CISCO will allow us to use the sider notation or the slash notation but for now we have type it in decimal. So that is the IP address that assigned but be careful. Because the VLAN1 interface is always administratively down by default. So what we have to do to bring it up? No shut down. It's been so many times I could just relay one experience where I configured devices and shipped them to clients meaning the you know for remote installations and stuffs like that and I kind of preconfigured the network and I've done you know config on it in a hurry and just shipped and forgot to do a "no shut down". And there's nothing more painful than thankfully with this client it was just a two-hour drive but there's nothing more painful than jumping on a plane playing planning a two week trip to find out you just have to type in "no shut down". So we've now got the management interface brought up and let me show you the first shortcut of the series. You know that show command only work from privilege mode right? I did this command right here with show IP interface brief to verify all the interfaces on my switch. Well, you can actually on modern CISCO switches and routers implement the new "do" command. I can type in "do" from any mode that I'm in, followed by a show command. Show IP interface brief. And it will execute that shield command from whatever mode I'm in. That's awesome. So I don't have to always exit back out. And I can verify that my VLAN1 interface is up.


Line protocol is up. That means we're communicating and this switch should now be able to telneted too since designed it with VTY password and an enable secret password. One more piece of that puzzle and that is the default gateway. That is a global configuration mode command. I type in "IP default-gateway" and the default gateway I plan on using. That would be my IP router up here. 192168.1.1, enter. We now, with that in place, can manage the switch from the local LAN just by giving out the IP address and remotely by giving in the default gateway. Without a default gateway, the switch has no way of getting of its local network. So that point the management of our switch is good to go.


And the default gateway is set. So we can move down the interfaces themselves. The speed, duplex and descriptions. Now with the interfaces, all of them are set into show run; by default it will probably hide it. All of them are set to auto negotiate the speed and duplex of the interface. Now my quick witty saying on that is the auto negotiation-we'll see I've ruined my own saying. With auto negotiation, you ought to not use it. Auto is typically bad in most thing CISCO, meaning that yes it will work most of the time but it leaves some room for doubt. And with the speed in duplex, if it auto detects it incorrectly, you're going to get a bunch of errors on the port.


Sometimes the port will just shut down. Other times it will just operate very slowly because it has a duplex mismatch between those sites. Now what I'm not saying, I'm not saying to go through in your entire organization of 1500 computers and hardcode every single switch ports to exactly the speed and duplex that is meant to be. The reason I'm not saying that is the auto detects mechanism has just a guestimate. This is from my experience about a 95% successful detection rate. Now first of, this isn't a CISCO problem.


It is not something that CISCO just implemented poorly. This happens across the board on any vendor switch just because the network cursor so diverse out there. Ninety five percent is pretty good. Meaning that 95% out of you hundred computers will typically work okay with auto detection but five of them will not. Meaning you're going to get slow links and so on. So what my rule of thumb is maybe skip over the clients, the computers, and just hardcode the key ports in your network. Meaning ports to routers.


Those are key ports. Ports to printers, ports to servers, those are all considered key ports in my mind and if we have a mismatch on those it will affect far more than just one user whose not able to work efficiently. So those of the ones you want to go underneath. In this case I'll just demonstrate one of those interfaces.


I'll go into interface pass Ethernet 0/1 which will eventually connect to this router. We have not actually physically connected it yet. And I'll type in IP@-oh what I'm I doing. Duplex followed by full, by default its auto, and in this case speed 100.


100 megabits per second. And that is hard coding the speed in duplex. Now this interface is going to connect to our internet facing router so I'd like to attach description. Again descriptions I use sparingly, I do not do that on every port, just the key ports so when I'm looking in my switch, I can get a quick feel of what's connected. Let me do this first and I'll give you a quick view of that. I'm going to type in that description, "INTERNET ROUTER CONNECTION".


Usually when I type in description, I usually type them in all uppercase and I do that for most things with the name so I can see it very quickly in running config and I know that something that I typed in. It's not a command. So that sets the description and that-let me get back, I'll show you a bonus command, not really documented very well in CISCO at all. But it is show interface description. That's a great way where you can scroll through the interfaces on your switch and see it quick view on what the description are and see those key ports without having to do a full running configuration done.


Let me just give you a good idea of what this looks like. I have a switch that runs my home. And I'm going to telnet right here. I actually have no log in on that required because it's protected from anyone outside of my home by my firewall. Now just to show interface description on there and you can see that I have all of these different interfaces.


I have you know my wife's IP phone, yes, I have IP phones in my home. I confess I am a true geek. We have the wireless router; all of that. So this is the quick way that I can see I even have a Cat 5 port in the kitchen. But I have quick view of all the interfaces and what they connect you. So if I'm looking for an interface, I can just do a quick show description and see exactly where those connect to. So that's a handy command. So that is assigning the speed duplex and descriptions of our interfaces. Finally, let's verify and back up our configuration. The first thing I'm going to do is use the CISCO discovery protocol to verify my network connections. I'm showing on my diagram that I have two routers plug in to the switch and I did connect one of this up to the, one of the fast Ethernet interfaces on the switch between the recordings of the one that we hard coded the speed in duplex on. So we do have these connections but the CISCO discovered protocol will help me map them out and see what ports are connected to what. So what I can do is jump into my switch and do a "show cdp neighbors". Now I'm verifying that I have-it looks like the same router connected to two interfaces. But when you really look at it, you see those are two different platforms. It is just two different platforms with the same name, same host name typed in. So one of the first things as we get in to our router configurations will be to clear the router configs. Now I can look right here and this is key information because I see the local interface that is plugged in to which is the interface on the switch. So I can look and see one router, choose connected the fast internet 0/1 that's the 26-11 router. I can tell you that's the sky right here. So this is, if I was diagramming it I say FA 0/1 and label that port. The other one I believe fast Ethernet 0/4.


So I can label that port FA0/4. Now make this diagram pretty as we go through in add the pieces one by one and I'm also able to see the remote port ID. Ethernet at 0/0 and fast internet 0/0 appeared. I got Ethernet 0/0 which is a 10 mega bit per second port because it's just plain Ethernet. Fast Ethernet FA0/0 is my hundred megabit per second port connection. So now I'm able to label those key ports on my network diagram and even put description on them eventually as we go through that configuration.


Now remember we can also type in shows CDP neighbor detail and hit enter and see all the information about the switches. I can see what remote IP address it's configured with. I can see the platform that it's configures as. We saw that in the brief outlet.


I can the see the IOS versions that running on there. This one is running version 12.4 released 4 xc and I can get-a lot of good information is displayed via CDP. Now we can also verify our configuration on the switch by using the show interfaces command. To show interfaces, we'll actually scroll through one by one starting with VLAN, every single interface that you have and all the stats about that interface. Let's scroll down even more. There's fast Ethernet 0/1. That's our internet router connection. I can see that that one has received 70 packets.


Not too much going on there in the last five minutes. I can see the, the duplex. You can see its such full duplex 10 megabit per second because that is an Ethernet connection. Even though the media, the cable can support 10/100, the router itself cannot.


I can also do a show Mac address table. And we'll see if any of that has been filled in. The static Mac addresses belong to the switch itself. You can see the port that is assigned to the CPU. And if I scroll down. There's my two Mac addresses of my routers that I've learn. Fast Ethernet 0/1 and 0/4. I guarantee you when we go on the routers in the upcoming videos, we'll be able to verify that those are indeed the Mac address is on there.


Last but not the least, I would like to back up our configuration. I know I mentioned TFTP on there and that is one way to back up the configuration but until we get the full network set up, I'm not going to do a TFTP back up because what I plan on doing is setting up a centralized TFTP server and having everything copied it's backed up config to that one server. For now, I'll show you the quick and dirty. That is actually my preferred way of backing up the configuration. First of, you want to save it.


The official CCNA approved method is copy, running config, start up config, and enter. When asked for a file name, you just hit enter because start up config is the default. Like I said CCNA approved way. Real world, that's what you do. Right, which is actually short for right memory is a quicken and fast way to save your configuration from run to start or from RAM to NV RAM.


Now to back up your configuration, the quick and dirty way is to do a show run. Scroll to the very bottom of that configuration. Shoot all the way back up to the top. Right there. You can either choose to start from here or from the first explanation point and highlight everything. I'll do it all to C which in Tera Term is copy. Don't right click on Tera Term. That will copy and paste everything.


Meanwhile, while that action is happening. I'll open the ultra-sophisticated note pad. Come over here. Hide all that gibberish going on and paste right there. That is a complete back up of the configuration. Oh looks like I've got some VLANS in there. I still need to delete from the old config. I'll talk more about VLANS as we get deeper into the concepts. But that is a complete back up of all the configuration that I put inside of this switch so far. There's my VLAN interface, my default gateway. And I say this is my complete back up in the sense that if I wanted to restore these config, I would just start from the first exclamation point. Highlight it down to the very end, edit copy. Now I want you to imagine with me that this switch is a brand new switch, meaning it doesn't have config. I know it does but imagine. I'll just come over here and go to edit, paste. What it's doing is pasting in the entire configuration that I just backed up. If this were a brand new switch, meaning it had no configuration on it. Right there would be the masterful way of reconfiguring it from scratch on the fly. Just like that. No TFTP server needed. No setting up IP addresses manually. That's in my opinion is one of the best ways to do a back up and restore your configuration.


I promised the fly by didn't I? (laughing) Whew! I can breath now (sighing in relief). That was the configuration, foundation configuration of the switch in the small office network. That was all the concepts that we talked about in the CCENT videos series with the exception of one and that is port security. I plan on adding that later on. We're-we have locking it down to a specific Mac address and only that Mac address can use that port. I don't want to do that yet because that will really throw us of when we start connecting devices. So what we did is we walked through a review of a lot of the LAN concepts as we went through that configuration and did the complete configuration of a small office LAN network. I hope that this has been informative for you and I'd like to thank you for viewing.

Review: Rebuilding the Small Office Network, Part 2

Review: Rebuilding the Small Office Network, Part 3

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.

comments powered by Disqus
16 hrs 32 videos


Training 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.

Offline Training
Our iOS and Android mobile apps offer the ability to download videos and train anytime, anywhere offline.

Accountability Coaching
Develop and maintain a study plan with one-to-one assistance from coaches.

Supplemental Files
Files/materials that supplement the video training.

Speed Control
Play videos at a faster or slower pace.

Included in this course
Pick up where you left off watching a video.

Included in this course
Jot down information to refer back to at a later time.

Closed Captions
Follow what the trainers are saying with ease.
Jeremy Cioara
Nugget trainer since 2003