Configuration Basics · Topic 3 of 5

Interfaces and Configuration Groups

Learn Junos interface naming, physical and logical properties, units and families, and configuration groups with apply-groups for JNCIA-Junos JN0-106.

  • 5 min
In a nutshell
  • Interface names are type-FPC/PIC/port, numbered from 0; .n is the logical unit.
  • ge is 1 Gbps, xe is 10 Gbps, et is 25 Gbps and faster, such as 40 or 100 Gbps.
  • fxp0, em0 and me0 are management interfaces; lo0 is the loopback.

What it is

Junos names every interface by its type and its position in the hardware, and splits it into a physical part and one or more logical units. Addresses and protocol families always go on a logical unit, never on the physical interface.

A configuration group is a block of configuration you write once under [edit groups] and then apply with apply-groups. It saves typing and keeps repeated settings consistent.

Physical interfacege 0/0/1Logical unitunit 0FamilyinetAddress10.1.1.1/24

How it works

Interface naming

A network port name has the form type-FPC/PIC/port, for example ge-0/0/1. Numbering starts at 0.

PartMeaning in ge-0/0/1
geInterface type: Gigabit Ethernet
First 0FPC (Flexible PIC Concentrator) slot
Second 0PIC (Physical Interface Card) slot
1Port number on the PIC
.0 in ge-0/0/1.0The logical unit number

Interface types

TypeExamplesPurpose
Network (transit)ge, xe, etGigabit, 10 Gigabit, and 25 Gigabit or faster Ethernet ports that forward traffic
Managementfxp0, em0, me0Out-of-band management; name depends on the platform
Loopbacklo0Always up; used for router ID, management and protecting the Routing Engine
Aggregated Ethernetae0, ae1Several physical links bundled into one
Integrated routing and bridgingirbLayer 3 interface for a VLAN
Tunnelgr, ipGRE and IP-IP tunnels

Management and loopback interfaces have no FPC/PIC/port number. Internal interfaces also exist for communication between the Routing Engine and the Packet Forwarding Engine; you see them in show interfaces terse but do not configure them for traffic.

Physical and logical properties

Physical propertiesLogical properties
descriptiondescription
mtufamily (inet, inet6, mpls, iso, ethernet-switching)
disableaddress under a family
vlan-taggingvlan-id on a tagged interface
Link speed and duplex settingsFirewall filters applied to a family
encapsulation

A logical unit needs at least one family to carry traffic. On an untagged Ethernet port you use a single unit, unit 0.

[edit interfaces]
user@R1# set ge-0/0/1 description "Link to R2"
user@R1# set ge-0/0/1 unit 0 family inet address 10.1.12.1/24

user@R1# set ge-0/0/2 vlan-tagging
user@R1# set ge-0/0/2 unit 100 vlan-id 100
user@R1# set ge-0/0/2 unit 100 family inet address 10.1.100.1/24

user@R1# set lo0 unit 0 family inet address 192.168.255.1/32

With vlan-tagging, each unit maps to one VLAN through vlan-id. The unit number and VLAN ID do not have to match, but matching them is easier to read.

disable shuts the physical interface down administratively. In show interfaces terse, the Admin column then shows down while the Link column shows the physical state.

Configuration groups

ElementPurpose
[edit groups <name>]Holds the reusable configuration
apply-groups <name>Makes a hierarchy level inherit the group
apply-groups-except <name>Stops a lower level inheriting a group applied above it
Wildcards such as <ge-*>Match many names inside a group
display inheritance after the pipeShows the configuration with the inherited statements filled in
[edit]
user@R1# set groups JUMBO interfaces <ge-*> mtu 9000
user@R1# set apply-groups JUMBO

Every ge- interface that is configured elsewhere now inherits mtu 9000. Wildcards match only objects that already exist in the configuration, so the group does not create new interfaces.

groups JUMBOwildcard ge interfacesapply groupsInherited byeach configured ge interfaceVisible withdisplay inheritance

Inheritance rules

RuleResult
A statement configured directlyOverrides the same statement from a group
Several groups in apply-groupsThe group listed first takes priority
show in configuration modeHides inherited statements unless you add the display inheritance pipe option

The special groups re0 and re1 hold settings, such as the host name and management address, that differ between two Routing Engines. Each Routing Engine applies only its own group.

Exam tip

When a value in the running device does not match what you see in show, check for groups with show | display inheritance. The value may be inherited.

Common mistakes

Putting an address on the physical interface. Addresses go under unit <n> family inet, never directly under ge-0/0/1.

Misreading the name. In ge-1/2/3, 1 is the FPC, 2 the PIC and 3 the port. The .0 after a name is the logical unit.

Expecting a group to work without apply-groups. Configuration under [edit groups] does nothing until a hierarchy level applies it.

Thinking a wildcard group creates interfaces. <ge-*> matches only interfaces that are already configured.

Watch out

A statement configured directly always beats the group. If an interface has its own mtu, the group value is ignored for that interface.

What to remember for the exam

  • Interface names are type-FPC/PIC/port, numbered from 0; .n is the logical unit.
  • ge is 1 Gbps, xe is 10 Gbps, et is 25 Gbps and faster, such as 40 or 100 Gbps.
  • fxp0, em0 and me0 are management interfaces; lo0 is the loopback.
  • Protocol families and addresses are logical properties under a unit.
  • vlan-tagging on the physical interface plus vlan-id per unit for tagged ports.
  • Groups are defined under [edit groups] and used with apply-groups.
  • Direct configuration overrides groups; the first group listed wins over later ones.

Check yourself

  • In xe-2/1/0.5, what is the PIC number and what is the unit?

    The PIC is 1, and the logical unit is 5.

  • Where is an IPv4 address configured on an interface?

    Under a logical unit and family, for example set interfaces ge-0/0/1 unit 0 family inet address 10.1.1.1/24.

  • How do you see statements that a group adds to the configuration?

    Use show | display inheritance in configuration mode, or the same pipe after show configuration.

Topic 3 of 5 in Configuration Basics

Test yourself on Configuration Basics

The full Juniper JNCIA-Junos JN0-106 question bank has 1,155 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.