test

Sun Update Connection - Automated Baseline Management Service 1.0 User's Guide

ProcedureHow to Create Individual TLP Patch Sets

This procedure describes how to use tlp commands to create individual patch sets.

Note –

This procedure describes how to create patch sets on demand. You might choose to set up a cron job to run this task at regularly scheduled intervals. For the best performance, value, and ease of use, TLP is configured to run weekly. Scheduling frequent TLP runs enables the tool to capture system changes and adjust patch set creation accordingly. For more information on setting up and running cron jobs, see Chapter 15, Scheduling System Tasks (Tasks), in System Administration Guide: Advanced Administration. Ensure that the TLP client also provides system information according to this schedule. See The TLP Client Run Process.

Before You Begin

Before beginning this procedure, you must have previously done the following:

Steps

  1. Log in to the system as the tlp-user.

  2. Create a patch set for all client systems.


    $ tlp main

    The tlp main command creates patch sets for all the client systems where the Explorer dumps exist.

  3. Locate the patch sets that were created for the phase, GREEN, in the directory, data/target/GREEN.

    You will now find the patch sets that were created for the phase, GREEN, in the data/target/GREEN directory. In this directory, a separate subdirectory for each client system was also created. You can adjust the allowed age of the TLP client data by modifying the explorer module in the tlp.cfg file, as shown in the following example:


    # ===================================================================
# System Info Collector which is responsible for collecting a nodes 
# sytem information
 
 <module explorer>
		# Fetches Explorer information from a directory
   Class Tlp::Collector::explorer            
 
 	# This directory contains explorer info
  	Directory $DataDirectory/explorer      
 
   # Optional: List with node names to examine. Each line
   # must be a name of a system. If this list is not provided
   # all Explorer dumps in the provided directory are examined
   # NodeList $DataDirectory/explorer/nodes.lst
 
   # Time after which an Explorer dump is regarded as obsolete.  
   # Unit can be "days", "weeks" or "months"
   # Default value are "4 Weeks"
   # MaxAge 4 weeks
 
</module>

    The TLP tool then runs an external analyzer to determine which patches are missing on a given system.

    For TLP 2.3, PatchPro is the analyzer that is used. You can choose to use another analyzer by modifying the analyzer section in the tlp.cfg file.

    Usually, all of the required patches have been installed on the TLP system with the snapshots. However, if the patches are not available, TLP attempts to download them.

  4. (Optional) To enable TLP to download patches from an external location, configure the Loader module in the tlp.cfg file.

    There are three Loader modules that you can use:

    • sunsolve

      Configure the sunsolve module to download patches directly from the SunSolve web site. Note that the user and proxy data must be entered correctly in the SunSolve module for TLP to work correctly.

    • swanloader

      Configure the swanloader module to download patches directly through a proxy server. Note that you must have an Internet connection to use this configuration value.

    • dirloader

      If you do not have access to the Internet, use the DirLoader module to load patches from a separate directory. Store missing patches in a directory that is accessible to TLP. Configure the DirLoader to find that directory.

    To use a particular Loader module, uncomment the line for that module in the tlp.cfg file, as shown in the following example:


    # Please be sure, that the sunsolve login and proxy parameters are set
# properly.if you want to enable loading of missing patches from
# SunSolve. Uncomment the Loader, you want to use.
# Loader sunsolve
# Loader swanloader
# Loader dirloader
.
.
.

    TLP then uses the DirProducer module to store the created patch sets, along with any helper files. Adjust the values in the tlp.cfg file, as appropriate.

  5. Check the results

    You will now find the created patch sets for the phase, GREEN, in the data/target/GREEN directory, where for each client system a separate subdirectory has been created. For information on how to install the patch sets on client systems, see How to Install a TLP Patch Set.

  6. To view the results and plan system updates across the data center, read the HTML reports that were automatically created below the data/target/reports/ directory.

    For information on how to interpret the HTML reports, see TLP Reporting.

    Note –

    In some cases, the TLP tool creates results that might not suit your needs. These results occur when the client systems run applications that require certain patch levels, or if third-party hardware is installed on the system. TLP cannot analyze this type of information. In these instances, you can direct the tool to add or remove patches from the patch sets. To do so, modify the results by using the whitelist and blacklist files. For more information on how to modify TLP results by using whitelists and blacklists, see How to Customize Whitelists and Blacklists.

Example 2–6 Creating a Patch Set

This example shows the output for a single system. The TLP tool completes this process on all client systems for which it finds up-to-date system information.


$ ./tlp main

  TLP - Creating Patch Set
  ------------------------
  
  --- GREEN:2003-05-27:edkclu0  ------------------------------
     * Tlp::Analyzer::PatchPro
       >........>.>>>.>.....>..>.>>...>>>>.>.>...>.>>
     * Tlp::Resolver::PatchDiag
     + Parsing cross-reference
  100% [===========================================]
     * Tlp::Producer::DirProducer (data/target/2003-05-27/edkclu0)
     + Checking patches
       .-.............-......-...
     + 108528-20 ... loading
     + Checking SunSolve CHECKSUM
     + Reloading CHECKSUMS: old size = 802973
     + Loading CHECKSUMS (803750 bytes)
  100% [===========================================]
     * Tlp::Loader::SunSolve
     + Loading 108528-23.zip (27076411 bytes)
  100% [===========================================]
     + Extracting ...
     + 108727-24 ... loading
     * Tlp::Loader::SunSolve
     + Loading 108727-25.zip (375168 bytes)
  100% [===========================================]
     + Extracting ...
     + 108974-28 ... loading
     * Tlp::Loader::SunSolve
     + Loading 108974-33.zip (615134 bytes)
  100% [===========================================]
     + Extracting ...
     + Copying patches
  100% [===========================================]
     + Creating support files