JNCIA-Junos Study Guide—Part 1

You can save the active configuration as the rescue configuration using the CLI’s operational-mode request system
configuration rescue save command. If a rescue configuration already exists, the request system
configuration rescue save command replaces the rescue configuration file with the contents from the active
configuration. To manually delete the current rescue configuration, issue the request system configuration rescue
delete command.
Once saved, you can load the rescue configuration by entering the rollback rescue configuration mode command.
Because the rollback operation only replaces the contents of the candidate configuration, you must issue commit to activate
the configuration.

Interface Overview
Interfaces are primarily used to connect a device to a network; however, some interfaces are used to provide a service or a
specific function for the system on which it operates. On platforms running the Junos OS, several types of interfaces exist,
including:
• Management interfaces: Used to connect the device running the Junos OS to a management network. The actual
designation for this interface is platform-specific; examples include fxp0 and me0.
• Internal interfaces: Used to connect the control and forwarding planes. The actual designation for this interface is
platform-specific; examples include fxp1 and em0.
• Network interfaces: Used to provide media-specific network connectivity. Some media examples include Ethernet,
SONET, Asynchronous Transfer Mode (ATM), T1, and DS3. We cover examples of network interfaces on subsequent
pages within this chapter.
• Services interfaces: Used to provide one or more user-configurable services such as encryption, tunneling, and link
services. Services interfaces can be provided through a physical services interface card or through software.
Services interfaces provided through a PIC do not have ports or media associated with them, but have two-letter
interface type designations as shown in the list that follows (actual coverage of the services provided by these
interfaces is beyond the scope of this class):
– es: Encryption interface;
– gr: Generic route encapsulation tunnel interface;
– ip: IP-over-IP encapsulation tunnel interface;
– ls: Link services interface;
– ml: Multilink interface;
– mo: Passive monitoring interface;
– mt: Multicast tunnel interface;
– sp: Adaptive services interface; and
– vt: Virtual loopback tunnel interface.
• Loopback interfaces: Used to provide a constant and dependable hardware-independent interface. The loopback
interface uses the lo0 designation on all platforms running the Junos OS. Use the lo0 interface in conjunction with
routing protocols to facilitate routing in a redundant environment that is independent of the individual physical
links within that environment. You can configure a single logical unit for the lo0 interface for each routing instance.
Each logical unit associated with a given routing instance can, however, have multiple configured IP addresses.

© 2012 Juniper Networks, Inc. All rights reserved. Initial Configuration • Chapter 3–9