There's no point having a network device without interfaces.
In this video, we're going to take a look at both physical and virtual interfaces.
Personally, if we want to see a list of our interfaces,
use show interfaces terms.
The output we're looking at here is from a switch.
So we've got 12 or so
some interfaces have an easy switch label next to them.
These are regular layer two ports.
Others have an iiNet next to them.
These are interfaces with IP addresses as you can see,
just like any other vendor.
We can see if an interface is admin up or down
and line up or down.
Admin down would mean the interface has been manually disabled.
Line down usually means that there's nothing plugged in
most of the interfaces that we can see here.
Our physical also called ifdef
We will also see logical interfaces or if else.
And we'll talk about if and if later
for our physical interfaces.
The first few letters are the interface type.
For example, GE is gigabit Ethernet
and ICSI is ten gig.
These don't always make a lot of sense.
Unfortunately, VLAN and IOB is some of the logical interfaces
that will come across both of these types.
Mapper VLAN to an IP address
The interface name has three numbers.
The first is called the FP or Flexible Pick Concentrator.
This is a fancy name for a line code.
Some devices allow you to add more speakers to get more ports.
Next is the module or slot.
If you have a fixed format, switch,
you might have some RJ 45 ports and some SFP ports.
These will both use different module numbers.
And finally, the third number is the port number.
Interface names
get a little tricky when SFP are involved.
SFP can have different speeds.
As you know, one may be gig while another may be one gig.
So on this, which this interface could begin with a G
if the one guy SFP or XY, if it's a ten gig SFP.
However, on some routers SFP will always use ICSI.
Does that sound confusing?
It is. Thanks. Juniper
in this example we have a ten gig SFP in PHP
zero module one port one.
Therefore the name is ICSI zero. 11.
Each device has an out-of-band management interface.
Unfortunately, the names aren't the same for all devices.
Routers will generally have p zero as a out-of-band
management port, while switches will often have m e0.
But if you connect several physical switches into a virtual chassis
you will now have a virtual management port called the MI zero.
If you're
wondering, a virtual chassis is what Cisco would call a switch stack.
Each switch in the virtual chassis is a separate PC or line code.
In addition to these ports, there are several internal ports.
We'll have a look at some of these in video 12.
You will also find that Juniper has virtual interfaces for special purposes.
These are called permanent interfaces.
These are usually mapped to a special feature like PIM for multicast.
These interfaces will exist whether you're using that interface or not.
Some interfaces can be unnumbered.
This might be a point to point interface.
It has no IP address assigned in order to conserve IP space.
In this case, the switch or router
will try to use an IP from a loopback interface
or the IP of a primary interface, which we can configure.
There's quite a
few quiz questions in this video, so I'm breaking it into a few sections.
Remember to pause a video or come back later to work these out.
Let's look at the interface configuration.
Everything is hierarchical in Junos and interfaces are no exception.
First, we have the interface itself.
If the interface we are configuring is physical,
then this is where we can figure out physical parameters.
This includes duplex settings, link speed, MTU, and so on.
This is also where our description goes.
Most configuration goes within a container called a unit.
A unit is a logical interface
The AFL that we spoke about earlier.
All logical configuration goes here
and all interfaces must have them.
Some devices like regular switchboards will only have one unit.
Some interfaces like PBP and HDL-C
require that the unit number is always zero.
In other cases, we can have multiple units per interface.
In fact, this is how we create sub interfaces based on VLANs
Under the unit goes a family.
The family is the type of addressing that's used like IPV
for IPv6 or Ethernet
Every unit must have at least one family member.
So an unmet family means an IPV four address will be applied to the interface
and Ethernet switching family will contain VLAN information.
Let's try this out on a loopback interface.
This is a virtual interface, but unlike iOS, we can only have one loopback.
We set the l0 zero interface with unit number 100
and the INET family
then an IPv4 address using side annotation.
We never use subnet masks in Junos, which is correct.
And for
completeness, we set a description on the interface.
This doesn't have to be inside the unit.
Now here's a quick shortcut for you.
You can simply put a dot followed by the unit number after the interface.
You may be comfortable
with this type of notation if you've used iOS sub interfaces before.
And while we're talking about tips, I have another one for you.
Let's say the loopback interface was supposed to be Unit zero, not 100.
Rather than remove the conflict and start again,
we can just use the rename command.
If we want multiple IPS on the same interface, that's fine too.
Geno's is different to wireless in this case, In iOS,
you have to make additional IP addresses secondary.
Juniper has the concept of primary and preferred addresses.
Any IP that's not configured as primary or preferred
is automatically a secondary address.
If you have more than one IP, one of them will be primary.
The primary IP is used for traffic that is sent to a remote network.
The preferred IP is used for traffic being sent to the local network.
If we don't choose that primary and preferred IP is ourselves,
the lowest IP on the interface will be selected.
Let's just add a primary and secondary IP to our lab.
Browser. Now,
Of course,
we need to remember to commit our changes when we're done here.
I'm using Commit and Quit, which leaves configuration mode.
If the committee is successful
to troubleshoot an interface, the simple option is to run
show interface.
We can see if the interface is up
We can see the M2 speed and duplex, and we can see
the input and output rates in bits per second and packets per second.
If that's
not enough information for you, add the extensive keyword to the end.
This shows us any Mac errors, interface
alarms, and so on.
If that's still not enough,
you can use a special loopback adapter to test for packet loss.
And when I say loopback in this case,
I mean a physical device that you can plug into the interface.
We disconnected.
We added ether options loop back setting to the interface that we want to test.
There's a link in the description if you want to learn more.
If you need to disable interface.
Just set the disable key word on the interface itself.
This is the same thing as using a shut down on a Cisco router.
When we're ready to bring it back up, we simply delete the disable setting.
Here's another trick for you.
We can also use the deactivate command to disable an interface.
The interesting part, though, is that we can apply this
to any part of config, not just to interfaces
This way we can still see the config, but Junos will ignore it.
And now a few more questions to get you thinking.
If you're having a hard time remembering some of these concepts,
you might want to consider using flashcards.
You can create your own, or you can get
some pre-made cards from the member section of the website.
Let's turn our attention to villains.
To create a villain.
We choose a villain name as well as a villain ID
We can also put a description on the villain if we want to
After committing our changes,
we can see a full list of villains with show villains.
We can configure a layered
two Ethernet interface as an access port or as a trunk port.
Under the Ethernet switching family.
The exact command you will use
will depend on how old your version of Geno's is
now that's configured.
We can add members to the port
We can add one at a time,
or we can use square brackets to define a list of VLANs
Just remember to put spaces
between each entry
Configuring an access port is just the same,
except we only have a single VLAN
I have another similar trick for you now.
We've got the 000 report configured.
We can copy the configuration to other ports using the copy command.
This can be used anywhere in config though, not just on interfaces devices
Before I show you the next
trick, I'm going to set up some descriptions on a few interfaces.
See here that get 000001.
Now have the description workstations
so when we copy interfaces, we might also want to consider using replace pattern.
This uses a pattern that we want to match
and a pattern that we want to replace it with.
In this example, we're going to change the interface description.
This is a simple example, but we could have used regex to make it fancy
if we want.
In the real world we might use replace pattern to change
the IPS on each interface, which would avoid IP conflicts
VLANs also allow us to create sub interfaces.
To do this we enable VLAN tagging on the physical port.
Notice that
this part is not configured under a unit number.
If we already have a unit configured,
we can remove them or reconfigure them.
Personally, I like the unit number to match the VLAN we're using
under the unit.
We can then apply the villain ID and assign an IP
address as normal
It looks like I left the address key word out,
but I'm sure you can follow what I'm trying to do.
Earlier I mentioned VLAN or IAB interfaces,
which map an IP address to a VLAN.
If you're coming from a Cisco background, you may have heard of this
being called an SVP.
VLAN interfaces and IAB interfaces are the same thing.
VLAN is just use on older versions of Junos
while IAB is used on newer versions.
Quite simply, we configure the villain or IAB interface
with one or more units and assign an IP to each one
then onto the villain configuration.
We map the villain name to the virtual interface and unit number.
We'll see this further in action in video for when we're going to configure a DHCP.
So what if we're connecting a phone
to a switch port There's three parts to this.
We need a voice VLAN.
We need power over Ethernet and we need LDP.
So step one is to define a villain that we can use for voice.
This is exactly the same as we did before.
Step two is to assign this to one or more interfaces.
This is not configured on the interface itself.
Instead, it's under switch options VoIP
or Ethernet switching options, VOIP
depending on whether you have a newer or an older switch
What we're really doing here is mapping
a switch port to a VLAN for voice usage.
We can still keep a data VLAN on the interface itself.
Next, we try to
power up any connected phones using power over Ethernet.
This is so very simple to configure.
Under the power hierarchy, we just list the ports we want play enabled on.
Sometimes it's simpler just to enable it on all ports.
And finally, phones need a way to configure themselves
Generally speaking, this is done using CDP
or LDAP, CDP, Cisco specific.
So we're going to use the vendor neutral option.
LDAP Well, technically, we're going to use LCP Med,
which is LDAP with some additional extensions just like play.
This is quite simple.
Under the protocols hierarchy, we can enable
LDAP Med on whichever interface we choose or on all of them at once.
Oh, and if you're wondering.
Yes, we can connect Cisco phones to Juniper switches
as long as the phone support low DPI Med, they're fine.
LCP configuration is one of the tasks in the Associated Lab.
If you want to check that out, the link is in a description.
Here's another quick tip that might help.
You can use the annotate commands to add
comments to any part of the configuration.
This makes it easier to see what's going on later.
If you're troubleshooting
Just a few more quiz questions for you.
You're doing really well.
Now you know all about interface types
and how they can be used as well as V line configuration.
Click the video shown here to start video for where
we'll look at configuring a server Juniper style.