WEBVTT

0:00:09.160000 --> 0:00:12.680000
 You don't need to have
 a terminal server.

0:00:12.680000 --> 0:00:17.280000
 Sometimes people call it an access
 server, but it's handy.

0:00:17.280000 --> 0:00:21.000000
 So what, in case you're not familiar
 with this term, what is this?

0:00:21.000000 --> 0:00:26.300000
 So in my office here at INE, I've got
 a little real mini rack I've put

0:00:26.300000 --> 0:00:30.880000
 together. It's got, I think, three
 routers and two switches in it.

0:00:30.880000 --> 0:00:35.260000
 And it's irritating, it's useful, but
 what's irritating to me is that

0:00:35.260000 --> 0:00:37.880000
 I don't have a terminal server
 in that little mini lab.

0:00:37.880000 --> 0:00:42.460000
 So what that means is, when I want
 to change my console connection, I

0:00:42.460000 --> 0:00:46.180000
 have to physically turn around, unplug
 the console port from switch one,

0:00:46.180000 --> 0:00:47.520000
 plug it in to switch two.

0:00:47.520000 --> 0:00:50.120000
 But I'm done with that, unplug it from
 switch two, plug it in to router

0:00:50.120000 --> 0:00:53.720000
 one. I have to physically move
 the console port around.

0:00:53.720000 --> 0:00:56.440000
 Like I said, it's kind
 of irritating.

0:00:56.440000 --> 0:01:04.740000
 If that bothers you for about $120 to
 $140, you can buy a Cisco 2509 or

0:01:04.740000 --> 0:01:07.860000
 25011. These are routers
 that are end of sale.

0:01:07.860000 --> 0:01:10.200000
 Cisco hasn't sold these in a million
 years, but they're still available

0:01:10.200000 --> 0:01:13.440000
 as used products on eBay
 and other sites.

0:01:13.440000 --> 0:01:15.680000
 And you can use this
 as a terminal server.

0:01:15.680000 --> 0:01:19.760000
 So a terminal server is a router that
 has a bunch of low speed serial

0:01:19.760000 --> 0:01:23.100000
 interfaces, and it's got a special cable
 that comes out of it called an

0:01:23.100000 --> 0:01:27.200000
 octal cable. So you'll need to buy
 the octal cable along with this.

0:01:27.200000 --> 0:01:31.080000
 An octal cable is a cable that's
 got a big fat connector on it.

0:01:31.080000 --> 0:01:34.940000
 You plug it in and it's got eight
 cables that come out of it.

0:01:34.940000 --> 0:01:39.820000
 And each one of those cables connects
 into the console ports of the various

0:01:39.820000 --> 0:01:41.520000
 devices you have in your rack.

0:01:41.520000 --> 0:01:44.620000
 So what you can do is you can connect
 to the console port of the terminal

0:01:44.620000 --> 0:01:48.960000
 server, and then from there, get into
 the console ports of any of your

0:01:48.960000 --> 0:01:53.060000
 routers or switches without physically
 having to plug and unplug your

0:01:53.060000 --> 0:01:58.800000
 console cables. So it's just a convenience
 device, but if you've got the

0:01:58.800000 --> 0:02:03.660000
 money to buy one, it certainly
 will make your life easier.

0:02:03.660000 --> 0:02:07.420000
 Don't think about resale value.

0:02:07.420000 --> 0:02:11.340000
 Cisco equipment does not,
 it's not an investment.

0:02:11.340000 --> 0:02:14.760000
 It's not like buying a house
 or diamonds or something.

0:02:14.760000 --> 0:02:18.580000
 This stuff goes down
 in value super fast.

0:02:18.580000 --> 0:02:22.420000
 I mean, you can buy routers out there
 nowadays for 40 or 50 bucks that

0:02:22.420000 --> 0:02:24.960000
 when you bought them brand
 new were $2,000.

0:02:24.960000 --> 0:02:29.420000
 So if you plan on reselling this when
 you're done, you're going to take

0:02:29.420000 --> 0:02:33.660000
 a hit. So if you're spending 500 bucks
 right now on building a rack, you

0:02:33.660000 --> 0:02:37.820000
 might get $150 back when you
 turn around and sell it.

0:02:37.820000 --> 0:02:41.380000
 So just consider that money gone.

0:02:41.380000 --> 0:02:46.000000
 Also, you know, don't just
 take my word for it.

0:02:46.000000 --> 0:02:49.820000
 Before you do any of this stuff,
 research a lot of other articles.

0:02:49.820000 --> 0:02:54.100000
 Just Google, build Cisco HomeLab.

0:02:54.100000 --> 0:02:57.560000
 Use those four keywords, build Cisco
 HomeLab, and you will find lots of

0:02:57.560000 --> 0:03:01.480000
 articles on there giving various different
 piece of advice of how to go

0:03:01.480000 --> 0:03:02.420000
 about doing this.

0:03:02.420000 --> 0:03:06.320000
 I would recommend before you lay down
 a single penny, not only watching

0:03:06.320000 --> 0:03:10.300000
 this video, but reading a minimum
 of three other articles.

0:03:10.300000 --> 0:03:13.840000
 Just to get a well rounded advice, make
 sure you hit all the bullet points.

0:03:13.840000 --> 0:03:18.320000
 Then I think you'll be well prepared to
 start your planning and your designing.

0:03:18.320000 --> 0:03:22.340000
 And lastly, this might happen.

0:03:22.340000 --> 0:03:25.720000
 You know, you might have planned as
 much as possible, prepared as much

0:03:25.720000 --> 0:03:29.640000
 as possible, create your spreadsheets,
 and at the end of the day, your

0:03:29.640000 --> 0:03:31.480000
 lab doesn't support something.

0:03:31.480000 --> 0:03:35.500000
 There's some feature that you just overlooked,
 some interfacing neglected

0:03:35.500000 --> 0:03:38.820000
 to buy. Don't beat yourself up.

0:03:38.820000 --> 0:03:40.720000
 Don't bang your head
 against the wall.

0:03:40.720000 --> 0:03:45.240000
 You could go out and buy another piece
 of equipment to supplement your

0:03:45.240000 --> 0:03:46.780000
 rack to support that feature.

0:03:46.780000 --> 0:03:51.360000
 But at that point, if it's just one
 or two things that your rack isn't

0:03:51.360000 --> 0:03:55.180000
 supporting, it might just be more financially
 beneficial for you to rent

0:03:55.180000 --> 0:03:58.820000
 some rack time on INE's rack
 or somebody else's rack.

0:03:58.820000 --> 0:04:03.660000
 Because maybe you can just spend three
 or four hours practicing that one

0:04:03.660000 --> 0:04:08.360000
 feature, and that only costs you maybe
 a hundred dollar investment of

0:04:08.360000 --> 0:04:13.380000
 tokens or something, which is less than
 buying the two or three routers

0:04:13.380000 --> 0:04:17.420000
 or additional two or three switches
 you would need yourself to practice

0:04:17.420000 --> 0:04:19.420000
 that. So consider that.

0:04:19.420000 --> 0:04:23.200000
 Hopefully your home rack will support
 pretty much everything you need,

0:04:23.200000 --> 0:04:26.860000
 but if it doesn't, you can always supplement
 it with rack time somewhere

0:04:26.860000 --> 0:04:30.740000
 else. So Elizabeth asked
 a good question.

0:04:30.740000 --> 0:04:34.960000
 I'm actually going to make this live
 because I want anybody else to weigh

0:04:34.960000 --> 0:04:36.060000
 in on this as well.

0:04:36.060000 --> 0:04:37.980000
 She says she's a Cisco partner,
 so that's great.

0:04:37.980000 --> 0:04:41.740000
 So Elizabeth, that means you've got
 access to iOS, which is awesome.

0:04:41.740000 --> 0:04:44.120000
 You're looking at building a combination
 of routing and switching and

0:04:44.120000 --> 0:04:46.160000
 collaboration home lab.

0:04:46.160000 --> 0:04:47.800000
 What budget would you recommend?

0:04:47.800000 --> 0:04:52.780000
 You don't know the routing and
 switching side very well.

0:04:52.780000 --> 0:04:58.080000
 Okay. So I don't know collaboration,
 so I can't speak to that, so I can't

0:04:58.080000 --> 0:05:01.760000
 really talk to you about what devices
 you'll need to buy to turn this

0:05:01.760000 --> 0:05:07.200000
 into a collaboration rack or how
 much those devices will cost you.

0:05:07.200000 --> 0:05:15.460000
 From a routing and switching perspective,
 just off the top of my head,

0:05:15.460000 --> 0:05:20.160000
 I would say for $600, you should
 be able to buy a printer.

0:05:20.160000 --> 0:05:23.100000
 It's a pretty decent routing
 and switching rack.

0:05:23.100000 --> 0:05:25.780000
 Like a lot of these routers that I showed
 you that we have in our rack,

0:05:25.780000 --> 0:05:33.260000
 like the 2011s and 1841s, you can
 buy those for $50 to $80 on eBay.

0:05:33.260000 --> 0:05:38.640000
 A lot of the switches you
 can buy for $120, $130.

0:05:38.640000 --> 0:05:42.720000
 So I'm just estimating that if you
 buy three switches and four routers

0:05:42.720000 --> 0:05:50.140000
 and the various cables and stuff, you
 should be able to do all of that.

0:05:50.140000 --> 0:05:50.900000
 You should be able to use that in a
 way that has a very robust, rough

0:05:50.900000 --> 0:05:57.120000
 estimate. Somebody else might be able
 to chime in on what additional things

0:05:57.120000 --> 0:06:00.420000
 you'd need for collaboration and
 how much those might cost you.

0:06:00.420000 --> 0:06:04.360000
 If any of those of you who are watching
 have already gone down that path.

0:06:04.360000 --> 0:06:15.620000
 Let's see here. So Mary asks, can you
 get by with just $235.60s and $35

0:06:15.620000 --> 0:06:22.600000
.50? Or would you get rid of the
 $35.50 and get all $35.60s?

0:06:22.600000 --> 0:06:25.200000
 Short answer is yes.

0:06:25.200000 --> 0:06:27.240000
 I think that what you're
 proposing is fine.

0:06:27.240000 --> 0:06:32.920000
 If you have a couple of $35.60s, I'd
 recommend you have at least $2.35

0:06:32.920000 --> 0:06:37.560000
.60s. And then a third switch can
 be pretty much whatever you want.

0:06:37.560000 --> 0:06:41.140000
 But you're going to want at least two
 switches that support your private

0:06:41.140000 --> 0:06:44.380000
 VLANs, your DHCP snooping
 and all that stuff.

0:06:44.380000 --> 0:06:46.280000
 You're going to want at least
 two switches that do that.

0:06:46.280000 --> 0:06:50.260000
 Ideally three, but if you've already
 got a $35.50 or you can get your

0:06:50.260000 --> 0:06:53.520000
 hands on a $35.50, that's fine.

0:06:53.520000 --> 0:06:56.600000
 That'll be fine for your third switch
 because that can still do routing.

0:06:56.600000 --> 0:07:00.420000
 $35.50s can still do your EIGRP
 and OSPF and stuff like that.

0:07:00.420000 --> 0:07:03.720000
 They just can't do some of the more
 advanced security features.

0:07:03.720000 --> 0:07:07.340000
 But if you've got two other switches
 that can, that should be good enough.

0:07:07.340000 --> 0:07:12.580000
 So that's fine. Someone's asking
 about the CCIE level.

0:07:12.580000 --> 0:07:17.800000
 When I was practicing for my CCIE, I basically
 used a rack that was similar

0:07:17.800000 --> 0:07:18.940000
 to what we have here.

0:07:18.940000 --> 0:07:22.420000
 That had four or five routers
 in it and three switches.

0:07:22.420000 --> 0:07:24.380000
 And I found that to be
 perfectly sufficient.

0:07:24.380000 --> 0:07:29.460000
 Now this is, of course, talking about
 the routing and switching CCIE.

0:07:29.460000 --> 0:07:33.960000
 So here at INE, of course, if you log
 into our INE CCIE racks, which I'll

0:07:33.960000 --> 0:07:38.340000
 show you when we get to part two here,
 they're much larger topologies.

0:07:38.340000 --> 0:07:40.960000
 But which is great, gives
 you a lot of flexibility.

0:07:40.960000 --> 0:07:45.560000
 But if you're building your own home
 lab, you don't need to build a home

0:07:45.560000 --> 0:07:49.480000
 lab that's got 10 or 15 routers
 in it and eight switches.

0:07:49.480000 --> 0:07:51.820000
 You know, great if you can.

0:07:51.820000 --> 0:08:00.440000
 But I think for CCIE level, you'd probably
 want an absolute minimum of

0:08:00.440000 --> 0:08:05.160000
 five routers. I can't see being able to
 do some of the more complex filtering

0:08:05.160000 --> 0:08:10.940000
 and summarization and redistribution
 topologies with anything less than

0:08:10.940000 --> 0:08:15.260000
 five routers. And a minimum
 of three switches.

0:08:15.260000 --> 0:08:19.200000
 And keep in mind, if those three switches
 are full multi-layer switches,

0:08:19.200000 --> 0:08:22.020000
 you've basically got a topology
 of eight routers, right?

0:08:22.020000 --> 0:08:24.860000
 Five routers and three multi-layer
 switches, gives you eight routers,

0:08:24.860000 --> 0:08:26.660000
 and you can do all kinds
 of stuff with that.

0:08:26.660000 --> 0:08:28.040000
 I would say that's the minimum.

0:08:28.040000 --> 0:08:31.180000
 And that should be fine for doing all
 of your routing and switching CCIE

0:08:31.180000 --> 0:08:36.660000
 level stuff. Someone's mentioning that
 their V4 CCIE routing and switching

0:08:36.660000 --> 0:08:39.340000
 home lab cost them $2,000.

0:08:39.340000 --> 0:08:44.540000
 So I'd be curious, Howard, if you could
 tell us sort of the quantity of

0:08:44.540000 --> 0:08:48.760000
 routers and switches that you have
 in your lab that led up to that.

0:08:48.760000 --> 0:08:53.180000
 And also, if all that stuff was used,
 or if you bought any of that stuff

0:08:53.180000 --> 0:08:57.160000
 new, certainly new stuff will ratchet
 up the price very, very quickly.

0:08:57.160000 --> 0:09:00.720000
 Michael's got a good point here, so
 I'll make sure this is all visible.

0:09:00.720000 --> 0:09:06.060000
 He says, for Cisco Partners, there is
 the NFR program where you can get

0:09:06.060000 --> 0:09:10.380000
 some devices refurbished from Cisco
 Direct at a steep discount.

0:09:10.380000 --> 0:09:12.600000
 So for those of you who are Cisco Partners,
 that's also something you

0:09:12.600000 --> 0:09:14.540000
 might want to look into as well.

0:09:14.540000 --> 0:09:15.880000
 And yeah, John has a good point.

0:09:15.880000 --> 0:09:19.880000
 If you buy a router as a terminal server,
 that's another router, right?

0:09:19.880000 --> 0:09:22.360000
 Not only do you have that Octo cable
 coming out to connect to the console

0:09:22.360000 --> 0:09:26.960000
 ports, but that terminal server should
 have probably at least, too fast

0:09:26.960000 --> 0:09:28.540000
-eathen it interfaces in it.

0:09:28.540000 --> 0:09:30.720000
 So that's another router that you
 can add into your topology.

0:09:30.720000 --> 0:09:34.720000
 Exactly. $37.50 is great.

0:09:34.720000 --> 0:09:40.320000
 Yes, certainly, if you can have a stack
 of $2.00 or $3.00, $37.50s, now

0:09:40.320000 --> 0:09:42.820000
 you can practice switch
 stacks as well.

0:09:42.820000 --> 0:09:46.720000
 That's also going to require that
 you buy that special stack cable.

0:09:46.720000 --> 0:09:48.640000
 I've never looked
 for that on eBay.

0:09:48.640000 --> 0:09:51.620000
 I'm sure somebody sells
 that used as well.

0:09:51.620000 --> 0:09:54.000000
 So $37.50s, they're a
 little bit pricier.

0:09:54.000000 --> 0:09:58.680000
 So $37.50s even used cost a little
 bit more than $35.60s do.

0:09:58.680000 --> 0:10:02.620000
 So you have to ask yourself, is that
 additional benefit of doing switch

0:10:02.620000 --> 0:10:09.320000
 stacking worth the extra $40 to $60
 per switch that I'm going to spend?

0:10:09.320000 --> 0:10:11.300000
 It's your choice.

0:10:11.300000 --> 0:10:14.160000
 And someone's, Jeremy's mentioning
 the backbone router idea has always

0:10:14.160000 --> 0:10:17.500000
 confused me. What is the purpose
 to serve as a WAN?

0:10:17.500000 --> 0:10:18.900000
 Should this be connected
 to the internet?

0:10:18.900000 --> 0:10:28.780000
 Okay, so here when you log into not just
 I and E's racks, but most companies

0:10:28.780000 --> 0:10:35.500000
 that give you the ability to purchase
 time on their racks usually will

0:10:35.500000 --> 0:10:40.420000
 have at least one router that's
 called a backbone router.

0:10:40.420000 --> 0:10:43.500000
 And the purpose of the backbone router
 is, you know, when you log into

0:10:43.500000 --> 0:10:48.260000
 the rack, you will have access to some
 routers and switches that you can

0:10:48.260000 --> 0:10:48.500000
 print into the rack.

0:10:48.500000 --> 0:10:49.860000
 You can't really much
 do anything on.

0:10:49.860000 --> 0:10:53.780000
 You can configure it, you can wipe out
 the configuration, you can do whatever.

0:10:53.780000 --> 0:10:58.180000
 But they are probably going to want to
 have in the background other routers,

0:10:58.180000 --> 0:11:02.060000
 maybe switches, that you
 don't have access to.

0:11:02.060000 --> whatever.

173
00:10:53,659 --> 00:10:55,491
But they are probably
going to want to have,

174
00:10:55,491 --> 00:11:00,183
in the background, other
routers, maybe switches,

175
00:11:00,183 --> 00:11:01,984
that you don't have access to.

176
00:11:01,983 --> 00:11:03,005
Like in our case.

177
00:11:03,006 --> 00:11:05,519
In our CCNA/CCNP rack.

178
00:11:05,797 --> 00:11:11,527
One of our backbone routers is
configured as a frame relay switch.

179
00:11:11,649 --> 00:11:15,402
So it's always preconfigured
with PBCs, with DLCI numbers.

180
00:11:15,402 --> 00:11:19,553
We don't want you to have access
to that, because that one router

181
00:11:19,553 --> 00:11:23,914
is serving as a frame relay switch
for lots of different racks.

182
00:11:23,914 --> 00:11:27,946
There's five different racks that
all feed into that one frame relay

183
00:11:27,946 --> 00:11:31,131
switch, and so we don't want people
getting in there and messing it up.

184
00:11:31,380 --> 00:11:34,728
There's another backbone router
that's in the rack which is being

185
00:11:34,728 --> 00:11:37,806
used to inject routes into your rack.

186
00:11:37,805 --> 00:11:43,851
So for example, when you're going
through the route workbook,

187
00:11:43,851 --> 00:11:48,126
when you're doing the EIGRP and the
OSPF tasks, you will notice that

188
00:11:48,126 --> 00:11:51,888
once you configure EIGRP and OSPF
all of a sudden magically you're

189
00:11:51,888 --> 00:11:55,885
seeing EIGRP routes, and you're seeing
OSPF routes, because that backbone

190
00:11:55,885 --> 00:11:58,886
router in the background is
injecting that in there.

191
00:11:58,886 --> 00:12:02,412
And we don't want you having access to
that to mess that up, because that's

192
00:12:02,412 --> 00:12:05,052
not only serving your rack,
but other people as well.

193
00:12:05,053 --> 00:12:08,516
So usually the concept of a backbone
router is simply, it's a device

194
00:12:08,516 --> 00:12:12,607
that is untouchable by you, that's
been pre-configured by somebody

195
00:12:12,608 --> 00:12:16,040
else to inject something into your rack.

196
00:12:16,040 --> 00:12:19,030
Now, certainly, if you're
building a home-based lab,

197
00:12:19,399 --> 00:12:21,114
you don't need that concept.

198
00:12:21,114 --> 00:12:23,041
You're going to have access to everything.

199
00:12:23,041 --> 00:12:26,743
So a backbone router is really only
something you would see conceptually

200
00:12:26,743 --> 00:12:29,621
in remote racks that you're logging into.

201
00:12:31,288 --> 00:12:34,102
John asks a good question right here.

202
00:12:34,102 --> 00:12:37,801
How do you switch back and forth
between console access and being

203
00:12:37,801 --> 00:12:39,202
on the actual network?

204
00:12:39,558 --> 00:12:41,788
Two cables are going to
the terminal router.

205
00:12:41,788 --> 00:12:48,799
In my particular case, when I'm
doing it here in my office-- your

206
00:12:48,799 --> 00:12:52,367
laptop has probably a WiFi connection.

207
00:12:52,367 --> 00:12:55,713
I use WiFi here while I'm on
the actual network, and my

208
00:12:55,712 --> 00:12:58,441
console connections via my USB port.

209
00:12:58,441 --> 00:13:03,086
So it's two completely different
interfaces on my laptop.

210
00:13:03,086 --> 00:13:08,461
I'm doing just asking and doing regular
text through the USB port as console,

211
00:13:08,461 --> 00:13:11,327
but all of my frame data, my
Ethernet frames going to the

212
00:13:11,327 --> 00:13:14,481
corporate network are either
going through my Ethernet cable,

213
00:13:14,481 --> 00:13:17,426
which connects to the corporate
network, or via WiFi.

214
00:13:17,426 --> 00:13:19,381
So the two are completely different,

215
00:13:19,381 --> 00:13:21,807
my laptop does not get confused.

216
00:13:23,012 --> 00:13:27,285
John asked, would you advise
purchasing a terminal server over

217
00:13:27,285 --> 00:13:29,222
a console access server?

218
00:13:29,222 --> 00:13:33,286
I'm personally not exactly sure what
the difference is between the two.

219
00:13:33,286 --> 00:13:37,298
In my mind, I've seen people
interchangeably use the term,

220
00:13:37,298 --> 00:13:39,825
terminal server and access server.

221
00:13:40,523 --> 00:13:44,045
Back when I worked at Cisco, in our labs,

222
00:13:44,045 --> 00:13:47,673
our 2509s and our 2511s, we
called them terminal servers.

223
00:13:47,673 --> 00:13:49,203
That's what connected the console ports.

224
00:13:49,203 --> 00:13:52,029
When I came here to INE,
the racks we have here,

225
00:13:52,029 --> 00:13:54,936
they call them access servers.

226
00:13:54,936 --> 00:13:58,462
So, I'm not sure if you're
thinking of something else.

227
00:13:58,687 --> 00:14:00,173
Okay, great, Howard.

228
00:14:00,173 --> 00:14:03,342
So I'll make that visible there. So
Howard had previously mentioned that

229
00:14:03,341 --> 00:14:08,100
his CCIE rack that he built cost
roughly two grand, and right there

230
00:14:08,100 --> 00:14:10,747
he's mentioning what
that rack consisted of.

231
00:14:10,747 --> 00:14:14,157
So for those of you who are watching
this recorded a month or six

232
00:14:14,157 --> 00:14:18,095
months from now, so Howard built a
rack consisting of it looks like

233
00:14:18,094 --> 00:14:23,501
roughly four switches, a couple
3560s, a couple of 3750s.

234
00:14:24,133 --> 00:14:32,346
He had three 1841s, two 3825s,
four 2600 XM. So you basically had

235
00:14:32,346 --> 00:14:35,945
four, five, six. So you had nine routers.

236
00:14:36,210 --> 00:14:39,773
And then you had a 2511
as an access server.

237
00:14:41,386 --> 00:14:44,238
And then a couple of actual racks as well.

238
00:14:44,238 --> 00:14:49,482
So you had nine routers, four
switches and an access server,

239
00:14:49,482 --> 00:14:51,896
and that cost you roughly $2,000.

240
00:14:54,636 --> 00:15:00,777
Alfonzo, I don't have any answer for
you about the CCIE security path,

241
00:15:00,777 --> 00:15:04,488
because I have not pursued that
certification, so maybe somebody

242
00:15:04,489 --> 00:15:07,399
else can chime in on that, but I'm
not sure what hardware you would

243
00:15:07,399 --> 00:15:11,732
need to build a rack for that.

244
00:15:12,956 --> 00:15:19,966
John clarified his question. So John
was wondering, if I want to use

245
00:15:19,966 --> 00:15:25,430
my laptop for two things, if I
want my laptop on the one hand to

246
00:15:25,430 --> 00:15:29,445
be sending actual data into my
rack, maybe I'm using some package

247
00:15:29,445 --> 00:15:32,407
generator software and I want
to send data into my rack,

248
00:15:32,407 --> 00:15:38,154
and at the exact same time I want my
laptop to have actual real internet

249
00:15:38,154 --> 00:15:44,013
access to my DSL modem or
something, how do I do that?

250
00:15:45,363 --> 00:15:49,898
The way I have done it in the past
is I use my hard-wire Ethernet

251
00:15:49,898 --> 00:15:53,746
cable to connect to my rack, and
that's where I did like my package

252
00:15:53,746 --> 00:15:58,278
generation stuff. I use my WiFi
connection to connect to my home

253
00:15:58,278 --> 00:16:02,463
WiFi network, and what you have
to tweak is you actually have to

254
00:16:02,463 --> 00:16:05,742
go into-- let me see here
if I can show it to you.

255
00:16:06,409 --> 00:16:09,425
I can only speak to Microsoft
here, I can't speak to those

256
00:16:09,425 --> 00:16:11,760
of you who are using MACs.

257
00:16:13,193 --> 00:16:16,726
But here, and I think you'll see it,

258
00:16:16,727 --> 00:16:19,510
if I use the command-- let
me expand this a little bit.

259
00:16:19,868 --> 00:16:24,234
If I use the command route print scroll up.

260
00:16:24,234 --> 00:16:28,036
So right now my laptop actually does
have a hard-wired Ethernet connection

261
00:16:28,036 --> 00:16:32,333
into INEs corporate network, and
I also have a Wi-Fi connection

262
00:16:32,333 --> 00:16:33,805
into INEs corporate network.

263
00:16:33,805 --> 00:16:37,991
And you'll see I have two default routes.

264
00:16:38,891 --> 00:16:44,851
So what you'd want to do is, in your
particular case, if my hard-wired

265
00:16:44,851 --> 00:16:49,607
Ethernet connection was going to my
rack, I'd want to make sure that

266
00:16:49,607 --> 00:16:54,085
my default route I only had one
of them, and that my default

267
00:16:54,085 --> 00:16:57,114
route was pointing to my Wi-Fi connection.

268
00:16:57,414 --> 00:17:03,637
So you'd want to use like the route
delete command in DOS to delete

269
00:17:03,637 --> 00:17:06,916
the default route that's pointing
out your Ethernet cable, because in

270
00:17:06,916 --> 00:17:11,567
reality, that's not a valid default
route to get to external networks.

271
00:17:11,566 --> 00:17:13,789
That's only going to your
own internal network.

272
00:17:13,789 --> 00:17:18,630
So as long as you delete that, and
then you might want to add a static

273
00:17:18,631 --> 00:17:23,669
route in DOS into the network you've
got built into your home lab.

274
00:17:23,669 --> 00:17:28,428
And then just keep one single
default route, which is the default

275
00:17:28,428 --> 00:17:31,288
route pointing out your WiFi
connector, which gives you

276
00:17:31,288 --> 00:17:34,019
your actual real internet connectivity.

277
00:17:34,019 --> 00:17:36,158
So that's how you want to accomplish that.

278
00:17:36,577 --> 00:17:39,319
Can't speak to how pricey
a basic voice lab.

279
00:17:39,319 --> 00:17:40,744
That goes back to collaboration.

280
00:17:40,744 --> 00:17:45,509
Somebody else was asking how much
a collaboration lab would cost.

281
00:17:46,206 --> 00:17:49,458
One other question and then
we'll take a break here.

282
00:17:49,458 --> 00:17:53,047
So Steven's asking, is it worth
mentioning talking about an IP power

283
00:17:53,047 --> 00:17:56,824
distribution unit, so you
can power cycle remotely?

284
00:17:57,483 --> 00:17:58,854
That's really your choice.

285
00:17:59,781 --> 00:18:01,650
You have to ask yourself this question,

286
00:18:01,650 --> 00:18:06,473
do you foresee that once you've
got this lab built and running in

287
00:18:06,473 --> 00:18:10,011
your house - in your bedroom, your garage,

288
00:18:10,011 --> 00:18:14,489
or wherever it's going to be -
do you foresee yourself needing

289
00:18:14,489 --> 00:18:16,213
to access this lab remotely?

290
00:18:16,213 --> 00:18:19,773
Do you foresee yourself working
from your actual office

291
00:18:19,773 --> 00:18:21,755
and needing to get into this lab?

292
00:18:21,755 --> 00:18:24,372
If the answer to that is yes, then yeah,

293
00:18:24,371 --> 00:18:29,021
you'll probably want to get an IP
power distribution unit so you

294
00:18:29,021 --> 00:18:31,334
can remotely power cycle  your equipment.

295
00:18:31,486 --> 00:18:33,439
If you don't think you're
ever going to need that,

296
00:18:33,439 --> 00:18:36,423
if you say to yourself, Well, the
only time I'm ever going to access

297
00:18:36,423 --> 00:18:38,591
this equipment is actually when
I'm right there physically in

298
00:18:38,591 --> 00:18:41,783
front of it, then no, you
obviously wouldn't need that.

299
00:18:42,549 --> 00:18:46,698
The other thing is, if you are
going to access your lab remotely,

300
00:18:46,698 --> 00:18:52,341
now you've got to think about, Okay,
my terminal server is probably

301
00:18:52,341 --> 00:18:54,999
now going to become a necessity.
It's no longer optional,

302
00:18:54,999 --> 00:18:58,371
I'm going to have to have one. And
that terminal server is going to

303
00:18:58,371 --> 00:19:05,472
have to have a public IP address so I
can get to it from the outside world.

304
00:19:05,472 --> 00:19:08,863
That opens up a whole other
ball of worms, is how you get a

305
00:19:08,863 --> 00:19:12,910
public static IP address on your
terminal server so you can get to it

306
00:19:12,910 --> 00:19:17,517
from your office, or from when you're
vacationing in Hawaii or whatever.

307
00:19:17,517 --> 00:19:21,240
So that's also something you'd have to
think about is how to accomplish that.

308
00:19:21,240 --> 00:19:26,013
[music]