1 00:00:02,001 --> 00:00:08,639 [music] 2 00:00:08,639 --> 00:00:10,739 So now we're going to go into the last section of today's 3 00:00:11,039 --> 00:00:14,603 presentation. You decide that you want to design and create your 4 00:00:14,903 --> 00:00:17,603 own labs. And what I mean by that is you're using somebody else's 5 00:00:17,603 --> 00:00:22,217 topology like INE's or somebody else but you're going to create your 6 00:00:22,217 --> 00:00:24,917 own topologies, your own protocols, and you're going to play with 7 00:00:25,217 --> 00:00:25,517 their equipment. 8 00:00:25,817 --> 00:00:27,617 So what's the best way to do that? 9 00:00:27,641 --> 00:00:31,641 And by the way, when I'm done with all of this somebody asked me 10 00:00:31,641 --> 00:00:34,041 earlier - I don't remember who it was - if I could just real quickly 11 00:00:34,041 --> 00:00:38,241 do a demonstration on how to get into INE's racks and how to rent 12 00:00:38,241 --> 00:00:39,141 time and stuff. 13 00:00:39,141 --> 00:00:40,041 I'll show you how to do that. 14 00:00:40,341 --> 00:00:42,741 So for those of you who are not familiar with that we will go into 15 00:00:43,041 --> 00:00:44,741 that as soon as I'm done with this session right here. 16 00:00:44,741 --> 00:00:50,141 Okay, so I talked about the pros and cons previously of using 17 00:00:50,141 --> 00:00:53,741 a workbook. What are the pros and cons of not using a workbook, 18 00:00:54,041 --> 00:00:55,541 doing everything from your own brain? 19 00:00:55,541 --> 00:01:01,241 Well, you can custom tailor your lab based on your available resources. 20 00:01:01,241 --> 00:01:08,041 That's nice. You can custom-tailor your lab based on your own interest. 21 00:01:08,041 --> 00:01:10,741 You're not dependent on the interest of the lab developer. 22 00:01:11,041 --> 00:01:12,241 You can do whatever features and protocols, 23 00:01:12,541 --> 00:01:15,841 whatever IOS commands you want to do. 24 00:01:15,841 --> 00:01:20,941 You have now opportunity to go into much greater depth on a topic 25 00:01:20,941 --> 00:01:23,941 than is typically found in a pre-designed lab guide. 26 00:01:23,941 --> 00:01:29,041 That's true. And this is probably the single biggest advantage. 27 00:01:29,041 --> 00:01:34,741 Trying something and failing is a great learning opportunity. 28 00:01:34,741 --> 00:01:41,041 For example, I have probably personally learned the most when I sat 29 00:01:41,041 --> 00:01:43,441 down with a piece of paper and I said, okay, 30 00:01:43,741 --> 00:01:44,841 here's what I want to do. 31 00:01:45,141 --> 00:01:53,036 I've got two routers with two paths to each other and I want to try 32 00:01:53,036 --> 00:01:57,836 to influence load-balancing, maybe influence my EIGRP load-balancing 33 00:01:57,836 --> 00:02:00,836 based off of the load variable. 34 00:02:01,136 --> 00:02:02,936 I don't care about bandwidth or delay. 35 00:02:02,936 --> 00:02:06,236 I want to see if I can influence the load on a particular link to 36 00:02:06,236 --> 00:02:09,236 get EIGRP to flip over to a link that has less load. 37 00:02:09,236 --> 00:02:11,636 Let's just say this is actually something I tried recently. 38 00:02:11,636 --> 00:02:14,636 I drew it all out. 39 00:02:14,636 --> 00:02:17,636 I pre-configured it with IP addresses and stuff. 40 00:02:17,636 --> 00:02:19,736 I discovered that I couldn't. 41 00:02:20,036 --> 00:02:22,436 There's no way for me to get that to work. 42 00:02:22,436 --> 00:02:25,436 Well that's not a failure in my mind. 43 00:02:25,436 --> 00:02:26,528 Even though I couldn't get to get it to work, 44 00:02:26,528 --> 00:02:28,328 that was an incredible learning opportunity. 45 00:02:28,328 --> 00:02:32,828 I learned how to get EIGRP to factor load into the calculation. 46 00:02:32,828 --> 00:02:36,728 I learned how to increase the load on an interface. 47 00:02:36,728 --> 00:02:37,628 I learned all kinds of stuff. 48 00:02:37,628 --> 00:02:39,728 So even though I wasn't able to meet my objective, 49 00:02:39,728 --> 00:02:44,228 by failing, I learned a whole bunch of stuff I didn't know before. 50 00:02:44,228 --> 00:02:47,828 You're not going to get that experience when you're following a lab 51 00:02:47,828 --> 00:02:51,428 guide, right? A lab guide is typically built so that if you follow 52 00:02:51,428 --> 00:02:53,528 the steps, you will succeed. 53 00:02:53,828 --> 00:02:56,528 If you follow the steps, you will succeed in configuring 54 00:02:56,528 --> 00:02:59,228 or doing whatever the lab developer wanted you to do. 55 00:02:59,228 --> 00:03:02,128 They're not typically-- you're going to design something into a lab 56 00:03:02,128 --> 00:03:05,728 guide to intentionally have you fail, sometimes but usually not. 57 00:03:05,728 --> 00:03:11,428 And in my personal opinion understanding why something doesn't 58 00:03:11,428 --> 00:03:15,628 work can be just as valuable as understanding why it does work. 59 00:03:15,628 --> 00:03:19,828 I tell people all the time, look, when you're first learning about 60 00:03:20,128 --> 00:03:23,428 EIGRP what are some of the first things they want you to know? 61 00:03:23,428 --> 00:03:25,228 EIGRP neighbor relationships. 62 00:03:25,228 --> 00:03:27,628 What's required to make the neighbor relationship? 63 00:03:27,628 --> 00:03:29,428 The K values have to be the same. 64 00:03:29,428 --> 00:03:32,128 The autonomous system values have to be the same, 65 00:03:32,128 --> 00:03:33,328 so they give you four or five things. 66 00:03:33,628 --> 00:03:36,928 But they don't really tell you about well, 67 00:03:36,928 --> 00:03:40,828 what are you going to see if some of those things don't match up? 68 00:03:40,828 --> 00:03:42,928 That's very valuable information. 69 00:03:42,928 --> 00:03:44,728 I love going into a lab and saying, okay, 70 00:03:44,728 --> 00:03:46,228 what if my K values don't match? 71 00:03:46,228 --> 00:03:49,528 What if my autonomous system number doesn't match? 72 00:03:49,828 --> 00:03:51,628 Can I see something in a debug? 73 00:03:51,628 --> 00:03:55,228 Can I see something in a sys log that will clue me off to that? 74 00:03:55,228 --> 00:03:57,928 Because that's going to help you in the long run with troubleshooting 75 00:03:57,928 --> 00:04:00,928 stuff. Just getting it to work, and getting it to work, 76 00:04:00,928 --> 00:04:03,028 and getting it to work, that's not really going to help you if you 77 00:04:03,028 --> 00:04:04,228 ever need to troubleshoot this stuff. 78 00:04:04,528 --> 00:04:10,528 Now what are some cons to designing your own labs? 79 00:04:10,828 --> 00:04:14,128 Well, you might end up spending valuable time on troubleshooting 80 00:04:14,428 --> 00:04:17,728 problems. Now there's a silver lining to this cloud but some people 81 00:04:17,728 --> 00:04:23,128 could say, hey look, I rented three hours on this rack and before 82 00:04:23,128 --> 00:04:26,128 I even pressed the start button I came up with this nice lab I want 83 00:04:26,128 --> 00:04:30,628 to do based on private VLANs here, which go into DHCP snooping here, 84 00:04:30,628 --> 00:04:35,128 which feed into EIGRP here, but I only got into the private VLAN 85 00:04:35,128 --> 00:04:38,128 section - the very first part of my lab - and I started getting error 86 00:04:38,128 --> 00:04:41,428 messages and it wasn't working right, and I consumed my entire three 87 00:04:41,428 --> 00:04:44,128 hours just troubleshooting private VLANs. 88 00:04:44,428 --> 00:04:47,428 Well, you can look at that one of two ways, 89 00:04:47,728 --> 00:04:51,928 right? That could be a con that you weren't able to complete within 90 00:04:51,928 --> 00:04:54,328 your allotted time what you wanted to complete, 91 00:04:54,328 --> 00:04:58,828 but the pro is you learned a heck of a lot about private VLANs during 92 00:04:59,128 --> 00:05:00,328 all that troubleshooting, right? 93 00:05:00,629 --> 00:05:03,028 So there is a silver lining to that. 94 00:05:03,028 --> 00:05:09,128 You may miss critical features and protocols, 95 00:05:09,128 --> 00:05:15,728 right? You are designing your lab based on what you think is in the 96 00:05:15,728 --> 00:05:19,628 certification exam and you did that probably based on the blueprint, 97 00:05:19,628 --> 00:05:22,628 you looked at the route or the switch or the CCIE blueprint, 98 00:05:22,628 --> 00:05:26,728 and you're doing your labs based on that but blueprints don't always 99 00:05:26,728 --> 00:05:27,928 give you the full picture. 100 00:05:27,928 --> 00:05:31,228 A lot of times there's features and protocols that these exams expect 101 00:05:31,228 --> 00:05:33,328 you to know that they don't put into the blueprint. 102 00:05:33,628 --> 00:05:36,628 Personally, I think that's kind of nasty that they do that but that 103 00:05:36,928 --> 00:05:39,928 does happen and so, if you're just making your labs up yourself, 104 00:05:40,228 --> 00:05:42,028 how are you going to know what you missed? 105 00:05:42,028 --> 00:05:44,428 That might be a problem. 106 00:05:44,428 --> 00:05:50,428 You might accidentally design a lab that's unsupported by your available 107 00:05:50,728 --> 00:05:52,528 hardware and feature set. 108 00:05:52,528 --> 00:05:53,728 It happens, right? 109 00:05:53,728 --> 00:05:57,628 I mean, when you're going back to building the home lab, 110 00:05:57,628 --> 00:06:02,128 chances are you're not going to be able to think of 100% of everything 111 00:06:02,428 --> 00:06:05,128 you're ever going to want to do on your home lab. 112 00:06:05,429 --> 00:06:06,928 There's going to be something you're going to miss. 113 00:06:06,928 --> 00:06:09,328 Same thing here. 114 00:06:09,328 --> 00:06:14,128 If you're using a remote rack, you know in advance what the topology 115 00:06:14,128 --> 00:06:15,328 that remote rack looks like. 116 00:06:15,328 --> 00:06:18,928 You know in advance what hardware and software is in there. 117 00:06:18,928 --> 00:06:21,128 So maybe you think to yourself, okay. 118 00:06:21,128 --> 00:06:26,028 based on this topology right here, I want to create IPv6 tunnels. 119 00:06:26,028 --> 00:06:29,028 I want to do some ISATAP between these two routers right here. 120 00:06:29,028 --> 00:06:31,728 And you spend a bunch of time writing up your lab, 121 00:06:32,028 --> 00:06:32,628 drawing it up. 122 00:06:32,928 --> 00:06:36,528 And then you press a start button, only to discover ISATAP is not 123 00:06:36,528 --> 00:06:39,528 an option. I'm doing tunnel mode and I don't see ISATAP in there 124 00:06:39,528 --> 00:06:42,228 because this feature set on this switch or router doesn't support 125 00:06:42,228 --> 00:06:45,828 it. That kind of stinks because now the time is counting down, 126 00:06:45,828 --> 00:06:48,528 and the lab you developed, you can't even do. 127 00:06:48,828 --> 00:06:51,228 So you'll run into that sometimes as well. 128 00:06:51,228 --> 00:06:56,928 And you might leave yourself down a rat hole. 129 00:06:56,928 --> 00:07:02,328 What I mean by this is you might start out by developing a lab on 130 00:07:02,328 --> 00:07:06,828 I don't know, DHCP snooping or something like that. 131 00:07:06,828 --> 00:07:09,528 You got all built out, you drew your Cloud, 132 00:07:09,828 --> 00:07:12,828 your IP address and everything, press the start button on your remote 133 00:07:12,828 --> 00:07:16,428 rack and now your two hours that you reserved starts counting down. 134 00:07:16,428 --> 00:07:18,406 And you get a little into it and you say, 135 00:07:18,406 --> 00:07:21,706 oh here's a cool keyword, I've never seen that before, 136 00:07:21,706 --> 00:07:22,606 I wonder what that does? 137 00:07:22,606 --> 00:07:26,506 Oh, let me try this, let me try this, and all of a sudden two hours 138 00:07:26,506 --> 00:07:29,806 has gone by and you've just been stuck on this one command trying 139 00:07:29,806 --> 00:07:32,206 out various keywords, doing a little bit of research right here, 140 00:07:32,506 --> 00:07:36,406 and your time is up and you never even got 20% into the lab you wanted 141 00:07:36,406 --> 00:07:39,106 to get into because you got stuck in this rathole. 142 00:07:39,106 --> 00:07:41,506 Once again, pros and cons. 143 00:07:41,806 --> 00:07:44,206 The pro of that is, well, you learned something still, 144 00:07:44,506 --> 00:07:45,706 it was a learning experience. 145 00:07:45,706 --> 00:07:49,306 The con is, you just spent money on two hours and you did not meet 146 00:07:49,306 --> 00:07:52,306 your objective of the lab that you developed that you wanted to do. 147 00:07:52,306 --> 00:07:54,406 So those are some cons. 148 00:07:54,406 --> 00:08:00,406 Okay, so what are some approaches to designing your own labs? 149 00:08:00,406 --> 00:08:03,106 Two approaches. 150 00:08:03,106 --> 00:08:08,806 Approach number one, you can find an available topology first and 151 00:08:08,806 --> 00:08:10,906 design your labs around your resources. 152 00:08:11,206 --> 00:08:12,906 So for example, you say, okay. 153 00:08:12,906 --> 00:08:17,706 I've looked at six different vendors who offer me remote racks and 154 00:08:17,706 --> 00:08:20,606 I'm going to go with INE, of course. 155 00:08:20,606 --> 00:08:23,006 I'm looking at this topology diagram here. 156 00:08:23,006 --> 00:08:26,306 INE has given me three switches and four routers, 157 00:08:26,606 --> 00:08:28,406 a couple of backbone routers I can't really touch, 158 00:08:28,406 --> 00:08:29,606 so I can't factor those in. 159 00:08:29,906 --> 00:08:32,906 So I really got four routers and three switches available to me. 160 00:08:33,206 --> 00:08:37,106 Based on that, I'm going to build my lab on that. 161 00:08:37,106 --> 00:08:39,406 I'm going to say, well, with that, I could have a couple of autonomous 162 00:08:39,406 --> 00:08:41,206 systems. I could do some filtering here. 163 00:08:41,206 --> 00:08:42,406 Blah, blah, blah. 164 00:08:42,406 --> 00:08:43,506 So that's one approach. 165 00:08:43,506 --> 00:08:50,106 Approach number two is start by building your lab on paper. 166 00:08:50,106 --> 00:08:51,512 Saying to yourself, okay 167 00:08:51,512 --> 00:08:52,412 Here's what I want to do. 168 00:08:52,412 --> 00:08:56,012 I want to do eBGP between three different autonomous systems. 169 00:08:56,312 --> 00:09:00,812 Within this autonomous system, I want to have iBGP with five routers 170 00:09:01,112 --> 00:09:05,383 so I can practice route reflection and local preference and blah, blah, blah 171 00:09:05,383 --> 00:09:09,583 okay, so this is what I want, and now you got out and you start 172 00:09:09,583 --> 00:09:13,183 looking at some vendors and say, okay does this vendor offer a rack 173 00:09:13,183 --> 00:09:15,283 where I can implement this thing I've developed. 174 00:09:15,283 --> 00:09:17,083 That's the second approach. 175 00:09:17,083 --> 00:09:21,283 Personally, I find approach number one to be more effective. 176 00:09:21,583 --> 00:09:26,083 I think it's better to know what your constraints are first, 177 00:09:26,383 --> 00:09:29,683 pick some remote equipment, some remote rack, 178 00:09:29,683 --> 00:09:32,683 whether it be the Cisco learning labs, whether it be INE, 179 00:09:32,683 --> 00:09:37,783 whatever, and then build your topology based around the hardware 180 00:09:37,783 --> 00:09:40,183 and the connections that you have available to you. 181 00:09:40,483 --> 00:09:44,083 As I said, you're going to find it very difficult to find racks that 182 00:09:44,083 --> 00:09:46,783 meet a predesigned topology. 183 00:09:46,783 --> 00:09:51,583 All right, finding the equipment. 184 00:09:51,583 --> 00:09:53,083 So you say, okay, well how do I choose? 185 00:09:53,383 --> 00:09:55,536 There's the Cisco learning labs, there's INE, 186 00:09:55,536 --> 00:09:56,736 there's this, that, and the other thing, 187 00:09:57,036 --> 00:10:00,136 there's lots of companies out there that are providing access 188 00:10:00,136 --> 00:10:01,036 to their equipment. 189 00:10:01,036 --> 00:10:02,536 How do I select one? 190 00:10:02,536 --> 00:10:06,136 Here's some key things to look for. 191 00:10:06,436 --> 00:10:10,036 Price, clearly. 192 00:10:10,036 --> 00:10:11,836 Right? That's a factor. 193 00:10:12,136 --> 00:10:13,068 I don't think I have to talk too much about that. 194 00:10:13,368 --> 00:10:19,068 The availability of both routers and switches in a single topology. 195 00:10:19,368 --> 00:10:23,568 So you're ideally going to want to look for topology that has a combination 196 00:10:23,568 --> 00:10:28,368 of routers and switches in it which will give you more flexibility. 197 00:10:28,368 --> 00:10:33,468 If some vendor out there says here's our switching lab and they got 198 00:10:33,768 --> 00:10:34,668 five switches. 199 00:10:34,668 --> 00:10:36,468 Here's our routing lab with five routers. 200 00:10:36,768 --> 00:10:40,068 Well now, you're kind of limited in what you can do if you can only 201 00:10:40,068 --> 00:10:41,868 choose one or the other. 202 00:10:41,868 --> 00:10:46,968 Is it real equipment or emulated equipment? 203 00:10:47,268 --> 00:10:48,768 This is a big one right here. 204 00:10:48,768 --> 00:10:54,168 Now for routing labs, emulated equipment typically is fine. 205 00:10:54,168 --> 00:10:58,068 For example, if you're using GNS or the Cisco Learning Labs or something 206 00:10:58,368 --> 00:11:01,668 which use IOU, you can pretty much do everything you want to do with 207 00:11:01,668 --> 00:11:03,768 routing with that. 208 00:11:03,768 --> 00:11:06,168 Switching though, we've already talked about that. 209 00:11:06,168 --> 00:11:09,168 When it comes to the more advanced switching topics and features, 210 00:11:09,468 --> 00:11:11,868 you're going to need access to real equipment. 211 00:11:11,868 --> 00:11:15,768 An emulated or a simulated switch is just not going to cut it. 212 00:11:15,768 --> 00:11:18,468 You're going to find yourself getting very frustrated over a lack 213 00:11:18,468 --> 00:11:22,068 of commands, a lack of features and protocols you'd have available 214 00:11:22,368 --> 00:11:24,168 in a real physical switch. 215 00:11:24,468 --> 00:11:25,668 So you should know that. 216 00:11:25,668 --> 00:11:28,968 This venue right here, this guy wants to rent me his stuff for $1 217 00:11:28,968 --> 00:11:30,768 an hour. Wow, that sounds really good. 218 00:11:30,768 --> 00:11:32,268 Oh, but what am I doing? 219 00:11:32,568 --> 00:11:35,831 I'm actually getting into a server that's running VMware and I'm 220 00:11:35,831 --> 00:11:37,931 getting access to some virtual routers and switches. 221 00:11:37,931 --> 00:11:41,831 Hm, it's cheap but I'm going to be kind of limited on what I can 222 00:11:41,831 --> 00:11:47,531 do there. You want to select a topology that's flexible. 223 00:11:47,531 --> 00:11:49,931 What do I mean by that? 224 00:11:50,231 --> 00:11:53,831 Well, you want to find a topology that has a lot of link redundancy, 225 00:11:53,831 --> 00:11:56,831 a topology that's got, you know, between your switches. 226 00:11:56,831 --> 00:11:59,531 If you've got a topology of switches and there's just a single link 227 00:11:59,531 --> 00:12:02,531 between then, how are you going to do ether channel with that? 228 00:12:02,831 --> 00:12:05,531 How are you going to do topologies where a link fails and has to 229 00:12:05,531 --> 00:12:06,731 back up to another link? 230 00:12:06,731 --> 00:12:08,231 You're not going to be able to do that. 231 00:12:08,231 --> 00:12:10,031 What about router topologies? 232 00:12:10,331 --> 00:12:13,031 If you got a topology where a router just has a single serial interface 233 00:12:13,031 --> 00:12:16,631 to another router and that's it, once again you're kind of limited. 234 00:12:16,631 --> 00:12:19,631 Ideally you want to find a topology that's got multiple links 235 00:12:19,931 --> 00:12:22,631 to multiple paths through the topology, 236 00:12:22,631 --> 00:12:25,931 so you can have all sorts of designs that you can come up with. 237 00:12:26,231 --> 00:12:33,131 Scheduling availability, another thing here. 238 00:12:33,131 --> 00:12:38,531 Most remote systems has some sort of scheduling tool, 239 00:12:38,531 --> 00:12:43,331 and most of them, certainly INE's, would let you see in advance what 240 00:12:43,631 --> 00:12:44,531 the availability is. 241 00:12:44,531 --> 00:12:46,331 So this is also something to look for. 242 00:12:46,631 --> 00:12:50,031 Check it out. If you go onto some vendor's website and you say, 243 00:12:50,031 --> 00:12:54,031 oh, that's an awesome topology, pretty decent price. 244 00:12:54,031 --> 00:12:58,231 But you look at the schedule, and most of the time it's in use, 245 00:12:58,531 --> 00:13:01,831 and it's just like little tiny snippets of time here and there where 246 00:13:01,831 --> 00:13:04,731 it's free, probably don't want to plop your money down with 247 00:13:04,731 --> 00:13:06,531 that vendor because you're going to be frustrated, 248 00:13:06,531 --> 00:13:09,531 you're not going to have access to that rack when you want it. 249 00:13:09,531 --> 00:13:11,031 That's something to look at. 250 00:13:11,031 --> 00:13:18,531 Doesn't require you to download any special front-end software. 251 00:13:18,531 --> 00:13:21,831 Now, INE does not require this, but some other vendors require you 252 00:13:21,831 --> 00:13:25,431 to download some Java software or some other stuff in advance. 253 00:13:25,431 --> 00:13:31,432 And you're using their special GUI, their special application to 254 00:13:31,731 --> 00:13:34,431 get in to the routers to type in the terminals and stuff. 255 00:13:34,431 --> 00:13:36,531 Are you okay with that? 256 00:13:36,531 --> 00:13:38,431 How do you know you're not downloading a virus? 257 00:13:38,431 --> 00:13:40,831 How do you know it's not going to mess up your laptop or something? 258 00:13:40,831 --> 00:13:42,931 So that's also something to consider. 259 00:13:42,931 --> 00:13:47,731 Are there pre-loaded configurations available? 260 00:13:48,031 --> 00:13:51,931 Now, if you're going to be developing your own labs from your head, 261 00:13:52,231 --> 00:13:56,131 a pre-loaded configuration is probably not going to really do much 262 00:13:56,131 --> 00:13:59,431 for you, so that's not really a benefit. 263 00:13:59,431 --> 00:14:06,631 One other thing on here that is not really listed is that you do 264 00:14:06,931 --> 00:14:11,531 not want to spend any money on a vendor's remote rack until you can 265 00:14:11,531 --> 00:14:14,231 see the topology diagram first. 266 00:14:14,231 --> 00:14:19,331 Makes kind of common sense, but it's pretty important. 267 00:14:19,331 --> 00:14:22,331 You've got to know what you're getting into first before you spend 268 00:14:22,331 --> 00:14:23,231 money with them. 269 00:14:23,231 --> 00:14:25,031 Make sure you can see-- okay, if I get into this rack, 270 00:14:25,331 --> 00:14:27,131 how many devices are in there? 271 00:14:27,131 --> 00:14:28,931 How many connections do they have? 272 00:14:29,231 --> 00:14:32,231 Is it pretty clear to me in their instructions how to move around 273 00:14:32,531 --> 00:14:34,031 between the different devices? 274 00:14:34,331 --> 00:14:36,431 So you should know all that stuff upfront. 275 00:14:36,731 --> 00:14:43,031 What I call creative labs, these are labs that you're designing yourself 276 00:14:43,331 --> 00:14:44,231 from your head. 277 00:14:44,231 --> 00:14:47,831 I typically recommend that they're used as a supplement alongside 278 00:14:47,831 --> 00:14:50,231 reading, or watching videos, or something. 279 00:14:50,531 --> 00:14:56,531 So the way I typically do this is I might be watching a video, 280 00:14:56,531 --> 00:15:01,631 for example, and some instructor is teaching me how to do MPLS VPNs. 281 00:15:01,631 --> 00:15:03,931 And here she is going through the steps. 282 00:15:04,231 --> 00:15:06,331 And I pause it for a second. 283 00:15:06,331 --> 00:15:08,831 I say, based on what I've just learned here, 284 00:15:08,831 --> 00:15:10,331 I think I'd like to try that. 285 00:15:10,331 --> 00:15:13,431 I pause the VLAN and I write on my piece paper, 286 00:15:13,431 --> 00:15:16,731 basically what I've learned I think if I have four routers here, 287 00:15:16,731 --> 00:15:18,531 and I have them configured with this. 288 00:15:18,831 --> 00:15:20,931 I put these IP addresses on and then I resume the video. 289 00:15:21,231 --> 00:15:22,731 So, it's used as a supplement. 290 00:15:22,731 --> 00:15:25,431 Or if I'm reading a book and I'm reading about, 291 00:15:25,431 --> 00:15:29,831 okay, here's the requirements for an OSPF adjacency. 292 00:15:30,131 --> 00:15:32,331 It says, here's the various stages of OSPF, 293 00:15:32,631 --> 00:15:35,631 init, 2A, start, exchange, loading full. 294 00:15:35,631 --> 00:15:37,431 I say, oh, I'd like to see that. 295 00:15:37,431 --> 00:15:40,331 I'd like to try and build a relationship and do a debug and see if 296 00:15:40,331 --> 00:15:41,531 I can see what's happening right there. 297 00:15:41,531 --> 00:15:44,131 I'll stop reading and I'll design a lab. 298 00:15:44,131 --> 00:15:48,631 I'll say, okay, let me put these two routers together and this is 299 00:15:48,631 --> 00:15:49,831 the IP addressing scheme I'm going to use. 300 00:15:50,131 --> 00:15:52,431 I just want to do a debug to see OSPF adjacency. 301 00:15:52,731 --> 00:15:57,231 So, as I'm getting ideas as I'm watching videos or reading things, 302 00:15:57,231 --> 00:16:00,531 I'm writing down those ideas and I'm coming up with labs I want to 303 00:16:00,531 --> 00:16:03,831 do, to try to flush out those ideas and make them real. 304 00:16:03,831 --> 00:16:09,831 So as inspiration strikes you, pause your reading, 305 00:16:09,831 --> 00:16:10,731 your VOD watching. 306 00:16:10,731 --> 00:16:12,531 Write down what you like to do. 307 00:16:12,831 --> 00:16:17,031 I always say, try to come up with ways to intentionally break it. 308 00:16:17,331 --> 00:16:20,031 That's just as valuable as making it work. 309 00:16:20,031 --> 00:16:24,231 And draw the minimum topology that would enable you to accomplish 310 00:16:24,531 --> 00:16:25,431 your objective. 311 00:16:25,431 --> 00:16:28,131 So let's do an example of this. 312 00:16:28,131 --> 00:16:37,731 Let's say that I had just read about BGP AS-path prepending. 313 00:16:38,031 --> 00:16:40,131 I thought, I'd like to try that. 314 00:16:40,431 --> 00:16:41,331 I want to do that. 315 00:16:41,331 --> 00:16:43,431 So I think to myself, Okay. 316 00:16:43,431 --> 00:16:49,458 What is the minimum requirements I would need to create a lab that 317 00:16:49,758 --> 00:16:51,558 would do BGP AS-path prepending? 318 00:16:51,858 --> 00:16:56,958 Well, I know that from what I learned, AS-path prepending is done 319 00:16:56,958 --> 00:16:59,358 between autonomous systems, right? 320 00:16:59,358 --> 00:17:01,458 It's an external BGP thing. 321 00:17:01,458 --> 00:17:04,158 When one company wants to influence another company, 322 00:17:04,158 --> 00:17:07,458 I say to myself, okay, I know at minimum I'm going to need to develop 323 00:17:07,758 --> 00:17:10,758 a topology that has two autonomous systems, 324 00:17:10,758 --> 00:17:14,658 let's say. I ask myself. 325 00:17:14,958 --> 00:17:19,658 I say, could I do this with just two routers? 326 00:17:19,658 --> 00:17:21,458 Is it possible? 327 00:17:21,458 --> 00:17:28,658 With BGP AS-PATH prepending, the idea is a single router has learned 328 00:17:28,658 --> 00:17:33,158 from a different company - a different AS - the same route but from 329 00:17:33,158 --> 00:17:34,058 two different locations. 330 00:17:34,358 --> 00:17:37,258 This router says, okay, I've learned about the 90 network via this 331 00:17:37,258 --> 00:17:39,958 guy up here and via this guy up here. 332 00:17:39,958 --> 00:17:45,058 They're trying to influence me by using AS-PATH prepend. 333 00:17:45,058 --> 00:17:46,258 I think, okay, let's see here. 334 00:17:46,258 --> 00:17:48,958 This router now needs to learn about one route from two different 335 00:17:49,258 --> 00:17:53,158 locations. Can't really do that with just two routers. 336 00:17:53,458 --> 00:17:58,258 At a minimum, I'm going to need three routers to accomplish this. 337 00:17:58,258 --> 00:18:00,058 I say, all right, I'll do this. 338 00:18:00,358 --> 00:18:04,258 Now how these guys are connected, I don't care. 339 00:18:04,258 --> 00:18:06,658 I don't care if it's Fast Ethernet, I don't care if it's serial. 340 00:18:06,658 --> 00:18:09,358 That's irrelevant to me, so I'll just draw some lines. 341 00:18:09,358 --> 00:18:13,658 Okay. Now let's say, all right, this is going to be AS 100, 342 00:18:13,658 --> 00:18:14,858 just to make up some numbers here. 343 00:18:15,158 --> 00:18:19,458 AS 200, put some numbers on these routers so I can identify them. 344 00:18:19,758 --> 00:18:25,358 Great. Now I say, okay, well, I'm going to need to come up with some-- 345 00:18:25,658 --> 00:18:27,458 let's see, what else do I need here? 346 00:18:27,458 --> 00:18:30,158 These Router 1 and Router 2 are going to need to advertise the exact 347 00:18:30,158 --> 00:18:31,658 same network to Router 3. 348 00:18:31,658 --> 00:18:34,659 Let's see, what's the minimum I could do to accomplish that? 349 00:18:34,659 --> 00:18:37,958 Minimum hardware, I'll just create the same loopback in both of them. 350 00:18:38,258 --> 00:18:42,158 Loopback0 20.20.20.0/24. 351 00:18:42,458 --> 00:18:46,358 This way I don't need an additional cable, 352 00:18:46,358 --> 00:18:50,558 I don't need an additional interface for these routers to advertise 353 00:18:50,558 --> 00:18:52,658 the exact same route to each other. 354 00:18:52,658 --> 00:18:54,158 Okay, great. 355 00:18:54,158 --> 00:19:01,958 So now I've just developed the minimal topology I will need to do 356 00:19:01,958 --> 00:19:05,858 AS Path prepending with just three routers and two interfaces, 357 00:19:05,858 --> 00:19:09,158 I could practice this feature. 358 00:19:09,158 --> 00:19:11,558 You're going to want to do something like this. 359 00:19:11,558 --> 00:19:14,258 Think about what you want to practice, draw it out, 360 00:19:14,258 --> 00:19:19,058 minimal possible, and then replicate that on your rack. 361 00:19:19,358 --> 00:19:24,693 Now you compare your drawing against your available lab topology. 362 00:19:24,693 --> 00:19:27,393 Here's where you take that drawing you came up with and you go to 363 00:19:27,693 --> 00:19:32,193 the INE rack you decide to use or the Cisco learning lab rack you 364 00:19:32,193 --> 00:19:33,093 decide to use. 365 00:19:33,093 --> 00:19:37,193 You say, okay, how 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]