Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > Junos OS > request system snapshot
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • EX Series
  • show system snapshot
  • J Series
  • show system snapshot
  • M Series
  • show system snapshot
  • MX Series
  • show system snapshot
  • T Series
  • show system snapshot
 

request system snapshot

Syntax

request system snapshot <partition>

Syntax (EX Series Switches)

request system snapshot<all-members | local | member member-id><media type><partition><re0 | re1 | routing-engine routing-engine-id><slice (1 | 2 | alternate)>

Syntax (J Series Routers)

request system snapshot <as-primary> <config-size size><data-size size><factory><media type><partition> <root-size size> <swap-size size>

Syntax (MX Series Router)

request system snapshot <all-members><local><member member-id><partition>

Syntax (TX Matrix Router)

request system snapshot <all-chassis | all-lcc | lcc number | scc> <partition>

Syntax (TX Matrix Plus Router)

request system snapshot <all-chassis | all-lcc | lcc number | sfc number> <partition>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 10.0 for EX Series switches.

Description

  • On the router, back up the currently running and active file system partitions to standby partitions that are not running. Specifically, the root file system (/) is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router's flash drive, and the /altroot and /altconfig file systems are on the router's hard drive.
  • On the switch, take a snapshot of the files currently used to run the switch—the complete contents of the root (/) , /config, and /var directories, which include the running Junos OS, the active configuration, and log files.

Caution: After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.

Options

The specific options available depend upon the router or switch:

none
—

Back up the currently running software as follows:

  • On the router, back up the currently running and active file system partitions to standby partitions that are not running. Specifically, the root file system (/) is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router's flash drive, and the /altroot and /altconfig file systems are on the router's hard drive.
  • On the switch, take a snapshot of the files currently used to run the switch—the complete contents of the root file system /, /config directory, and /var directory, which include the running Junos OS, the active configuration, and log files—and copy all these files onto an external drive. (If a USB flash drive is not connected, an error message is displayed.)
all-chassis | all-lcc | lcc number
—

(TX Matrix and TX Matrix Plus router only) (Optional)

  • all-chassis—On a TX Matrix router, archive data and executable areas for all Routing Engines in the chassis. On a TX Matrix Plus router, archive data and executable areas for all Routing Engines in the chassis.
  • all-lcc—On a TX Matrix router, archive data and executable areas for all T640 routers (or line-card chassis) connected to a TX Matrix router. On a TX Matrix Plus router, archive data and executable areas for all T1600 routers (or line-card chassis) connected to a TX Matrix Plus router.
  • lcc number—On a TX Matrix router, archive data and executable areas for a specific T640 router (or line-card chassis) that is connected to a TX Matrix router. On a TX Matrix Plus router, archive data and executable areas for a specific T1600 router (or line-card chassis) that is connected to a TX Matrix Plus router. Replace number with a value from 0 through 3.
all-members | local | member member-id
—

(EX4200, EX4500, and EX8200 Virtual Chassis and MX Series routers only) (Optional) Specify where to place the snapshot (archive data and executable areas) in a Virtual Chassis:

  • all-members—Create a snapshot (archive data and executable areas) for all members of the Virtual Chassis.
  • local—Create a snapshot (archive data and executable areas) on the member of the Virtual Chassis that you are currently logged into.
  • member member-id—Create a snapshot (archive data and executable areas) for the specified member of the Virtual Chassis.
as-primary
—

(J Series routers only) (Optional) Create a snapshot that can be used to replace the medium in the primary compact flash drive. This option can be used on the removable compact flash only. The option copies the default files that were loaded on the primary compact flash drive when it was shipped from the factory, plus the rescue configuration if one has been set. This option is useful if you have multiple routers and want to use the same software and configuration on each router. After a boot device is created as a primary compact flash drive, it can operate in only a primary compact flash drive slot. This option causes the boot medium to be partitioned.

config-size size
—

(J Series routers only) (Optional) Specify the size of the config partition, in megabytes. The default value is 10 percent of physical memory on the boot partition. The config partition is mounted on /config, and the configuration files are stored in this partition. This option causes the boot medium to be partitioned.

data-size size
—

(J Series routers only) (Optional) Specify the size of the data partition, in megabytes. The default value is 0 MB. The data partition is mounted on /data. This space is not used by the router, and can be used for extra storage. This option causes the boot medium to be partitioned.

factory
—

(J Series routers only) (Optional) Copy only default files that were loaded on the primary compact flash drive when it was shipped from the factory, plus the rescue configuration if one has been set. After the boot medium is created with the factory option, it can operate in only the primary compact flash drive.

media type
—

(J Series routers and EX Series switches only)(Optional) Specify the boot device the software is copied to:

  • compact-flash—Copy software to the primary compact flash drive.
  • external—(Switches only) Copy software to an external mass storage device, such as a USB flash drive. If the media option is not specified, this is the default. If a USB drive is not connected, the switch displays an error message.
  • internal—(Switches only) Copy software to an internal flash drive.
  • removable-compact-flash—Copy software to the removable compact flash drive.
  • usb—(M320, T640, MX960, and J Series routers only) Copy software to the device connected to the USB port.
partition
—

(Optional) Repartition the flash drive before a snapshot occurs. If the partition table on the flash drive is corrupted, the request system snapshot command fails and reports errors. The partition option is only supported for restoring the software image from the hard drive to the flash drive.

(Routers only) You cannot issue the request system snapshot command when you enable flash disk mirroring. We recommend that you disable flash disk mirroring when you upgrade or downgrade the software. For more information, see the Junos OS System Basics Configuration Guide PDF Document.

re0 | re1 | routing-engine routing-engine-id
—

(EX8200 switch only) Specify where to place the snapshot in a redundant Routing Engine configuration.

  • re0—Create a snapshot on Routing Engine 0.
  • re1—Create a snapshot on Routing Engine 1.
  • routing-engine routing-engine-id—Create a snapshot on the specified Routing Engine.
root-size size
—

(J Series routers only) (Optional) Specify the size of the root partition, in megabytes. The default value is one-third of the physical memory minus the config, data, and swap partitions. The root partition is mounted on / and does not include configuration files. This option causes the boot medium to be partitioned.

slice (1 | 2 |alternate)
—

(EX Series switches only) (Optional) Take a snapshot of the active root partition and copy it to the selected slice on the boot media.

scc
—

(TX Matrix router only) (Optional) Archive data and executable areas for a TX Matrix router (or switch-card chassis).

sfc number
—

(TX Matrix Plus router only) (Optional) Archive data and executable areas for a TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.

swap-size size
—

(J Series router only) (Optional) Specify the size of the swap partition, in megabytes. The default value is one-third of the physical memory on a boot medium larger than 128 MB, or 0 MB on a smaller boot device. The swap partition is used for swap files and software failure memory snapshots. Software failure memory snapshots are saved to the boot medium only if it is specified as the dump device in the system dump-device configuration hierarchy. This option causes the boot medium to be partitioned.

Additional Information

  • (Routers only) Before upgrading the software on the router, when you have a known stable system, issue the request system snapshot command to back up the software, including the configuration, to the /altroot and /altconfig file systems. After you have upgraded the software on the router and are satisfied that the new packages are successfully installed and running, issue the request system snapshot command again to back up the new software to the /altroot and /altconfig file systems.
  • (Routers only) You cannot issue the request system snapshot command when you enable flash disk mirroring. We recommend that you disable flash disk mirroring when you upgrade or downgrade the software. For more information, see the Junos OS System Basics Configuration Guide PDF Document
  • (TX Matrix and TX Matric Plus router only) On a routing matrix, if you issue the request system snapshot command on the master Routing Engine, all the master Routing Engines connected to the routing matrix are backed up. If you issue this command on the backup Routing Engine, all the backup Routing Engines connected to the routing matrix are backed up.

Required Privilege Level

maintenance

 

Related Documentation

  • EX Series
  • show system snapshot
  • J Series
  • show system snapshot
  • M Series
  • show system snapshot
  • MX Series
  • show system snapshot
  • T Series
  • show system snapshot
 

List of Sample Output

request system snapshot (Routers)
request system snapshot (EX Series Switches)
request system snapshot (When Partition Flag Is On)
request system snapshot (When Mirroring Is Enabled)
request system snapshot all-lcc (Routing Matrix)
request system snapshot all-members (Virtual Chassis)

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output

request system snapshot (Routers)

user@host> request system snapshot
umount: /altroot: not currently mounted
Copying / to /altroot.. (this may take a few minutes)
umount: /altconfig: not currently mounted
Copying /config to /altconfig.. (this may take a few minutes)

The following filesystems were archived: / /config

request system snapshot (EX Series Switches)

user@switch> request system snapshot
fpc0:
--------------------------------------------------------------------------
Verifying compatibility of destination media partitions...
Running newfs (345MB) on external media  / partition ...
Running newfs (235MB) on external media  /config partition ...

The following filesystems were archived: / /config /var

request system snapshot (When Partition Flag Is On)

user@host> request system snapshot partition
Performing preliminary partition checks ...
Partitioning ad0 ...
umount: /altroot: not currently mounted
Copying / to /altroot.. (this may take a few minutes)

The following filesystems were archived: / /config

request system snapshot (When Mirroring Is Enabled)

user@host> request system snapshot
Snapshot is not possible since mirror-flash-on-disk is configured.

request system snapshot all-lcc (Routing Matrix)

user@host> request system snapshot all-lcc
lcc0-re0:
--------------------------------------------------------------------------
Copying '/' to '/altroot' .. (this may take a few minutes)
Copying '/config' to '/altconfig' .. (this may take a few minutes)
The following filesystems were archived: / /config

lcc2-re0:
--------------------------------------------------------------------------
Copying '/' to '/altroot' .. (this may take a few minutes)
Copying '/config' to '/altconfig' .. (this may take a few minutes)
The following filesystems were archived: / /config

request system snapshot all-members (Virtual Chassis)

user@switch> request system snapshot all-members media internal

fpc0: -------------------------------------------------------------------------- Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: / fpc1: -------------------------------------------------------------------------- Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: / fpc2: -------------------------------------------------------------------------- Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: / fpc3: -------------------------------------------------------------------------- Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: / fpc4: -------------------------------------------------------------------------- Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: / fpc5: -------------------------------------------------------------------------- Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: /

Published: 2012-03-05

 
  • About Juniper
  • The New Network
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out