Certain hardware platforms run an upgraded FreeBSD kernel (FreeBSD 10.x or later) instead of FreeBSD 6.1. Juniper Networks devices that run Junos OS with upgraded FreeBSD have two separate volumes:
dev/gpt/junos(/junosfor short) volume that is used to run Junos OS and to store the configuration and log files
dev/gpt/oam(/oamfor short), an Operations, Administration, and Maintenance (OAM) volume that is used to store a complete backup of Junos OS and the configuration.
In case of damage to the device’s software or failure of the/junosvolume, you can use the backed up software and configuration stored in the/oamvolume to boot the system and restore Junos OS with the recovery configuration. To perform this reboot and restore the configuration, the/oamvolume must have all of the information required to provide the system with a running configuration. This information is provided by the recovery snapshot, created using therequest system snapshot recoverycommand.
Note: You need console access to perform the following procedure to recover Junos OS.
To recover Junos OS by using the recovery snapshot stored in the/oamvolume:
Power off the device, such as a router or a switch, by pressing the power button on the front panel.
Connect and configure the management device, such as a PC or a laptop, as follows:
Turn off the power to the management device.
Plug one end of the Ethernet rollover cable supplied with the device into the RJ-45–to–DB-9 serial port adapter supplied with the device.
Plug the RJ-45–to–DB-9 serial port adapter into the serial port on the management device.
Connect the other end of the Ethernet rollover cable to the console port on the device.
Turn on the power to the management device.
On the management device, start your asynchronous terminal emulation application (such as Microsoft Windows Hyperterminal) and select the appropriate communication (COM) port to use (for example, COM1).
Configure the port settings as follows:
Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Power on the device by pressing the power button on the front panel.
Verify that thePOWERLED on the front panel turns green.
The terminal emulation screen on your management device displays the boot sequence of the device.
Access the Junos Main Menu.
Press Ctrl+c within the 3-second window to stop the automatic boot sequence and display the Junos Main Menu.
content_copyzoom_out_map
Main Menu
1. Boot [D]irectly fromJunos volume
2. Boot Junos volume in [S]afe mode
3. [R]eboot
4. [B]oot menu
5. [M]ore options
Choice:
At the Choice: prompt in Junos Main Menu, enterBor4to choose4. [B]oot menu. Only the options valid for your device appear. The menu numbers change based on what's available.
content_copyzoom_out_map
Boot Menu
1. Boot [P]revious installed Junos packages
2. Boot [A]ctive Junos packages
3. Boot Junos in [S]ingle user mode
4. Boot from [R]ecovery snapshot
5. Boot from [Network]
6. Boot from [U]SB
7. Boot to [O]AM shell
8. Snapshot [B]oot menu
9. [M]ain menu
Choice:
Showmore
At the Choice: prompt in Boot Menu, enterRor3to choose the4. Boot from [R]ecovery snapshotoption. The device reboots into recovery mode. The following sample output shows the messages displayed on the terminal when you recover Junos OS on an EX2300 switch.
content_copyzoom_out_map
Booting from recovery snapshot ...
-
/boot/junos/boot/os-kernel/kernel data=0xe8c000 syms=[0x4+0x6b020+0x4+0x72cfe]
/boot/junos/boot/os-kernel/ex2300-48mp.dtb size=0x18b8
/boot/junos/boot/os-kernel/ex2300.dtb size=0x1e67
/boot/junos/boot/junos-modules/fips_core.ko text=0x13bc data=0x275+0x7 syms=[0x4+0x7a0+0x4+0x518]
loading required module 'netstack'
/boot/junos/boot/netstack/netstack.ko text=0x910a3c data=0x3ae2f+0x10dded syms=[0x4+0xf0570+0x4+0xdc394]
loading required module 'crypto'
[...Output truncated...]
/var/pdb/profile_db initialized
Profile database initialized
realpath: /dev/dumpdev: No such file or directory
/etc/rc: WARNING: Dump device does not exist. Savecore not run.
Prefetching /usr/sbin/rpd ...
Prefetching /usr/sbin/lacpd ...
Prefetching /usr/sbin/chassisd ...
mkdir: /packages/sets/active: Read-only file system
Starting jlaunchhelperd.
sysctl: unknown oid 'kern.rtc_retries'
Starting cron.
Fri Jun 22 01:25:20 PDT 2018
FreeBSD/arm (device-name) (ttyu0)
login:
Showmore
Log in to the device and run the commandrequest system recover junos-volume.
content_copyzoom_out_map
[...Output truncated...]
login: root
--- JUNOS 18.1-20180125.0 built 2018-01-25 20:34:55 UTC
root@:RE:0% FreeBSD/arm (Amnesiac) (ttyu0)
login: root
--- JUNOS
Note: Junos is currently running in recovery mode on the OAM volume
root@:RE:0% CLI
{master:0}
root> request system recover junos-volume
NOTICE: Recovering the Junos volume ...
...
Junos OS Evolved is a unified, end-to-end network operating system that provides
reliability, agility, and open programmability for successful cloud-scale deployments.
With Junos OS Evolved, you can enable higher availability, accelerate your deployments,
innovate more rapidly, and operate your network more efficiently. We've aligned Junos OS
Evolved with Junos OS so that you can seamlessly continue to manage and to automate your
network.
Benefits
Junos OS Evolved provides several benefits to Juniper Networks customers:
It runs natively on Linux, providing direct access to all the Linux utilities
and operations. With Linux integration, you can use standard Linux and
open-source tools to speed up onboarding, accelerate feature adoption with a
smooth upgrade process, and enjoy enhanced debugging capabilities for
streamlined qualification and deployment.
Support for 3rd party applications and tools. You can run Linux applications
directly on Junos OS Evolved using Docker containers, or create custom
applications for advanced networking solutions. You can use existing Linux tools
and procedures to create custom functions on a developer-friendly platform with
a short learning curve. This versatility allows you to create the solution that
best fits your needs through simple third-party application integration and the
ability to implement the components required for specific use cases.
You can install multiple different Junos OS Evolved software releases on a
device, with support for rolling back to previous versions. This gives you the
flexibility to try out different software releases and easily revert back to
your preferred version if necessary.
Enhanced security at all OS layers. Junos OS Evolved uses an integrity solution
called Integrity Measurement Architecture (IMA), and a companion mechanism
called the Extended Verification Module (EVM). These open source protections are
part of a set of Linux Security Modules that are industry-standard and
consistent with the trust mechanisms specified by the Trusted Computing Group.
Junos OS Evolved also supports other security features such as TPM
infrastructure, hardened secure BIOS, and secure boot. Security is a core design
principle for Junos OS Evolved. Juniper Networks is committed to maintaining a
strong security infrastructure to keep your network safe and protected.
Nearly all of the CLI and user interfaces are identical to those provided in
Junos OS, meaning you can pick up Junos OS Evolved with a minimal learning
curve. These similarities provide simplicity and operational consistency,
minimizing the effort required to implement, maintain, and customize your
end-to-end solution.
Native Linux Base
Whereas Junos OS runs over an instance of the FreeBSD operating system on a specific
hardware element (for example, the CPU on the Routing Engine), Junos OS Evolved runs
over a native Linux system. Having Linux as a base leverages a much wider, dynamic,
and active development community. The Linux system also contains multiple
third-party applications and tools developed for Linux that Junos OS Evolved can
integrate with minimal effort.
The Junos OS Evolved infrastructure is a horizontal software layer that decouples the
application processes from the hardware on which the processes run. Effectively,
this decoupling creates a general-purpose software infrastructure spanning all the
different compute resources on the system (Routing Engine CPUs, line card CPUs, and
possibly others). Application processes (protocols, services, and so on) run on top
of this infrastructure and communicate with each other by publishing and consuming
(that is, subscribing to) state.
To use HTTPS, you must have installed a certificate on the switch and enabled HTTPS.
Afterhttps://in your Web browser, type the hostname or IP address of the switch and pressEnter.
The J-Web login page appears.
On the login page, type your username and password, and clickLogin.
Note:
The default username is root with no password. You must change this during initial configuration or the system does not accept the configuration.
If you are using an Application package of J-Web, the Dashboard information page appears; if you are using a Platform package of J-Web, the Configure Options page appears.
Before you stage an upgrade between different releases of Junos OS with upgraded
FreeBSD, you should install the os-package software to help the upgrade go more
smoothly. A vast majority of all upgrade problems are due to
limitations
in the already running software that is performing the installation, rather than
the new software being installed. The os-package software contains the latest
version of the package system. The software is installable on any
release of
Junos OS running an upgraded FreeBSD version (FreeBSD 10 or
later).
Benefits:
os-package facilitates the major FreeBSD upgrades (that is, version 10 to
version 11 or version 11 to version 12).
The goal of the os-package is to be backward compatible with all prior
BSDx releases of JUNOS.
os-package is architecture neutral.
You do not need to reboot the device after installing os-package. It takes only a
few seconds to add and is immediately available for help with a planned upgrade.
When added, the os-package checks the os-kernel for a feature toggle, which
indicates that it is safe to reboot with the os-package in the active set. If
the toggle is missing, the
following
note is issued:
content_copyzoom_out_map
NOTE: os-package will remove itself from 'active' set at next boot.
Note:
The os-package is NOT bundled with Junos OS
Release
22.2R1 and older. os-package is needed only when the
shipped JUNOS package that is running on a device needs to be updated to
facilitate an upgrade. You
should
install the latest package before every upgrade regardless of whether the
os-package was installed previously on the device. Even when os-package is
bundled with Junos OS (Release 22.3R1 and later), you should fetch and
install the latest os-package before you upgrade to reduce the likelihood of
issues impacting the upgrade.
Once you know which Junos OS BSDx release you have, find the correct
os-package for it:
Junos OS Release 18.x and later: os-package (For example,
os-package-20221105.013526_builder_stable_12.tgz.)
Junos OS Release 17.x and earlier: os-package-sha1 (For example,
os-package-sha1-20221105.013526_builder_stable_12.tgz.)
Download the latest copy of os-package for your
version
of Junos OS. Save the copy to the /var/tmp folder of
the device.
The original filename of os-package looks similar to
this
example:
os-package-20221105.013526_builder_stable_12.tgz.
In this
procedure, we are using the filename os-package.tgz to
refer to the
package.
Install os-package.
content_copyzoom_out_map
root@juniper> request system software add /var/tmp/os-package.tgz
Note:
It only takes a few seconds to run and does not need a reboot.
Do not add os-package when there is already a 'pending' set, else you
will get no benefit from os-package. Thus, if you see the following
notice after adding os-package, you'll need to rollback the
software:
content_copyzoom_out_map
NOTICE: 'pending' set will be activated at next reboot...
content_copyzoom_out_map
root@juniper> request system software rollback
If you had to rollback the software in the previous step due to a pending
set, you need to repeat steps 1 and 2 to install os-package.
Once os-package has successfully installed, you can proceed to upgrade to a
higher version of Junos OS. If the system reboots before you've had a chance to
upgrade Junos OS, os-package deactivates itself, and you will have to install
os-package again. If you ever want to delete os-package, you can use the
request system software delete os-package CLI command.
Install Junos OS with Upgraded FreeBSD Over Junos OS with Upgraded FreeBSD of a
Different Release
CAUTION:
If you do a media install (either USB or network), the system is wiped and
re-partitioned completely. Before you begin, if you have important files,
copy them from the device to a secure location before upgrading the
device.
To install Junos OS with upgraded FreeBSD over Junos OS with upgraded FreeBSD of
a different release:
Enter the request system software add
package-name validate reboot command
from the operational mode in the CLI:
Note:
Because Junos OS Release 21.2R1 runs on FreeBSD 12, which uses system
calls not available on FreeBSD 10 or 11, you must include one of the
following options instead of the validate option on
the request system software add command when
installing the package:
no-validate
validate-on-host
validate-on-routing-engine
Note:
The no-copy option is
ignored.
Use the validate and reboot options
with the request system software add command. The
command uses the validate option by default. We
encourage users to validate using the validate option
when upgrading from Junos OS to Junos OS or from Junos OS with upgraded
FreeBSD to Junos OS with upgraded FreeBSD.
If you leave out the reboot option, you can take care of
that in a separate reboot step.
The new Junos OS image is installed on the device.
Verify the installation of Junos OS with upgraded FreeBSD.
content_copyzoom_out_map
user@host> show version
Note:
The output shows the OS kernel, OS runtime, and other packages
installed on the device.
If you previously left off the reboot option in Step 1,
reboot the device to start the new software using the request system
reboot command:
content_copyzoom_out_map
user@host> request system reboot
Reboot the system? [yes, no] (no) yes
Note:
You must reboot the device to load the newly installed version of
Junos OS with upgraded FreeBSD on the device.
To terminate the installation, do not reboot the device. Instead,
finish the installation and then issue the
request system
software rollback
install-package-name.tgz command.
This is your last chance to stop the installation (not applicable on
EX2300 and EX3400 platforms).
The software is loaded when you reboot the system. Installation can take
between 5 and 10 minutes. The device then reboots from the boot device
on which the software was just installed. When the reboot is complete,
the device displays the login prompt.
While the software is being upgraded, the Routing Engine on which you are
performing the installation does not route traffic.
Upgrade
to a Junos
OS
Release with Upgraded FreeBSD
This topic discusses
how
to
upgrade to a release of Junos OS with upgraded FreeBSD.
This
section covers upgrading from Junos OS based on FreeBSD 6.1 to Junos OS with upgraded
FreeBSD. It does not address upgrading using ISSU. There are certain
limitations to using ISSU when upgrading to Junos OS with upgraded FreeBSD. For more
information on using ISSU, see
Example: Performing a Unified
ISSU.
When you are upgrading to a different release of Junos OS, you usually use the
request system software add validate command. The
validate option checks the candidate software against the current
configuration of the device to ensure they are compatible. (Validate is the default
behavior when the software package being added is a different release.) However, there
are circumstances under which you cannot validate the running configuration in this way.
One such circumstance is when you are upgrading to Junos OS with upgraded FreeBSD from
Junos OS based on FreeBSD 6.1. Another such circumstance is when you are updating
between different releases of Junos OS with upgraded FreeBSD, and the newest version of
FreeBSD uses system calls that are not available in earlier versions of FreeBSD.
If you are upgrading between releases that cannot use direct validation, you need to
specify one of the following on the request system software add
operational mode command when you upgrade:
The no-validate option—this option does not validate the
software package against the current configuration. Therefore, the current
configuration might fail once you upgrade the system. Choose this option for the
first time you upgrade to the newer version.
The validate-on-host option—this option validates the software
package by comparing it to the running configuration on a remote Junos OS host.
Be sure to choose a host that you have already upgraded to the newer version of
software.
The validate-on-routing-engine option—(for systems with
redundant
Routing
Engines) this option validates the software package by
comparing it to the running configuration on a Routing Engine in the same
chassis. Use this option when you have already upgraded the other Routing Engine
to the newer version.
If you are upgrading between releases that cannot use direct validation, another approach
would be to validate on a different host. It does not matter where that other host is,
as long as you can reach it with NETCONF over SSH (see Establishing an SSH Connection for a NETCONF
Session). The target system uses the network to contact the other host, run
the validation and authentication, and return the result.
The
procedure covers
upgrading
to a
release of Junos OS with upgraded FreeBSD
from a
release of Junos OS based on FreeBSD
6.1.
To determine whether you are upgrading between releases that can use direct validation
or not, see Upgrade to a Junos OS Release with Upgraded FreeBSD.
Note:
Before installing software on a device that has one or more custom YANG data models
added to it, back up and remove the configuration data corresponding to the custom
YANG data models from the active configuration. For more information see Managing YANG Packages and Configurations During a Software Upgrade or
Downgrade.
To determine which software package to install to upgrade to Junos OS with
upgraded FreeBSD, you will need to consult the Feature Explorer and Table 1.
You can skip no more than two releases when upgrading (or downgrading). That
means you can upgrade only to one of the three releases subsequent to your
current release. If you want to upgrade across more releases than this, you need
to perform multiple upgrades.
We recommend you upgrade to a 64-bit image of Junos OS with upgraded FreeBSD. In
Junos OS releases earlier than 15.1, the partition swap pages are counted as
part of the memory file system partition. Using this method leaves 4 GB of
memory as the maximum that is theoretically accessible when you are using a
32-bit image. However, when Junos OS with upgraded FreeBSD is run, the system
only counts the actual partition size, which leaves around 3.4 GB of available
physical address space, or only 3 GB of usable RAM.
To determine which installation package and procedure you require:
See the Junos kernel upgrade to FreeBSD 10+ entry
in
Feature Explorer.
Click the link or go
to
https://apps.juniper.net/feature-explorer/,
type freebsd, and select Junos kernel
upgrade to FreeBSD 10+.
You will see a listing of
platforms that run Junos OS with upgraded FreeBSD and the software
release it was introduced in. Different platforms first support Junos OS
with upgraded FreeBSD in different releases. Use this listing to find
which release you need to install for your device to upgrade to Junos OS
with FreeBSD.
Consult Table 1 to determine the upgrade path to follow.
Determine which release your device is currently running.
Look first at the release sequence and then at the second
column and find the release running on your device.
Determine which release you need to install.
The third
column will give you the earliest release you need to install
for your platform type to be running Junos OS with upgraded
FreeBSD.
Table 1: Upgrade Path to Junos OS with the Upgraded FreeBSD
Release
Sequence
Current
Router’s Junos OS Release
Earliest
Release Supporting Junos OS with Upgraded FreeBSD
Upgrade
Path
Example
Routing and
Switching
All currently supported
routers and switches run Junos OS with Upgraded
FreeBSD.
All currently supported
routers and switches run Junos OS with Upgraded
FreeBSD.
Upgrade in a single
step.
To upgrade from Release
23.4R1, upgrade directly to either Release 24.2R1 or
24.4R1.
Security
12.3 to 17.2
17.3
Upgrade in a single
step.
To upgrade from Release
12.3X48, upgrade directly to Release
17.3.
15.1 to 17.2
17.3
Upgrade in a single
step.
To upgrade from Release
15.1X49, upgrade directly to Release
17.3.
15.1 to 17.3
17.4
Upgrade in a single
step.
To upgrade from Release
15.1x49-D80, upgrade directly to Release
17.4.
(SRX300, SRX320, SRX340,
SRX345, SRX380 only), 23.4R2-S3 or
24.2R2
24.4R1
Upgrade in a single
step.
For upgrade instructions,
including for upgrading from releases earlier than
23.4R2-S3, see
KB85650.
Note:
You can also downgrade
from
a Junos OS
release
with upgraded FreeBSD
to
a Junos
OS
release based on FreeBSD 6.1 as long as the path
complies with the Junos OS policy of skipping at most two earlier
releases.
Download the Junos OS with upgraded FreeBSD package.
Install
a Junos OS with Upgraded
FreeBSD
Release
Over an
Existing Junos
OS
Release
Upgrading
to a
release of Junos OS with upgraded FreeBSD reformats the file
system.
Unless
you take precautions to save important files elsewhere, most files
and directories are
deleted.
By default, the upgrade process preserves only the following
directories
and the files within them:
/config
/etc/localtime
/var/db
/var/etc/master.passwd
/var/etc/inetd.conf
/var/etc/pam.conf
/var/etc/resolv.conf
/var/etc/syslog.conf
/var/etc/localtime
/var/etc/exports
/var/etc/extensions.allow
/var/preserve
/var/tmp/baseline-config.conf
/var/tmp/preinstall_boot_loader.conf
Note:
In
the
/var/db/config
directory, up to 10 rollback configurations
are
saved, depending on the configuration file size.
Note:
On EX2300 and EX3400 switches, the following directories are not applicable:
/etc/localtime
/var/etc/localtime
/var/etc/exports
/var/preserve
/var/tmp/preinstall_boot_loader.conf
Before you begin, if you have important files
in
directories that are not preserved, copy them from the
device
to a secure location before upgrading the
device.
CAUTION:
If you do a media install (either USB or network), the system is wiped and
re-partitioned completely. Before you begin, if you have important files,
copy them from the device to a secure location before upgrading the
device.
To
install
a release of Junos OS with upgraded FreeBSD over plain Junos
OS:
Enter the request system software add
install-package-name.tgz no-validate
command from the operational mode in the CLI:
Note:
The no-copy option is enabled by default.
Use the no-validate
option with the request system
software add command. If you leave out the
no-validate option, the command uses the
validate option by default, and direct validation
of the running configuration does not work for upgrading to Junos OS
with upgraded FreeBSD from Junos OS based on older versions of the
FreeBSD kernel.
Note:
You can also use the reboot option along with the
request system software add command, but it is
not recommended to do this in a single step while upgrading from a
FreeBSD 6.1 based Junos OS to Junos OS with upgraded FreeBSD.
user@host>request system software add /var/tmp/install-package-name.tgz no-validate
The new Junos OS image is installed on the device.
Reboot the device to start the new software using the request
system reboot command:
content_copyzoom_out_map
user@host> request system reboot
Reboot the system? [yes, no] (no) yes
Note:
You must reboot the device to load the newly installed version of
Junos OS on the device.
To terminate the installation, do not reboot the device. Instead,
finish the installation and then issue the request system
software delete
install-package-name.tgz command.
This is your last chance to stop the installation (not applicable on
EX2300 and EX3400 platforms).
The software is loaded when you reboot the system. Installation can take
between 5 and 10 minutes. The device then reboots from the boot device
on which the software was just installed. When the reboot is complete,
the device displays the login prompt.
While the software is being upgraded, the Routing Engine on which you are
performing the installation does not route traffic.
Log in and issue the show version command to verify the
version of the software installed.
Note:
The output shows the OS kernel, OS runtime, and other packages
installed on the device.
This topic discusses the different procedures for downgrading from a release of Junos
OS with upgraded FreeBSD.
Certain hardware platforms run a Junos OS based on an upgraded FreeBSD kernel instead of older
versions of FreeBSD. To find which platforms support Junos OS with upgraded FreeBSD, see
Feature Explorer, enter
freebsd, and select Junos kernel upgrade to
FreeBSD 10+.
This topic discusses the different procedures for downgrading
from a release of Junos OS with upgraded FreeBSD. One procedure describes
how to downgrade to legacy Junos OS. The other procedures describe
how to downgrade to an earlier release of Junos OS with upgraded FreeBSD.
The main difference between the procedures is whether to use
the validate or no-validate option with the request system software add command. If you downgrade between
two versions of legacy Junos OS, validate works. Similarly,
if you downgrade from Junos OS with upgraded FreeBSD Release 18.1
or later to Release 17.4 or later, validate works. However,
there is one set of circumstances in which the no-validate option must be used when downgrading between Junos OS with upgraded
FreeBSD releases, and that is when you downgrade from a Junos OS with
upgraded FreeBSD Release 17.4 or later to a release earlier than 17.4,
that is, Junos OS releases 15.1 through 17.3.
Select and perform the procedure that matches your set of circumstances.
Downgrading from Junos OS with Upgraded FreeBSD to Legacy Junos
OS
If you have previously upgraded to Junos OS with upgraded FreeBSD, you can downgrade
to an earlier version of Junos OS (that is, legacy Junos OS) as long as the
downgrade conforms to the Junos OS policy of skipping at most two earlier
releases.
Note:
For SRX300, SRX320, SRX340, SRX345, and SRX380 firewalls, you must first
downgrade to either Junos OS Release 23.4R2-S3 or Release 24.2R2 before
downgrading to any other release. Also, if you have chassis clusters, you cannot
use the In-Band Cluster Upgrade (ICU) method for this particular downgrade. You
can use either the procedure outlined in KB85650 or the
minimal downtime procedure documented in KB17947 (Minimal_Downtime_Upgrade_Branch_Mid
PDF file). You must use the request system software add
package-name no-validate command to
downgrade the software.
This example uses the package /var/tmp/jinstall-13.3R2.7-domestic-signed.tgz to install legacy Junos OS on the primary Routing Engine (re0).
To downgrade from Junos OS with upgraded FreeBSD to legacy Junos
OS:
Enter the request system software add package-name no-validate reboot command from the operational mode in the
CLI.
Use the no-validate and reboot options
with the request system software add command. If you leave
out the no-validate option, the command uses the validate option by default, and direct validation of running configuration
does not work for downgrading to legacy Junos OS from Junos OS with
upgraded FreeBSD.
If you leave out the reboot option, you can take
care of that in a separate reboot step.
The following example uses the re0 option:
content_copyzoom_out_map
user@host> request system software add /var/tmp/jinstall-13.3R2.7-domestic-signed.tgz re0 no-validate reboot
THIS IS A SIGNED PACKAGE Saving the config files ...
NOTICE: uncommitted changes have been saved in
/var/db/config/juniper.conf.pre-install Rebooting. Please wait ...
shutdown: [pid 11001] Shutdown NOW! *** FINAL System shutdown message
from root@host *** System going down IMMEDIATELY Shutdown NOW! System
shutdown time has arrived\x07\x07 users@host> Connection to
device1.example.com closed by remote host. Connection to
device1.example.com closed. ... user@router> show version
Hostname: host
Model: mx240
Junos: 13.3R2.7
JUNOS Base OS boot [13.3R2.7]
JUNOS Base OS Software Suite [13.3R2.7]
JUNOS Kernel Software Suite [13.3R2.7]
JUNOS Crypto Software Suite [13.3R2.7]
JUNOS Packet Forwarding Engine Support (M/T/EX Common) [13.3R2.7]
JUNOS Packet Forwarding Engine Support (MX Common) [13.3R2.7]
JUNOS Online Documentation [13.3R2.7]
JUNOS Services AACL Container package [13.3R2.7]
...
Show
more
Verify the downgrade of the software package.
content_copyzoom_out_map
user@host> show version
The output shows the OS kernel, OS runtime, and other packages
installed on the device.
Downgrading from Junos OS with Upgraded FreeBSD Release 17.4
or Later to Release 15.1 Through 17.3
This procedure is applicable when downgrading from Junos OS
with Upgraded FreeBSD Release 17.4 or later to an earlier release
of Junos OS with Upgraded FreeBSD.
Note:
If you have important files in other directories, copy
them from the router or switch to a secure location before upgrading
the router or switch.
To downgrade from Junos OS with upgraded FreeBSD Release
17.4 or later to a Release 15.1 through 17.3:
Enter the request system software add package-name no-validate reboot command from the operational mode in the
CLI:
Use the no-validate and reboot options
with the request system software add command. If you leave
out the no-validate option, the command uses the validate option by default, and direct validation of running configuration
does not work for downgrading to an earlier release of Junos OS with
upgraded FreeBSD from Junos OS with upgraded FreeBSD Release 17.4
or later.
If you leave out the reboot option, you can take
care of that in a separate reboot step.
The new Junos OS image is installed on the device.
Verify the installation of Junos OS with upgraded FreeBSD:
content_copyzoom_out_map
user@host> show version
The output shows the OS kernel, OS runtime, and other packages
installed on the device.
Downgrading from Junos OS with Upgraded FreeBSD Release 17.3
or Earlier to Release 15.1 Through 17.2
This procedure is applicable when downgrading from Junos OS
with Upgraded FreeBSD Releases 17.3 through 15.1 to an earlier release
of Junos OS with Upgraded FreeBSD.
Note:
If you have important files in other directories, copy
them from the router or switch to a secure location before upgrading
the router or switch.
To downgrade from Junos OS with upgraded FreeBSD Release
17.3 or earlier to an earlier release of Junos OS with upgraded FreeBSD:
Enter the request system software add package-name validate reboot command from the operational mode in the CLI:
Use the validate and reboot options with
the request system software add command. The command uses
the validate option by default. If you leave out the reboot option, you can take care of that in a separate reboot
step.
The new Junos OS image is installed on the device.
Verify the installation of Junos OS with upgraded FreeBSD:
content_copyzoom_out_map
user@host> show version
The output shows the OS kernel, OS runtime, and other packages
installed on the device.
Downgrading from Junos OS with Upgraded FreeBSD Release 18.1
or Later to Release 17.4 or Later
This procedure is applicable when downgrading from Junos OS
with Upgraded FreeBSD Releases 18.1 or later to a Junos OS with Upgraded
FreeBSD Release 17.4 or later.
Note:
If you have important files in other directories, copy
them from the router or switch to a secure location before upgrading
the router or switch.
To downgrade from Junos OS with upgraded FreeBSD Release
18.1 or later to Junos OS with Upgraded FreeBSD Release 17.4 or later:
Enter the request system software add package-name validate reboot command from the operational mode in the CLI:
Use the validate and reboot options with
the request system software add command. The command uses
the validate option by default. If you leave out the reboot option, you can take care of that in a separate reboot
step.
The new Junos OS image is installed on the device.
Verify the installation of Junos OS with upgraded FreeBSD:
content_copyzoom_out_map
user@host> show version
The output shows the OS kernel, OS runtime, and other packages
installed on the device.
