Configure Layer 2 Switching on Junos

0:05If you follow my content at all in the JNCIA certification

0:09playlist that we have here in CBT Nuggets,

0:11you heard me say very surprisingly,

0:13that layer 2 was not part of the JNCIA certification.

0:17I mean it's a critical part of networking.

0:19You oftentimes learn layer 2 before you learn layer 3.

0:23How does communication within the same network

0:25work before we move on to inter-network communication?

0:29This is kind of the gist of why Juniper

0:31chose to push layer 2 into the JNCIA certifications.

0:35Here's why.

0:36Because at the end of the day, all Juniper platforms

0:39perform some form of Ethernet switching, even the routers

0:43and even the firewalls.

0:44Now throughout this playlist, we're

0:46going to figure out that even though they all run Junos,

0:48that all the exact same operating system,

0:50they all approach switching just a little bit differently.

0:53The commands from one platform to the next

0:56are just different enough to where they

0:57get their own unique commands.

0:59MX series routers for instance, do not

1:01perform the exact same function than an EX series switch does.

1:06So that kind of explains why then the MX series router

1:09may approach layer 2 in switching

1:11just a little bit differently than an enterprise grade

1:13switch.

1:14So what we're going to do throughout this skill

1:16is actually introduce, what switching does.

1:18How does switching actually work,

1:19and how does Juniper approach it.

1:21Then we're actually going to deploy

1:22layer 2 switching solutions on each

1:24of the different platforms.

1:25We're going to cover EX series switches, which are primarily

1:28used in the enterprise.

1:29We're going to cover EMX routers which are primarily

1:32used in service providers and QFX series

1:34switches, which are primarily used in the data centers.

1:37Now if you're here because you want to follow along,

1:39let me just tell you right now, there's

1:41content in the JNCIA certification playlist, where

1:44we talk about how to go about building a home lab,

1:47whether virtual or physical.

1:49And all of those platforms, whether physical or virtual

1:51will be covered throughout this content.

1:53So, you may want to jump back to the JNCIA playlist real quick,

1:56and then see like, OK he's using an EX series switch.

1:59Where did he go to get an EX switch?

2:01It was eBay like at the EX 22,100

2:03because they're the most affordable.

2:05But go check that content out if you're

2:06really interested in following along and labbing

2:09your own layer 2 switching environment with a Junos

2:12operating system.

2:13So with that being said, in the next Nugget we're

2:15going to cover, what is the entire point of layer

2:172 in switching?

2:18And how does Juniper approach layer 2 and switching?

2:20Then we're going to follow that up

2:22with all of the configuration items

2:23creating VLANs, creating access and trunk ports,

2:26and then creating switch virtual interfaces.

2:28Get ready because it's going to be a blast,

2:30and I'll see you there.

0:05So now it's time to talk about layer 2 switching

0:08and get refreshed on what the entire point of layer 2 is.

0:11We're going to cover what a VLAN is.

0:13What is an access port versus a trunk port and any 2.1 queue

0:16tagging and then what is a switched virtual interface.

0:20All of this is kind of a refresher course

0:22because Juniper's expectation, even though it hasn't

0:24been covered in a certification up to this point,

0:26is that you have a little bit of experience

0:28in this type of technology.

0:30And what the JNCIS wants you to know

0:32is how do the different Juniper platforms

0:34approach layer 2 switching.

0:36But before we just dive in and I just assume

0:38you already know layer 2.

0:40Let's talk about what layer 2 switching is all about.

0:43Let's go.

0:43This is honestly, one of my favorite

0:45topologies that I've ever whipped up

0:47for any of our content here on CBT Nuggets.

0:48And before you freak out and say, wait a minute,

0:50I don't see Juniper devices.

0:52That's OK, we're just talking about kind of design

0:55right now in the point of layer 2.

0:57And in fact, this topology was actually

0:59created for a Cisco Enterprise design certification

1:02that you could actually learn how enterprises should be laid

1:05out and how traffic should flow through an enterprise that's

1:08the entire point of the certification.

1:10And what's very interesting is that so much

1:12of that was learned in that exam is actually

1:15applicable to stuff in really any certification.

1:17Now Juniper does have a design track

1:20and we're not really going to dwell too much on design itself

1:23right now because there's design content out there

1:25for those exact things.

1:26We're just trying to refresh ourselves

1:28on the point of layer 2 and this is a great topology

1:31to just get refreshed on layer 2 before we

1:34dive into the actual Juniper hardware themselves

1:36and start configuring things.

1:37So getting started, let's start off

1:39with just one of these little box here.

1:41I'm going to zoom in quite a bit and let's

1:43just focus on the yellow section here in the screen.

1:47Pretend for a moment this yellow section is say,

1:49our accounting department on a large enterprise campus

1:53maybe even like a university campus

1:54and they've got a bursar's office and a finance office.

1:57And all of that exists in this one building that's

2:00what we're looking at here and we're

2:01kind of looking at this yellow section

2:03is a building that houses all of our accounting staff.

2:06Then let's say we've got four computers just

2:08these basic four computers attached in.

2:11Let's say we've got Bob, and Lois,

2:14and let's say we've got Knox, and Keith,

2:17are all attached here in this little area.

2:20We see them that they plug-in to a switch just like

2:23so on each one of these sections here

2:26and this section is called the access layer.

2:29It's very cleverly called the access layer

2:31because this is where our devices are, our end-users gain

2:34access into the network.

2:36Now without dwelling too much on this,

2:38we see how these switches can be linked up

2:42to another set of switches.

2:43This is actually the layer 3 switch symbol here and then

2:47they all kind of interact with each other.

2:49They all kind of interconnect.

2:50So for instance, if Bob wanted to talk to Keith,

2:53Bob's traffic would go something like this.

2:56It would come in to switch 18, and then down to switch 20,

3:00and then out towards Keith.

3:01This is where the whole switching thing comes into play

3:04and this is also where it kind of gets into enterprise design

3:07because this is kind of a bit of a moving target these days.

3:10We'll talk more about why in just a second.

3:13If we pretend for a moment that all of my accounting staff are

3:16all on the exact same network like 192.168.3.0/24,

3:22Bob would then basically be able to communicate directly

3:25to Keith without having to pass through a router because this

3:29is the entire point of layer 2.

3:32Layer 2 is all about how two devices that

3:35are on the exact same network can communicate directly

3:38to each other using frames.

3:41If you recall for a minute what the entire point of the OSI

3:44model is, it's really to logically define

3:47how routing and networking decisions can

3:49be made one step at a time.

3:51And as the decision itself gets a little more complicated,

3:55we just introduce some more layers into the mix

3:58so you can make even further or more accurate decisions.

4:00The cool thing about layer 2 is that because we're

4:03on the exact same network, we don't

4:05have to add too much complexity in it.

4:07For instance, Bob's traffic that speaking directly to Keith

4:10never has to pass through a router.

4:13It can just pass through a switch

4:14because the entire point of a switch

4:16is to send traffic within the same network to each other.

4:20So how does it do this?

4:21This introduces one of the most major concepts in all

4:24of switching and that's how broadcast work

4:27and why switching and routers really exist.

4:29When it's time for, let me clean up the screen for just a moment

4:32and we'll just highlight Bob and Keith.

4:34When it's time for Bob to communicate directly to Keith

4:37and we know that we're on the exact same network,

4:39because maybe Bob looks at his IP address and sees 192.168.3.5

4:45and Keith is 192.168.3.6, I'm going to write 6 here

4:48for simplicity's sake.

4:49Bob says, Oh, you're on my same network

4:51I can see that because the address

4:53that I'm trying to reach is clearly on my same network.

4:56What I'm just going to then do is just

4:58shout throughout my entire network hey,

5:01how do I get to you.

5:02Specifically, it uses address resolution protocol or ARP

5:06for short.

5:07And it literally asks the question

5:08or at least if you do a Wireshark packet capture,

5:10it says who has 192.168.3.6 and this all takes place in Layer 2

5:19within the switch itself.

5:21The payload asks this question, who has that?

5:24Because what they're really asking

5:25for is what is your Mac address so that I can send

5:29my traffic directly to you.

5:32It takes this IP address and maps it to this Mac address

5:36so that way we know if we're ever

5:38trying to reach this IP address, we can just reach it directly

5:41by its Mac address.

5:42So it asks this question, who has

5:44192.168.3.6 expecting a reply of, I have it, here's

5:49my Mac address.

5:50And it becomes a broadcast frame because it sends this

5:54to the broadcast IP address and the broadcast Mac address.

5:59If I turn on Wireshark for even a brief moment on my computer,

6:02I'm just going to leave it sitting for just a second so it

6:05grabs some broadcast frames.

6:07There it is, I see a bunch of ARP requests right there.

6:09Let me zoom way on in so we can see it.

6:13Do you see this one right here?

6:14This is my ARP request, I got my mouse on it

6:16right now for whatever reason my pin isn't letting me do it.

6:18We can see that my source address is asking,

6:21is this ubiquiti router is asking, hey,

6:24who has 10.21.156 tell 10.10.21.1.

6:29The destination is the all bits broadcast address

6:33of ff,ff,ff,ff,ff,ff, that's right.

6:36When we send in a broadcast frame

6:38into the network destined for ff, ff, ff, ff,

6:42this frame is then told you need to go

6:45to everyone that's communicating within the same network.

6:48This is oftentimes referred to as a virtual LAN.

6:52So in the case here, when Bob's computer is

6:54goes to speak to Keith's computer here,

6:57it's going to send in a broadcast frame,

6:59an ARP request asking, how do I reach you at your address?

7:03Keith's computer will reply directly back to Bob

7:06because it has seen the source Mac address

7:09and it knows who is asking specifically for this question

7:12and where do we need to go from there.

7:14So Bob and Keith now know each other's Mac address

7:17after ARP has been handled but very

7:19interestingly all the switches in the middle do too.

7:23As a frame comes in when it's sourced from a Mac address,

7:27the switch remembers on this interface,

7:29I learned about this Mac address so it knows exactly

7:32which interface each Mac address is connected to.

7:35That way when further flows of traffic

7:37need to happen between Bob and Keith,

7:39all of the switches along the path

7:41remember where the source Mac address was learn from

7:45and if it receives a frame destined to that Mac address.

7:48It knows which interface to send it

7:50which makes this whole process very, very quick.

7:53Now taking it even a step further,

7:55switches are built with something

7:57in there interfaces called ASICs that's

7:59application specific integrated circuits

8:02and it's all about making this decision of how to forward

8:05a frame even quicker.

8:07And this is one of the reasons why switches are typically

8:09more expensive than routers.

8:11Just a whole lot of R&D has gone into developing

8:14the silicon in order to making these ASICs run blazing fast

8:17and this is one of the ways that Juniper really

8:20prides itself on how performance is switching platforms are.

8:24So this is how devices that are on the same network

8:26would communicate directly to each other.

8:28It's all about finding out where the neighbor is.

8:31What their Mac address is and then the switches

8:33learn about each of these devices as communication

8:36starts to flow back and forth.

8:38But what happens if all of a sudden

8:40we have too many devices.

8:42You see if everybody is sending in broadcasts all the time

8:46then our devices get choked up.

8:48And this is one of the reasons why we limit the number

8:50of devices on our subnets to a /24.

8:55The /24 limits it to basically a broadcast domain meaning,

8:59how many devices can broadcast within this entire domain

9:03to 255, 254 devices really and that's been just a healthy

9:07number for pretty much the entire length or duration

9:10of ethernet itself.

9:12So if for instance, maybe Bob and Keith exist on a network

9:16like 192-168.3 and then all of a sudden we have 254 users

9:21or devices on that network.

9:23We've run into a problem and we need to create more networks

9:26for more people to attach to.

9:28At layer 2, what we begin doing is creating VLANs

9:32or virtual local area networks.

9:34This is just a way to separate broadcast domains

9:37from one another.

9:39So maybe now, these two devices, this was Lois and Knox,

9:42they join a VLAN that is separated from Bob and Keith.

9:46So these two people, Lois and Knox

9:48can communicate directly to each other

9:50just like the others have been.

9:52And Keith and Bob can communicate directly

9:54to each other just like the others have been.

9:56However, Lois and Knox exist on a different network

10:00than Bob and Keith.

10:01Lois and Knox may exist on a 192.168.4 network

10:07whereas, Bob and Keith existed on the 192.168.3 network.

10:11And in order for now Bob or Keith to ping Lois or Knox,

10:15they then have to go through a router to make that happen.

10:19Because we're moving from one network to the next,

10:21the thing that you find out pretty quickly

10:23is that ARP and broadcast frames in general

10:26are only limited to the domain that they can broadcast within.

10:30We can't ARP to a different network

10:32because then that kind of defeats the entire purpose

10:34of limiting the scope of how far we can broadcast out or shout

10:38for help.

10:38So in this case, if Lois wants to ping Bob, Lois within ARP

10:43for her router or her default gateway

10:46and then send the packet to the router and the router

10:49would have to be connected to both networks to send it back.

10:51But here in the screen you may be thinking yourself, Knox, I

10:54don't see any routers, I only see switches.

10:56Well, there are lots of switches that

10:58can perform this routing option for us

11:00and this is where those whole VLANs come into play.

11:03For instance on these two devices,

11:05we set up the fact that they were in the 192.168.4 subnet.

11:09We could actually create them a layer 2 segment or a layer 2

11:13broadcast you may called VLAN4.

11:15Bob and Keith however we're located on 192.168.3

11:19so we would create a layer 2 segment for them called VLAN3.

11:23And I keep saying segment, I really

11:24meant a whole network not just one ethernet segment.

11:27When a user in VLAN3 wants to communicate to a user in VLAN4,

11:32like we've said, they have to be routed

11:33so it would make its way down to a default gateway

11:36like switch 18 located here.

11:38But then switch 18 can have an IP address

11:41on each one of these VLANs called

11:43a switched virtual interface.

11:46It's not a physical interface that is plugged into here,

11:49it's just basically saying, hey, switch,

11:51we just want you to have your own IP address on these VLANs

11:55that way you can communicate to these devices.

11:57And when switch 18 has its own IP address,

12:01for instance in VLAN3, it may have 192.168.3.1

12:06and in VLAN4 it may have its own IP address of 192.168.4.1

12:11it can then perform the routing option itself.

12:14So when Keith sends in a ping destined for Knox,

12:18his default gateway is going to be

12:20this default gateway, the switched virtual interface

12:22of 192.168.3.1.

12:24And then the switch itself can perform

12:26the routing action of routing it into VLAN4 inserting

12:30it onward towards Knox.

12:32So this is the concept of switching and rerouting bits

12:35in to play.

12:36We're limiting the broadcast domains down

12:38so they don't get so big that we have nothing but broadcast

12:41going on and on and on.

12:42And then we allow routing in between the VLANs

12:45when one device on one VLAN wants

12:47to communicate to a different VLAN using the switch

12:50virtual interface.

12:51The last thing we really need to talk about

12:52is how the actual mechanism or configuration

12:55of each of these interfaces really works.

12:57You see, all of our devices up to this point of plug

13:00directly into a switch.

13:01That's fine, this is very common for the access

13:03layer for these devices to plug into an access switch.

13:06We may very frequently also have a voice over IP phone connected

13:11into the mix and then off of that voice over IP phone,

13:14we have a computer plugged into that.

13:16Either way, what happens here is we configure these interfaces

13:20as what's called access ports.

13:22Basically saying, you belong to this specific VLAN

13:26and here's your access into the network,

13:28it's going to be through that VLAN.

13:29But then in this case, we may have multiple devices connected

13:33to different versions on the same switch

13:36and whatever this switch needs to carry traffic

13:39upstream into the core or from one switch to the next,

13:43it needs the capability to be able to carry multiple VLANs

13:47on the same ethernet segment.

13:50This is called a trunk port.

13:52For instance, when this device on VLAN4 wants to communicate

13:56into the network, ethernet 02 here is just configured to be

14:00an access port on VLAN4.

14:01So when the frame comes into this interface, this switch,

14:04switch 21 knows that this belongs to VLAN4.

14:07However, the link between switch 21 and switch 18

14:11may need to carry traffic between VLAN4 and VLAN3.

14:15So as the frame leaves switch 21 towards switch 18,

14:19switch 21 will add an 802.1Q tag.

14:24Just a tag on the actual frame itself that says,

14:27this belongs to VLAN4.

14:29So the tag will say, 4 on.

14:31When switch18 receives it, it says, Oh, I realized

14:34that this belongs to VLAN4.

14:36So it makes sure to forward it through its VLAN4 interfaces,

14:39whether those are trunk ports or access ports itself.

14:42As the traffic gets sent back down to the other computer like

14:44Knox, the moment it leaves the access port,

14:47the 802.1Q tag is removed.

14:50It's stripped off and it just becomes the basic naked frame

14:53that it was when it begins with.

14:55So this has been the crash course in Layer 2 switching.

14:57Now obviously, the expectation that we've set up to this point

15:00is that you have some experience with layer 2 switching

15:02and this is more or less a refresher at this point.

15:05If any of this was brand new, I'd

15:06really encourage you to pivot to something like our network plus

15:10content or a CCNA content here on CBT Nuggets

15:12because that has a lot of dedicated tutorials on what's

15:15switching really does and what the use cases are for things

15:18like access ports, trunk ports, VLANs, and Switch Virtual

15:22Interfaces.

15:23So this has been just refreshing the entire point of layer 2

15:26switching.

15:27In the next Nugget, we're going to deploy it.

15:28We're going to see it in action on EX series which is.

15:30I hope this has been informative for you

15:32and I'd like to thank you for viewing.

0:05So our first platform that we're going

0:07to cover in our Juniper layer 2 switching journey

0:09is going to be the most popular enterprise-grade solution

0:12that there is.

0:12It's the EX-series switch.

0:14I have deployed hundreds of these switches in my time,

0:18and they are all just a pleasure to work with, because they

0:20are rock-solid devices.

0:21So what we're going to cover throughout this Nugget

0:24is how to configure a VLAN on an EX-series switch.

0:26We're going to build on it over the next couple Nuggets

0:29until we've got a full-blown enterprise-grade solution.

0:31And then in the next skill, we'll

0:33actually cover how to perform layer 2 security

0:35options on top of that using the exact same platform.

0:38So let's get started with our first baby steps

0:40in layer 2 switching, and that is deploying

0:42a VLAN on a Juniper switch.

0:43I'll see you there.

0:44So like I said already, for this content, what

0:46I'm going to be doing is demonstrating

0:48how to configure basically VLANs, trunk ports,

0:51access ports, and SVIs on an EX-series switch.

0:54The EX-series switch that I'm working

0:56with is an EX2200 switch, just like the one that we're

0:59seeing on the screen here.

1:00Let me zoom over It.

1:01Yeah, it's just a little 24-port switch.

1:03It's an EX2200.

1:05It does come with some limitations.

1:07It doesn't have every single feature available to it,

1:09like an EX4200 might.

1:11And the EX2200 series switch, I should point out,

1:14is also end of life as of the time of this recording.

1:17The EX2300 switches are the ones that are currently supported

1:21and run the latest Junos code.

1:23But nonetheless, you can see, at the whopping price of $59.95

1:26with free shipping, it's really pretty affordable

1:29to get started labbing Juniper devices.

1:31You could buy two or three of these and still be under $200

1:35and have a full-blown Juniper switching lab.

1:37So with that being said, let's jump over

1:39to my command line of my EX-series switch.

1:42This is consoled in.

1:43I'm on the console port of my EX-series switch.

1:46And I'll give it a show interfaces terse real quick.

1:49And you can see just what we have here.

1:51We've got 24 ports that we're working with.

1:53They're ranging from interface ge-0/0/0 down to ge-0/0/23.

1:59We also have a loopback address, and this

2:01is where we're going to get started configuring

2:03this EX-series device.

2:05So here we go.

2:06From EX-SW1 on my EX-series device,

2:09I'm going to go into configuration mode.

2:10And the first thing you really want to do,

2:12before you try and do anything else,

2:14is you just want to create your VLANs.

2:16You got to remember, why are you creating more VLANs?

2:19It's really in order to administratively define

2:22how many users should connect to an actual interface

2:25or VLAN itself, as well as maybe separate

2:28specific classes of users from reaching each other.

2:31Let me just say this right now.

2:32If I were to, say, create a VLAN for accounting and then create

2:36a VLAN for HR, and we limit these to be /24s when we get

2:41into layer 3, if I have a user like Lois in HR that connect

2:45to the HR VLAN, and I have a user like Bob connects

2:48to the accounting VLAN, does that automatically stop us from

2:52reaching each other?

2:53If we're performing switched virtual interfaces,

2:55or what's called inter-VLAN routing,

2:56basically meaning that this device is allowed

2:59to perform the routing, no.

3:00We don't have any security here by doing that.

3:03We've stopped them from reaching each other on layer 2,

3:06but there's a very high chance in

3:08a correctly-designed enterprise environment that

3:10will still going to allow routing between them.

3:12However, the idea here is that by administratively separating

3:15Bob from Lois, we then have extra mechanisms from stopping

3:18them from reaching each other.

3:20First of all, they can't reach each other directly by layer 2.

3:22But secondly, we can then introduce

3:24things like firewall filters, which other vendors call ACLs,

3:27or even policies that stop that traffic from flowing one

3:30to the next.

3:30So this is one of the ways that at least is

3:32a first step in the right direction of security

3:34practices, by stopping accounting users from reaching

3:37HR users.

3:38So you just want to keep this in mind,

3:40that it's not the perfect security solution,

3:42just creating a VLAN.

3:43It's just what the first step is in a security

3:45solution is creating a VLAN.

3:47But also keeping in mind that the reason why

3:48we're really doing this is to limit the broadcast domain

3:50itself.

3:51So let's pretend for a moment that we

3:53have 40 users that we need to set up for HR,

3:57and then another 40 for IT, and then another 40 for accounting,

4:01and then another 40 for, let's say, C-suite executives.

4:04I know that's going to be a lot of C-suite executives.

4:06But we've got four different sets of users

4:09with four different sets of security reasons

4:12that they would need to be separated from each other.

4:14HR has access to everybody's HR records and payroll

4:18information.

4:18IT is-- well, you know what IT is.

4:20Accounting-- obviously, they're going

4:22to be the ones who are managing the money.

4:24We need them to be secure.

4:25And then C-suite executives are the ones

4:27who are making all the decisions,

4:28so they need to be separated from everybody else, too.

4:30So I see four VLANs that we need to create here.

4:33Now what we also need to consider

4:35is when we create these VLANs, like HR, IT, accounting,

4:39and C-suite executives, what are the VLAN numbers

4:43that they should have?

4:44This kind of gets outside the scope of what the JNCIS wants

4:48you to know, but we are getting into real-world practices

4:51at the same time.

4:52It makes sense to design our VLAN numbers

4:54to coincide with the subnet ranges that are

4:57going to match with them, too.

4:59For instance, if I give HR the VLAN ID of 4,

5:03I may want their IP address to be something like 10.0.4 dot

5:08whatever /24.

5:11The 10 obviously indicates this is

5:13going to be RFC 1918 private address space.

5:16Maybe the second octet could indicate

5:18which building they're located in, or which geographical site

5:21they're located in.

5:22This would represent their VLAN.

5:24And then, of course, there's their host bits

5:26that are serving as the remainder here.

5:28So I could quickly see, private address, this building,

5:30this VLAN, and that's their account or host address.

5:34For IT, I may do the exact same thing-- give them

5:36the VLAN ID of 5.

5:38So 10.0.5.X. For accounting, we may give them the VLAN ID

5:43of-- make something up-- like 11.

5:4510.0.11.X. And for C-suite executives,

5:49let's go with like 254.

5:5110.0.254.X.

5:55And this begs the next question.

5:56What are the maximum VLAN IDs that we can sets?

5:59Traditionally, VLAN IDs could be set between 0 and 4094 or 4095,

6:04depending on which vendor you're looking at here.

6:06But some of these VLAN IDs are reserved.

6:09For instance, VLAN ID 1 in Juniper devices

6:12is reserved for what's called the default VLAN.

6:14If I take a Juniper switch out of the box, I plug it in,

6:17and then I plug hosts directly into it,

6:19they can still communicate directly to each other,

6:21because without any additional configurations,

6:23all of my interfaces by default are placed into the default

6:27VLAN, which is VLAN ID 1.

6:29Big talking point coming up when we

6:30start talking about trunk interfaces around that.

6:33So here we go.

6:33On my EX-series switch--

6:34let me put those back up there so I can just

6:36remember what to do-- let's create each one of these VLANs.

6:39To create a VLAN on a Juniper-series switch,

6:41you simply say set vlans.

6:44And then this is where it gets pretty stinking interesting.

6:46Instead of on other vendors where you just

6:48say like the VLAN and then the number, on Juniper devices,

6:51all of the VLANs are called out by name.

6:54Critical to understand is that in other places

6:57of the configuration, you identify the VLAN by name, not

7:01by ID.

7:02So in this case, I'll create a VLAN called HR.

7:05And then I'll explicitly say your vlan-id is 4.

7:10It also doesn't hurt to hit up, delete out the vlan-id--

7:14we've got set vlans HR.

7:16And if I hit question mark, we do

7:18have the ability to give it a description

7:20if that's what we want to do.

7:22So I can say description "HR vlan" here,

7:25and that way, we actually have a nice little description

7:27showing what we're doing whenever we

7:29need to read the configuration.

7:30It'll make more sense in one second.

7:32Let's create the IT VLAN.

7:33So I'll say set vlans IT vlan-id 5.

7:38We'll hit up, give it a description of "IT vlan".

7:42Notice that my description with spaces

7:44also has to be enclosed in double quotes.

7:46We'll say set vlans accounting.

7:48We'll put it in the vlan-id of 11.

7:51And I'll say, description is going to be "Acct vlan".

7:56And then lastly, set vlans CSuite with a vlan-id--

8:00look, if I hit a question mark, you can see right here,

8:02it does say exactly explicitly that I can only

8:04set this VLAN-ID to be 1 through 4094.

8:07Just so you know, just so you can

8:08see that that's verified right there.

8:10Also, notice that this is primarily going to be used

8:12for an 802.1q tag whenever that time comes.

8:15But of course, it's also used exactly

8:16to identify the access ports, too.

8:18And this, of course, was VLAN-ID 254.

8:21So now if I give this a commit check, everything looks good.

8:24Oh, I forgot to give this a description, didn't I, though?

8:26That's important.

8:27Let's give it a description--

8:28"Csuite vlan".

8:30And now what I'm going to say is show |

8:32compare, and we'll see what I've changed.

8:34Ah, there we go.

8:35So this is what my VLANs configuration looks like.

8:38I have the vlans tier, then each of my VLANs

8:41is identified by name.

8:42I can see exactly what is covered in the description,

8:45as well as which vlan-id do they belong to.

8:49So with these all in place, I'm now going to say commit.

8:51I'm going to give it a comment that says, "create

8:54vlans HR, IT, Acct, CSuite".

8:59I'll close my quotes and press Enter.

9:01And now my VLANs have been successfully created.

9:04If I quit out of configuration mode,

9:06I can now do a few things.

9:07First of all, just for fun, I'll say show system commit.

9:11And I see where my commit was, specifying what the comment was

9:15that I left, so I know exactly what took place in this commit.

9:17Secondly, I'll say show vlan.

9:19And then if I hit question mark, you

9:20see we've got a bunch of different things

9:22that we can enter here.

9:23We can identify the VLAN by name.

9:25We can say brief.

9:26We can say detail.

9:27We can say extensive.

9:28All of these are big, and you should have learned

9:30about those in the JNCIA.

9:31Let's start off with brief.

9:32There we go.

9:33It identifies each of the VLANs by name and their tag, whenever

9:36we set the layer 3 interface, or the ports that

9:39are available in this.

9:40In the next Nugget, we'll be circling back to it.

9:42I can also check out extensive, because that is, honestly,

9:45one of my favorite parameters to throw onto this.

9:47And we see all--

9:49bunch of good information about the VLANs themselves.

9:52Notice that when we do extensive,

9:54we also see our default VLAN and how the interfaces are actually

9:58configured to be.

9:58Are they tagged, meaning are they trunk ports?

10:01Are they untagged, meaning they're access ports?

10:03And what interfaces belong to it?

10:05Notice, none of these have physical interfaces

10:08connected to it.

10:09They're all logical interfaces.

10:10And that's what the next Nugget's

10:11going to be all about-- what does all this mean?

10:14How do we configure different port types?

10:16Get ready to have some fun in the next Nugget.

10:18We've now created VLANs on an EX-series

10:21enterprise-grade switch.

10:22I hope this has been informative for you,

10:24and I'd like to thank you for viewing.

0:00[MUSIC PLAYING]

0:05The VLANs are all created.

0:06But they don't really do anything

0:08unless we actually attach those VLANs to ports,

0:10whether that's trunk ports or access ports.

0:13So what we're going to do in this Nugget

0:14is take all that work that we've done in the previous Nugget

0:17and then see it in action as we actually deploy trunk ports

0:19and access ports.

0:20This is going to be a whole lot of fun

0:21as we start to explore the different characteristics

0:24of trunk ports and access interfaces.

0:27So get ready.

0:27Let's have some fun as we deploy access in trunk ports on EX

0:30series switches.

0:31So now it's time to actually do something with those VLANs.

0:34If I give it a show interfaces terse, let's see real quick.

0:37Well, I've got all of these ethernet switching ports.

0:40But none of them are associated to those VLANs.

0:43Remember, if I did show VLANs brief real quick.

0:46I see, well, I've got a bunch of VLANs created but no ports.

0:52This is actually where you would count up how many ports

0:54are in this VLAN.

0:55I have no ports listed there.

0:57So here's what I suggest.

0:58I suggest looking at my show interfaces

1:00terse output real quick.

1:01Let's have some fun with this.

1:03Let's put port 1 here in HR.

1:06Let's put port 2 in IT, port 3 in accounting,

1:11port 4 in C-suite.

1:14And then very cool, what we should do

1:16is talk about what happens when I

1:17need to carry all of those VLANs upstream to the next switch.

1:22Remember the concept of 802.1Q tagging where we could trunk

1:26each of these VLANs over one ethernet link up to the next

1:30switch.

1:30We would just tag them and let them know, let

1:32the upstream switch know which VLAN

1:34does this particular frame belong to.

1:36So let's take GE000 and turn it into a trunk port that

1:40can carry all of these VLAN.

1:43Keep in mind one very important thing about this trunk port

1:45that we're going to address when we get to this point,

1:48these are the four VLANs that we created,

1:50but there is also that concept of a default VLAN

1:53that's operating by default, very clever name after all,

1:55isn't it.

1:56That was VLAN 1 that was our default VLAN.

1:59So here we go.

1:59Let's get started configuring these interfaces.

2:01From configuration mode, the first thing I'm going to do

2:04is I'm going to move into edit interfaces GE001.

2:07This is where we wanted our HR report to be.

2:10If I say show, by default out of the box on EX series switches,

2:14they belong to the family of ethernet switching.

2:16That's correct.

2:17That's the protocol family that we

2:19want this particular interface to be in.

2:21It's not in inet because it's not a routed interface.

2:24Inet6 is a routed interface.

2:26ISO is for something, you know with isis.

2:28You'll learn about that later.

2:29The same with NPLS if you're in the service provider track.

2:32This is where we want this particular interface

2:34to behave like a switch.

2:36But we need to add some additional parameters to it.

2:38Do we want it to behave like an access port?

2:40And if so, which access port?

2:42Which VLAN does it belong to?

2:43This is where we go to configure this.

2:45So we're going to say, set unit 0 family ethernet switching,

2:48keeping in exactly the same that it was.

2:50But then we're going to say, your port mode

2:53is going to be-- hit question mark.

2:54We see we've got two options.

2:56Is this an access port or is this a trunk port?

2:58Recalling what we're doing here, I've

3:00got this switch with these interfaces.

3:03And I have a user in HR connecting into this interface.

3:07I don't want to have my user worry about tagging this frame

3:11as a frame comes in to this interface.

3:14I want this switch to already know

3:16which VLAN this belongs to.

3:18And that's why we would use an access port.

3:20An access port is all about the frames

3:23that go in or out of this interface

3:25are going to automatically belong to that specific VLAN.

3:29That way when we spin up another port,

3:31like an access port that belongs in the same VLAN,

3:34these two would have direct connectivity to each other

3:37without ever having to tag a frame.

3:39Or if this port becomes a trunk port,

3:41we would know that as a frame comes in on an access port,

3:45before it leaves the trunk port, make sure to tag it

3:47with the associated VLAN.

3:49So in this case, we're saying the port mode

3:51is going to be accessed.

3:52That way, now, when I say show, we

3:54see that this interface is configured

3:56for ethernet switching.

3:57And it's an access port.

3:58But without configuring anything else, which VLAN does

4:01it belong to?

4:02I'll give you a quiz.

4:03Yeah, it belongs to the default VLAN

4:06because that's the default setting on all of these.

4:08Therefore, this would only communicate

4:10to other devices that are communicating

4:12within the default VLAN, VLAN1.

4:14So we need to override that.

4:16We need to tell it, you belong to the HR VLAN.

4:20So I'm going to say, set unit 0 family ethernet switching.

4:23Then I'm going to say, VLAN members,

4:25and then you hit question.

4:26And you see again, you identify these by name.

4:30You can also identify a list of VLANs.

4:33But that really only applies to trunk ports.

4:36So in my case, I'm going to specify the HR VLAN, which

4:39it does tell me, this is associated

4:41with the VLAN tag of 4.

4:43Now, if I hit show, it looks like we've

4:45got our access port configured to be in the HR VLAN.

4:48I'm going to move up one tier, and we'll

4:50move on to the next interface.

4:52So I'll say set GE002 unit 0 family ethernet switching.

4:58And we knew that we wanted this one to also be an access port.

5:01So we'll say port mode of access.

5:03And this was going to for my ITV LAN.

5:06So I'll say for the Ethernet switching family,

5:09you are a member of VLAN IT.

5:12Also keep in mind that because we've now

5:14configured the names of each of these VLANs,

5:17you can use tab complete on Juniper operating systems

5:20to autocomplete them.

5:21So there's IT configured.

5:23And if I say show GE002, we see the configuration here.

5:27It looks good to go.

5:28Let's say set GE003 unit 0 family ethernet

5:32switching is going to be a port mode of access.

5:36And this one was going to belong to the VLAN

5:39members of accounting.

5:41If I say show GE003, we're looking good to go there.

5:45The last access port that we were configuring

5:47was going to be our C-suite executives.

5:49So I'll say set GE004 unit 0 family

5:54ethernet switching port mode of access and VLAN

6:00members of C-suite.

6:02So at this point, it looks like all of my access ports

6:05are configured exactly like I want.

6:06The last thing I need to do is get this trunk port up

6:10and running.

6:10That way it knows to tag this traffic as it goes

6:13across this one ethernet link towards an upstream switch

6:17so that they know, oh, this frame belongs to this VLAN.

6:20So what we're going to do is we're

6:21going to move into edit GE000.

6:24We're going to keep this in the protocol

6:26family of ethernet switching.

6:28But now of course, our port mode is going to be trunk.

6:31And this is where it gets a little bit trickier.

6:33We're going to identify, what are the VLANs that

6:36are allowed to be trunked over this port that

6:39also need to be tagged?

6:41You see, this is a thing about the trunk ports themselves.

6:44I'm going to draw two switches here on the screen

6:46and talk about what is the behavior between two trunk

6:49ports.

6:50For instance, if my HR VLAN wants

6:52to go across this trunk port, we're going to stick a tag of 4

6:56on it before it goes up towards the interface,

6:58then that 4 is removed.

7:00However, what happens when I have

7:02someone plugged in to the default VLAN down here

7:04that was VLAN ID1?

7:06The default behavior on a trunk port

7:08is that we want to send that frame across the link

7:12completely untagged.

7:14That way when it's received, we see, oh, wait,

7:16this is an untagged frame.

7:18Therefore it belongs to the default VLAN.

7:20This is called the native VLAN ID.

7:24The native VLAN ID means if this frame is arriving on a trunk

7:28port untagged, meaning there's no 802.1Q tag,

7:32then it belongs to the native VLAN.

7:34And whatever your native VLAN is,

7:35you need to configure it so that switches

7:38know how to behave when they receive an untagged frame.

7:40It doesn't have to be VLAN ID1.

7:43You could change that to be VLAN ID10.

7:45You just need to make sure it matches on both sides,

7:47so they know not to tag the frame

7:49as it leaves the interface, or what to do when

7:51it receives an untagged frame.

7:53So what we're talking about now is

7:54when we say set unit 0 family ethernet switching VLAN

7:58members, we're saying, what are the tagged

8:01frames that we're going to allow over this trunk port?

8:04We specify which VLANs go over the trunk port.

8:07And because I'm allowing multiple VLANs over the trunk

8:10port, I use an open bracket to say,

8:12here's going to be a list of VLANs.

8:15So I'll say ACCT, C-suite, HR and IT.

8:20Then I say close brackets.

8:21When I press Enter here, now we'll say show.

8:24And you see how this is written out.

8:26The next thing I need to do is set the native VLAN ID.

8:29And this doesn't always show up in the most intuitive place.

8:32Let me say, set unit 0.

8:33And I'll give it a question mark.

8:35And so far everything is looking good.

8:37We're going to move into family ethernet switching

8:39and then say question mark one more time.

8:41And now under the ethernet switching

8:43without configuring anything under the VLAN members

8:46or without configuring things like the port mode,

8:48we see we have a native VLAN identification configuration.

8:52And this is the next most confusing part.

8:54In this case, we specify the VLAN by ID, not by name.

8:58This is like the only place in Juniper

9:00switching where we specify it by the VLAN ID and not by name.

9:03But this is where we would go to do it.

9:05In this case, since I want it to be my default VLAN, which

9:07is VLAN ID by default, I'm just going to set it to 1

9:10and press Enter.

9:11So now when I say, show, this is how

9:13my trunk port is configured.

9:15We see that I have the protocol family of ethernet switching

9:18turned on.

9:19And it's going to behave like a trunk.

9:20These VLAN members are what's going

9:22to be tagged as they go across the trunk port.

9:24And this is what's going to be untagged as it

9:27goes across the trunk port.

9:28Let's give it a permit check.

9:29Waiting for the commit check.

9:30The EX 2200s are a little bit slower.

9:32So sometimes it takes a little bit longer for the commit check

9:35to take effect.

9:35But the configuration check succeeds.

9:37So let's commit and quit.

9:39Now we've created VLANs and attached them to interfaces.

9:42So we've done a huge amount of ethernet switching work

9:44on our EX series Switch.

9:46Now what I want to have happen is

9:47I want this EX 2200 to be able to handle routing traffic

9:51from one VLAN to the next.

9:53That way, if we have a host on the HR VLAN

9:56that needs to talk to the IT VLAN,

9:58they could communicate through the switch

10:00by allowing the switch to do the routing.

10:01That's what the next nugget's all about.

10:03I'll see you there.

10:04In the meantime, this has been configuring the interfaces

10:06on an EX series switch.

10:07I hope this has been informative for you.

10:09And I'd like to thank you for viewing.

0:05We touched on that concept of intervlan routing,

0:07and how it's an absolutely critical feature when

0:10it comes to deploying Juniper devices or really any device

0:13that a host needs to use as its default gateway.

0:15That way we could just push some of that stress of routing down

0:19closer towards the host themselves,

0:21and let maybe even the access core

0:22or the distribution core of our network

0:24handle that routing for us if it all takes

0:26place on the exact same device.

0:28So in this Nugget what we're going to do is,

0:29we're actually going to explore how

0:31to take those VLANs that we created

0:32and all of the access and trunk parts

0:34and then add one special interface into the mix that

0:37could perform some intervlan and routing

0:39for us directly on the Juniper switch itself.

0:42So let's get going deploying the layer 3

0:43interface for each one of our VLANs oftentimes referred

0:46to as the Switched Virtual Interface.

0:48Let's get going.

0:49So now here's the scenario that we're

0:51going to have some fun with.

0:53We're going to be taking this Ethernet series, this EX

0:55series, which ethernet.

0:57EX series yes it is ethernet, EX series switch

0:59that we configured here and pretend for a moment

1:02that we had to say, an HR user right here, which was VLAN 4,

1:06and we had an IT user here, which was VLAN 5,

1:10and they wanted to communicate directly

1:11to each other maybe sharing a file or something like that,

1:14and we don't necessarily want to trump this up to a router

1:18and then back down the trunk port and out the interface

1:20so that the router can handle this.

1:22This is actually a design scenario

1:24called a Router on a Stick or RoaS,

1:27if that's what you want to call it.

1:29Because we have a one ethernet link going up

1:32that's trunking VLAN tagged traffic up to the router.

1:35The router performs the routing operation

1:37and sends the tag traffic back down destined

1:40for the other subnet or the other VLAN,

1:42and it's kind of an inefficient use of resources.

1:46I mean especially think about it like this,

1:47how stinking inefficient would it be if this device wanted

1:51to ping this device, and it had to go all the way down

1:53into the core in order to be routed back up or worse all

1:57the way over to a router in order

1:59to be routed back up when the devices that

2:01are located right here could perform

2:03this routing option for us.

2:05Or even better if the other device

2:07that we were trying to ping was connected

2:09to the exact same switch?

2:10We don't want to have to send it upstream just to send it

2:12back downstream and then over.

2:14These switches can handle this routing operation for us

2:17because a locally connected route is not that big of a lift

2:20first switch to perform.

2:22So let's talk about how to get this going.

2:24Jumping back to my EX series switch,

2:26let's say show VLANs real quick.

2:28And now I see this is why my VLANs look,

2:30I see which VLANs are participating in it.

2:32Notice when I do show VLANs, the trunk ports

2:34also show up as participating in the VLAN that's ge 0, 0, 0.

2:38So I have see that I have these VLANs,

2:41and what I want to have happen is a HR user

2:43to be able to speak directly to an IT user.

2:45The way this switch needs to make this happen

2:47is we have the switch, we need to basically turn

2:50a little router on inside of it.

2:52And the way routers work is they have

2:54to have a leg in each Ethernet segment to do this.

2:57So we're virtually going to accomplish this

3:00by just giving the switch an IP address located on each VLAN.

3:05So if I go into configuration mode, this is how I do this.

3:08I have VLAN ID 4 and VLAN ID 5.

3:11What I'm going to do is, I'm going to create

3:13an interface on the VLAN.

3:15We're going to say set interface is VLAN

3:18and then subinterface is going to be mapped directly

3:21to the VLAN ID itself.

3:23Note, you do not need to do this,

3:25it's just a cleanliness thing that you probably

3:27should do it this way.

3:29The subinterface of 4 is going to map to the VLAN ID of 4.

3:32However just creating the subinterface of 4

3:35doesn't actually perform the map itself,

3:38you do have to explicitly set this again,

3:40this is just a naming convention in order to make it easier.

3:43So I'm going to say for the VLAN interface

3:46with a subunit of 4 we're going to use

3:48the family of inet address because we're

3:51creating an IPv4 address.

3:52Let's go ahead and give us IP address of-- oh, no,

3:54we used 10 in the earlier example.

3:5610 dot 0 dot 4 dot 1, we'll put it 1 and slash 24.

4:00I'll now create the other interface

4:02that will be put into the other VLAN.

4:04Set interface is unit family inet address 10, 0, 5,

4:101, slash 24.

4:11So here's the thing we created the IPv4 address that's

4:15going to be usable by the VLAN itself,

4:18but the VLANs don't actually know,

4:20they're not actually associated to this interface yet.

4:24You have to go in the VLAN configuration

4:26and say, hey, HR VLAN that's your layer 3 interface.

4:30Hey, IT VLAN that's your layer 3 interface.

4:34So here's how we do this.

4:35I'm going to say set VLANs HR, and then the command

4:39is layer 3 interface.

4:41You then say this is going to be your VLAN subunit of 4.

4:45I'll say set VLANs IT is going to have the layer

4:493 interface, a VLAN subunit 5.

4:52All commit this configuration or at least

4:54I'll do a check first to validate that it works.

4:56She always want to do a commit check.

4:57Make sure that it's going to work before you actually just

4:59pull the trigger on this thing.

5:01And now I'll say commit with a comment intervlan routing

5:06enabled, and press Enter, and that's it.

5:09That's what it takes to actually configure this device

5:12to perform intervlan routing, that way this device now has

5:15an IP address on each of these VLANs.

5:17We create the VLAN interface and I'd

5:20like to put a subunit that matches

5:22the VLAN ID, that way it's nice and clear what's going on.

5:25Then we just associate that VLAN interface with the VLAN itself

5:29with the L3 interface command.

5:30So now, our EX series switch has been

5:33configured for VLANs interfaces and intervlan routing.

5:37I hope this has been informative for you,

5:39and I'd like to thank you for viewing.

0:05In a previous Nugget, I did sneakily mention

0:08that there is a scenario where we could have a phone

0:11and a computer plugged in to, essentially,

0:13the exact same port, right?

0:15We've got the computer passing through the phone

0:18to get to the actual internet or the internetwork

0:20that we're trying to run itself.

0:22How, then, do we set up a scenario where

0:24we've got two devices connected to the same port,

0:27but we want them in separate VLANs

0:28because we don't want our voice VLAN to be

0:30on the same traffic as someone browsing ESPN or, at least,

0:34writing data to a database or a file share,

0:36or something like that?

0:37We want those to be separated.

0:38Juniper has a way of handling this

0:40by configuring the voice VLAN.

0:42And it's a little bit different from other vendors'

0:44implementation of the voice VLAN.

0:46This is going to have a separate section under Ethernet

0:48switching options, where we tell it, for voice traffic,

0:51treat this interface differently.

0:53Let's get going, talking about how to configure the voice

0:56VLAN on EX Series switches.

0:58There is an interesting switching scenario

1:00that especially comes up in the enterprise,

1:01especially at the access tier, when

1:03it talks about IP phones and voice over IP and telephony.

1:07We did hint at this a little bit already,

1:09where we could have a switch, like, this one,

1:12and connected to it, is, first of all, a phone.

1:14This is going to be my attempt to draw a phone.

1:16It kind of looks, honestly, like,

1:18the mushroom guy on Mario Brothers right there.

1:20Doesn't it look like?

1:21OK, anyway, sorry.

1:22Here we go.

1:22So there's the phone.

1:23Well, maybe I'll put it like--

1:24no, this is getting worse.

1:25I was going to put a dial there, but-- and then

1:27off of the phone, we have daisy chained a computer.

1:30Now, how does this work, because voice is often

1:33on a different VLAN than data, isn't it?

1:35I mean, it makes a whole lot of sense to do it that way.

1:37But we've only got one little switch configured here.

1:40Now, in the olden days, we would actually configure this to be

1:42an 802.1Q trunk.

1:44And theoretically, that is how it works.

1:47However, Juniper devices are configured specifically

1:50to identify what voice traffic is

1:52going to look like versus what data traffic is

1:54going to look like.

1:55And then we tell this interface that it has a voice VLAN that

1:59is separate from the data VLAN.

2:01Ultimately, what's going to happen

2:02is native frames that come in on this interface untagged

2:07are going to be associated with the voice VLAN.

2:09And the phone itself will tag the traffic

2:12from the computer as part of the data VLAN.

2:15[SOUND EFFECT]

2:17Wait, what did I just say?

2:18No, that's backwards.

2:19I got myself completely turned around here and just confused

2:21myself.

2:22Forget everything that I just said.

2:24The way this really works, the phone just

2:26behaves like a dumb switch.

2:28As the data packets themselves from the computer pass

2:31through the phone, they remain untagged.

2:34We're going to let the switch handle figuring out what

2:36untagged frames are all about.

2:38And that's why we configure our switchboards

2:39to be access boards and tell them what VLAN they belong in.

2:43So if we're using an accounting VLAN or an IT VLAN,

2:46or an HR VLAN, the computer doesn't

2:47have to worry about tagging those frames.

2:49And the phone doesn't have to worry

2:50about tagging those frames.

2:52The switchboard itself will just use the basic configuration

2:54and treat untagged frames the way it's always done.

2:57For the phone itself, when it needs

2:59to send voice traffic into the switch,

3:01it will have to tag that traffic with the voice VLAN tag.

3:06And then we configure the voice VLAN interface itself.

3:09And we tell it how it is should treat these tagged frames

3:11within the voice VLAN.

3:13So let's get going, creating a voice VLAN.

3:15What we're going to do is we're just going

3:17to create a voice VLAN first.

3:18I'm going to say, create set vlans voice

3:20and then give it a voice VLAN ID of something, like, vlan-id 99.

3:25I'll go ahead and just set the description here, too,

3:27at the same time.

3:28Why not?

3:28It's good measure here.

3:29Let's say, description, "voice vlan," and press Enter.

3:33That's created the voice VLAN.

3:35Now we need to do is associate that voice VLAN

3:38with the interface itself.

3:40I've been picking on my HR VLAN.

3:42So why not stick with it?

3:43I'm going to say run show vlan real quick.

3:45And I see my HR VLAN is configured on interface

3:48ge-0/0/1.

3:50So what I'm going to do is I'm going to say set an Ethernet

3:53switching option.

3:55This is where you go to configure the voice VLAN.

3:57Under Ethernet switching options,

3:58we have VoIP as one of our options that we can set.

4:02So this is where we're going to be saying, hey,

4:04these interfaces here can use a voice VLAN.

4:07In fact, what we're about to specify is the voice VLAN.

4:10I'll say interface ge-0/0/1.0 because we do have to specify

4:15the logical interface since that's where the protocol

4:17family is configured.

4:18Now I can say question mark, and we see what we can set.

4:21We can set the VLAN and then specify voice--

4:25voice, right there.

4:26Beyond that, it's interesting to know

4:27that outside of the interface, if I hit question mark,

4:30we can also set things, like, class of service,

4:32like, the forwarding class.

4:33If I hit question mark here, now, we

4:35can say something, like, assured forwarding.

4:37That way, we can actually set class of service bits or QoS

4:40bits on the actual voice over IP frames themselves.

4:43Now, that's outside of the JNCIS topic.

4:45But it's such an easy configuration,

4:47I wanted you to know about that.

4:48So let me say show routing options.

4:50And you can see how this configure-- (SOUND EFFECT) oop,

4:52no--

4:52show ethernet-switching-options, and you

4:54can see how this is configured right now.

4:56We created the voice VLAN under VLANs.

4:58And then under Ethernet switching options,

5:01we created the voice over IP tier.

5:03We said, for this interface, this VLAN

5:06is going to be associated with voice over IP traffic.

5:09Then we also set some very easy class

5:11of service bits allowing a shared forwarding

5:13to be tagged in the CoS bits on the frame itself.

5:16So if I give this a commit check, everything, I assume,

5:20is going to check out just fine.

5:21Ah, it does.

5:22Let's commit and quit.

5:23And now what you should know is the untagged traffic

5:26that comes in is going to be treated like a data VLAN.

5:29And the phone will now have to tag the outgoing frames

5:32with the voice traffic.

5:33Our switch, now knows how to treat

5:35the untagged versus tagged traffic

5:37and forward it on-- a little bit different from the trunk

5:39configuration, even though, theoretically, it

5:41does the exact same thing.

5:42So this has been understanding how to configure a voice

5:45VLAN on an EX Series switch.

5:46I hope this has been informative for you.

5:48And I'd like to thank you for viewing.

0:05The crazy thing about the MX-Series router

0:07is that they don't just stick to layer 3.

0:10In fact, one of the more popular service provider services

0:13that they could provide, very coincidentally named,

0:16to their customers is a layer 2 ethernet segment.

0:19That way, a customer who's got one site in, say, New York

0:22City, and a different site across town in New York City

0:26could still be connected as if they're on the layer 2 segment.

0:29The service provider provides their own backbone

0:32as a layer 2 ethernet segment for them to be carried.

0:34Now, there's a lot of content in the JNCIS service

0:38provider playlists on how this is actually

0:40done using QinQ technologies as well as

0:43link aggregation of multi-chassis link aggregation.

0:45It's fascinating stuff.

0:46But for now, what you should know

0:47is that the MX-Series router doesn't just call these VLANs.

0:51They actually call this a bridge domain

0:53because what they're really doing, at the end of the day,

0:55is bridging one customer site all the way

0:57to the other customer site.

0:59So let's explore how we would go through the bridge domain

1:01configurations on an MX-Series router

1:03to basically perform the same tasks as an EX-Series switch.

1:06Let's go.

1:07So switching is switching at the end of the day.

1:09But it does help to see what is the point of what

1:12it is that we're trying to do.

1:13And this topology-- if you're not following along

1:16in the JNCIS service provider-- this

1:18is a topology that we very much use in the JNCIS service

1:21provider studies that we have here at CBT Nuggets.

1:24Even though you're in the enterprise track

1:25and you may not be going for service provider,

1:27there's still a lot of enterprise in it

1:29because enterprises consume service provider services.

1:33The idea here is that we may have a device,

1:36like, this router here.

1:37Behind this device, we have a lot of hosts and servers

1:40that we have wanting to use service provider services.

1:43And then we have a remote site down here.

1:46And maybe a user in this remote site

1:49wants to access a server in this site.

1:52And beyond that, they want to do it directly using layer 2.

1:55They want to do a broadcast or an ARP

1:58and trunk all the way across the service provider backbone

2:02in order to reach end to end.

2:04This is absolutely something that service providers

2:07can do, believe it or not.

2:09They do this a bunch of different ways.

2:11The simplest way is QinQ.

2:12The most complicated way is EVPN or layer 2 VPN.

2:16There's also something called VPLS

2:18that leverages MPLS to make all of this happen.

2:20Anyway, they can do it.

2:21And you may encounter a vMX router

2:24at some point in your studies.

2:26And then be totally confused as to how to configure switching,

2:30and VLANs, and interface trunk ports,

2:32and layer 3 routed interfaces on these MX-Series routers

2:36because they're wildly different than the config-- actually,

2:39they're not wildly different-- they're essentially

2:41the exact same thing.

2:42But it's very different, at the same time,

2:44when you see it compared to the EX-Series switch.

2:46You don't create VLANs on a MX-Series router.

2:50You don't create VLAN interfaces on an MX-Series router.

2:53You don't even configure a port mode on the MX-Series router.

2:56There's different commands on an MX-Series router

2:59to accomplish the exact same thing.

3:00So I think I'm waiting on my MX-Series router to boot--

3:03Oh, it is booted up here.

3:04Let me just get logged in here and I'll

3:05show you how we go about configuring this one

3:08step at a time.

3:09The first thing that you should know on an MX-Series router

3:11is that they don't consider this a VLAN or, at least, an area

3:15of a VLANs that they configure.

3:16What they configure is bridge domain.

3:18You see, the idea is that we may have multiple customers-- right

3:22here is one customer.

3:23But what if we had another customer up here

3:25and another customer up here, and they all

3:26wanted to trunk VLANs across our provider network?

3:29What we then need to do is create a domain

3:32for this customer, so that they can bridge from one site

3:36to the next site over our network.

3:38So what we do is we create a bridge domain

3:40and say what all interfaces or what all VLANs are associated

3:43with that bridge domain.

3:45So from vMX1-- oop, it's giving me some virtualization messages

3:48here--

3:49Sorry about that.

3:49I'm going to go into configuration mode.

3:51And what I'm going to do is instead of creating VLANs,

3:53I'm going to create bridge domain.

3:55And just like the VLAN configuration,

3:57we identify our bridge domains by name.

4:00I'll say customer one, for instance,

4:02could be one of our customers that's

4:03going to send VLANs to us.

4:05Maybe I'll say this customer one BD,

4:07so that I know it's a customer one bridge domain.

4:10Then check this out.

4:10I can hit question mark here and there's

4:12a lot of additional configuration.

4:13But this one should look nice and familiar, VLAN ID.

4:17That's right.

4:17We can associate a VLAN with this customer

4:20or we can create a list of VLANs for this customer.

4:23Both are common deployment scenarios.

4:25For now, I'll say VLAN ID.

4:28And we'll put something, like, VLAN ID 101.

4:30That way, we know that the customer that's

4:32going to be sending stuff in to us,

4:33maybe we're going to tag those customers

4:35frames with our own frame of 101,

4:38or maybe we're expecting the customer

4:39to send tagged frames with 101 on them, already on them.

4:43And that way, we know how to receive them.

4:45I can also create a bridge domain for my customer two.

4:49I'll call this customer two BD.

4:51And maybe this customer is going to send multiple VLANs to us.

4:55So with a VLAN ID list, I can create

4:57a list of VLANs identified by number, like, 202, 203, 204,

5:02and then close the list.

5:03Now, if I say show bridge domains,

5:05we actually see how the actual bridge domains are listed out.

5:08And very cleverly-- I love this about the MX-Series routers--

5:11because it identified that we did 202 through 204,

5:15it actually wrote it out as 202 through 204.

5:17It's a very handy way that we could actually

5:19create these VLANs.

5:20So now, we've created VLANs on this particular device

5:23on an MX-Series router.

5:24This is what it takes to do it.

5:25Instead of creating VLANs, we're creating bridge domains.

5:29Now, in the next Nugget, what we're going to do

5:31is assign these bridge domains on the interfaces themselves,

5:34both as access ports and as trunk ports.

5:36It's going to be a lot of fun.

5:37We'll see how to do this on an MX-Series router.

5:40I hope this has been informative for you.

5:41And I'd like to thank you for viewing.

0:05So now, that the bridge domains are created, that really,

0:08by de facto, created the VLANs themselves

0:10that the image series router can now use for its interfaces.

0:13And just like the EX switches, we

0:16could create access ports and trunk ports,

0:18so can we on the MX series routers.

0:20The crazy thing is if you haven't seen an MX series

0:22router, it kind of looks like a gigantic six foot tall chassis

0:26with just rows and rows and rows of ports.

0:28It kind of looks like a mega switch,

0:29even though its primary purpose is to be a router.

0:32So we can now configure all of these rows of ports

0:34to behave trunk ports or access ports if that's

0:37what we want them to do.

0:39We're just going to use the bridge protocol family

0:42on the interfaces themselves.

0:44Let's get go and explore how to configure an MX series routers

0:46interfaces to behave like a switchboard.

0:49So, our bridge domains are created for our customers.

0:52Now, what we need to do is actually

0:53associate their interfaces with the bridge domains themselves.

0:56What we're really talking about is

0:58these are the interfaces that we're expecting customers

1:00to send traffic to us.

1:02Again, maybe we are doing the ones

1:04doing the tagging as their frame arrives on this interface,

1:07or maybe they're sending tag frames up to us.

1:09It really depends on the deployment scenario.

1:11I'm not going to dig too deep into that.

1:13If you're interested in how you would actually do those things

1:16or why and when you would actually

1:17do those things totally covered on the JNCIS service provider,

1:21check out the content called service provider

1:23bridging concepts, as well as deploying QNQ.

1:25Whole lot of fun.

1:26All right.

1:27Here we go.

1:28So, what I'm going to do is I'm just going to move into edit

1:30interfaces ge-0/0/0.

1:32Let's pretend for a moment that this is going

1:34to be customer ones interface.

1:36If I say show, we actually have the family

1:39of inet configured on this interface.

1:40One of the things that you find out about in a MX series

1:43routers is they can either be layer 3 or they can be layer 2,

1:46but they can't be both.

1:47So what we need to do is we need to delete the family of inet

1:51because we want this interface to be doing switching.

1:53Now, what I'll do is I'll set the family of bridge.

1:56We're not setting the protocol of ethernet switching,

1:59we're setting this as the bridge family.

2:01And then interestingly, we don't actually associate--

2:04we don't actually say you're part of customer 1 BD,

2:06we go straight into specifying the VLAN ID itself,

2:10like one on one.

2:12Because that's what we created above when

2:14we created the bridge domain.

2:16Now, I also want to point out another way

2:18that you could do this is you could

2:19set the interface within the bridge domain

2:22itself right there.

2:23So if I say top, it may be a good scenario for you

2:26to say set bridge domains customer 1 BD,

2:30and then specify the interface that you want to be associated

2:34with this bridge domain.

2:35So now, I can say show bridge domains,

2:36and we see it's created VLAN ID 101,

2:39and associated the interface to it,

2:41or I can say show interfaces ge-0/0/0.0.

2:46Oh, too many slashes.

2:47There we go.

2:47And now, I see that I've created this to be

2:49a switchboard in VLAN ID 101.

2:52We should also tell this explicitly

2:54that it's going to be an access port if we

2:56don't want to tag any frames going

2:58back out towards the customer.

3:00So, I'll say set interfaces ge-0/0/0.0 family bridge

3:05and the configuration here isn't porth mode,

3:07it's interface mode.

3:09Here, I can say you're on access port.

3:11The same thing can go for customer two.

3:13We go through a similar configuration.

3:15We'll do this on interfaces ge-0/0/1,

3:18pretending that's what's going to connect the customer to.

3:20I'll say family bridge, and then we're going to say the VLAN ID

3:24list. , Because up above we used a VLAN ID list.

3:29I can use the exact same syntax here and specify 202

3:33through 204.

3:34But because this is sending multiple VLANS,

3:36we're definitely going to need to tag this, aren't we?

3:38So, I'll hit up and under the family of bridge for ge-0/0/1,

3:42I'll set the interface mode to be shrunk.

3:46Now, if I give it a commit check,

3:47let's just see how things are looking.

3:49And this is one of the first things that you should know,

3:51if we configure our interface under the bridge domain

3:55section, we cannot also configure it under the ethernet

3:58interface, at least not with an interface mode already set

4:02to it.

4:02So, what I'm going to do is I'm going

4:04to delete out the bridge domains command that we

4:06set for customer 1 BD.

4:08Let's specify the interface of ge-0/0/0.0.

4:11You're going to have one or the other.

4:13So, if you're going to configure the interfaces under the bridge

4:16domains, don't configure it under the interface or vise

4:18versa.

4:19Let me give it another commit check real quick.

4:21Everything checks out OK.

4:22But before I commit this, I want to also

4:24be able to configure layer 3 inter VLAN routing.

4:28That way, these bridge domains know

4:30which layer 3 interface they can broadcast into and use in order

4:33to communicate.

4:34That's what the next Nugget's all about.

4:35I hope this has been informative for you,

4:37and I'd like to thank you for viewing.

0:05Just like on the EX Series switch,

0:07where we had a switch virtual interface that

0:09could perform routing options and inter-VLAN

0:11and routing for us directly on the switch itself,

0:14we can do the very same thing with our bridge domains

0:16in the MX Series routers.

0:17What we're going to do in this particular Nugget

0:19is configure the routing interface on the bridge domain

0:23itself.

0:23This is going to feel very similar to what

0:25we did on the EX Series switch.

0:26It's just some slightly different commands

0:28that get us there.

0:29The end result is the exact same.

0:31So let's get going, getting the routing interface on a bridge

0:34domain configured in an MX Series router.

0:36I'll see you there.

0:37So our last step is to configure inter-VLAN routing.

0:39Another very common deployment scenario on Juniper MX Series

0:43routers.

0:44We already configured the Ethernet switching on it

0:46or at least we configured it under bridge domains.

0:49Now we're going to take those bridge domains and those VLANs

0:51associated with those bridge domains

0:53and configure the actual routing interfaces themselves.

0:56This is familiar to what we did on the EX Series switch,

0:59but it's just different enough to be kind of confusing.

1:03I'm going to start off by creating the interface first,

1:05and it's not the VLAN interface.

1:08Juniper devices uses the integrated routing and bridging

1:11interface or IRB.

1:13So instead of VLANs we're setting the IRB on the router.

1:17Then we say what unit we want this to be associated with.

1:19Again, I do this based on the VLAN IDs themselves.

1:24So I'm going to set unit 101 for VLAN ID of 101.

1:27Now I can set the family inet address.

1:29Let's put 192.168.101.1/24 just for cleanliness sake.

1:34For VLAN ID 202, I'm going to do the exact same thing.

1:38We're going to say set interfaces IRB unit 202 family

1:42inet address, the setting IP address, 2,

1:441 six 192.168.202.1/24.

1:48So this creates the interfaces themselves.

1:50Now I need to associate them with the bridge domains.

1:54Let's say set bridge domains for customer 1,

1:57and then the command that we're setting here

1:59is routing interface, not layer 3 interface routing interface.

2:04Then we specify irb.101 to set the sub-interface of 101

2:09with it.

2:10Just like before, will say set bridge-domains this time

2:12for customer 2.

2:14And the routing interface is going to be irb.202.

2:17Now if I give this a commit check well,

2:19this makes a whole lot of sense because the previous bridge

2:22domain for customer two had a VLAN I'd list.

2:26It's expecting to have multiple VLANs and how can

2:28we associate one layer 3 interface with multiple VLAN,

2:31it makes a whole lot of sense.

2:33And that's why I configure this to actually show you explicitly

2:36what is the configuration failure error here.

2:39It says we need to have either a vlan-id or a vlan-tag not

2:43a vlan-id of list because that doesn't make

2:45a whole lot of sense, Knox.

2:46Of course not, that's why we're demonstrating this.

2:48So let's delete this configuration out.

2:50Now give it a commit check and at a minimum,

2:53the configuration check succeeds and now my customer 1

2:56has the ability to actually be routed between VLANs

2:59on this particular bridge.

3:00We may not want to have our customers being routed

3:02themselves, but there are scenarios

3:03in the course of service providers

3:05where we may have layer 3 interfaces that we

3:08want to perform bridging and routing this way.

3:10You actually see this in JNCIA service provider

3:13content when you go to deploy multi-chassis link aggregation,

3:17specifically using the ICCP protocol.

3:20Fascinating stuff, and I'd really

3:21encourage you to check it out.

3:22So this is how to deploy inter-VLAN

3:24routing on an MX Series rather.

3:26I hope this has been informative for you,

3:27and I'd like to thank you for viewing.

0:00[MUSIC PLAYING]

0:05So we've covered the Enterprise, we've

0:06covered the Service Provider.

0:08Now do it in the Data Center, that's what we're here to do.

0:10When you're working in a data center,

0:12you're more likely to encounter the Juniper QFX Series switch.

0:16And a switch is still a switch at the end of the day,

0:18so a lot of the stuff that you've seen on the EX Series

0:21switch is really applicable to the QFX Series switch.

0:24However, there are some slightly different commands

0:27for the QFX Series switch than the EX Series switch

0:29and I just wanted you to be aware of that.

0:31So what we're going to see here in this Nugget

0:33is a lot of stuff that you've already seen, probably

0:35in the EX Series switch, but just

0:37a slightly different command.

0:38And I'll call it out when we get to that point.

0:40So here's how we go configuring VLANs, access,

0:43trunk ports, and SVIs, all on a QFX Series switch.

0:46Now we're going to talk about one

0:47of the big whoppers in the Juniper lab and virtualization

0:51world, and that is the QFX Series switch here.

0:54This is what's used in the data center world,

0:56and this is going to be your primary usage when you start

0:58going into JNCIP Data Center.

1:01That being said, it is a good way

1:02to get some hands-on experience with data center technologies.

1:05Now, a lot of the stuff that you're looking at here

1:07is part of the Spanning Tree Protocol learning

1:10in skills and Nuggets that are coming up

1:12in the JNCIS playlists.

1:14And we do use the QFX Series routers

1:16to perform that because it's just an easier way

1:18to lab a bunch of different switches.

1:19But here we go.

1:20We're going to check out how to perform these configurations

1:22on the QFX switch.

1:24Now, it does take a while to mount and boot these devices

1:27up because they are whoppers.

1:28So I'm going to sit back and let it boot up here

1:30for a few minutes, and we'll come back to it once we're

1:32on the command line and we can get logged

1:34in to this QFX series switch.

1:36All right, here we are on the command line.

1:37It is booted up.

1:38It still may take a minute to recognize the packet forwarding

1:41engine because that's just the nature of these QFX devices.

1:44But let's get logged in here.

1:44Let's see.

1:45Just going to log in, type in the password.

1:47Oh-- it's struggling here today.

1:51One more time.

1:52There we go.

1:53OK, so I'm finally on the command line of this QFX Series

1:56device.

1:57Let's go into the configuration mode,

1:58and we're going to do the exact same things

2:00that we've been doing.

2:00Let's mimic what we did when we did this for the EX Series

2:04switch.

2:05We had HR, accounting, IT, and a C-suite executive.

2:08We'll do the same things here.

2:10I'll say set VLANs--

2:10try it one more time because I keep getting syslog messages.

2:13There we go.

2:13Set VLANs then we'll say HR and VLAN ID.

2:17Exact same configurations as we did before.

2:20The VLAN ID was 4 for this one.

2:22We'll set VLANs for the IT VLAN, and we'll set the VLAN ID of 5.

2:27And I'm just going to stop there because that's

2:29all we need in order to demonstrate

2:31how to configure these items on a QFX Series switch.

2:34Where it starts to shake up a little bit,

2:35and I mean just a tiny little bit,

2:38is when we go into configuring the interfaces themselves.

2:40First of all, the EX Series switches,

2:42if you're an astute observer, you'd

2:43notice these are actually using 10 gig Ethernet interfaces.

2:47So the commands with GE are gone.

2:49Now we're actually using XE.

2:50Let's pick on xe-0/0/0 here and maybe xe-0/0/4 because I see

2:56my xe-0/0/0 would be an access port connecting to this host,

2:59but xe-0/0/4 may be a trunk port connecting to an upstream

3:03switch.

3:04So we'll say set interfaces xe-0/0/0 unit 0,

3:08and then the family here is Ethernet switching,

3:11just like it was on the EX Series switch.

3:14But this is where the one tiny command is a little bit

3:17different.

3:17Xe-0/0/0, we knew we wanted it to be an access port.

3:21The command on the EX Series switch was port mode, right?

3:24Well, we don't have a port mode on these 10 gig interfaces.

3:27We have an interface mode.

3:29Isn't that interesting?

3:30We had port mode, then we had, on the MX Series routers,

3:32we had interface type, and now on the 10 gig interfaces

3:36on the QFX Series switches, we have interface mode.

3:40And there's a syslog message again, throwing me off.

3:42Let's hit Up, and we've got interface mode.

3:44We're going to set this to be an access port.

3:46Now if I hit Up, we're going to set the VLANs.

3:48And again, the command is just like before, VLAN-members.

3:52Just like on the EX Series switch,

3:54we identify these by name.

3:56But because I haven't committed my configuration yet,

3:58I don't actually see the VLANs listed above.

4:02So I will have to explicitly type these out instead of tag

4:04completing them.

4:05So I'll say HR just for good measure here.

4:07And now if I say show interfaces xe-0/0/0,

4:11there's my configuration.

4:12Oh, it looks like I already had data on this one

4:14from a previous configuration.

4:15Let's delete that out.

4:16Unit 0, delete interfaces xe-0/0/0 unit 0,

4:21family Ethernet switching, VLAN members, data.

4:24Now, before I actually hit Enter, why do you

4:27think I want to delete data here out of this configuration?

4:30(SINGING) do-do-do.

4:31Because we set this to be access.

4:33And since we have an access port here,

4:35we can't have two VLANs associated with one access

4:38port on the Juniper platform.

4:39So I'll delete the data member out,

4:41and then say show interfaces xe-0/0/0.

4:44And now we have just the HR configuration.

4:47Now I want to configure the trunk port on the other end,

4:50going towards xe-0/0/3.

4:51So I'll say set interfaces xe-0/0/3, unit 0,

4:56family Ethernet switching.

4:57Again, my interface mode is going to be a trunk.

5:00Then under Ethernet switching, I can specify my VLAN members

5:05in an array.

5:06So I'll say HR and IT, enclose those brackets.

5:10And now if I say show interfaces xe-0/0/3.

5:13Oh, it looks like I already had the all VLANs allowed

5:17to traverse over this trunk port as a previous configuration.

5:20That's another good talking point.

5:22On the EX Series and QFX Series switches,

5:25instead of explicitly typing out every single VLAN,

5:28if you do want it to be trunked across that entire port,

5:31we can specify it right there with just an all,

5:33and that's allowable.

5:34So all of those VLANs would be trunked across it.

5:37And now with that being said, we can create the actual VLAN

5:41interfaces themselves.

5:42Yet this is another minor way that the QFX Series

5:45deviates from the EX Series.

5:47On the EX Series switches, we created the VLAN interface.

5:50On the MX Series, we created the IRB interface.

5:53The QFX Series also needs an IRB interface

5:57in order to create this configuration,

5:59even if the command that we type on the EX Series is the same.

6:03Watch this.

6:03It's going to be set interfaces IRB unit 4,

6:06to map to the HR VLAN, I'll say family inet address 192.168--

6:12actually let's give it the IP address 10.0.4.1/24.

6:16Then I'll hit up.

6:17We'll do the exact same thing for unit 5,

6:20which was the IT VLAN.

6:23And now what I'll say is, I'll say set VLANs HR, layer 3

6:27interface, exact same command that we

6:29did with EX Series devices.

6:31But now I'll say irb.4.

6:34If I hit Up, I can set the IT interface to be

6:37associated with IRB unit 5.

6:40If I say show VLANs, I see how the configuration is now

6:43set up.

6:44If I commit check this, it honestly

6:47may fail out because of this whole virtualization

6:49thing where it's stuck on the line card.

6:51It doesn't-- oh there it goes.

6:51It finally said it succeeded.

6:53I've been sitting here waiting for a while.

6:54OK, so it does check out.

6:56The configuration is good.

6:57So now we configured VLANs on the QFX appliance,

7:00identical to what we did with the EX Series switch.

7:03Then we configured the actual ports themselves.

7:06It's kind of a mix of both.

7:07We have the Ethernet switching family,

7:10but we're specifying an interface mode instead

7:12of a port mode.

7:13Then we configured Switched Virtual Interfaces

7:15and inter-VLAN routing.

7:17The actual Switched Virtual Interface

7:19is configured under the IRB, or the integrated

7:22routing and bridging interface, as opposed to the VLAN

7:25interface.

7:25This was much closer to what we saw on the MX Series switches.

7:28But then we configured the VLANs themselves

7:30to have a layer 3 interface, just like we

7:32did on the EX Series switches.

7:34So the QFX Series switch, the reason why I saved it for last,

7:37is it's kind of a blend between what

7:39happens on the EX Series switch and the MX series router.

7:42So that's been understanding how to deploy switching on the QFX

7:45appliances.

7:46I hope this has been informative for you,

7:47and I'd like to thank you for viewing.

0:05So there you have it.

0:06There's the Juniper switching journey,

0:08and you're now acclimated to how Juniper approaches layer 2.

0:12It's not terribly different from other vendors

0:14until you start getting into the switch virtual interfaces.

0:17VLAN is still a VLAN, and a trunk port

0:20is still a trunk port and an access port isn't access port.

0:22But then when you attach those interfaces to the VLANs

0:26and then the VLANs to the switch virtual interface,

0:28it can get a little fuzzy the first couple

0:30of times you do it.

0:31Trust me after you've typed those commands a few 100,000

0:33times like I have, you'll be just on autopilot,

0:36and you'll just truly understand how Juniper

0:38approaches layer 2 switching.

0:40So that's been how to handle layer 2 switching

0:42on EX series, EMX series, and QFX series devices.

0:45I hope this has been informative for you,

0:47and I'd like to thank you for viewing.