I've been hiding something
from you, A secret project, actually a secret room that I've been
building for a while now, almost a year, and I think I'm finally ready to
show you. I'm so excited. Austin, pull the curtain. Wait, wait,
wait. Hold up. Before I show you, let me give you a bit of background
and why this is so amazing. I'm currently right now in my new
studio. Now I know I owe you guys a tour, but it's not quite ready yet. But
you've seen glimpses here and there. My other studio, kitchen, the
living room, the video editing room. Now I used to be in a tiny little bedroom. That's where I filmed every video
amidst the chaos of my big family. I have six daughters and
while that was pretty crazy, the crazier part was
where my server room was. Venture passed my master bathroom with
the toilet right there is my server rack racks with all of my routers
and switches and servers, constantly tripping the breaker,
making my closet too hot, making my wife too mad. It just wasn't a
great situation. I had to do something. So when we had our sixth daughter, my
wife said, you can't be here anymore. So I bought a new house and finally I get
to build the server room of my dreams. No more dirty, dusty
bathroom closet. No, no, A dedicated space built for my stuff.
Are you ready to see it? Austin? Now you can pull the curtain. So now my server room is finally
totally not ready. I mean, look at it. It's messy. The cabling is embarrassed. I can't believe I'm even showing you
this. Nothing is organized. And look, I'm still building a rack,
but it's beautiful I isn't it? I missed all the chaos. I've
got two internet connections, five gig and one gig internet. I have a dedicated AC unit to keep
that server room nice and cool. And my favorite part, we just added this, a glass wall so I can show the entire
thing off from my other studio. This is my favorite thing, but it's still
not done. I'm still building the rack, which will house my new 45
drive servers. So you know what? Lemme take you on a journey, A journey of how I'm turning my
server room into kind of a cloud. So first we'll start with the rack
build, which I forgot how to build. I'll probably have to build
it three times foreshadowing. Then we'll open up the servers and see
what's inside because I can't wait to see what's inside. What's a C P U?
What's the ram? They are beast. I can't wait to see. And
then we'll rack them, which is super hard because
they are extremely heavy. And then this is kind of as S M R. We'll install the terabytes of hard drives
that 45 drives gave me. And finally, probably the hardest part,
let's configure the networking. Each of these servers has
four 10 gig interfaces, which means I need a pretty
big 10 gig switch. I found one, but I have no idea how to configure it
because it's micro tick and I'm a Cisco man, so come watch me struggle. Let's go
on an adventure. Get your coffee ready. I've got mine. I'm already
tired. Let's do this building. This rack was the worst. I built
the exact same rack two years ago. I forgot how to build it.
And now here we are again. But I'm sure if I followed the
instructions, I'll be fine. It shouldn't take me more than an hour.
But I had a few interruptions like Ted. Number two needed help with her
headphones, so I had to fix those. Auto number one, needed help
with math. What do you mean math? This is pretty much how
my days go every day. But finally I got two sides built up. The instructions were
actually pretty clear. I aced this or so I thought
foreshadowing, but again, things are going pretty good.
I mean, I was pretty cold. Hopefully my coffee will
keep me warm. Coffee break, but also I was starting to run out of
room. I couldn't move the rails around. I think I scratched the wall up pretty
good and maybe even the glass maybe scratched my. Wall. I'm not sure. I really hope not and knocked
off my light thing and severely scoped. Up my wall, but I figured it out
and I even big brained some stuff. The instructions told me to
flip it, but I'm like, no, I'm going to do steps three and four
first because I'm smarter than the instructions. No, I'm
not. But I thought I was. And even though I kept losing my
screwdriver, I finally did it. I built the stinking rack that was way
easier than I thought it'd be wrong. That's what I did. I made a mistake
and I had to redo the entire thing. I installed them in reverse backwards.
I failed. So before I continued, I decided to get more
coffee, but not good coffee. I only deserved Qre good
coffees for winners. So after I lost my screwdriver
again and found it again, I built the rack again because it ain't
government work unless you do it twice. Larry gge or Gary or
Jerry, you never know. But finally I did it and I can finally
do the rack dance now before we start the build. Why all these
servers? Why is server room? I'm trying to do some bigger projects
and use new exciting things like Kubernetes and DevOps and C I C
D pipelines, all these buzzwords, but at the same time, I don't want to get hacked and that's
where the sponsor of today's video comes in. Contrast security. They're going to help protect me from
me and all my terrible, terrible code. I am not a developer, but I pretend
to be a lot. Thank you Chad, g p t. And while I have a lot of tools
to produce a lot more code, what I don't know is if my code is
secure or if my containers are secure pipeline I'm using
secure. I don't know that. So this is where contrast
security comes in. You've got a number of products to
help you with your secure coding, but the one I want to focus on
right now is contrast. Assess. This sucker will meticulously look over
all your code as you're writing it. It embeds automated security
testing right into your pipelines. So you're not waiting for a security
test, it's already happening. It's called an IAS or interactive
application security testing. And it's going to find
your vulnerabilities, it's going to throw it right in your face. It doesn't matter where you're coding
containerized apps and Kubernetes, like I'm going to do the
cloud Serverless functions, APIs and Contrast Assess will provide
simple guidance right in your I D E so you can fix those issues immediately,
not later during review processes. And you find out your code sucks
and you have to redo everything. No, don't do that. Ship good secure
code the first time. Now again, I want to hit this home. Developers need this because we're relying
more and more on ai, Chad, b t cloud, G B T, whatever it is, and we don't know if the code
they're giving us is secure. And while you probably shouldn't trust
ai, you can trust contrast security. They're an industry leader. They've been doing this for a while
and they're trusted by a lot of big companies. So keep writing
your code crazy fast, but do it securely with contrast.
Check it out, link below, they'll give you a demo. And thanks again to contrast
for supporting this channel
and providing awesome security tools with my rack built.
Now let's bust these things open. See what's inside. I think I just pop it off or
slide it forward. Oh, there we go. Just comes off like this. We'll
add our drives here in a second. I want to see what's making this thing
tick. I think the goodies are over here. Oh, so a lot of things going on in
here. Let me flip this guy around. The C P U is a zon silver
42 10, 10 cores, 20 threats, the ram, let me go gorilla
style here for the ram. We have 4 32 gig sticks.
There's one over there. There he is giving us 128 gigs of
ram. And this is just one server. These guys right here with the
heat sinks and looking all crazy. I believe these are our
storage controllers. And then just above them we
have our two 10 gig nicks. And you can see here that
they're actually not ethernet. They're SFPs four 10 gig SS F P ports
and they're right at the top here. I have dual power supplies. And then right up here I've
got 2 250 gig SSDs running my oss. Now that's the specs.
Let's pop in some hard drives. Oh my gosh, I just flicked my screws
everywhere. I really screwed up, dude. I've got six kids. The dad jokes are
plentiful. Now I almost made a mistake. I was about to put the hard drives
in first before I racked it. After the whole rack
debacle, I learned my lesson. I looked at the instructions
and I followed them to a
T. Thank you. 45 drives. So then me, Austin, and Michael, we racked
the servers. Did it pretty fast too. Alright. We're about to move the
servers, me and Austin here. Let's. Do it. We're going to take
this from here to there. So actually I can carry it in. There. All right. The good news is that this is
only one of four right here. One down baby. So let's unbox
and get the other one going. What side do you have gun? L. All right, I've got R. That's what we're
going to aim for is the middle of 30. In the middle of 29. Got it. Perfect.
Now we're going to pull this guy out. Wait, where is it? Oh, there it's now we're going to screw
him onto the side of the server here. I will be Austin, I will be
to Austin. I will be Austin. Done. Dang it. Okay, there we go. I'm way faster than Austin and now
it's been an entire day. I'm exhausted. It's like six o'clock. My wife's texting
me when you come home for dinner. I'm like, hold on honey, I
got to do one more thing. I've got to install these hard drives, these terabytes of hard drives and
my 45 drive servers. I have to do it. I've been looking forward to this all
day. So I set the cameras up, A S M R. This is so fun. I installed the SSDs, the HDDs and each server and
because I put them super high, my camera couldn't reach. The
angles get weirder and weirder, but I still think it looks
nice. And yeah, that was again, probably the hardest part you didn't
see Most of that was me having to unwrap each hard drive. I was so tired
of putting those hard drives in. It was a long day. I hit my head, hurt
like crazy, and then I hit it again. I was that tired and by the end
of it I was just, was toast. But it's finally done. It's time
to go home, but I did everything. It looks good. Well, not
everything I had the switch to do. I'll save that for another day. Now. I had to find a switch that could handle
the insane networking requirements of my servers. My four servers. Each server has four 10 gig S F P
interfaces giving me 16 interfaces total. Also two 10 gig ports per gateway. That brings me up to 2010
gig interfaces, SS F P. And this switch had to be fast enough
to handle all the back plane traffic. And this is where micro tick comes
in. They had an amazing switch. The c r s 3 26 dash 24
s plus two Q plus rmm. I know it's an amazing name. And
this switch is kind of amazing. It costs me about 500 bucks. It
has 24 10 gig S F P interfaces. It can handle 320 gigabits per
second of non-blocking traffic. Non-blocking meaning
there's no bottlenecks. Even if I'm using all the ports up to
320 gigabits per second, it's perfect. But micro tick is different. Like I said,
I'm a Cisco man, I have to learn that. Now. Full transparency, I
already have a micro tick switch, but I configured that a while ago and I
don't remember anything about it because I'm dumb and I didn't
document any of the process. I was just excited about configuring
it and making it work. Don't do that. Documentation is key. If you learn
documentation right now in your career, you'll be amazing. So I unbox the
microtech switch looks pretty good. It's kind of small actually, and
kind of light two power supplies. I don't know how they're doing
it now. Look at the instructions, it's not too bad. Plug it into my laptop. Set the IP address on my laptop to
access it. Go to the web interface, set my password, set the management interface to receive
D H C P and we're off to the races. Then I installed the switch, man, I forgot
how much I love cage nuts. I just do. I don't care what people say. And I only
dropped one screw, so I'm pretty good. Also, I could not wait to plug
in all the servers to my switch. So I went ahead and did that. I meticulously unwrapped all of my
SS F P cables and plugged them in. This was nice. Similar to
plugging in an ethernet cable. It's one of my favorite sounds, but my fingers almost died from being
frozen and untwisting twisty ties. But hey, it was kind of fun. I got a little visitor asking me for
a snack and she did a little dance. I go rack this sucker, plugging the
power, plugging the ethernet cable. I string it across my server
room, boot that sucker up, see what IP address I got in my
dream machine. Well, actually no, my dream machine decided it didn't
want to be a router for a moment. I had to reboot that for a while
and come back the next day. But finally I got an IP address on this
and I can connect to it and configure it. So far it's not been too bad. Now here's why Micro tick is weird and
let me kind of show you what I'm going to do. I've got two network racks. Rack
number one has all my current stuff, my main router, which is my dream machine servers and my
switch where all my workstations in my studio connect to. So obviously I would need to connect
rack number two to rack number one. Now as I said before, I do already have one Microtech switch
that I configured and I don't remember how I did it, but it's this guy
right here. It's a smaller one. What's the model? It's c R s three
12 dash four c plus eight xg. Pretty awesome. So one goal is to connect
my two micro tick switches together. I'll throw over two 10 gig connections
and I'll bond these two interfaces into an Ether channel. So they pretty much become one interface
and they'll also be a what's known as a trunk, which if you're
familiar with networking, a trunk will carry traffic for multiple
VLAN interfaces. And if you're like, what's all that? Go check out my C N
A series, I'll walk you through it. And then of course I'll have my 4 45
drive servers and I'll cable these up. Now each of the four interfaces I'll
also make into a bond an ether channel. Now I'm saying bond because I know
that's what Micro Tick calls their Ether channels. They call 'em bonds and that's just one
of the fun things I had to struggle with and learn. I will also make each one of these
bonded interfaces a trunk because I want my 45 drive servers to be
able to facilitate multiple
networks, multiple VLANs. So that's the two goals. And actually I'll probably end up doing
the interfaces on the 45 drive servers first. So that's goal one. And of course the trunk to my
other microtech switches Goal two, and I got a challenge for myself.
I don't want to use the gui. Microtech actually has a really
amazing web gui, a web interface. It's going to be harder,
but I love command line. Now the first big thing I hit is a show
interfaces or show anything is not what they do. They say print. So if I
want to print a list of interfaces, I would say forward slash interfaces
print. Not a crazy thing to learn. It's fine until I got
to the idea of VLANs. Microtech does these so weird. And where it really confused me was
the idea and concept of a bridge. I'm not going to go too deep because
this is not a microtech video, which just know and microtech speak. A
bridge is essentially a vlan kind of, but not really. It can also
be thought of as an S V I, and I'm speaking like Cisco language
now. It performs those functions, but it also does a bit more, we'll talk more about this
bridge thing here in a second. This definitely tripped me up and was
one of the main things I struggled with. But let's go ahead and start configuring. The first thing I wanted to do is get
the bond out of the way. The channel. Now here, I'm not trying to teach you, which just kind of illustrating the
differences between maybe a Cisco switch and a micro dig switch. So I started
out with, okay, I want to create neath, the channel between four
interfaces. That was my first goal. I looked up the documentation,
figured out this command will do it, but then it told me these interfaces
were already part of a bridge. Okay, what's a bridge? A bridge is kind
of like a vlan, but it's not a vlan. It's more like an S V I. But it's more,
it's almost like its own little switch. When I say a VLAN is like
a switch in Cisco world, I'm like a switch a bridge and micros
is like a whole stinking switch. It's strange. So I had to first remove
these interfaces from that bridge, which by default it was part of that. And it was weird because I had to print
the bridge ports and then remove them based on their indexes. And these
indexes changed as I removed each port. Kind of dumb. But we did it, folks.
We did it, we figured it out. Then I could create my
bond, which wasn't too bad. It made sense using 8 0
2 0.3 ad, which is LAC P. Basically ether channel traffic,
low balancing industry standard. And now I have my bond,
my one logical interface, and I created four of 'em for the
Hogwarts house as Griffindor, Hufflepuff, Raven Claw and Slitherin. Of course,
now time to add them to a bridge. Now it could create another bridge.
You could have multiple bridges, but according to micro tick documentation, my particular switch can only have
hardware offloading on one bridge. I want hardware offloading. I'm
imagining that's probably the asics, which make your packet switching
go crazy vast. It's specialized. So the bridge already exists. So
instead of using the ad command, I use the set and that'll be a
common theme throughout this. I set the name to platform
nine, three. Four, of course platform nine
and three quarters. And now I'm going to add
my bonds to this bridge. Whereas before they were added
as individual interfaces. Now they're being added as a bond.
With this command. I added them, making sure HW equals yes
is indeed equaling yes, which enables hardware offloading.
Now how do I make them a trunk? In Cisco world, it actually is kind of
more complex interface trunk 8 0 2 0.1 Q, the whole shenanigans and craziness. Here you're going to change the bond
interface by using the set command and you're going to set the frame types to
allow only tag VLANs. Now this command, we're allowing all VLANs. We're
not restricting any type of VLANs. We don't specify any,
we're just allowing all, we turned it into a trunk
and that's all we had to do. It felt kind of unfinished, kind of
weird, but I think we did it by default. The native VLAN is one, and it's just
by default. If I print the detail, P V I D equals one. So now I've set
up my eighth, the channel, my bonds, I've added them to my bridge
and I've made them trunks. Now let's do the same thing for the
connection to my micro tick switch. My other one, same story really
just doing two interfaces. I'm going to bond them doing that now, add 'em to the bridge and
then turn them in into trunks. Now that begs the question, we saw how we can create a
trunk that carries all VLANs, but how do we do an access port that
only allows one vlan like connecting my computer to the switch,
which I'm going to do. And here it's all about setting
the P V I D in the frame type. I'm saying the P D I D or Port V i D is
equal to seven and it can only accept on the frame type untag VLANs, and then
I'll add in priority VLANs as well. This was so weird, but that's with the
configs now. I haven't tested it yet. Now I know it's working On
my other microtech switch, I'll look at the config and that's
kind of what's there and it's currently working for me. That's what I'm currently
using right now for my computer. Fingers crossed, I hope
it's going to work.
