HP b2600 Service manual

System Configuration Repository
User’s Reference
HP-UX/HP 9000 Computers
Edition 1.2
April 2001
Printed in: USA

2
Legal Notices
The information contained in this document is subject to change without
notice.
Hewlett-Packard makes no warranty of any kind with regard to this manual,
including, but not limited to, the implied warranties of merchantability and
fitness for a particular purpose. Hewlett-Packard shall not be liable for errors
contained herein or direct, indirect, special, incidental or consequential
damages in connection with the furnishing, performance, or use of this
material.
Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard
product and replacement parts can be obtained from your local Sales and
Service Office.
Restricted Rights Legend
Use, duplication, or disclosure by the U.S. Government is subject to restrictions
as set forth in sub-paragraph (c)(1)(ii) of the Rights in Technical Data and
Computer Software clause in DFARS 252.227-7013.
Hewlett-Packard Company 3000 Hanover Street Palo Alto, CA 94304 U.S.A.
Rights for non-DOD U.S. Government Departments and Agencies are as set
forth in FAR 52.227-19(c)(1,2).
All rights reserved.
Trademark Acknowledgments
UNIX is a registered trademark in the United States and other countries,
licensed exclusively through X/Open Company Limited.
© Copyright 1999 - 2001 Hewlett-Packard Company
© Copyright 1980, 1984, 1986 Novel, Inc.
© Copyright 1995 IBM Corporation
© Copyright 1990, 1993, 1994, 1995, 1996, 1997, 1998 Sleepycat Software
© Copyright 1990, 1993, 1994, 1995 The Regents of the University of
California
© Copyright 1995, 1996 The President and Fellows of Harvard University
© Copyright Regents of the University of California, Sun Microsystems, Inc.,
Scriptics Corporation and other parties
Reproduction, adaptation, or translation without prior written permission is
prohibited, except as allowed under the copyright laws.

Contents
3
1. Introduction
2. SCR Overview
Installing SCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Using SCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring SCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Registering Managed Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting the Data Collection Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Collecting Configuration Data On Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Checking Data Collection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Viewing Configuration Information on a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Tracking Configuration Changes with SCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Checking Node Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Using Tags to Simplify Node Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Using Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Simple Filter Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Standard Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Using the Probe Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Additional Uses of SCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Inventory Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
SCR Reference (man Pages) 33
scr (5) 34
scrconfig (1M) 43
scrdelete (1M) 48
scrdiff (1M) 50
scrfilter (1M) 53
scrhist (1M) 64
scrstatus (1M) 66
scrtag (1M) 69
scrupdate (1M) 72
scrviewer (1M) 74
scrlog_viewer (1M) 77
A. SCR File Set

4
Contents

5
About this Manual
Printing History
The printing date will change when a new edition is printed. Minor changes
may be made at reprint without changing the printing date. The manual part
number will change when extensive changes are made.
Manual updates may be issued between editions to correct errors or document
product changes. To ensure that you receive these updates or new editions, see
your HP sales representative for details.
April 2001…Edition 1.2.
April 2000…Edition 1.1.

6
How to Use this Guide
This is a technical reference for the ServiceControl Manager. It deals with the
concepts and technical details necessary to create a managed cluster using
ServiceControl Manager and to efficiently manage the systems using the
ServiceControl tools.
This guide contains the following information:
•Chapter 1 , “Introduction,” provides an introduction to this manual.
• Chapter 2 , “SCR Overview,” provides an overview of the System
Configuration Repository.
• Chapter , “SCR Reference (man Pages),” includes the man pages for the
System Configuration Repository.
Appendix A , “SCR File Set,” describes the file set for the System
Configuration Repository.
Comments about this manual (no technical questions, please) can be directed
to: [email protected].com. Please consult your HP service and support
representative for technical support questions. Thanks.

7
Typographic Conventions
This guide uses the following typographic conventions:
Boldface Words defined for the first time appear in boldface. For
example, an argument is the part of a command line that
indicates what file or directory the command is to act on.
Computer Computer font indicates literal items displayed by the
computer. For example: file not found
User input Bold, computer text indicates literal items that you type. For
example: cd
Italics Manual titles and emphasized words appear in italics, as do
values that you supply.
For example, in the command below you would substitute an
actual directory name (such as mydir) for directory_name.
cd directory_name
Enter Text in a bold, sans serif font denotes a keyboard key. A
notation like CTRL+Qindicates that you should hold the
control key down, then press Q.
Softkey Select an on-screen item or a corresponding softkey. For
example,
Help
shown at the bottom left side of the screen means that
pressing the softkey corresponding to that position on the
screen (f1) will cause a help screen to be displayed.

8

9
1Introduction
This manual describes the features of Hewlett Packard’s System
Configuration Repository (SCR) for HP-UX and how to use them.
Although powerful, SCR is simple to use, if you have a basic
understanding of the HP-UX command syntax.
• Chapter 2 describes how to use SCR commands to configure the
program for operation. This is all you need to do to begin tracking
changes in your system quickly and easily.
• Chapter 3 describes the full capabilities of all 10 SCR commands.
The best way to learn SCR’s capabilities is to experiment with the
commands. SCR does not change any system configurations. Using a
command incorrectly may give you some error messages or strange
information, but it will not harm your system.
SCR Features SCR provides the following time-saving features:
• SCR can extract a static “snapshot” of a system's configuration by
request or by schedule, and store it in the persistent repository. A
snapshot is a record of a system’s configuration at a specific time.
• SCR snapshots stored in the repository can be compared with each
other to identify any differences.
• SCR configuration snapshots include all relevant configuration
information included in the Management Information Format (MIF)
for the Desktop Management Interface (DMI). See the DMI User’s
Reference for information about DMI and the MIF.
SCR shows you quickly what is going on in a system. As root user, you
can enter a command to learn the current status of a particular system
or an entire set of systems. With options to that command, you can
learn what changes have taken place recently. If desired, these com-
mands will execute according to a schedule and automatically generate
reports. By monitoring changes in a set of similarly configured systems,
SCR can give you advance warning of potential problems.
Using SCR, you can retrieve a snapshot and compare it to a previous
snapshot. This may reveal things that are going wrong in a system but
not generating error messages. SCR uses DMI programming routines to
gather information from systems. Be sure DMI is running and
managing each node for which you want a snapshot. See the DMI 2.0
User’s Reference for DMI installation and configuration instructions.

10 Chapter1
Introduction

11
2SCR Overview
This chapter describes SCR and how it works. Then it tells you how to
install SCR and how to configure it for first use. With this information,
you can be tracking system changes and viewing reports about system
nodes with SCR within a short time.
SCR consists of seven components:
• Configuration Management
• Data Management
• Filter Management
• Tag Management
• Presentation
• Repository Management
• Log Components.
The Repository component provides the internal software interface. The
other components provide the external user interface to SCR. Figure
2.1 shows the SCR Component structure.
Figure 2-1 SCR Component Structure
scrconfig(1m)
scrstatus(1m)
scrfilter(1m) scrtag(1m)
scrdaemon
scrupdate(1m)
scrdelete(1m)
scrhist(1m)
scrdiff(1m)
scrviewer(1m)
scrlog_viewer(1m)
Internal Interface
Routines
Filter
Configuration
Information
Configuration Mgmt Filter Mgmt Tag Mgmt
Data Mgmt Repository Presentation
Log scrlog

12 Chapter2
SCR Overview
The Configuration Management component provides the scrconfig
and scrstatus commands. Scrconfig maintains the configuration
data collection schedule and managed node list. Scrstatus generates a
status summary report of data collection activity.
The Data Management component provides the scrdaemon,scrupdate,
and scrdelete commands. Scrupdate collects configuration data from
a managed node through the DMI interface and stores data in the
repository. Scrdelete removes specified or expired configuration data
from the Repository. Scrdaemon invokes scrupdate based on the data
collection schedule maintained by Configuration Management
component.
The Filter Management component provides the scrfilter command
to refer to and update view filters. View filters are stored in the SCR
Repository.
The Presentation component provides the scrhist,scrdiff, and
scrviewer commands. These commands retrieve stored configuration
information and display it in human readable format.
The Tag Management component provides user friendly naming
capability for a snapshot. Using scrtag, you can change the name
“200102010005” for a snapshot to “StableSystem”. You can then use
StableSystem instead of 200102010005 in commands to the
Presentation components scrdiff and scrviewer.
The Log Component provides the scrlog_viewer command. This
command displays all SCR activities that have been recorded in a log
file with a graphical user interface.

Chapter 2 13
SCR Overview
Installing SCR
Installing SCR
SCR is part of the SCR+DMI bundle. Install SCR+DMI to use SCR.
SCR can only work on system nodes that have been configured to be
managed by DMI.
See the DMI User’s Reference document for an explanation of DMI
installation, concepts, and operations.
When SCR+DMI has been installed and the system configured, you can
begin using SCR commands to monitor your system, as described in the
next section.

14 Chapter2
SCR Overview
Using SCR
Using SCR
SCR has two types of management systems:
SCR can perform scheduled and on-demand configuration data collec-
tion on the CMS and all managed nodes.
For configuration data collection and management of system nodes,
DMI must be managing the nodes. You must include the CMS IP
address in that server’s /var/dmi/dmiMachines file. You also must add
the CMS IP address in each managed node’s /var/dmi/dmiMachines
file to allow access from the CMS.
The next step is to configure SCR to perform the data collection and
reporting you want, as described in the next section.
Table 2-1 SCR Management Systems
System Type Description
Central Management Server
(CMS) An HP-UX system that maintains
SCR
Managed Nodes Other HP-UX systems to be
managed by the CMS.

Chapter 2 15
SCR Overview
Configuring SCR
Configuring SCR
SCR must be configured to perform its data gathering and storing
tasks. Use the scrconfig command to specify SCR tasks for each
managed node.
Registering Managed Nodes
To begin, each managed node must be registered using the scrconfig
command. To register a managed node named elsa, type the following
command on your management server:
# scrconfig –n +elsa
The -n option to the scrconfig command applies the command to a
particular node. The +sign tells SCR to add the node. A -sign would
remove the node. This node is named elsa.
NOTE The request to register a managed node may fail if DMI is not properly
configured on the node or disallows access to the node from the CMS.
Repeat this operation for each system node that you want to track. You
can add multiple nodes with one command:
# scrconfig –n +
node1 + node2 + node3
Substitute your node names for node1 , etc. above. You can add as many
nodes as you want in one command. As the Repository can become quite
large, we recommend a maximum of 20 to 50 nodes per CMS, depending
on your CMS resources.

16 Chapter2
SCR Overview
Configuring SCR
Setting the Data Collection Schedule
The next step is to set up a day and time for the first data collection on
each registered node. SCR will collect data automatically at that day
and time each week. It takes a “snapshot” of the node data and stores it
in the repository.
Set the data collection schedule with the scrconfig command. For
example, enter the following command to set scheduled data collection
time at 12:05 Feb 7, 1999 for managed node elsa.
# scrconfig –n elsa –s 199902071205
As before, -n specifies a particular node that is named immediately
afterward. The -s option tells SCR to collect data at the time that
follows. Enter the time as shown above, with the full year digits,
followed without spaces by the month, day, and time digits. Time uses
the 24-hour clock.
To confirm that you entered the current schedule parameters correctly,
enter the following command:
# scrconfig –n elsa –l
The -l option tells SCR to list the schedule details for elsa on stdout.
The result resembles the following example:
NODE SCHEDULE TIME INTERVAL EXPIRATION TIMEOUT
elsa 02/07/1999 13:05 PST 1 day 3 months 5 minutes
This example shows that data will be collected from node elsa at 1:05
PM Pacific Standard Time on February 7, 1999, and will occur each day
after that at the same time. Snapshots will be deleted automatically
when they are three months old. (Snapshots that have been named
with the scrtag command will not be deleted. See the scrtag(1M) man
page in Chapter 3 for details.) The timeout parameter indicates that
SCR will try to collect data for five minutes each time, before giving up.
Data collection interval, expiration, and timeout parameters can be
customized on the command line, as well. See the scrconfig(1M) man
page or the description of the scrconfig command in Chapter 3 for
details.
If you omit the -n option and node name, scrconfig lists schedule
details for all registered nodes. A daemon invoked by the init process
controls data collection.
You can disable automatic data collection with the command:
# scrconfig –s off

Chapter 2 17
SCR Overview
Collecting Configuration Data On Demand
Collecting Configuration Data On Demand
The above steps set up automatic data collection on particular nodes at
particular times. For immediate data collection, use the scrupdate
command. For example, enter the following command to get a data
snapshot of the managed node ortrud:
# scrupdate –n ortrud
You will see a message similar to the following:
Configuration data “ortrud:
time ” is collected.
Collection can take from 5 to 15 minutes (and sometimes longer),
depending on the node size, network load, and how much data is
collected. See Using the Probe Filter, Chapter 3, to learn how to control
the amount of information that SCR collects from a node.
If configuration data for ortrud has changed since the last collection,
the new data will be placed in the SCR repository. If configuration data
has not changed, no data is stored.

18 Chapter2
SCR Overview
Checking Data Collection Status
Checking Data Collection Status
To check data collection status of all registered nodes, use the scrsta-
tus command. This provides a summary report of the last, current, and
scheduled data collection for all registered nodes, in time order.
# scrstatus
The report, printed to stdout, resembles the following example:
TIME (START – STOP) NODE STATUS DETAIL
02/06/199912:05 – 12:08 PST elsa Completed
02/06/199912:15 – 12:17 PST ortrud Warning - AcErr -
02/07/199916:37 - PST ortrud Executing
02/07/199900:05 - PST ortrud Scheduled
02/07/199912:05 - PST elsa Scheduled
This report appears in three blocks separated by vertical space. The
first block above (the first two lines) reports the most recent data
collection. The second block shows data collection being performed. The
last block shows future scheduled data collection. Some of these blocks
might be empty, especially when SCR is first installed.

Chapter 2 19
SCR Overview
Viewing Configuration Information on a Node
Viewing Configuration Information on a Node
Use the scrviewer command to see configuration information on a
node at a certain time. In the following example, we are using the
“latest” tag to get the most recent collected data. SCR automatically
assigns the latest collection time to the tag. The report tells us what
that time is.
# scrviewer elsa:latest
elsa : 04/10/1999 13:05 PDT (latest)
COMPONENT NAME VALUE
GROUP NAME
ATTRIBUTE NAME
HP Visualize Workstation
:
“HP-UX Standard Groups Definition”
:
“General Information”
[System Name] elsa
[System Location] 3000 Hanover St, Palo Alto, CA
:
If we wanted data from an earlier snapshot, we would have to enter the
time of the snapshot instead of the “latest” tag, or create a tag to
represent that information. (See “Using Tags to Simplify Node
Management” on page 23, for additional information about tags.)

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.