Changing the Reset Config Button Behavior on the SRX100 Services Gateway
You can change the default operation of the RESET CONFIG button by limiting how the
button resets the services gateway:
•
To prevent the RESET CONFIG button from setting the device to the factory-default
configuration and deleting all other configurations:
admin@host#
set chassis config-button no-clear
You can still press and quickly release the button to reset it to the rescue configuration.
•
To prevent the RESET CONFIG button from setting the device to the rescue
configuration:
admin@host#
set chassis config-button no-rescue
You can still press and hold the button for 15 seconds or more to reset the gateway to
the factory-default configuration.
•
To disable the button and prevent the device from resetting to either configuration:
admin@host#
set chassis config-button no-clear no-rescue
The
no-clear
option prevents the RESET CONFIG button from deleting all configurations
on the services gateway. The
no-rescue
option prevents the RESET CONFIG button from
loading the rescue configuration.
To return the function of the RESET CONFIG button to its default behavior, remove the
config-button
statement from the device configuration.
Related
Documentation
Using the Reset Config Button on the SRX100 Services Gateway on page 102
•
•
Monitoring the SRX100 Services Gateway Chassis Using the CLI on page 95
•
Monitoring the SRX100 Services Gateway Components Using LEDs on page 97
•
Monitoring the SRX100 Services Gateway Using Chassis Alarm Conditions on page 99
•
Monitoring the SRX100 Services Gateway Power System on page 101
•
Juniper Networks Technical Assistance Center on page 103
Juniper Networks Technical Assistance Center
If you need assistance while troubleshooting a services gateway, open a support case
using the Case Manager link at
http://www.juniper.net/support/
, or call 1-888-314-JTAC
(within the United States) or 1-408-745-9500 (from outside the United States).
Related
Documentation
•
Contacting Customer Support on page 107
103
Copyright © 2015, Juniper Networks, Inc.
Chapter 16: Troubleshooting Components