But they are probably going to want to have,
in the background, other routers, maybe switches,
that you don't have access to.
Like in our case.
In our CCNA/CCNP rack.
One of our backbone routers is configured as a frame relay switch.
So it's always preconfigured with PBCs, with DLCI numbers.
We don't want you to have access to that, because that one router
is serving as a frame relay switch for lots of different racks.
There's five different racks that all feed into that one frame relay
switch, and so we don't want people getting in there and messing it up.
There's another backbone router that's in the rack which is being
used to inject routes into your rack.
So for example, when you're going through the route workbook,
when you're doing the EIGRP and the OSPF tasks, you will notice that
once you configure EIGRP and OSPF all of a sudden magically you're
seeing EIGRP routes, and you're seeing OSPF routes, because that backbone
router in the background is injecting that in there.
And we don't want you having access to that to mess that up, because that's
not only serving your rack, but other people as well.
So usually the concept of a backbone router is simply, it's a device
that is untouchable by you, that's been pre-configured by somebody
else to inject something into your rack.
Now, certainly, if you're building a home-based lab,
you don't need that concept.
You're going to have access to everything.
So a backbone router is really only something you would see conceptually
in remote racks that you're logging into.
John asks a good question right here.
How do you switch back and forth between console access and being
on the actual network?
Two cables are going to the terminal router.
In my particular case, when I'm doing it here in my office-- your
laptop has probably a WiFi connection.
I use WiFi here while I'm on the actual network, and my
console connections via my USB port.
So it's two completely different interfaces on my laptop.
I'm doing just asking and doing regular text through the USB port as console,
but all of my frame data, my Ethernet frames going to the
corporate network are either going through my Ethernet cable,
which connects to the corporate network, or via WiFi.
So the two are completely different,
my laptop does not get confused.
John asked, would you advise purchasing a terminal server over
a console access server?
I'm personally not exactly sure what the difference is between the two.
In my mind, I've seen people interchangeably use the term,
terminal server and access server.
Back when I worked at Cisco, in our labs,
our 2509s and our 2511s, we called them terminal servers.
That's what connected the console ports.
When I came here to INE, the racks we have here,
they call them access servers.
So, I'm not sure if you're thinking of something else.
Okay, great, Howard.
So I'll make that visible there. So Howard had previously mentioned that
his CCIE rack that he built cost roughly two grand, and right there
he's mentioning what that rack consisted of.
So for those of you who are watching this recorded a month or six
months from now, so Howard built a rack consisting of it looks like
roughly four switches, a couple 3560s, a couple of 3750s.
He had three 1841s, two 3825s, four 2600 XM. So you basically had
four, five, six. So you had nine routers.
And then you had a 2511 as an access server.
And then a couple of actual racks as well.
So you had nine routers, four switches and an access server,
and that cost you roughly $2,000.
Alfonzo, I don't have any answer for you about the CCIE security path,
because I have not pursued that certification, so maybe somebody
else can chime in on that, but I'm not sure what hardware you would
need to build a rack for that.
John clarified his question. So John was wondering, if I want to use
my laptop for two things, if I want my laptop on the one hand to
be sending actual data into my rack, maybe I'm using some package
generator software and I want to send data into my rack,
and at the exact same time I want my laptop to have actual real internet
access to my DSL modem or something, how do I do that?
The way I have done it in the past is I use my hard-wire Ethernet
cable to connect to my rack, and that's where I did like my package
generation stuff. I use my WiFi connection to connect to my home
WiFi network, and what you have to tweak is you actually have to
go into-- let me see here if I can show it to you.
I can only speak to Microsoft here, I can't speak to those
of you who are using MACs.
But here, and I think you'll see it,
if I use the command-- let me expand this a little bit.
If I use the command route print scroll up.
So right now my laptop actually does have a hard-wired Ethernet connection
into INEs corporate network, and I also have a Wi-Fi connection
into INEs corporate network.
And you'll see I have two default routes.
So what you'd want to do is, in your particular case, if my hard-wired
Ethernet connection was going to my rack, I'd want to make sure that
my default route I only had one of them, and that my default
route was pointing to my Wi-Fi connection.
So you'd want to use like the route delete command in DOS to delete
the default route that's pointing out your Ethernet cable, because in
reality, that's not a valid default route to get to external networks.
That's only going to your own internal network.
So as long as you delete that, and then you might want to add a static
route in DOS into the network you've got built into your home lab.
And then just keep one single default route, which is the default
route pointing out your WiFi connector, which gives you
your actual real internet connectivity.
So that's how you want to accomplish that.
Can't speak to how pricey a basic voice lab.
That goes back to collaboration.
Somebody else was asking how much a collaboration lab would cost.
One other question and then we'll take a break here.
So Steven's asking, is it worth mentioning talking about an IP power
distribution unit, so you can power cycle remotely?
That's really your choice.
You have to ask yourself this question,
do you foresee that once you've got this lab built and running in
your house - in your bedroom, your garage,
or wherever it's going to be - do you foresee yourself needing
to access this lab remotely?
Do you foresee yourself working from your actual office
and needing to get into this lab?
If the answer to that is yes, then yeah,
you'll probably want to get an IP power distribution unit so you
can remotely power cycle your equipment.
If you don't think you're ever going to need that,
if you say to yourself, Well, the only time I'm ever going to access
this equipment is actually when I'm right there physically in
front of it, then no, you obviously wouldn't need that.
The other thing is, if you are going to access your lab remotely,
now you've got to think about, Okay, my terminal server is probably
now going to become a necessity. It's no longer optional,
I'm going to have to have one. And that terminal server is going to
have to have a public IP address so I can get to it from the outside world.
That opens up a whole other ball of worms, is how you get a
public static IP address on your terminal server so you can get to it
from your office, or from when you're vacationing in Hawaii or whatever.
So that's also something you'd have to think about is how to accomplish that.
[music]