Red Hat NETWORK PROXY 5.3.0 - Podręcznik Użytkownika Pobierz pdf (Strona 175)

If you define an alternate location for a particular Machine Group such as Servers (in Patching | VCM

Patching Administration | Machine Group Mapping wizard | Local Patch Path), you must select that

Machine Group at the top of the VCM Portal before you deploy the patches. Otherwise, if the same

Machine Group is not selected, VCM Patching will not acknowledge the machine group mapping to the

alternate patch location, and the patches will not be deployed.

Default Location for UNIX/Linux Patches

If you do not define an alternate location for the patches using Machine Group Mapping, the default

location of /tmp will be used. A temporary expansion of the patches will be performed in the /tmp

directory.

Deploy Patches to UNIX/Linux Machines

After running the assessment template and evaluating the results, and acquiring and storing the patches,

you can install the patches on the UNIX/Linux machines that are managed by VCM Patching. The deploy

action assesses whether the patch was installed on the VCM-managed machine.

For a list of UNIX/Linux machines and operating systems supported for patch deployment, see the VCM

Hardware and Software Requirements Guide.

Prerequisites for Deployment

Before deploying the patches to VCM-managed UNIX/Linux machines, ensure the following:

VCM Patching for UNIX must be licensed on the UNIX/Linux machine.

Ensure that the assessments have run successfully.

The patches must be available locally to the VCM-managed machine.

IMPORTANT If you will be deploying patches in single-user mode on UNIX machines, you MUST do

the following:

1) Store or extract the patches in a local location other than /tmp that will be accessible in single user-

mode.

2) If you did not manually extract the files in step 1, ensure enough disk space exists to extract the

patches in /var/tmp.

3) Set the machine group mapping to the patch path location where you have stored the patches.

If you will be deploying patches without changing the run level, you must do the following:

1) Store or extract the patches in a local location (not /tmp on Solaris as this directory will be cleaned out

upon reboots that may be initiated by the patches).

2) If you did not manually extract the files in step 1, ensure enough disk space exists to extract the

patches in /tmp (or /var/tmp on Solaris).

3) Set the machine group mapping to the patch path location where you have stored the patches.

Default Location for UNIX/Linux Patches

If you do not define an alternate location for the patches using Machine Group Mapping, the default

location of /tmp will be used. A temporary expansion of the patches will be performed in the /tmp

directory.

Deploying the Patches

NOTE Before deploying patches, see Patch Deployment Notes in the online Help.

Getting Started with VCM Patching

VMware, Inc. 175

1 2 ... 170 171 172 173 174 175 176 177 178 179 180 ... 273 274

Brak uwag

Red Hat NETWORK PROXY 5.3.0 - Podręcznik Użytkownika Strona 175