|
VMware Smart Assurance 10.1.9 | 15 SEP 2022 Check for additions and updates to these release notes. |
VMware Smart Assurance supplies automated IT management insights, including:
With Smart Assurance 10.1.9 release, the following features, enhancements, and changes are introduced:
Following third-party software components are upgraded in VMware Smart Assurance 10.1.9:
For OSL (Open Source License) file (open_source_license_VMware_Smart_Assurance_GA.txt), navigate to <BASEDIR>/smarts/setup/osl.
In VMware Smart Assurance 10.1.9 release, support for RHEL 8.6 operating system is added.
SAM Console is now supported on Linux 8.x versions.
The VMware Smart Assurance SAM, IP, ESM, MPLS, and NPM Managers Support Matrix available from the VMware Support website provides the latest platform and interoperability information. For detailed information about platform support and interoperability, refer support matrix for your release.
SMARTA-1799/ SR 22330301605
PUT operation on notification throwing MsaError (OPERATION_ERROR).
Fix provided to handle PUT operation for SAM Notifications .
SMARTA-1805 / SR 22320251404
Rabbitmq messages are incrementing and not updating in M&R.
Fixed issue with mapping types in ES .
SMARTA-1795 / SR 22329686605
Warnings message appears in NCM collector manager logs, when NCM host has more than 9 CPUs due to issue in the script AppSvrPerf.sh file.
Updated grep command in AppSvrPerf.sh script file to handle host with more than 9 CPUs.
SMARTA-1544 / SR 21204961703
Additional timestamps displayed on the exported CUCM MOS and Smarts Alerts counts report.
Fix provided for frontend package to handle report exports.
SMARTA-1843 / SR-22320251404
The rabbitmq erlang20.2 files are missing in the third-party dependency.
Added required dependencies and fixed them in release 10.1.9.
SMARTA-1828 / SR-22334102806
Incorrect Notification count in M&R. By default Elasticsearch returns 10,000 documents for search queries.
The issue has been fixed by adding necessary flags to get all documents.
SMARTA-1632 / SR-22300233601
In M&R, multiple vulnerabilities are detected in java version used (1.8.0_281).
Java has been upgraded to 1.8.0_321 in M&R 7.4.1.1.
SMARTA-1779 / SR-22326829905
In M&R, critical vulnerability reported, due to log4j-1.2.15.jar and log4j 1.2.x has reached end of life.
Log4j 1.2.x is upgraded to Log4j 2.17.x in all components in M&R 7.4.1.1.
SMARTA-1729 / SR-22317467503
Manage Database Metrics does not popup metrics details in M&R 7.3.0.5.
The issue has been fixed in the core component in M&R 7.4.1.1.
SMARTA-1726 / SR-22311742903
Issue with formatting Value to String conversion in Table reports.
The issue has been fixed in core component in M&R 7.4.1.1.
SMARTA-1757 / SR-22322555104
User Sessions information not available, when external user session becomes inactive.
The issue has been fixed in core component in M&R 7.4.1.1.
SMARTA-1563 / SR-21267674910
Unable to login to FE with admin user when LDAP connectivity is failed due to SSL certificates not imported in 7.2.0.x.
The issue has been fixed in core component in M&R 7.4.1.1.
SMARTA-1914 / SR-22338856906
BGP 10.1.2 is not alerting on SNMP Agent Errors.
Fix provided to generate alarms on SNMP Agent Errors.
SMARTA-1599 / SR-21290332912
Discrepancies in the CUCM records between two stacks (primary and resilient), probable data loss.
The issue has been fixed in core component in M&R 7.4.1.1.
SMARTA-1832/ SR 22332003705
APM crash no proper exception handling.
Fixed the issue by handling the exception.
SMARTA-1733 / SR-22317392503
SMARTS OI stops processing the VMware vRealize Operations events.
DCF has been updated to request less queries from VMware vRealize Operations in order to reduce the number of queries, hence less data is requested from VMware vRealize Operations which increases the vROPS collector performances. Now there is optimised data which is being processed at the OI level.
Following warning message displayed in INCHARGE-OI logs:
MAIN_MSG-*-STDFD_ERR-stderr: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".SLF4J: Defaulting to no-operation (NOP) logger implementationSLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.This is a warning message , No Impact of functionality . To avoid this warning messgae, you can add a supporting jar or upgrade to slf4j 2.x version.
Default DCF password is not working for DCF SAM-OI communication. Notification will not be pulled from VMware vRealize Operations to SAM-OI.
Create a new user and password in DCF at <DCF Location>/Tools/Webservice-Gateway/Default/conf/users.
For example: admin1:admin123 at users file, and restart the Webservice-Gateway in DCF.
All Services are not installed post upgrade for SAM and SAM-Console.
Refer Services for the Service Assurance Manager section in VMware Smart Assurance Installation Guide to install services manually.
The Rabbit MQ service is not started in SAM.
Error:
[root@vmwbgc052 bin]# ./sm_rabbitmq --ignoreme ERROR: epmd error for host vmwbgc052: address (cannot connect to host/port) [root@vmwbgc052 bin]#If the RabitMQ process fails to start, you need to add the following mapping in the/etc/hosts file:
127.0.0.1 <FQDN of the host>
In some hosts, the pre-installed services such as smarts-tomcat and smarts-elasticsearch may fail to start.
Restart the ic-serviced daemon process by running the following commands:
/etc/init.d/ic-serviced stop /etc/init.d/ic-serviced stop
If the ic-business-dashboard service in SAM Console does not start, then restart the ic-serviced daemon process by running the earlier commands.
After SAM 10.1.2.0 upgrade, epmd service-related errors appear in the SAM upgrade log.
Log message:
/opt/InCharge/SAM/smarts/toolbox/OTP/erts-9.2/bin/epmd (Text file busy) at com.zerog.util.expanders.ExpandToDiskZip.ag(Unknown Source) at com.zerog.util.expanders.ExpandToDiskPMZ.ab(Unknown Source)SMARTS NCM adapter fails to connect to VSA domain managers when there are a higher number of domains registered with the broker.
As broker.getDomainManagers() API returning all domain managers attached to the broker and due to the character variable size restriction at the NCM adapter code, there are failures in processing the domain manager list. The acceptable characters are limited to 256.
Connect to the broker where there is less number of domain managers registered.
SAM Console upgrade is allowing on top of same existing version.
While installing SAM console in windows platform there is no registry check mechanism and hence user has to enter the upgrade path manually.
When all the EdgeNodes of NSX-T goes down which has Tier 0 Router due to ESX(Host)Down or VM going down, then Compute VMs host Unresponsive will not be explained by the Host(ESX) / VM Down RCA alert.
Currently there is no workaround available.
However, RCA alert will be shown only, impact to Host unresponsive will be not available for NSX-T Compute VMs. In the impact list EdgeNode Down, LogicalRouter(T0) Down is displayed.
User needs to mandatorily discover ESX Servers for getting Virtual Machine Down event.
Currently the Virtual Machine Down event is not generated if the corresponding ESX Servers are not discovered in IP Server. So, its recommended to discover Virtual Machines to get proper Root cause events.
When Kafka is not reachable, monitoring failure event appears in SAM after reconfiguration of ESM Server.
Workaround:
Few vSwitch and VMKernelPort are not getting deleted when deleting the NSXT-3.0 in ESM Domain Manager.
The stale entries need to be removed manually.
A set of reports are created by default when user installs the Smart Assurance Adapter pack.
These reports are retained in the dashboard even after uninstalling the management pack. Ideally, these reports must be deleted as part of the management pack uninstallation process.
User can manually delete the reports from the dashboard.
When a new credentials added without any username and password while configuring an instance of the adapter and edit it later with correct username and password, the password field wont be updated resulting the connection failure.
Edit the credentials again and update the password again and save it.
Patch files are getting migrated, when performing migration on ESM 10.0.0.1 and in IP 10.0.0.2 to 10.1.0.0 respectively.
This is applicable only if migration is triggered on the below two products and patch versions:
When performing migration only on the above two versions, you need to follow the below procedure:
Shutting down IP server with Cisco ACI discovered does not stop ACI Monitoring collector in DCF.
DCF cisco-aci monitoring collector needs to be stopped manually post stopping IP domain.
On RHEL 7.8 version, if you start any domain manager as a service, the domain gets registered to a broker using both v4 and v6 IP address space. Due to this issue domain manager v6 entry will go to DEAD state in brcontrol output and the communication between the servers is failing sometimes due to this issue. This issue also detected on some machines with RHEL 7.2 and 7.6.
To avoid a domain running in v6 mode, allow only v4, by setting the below flag in runcmd_env.sh file:
SM_IP_VERSIONS=v4
Restart the domain manager, after updating runcmd_env.sh file.
"-help" command installer displays following invalid options:
-i [gui] -jvmxms <size> -jvmxmx <size> -add <feature_name_1> [<feature_name_2 ...] -remove <feature_name_1> [<feature_name_2 ...] -repair -uninstallVMware Smart Assurance products in silent mode are getting installed in root folder, when user disable or comment the user install directory (<Products>SUITE.installLocation=/opt/InCharge) in silent response file.
Few Log messages are tagged as ERROR in the collector log incorrectly.
The vCenter Management Pack does not have any API to detect floating IP.
If a VNF (sprout or bono) is configured with floating IP and private IP, only the private IP is used to establish the relationship between VNFs (P-CSCF or I/S-CSCF) and VirtualMachines.
After successful installation, while viewing the content of management pack the number of dashboards displayed as 0 instead of 11.
There is no functional impact due this, you can still view all the management packs in the dashboard area.
ASAM server is not running in service way, but the user able to run via the Server way.
When the user installs any application with java 11 enabled on the VM, ic-serviced (sm_serviced) is also installed, which is compiled with java 11. And, when the user installs another application with java 8 installed (in this case ASAM), then the application crashes during the starting of service (ic-asam). This is because all the executables installed under ASAM bin directory are compiled with java 8 which in turn not compatible with ic-serviced, hence crashing only in the service way starting.
User needs to stop ic-serviced and start it again from the ASAM bin directory and then again try to start the server in service way. Also, the ASAM must be installed on a fresh VM without any other application installed along with it (except SAM CONSOLE Linux which is also on java 8).
Objects deleted in IP are not getting deleted in VMware vRealize Operations even after object deletion time interval.
To delete the objects manually:
URL available in User defined field 10 in SAM is not directing to the particular alert in VMware vRealize Operations when launched in browser.
This UserDefined10 is only applicable for VMware vRealize Operations version 8.6.2.
Upgrade option is not displayed for MPLS product.
This is applicable only when prior to version VSA 10.1.9 is installed.
Follow the procedure get the upgrade option:
Open /var/.com.zerog.registry.xml file from a machine where smarts is Installed, and perform the following changes:
1. MPLS independent upgrade:
Resolution : Under <product> tag search for old MPLS installation and modify id from 28322b95-1f3b-11b2-bb9a-eb6ec3979369to 28322b95-1f3b-11b2-bb9a-eb6ec3979370.
2. When NPM and MPLS installations are present in same directory, and incase user wants to upgrade NPM and then MPLS:
Resolution : Add below <product> tag content under <products> tag, just before MPLS upgrade:
<product name="MPLS" id="28322b95-1f3b-11b2-bb9a-eb6ec3979370" upgrade_id="db14898f-1f3a-11b2-a90c-eb6ec3979369" version="10.1.7.0" copyright="2019" info_url="VMware Inc" support_url="www.http://vmware.com" location="/opt/InCharge" last_modified="2022-07-29 05:02:08"><![CDATA[]]><vendor name="InstallAnywhere" id="2832bde7-1f3b-11b2-bb9a-eb6ec3979369" home_page="http://www.installanywhere.com" email="[email protected]"/><feature short_name="Application" name="Application" last_modified="2022-07-29 05:02:08"><![CDATA[This installs the application feature.]]><component ref_id="db1488e4-1f3a-11b2-a8c7-eb6ec3979369" version="1.0.0.0" location="/tmp/install.dir.4793/./devstat_err-javadoc.jar"/><component ref_id="db1488e3-1f3a-11b2-a8c8-eb6ec3979369" version="1.0.0.0" location="/opt/InCharge/MPLS/jre"/></feature></product>3. When MPLS and NPM installations are present in same directory, Incase user wants to upgrade MPLS and then NPM
Resolution : Add below <product> tag content under <products> tag, just before MPLS upgrade:
<product name="MPLS" id="28322b95-1f3b-11b2-bb9a-eb6ec3979370" upgrade_id="db14898f-1f3a-11b2-a90c-eb6ec3979369" version="10.1.7.0" copyright="2019" info_url="VMware Inc" support_url="www.http://vmware.com" location="/opt/InCharge" last_modified="2022-07-29 05:02:08"><![CDATA[]]><vendor name="InstallAnywhere" id="2832bde7-1f3b-11b2-bb9a-eb6ec3979369" home_page="http://www.installanywhere.com" email="[email protected]"/><feature short_name="Application" name="Application" last_modified="2022-07-29 05:02:08"><![CDATA[This installs the application feature.]]><component ref_id="db1488e4-1f3a-11b2-a8c7-eb6ec3979369" version="1.0.0.0" location="/tmp/install.dir.4793/./devstat_err-javadoc.jar"/><component ref_id="db1488e3-1f3a-11b2-a8c8-eb6ec3979369" version="1.0.0.0" location="/opt/InCharge/MPLS/jre"/></feature></product>Add below tag before NPM upgrade, if not present.
<product name="NPM" id="28322b95-1f3b-11b2-bb9a-eb6ec3979369" upgrade_id="db14898f-1f3a-11b2-a90c-eb6ec3979369" version="10.1.7.0" copyright="2019" info_url="VMware Inc" support_url="www.http://vmware.com" location="/opt/InCharge" last_modified="2022-08-02 02:28:34"><![CDATA[]]><vendor name="InstallAnywhere" id="2832bde7-1f3b-11b2-bb9a-eb6ec3979369" home_page="http://www.installanywhere.com" email="[email protected]"/><feature short_name="Application" name="Application" last_modified="2022-08-02 02:28:34"><![CDATA[This installs the application feature.]]><component ref_id="db1488e4-1f3a-11b2-a8c7-eb6ec3979369" version="1.0.0.0" location="/tmp/install.dir.7209/./devstat_err-javadoc.jar"/><component ref_id="db1488e4-1f3a-11b2-a8c7-eb6ec3979369" version="1.0.0.0" location="/opt/InCharge/NPM/_uninst/uninstaller"/></feature></product>Ensure that, the 'location' and 'version' attributes are updated correctly as per existing smarts deployment location and version.
For older known issues and fixed issues, refer previous VMware Smart Assurance Release Notes.
