Bitzu

JN0-106 ยท Monitoring and maintenance

Powering on and shutting down Junos devices

Graceful shutdown with request system halt/power-off/reboot, why not to pull power, and boot sequence basics.

Key points

  • Do not simply cut the power: it risks file-system and log corruption.
  • request system halt (stops the software) or power-off; request system reboot restarts. Wait for the console to confirm it is safe.
  • Options: at (now, +minutes or a time), in (minutes), message "text" to warn users.
  • These commands need maintenance privilege.
  • Boot order: bootloader, kernel, Junos processes, login prompt.

Source: https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/request-system-halt.html

Practice questions

Single choice

Which command stops the Junos software gracefully so the device can be powered off safely?

  1. request system halt
  2. request system reboot
  3. request system zeroize
  4. request system snapshot
Show answer

Answer: A. request system halt

request system halt (or power-off) performs an orderly stop. reboot restarts the device, and zeroize erases the configuration.

Select all that apply

Which options can be used with request system reboot?

  1. at
  2. in
  3. message
  4. validate
  5. snapshot
Show answer

Answer: A. at, B. in, C. message

at, in and message are options of the command; validate and snapshot are not.

True or false

True or false: cutting the power is as safe as request system halt, because committed configuration is always stored on disk.

Show answer

Answer: False

False. Abrupt power loss can corrupt the file system and logs even when the committed configuration exists. A graceful halt stops processes and closes files first.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More JN0-106 topics in this module