WEBVTT

0:00:08.260000 --> 0:00:11.600000
 So now we're going to go into the last
 section of today's presentation.

0:00:11.600000 --> 0:00:15.560000
 You decide that you want to design
 and create your own labs.

0:00:15.560000 --> 0:00:18.900000
 What I mean by that is you're using
 somebody else's topology like INE's

0:00:18.900000 --> 0:00:22.720000
 or somebody else, but you're going
 to create your own topologies, your

0:00:22.720000 --> 0:00:25.760000
 own protocols, and you're going
 to play with their equipment.

0:00:25.760000 --> 0:00:30.380000
 So what's the best way to do that?


0:00:30.380000 --> 0:00:33.080000
 Somebody asked me earlier, I don't remember
 who it was, if I could just

0:00:33.080000 --> 0:00:37.540000
 real quickly do a demonstration on
 how to get into INE's racks and how

0:00:37.540000 --> 0:00:38.880000
 to rent time and stuff.

0:00:38.880000 --> 0:00:39.940000
 I'll show you how to do that.

0:00:39.940000 --> 0:00:42.680000
 So for those of you who are not familiar
 with that, we will go into that

0:00:42.680000 --> 0:00:45.660000
 as soon as I'm done with
 this session right here.

0:00:45.660000 --> 0:00:50.880000
 Okay, so I talked about the pros and
 cons previously of using a workbook.

0:00:50.880000 --> 0:00:54.460000
 Were the pros and cons of not using
 a workbook, doing everything from

0:00:54.460000 --> 0:01:00.300000
 your own brain? Well, you can custom tailor
 your lab based on your available

0:01:00.300000 --> 0:01:03.440000
 resources. That's nice.

0:01:03.440000 --> 0:01:07.880000
 You can custom tailor your lab
 based on your own interests.

0:01:07.880000 --> 0:01:10.580000
 You're not dependent on the interests
 of the lab developer.

0:01:10.580000 --> 0:01:14.280000
 You can do whatever features and protocols,
 whatever iOS commands you

0:01:14.280000 --> 0:01:20.300000
 want to do. You have now opportunity
 to go into much greater depth on

0:01:20.300000 --> 0:01:23.800000
 a topic than is typically found
 in a pre-designed lab guide.

0:01:23.800000 --> 0:01:29.440000
 That's true. This is probably
 the single biggest advantage.

0:01:29.440000 --> 0:01:35.260000
 Trying something and failing is
 a great learning opportunity.

0:01:35.260000 --> 0:01:40.800000
 For example, I have probably personally
 learned the most when I sat down

0:01:40.800000 --> 0:01:45.100000
 with a piece of paper and I said,
 okay, here's what I want to do.

0:01:45.100000 --> 0:01:50.580000
 I've got two routers with
 two paths to each other.

0:01:50.580000 --> 0:01:54.480000
 I want to try to influence
 load balancing.

0:01:54.480000 --> 0:02:01.080000
 Maybe influence my EIJRP load balancing
 based off of the load variable.

0:02:01.080000 --> 0:02:02.560000
 I don't care about bandwidth
 and delay.

0:02:02.560000 --> 0:02:06.000000
 I want to see if I can influence the
 load on a particular link to get

0:02:06.000000 --> 0:02:09.060000
 EIJRP to flip over to a
 link that has less load.

0:02:09.060000 --> 0:02:12.180000
 Let's just say this is actually
 something I tried recently.

0:02:12.180000 --> 0:02:15.060000
 I drew it all out.

0:02:15.060000 --> 0:02:17.500000
 I pre-configured it with
 IP addresses and stuff.

0:02:17.500000 --> 0:02:19.680000
 I discovered that I couldn't.

0:02:19.680000 --> 0:02:22.680000
 There was no way for me
 to get that to work.

0:02:22.680000 --> 0:02:25.140000
 That's not a failure in my mind.

0:02:25.140000 --> 0:02:27.320000
 Even though I couldn't get it to work,
 that was an incredible learning

0:02:27.320000 --> 0:02:33.160000
 opportunity. I learned how to get EIJRP
 to factor load into the calculation.

0:02:33.160000 --> 0:02:36.440000
 I learned how to increase
 the load on interface.

0:02:36.440000 --> 0:02:37.480000
 I learned all kinds of stuff.

0:02:37.480000 --> 0:02:42.220000
 Even though I wasn't able to meet my
 objective by failing, I learned a

0:02:42.220000 --> 0:02:45.120000
 whole bunch of stuff
 I didn't know before.

0:02:45.120000 --> 0:02:48.480000
 You're not going to get that experience
 when you're following a lab guide.

0:02:48.480000 --> 0:02:52.820000
 A lab guide is typically built so that
 if you follow the steps, you will

0:02:52.820000 --> 0:02:56.700000
 succeed. If you follow the steps, you
 will succeed in configuring or doing

0:02:56.700000 --> 0:02:59.220000
 whatever the lab developer
 wanted you to do.

0:02:59.220000 --> 0:03:02.540000
 They're not typically going to design something
 to a lab guide to intentionally

0:03:02.540000 --> 0:03:07.420000
 have you fail. Sometimes,
 but usually not.

0:03:07.420000 --> 0:03:12.240000
 In my personal opinion, understanding
 why something doesn't work can be

0:03:12.240000 --> 0:03:16.360000
 just as valuable as understanding
 why it does work.

0:03:16.360000 --> 0:03:21.020000
 I tell people all the time, look, when
 you're first learning about EIJRP,

0:03:21.020000 --> 0:03:23.320000
 what are some of the first things
 they want you to know?

0:03:23.320000 --> 0:03:25.160000
 EIJRP neighbor relationships.

0:03:25.160000 --> 0:03:27.420000
 What's required to make the
 neighbor relationship?

0:03:27.420000 --> 0:03:29.660000
 The K values have to be the same.

0:03:29.660000 --> 0:03:31.700000
 The autonomous system values
 have to be the same.

0:03:31.700000 --> 0:03:34.100000
 They give you like four
 or five things.

0:03:34.100000 --> 0:03:37.900000
 But they don't really tell you about,
 well, what are you going to see

0:03:37.900000 --> 0:03:40.900000
 if some of those things
 don't match up?

0:03:40.900000 --> 0:03:42.760000
 That's very valuable information.

0:03:42.760000 --> 0:03:46.460000
 I love going into a lab and saying, okay,
 what if my K values don't match?

0:03:46.460000 --> 0:03:49.860000
 What if my autonomous system
 number doesn't match?

0:03:49.860000 --> 0:03:51.500000
 Can I see something in a debug?

0:03:51.500000 --> 0:03:55.320000
 Can I see something in a syslog
 that will clue me off to that?

0:03:55.320000 --> 0:03:57.540000
 Because that's going to help you in
 the long run with troubleshooting

0:03:57.540000 --> 0:04:01.220000
 stuff. Just getting it to work and getting
 it to work and getting it to

0:04:01.220000 --> 0:04:03.480000
 work, that's not really going to help
 you if you ever need to troubleshoot

0:04:03.480000 --> 0:04:11.520000
 this stuff. Now, where are some
 cons to designing your own labs?

0:04:11.520000 --> 0:04:14.660000
 Well, you might end up spending valuable
 time on troubleshooting problems.

0:04:14.660000 --> 0:04:17.900000
 Now, there's a silver lining to this
 cloud, but some people could say,

0:04:17.900000 --> 0:04:21.920000
 hey, look, I rented three
 hours on this rack.

0:04:21.920000 --> 0:04:25.580000
 And before I even press the start button,
 I came up with this nice lab

0:04:25.580000 --> 0:04:30.100000
 I want to do based on private VLANs
 here, which go into DHCP snooping

0:04:30.100000 --> 0:04:32.720000
 here, which feed into EIGRP here.

0:04:32.720000 --> 0:04:36.560000
 But I only got into the private VLANs
 section, the very first part of

0:04:36.560000 --> 0:04:39.900000
 my lab. I start getting air messages
 and it wasn't working right.

0:04:39.900000 --> 0:04:44.260000
 And I consume my entire three hours
 just troubleshooting private VLANs.

0:04:44.260000 --> 0:04:47.940000
 Well, you can look at that
 one of two ways, right?

0:04:47.940000 --> 0:04:51.900000
 That could be a con that you weren't
 able to complete within your allotted

0:04:51.900000 --> 0:04:54.680000
 time what you wanted to complete.

0:04:54.680000 --> 0:04:58.600000
 But the pro is, you'll learn to heck
 up a lot about private VLANs during

0:04:58.600000 --> 0:05:00.280000
 all that troubleshooting, right?

0:05:00.280000 --> 0:05:03.400000
 So, there is a silver
 lining to that.

0:05:03.400000 --> 0:05:09.820000
 You may miss critical features
 and protocols, right?

0:05:09.820000 --> 0:05:15.680000
 You are designing your labs based on what
 you think is in the certification

0:05:15.680000 --> 0:05:19.600000
 exam. And you did that probably
 based on the blueprint.

0:05:19.600000 --> 0:05:23.100000
 You looked at the route or the switch
 or the CCIE blueprint, and you're

0:05:23.100000 --> 0:05:24.940000
 doing your labs based on that.

0:05:24.940000 --> 0:05:27.940000
 But these blueprints don't always
 give you the full picture.

0:05:27.940000 --> 0:05:30.900000
 A lot of times there's features and
 protocols that these exams expect

0:05:30.900000 --> 0:05:33.540000
 you to know that they don't
 put into the blueprint.

0:05:33.540000 --> 0:05:36.700000
 Personally, I think that's kind of nasty
 that they do that, but that does

0:05:36.700000 --> 0:05:41.000000
 happen. And so if you're just making
 your labs up yourself, how are you

0:05:41.000000 --> 0:05:42.860000
 going to know what you missed?

0:05:42.860000 --> 0:05:45.640000
 That might be a problem.

0:05:45.640000 --> 0:05:50.240000
 You might accidentally design a lab
 that's unsupported by your variable

0:05:50.240000 --> 0:05:52.380000
 hardware and feature set.

0:05:52.380000 --> 0:05:53.400000
 It happens, right?

0:05:53.400000 --> 0:05:56.120000
 I mean, when you're designing, you
 know, when you're going back to the

0:05:56.120000 --> 0:05:59.600000
 building the home lab, chances are you're
 not going to be able to think

0:05:59.600000 --> 0:06:05.100000
 of 100% of everything you're ever going
 to want to do on your home lab.

0:06:05.100000 --> 0:06:07.760000
 There's going to be something
 you're going to miss.

0:06:07.760000 --> 0:06:09.060000
 So same thing here.

0:06:09.060000 --> 0:06:13.760000
 If you're using a remote rack, you know
 in advance what the topology of

0:06:13.760000 --> 0:06:15.540000
 that remote rack looks like.

0:06:15.540000 --> 0:06:19.100000
 You know in advance what hardware
 and software is in there.

0:06:19.100000 --> 0:06:23.220000
 So maybe you think to yourself, okay,
 based on this topology right here,

0:06:23.220000 --> 0:06:25.720000
 I want to create IPv6 tunnels.

0:06:25.720000 --> 0:06:29.300000
 I want to do some isotap between
 these two routers right here.

0:06:29.300000 --> 0:06:32.560000
 And you spend a bunch of time writing
 up your lab, drawing it up, and

0:06:32.560000 --> 0:06:36.180000
 then you press the start button only
 to discover, oh, isotap's not an

0:06:36.180000 --> 0:06:39.480000
 option. I'm doing tunnel mode and I
 don't see isotap in there because

0:06:39.480000 --> 0:06:42.920000
 this feature set on this switch
 or router doesn't support it.

0:06:42.920000 --> 0:06:46.460000
 That kind of stinks because now the
 time is counting down and the lab

0:06:46.460000 --> 0:06:48.800000
 you developed, you can't even do.

0:06:48.800000 --> 0:06:53.420000
 So you'll run into that
 sometimes as well.

0:06:53.420000 --> 0:06:56.640000
 And you might leave yourself
 down a rat hole.

0:06:56.640000 --> 0:07:02.420000
 And what I mean by this is you might
 start out by developing a lab on,

0:07:02.420000 --> 0:07:07.360000
 I don't know, DHCP snooping
 or something like that.

0:07:07.360000 --> 0:07:11.000000
 You've got all built out, you drew your
 cloud, your IP addresses and everything,

0:07:11.000000 --> 0:07:14.960000
 press the start button on your own rack,
 and now your two hours you reserve

0:07:14.960000 --> 0:07:16.860000
 starts counting down.

0:07:16.860000 --> 0:07:20.600000
 And you get a little into it and you
 say, oh, here's a cool keyword.

0:07:20.600000 --> 0:07:21.400000
 I've never seen that before.

0:07:21.400000 --> 0:07:22.920000
 I wonder what that does.

0:07:22.920000 --> 0:07:24.780000
 Oh, well, let me try this.

0:07:24.780000 --> 0:07:25.360000
 Let me try this.

0:07:25.360000 --> 0:07:28.060000
 And all of a sudden two hours has gone
 by and you've just been stuck on

0:07:28.060000 --> 0:07:29.140000
 this one command.

0:07:29.140000 --> 0:07:32.500000
 Trying out various keywords, doing a
 little bit of research right here,

0:07:32.500000 --> 0:07:36.140000
 and your time is up and you never even
 got 20% into the lab you want to

0:07:36.140000 --> 0:07:39.340000
 get into because you got
 stuck in this rat hole.

0:07:39.340000 --> 0:07:41.760000
 Once again, pros and cons, right?

0:07:41.760000 --> 0:07:44.140000
 The pro of that is, well, you
 learned something still.

0:07:44.140000 --> 0:07:45.420000
 It was a learning experience.

0:07:45.420000 --> 0:07:49.040000
 The con is you just spent money on
 two hours and you did not meet your

0:07:49.040000 --> 0:07:52.860000
 objective of the lab that you developed
 that you wanted to do.

0:07:52.860000 --> 0:07:56.660000
 So those are some cons.

0:07:56.660000 --> 0:08:01.060000
 Okay, so where are some approaches
 to designing your own labs?

0:08:01.060000 --> 0:08:04.380000
 Two approaches. Approach
 number one.

0:08:04.380000 --> 0:08:10.060000
 You can find an available topology first
 and design your labs around your

0:08:10.060000 --> 0:08:14.240000
 resources. So, for example, you say,
 okay, I've looked at six different

0:08:14.240000 --> 0:08:20.640000
 vendors who offer me remote racks and
 I'm going to go with INE, of course.

0:08:20.640000 --> 0:08:22.800000
 So I'm looking at this
 topology diagram here.

0:08:22.800000 --> 0:08:26.380000
 This is this, INE has given me three
 switches and four routers, a couple

0:08:26.380000 --> 0:08:27.180000
 of backbone routers.

0:08:27.180000 --> 0:08:30.100000
 I can't really touch, so
 I can't factor those in.

0:08:30.100000 --> 0:08:32.960000
 So really I've got four routers and
 three switches available to me.

0:08:32.960000 --> 0:08:36.760000
 Okay, based on that, I'm going
 to build my lab on that.

0:08:36.760000 --> 0:08:38.980000
 I'm going to say, okay, well, with that,
 I could have a couple of autonomous

0:08:38.980000 --> 0:08:41.380000
 systems. I could do
 some filtering here.

0:08:41.380000 --> 0:08:42.160000
 Blah, blah, blah.

0:08:42.160000 --> 0:08:44.280000
 So that's one approach.

0:08:44.280000 --> 0:08:50.860000
 Approach number two is start by building
 your lab on paper saying yourself,

0:08:50.860000 --> 0:08:52.080000
 okay, here's what I want to do.

0:08:52.080000 --> 0:08:56.540000
 I want to do eBGP between three
 different autonomous systems.

0:08:56.540000 --> 0:09:00.800000
 Within this autonomous system, I want
 to have IBGP with five routers so

0:09:00.800000 --> 0:09:15.440000
 I can practice route reflection and local
 preference and blah, blah, blah.

0:09:15.440000 --> 0:09:17.420000
 That's the second approach.

0:09:17.420000 --> 0:09:21.600000
 Personally, I find approach number
 one to be more effective.

0:09:21.600000 --> 0:09:26.820000
 I think it's better to know what your
 constraints are first, right?

0:09:26.820000 --> 0:09:29.960000
 Pick some remote equipment, some remote
 rack, whether it be the Cisco

0:09:29.960000 --> 0:09:35.620000
 learning labs, whether it be INE, whatever,
 and then build your topology

0:09:35.620000 --> 0:09:39.240000
 based around the hardware and the connections
 that you have available

0:09:39.240000 --> 0:09:43.460000
 to you. As it says, you're going to
 find it very difficult to find racks

0:09:43.460000 --> 0:09:49.000000
 that meet a pre-designed topology.


0:09:49.000000 --> 0:09:51.380000
 All right, finding the equipment.

0:09:51.380000 --> 0:09:53.060000
 So you say, okay, well,
 how do I choose?

0:09:53.060000 --> 0:09:56.120000
 There's the Cisco learning labs, there's
 INE, there's this, that, and

0:09:56.120000 --> 0:09:56.600000
 the other thing.

0:09:56.600000 --> 0:09:58.660000
 There's lots of companies
 out there.

0:09:58.660000 --> 0:10:01.140000
 They're providing access
 to their equipment.

0:10:01.140000 --> 0:10:03.980000
 How do I select one?

0:10:03.980000 --> 0:10:06.580000
 Okay, so here's some key
 things to look for.

0:10:06.580000 --> 0:10:10.480000
 Price, clearly, right?

0:10:10.480000 --> 0:10:14.560000
 That's a fact. I don't think I have
 to talk too much about that.

0:10:14.560000 --> 0:10:18.980000
 The availability of both routers and
 switches in a single topology.

0:10:18.980000 --> 0:10:22.940000
 So you're ideally going to want to look
 for topology that has a combination

0:10:22.940000 --> 0:10:30.280000
 of routers and switches in it, which
 will give you more flexibility.

0:10:30.280000 --> 0:10:33.280000
 If some vendor out there says, here's
 our switching lab, and they got

0:10:33.280000 --> 0:10:36.820000
 five switches. Here's our routing
 lab with five routers.

0:10:36.820000 --> 0:10:39.940000
 Well, now you're kind of limited in what
 you can do if you can only choose

0:10:39.940000 --> 0:10:41.820000
 one or the other.

0:10:41.820000 --> 0:10:46.940000
 Is it real equipment or
 emulated equipment?

0:10:46.940000 --> 0:10:48.880000
 This is a big one right here.

0:10:48.880000 --> 0:10:54.320000
 Now, for routing labs, emulated
 equipment typically is fine.

0:10:54.320000 --> 0:10:57.900000
 For example, if you're using GNS or
 the Cisco learning labs or something

0:10:57.900000 --> 0:11:02.180000
 which use IOU, you can pretty much do
 everything you want to do with routing

0:11:02.180000 --> 0:11:06.080000
 with that. Switching, though, we've
 already talked about that.

0:11:06.080000 --> 0:11:09.840000
 When it comes to the more advanced switching
 topics and features, you're

0:11:09.840000 --> 0:11:12.520000
 going to need access
 to real equipment.

0:11:12.520000 --> 0:11:15.540000
 Emulated or assimilated switches
 just not going to cut it.

0:11:15.540000 --> 0:11:19.520000
 You're going to find yourself getting very
 frustrated over a lack of commands,

0:11:19.520000 --> 0:11:23.300000
 a lack of features and protocols you'd
 have available in a real physical

0:11:23.300000 --> 0:11:25.680000
 switch. So you should know that.

0:11:25.680000 --> 0:11:28.600000
 This venue right here, this guy wants
 to rent me his stuff for a dollar

0:11:28.600000 --> 0:11:31.100000
 an hour. Wow, that
 sounds really good.

0:11:31.100000 --> 0:11:32.000000
 What am I doing?

0:11:32.000000 --> 0:11:35.560000
 I'm actually getting into a server that's
 running VMware and I'm getting

0:11:35.560000 --> 0:11:38.180000
 access to some virtual
 routers and switches.

0:11:38.180000 --> 0:11:42.920000
 It's cheap, but I'm going to be kind
 of limited in what I can do there.

0:11:42.920000 --> 0:11:48.180000
 You want a selected topology
 that's flexible.

0:11:48.180000 --> 0:11:50.440000
 What do I mean by that?

0:11:50.440000 --> 0:11:54.020000
 Well, you want to find a topology
 that has a lot of link redundancy.

0:11:54.020000 --> 0:11:56.860000
 A topology that's got
 between your switches.

0:11:56.860000 --> 0:11:59.660000
 If you've got a topology of switches and
 there's just a single link between

0:11:59.660000 --> 0:12:02.740000
 them, how are you going to
 do ether channel with that?

0:12:02.740000 --> 0:12:05.440000
 How are you going to do topologies where
 a link fails and it has to back

0:12:05.440000 --> 0:12:06.580000
 up to another link?

0:12:06.580000 --> 0:12:08.320000
 You're not going to
 be able to do that.

0:12:08.320000 --> 0:12:10.200000
 What about router topologies?

0:12:10.200000 --> 0:12:12.740000
 If you've got a topology where a router
 just has a single serial interface

0:12:12.740000 --> 0:12:16.560000
 to another router and that's it, once
 again, you're kind of limited.

0:12:16.560000 --> 0:12:20.100000
 Ideally, you want to find a topology that's
 got multiple links and multiple

0:12:20.100000 --> 0:12:24.880000
 paths through the topologies so you
 can have all sorts of designs that

0:12:24.880000 --> 0:12:26.640000
 you can come up with.

0:12:26.640000 --> 0:12:32.040000
 Scheduling availability.

0:12:32.040000 --> 0:12:34.080000
 Another thing here.

0:12:34.080000 --> 0:12:40.320000
 Most remote systems have some sort of
 scheduling tool and most of them,

0:12:40.320000 --> 0:12:44.420000
 certainly, INE's will let you see in
 advance what the availability is.

0:12:44.420000 --> 0:12:46.940000
 This is also something
 to look for.

0:12:46.940000 --> 0:12:50.380000
 Check it out. If you go on to some vendor's
 website and you say, oh, that's

0:12:50.380000 --> 0:12:55.980000
 an awesome topology, pretty decent price,
 but you look at a schedule and

0:12:55.980000 --> 0:12:58.820000
 most of the time it's in use.

0:12:58.820000 --> 0:13:01.500000
 There's just like little tiny snippets
 of time here and there where it's

0:13:01.500000 --> 0:13:04.820000
 free. You probably don't want to pop
 your money down with that vendor

0:13:04.820000 --> 0:13:06.980000
 because you're going to be frustrated
 because you're not going to have

0:13:06.980000 --> 0:13:09.740000
 access to that rack
 when you want it.

0:13:09.740000 --> 0:13:14.140000
 So that's something to look at.

0:13:14.140000 --> 0:13:18.160000
 Does it require you to download
 any special front-end software?

0:13:18.160000 --> 0:13:21.560000
 Now, INE does not require this, but
 some other vendors require you to

0:13:21.560000 --> 0:13:25.940000
 download some Java software or some
 other stuff in advance and you're

0:13:25.940000 --> 0:13:32.300000
 using their special GUI, their special
 application to get into the routers

0:13:32.300000 --> 0:13:34.860000
 to type in the terminals
 and stuff?

0:13:34.860000 --> 0:13:36.680000
 Are you okay with that?

0:13:36.680000 --> 0:13:38.340000
 How do you know you're not
 downloading a virus?

0:13:38.340000 --> 0:13:40.460000
 How do you know it's not going to
 mess up your laptop or something?

0:13:40.460000 --> 0:13:43.000000
 So that's also something
 to consider.

0:13:43.000000 --> 0:13:47.920000
 Are there preloaded configurations
 available?

0:13:47.920000 --> 0:13:52.360000
 Now, if you're going to be developing
 your own labs from your head, a

0:13:52.360000 --> 0:13:56.920000
 preload configuration is probably not
 going to really do much for you.

0:13:56.920000 --> 0:13:59.500000
 So that's not really a benefit.

0:13:59.500000 --> 0:14:06.880000
 One other thing on here that is not really
 listed is that you do not want

0:14:06.880000 --> 0:14:10.520000
 to spend any money on a
 vendor's remote rack.

0:14:10.520000 --> 0:14:14.780000
 Until you can see the topology
 diagram first.

0:14:14.780000 --> 0:14:19.060000
 It makes kind of a common sense,
 but it's pretty important.

0:14:19.060000 --> 0:14:22.320000
 You've got to know what you're getting
 into first before you spend money

0:14:22.320000 --> 0:14:25.920000
 with them. Make sure you can see, okay,
 if I get into this rack, how many

0:14:25.920000 --> 0:14:27.180000
 devices are in there?

0:14:27.180000 --> 0:14:29.160000
 How many connections do they have?


0:14:29.160000 --> 0:14:32.440000
 Is it pretty clear to me in their instructions
 how to move around between

0:14:32.440000 --> 0:14:34.360000
 the different devices?

0:14:34.360000 --> 0:14:38.860000
 So you should know all
 that stuff up front.

0:14:38.860000 --> 0:14:42.820000
 So what I call creative labs, these are
 labs that you're designing yourself

0:14:42.820000 --> 0:14:46.640000
 from your head. I typically recommend
 that they're used as a supplement

0:14:46.640000 --> 0:14:50.040000
 alongside reading or watching
 videos or something.

0:14:50.040000 --> 0:14:56.900000
 So the way I typically do this is I might
 be watching a video, for example,

0:14:56.900000 --> 0:15:01.740000
 and some instructors teaching
 me how to do MPLS VPNs.

0:15:01.740000 --> 0:15:04.260000
 And he or she is going
 through the steps.

0:15:04.260000 --> 0:15:06.180000
 And I start and I pause
 it for a second.

0:15:06.180000 --> 0:15:09.300000
 I say, oh, okay, well, based on what
 I've just learned here, I think I'd

0:15:09.300000 --> 0:15:10.360000
 like to try that.

0:15:10.360000 --> 0:15:13.780000
 So I pause the video and I write on
 my piece of paper, okay, based on

0:15:13.780000 --> 0:15:17.400000
 what I've learned, I think if I have
 four routers here and I have the

0:15:17.400000 --> 0:15:20.100000
 configured with this and I put these
 IP addresses on and then I resume

0:15:20.100000 --> 0:15:24.580000
 the video. So it's used as a supplement
 or if I'm reading a book and I'm

0:15:24.580000 --> 0:15:29.920000
 reading about, okay, here's the requirements
 for an OSPF adjacency.

0:15:29.920000 --> 0:15:34.260000
 And it says, here's the various stages
 of OSPF, and knit, two-way, X-Star

0:15:34.260000 --> 0:15:37.280000
 exchange, loading, full and I
 say, oh, I'd like to see that.

0:15:37.280000 --> 0:15:40.120000
 I'd like to try to build a relationship
 and do a debug and see if I can

0:15:40.120000 --> 0:15:41.620000
 see what's happening right there.

0:15:41.620000 --> 0:15:43.660000
 I'll stop reading and
 I'll design a lab.

0:15:43.660000 --> 0:15:48.280000
 I'll say, okay, let me put these two
 routers together and this is the

0:15:48.280000 --> 0:15:49.740000
 IP addressing scheme
 I'm going to use.

0:15:49.740000 --> 0:15:52.860000
 And so I just want to do a debug
 to see OSPF adjacency.

0:15:52.860000 --> 0:15:57.580000
 So as I'm getting ideas, as I'm watching
 videos or reading things, I'm

0:15:57.580000 --> 0:16:00.540000
 writing down those ideas and I'm coming
 up with labs I want to do to try

0:16:00.540000 --> 0:16:05.080000
 to flesh out those ideas
 and make them real.

0:16:05.080000 --> 0:16:10.340000
 So as inspiration strikes you, pause
 your reading or vaud washing right

0:16:10.340000 --> 0:16:16.220000
 down what you like to do, I always say try
 to come up with ways to intentionally

0:16:16.220000 --> 0:16:20.780000
 break it. That's just as valuable
 as making it work.

0:16:20.780000 --> 0:16:24.340000
 And draw the minimum topology that it
 would enable you to accomplish your

0:16:24.340000 --> 0:16:28.680000
 objective. So, let's do
 an example of this.

0:16:28.680000 --> 0:16:38.280000
 Let's say that I had just read
 about BGP AS path prepending.

0:16:38.280000 --> 0:16:40.300000
 I thought, I'd like to try that.

0:16:40.300000 --> 0:16:41.180000
 I want to do that.

0:16:41.180000 --> 0:16:47.360000
 So I think to myself, okay, what is the
 minimum requirements I would need

0:16:47.360000 --> 0:16:51.540000
 to create a lab that would
 do BGP AS path prepending?

0:16:51.540000 --> 0:16:57.140000
 Well, I know that from what I learned,
 AS path prepending is done between

0:16:57.140000 --> 0:16:58.840000
 autonomous systems.

0:16:58.840000 --> 0:17:03.240000
 It's an external BGP thing when one
 company wants to influence another

0:17:03.240000 --> 0:17:06.820000
 company. So I say to myself, okay, so
 I know at minimum I'm going to need

0:17:06.820000 --> 0:17:11.920000
 to develop a topology that has two
 autonomous systems, let's say.

0:17:11.920000 --> 0:17:17.300000
 Okay? And so now I ask myself, I say,
 okay, well, could I do this with

0:17:17.300000 --> 0:17:20.200000
 just two routers?

0:17:20.200000 --> 0:17:26.740000
 Is it possible? Well, with BGP AS path
 prepending, the idea is a single

0:17:26.740000 --> 0:17:31.900000
 router has learned from a different
 company, a different AS, the same

0:17:31.900000 --> 0:17:34.120000
 route, but from two
 different locations.

0:17:34.120000 --> 0:17:37.120000
 This router says, okay, I've learned
 about the 90 network via this guy

0:17:37.120000 --> 0:17:40.240000
 up here and via this guy up here.

0:17:40.240000 --> 0:17:44.700000
 And they're trying to influence
 me by using AS path prepending.

0:17:44.700000 --> 0:17:45.940000
 So I think, okay, let's see here.

0:17:45.940000 --> 0:17:50.280000
 This router now needs to learn about one
 route from two different locations.

0:17:50.280000 --> 0:17:53.520000
 Can't really do that with
 just two routers.

0:17:53.520000 --> 0:17:58.300000
 So at a minimum, I'm going to need
 three routers to accomplish this.

0:17:58.300000 --> 0:18:00.600000
 So I say, all right, I'll do this.


0:18:00.600000 --> 0:18:03.980000
 Now, how these guys are
 connected, I don't care.

0:18:03.980000 --> 0:18:06.720000
 I don't care if it's fast-eathened,
 I don't care if it's serial.

0:18:06.720000 --> 0:18:09.640000
 That's irrelevant to me, so
 I'll just draw some lines.

0:18:09.640000 --> 0:18:13.620000
 Okay, now let's say, all right, this
 is going to be AS 100 just to make

0:18:13.620000 --> 0:18:15.400000
 up some numbers here.

0:18:15.400000 --> 0:18:19.980000
 AS 200, put some numbers on these
 routers so I can identify them.

0:18:19.980000 --> 0:18:25.800000
 Great. Now I say, okay, well, I'm going
 to need to come up with some,

0:18:25.800000 --> 0:18:26.860000
 let's see, what else
 do I need here?

0:18:26.860000 --> 0:18:29.500000
 Well, these router one and router two
 are going to need to advertise the

0:18:29.500000 --> 0:18:31.600000
 exact same network
 to router three.

0:18:31.600000 --> 0:18:34.560000
 Well, let's see, what's the minimum
 I could do to accomplish that?

0:18:34.560000 --> 0:18:38.180000
 Minimum hard run is create the
 same loopback in both of them.

0:18:38.180000 --> 0:18:42.640000
 Loopback zero, 2020
-20-0, slash 24.

0:18:42.640000 --> 0:18:47.440000
 This way, I don't need an additional
 cable, I don't need an additional

0:18:47.440000 --> 0:18:52.000000
 interface for these routers to advertise
 the exact same route to each

0:18:52.000000 --> 0:18:55.820000
 other. Okay, great.

0:18:55.820000 --> 0:19:02.040000
 So now I've just developed the minimal
 topology I will need to do AS path

0:19:02.040000 --> 0:19:06.680000
 prepending. With just three routers
 and two interfaces, I could practice

0:19:06.680000 --> 0:19:11.560000
 this feature. So you're going to
 want to do something like this.

0:19:11.560000 --> 0:19:15.980000
 Think about what you want to practice,
 draw it out, minimal possible,

0:19:15.980000 --> 0:19:20.060000
 and then replicate
 that on your rack.

0:19:20.060000 --> 0:19:24.360000
 Okay, so now you compare your drawing
 against your available lab topology.

0:19:24.360000 --> 0:19:27.320000
 So here's where you take that drawing
 you came up with, and you go to

0:19:27.320000 --> 0:19:31.780000
 the INE rack you decide to use, or the
 Cisco Learning Lab rack you decide

0:19:31.780000 --> 0:19:36.840000
 to use. You say, okay, how am I going
 to incorporate this into the equipment

0:19:36.840000 --> 0:19:39.180000
 I have available to me?

0:19:39.180000 --> 0:19:42.240000
 And here's where you're going to add
 port numbers and interface numbers

0:19:42.240000 --> 0:19:44.580000
 to my drawing to match
 the lab topology.

0:19:44.580000 --> 0:19:46.240000
 So I say, okay, let's go back.

0:19:46.240000 --> 0:19:52.500000
 So this is what I'm going to build,
 okay, and this is the rack available

0:19:52.500000 --> 0:19:55.780000
 to me. And right now I'm just
 looking at my LAN connections.

0:19:55.780000 --> 0:19:57.860000
 So I know I need three routers.

0:19:57.860000 --> 0:20:03.020000
 So why don't I just use routers
 one, two, and three.

0:20:03.020000 --> 0:20:04.660000
 Expand this a little bit here.

0:20:04.660000 --> 0:20:07.980000
 You can see this better.

0:20:07.980000 --> 0:20:20.760000
 There we go. Three is sort
 of a hub and spoke design.

0:20:20.760000 --> 0:20:22.820000
 So three needs to connect
 to one and two.

0:20:22.820000 --> 0:20:27.940000
 Well, if I look at this, three
 does have two interfaces.

0:20:27.940000 --> 0:20:30.920000
 So fast ethernet zero zero and
 fast ethernet zero slash one.

0:20:30.920000 --> 0:20:33.180000
 Okay, so I'll draw that on here.

0:20:33.180000 --> 0:20:36.340000
 So we'll just say this is
 fast ethernet zero zero.

0:20:36.340000 --> 0:20:40.120000
 This is fast ethernet
 zero slash one.

0:20:40.120000 --> 0:20:41.320000
 Okay, I've got my interface there.


0:20:41.320000 --> 0:20:44.820000
 Now, to connect three to one, how am
 I going to do that with my available

0:20:44.820000 --> 0:20:46.760000
 topology? Well, let's see here.

0:20:46.760000 --> 0:20:49.380000
 I can go through switch
 two and do that.

0:20:49.380000 --> 0:20:52.220000
 So I'll just draw that into
 my topology diagram.

0:20:52.220000 --> 0:20:55.100000
 I'll say, okay, I'm going to
 have switch two right here.

0:20:55.100000 --> 0:21:02.160000
 Switch two, and that's going to be
 zero three on one side and zero two

0:21:02.160000 --> 0:21:05.140000
 on another. And so you just
 start addhow am I going to
incorporate this into the equipment

366
00:19:37,193 --> 00:19:38,693
I have available to me?

367
00:19:38,693 --> 00:19:42,593
Here's where you're going to add
port numbers and interface numbers

368
00:19:42,593 --> 00:19:44,993
to my drawing to match the lab topology.

369
00:19:44,993 --> 00:19:46,193
I say, okay, let's go back.

370
00:19:46,493 --> 00:19:53,193
This is what I'm going to build
and this is the rack available to

371
00:19:53,193 --> 00:19:55,593
me. Right now, I'm just looking
at my LAN connections.

372
00:19:55,593 --> 00:19:57,393
I know I need three routers.

373
00:19:57,393 --> 00:20:04,293
Why don't I just use Routers 1,
2, and 3 expand this a little bit

374
00:20:04,293 --> 00:20:06,693
here so you can see this better.

375
00:20:06,993 --> 00:20:13,093
Here we go. So routers 1, 2, and 3.

376
00:20:13,093 --> 00:20:15,793
And according to my diagram right here,

377
00:20:15,793 --> 00:20:22,693
3 is sort of a hub-and-spoke design,
so 3 needs to connect to 1 and

378
00:20:22,693 --> 00:20:28,093
2. Well, if I look at this,
3 does have two interfaces,

379
00:20:28,093 --> 00:20:31,393
so FastEthernet0/0 and FastEthernet0/1.

380
00:20:31,393 --> 00:20:32,593
Okay, so I'll draw that on here.

381
00:20:32,593 --> 00:20:36,193
So we'll just say this is FastEthernet0/0,

382
00:20:36,193 --> 00:20:40,093
this is FastEthernet0/1.

383
00:20:40,393 --> 00:20:41,593
Okay, I got my interface there.

384
00:20:41,593 --> 00:20:45,193
Now, to connect 3 to 1, how am I
going to do that with my available

385
00:20:45,193 --> 00:20:49,093
topology? Well, see here, I could
go through switch 2 and do that.

386
00:20:49,093 --> 00:20:52,693
So I'll just draw that
into my topology diagram.

387
00:20:52,693 --> 00:20:54,793
I'll say, okay, I'm going to
have switch 2 right here,

388
00:20:54,793 --> 00:21:03,193
switch 2, and that's going to be
0/3 on one side and 0/2 on another

389
00:21:03,493 --> 00:21:05,293
You just start adding this in.

390
00:21:05,293 --> 00:21:13,993
This can be 0/3 over here and let's say 0/
- I'm going to Router

391
00:21:13,993 --> 00:21:18,793
2 - so 0/1-- okay, Router 1 0/2.

392
00:21:19,093 --> 00:21:24,193
That ultimately leads
me to fastethernet 0/1.

393
00:21:24,493 --> 00:21:26,593
This is what you're doing.

394
00:21:26,893 --> 00:21:30,793
You're taking what you conceptually
developed and you're adding the

395
00:21:30,793 --> 00:21:34,393
real logistics to this of what
your actual topology supports.

396
00:21:34,393 --> 00:21:35,293
I would do the same thing.

397
00:21:35,293 --> 00:21:36,493
I'm not going to fill
it in here but I'd say,

398
00:21:36,493 --> 00:21:41,193
okay, for 3 to use his other
interface fastethernet 0/1 to get to

399
00:21:41,493 --> 00:21:46,593
Router 2, I would probably add in two
switches and type in my interface

400
00:21:46,593 --> 00:21:51,093
numbers. Eventually, I'd come up
with a real drawing of the port

401
00:21:51,393 --> 00:21:55,293
numbers and interface names and
numbers I'm going to use to connect

402
00:21:55,593 --> 00:21:56,193
this altogether.

403
00:21:56,493 --> 00:22:03,993
Now you can devise your IP addressing
scheme and any other prerequisite

404
00:22:03,993 --> 00:22:04,893
configurations.

405
00:22:05,193 --> 00:22:06,993
So I take a look at what
I'm drawing right here.

406
00:22:07,293 --> 00:22:11,193
And remember, we're doing all this
before I actually rent any time,

407
00:22:11,193 --> 00:22:13,893
and my money is actually
counting down at all.

408
00:22:13,893 --> 00:22:18,993
And I say, you'll see see here,
in order to do my IP addressing--

409
00:22:18,993 --> 00:22:21,393
let's just put in some addresses here.

410
00:22:21,393 --> 00:22:28,593
Let's just say this is 3.2.3.3,
let's say this is 3.2.3.2.

411
00:22:28,593 --> 00:22:33,693
And so now, I come up with my--
let's just do this one over here,

412
00:22:33,693 --> 00:22:37,593
since I've already done
my interface numbers.

413
00:22:37,893 --> 00:22:47,193
This one up here, 3.1.3.1/24.

414
00:22:47,193 --> 00:22:51,393
At this point, this is where I
start coming off of my pre-config,

415
00:22:51,393 --> 00:22:55,893
so I can just copy and paste something
into my router without wasting

416
00:22:55,893 --> 00:22:57,393
valuable rack rental time.

417
00:22:57,393 --> 00:23:07,593
So I say, this is going to be
R3 enable config T hostname R3,

418
00:23:07,593 --> 00:23:13,593
interface FastEthernet0/0, and
let's put all my stuff in here.

419
00:23:13,593 --> 00:23:15,993
I'm not going to complete this,
but you just get the idea.

420
00:23:16,293 --> 00:23:24,093
IP address 3.1.3.3 no shut.

421
00:23:24,093 --> 00:23:29,493
And so by the time I'm done with
this, I will have a configuration,

422
00:23:29,793 --> 00:23:34,066
for R3 has got my IP addresses,
it has my BGP configuration with

423
00:23:34,066 --> 00:23:38,266
AS 200. And so once I hit the
start button on my rack rental,

424
00:23:38,266 --> 00:23:44,066
I can just copy and paste this in
without wasting time of coming up

425
00:23:44,066 --> 00:23:45,266
with it beforehand.

426
00:23:45,266 --> 00:23:49,766
And then lastly, devise a rough
time estimate for how long I think

427
00:23:49,766 --> 00:23:52,766
it's going to take for me
to complete my objective.

428
00:23:53,066 --> 00:23:56,866
So I might think to myself, well,
after I'm all said and done

429
00:23:56,866 --> 00:23:59,566
here, this is actually a pretty small lab.

430
00:23:59,866 --> 00:24:03,466
I think it's probably only going
to take me about 15 or 20 minutes

431
00:24:03,466 --> 00:24:08,566
to complete this but when I
look at this company's website,

432
00:24:08,866 --> 00:24:12,766
the minimum time I have to rent
time on the rack is one hour.

433
00:24:12,766 --> 00:24:17,566
I don't want to rent one hour and
then just spend 20 minutes doing

434
00:24:17,866 --> 00:24:19,966
my lab and then I'm done
because that's wasted time,

435
00:24:19,966 --> 00:24:23,866
so now that I know that in advance,
let me see if I can come up with

436
00:24:23,866 --> 00:24:27,166
some other objectives that will fill
up that time so I will effectively

437
00:24:27,466 --> 00:24:31,066
use that one hour slot
that I'm renting because,

438
00:24:31,066 --> 00:24:33,166
remember, my objective here is
I don't want to waste money.

439
00:24:33,466 --> 00:24:37,666
So, don't log into the remote equipment
until you have enough objectives

440
00:24:37,666 --> 00:24:40,666
to fill up your scheduled time slot.

441
00:24:40,966 --> 00:24:44,266
When you're using a vendor's remote
rack system for the first time,

442
00:24:44,266 --> 00:24:45,766
you're not going to be familiar with it.

443
00:24:45,766 --> 00:24:48,166
You're not going to be
familiar with the menu system,

444
00:24:48,166 --> 00:24:50,866
with how to move around in
it, with how to start it,

445
00:24:51,166 --> 00:24:55,066
with how to load configs, so be aware
of that up front and just know,

446
00:24:55,366 --> 00:24:58,366
just think to yourself, okay I'm really
going to have to budget probably

447
00:24:58,366 --> 00:25:01,666
a minimum of 5 or 10 minutes
up front, maybe 15 minutes,

448
00:25:01,966 --> 00:25:04,966
just to get familiar with the
system but you only have to do that

449
00:25:05,266 --> 00:25:08,866
once. So that will be a-- you
might consider that money wasted,

450
00:25:08,866 --> 00:25:11,266
but it'll only be once and then
you'll be familiar with it.

451
00:25:11,266 --> 00:25:13,066
But just be familiar with that.

452
00:25:13,066 --> 00:25:16,366
Start with a clean slate.

453
00:25:16,366 --> 00:25:18,166
Delete any existing configurations.

454
00:25:18,466 --> 00:25:21,166
Now, when you get into their system,
what this is talking about is,

455
00:25:21,166 --> 00:25:24,466
ideally, when you log in
to the vendor's rack,

456
00:25:24,466 --> 00:25:26,266
it'll start out with nothing.

457
00:25:26,266 --> 00:25:29,466
Right? No IP addresses, no host
names, and you can just do all that

458
00:25:29,766 --> 00:25:33,066
from scratch. But if for some reason
you select a vendor's equipment--

459
00:25:33,366 --> 00:25:38,466
for example, let's see you go with
the Cisco Learning Labs and you

460
00:25:38,466 --> 00:25:41,566
say, well, there's really no
learning lab that says default.

461
00:25:41,566 --> 00:25:42,866
So you say, let's see here.

462
00:25:42,866 --> 00:25:44,666
I want to practice BGP.

463
00:25:44,666 --> 00:25:46,166
I want to do AS path prepending.

464
00:25:46,466 --> 00:25:49,766
And looking at the learning labs
here, they've got a learning lab

465
00:25:50,066 --> 00:25:51,566
that's on OSPF.

466
00:25:51,566 --> 00:25:55,166
I don't care about that, but
looking at the topology,

467
00:25:55,166 --> 00:25:57,566
I think I could do my BGP lab here.

468
00:25:57,566 --> 00:26:00,266
So in that particular case,
when you log into that lab,

469
00:26:00,266 --> 00:26:03,266
it's probably going to be preconfigured
with some IP addresses and

470
00:26:03,566 --> 00:26:06,566
OSPF stuff. What I'm saying
here is wipe all that out.

471
00:26:06,566 --> 00:26:10,166
Don't add your configuration to it because,

472
00:26:10,166 --> 00:26:12,266
now, you might be introducing a
whole bunch of problems that you

473
00:26:12,266 --> 00:26:13,166
don't want to have to troubleshoot.

474
00:26:13,466 --> 00:26:14,666
Just clean it all out.

475
00:26:14,666 --> 00:26:17,966
Yes, it'll take maybe three or four
minutes of time to clean it all

476
00:26:17,966 --> 00:26:20,966
out, write, erase, and reload, but
then start with a clean slate.

477
00:26:21,266 --> 00:26:24,266
And after implementing
your own initial config,

478
00:26:24,266 --> 00:26:26,966
save them again to text files
if any changes were made.

479
00:26:26,966 --> 00:26:31,166
As I was making my pre-config
there in my Notepad or whatever,

480
00:26:31,166 --> 00:26:33,566
it's inevitable that I'm
going to make mistakes.

481
00:26:33,566 --> 00:26:38,366
I might forget to put the AS number
after my router BGP statement.

482
00:26:38,666 --> 00:26:43,166
I might forget to put the update
source loopback0 after my neighbor

483
00:26:43,466 --> 00:26:45,566
statement. There might be little
things like that here and there

484
00:26:45,566 --> 00:26:51,266
which as I copy and paste, I will
realize and say unsupported command

485
00:26:51,266 --> 00:26:53,366
or incomplete command
or something like that.

486
00:26:53,366 --> 00:26:56,966
Well, as I change that,
change it in my pre-config.

487
00:26:56,966 --> 00:26:59,666
So now, if I ever want to
go back and redo that lab,

488
00:26:59,666 --> 00:27:01,466
I fixed my text file.

489
00:27:01,766 --> 00:27:03,666
It's perfect. I can now copy and paste it.

490
00:27:03,666 --> 00:27:07,266
ready to go. You're probably going
to want to play around debugs.

491
00:27:07,266 --> 00:27:08,766
Debugs are fun, right?

492
00:27:08,766 --> 00:27:10,266
Debugs show you all kinds of stuff.

493
00:27:10,566 --> 00:27:14,166
It is a good thing to know what
debug do I need to turn on to see

494
00:27:14,166 --> 00:27:15,966
what I want to see.

495
00:27:15,966 --> 00:27:18,666
What debug will show me
what I'm looking for?

496
00:27:18,966 --> 00:27:22,566
But as it says here, debugs can
be hazardous to your health.

497
00:27:22,566 --> 00:27:24,966
Keep in mind that when you turn on a debug,

498
00:27:24,966 --> 00:27:27,966
what are you asking that
router or switch really to do?

499
00:27:28,266 --> 00:27:33,666
You're telling the CPU, hey CPU, even
though you can do billions of instructions

500
00:27:33,666 --> 00:27:38,266
per second, I want you to slow down
and everything you think about,

501
00:27:38,266 --> 00:27:41,866
I want you to send it to the
console so I can see it.

502
00:27:41,866 --> 00:27:46,666
If a debug is really chatty like let's
say you do some sort of spanning-tree

503
00:27:46,666 --> 00:27:50,566
debug and spanning-tree can be very
chatty-- if you've got lots of

504
00:27:50,566 --> 00:27:52,966
interfaces running spanning-tree
and lots of VLANs,

505
00:27:53,266 --> 00:27:55,666
you can turn on debug within a
couple of seconds and [boom?],

506
00:27:55,966 --> 00:27:57,666
all kinds of stuff is going on there.

507
00:27:57,666 --> 00:28:01,266
Ultimately, you can end up
crashing a system by doing that.

508
00:28:01,566 --> 00:28:06,066
The CPU can just be so overwhelmed
spitting out all that output to

509
00:28:06,066 --> 00:28:08,166
the console that just freezes up or dies.

510
00:28:08,466 --> 00:28:10,066
So here's a suggestion.

511
00:28:10,066 --> 00:28:12,166
Number one, don't log it to the console.

512
00:28:12,166 --> 00:28:14,866
You don't really need
to see it in real time.

513
00:28:14,866 --> 00:28:18,166
You don't want to have a situation
where your inner remote rack,

514
00:28:18,166 --> 00:28:22,066
you paid money to be there,
and then you crashed it.

515
00:28:22,066 --> 00:28:23,866
You don't want to deal with that.

516
00:28:23,866 --> 00:28:27,766
So no logging console debug,
which is basically saying,

517
00:28:27,766 --> 00:28:31,566
look, when I turn on a debug, don't
show me the results in the console.

518
00:28:31,566 --> 00:28:36,366
Instead, take those results and
send them to a memory buffer,

519
00:28:36,366 --> 00:28:38,466
logging buffer debug.

520
00:28:38,466 --> 00:28:42,366
And then I can just see the
output of that when I want to.

521
00:28:42,666 --> 00:28:45,366
So for example I can say,
Clear log, start my debug,

522
00:28:45,366 --> 00:28:48,066
like in this case I'm using an EIGRP debug.

523
00:28:48,066 --> 00:28:52,666
Let it run for a few seconds,
stop it with un all,

524
00:28:52,666 --> 00:28:55,366
that's short for undebug all,
and then look at the log.

525
00:28:55,666 --> 00:28:57,766
Show log, and there will be
all the output right there.

526
00:28:58,066 --> 00:29:02,966
And I don't risk crashing the router
or crashing the switch by doing

527
00:29:02,966 --> 00:29:06,866
that, because there's nothing
worse than crashing a device in

528
00:29:06,866 --> 00:29:10,166
your rack and then having to sit
back and wait potentially hours

529
00:29:10,466 --> 00:29:14,666
or days for some technician to get
to that rack and fix it again.

530
00:29:14,666 --> 00:29:22,766
All right, so that brings
me to the end of this.

531
00:29:22,766 --> 00:29:26,066
Now I did promise you that before I
finished I would show you how to

532
00:29:26,066 --> 00:29:30,066
access INE's racks and sort of
how to move around within them.

533
00:29:30,066 --> 00:29:34,266
But before I do that, let me just see
if there's any unanswered questions.

534
00:29:34,566 --> 00:29:35,766
Are there any questions from anyone?

535
00:29:35,766 --> 00:29:40,266
Nathaniel, you've got a good question here.

536
00:29:40,566 --> 00:29:44,766
So Nathaniel says sometimes he has
a hard time understanding what

537
00:29:44,766 --> 00:29:46,866
the INE lab is asking him to do.

538
00:29:46,866 --> 00:29:49,866
I assume you're talking about like
instructions within an INE workbook,

539
00:29:50,166 --> 00:29:54,366
I think. Are the Cisco labs
written in a similar verbiage?

540
00:29:54,666 --> 00:29:58,366
I always recommend to people, and
this is why I say read through a

541
00:29:58,366 --> 00:30:02,266
lab workbook in advance before you
actually start your timer on your

542
00:30:02,566 --> 00:30:03,166
remote equipment.

543
00:30:03,466 --> 00:30:07,366
If you read through a workbook or a
pre-designed lab guide and something

544
00:30:07,669 --> 00:30:10,966
in there is unclear, that's your
opportunity to contact the company.

545
00:30:10,966 --> 00:30:16,066
Send a message to-- for example,
you might not know who within INE

546
00:30:16,066 --> 00:30:19,966
developed a workbook but you can
always send a-- within INE's website,

547
00:30:19,966 --> 00:30:22,966
there is a contact link and you can
always send us a general e-mail

548
00:30:22,966 --> 00:30:26,166
saying I've got a question
about task number

549
00:30:26,466 --> 00:30:27,666
5 in the route workbook.

550
00:30:27,666 --> 00:30:30,066
Can you please have someone
get back to me on that?

551
00:30:30,366 --> 00:30:34,266
Send an e-mail to sales or support
at INE.com or something like that.

552
00:30:34,266 --> 00:30:36,366
That's your opportunity
to ask for clarification.

553
00:30:36,666 --> 00:30:38,166
Yeah, you want to get that clarification.

554
00:30:38,466 --> 00:30:41,466
The Cisco labs, I don't know.

555
00:30:41,466 --> 00:30:44,166
If you're talking about labs
written on Cisco's website,

556
00:30:44,166 --> 00:30:47,466
I have not looked at those so I
don't know if they are well-written

557
00:30:47,775 --> 00:30:48,966
or if they are not.

558
00:30:48,966 --> 00:30:56,466
Imran asks, is there any way that
we can use network monitoring

559
00:30:56,766 --> 00:31:00,966
software like CiscoWorks, Cisco Prime,
or SolarWinds to work alongside

560
00:31:01,266 --> 00:31:05,466
your devices? I assume you're
talking about a home lab,

561
00:31:05,466 --> 00:31:06,666
not a remote lab.

562
00:31:06,966 --> 00:31:09,366
If you're using a home lab, certainly.

563
00:31:09,366 --> 00:31:12,966
If you have access to CiscoWorks
or SolarWinds or something like

564
00:31:13,266 --> 00:31:16,266
that, you can always
install that and use that.

565
00:31:16,266 --> 00:31:19,866
If you were accessing a
remote lab, probably not.

566
00:31:19,866 --> 00:31:24,366
You're going to be limited to
whatever hardware or whatever servers

567
00:31:24,366 --> 00:31:26,766
they have available in the remote rack.

568
00:31:26,766 --> 00:31:30,966
[music]