The release notes cover the following topics

About VMware Smart Assurance GA Patch

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 in this Release

The VMware Smart Assurance 10.1.2.15 introduces the following enhancement:

  • Following System OIDs are certified in this release: 

Certified Devices

This section describes the devices certified and the certification impact in this patch.

Simple Certification

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-16014/306555 CISCO Certified the following components for the ciscoASA5512sc Firewall (System OID:.1.3.6.1.4.1.9.1.1411):
Interface,Memory,and Processor.
SASS-16020/306518 FORTINET Certified the following components for the FortiGate-2200E Firewall (System OID:.1.3.6.1.4.1.12356.101.1.18000):
Disk,Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.
SASS-16018/306516 FORTINET Certified the following components for the FortiGate-VM64-KVM Firewall (System OID:.1.3.6.1.4.1.12356.101.1.80008):
Disk,Interface,Memory,and Processor.
SASS-16031/306535 ALLIEDTELESIS Certified the following components for the at-8088-SC Switch (System OID:.1.3.6.1.4.1.207.1.4.87):
Interface,Port,and Vlan.
SASS-16033/306547 CISCO Certified the following components for the ciscoC11278PLteP Router (System OID:.1.3.6.1.4.1.9.1.2759):
Card,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,and Vlan.
SASS-16053/306559 FORTINET Certified the following components for the FortiGate 80F Firewall (System OID:.1.3.6.1.4.1.12356.101.1.845):
Disk,Interface,Memory,Processor,and TemperatureSensor.
SASS-16054/306557 FORTINET Certified the following components for the FortiProxyVM64 Firewall (System OID:.1.3.6.1.4.1.12356.109.1.10030):
Disk,Interface,Memory,and Processor.
SASS-16049/306481 FORTINET Certified the following components for the FortiGate-1100E Firewall (System OID:.1.3.6.1.4.1.12356.101.1.10006):
Disk,Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.
SASS-16050/306513 FORTINET Certified the following components for the FortiGate-3400E Firewall (System OID:.1.3.6.1.4.1.12356.101.1.34001):
Disk,Fan,Interface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.
SASS-16060/306485 CHECKPOINT Certified the following components for the MHO-175 Firewall (System OID:.1.3.6.1.4.1.2620.1.6.123.1.4002):
Disk,Interface,Memory,PowerSupply,and Processor.
SASS-16063/306469 INFOBLOX Certified the following components for the IB-4025 Host (System OID:.1.3.6.1.4.1.7779.1.1525):
Disk,Fan,FileSystem,Interface,Memory,MemoryGroup,PowerSupply,Processor,ProcessorGroup,and TemperatureSensor.
SASS-16084/306521 ARISTA Certified the following components for the DCS-7050CX3M-32S Switch (System OID:.1.3.6.1.4.1.30065.1.3011.7050.2733.3.972.32.3282):
Interface,Memory,Port,Processor,and Vlan.
SASS-16074/306509 JUNIPER Certified the following components for the jnxProductQFX512032C Switch (System OID:.1.3.6.1.4.1.2636.1.1.1.4.82.24):
AggregatePort,Card,Disk,Fan,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.
SASS-16077/306460 BLUE-COAT Certified the following components for the sgvmwareesx Host (System OID:.1.3.6.1.4.1.3417.1.1.30):
Disk,Interface,Memory,MemoryGroup,Processor,and ProcessorGroup.
SASS-16096/306504 ADVA Certified the following components for the OSA 5422 Switch (System OID:.1.3.6.1.4.1.5551.3.27):
Interface,Port,and PowerSupply.
SASS-16093/306507 CISCO Certified the following components for the IE-3300-8U2X Switch (System OID:.1.3.6.1.4.1.9.1.3008):
AggregatePort,Card,Fan,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,and Vlan.
SASS-16091/306508 ALCATEL Certified the following components for the OmniSwitch6860E-24 Switch (System OID:.1.3.6.1.4.1.6486.801.1.1.2.1.11.1.5):
Card,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,and Vlan.
SASS-16086/306526  JUNIPER Certified the following components for the jnxProductNameACX2100 Router (System OID:.1.3.6.1.4.1.2636.1.1.1.2.116):
Card,Disk,Interface,Memory,PowerSupply,Processor,TemperatureSensor,and VoltageSensor.
SASS-16098/306523 CISCO Certified the following components for the ciscoC9120AXME WirelessController (System OID:.1.3.6.1.4.1.9.1.2850):
Memory,Port,and Processor.
SASS-16128/306466 ARISTA Certified the following components for the DCS-7368 Switch (System OID:.1.3.6.1.4.1.30065.1.7368):
Interface,Memory,Port,Processor,and Vlan.
SASS-16121/306459 FORTINET Certified the following components for the FWF60D Firewall (System OID:.1.3.6.1.4.1.12356.101.1.626):
Disk,Interface,Memory,and Processor.
SASS-16124/306462 CISCO Certified the following components for the UCS 6454 Switch (System OID:.1.3.6.1.4.1.9.12.3.1.3.1828):
AggregatePort,Card,Fan,Memory,Port,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.
SASS-16139/306317 RAD Certified the following components for the vRIC Router (System OID:.1.3.6.1.4.1.164.6.1.6.38):
Interface.
SASS-16135/306491 NETAPP Certified the following components for the NetApp-8.1.2RC1-Cluster-Mode FileServer (System OID:.1.3.6.1.4.1.789.2.5):
Disk,FileSystem,Processor,and ProcessorGroup.

Complex Certifications

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-16045/306505 ALLIEDTELESIS Certified the following components for the at-8100S-16F8-LC Switch (System OID:.1.3.6.1.4.1.207.1.4.176):
Fan,Interface,Port,PowerSupply,TemperatureSensor,and Vlan.
SASS-16057/306534 ALLIEDTELESIS Certified the following components for the at-FS970M-16F8-LC Switch (System OID:.1.3.6.1.4.1.207.1.4.239):
Fan,Interface,Port,PowerSupply,TemperatureSensor,and Vlan.
SASS-16065/306520 ARUBA Certified the following components for the s3500-24P Switch (System OID:.1.3.6.1.4.1.14823.1.1.24):
Card,Fan,FileSystem,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,and Vlan.
SASS-16068/306548 ALLIEDTELESIS Certified the following components for the at-8516F Switch (System OID:.1.3.6.1.4.1.207.1.4.100):
Interface,Port,and Vlan.
SASS-16107/306139 F5NETWORKS   Certified the following components for the BIG-IP-I4600 LoadBalancer (System OID:.1.3.6.1.4.1.3375.2.1.3.4.106):
AggregatePort,Disk,Fan,FileSystem,Interface,Memory,Port,PowerSupply,Processor,TemperatureSensor,and Vlan.
SASS-16132/306558 CISCO Certified the following components for the ciscoFpr4120K9 Firewall (System OID:.1.3.6.1.4.1.9.1.2294):
AggregateInterface,Card,Fan,Memory,Interface,PowerSupply,Processor,TemperatureSensor,VoltageSensor,and Vlan.
SASS-16137/306465 INFINERA Certified the following components for the lumentis FibreChannelSwitch (System OID:.1.3.6.1.4.1.8708):
Card,Fan,Interface,Memory,Port,PowerSupply,Processor,and TemperatureSensor.
SASS-16130/306537 EXTREME Certified the following components for the X460G2-24-10G4 StackSwitchSystem (System OID:.1.3.6.1.4.1.1916.2.93):
AggregatePort,Card,Fan,Interface,Memory,Port,PowerSupply,Processor,and TemperatureSensor.
SASS-16029/306560 FORTINET Certified the following components for the FortiSwitch-148F Switch (System OID:.1.3.6.1.4.1.12356.106.1.1484):
Disk,Interface,Memory,Port,Processor,and Vlan.
 

Certification impact

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

TASC Number Impacted Drivers Impacted SysOIDs
306560 HEALTH             = FortiSwitch-Health .1.3.6.1.4.1.12356.106.1.1484
306505,
306534,
306548		 HEALTH             = AlliedWare-Health
VLAN             = AlliedWare

.1.3.6.1.4.1.207.1.4.176
.1.3.6.1.4.1.207.1.4.239
.1.3.6.1.4.1.207.1.4.100
306520 HEALTH             = Aruba-Switch-Controller

.1.3.6.1.4.1.14823.1.1.24
306139 HOSTRESRCS                = F5-MIB2 .1.3.6.1.4.1.3375.2.1.3.4.106
.1.3.6.1.4.1.3375.2.1.3.4.11
.1.3.6.1.4.1.3375.2.1.3.4.10
.1.3.6.1.4.1.3375.2.1.3.4.4
.1.3.6.1.4.1.3375.2.1.3.4.6
.1.3.6.1.4.1.3375.2.1.3.4.5
.1.3.6.1.4.1.3375.2.1.3.4.8
.1.3.6.1.4.1.3375.2
.1.3.6.1.4.1.3375.2.1.3.4.12
.1.3.6.1.4.1.3375.2.1.3.4.21
.1.3.6.1.4.1.3375.2.1.3.4.20
.1.3.6.1.4.1.3375.2.1.3.4.1000
.1.3.6.1.4.1.3375.2.1.3.4.23
.1.3.6.1.4.1.3375.2.1.3.4.22
.1.3.6.1.4.1.3375.2.1.3.4.13
.1.3.6.1.4.1.3375.2.1.3.4.2
.1.3.6.1.4.1.3375.2.1.3.4.1
.1.3.6.1.4.1.3375.2.1.3.4.24
.1.3.6.1.4.1.3375.2.1.3.4.25
.1.3.6.1.4.1.3375.2.1.3.4.19
.1.3.6.1.4.1.3375.2.1.3.4.43
.1.3.6.1.4.1.3375.2.1.3.4.57
.1.3.6.1.4.1.3375.2.1.3.4.53
.1.3.6.1.4.1.3375.2.1.3.4.26
.1.3.6.1.4.1.3375.2.1.3.4.48
.1.3.6.1.4.1.3375.2.1.3.4.61
.1.3.6.1.4.1.3375.2.1.3.4.87
.1.3.6.1.4.1.3375.2.1.3.4.81
.1.3.6.1.4.1.3375.2.1.3.4.59
.1.3.6.1.4.1.3375.2.1.3.4.82
.1.3.6.1.4.1.3375.2.1.3.4.47
.1.3.6.1.4.1.3375.2.1.3.4.60
.1.3.6.1.4.1.3375.2.1.3.4.71
.1.3.6.1.4.1.3375.2.1.3.4.63
.1.3.6.1.4.1.3375.2.1.3.4.80
.1.3.6.1.4.1.3375.2.1.3.4.84
.1.3.6.1.4.1.3375.2.1.3.4.94
.1.3.6.1.4.1.3375.2.1.3.4.72
.1.3.6.1.4.1.3375.2.1.3.4.70
.1.3.6.1.4.1.3375.2.1.3.4.97
.1.3.6.1.4.1.3375.2.1.3.4.89
.1.3.6.1.4.1.3375.2.1.3.4.83
.1.3.6.1.4.1.3375.2.1.3.4.95
.1.3.6.1.4.1.3375.2.1.3.4.99
.1.3.6.1.4.1.3375.2.1.3.4.108
.1.3.6.1.4.1.3375.2.1.3.4.33
.1.3.6.1.4.1.3375.2.1.3.4.46
.1.3.6.1.4.1.3375.2.1.3.4.78
.1.3.6.1.4.1.3375.2.1.3.4.107
.1.3.6.1.4.1.3375.2.1.3.4.77
.1.3.6.1.4.1.3375.2.1.3.4.101
.1.3.6.1.4.1.3375.2.1.3.4.104
.1.3.6.1.4.1.3375.2.1.3.4.109
.1.3.6.1.4.1.3375.2.1.3.4.105
.1.3.6.1.4.1.3375.2.1.3.4.118
.1.3.6.1.4.1.3375.2.1.3.4.111
.1.3.6.1.4.1.3375.2.1.3.4.130
.1.3.6.1.4.1.3375.2.1.3.4.122
.1.3.6.1.4.1.3375.2.1.3.4.110
.1.3.6.1.4.1.3375.2.1.3.4.112
.1.3.6.1.4.1.3375.2.1.3.4.85
.1.3.6.1.4.1.3375.2.1.3.4.92
.1.3.6.1.4.1.3375.2.1.3.4.102
.1.3.6.1.4.1.3375.2.1.3.4.86
.1.3.6.1.4.1.3375.2.1.3.4.113
.1.3.6.1.4.1.3375.2.1.3.4.91
306558 CONT              = Cisco-FirePower-4120
    HEALTH            = Cisco-FirePower-4120		 .1.3.6.1.4.1.9.1.2294
306465 CONT                 = Infinera-Switch
HEALTH                 = Infinera-Switch		 .1.3.6.1.4.1.8708
306537 CONT = Extreme-Summit .1.3.6.1.4.1.1916.2.93
.1.3.6.1.4.1.1916.2.6
.1.3.6.1.4.1.1916.2.12
.1.3.6.1.4.1.1916.2.15
.1.3.6.1.4.1.1916.2.66
.1.3.6.1.4.1.1916.2.56
.1.3.6.1.4.1.1916.2.54
.1.3.6.1.4.1.1916.2.71
.1.3.6.1.4.1.1916.2.22
.1.3.6.1.4.1.1916.2.76
.1.3.6.1.4.1.1916.2.58
.1.3.6.1.4.1.1916.2.77
.1.3.6.1.4.1.1916.2.82
.1.3.6.1.4.1.1916.2.129
.1.3.6.1.4.1.1916.2.72
.1.3.6.1.4.1.1916.2.155
.1.3.6.1.4.1.1916.2.154
.1.3.6.1.4.1.1916.2.223
.1.3.6.1.4.1.1916.2.227

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.2.15(200546), 17-Jan-2022 13:40:57 Copyright 2022, VMware Inc - Build 88
Foundation V10.1.2.1(198125), 08-Oct-2021 17:45:02 Copyright 2021, VMware Inc - Build 4

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 detail for IP-10.1.5.4 release is:

IP:setup-IP-linux-10_1_2_15-20220118-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_2_15-20220118-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.5.*

           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_2_15-20220118-64BIT.bin -i silent -DrpProduct.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