In part one we discussed logging into Junos, changing the root password, creating a user account, and enabling remote access.
In part two of getting started with Junos, we will look at interface configuration.
The Quick Answer
If you’re looking for a quick answer, the following is the basic format of the command.
set interfaces <<Interface>> unit <<Unit-Number>> family <<address-family>> address <<address/prefix-length>>A specific example might be:
set interfaces ge-0/0/2 unit 0 family inet address 192.168.51.1/24Read on to see more detailed examples.
Interface Naming
The naming for interfaces in Junos is typically the hardware type, followed by three numbers, a period (.), and one final number. These numbers historically represented the FPC (slot or line card), PIC (interface module), and port (Individual interface). The number after the period is the logical unit number. All numbering starts at zero (0).
For example, ge-0/0/0 is a gigabit Ethernet interface (hardware type), located in the first physical line-card slot (slot 0), in the first interface module (module 0), in the first port (port 0).
The logical unit, or just unit, represents the logical interface. We’ll cover this more in the section on interface configuration theory further below.
Some common hardware types are listed below:
- fe – Fast Ethernet
- ge – Gigabit Ethernet
- xe – 10-Gigabit Ethernet
- et – Ethernet Interface. This usually applies to interfaces faster than 10Gbps.
- so – Sonet/SDH
- at – ATM
- ae – Aggregated Ethernet, for interfaces aggregated together in a lag, bundle, or port channel, depending on your terminology.
This naming convention makes sense for most of the larger chassis-based Junos devices. The smaller devices tend to differ a bit.
Most Junos-based switches will have the FPC number set to 0. Unless they are in a virtual chassis, in which case the FPC can be thought of as representing the switch number in the stack. The front interface ports are typically in “PIC” 0. Ports on installable modules, or higher-speed fixed ports to the side of the front panel, or on the back, are typically a non-zero PIC number.
Two helpful commands are ‘show interface terse’ and ‘show chassis hardware’, which we looked at in part one. These will help you identify what physical hardware is present in the device, and which interfaces are available for use.
You should know that the ‘show interface terse’ command only shows you interfaces that are powered on. If you have hardware that is offline, you will see it in the hardware listing, but not the interface listing.
A Brief Detour Into History
We need to discuss some older hardware for a moment to understand some of these naming conventions.
The older M and T series routers were mostly chassis-based devices. The M40e had 8 FPC slots numbered 0-7, into which a line card, called a Flexible PIC Concentrator (FPC) could be installed. The M10i, on the other hand, was a smaller device with two fixed (non-removable) FPCs built in.
Each FPC could hold either 2 or 4 Physical Interface Cards (PIC). The M40e and T640 took FPCs that held 4 PICs, while the T320 FPCs typically held 2 PICs.
Each PIC was of a certain media type. You might have a 4-port ATM PIC, a single-port Gigabit Ethernet PIC, or a 2- or 4-port Sonet/SDH PIC.
In this era, life was pretty simple. Each slot in a chassis could have an FPC installed. Each FPC could have a number of PICs installed. These PICs would provide different interface types – ATM, Sonet, Ethernet, etc. Each PIC had a number of interfaces of the same type.
The whole HW-Type-FPC/PIC/Port naming convention made complete sense.
Over time, it started to get a little confusing.
With the advent of the MX960, we started to get DPC cards or Dense Port Concentrators. Later, we started to get MPCs or Modular Port Concentrators. MPCs took MICs (Modular Interface Cards), which were basically the new PIC. The difference was that MPCs typically had two slots, and MICs were double-wide. This meant each MIC represented two PICs from an interface naming point of view.
As an example, a 20-port Gigabit Ethernet MIC would be divided into two lots of 10 interfaces. The first lot would be numbered “PIC” location 0, and the second lot would be numbered “PIC” location 1.
Even more confusingly, if the MIC was installed in the first slot of the MPC, it took PIC locations 0 and 1, but if installed in the second slot of the MPC, that same MIC would take PIC locations 2 and 3.
This is before we get to fixed-configuration DPC or MPC cards that have a fixed number of ports and don’t take a MIC at all.
This is to say that yes, until you get used to it, the interface naming can seem a little weird.
Other Interfaces
In addition to the hardware interfaces mentioned above, there are other interface types.
Most devices have a management interface which will be fxp0 on most devices, but might be me0 or em0 on some of the switching hardware.
All devices have a loopback interface, called lo0. The lo0 interface can have multiple units, but only one loopback interface unit can be in a given routing instance or logical system. This means instead of having multiple loopback interfaces with one address each, you have one lo0 interface with multiple addresses.
The loopback interface has another important function. It acts as the interface between the forwarding plane (Packet Forwarding Engine, or PFE) and the control plane (Routing Engine, or RE). Since most of the routing and control processes run on the routing engine, applying a firewall filter (ACL) on the loopback interface can control what traffic passes from the PFE to the RE.
You’ll sometimes hear this talked about as an RE protection filter.
Juniper hardware started as a one-pass architecture. A packet came in, a lookup was done, and the packet was sent out. It did not do a double lookup. This causes some issues when packets are encapsulated or tunneled, as you need one pass to remove the packet from the tunnel, and a second pass to deal with the un-encapsulated packet.
To get around this, several PICs were created to allow traffic to be sent back through the router for a second lookup. These were typically called a Tunnel Services PIC or similar name, and created additional interfaces such as lt-, vt-, pd-, pe-, gr-, and ip-. These were all a way to loop traffic back through the forwarding engine to allow for a second lookup. Most were to deal with various tunneling protocols, or for the encapsulation and decapsulation of PIM messages.
On the MX series, it is possible to configure one of the PFE engines on an MPC card to act as a tunnel services PIC, so additional hardware is not needed.
Interface Configuration – Theory
When configuring an interface in Junos, you can think of it as having three levels of configuration.
First, we have the physical interface settings which are configured directly under the interface. These include things such as the physical interface MTU, possibly speed or duplex, and similar settings.
The next level of configuration is the logical unit. These logical units can be thought of as sub-interfaces. Where a physical interface can only have one logical interface, unit 0 is used. Where multiple units are possible, the number available depends on the type of interface. Most interfaces support numbering units 0 through 16,385.
On tagged ethernet interfaces, you will often see an automatically created unit numbered 16,386 or 32767 to accept untagged packets that come into an interface.
The third level of interface configuration is the address family. This is where we configure logical properties like addresses.
Some common address families are:
- family inet – IPv4 configuration
- family inet6 – IPv6 configuration
- family ethernet-switching – Interface configuration for layer 2 switching such as access or trunk ports. This address family only allows for a single logical unit on the interface.
- family iso – Enabled without any addressing on physical interfaces, it is needed for the interface to process IS-IS routing protocol packets. The ISO address for the router is configured under the loopback interface.
- family mpls – Enabled without any addressing, it allows the interface to process MPLS labeled packets. This is typically seen on interfaces in the core of MPLS networks.
Interface Configuration – Practical
The following examples mainly consist of configuring IP or layer-3 interfaces. To configure switching interfaces, look at configuring VLANs on Junos.
GE Interface With Single Unit
In this example, we will configure an un-tagged Ethernet interface with an IPv4 address.
First, let’s check the interface and its configuration. We’ll use ge-0/0/2.
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.16386 up up
lab@MyRouter> show configuration interfaces ge-0/0/2
lab@MyRouter>The interface is up, and there is no existing configuration for the interface.
lab@MyRouter> configure
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 0 family inet address 192.168.51.1/24
[edit]
lab@MyRouter# show | compare
[edit interfaces]
+ ge-0/0/2 {
+ unit 0 {
+ family inet {
+ address 192.168.51.1/24;
+ }
+ }
+ }
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter>For this configuration, we used the address of 192.168.51.1. The subnet mask is specified using CIDR notation (/24). If this is left off, Junos assumes it should be /32. This is a common mistake for people new to Junos.
Remember, the configuration must be committed for the change to take effect. We can verify our work by running the show interface and show configuration commands we started with.
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.0 up up inet 192.168.51.1/24
multiservice
lab@MyRouter> show configuration interfaces ge-0/0/2
unit 0 {
family inet {
address 192.168.51.1/24;
}
}
lab@MyRouter>I know another device on the network is using the .10 address, so we can ping that to confirm connectivity.
lab@MyRouter> ping 192.168.51.10 count 2
PING 192.168.51.10 (192.168.51.10): 56 data bytes
64 bytes from 192.168.51.10: icmp_seq=0 ttl=64 time=359.680 ms
64 bytes from 192.168.51.10: icmp_seq=1 ttl=64 time=108.231 ms
--- 192.168.51.10 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 108.231/233.956/359.680/125.725 ms
lab@MyRouter>GE Interface With Multiple Units
Since we are using an Ethernet interface, we can make it VLAN-aware. When we turn it into a tagged interface, we also need to specify the VLAN id for each unit.
In the next steps, we will configure the interface for VLAN tagging, rename the existing unit, and add two further units. Note: I’ll also change the other end to be a trunk interface. I won’t show this here, but it was covered in Junos VLAN basics.
To be clear, adding the ‘vlan-tagging’ setting only makes the interface VLAN aware. It does not make the interface behave like a switch port. The VLAN tags are only used to identify which unit, or sub-interface, the traffic should be processed by.
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 vlan-tagging
[edit]
lab@MyRouter# rename interfaces ge-0/0/2 unit 0 to unit 51
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 51 vlan-id 51
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 52 vlan-id 52
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 52 family inet address 192.168.52.1/24
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 53 vlan-id 53 family inet address 192.168.53.1/24
[edit]
lab@MyRouter# show interfaces ge-0/0/2
vlan-tagging;
unit 51 {
vlan-id 51;
family inet {
address 192.168.51.1/24;
}
}
unit 52 {
vlan-id 52;
family inet {
address 192.168.52.1/24;
}
}
unit 53 {
vlan-id 53;
family inet {
address 192.168.53.1/24;
}
}
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2]
+ vlan-tagging;
[edit interfaces ge-0/0/2]
- unit 0 {
- family inet {
- address 192.168.51.1/24;
- }
- }
+ unit 51 {
+ vlan-id 51;
+ family inet {
+ address 192.168.51.1/24;
+ }
+ }
+ unit 52 {
+ vlan-id 52;
+ family inet {
+ address 192.168.52.1/24;
+ }
+ }
+ unit 53 {
+ vlan-id 53;
+ family inet {
+ address 192.168.53.1/24;
+ }
+ }
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter>There are a few things worth mentioning in the above output.
The vlan-tagging is configured directly under the ge-0/0/2 interface. This is because it relates to the configuration of the physical interface, rather than to a single logical unit.
The rename command is useful for renaming parts of the configuration. In this case, it saved having to delete unit 0 and re-add those details as unit 51.
Some commands can be combined. For example, when configuring unit 53, I configured the VLAN id and the IP address in the same command, rather than two separate commands.
The logical unit number and the VLAN id do not need to match, they can be different values. It is always a good idea to make them the same if you can, though, as it is more intuitive for the people operating the network.
As always, it’s a good idea to run a ‘show | commit’ before committing any changes, so you know what will be applied.
Now, we can test if this works by pinging the .10 address, which I have configured on another device.
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.51 up up inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up up inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up up inet 192.168.53.1/24
multiservice
ge-0/0/2.32767 up up multiservice
lab@MyRouter> ping 192.168.51.10 count 2
PING 192.168.51.10 (192.168.51.10): 56 data bytes
64 bytes from 192.168.51.10: icmp_seq=0 ttl=64 time=321.063 ms
64 bytes from 192.168.51.10: icmp_seq=1 ttl=64 time=113.723 ms
--- 192.168.51.10 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 113.723/217.393/321.063/103.670 ms
lab@MyRouter> ping 192.168.52.10 count 2
PING 192.168.52.10 (192.168.52.10): 56 data bytes
64 bytes from 192.168.52.10: icmp_seq=0 ttl=64 time=315.933 ms
64 bytes from 192.168.52.10: icmp_seq=1 ttl=64 time=118.301 ms
--- 192.168.52.10 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 118.301/217.117/315.933/98.816 ms
lab@MyRouter> ping 192.168.53.10 count 2
PING 192.168.53.10 (192.168.53.10): 56 data bytes
64 bytes from 192.168.53.10: icmp_seq=0 ttl=64 time=550.220 ms
64 bytes from 192.168.53.10: icmp_seq=1 ttl=64 time=126.148 ms
--- 192.168.53.10 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 126.148/338.184/550.220/212.036 ms
lab@MyRouter>Changing An Interface IP Address
Sometimes we need to re-number an interface, changing its IP address.
In this example, we will look at a common mistake and how to fix it.
Following on from the tagged Ethernet example above, I will add unit 54 but leave the subnet portion off of the address I configure.
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 54 vlan-id 54 family inet address 192.168.54.1
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter> ping 192.168.54.1 count 2
PING 192.168.54.1 (192.168.54.1): 56 data bytes
64 bytes from 192.168.54.1: icmp_seq=0 ttl=64 time=0.117 ms
64 bytes from 192.168.54.1: icmp_seq=1 ttl=64 time=0.090 ms
--- 192.168.54.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.090/0.104/0.117/0.014 ms
lab@MyRouter> ping 192.168.54.10 count 2
PING 192.168.54.10 (192.168.54.10): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
--- 192.168.54.10 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
lab@MyRouter> show configuration interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/32;
}
lab@MyRouter>We can ping our address, 192.168.54.1, but can’t ping the .10 address. The error is no route to host. Checking the interface configuration, we can see that we’ve forgotten to specify it as a /24, so Junos has assumed the address should be a /32.
Your first thought might be to repeat the command specifying the correct address. Let’s see how that goes.
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 54 vlan-id 54 family inet address 192.168.54.1/24
[edit]
lab@MyRouter# show interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/32;
address 192.168.54.1/24;
}
[edit]
lab@MyRouter#Because Junos supports multiple addresses of the same family on an interface, it accepts the second address and adds it to the configuration. This is not what we want in this example.
Because we do not want to commit this change, we can issue a ‘rollback 0’ to discard the changes we have made, before we try again.
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2 unit 54 family inet]
address 192.168.54.1/32 { ... }
+ address 192.168.54.1/24;
[edit]
lab@MyRouter# rollback 0
load complete
[edit]
lab@MyRouter# show | compare
[edit]
lab@MyRouter# show interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/32;
}
[edit]
lab@MyRouter#We have two options. We can either delete the address and add the correct one, or we can use rename to change the existing address.
I’ll show both below, starting with the delete option.
[edit]
lab@MyRouter# show interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/32;
}
[edit]
lab@MyRouter# delete interfaces ge-0/0/2 unit 54 family inet address 192.168.54.1/32
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 54 family inet address 192.168.54.1/24
[edit]
lab@MyRouter# show interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/24;
}
[edit]
lab@MyRouter#I have not committed the configuration, so the router’s behavior has not been changed.
Instead of deleting just the address, I could have deleted the entire ‘family inet’ statement, since nothing else is configured there yet.
Let’s roll back the config and try the rename option.
[edit]
lab@MyRouter# rollback 0
load complete
[edit]
lab@MyRouter# show interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/32;
}
[edit]
lab@MyRouter# rename interfaces ge-0/0/2 unit 54 family inet address 192.168.54.1/32 to address 192.168.54.1/24
[edit]
lab@MyRouter# show interfaces ge-0/0/2 unit 54
vlan-id 54;
family inet {
address 192.168.54.1/24;
}
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2 unit 54 family inet]
+ address 192.168.54.1/24;
- address 192.168.54.1/32;
[edit]
lab@MyRouter# commit
commit complete
[edit]
lab@MyRouter#After using the rename command, I’ve shown the interface itself so you can see how it is currently configured. The ‘show | compare’ also clearly shows one address being removed and another being added. Since the address is now correct, we can commit the change so it takes effect.
Shutting Down Or Disabling An Interface
To shut down, or disable, an interface in Junos, we need to set the ‘disable’ statement.
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.51 up up inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up up inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up up inet 192.168.53.1/24
multiservice
ge-0/0/2.54 up up inet 192.168.54.1/24
multiservice
ge-0/0/2.32767 up up multiservice
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 disable
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2]
+ disable;
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 down down
ge-0/0/2.51 up down inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up down inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up down inet 192.168.53.1/24
multiservice
ge-0/0/2.54 up down inet 192.168.54.1/24
multiservice
ge-0/0/2.32767 up down multiservice
lab@MyRouter> From the above output, you can see the interface changes to the down state.
To re-enable the interface, we need to remove the ‘disable’ statement, we do this with the delete command.
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# delete interfaces ge-0/0/2 disable
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2]
- disable;
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.51 up up inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up up inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up up inet 192.168.53.1/24
multiservice
ge-0/0/2.54 up up inet 192.168.54.1/24
multiservice
ge-0/0/2.32767 up up multiservice
lab@MyRouter>Adding A Description To An Interface
Descriptions are added by setting the description statement. If you want to use spaces, the description must be enclosed in quote marks.. Descriptions can be set at both the physical interface and the unit level.
lab@MyRouter> show interfaces descriptions
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 description "Description for Physical Interface - e.g. Connected to Device/Port"
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 51 description "Description for Logical Interface - e.g. Connected to VLAN 51 - Test Servers"
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2]
+ description "Description for Physical Interface - e.g. Connected to Device/Port";
[edit interfaces ge-0/0/2 unit 51]
+ description "Description for Logical Interface - e.g. Connected to VLAN 51 - Test Servers";
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.51 up up inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up up inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up up inet 192.168.53.1/24
multiservice
ge-0/0/2.54 up up inet 192.168.54.1/24
multiservice
ge-0/0/2.32767 up up multiservice
lab@MyRouter> show interfaces descriptions
Interface Admin Link Description
ge-0/0/2 up up Description for Physical Interface - e.g. Connected to Device/Port
ge-0/0/2.51 up up Description for Logical Interface - e.g. Connected to VLAN 51 - Test Servers
lab@MyRouter>Something to be aware of is that the ‘show interfaces descriptions’ command only shows interfaces with a description set. Interfaces without a description are not displayed in the output.
Configuring An IPv6 Address
The most basic IPv6 configuration is to enable family inet6 on an interface.
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 54 family inet6
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2 unit 54]
+ family inet6;
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter> Although we have not configured an actual address, once IPv6 is enabled the interface will get a link-local address.
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.51 up up inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up up inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up up inet 192.168.53.1/24
multiservice
ge-0/0/2.54 up up inet 192.168.54.1/24
inet6 fe80::5200:0:360b:3/64
multiservice
ge-0/0/2.32767 up up multiservice
lab@MyRouter> If we configure an address, we’ll see the interface now has two IPv6 addresses. The link-local address and the one we have specified.
lab@MyRouter> configure
Entering configuration mode
[edit]
lab@MyRouter# set interfaces ge-0/0/2 unit 54 family inet6 address 2001:db8:54::1/64
[edit]
lab@MyRouter# show | compare
[edit interfaces ge-0/0/2 unit 54 family inet6]
+ address 2001:db8:54::1/64;
[edit]
lab@MyRouter# commit and-quit
commit complete
Exiting configuration mode
lab@MyRouter> show interfaces ge-0/0/2 terse
Interface Admin Link Proto Local Remote
ge-0/0/2 up up
ge-0/0/2.51 up up inet 192.168.51.1/24
multiservice
ge-0/0/2.52 up up inet 192.168.52.1/24
multiservice
ge-0/0/2.53 up up inet 192.168.53.1/24
multiservice
ge-0/0/2.54 up up inet 192.168.54.1/24
inet6 2001:db8:54::1/64
fe80::5200:0:360b:3/64
multiservice
ge-0/0/2.32767 up up multiservice
lab@MyRouter>Summary
We have looked at interface naming and some basic interface configurations.
For more information on interfaces, you can look at the following: