20 Chapter2
SCR Overview
Tracking Configuration Changes with SCR
Tracking Configuration Changes with SCR
Use the scrhist command to check the configuration collection history
for managed nodes. This command reports a brief list with node, time
and tag information. To generate a report for all system nodes, enter
the following command:
# scrhist
This command generates a report that resembles the following
example:
NODE TIME ERR TAG
elsa 12:05 02/07/1999 PST oldest
12:05 02/14/1999 PST
13:05 04/10/1999 PDT latest
ortrud 12:25 03/23/1999 PST oldest
13:25 04/10/1999 PDT latest
If no time period is specified, as in this example, the report includes all
configuration collections that have not expired. The SCR tag, oldest,
stands for the oldest configuration update that has not expired.
SCR does not store a snapshot if there are no differences in the node
configuration since the previous snapshot. You can use this feature to
observe how often the configuration of certain nodes changes. If data
has been automatically collected weekly, this report shows that node
elsa’s configuration changed between February 7 and February 14,
1999, but did not change again until April 10, 1999.
You can limit the scope of the list by time period and managed nodes. To
limit the time period, enter one of the following lines:
# scrhist –p 19990101 19990226
# scrhist –p 19990401 latest
The -p option signifies that the digits that follow are a time period that
limits the report.
To specify the managed nodes reported, use the following syntax:
# scrhist –n elsa
This command limits the report to only the node elsa.
To Next Page
Loading...
Need help?
General
