5.7.2
Table Of Contents
- Software Content Repository Tool 5.1 Guide
- Contents
- About This Book
- Introduction to the Software Content Repository Tool
- Preparing for SCR Tool Installation
- Installing the Prerequisite Software for the SCR Tool
- Configuring the Red Hat Host Machine
- Managing Patch Content with the SCR Tool
- Troubleshooting the SCR Tool
- Out of Memory Error
- Content Download Network Connection Error
- Cannot Connect to Red Hat Account
- Session Login to Red Hat Fails
- Download from Red Hat Fails
- HP-UX Service Authentication Fails
- Download from HP Fails
- Proxy Server Configuration Fails
- Mismatch in Number of Patches
- OS Vendor Does Not Accept Credentials
- OS Vendor Errors
- Patch Download Errors
- Obsolete Patches Cause the Download to Fail
- HTTP Errors Are Not Marked as SEVERE
- Connection Refused Errors
- Null Pointer Exception Errors
- Index
Managing Patch Content with the SCR
Tool
5
Managing Patch Content with the SCR Tool
The SCR Tool downloads patch content files from the Content Download Network (CDN), which is
managed by Akamai, the hosted content service provider. The SCR Tool obtains any additional patches
from the AIX (IBM), CentOS, HP-UX, Mac OS X, Oracle Enterprise Linux (OEL), Red Hat, SUSE, and Solaris
vendor Web sites, and saves those patches in your defined directories.
The SCRTool performs delta downloads. After the first download, successive downloads retrieve only the
differences in patch content that occurred since the last download. When the files download, the patch
source, CDN, vendor, and other information is written to the log files.
IMPORTANT Do not delete the patch signature (.pls) files, because they confirm whether the patches are
available. Patch signature files are stored in the platform subdirectories defined by the property parameter
SCR_output_folder.
This chapter includes the following topics:
Download the Patch Content 29
Schedule Downloads 30
Maintain the Software Content Repository 31
Download the Patch Content
You download patch content to the SCR Tool machine so that you can deploy the patches to the supported
VCM managed machines.
Prerequisites
n If you run multiple replication processes simultaneously on a single SCR Tool host machine, verify that
the host machine has sufficient memory to support each process. Insufficient memory might cause
errors.
Procedure
1. To specify a schedule to run the shell commands, use a crontab command to run the updated
properties files.
2. From the directory defined as SCR_output_folder, open a terminal session.
3. Run the following commands to interactively track the progress of the download.
date; df -k ; du -k | grep -i Vendor_Name
When the patch download process is finished, use VCM to patch the Linux and UNIX managed machines.
VMware, Inc.
29