Juniper JUNOSE 11.3, Configuration Manual

Page: 288 / 632

no boot subsystem
no boot backup subsystem
•
See show configuration.
show running-configuration
•
Use to display the configuration currently running on the router, a specified virtual
router, a specified interface, or a specified category of router settings.
•
Example
host1# show running-configuration
•
Example 2
host1# show running-configuration interface serial 4/0
•
Example 3
host1# show running-configuration category system file-system
•
See show running-configuration.
tag-group
•
Use to configure an interface tag group.
•
Any number of interfaces can be in a tag group.
•
Interface types tunnel, lag, mlppp, and mlframe-relay cannot be added to tag groups.
•
An interface can be in only one tag group.
•
Example
host1(config-if)# tag-group red
•
Use the no version to remove the tag group.
•
See tag-group.
Detecting Corrupt File Configurations
You can detect corruption of running configuration files and CNF files on both the primary
SRP when the corruption is due to a fatal duplicate key error. CNF files must be present
on the active file system to monitor them; you cannot monitor CNF files that reside alone
on the standby SRP.
You can use the service check-config command to control the mode of detection for
corruption detection of the running configuration. Auto mode provides a background
monitoring task that periodically checks the validity of running configurations. The
service
config-monitor-periodicity command enables you to set the time for background
monitoring of the active and standby SRP. By default, background monitoring is not
running. Manual mode is the default detection mode. For corruption detection of the CNF
files, you must use manual mode.
A critical message that indicates whether the corrupted configuration files are recoverable
appears prompting you to manually recover the corrupt files.
Copyright © 2010, Juniper Networks, Inc. 258
JunosE 11.3.x System Basics Configuration Guide