close
keyboard_arrow_left
Table of Contents
- play_arrow Overview
- play_arrow Configuring Administrative Credentials and Privileges
- play_arrow Configuring Roles and Authentication Methods
- Understanding Roles and Services for Junos OS
- Understanding the Operational Environment for Junos OS in FIPS Mode
- Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode
- Downloading Software Packages from Juniper Networks
- Installing Software on a Device with Single Routing Engine
- Understanding Zeroization to Clear System Data for FIPS Mode
- Zeroizing the System
- Enabling FIPS Mode
- Configuring Crypto Officer and FIPS User Identification and Access
- play_arrow Configuring SSH and Console Connection
- play_arrow Configuring MACsec
- play_arrow Configuring Event Logging
- play_arrow Configuring IPsec VPN
- play_arrow Performing Self-Tests on a Device
list Table of Contents
keyboard_arrow_right
request system zeroize
date_range
15-Dec-21
Description
Remove all configuration information on the Routing Engines hypervisor and reset all key values. The command removes all data files, including customized configuration and log files, by unlinking the files from their directories. The command removes all user-created files from the system including all plain-text passwords, secrets, and private keys for SSH, local encryption, and local authentication and IPsec.
This command reboots the device and sets it to the factory default configuration. After the reboot, you cannot access the device through the management Ethernet interface. Log in through the console as root and start the Junos OS CLI by typing cli at the prompt.
Sample Output
request system zeroize
content_copy zoom_out_map
root@device: fips> request system zeroize warning: System will be rebooted and may not boot without configuration Erase all data, including configuration and log files? [yes,no] (no) yes warning: zeroizing re0 Jul 27 22:25:53 jlaunchd: gkd-re (PID 5264) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: inet-process (PID 5267) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: periodic-packet-services (PID 5271) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: disk-monitoring (PID 5273) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: neighbor-liveness (PID 5307) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: event-processing (PID 5209) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: clksyncd-service (PID 5316) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: ethernet-link-fault-management (PID 5321) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: subscriber-management (PID 5323) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: shm-rtsdbd (PID 5325) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: gstatd (PID 5326) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: rpcbind-service (PID 5330) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: icmd (PID 5332) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: pmcd (PID 5333) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: ftp-inet-process (PID 5334) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: process-monitor (PID 5338) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: smg-service-telemetry (PID 5340) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: application-identification (PID 5341) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: resource-management (PID 5342) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: charged (PID 5346) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: license-service (PID 5351) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: ntp (PID 6120) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: gkd-chassis (PID 6121) terminate signal 15 sent Jul 27 22:25:53 jlaunchd: gkd-lchassis ........
