This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

VMware Smart Assurance 10.1.12.4 | 13 FEB 2024

Check for additions and updates to these release notes.

Product Description

A patch provides one or more fixes to a VMware Smart Assurance product. A patch can only be applied to the specific major or minor release and Service Pack of the particular product for which it is intended, this is called the product’s baseline.

What's New

  • Certified Devices

    • Simple Certification

    • Complex Certification

  • Fixed Issues

Simple Certifications

Simple certification involves only in configure file changes and the qualification of new OID in the currently existing driver. This section describes the devices certified in this patch.

Simple devices certified in the patch:

SR/TASC Number

Vendor Name

Description

SASS-16765/307032

CHECKPOINT

Certified the following components for the Check Point Smart-1 6000 FIREWALL (System OID:.1.3.6.1.4.1.2620.1.6.123.1.101): Disk,Fan,FileSystem,Inerface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.

SASS-16763/307031

CHECKPOINT

Certified the following components for the Maestro Hyperscale Orchestrator 140 FIREWALL (System OID:.1.3.6.1.4.1.2620.1.6.123.1.4000): Fan,FileSystem,Inerface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.

SASS-16772/307033

CISCO

Certified the following components for the FPR3140-NGFW-K9 FIREWALL (System OID:.1.3.6.1.4.1.9.1.3056): Fan,FileSystem,Inerface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.

SASS-16785/307051

CISCO

Certified the following components for the ciscoASR92012CZA-8201-24H8FH ROUTER (System OID:.1.3.6.1.4.1.9.1.3157): Interface,Memory,and Port.

SASS-16784/307048

CISCO

Certified the following components for the cevChassisC83001N1S6T ROUTER (System OID:.1.3.6.1.4.1.9.12.3.1.3.2222): Card,Fan,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

SASS-16764/307043

CISCO

Certified the following components for the ciscoC83001N1S6T ROUTER (System OID:.1.3.6.1.4.1.9.1.2989): Card,Fan,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

SASS-16768/307040

FORTINET

Certified the following components for the FortiGate 400F FIREWALL (System OID:.1.3.6.1.4.1.12356.101.1.4010): Disk,Fan,Inerface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.

SASS-16766/307034

FORTINET

Certified the following components for the Fortinet FG-1000F FIREWALL (System OID:.1.3.6.1.4.1.12356.101.1.10008): Disk,Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.

SASS-16767/307039

CISCO

Certified the following components for the ciscoIE33008P2S SWICTH (System OID:.1.3.6.1.4.1.9.1.2686): Card,Fan,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,and Vlan.

SASS-16769/306967

CISCO

Certified the following components for the ISR4451-X ROUTER (System OID:.1.3.6.1.4.1.9.1.1707): Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

SASS-16782/307076

FORTINET

Certified the following components for the FortiSwitch-548D-FPOE SWITCH (System OID:.1.3.6.1.4.1.12356.106.1.5481): Disk,Interface,Memory,Port,Processor,and Vlan.

SASS-16786/307078

CISCO

Certified the following components for the ciscoC83002N2S4T2X ROUTER (System OID:.1.3.6.1.4.1.9.1.2963): Card,Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

SASS-16787/307083

ZPE-NSR

Certified the following components for the NodeGrid Manager ROUTER (System OID:.1.3.6.1.4.1.42518.2.1): Interface,Memory,and Processor.

Complex Certification

Complex certifications involve re-certification, new device certifications, and involve new driver creations or multiple file changes. This section describes the devices certified in this patch.

Complex devices certified in the patch:

SR / TASC Number

Vendor Name

Description

SASS-16770/306968

CISCO

Certified the following components for the ISR 4351 ROUTER (System OID:.1.3.6.1.4.1.9.1.1999): Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

SASS-16771/306981

CISCO

Certified the following components for the cevChassisN5KC5672UP SWITCH (System OID:.1.3.6.1.4.1.9.12.3.1.3.1410): AggregatePort,Card,Fan,Memory,Port,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

SASS-16788/307002

AI

Certified the following components for the AI232 SWITCH (System OID:.1.3.6.1.4.1.539.2.12): Interface,Port,and Processor.

SASS-16753/307071

FORTINET

Certified the following components for the FG-100F FIREWALL (System OID:.1.3.6.1.4.1.12356.101.1.1000): Disk,Fan,Interface,Memory,Port,PowerSupply,Processor,and TemperatureSensor.

SASS-16783/307077

CISCO

Certified the following components for the N9K-C9364D-GX2A SWITCH (System OID:.1.3.6.1.4.1.9.12.3.1.3.2400): Card,Fan,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.

Certification impact

This section lists the impacted drivers and SysOIDs as a result of certification changes.

TASC Number

Impacted Drivers

Impacted SysOIDs

307002

HEALTH = AI-Health, CPU/Memory = Ai:DeviceID

.1.3.6.1.4.1.539.2.12

307077

HEALTH = Nexus-Entity-EntSensor, Environment = CiscoEntityFRU:DeviceID

.1.3.6.1.4.1.9.12.3.1.3.377 .1.3.6.1.4.1.9.12.3.1.3.1060 .1.3.6.1.4.1.9.12.3.1.3.1326 .1.3.6.1.4.1.9.12.3.1.3.1327 .1.3.6.1.4.1.9.12.3.1.3.612 .1.3.6.1.4.1.9.12.3.1.3.840 .1.3.6.1.4.1.9.12.3.1.3.719 .1.3.6.1.4.1.9.12.3.1.3.616 .1.3.6.1.4.1.9.12.3.1.3.777 .1.3.6.1.4.1.9.12.3.1.3.798 .1.3.6.1.4.1.9.12.3.1.3.1008 .1.3.6.1.4.1.9.12.3.1.3.1038 .1.3.6.1.4.1.9.12.3.1.3.1084 .1.3.6.1.4.1.9.12.3.1.3.1106 .1.3.6.1.4.1.9.12.3.1.3.1107 .1.3.6.1.4.1.9.12.3.1.3.1105 .1.3.6.1.4.1.9.12.3.1.3.932 .1.3.6.1.4.1.9.12.3.1.3.1163 .1.3.6.1.4.1.9.12.3.1.3.1238 .1.3.6.1.4.1.9.12.3.1.3.1308 .1.3.6.1.4.1.9.12.3.1.3.1147 .1.3.6.1.4.1.9.12.3.1.3.1237 .1.3.6.1.4.1.9.12.3.1.3.1467 .1.3.6.1.4.1.9.12.3.1.3.1352 .1.3.6.1.4.1.9.12.3.1.3.1354 .1.3.6.1.4.1.9.12.3.1.3.1508 .1.3.6.1.4.1.9.12.3.1.3.1390 .1.3.6.1.4.1.9.12.3.1.3.1507 .1.3.6.1.4.1.9.12.3.1.3.1388 .1.3.6.1.4.1.9.12.3.1.3.1627 .1.3.6.1.4.1.9.12.3.1.3.1625 .1.3.6.1.4.1.9.12.3.1.3.1409 .1.3.6.1.4.1.9.12.3.1.3.1489 .1.3.6.1.4.1.9.12.3.1.3.1626 .1.3.6.1.4.1.9.12.3.1.3.1619 .1.3.6.1.4.1.9.12.3.1.3.1491 .1.3.6.1.4.1.9.12.3.1.3.1666 .1.3.6.1.4.1.9.12.3.1.3.1353 .1.3.6.1.4.1.9.12.3.1.3.1239 .1.3.6.1.4.1.9.12.3.1.3.1660 .1.3.6.1.4.1.9.12.3.1.3.1712 .1.3.6.1.4.1.9.12.3.1.3.1824 .1.3.6.1.4.1.9.12.3.1.3.1175 .1.3.6.1.4.1.9.12.3.1.3.1812 .1.3.6.1.4.1.9.12.3.1.3.1570 .1.3.6.1.4.1.9.12.3.1.3.1539 .1.3.6.1.4.1.9.12.3.1.3.1697 .1.3.6.1.4.1.9.12.3.1.3.1743 .1.3.6.1.4.1.9.12.3.1.3.1758 .1.3.6.1.4.1.9.12.3.1.3.1759 .1.3.6.1.4.1.9.12.3.1.3.1839 .1.3.6.1.4.1.9.12.3.1.3.1726 .1.3.6.1.4.1.9.12.3.1.3.1843 .1.3.6.1.4.1.9.12.3.1.3.1389 .1.3.6.1.4.1.9.12.3.1.3.1454 .1.3.6.1.4.1.9.12.3.1.3.1675 .1.3.6.1.4.1.9.12.3.1.3.1744 .1.3.6.1.4.1.9.12.3.1.3.1519 .1.3.6.1.4.1.9.12.3.1.3.1291 .1.3.6.1.4.1.9.12.3.1.3.1850 .1.3.6.1.4.1.9.12.3.1.3.1921 .1.3.6.1.4.1.9.12.3.1.3.1954 .1.3.6.1.4.1.9.12.3.1.3.2039 .1.3.6.1.4.1.9.12.3.1.3.2010 .1.3.6.1.4.1.9.12.3.1.3.1955 .1.3.6.1.4.1.9.12.3.1.3.1506 .1.3.6.1.4.1.9.12.3.1.3.1648 .1.3.6.1.4.1.9.12.3.1.3.1727 .1.3.6.1.4.1.9.12.3.1.3.1788 .1.3.6.1.4.1.9.12.3.1.3.1609 .1.3.6.1.4.1.9.12.3.1.3.1621 .1.3.6.1.4.1.9.12.3.1.3.1746 .1.3.6.1.4.1.9.1.2804 .1.3.6.1.4.1.9.12.3.1.3.1893 .1.3.6.1.4.1.9.12.3.1.3.2238 .1.3.6.1.4.1.9.12.3.1.3.2272 .1.3.6.1.4.1.9.12.3.1.3.2377 .1.3.6.1.4.1.9.12.3.1.3.2237 .1.3.6.1.4.1.9.12.3.1.3.2076 .1.3.6.1.4.1.9.12.3.1.3.2054 .1.3.6.1.4.1.9.12.3.1.3.1509 .1.3.6.1.4.1.9.12.3.1.3.1894 .1.3.6.1.4.1.9.12.3.1.3.2239 .1.3.6.1.4.1.9.12.3.1.3.2378 .1.3.6.1.4.1.9.12.3.1.3.2193 .1.3.6.1.4.1.9.12.3.1.3.1828 .1.3.6.1.4.1.9.12.3.1.3.2353 .1.3.6.1.4.1.9.12.3.1.3.2340 .1.3.6.1.4.1.9.12.3.1.3.2400

307071

HEALTH = Fortigate-Health

.1.3.6.1.4.1.12356.101.1.810 .1.3.6.1.4.1.12356.101.1.1002 .1.3.6.1.4.1.12356.101.1.30160 .1.3.6.1.4.1.12356.101.1.50011 .1.3.6.1.4.1.12356.101.1.801 .1.3.6.1.4.1.12356.101.1.6200 .1.3.6.1.4.1.12356.106.1.50030 .1.3.6.1.4.1.12356.101.1.800 .1.3.6.1.4.1.12356.101.1.8001 .1.3.6.1.4.1.12356.101.1.12400 .1.3.6.1.4.1.12356.101.1.10001 .1.3.6.1.4.1.12356.101.1.2003 .1.3.6.1.4.1.12356.101.1.3002 .1.3.6.1.4.1.12356.101.1.502 .1.3.6.1.4.1.12356.101.1.39500 .1.3.6.1.4.1.12356.101.1.3005 .1.3.6.1.4.1.12356.101.1.10004 .1.3.6.1.4.1.12356.101.1.36004 .1.3.6.1.4.1.12356.101.1.37000 .1.3.6.1.4.1.12356.101.1.15000 .1.3.6.1.4.1.12356.101.1.50015 .1.3.6.1.4.1.12356.101.1.1004 .1.3.6.1.4.1.12356.101.1.2005 .1.3.6.1.4.1.12356.101.1.5004 .1.3.6.1.4.1.12356.101.1.51010 .1.3.6.1.4.1.12356.101.1.50013 .1.3.6.1.4.1.12356.101.1.60 .1.3.6.1.4.1.12356.101.1.20000 .1.3.6.1.4.1.12356.101.1.30400 .1.3.6.1.4.1.12356.101.1.2009 .1.3.6.1.4.1.12356.101.1.1041 .1.3.6.1.4.1.12356.101.1.3007 .1.3.6.1.4.1.12356.101.1.641 .1.3.6.1.4.1.12356.101.1.5005 .1.3.6.1.4.1.12356.101.1.5006 .1.3.6.1.4.1.12356.101.1.30 .1.3.6.1.4.1.12356.101.1.37001 .1.3.6.1.4.1.12356.101.1.900 .1.3.6.1.4.1.12356.101.1.60001 .1.3.6.1.4.1.12356.101.1.36011 .1.3.6.1.4.1.12356.101.1.38001 .1.3.6.1.4.1.12356.101.1.8003 .1.3.6.1.4.1.12356.101.1.3008 .1.3.6.1.4.1.12356.101.1.4007 .1.3.6.1.4.1.12356.101.1.12000 .1.3.6.1.4.1.12356.101.1.3006 .1.3.6.1.4.1.12356.101.1.46 .1.3.6.1.4.1.12356.101.1.6005 .1.3.6.1.4.1.12356.101.1.6006 .1.3.6.1.4.1.12356.101.1.42002 .1.3.6.1.4.1.12356.101.1.45 .1.3.6.1.4.1.12356.101.1.15002 .1.3.6.1.4.1.12356.101.1.18000 .1.3.6.1.4.1.12356.101.1.80008 .1.3.6.1.4.1.12356.101.1.34001 .1.3.6.1.4.1.12356.101.1.10006 .1.3.6.1.4.1.12356.101.1.845 .1.3.6.1.4.1.12356.109.1.10030 .1.3.6.1.4.1.12356.101.1.626 .1.3.6.1.4.1.12356.101.1.26001 .1.3.6.1.4.1.12356.101.1.10007 .1.3.6.1.4.1.12356.101.1.441 .1.3.6.1.4.1.12356.101.1.26000 .1.3.6.1.4.1.12356.101.1.15003 .1.3.6.1.4.1.12356.101.1.4010 .1.3.6.1.4.1.12356.101.1.10008 .1.3.6.1.4.1.12356.101.1.1000

306968

HEALTH = Cisco-Router-ASR-EntSensor

.1.3.6.1.4.1.9.1.923 .1.3.6.1.4.1.9.1.924 .1.3.6.1.4.1.9.1.1525 .1.3.6.1.4.1.9.1.1707 .1.3.6.1.4.1.9.1.2252 .1.3.6.1.4.1.9.1.2348 .1.3.6.1.4.1.9.1.2449 .1.3.6.1.4.1.9.1.2443 .1.3.6.1.4.1.9.1.2444 .1.3.6.1.4.1.9.1.2769 .1.3.6.1.4.1.9.1.3004 .1.3.6.1.4.1.9.1.2990 .1.3.6.1.4.1.9.1.2555 .1.3.6.1.4.1.9.1.2455 .1.3.6.1.4.1.9.1.2819 .1.3.6.1.4.1.9.1.2759 .1.3.6.1.4.1.9.1.2989 .1.3.6.1.4.1.9.1.2971 .1.3.6.1.4.1.9.1.3079 .1.3.6.1.4.1.9.1.2988 .1.3.6.1.4.1.9.12.3.1.3.2222 .1.3.6.1.4.1.9.1.3074

306984

HEALTH = Vss-health

.1.3.6.1.4.1.21671.1.2

Product and Version Details

Product

Version Number Details

IP

From <BASEDIR>/smarts/bin/, type the following command:

./sm_server --version (Linux)

The following output is displayed:

sm_server: linux_rhAS50-x86-64/301095700 IP_NETWORK_SUITE: V10.1.12.4(218178), 22-Jan-2024 06:02:17 Copyright 2024, VMware Inc - Build 8 Foundation V10.1.12.1(212834), 13-Jun-2023 14:06:52 Copyright 2023, VMware Inc - Build 1

Installation

A patch installs files to the <BASEDIR>/smarts/local directory of the product. The Installation software performs the following actions:

  • Backs up all files that are being replaced or merged.

  • Merges changes from your current, user-modifiable configuration files into the new versions of the files from the patch.

  • Displays complete summary at the end of patch installation.

  • Displays the location of a log file that lists the results of merging the files.

Note: If the original product was installed on one computer and then was copied to another computer, the patch cannot be applied to the copied installation. You must apply the patch to the computer with the original installation, and then the results can be copied to another computer.

Patch Installation File

You can install the patch on the host where the IP product is running. 

Binary details for 10.1.12.1 release are:

IP:setup-IP-linux-10_1_12_4-20240122-64BIT.bin

Note: You can download the binary from  https://support.vmware.com.

Installation directory

In this document, the term <BASEDIR> represents the location where Smarts software is installed.

For UNIX, the default location is:/opt/InCharge/<productsuite>.

The <productsuite>; represents the Smarts product suite to which the product belongs.

Optionally, you can specify the root of <BASEDIR> to be something other than /opt/InCharge (on UNIX) but you cannot change the name of the <productsuite> that is part of the <BASEDIR>.

Install a new patch over an older patch

Patches are cumulative each successive patch includes all of the fixes from any previous patches. As a result, a newer patch can be installed on top of an older patch. The patch number, which increments itself for each successive patch, indicates the version. A patch with higher version number can be installed over a patch with a lower version number.

The Installation software checks the version of the installed product and the version to be installed at the beginning of its process. It will not allow an older version to be installed on top of a newer version.

Apply patch using CLI mode

CLI mode provides a text-based method for invoking the Installation software. This mode is intended for UNIX platforms with non-graphic (text-only) consoles. The CLI mode installation follows the same process as the wizard mode but displays text on the terminal screen and requires user responses on the keyboard.

Run CLI mode

  1. Change directory to the directory where you typically store patches, for example, ./opt.

  2. Run following setup command and then press Enter. Replace xx with the relevant product name, for example: ESM. For exact name, see the Patch Installation File section:

           Setup command syntax for CLI mode (Linux): ./setup-IP-linux-10_1_12_4-20240122-64BIT.bin.

           A welcome message with information about the installation appears.

Note: Stop all VMware Smart Assurance services and processes that use programs or libraries from the product being upgraded or installed before performing the installation.

User selections and navigation in CLI mode

  • During the patch installation process, at the end of each screen of text, you are prompted with a set of options. For example:

           type 'back' - to go to the previous step

           type 'quit' - to cancel anytime

  • Select a choice by typing the text and press Enter.

  • Accept the default choice, and press Enter.

  • Other screens have different choices. For example when the license agreement is displayed, the following prompt appears:

           Press any key to continue to read license agreement or press '0' to advance to end.

  • At the end of the license agreement, the installation process displays the first of several menus.

           Choose from the following (Y/N) options:

           Y - to accept the terms of the license agreement.

           N - not to accept the terms of the license agreement.

  • Type the desired selection and press Enter. In the case of the license agreement, you must accept the agreement by typing Y and pressing Enter.

           The screen is displayed with an Get User Input. Choose the base location by entering the correct number.

            For example, type 1 to choose the default location for installation and press Enter.

     Get User Input

      1) /opt/InCharge 10.1.12.*

           For example, if the product name is ESM and default install folder is /opt/InCharge, the installer displays:

           VMware Smart Assurance Server Manager Suite will be installed in the following location:

           Product Name: ESM

           Install Folder: /opt/InCharge

  • Press Enter to continue the installation.

  • Press Enter to exit the installer.

           When the patch installation is complete, reconcile the configuration files as described in Reconcile user-modifiable files.

Apply patch using Unattended (Silent) mode

Unattended mode installs the patch without user input or a response file. When invoking the install program, specify the location of the product suite to be patched.

In order to invoke an unattended installation of the patch, type the appropriate setup command from below table and then press Enter. Replace “xx” with the relevant product name, for example, ESM. For exact name, see the Patch Installation File section:

Setup command syntax for unattended mode (Linux):setup-IP-linux-10_1_12_4-20240122-64BIT.bin -i silent -Product.installLocation=/opt/InCharge.

Where xx represents the product name.

Note: You must provide the correct base installation location. For example: base10.1 build is installed inside /opt/InCharge.

Once the installation is completed inside /tmp ** log file will be created with the summary. When the patch installation is complete, reconcile the configuration files as described in Reconcile user-modifiable files.

Log Files

Patch report and log file locations, lists the files that the Installation software creates during the install process.

Patch report and log file locations:

Name

Path

File Name

Install log

<BASEDIR>/smarts/setup/logs

Install.<product>_SUITE. <patchversion>.log

Merged files log

<BASEDIR>/smarts/setup/logs

merge-summary-<patch version>.log

Install log

The installer creates an Install log file listing all actions performed by the installation. You need not read this file unless you suspect an installation failure.

If the installation process fails, the log files are located in a temporary directory, for example /tmp or C:\temp. A non-zero status indicates a failure.

Merged files Log

This log lists the files in the BASEDIR/smarts/local directory structure that were merged. For each merged file, the log lists the location and name of the file. If any file cannot be merged due to conflicts, this is also noted. In addition, the log lists the name and location for unmerged versions of all user-modifiable files that are included in the patch.

For example, in case of ESM: 

  • Summary of merge operation can be found at location: /opt/InCharge/ESM/smarts/setup/logs/merge-summary-10.x.x.x.log

  • For more detail logs: /opt/InCharge/ESM/smarts/setup/logs/detail-merge-10.1.5.1.log

If there were any conflict during the merge operation, the old local backup file will be saved as "File_Name.bkp" in its same location. These conflict files needs to be merged manually before starting the server.

Review the results of the reconciliation process

The results of the reconciliation analysis performed during the installation and all actions taken are included in the merged files log located in <BASEDIR>/smarts/setup/logs. The name of the log file is: install.merge.<patch version>.log

Reconcile User-modifiable Files

The Installation software is designed to preserve your changes to user-modifiable files when installing new versions of these files. Existing changes to user-modifiable files are always automatically merged. All files are merged by default.

The Installation software also creates a backup of all the versions of the user-modifiable files to ensure that you will not lose any configuration data.

Review the results of the reconciliation process

The results of the reconciliation analysis performed during the installation and all actions taken are included in the merged files log located in <BASEDIR>/smarts/setup/logs. The name of the log file is: install.merge.<patch version>.log.

Determine which files require action by reviewing the merged files log generated by the install process:

  1. Using any editor, open and review the log:

    <BASEDIR>/smarts/setup/log/Install.Merge.10.x.x.x.log.

  2. Review the log:

    1. Resolve conflicts in files manually. See Resolve the issue in conflict files.

    2. During the installation, the entries that indicate file merges without conflicts that resulted in automerge files.

Resolve issues in conflict files

If a conflict occurs for any file in the same local directory of the file location, you can find the below files:

  • One is the conflict file. For example, <filename>

  • Another file is .bak.001. For example, <filename>.bak.001

Review the conflict files and resolve issues using the following procedure:

  1. Open the user-modifiable file where the conflict occurs using sm_edit.

    For example, the conflict file for esm.param.conf is named esm-param.conf.

  2. Review and resolve the conflict manually.

  3. Save and close the file.

To use patch introduced file (for example, esm-param.conf):

  1. Rename the original conflict file. (For example, if the conflict file name is esm-param.conf, rename the file esm-param.conf to esm-param.conf_old).

  2. Rename the <filename>.bak.001 file to the original file name <filename> by removing .bak.001 extension.

    For example, if the patch file name is esm-param.conf.bak.001, rename it to the esm-param.conf to use the original file.

  3. Save and close the file.

Note: All the user-modifiable unmerged files before patch installation, are backed up in "<BASEDIR>/<Product Name>/smarts" location. By default, the backup directory is hidden.

Uninstallation

Uninstalling a patch removes all previously applied patches and returns the software to the baseline product version.

Note:Root privileges are required to uninstall a patch. Use either the uninstaller program to uninstall a patch. Failure to use one of these methods can result in an unstable system and/or inconsistent product directories.

Before uninstallation

You must complete the following task before uninstalling the patch:

  • Stop all VMware Smart Assurance services and processes that use programs or libraries from the product.

Roll back to a previous patch

If you want to revert to a previous patch, you must:

  • Uninstall the currently installed patch to return to the baseline version.

  • Reinstall the previous patch.

For example, to revert from Patch 2 to Patch 1, uninstall Patch 2, and then reinstall Patch 1.

Uninstall Patch Using the Uninstaller Program

Use the uninstaller program to uninstall a patch:

Note: Do not to use the uninstaller program in the _uninst directory because it will remove the entire product.

  1. Change the directory or use the file navigator to find the _rpuninst directory.

    For Example: /opt/InCharge/<Product>/_rpuninst on UNIX systems.

  2. Invoke the uninstaller program.

    For example: ./uninstaller on UNIX systems.

  3. Press Enter to continue the uninstallation.

Uninstall Patch Using Unattended (Silent) Mode

Use the uninstaller program to uninstall a patch.

Note: Do not to use the uninstaller program in the _uninst directory because it will remove the entire product.

  1. Change the directory or use the file navigator to find the _rpuninst directory.

    For Example: /opt/InCharge/<Product>/_rpuninst on UNIX systems.

  2. Execute the uninstaller program.

    ./uninstaller -i silent on UNIX systems.

  3. Press Enter to continue the uninstallation.

check-circle-line exclamation-circle-line close-line
Scroll to top icon