VMware Smart Assurance supplies automated IT management insights, including:
Intelligent, automated root-cause and impact analysis
Event correlation
Discovery and modelling of IT environments being monitored. These insights enable IT operations personnel to visualize, analyze, and optimize the availability, performance, and configurations of their physical and virtual network, server, and storage environments so that service levels can be met or exceeded.
With Smart Assurance 10.1.12 release, the following features, enhancements, and changes are introduced:
M&R 7.5.0.3 [build 189]. Following SolutionPacks are qualified with M&R 7.5.0.3:
Health
Cisco IPSLA
Cisco Unified Communication Manager
VMware vCenter
Traffic Flows
VMware Smarts
Support for VMware vSphere 8.0b and 7.0u3j in ESM and M&R:
vSphere 8.0b and 7.0u3j, discovery and monitoring are qualified on ESM. Also reporting through VMware vCenter SolutionPack is qualified on M&R 7.5.0.3.
Support for VMware NSX-T 4.1 in ESM
Discovery and Monitoring of VMware NSX-T 4.1 has been qualified.
Support for VMware VMware vCloud Director in ESM
Discovery and Monitoring of VMware vCloud Director 10.4 has been qualified.
Support for VMware vRealize Operations 8.6.4.
Discovery and Monitoring of VMware vRealize Operations 8.6.4 has been qualified.
Interoperability Support
VMware Smart Assurance 10.1.12, 10.1.9, and 10.1.7 is interoperable with VMware Telco Cloud Service Assurance 2.2.0.
In VSA 10.1.12 release, some of the document(s) do not require modification. The older version document(s) are released as it is.
The VeloCloud, vIMS, and, vEPC discovery and monitoring functionality is only available with VMware Telco Cloud Service Assurance deployment. It is not available for standalone VMware Smart Assurance/Data Collector Framework.
VMware vRealize Operations is rebranded as VMware Aria Operations for Integrations. In VMware Smart Assurance, the rebranding of application and documentation takes effect in future release.
Following third-party software components are upgraded in VMware Smart Assurance 10.1.12:
OpenJDK is upgraded to 11.0.18.
OpenJDK for SAM console (Windows / Linux) is upgraded to 1.8.0_362.
Zlib is upgraded to 1.2.13.
Apache Tomcat is upgraded to 9.0.72.
Spring Security Core upgrade to 6.0.1.
Snakeyaml is upgraded to 2.0.
Groovy has been upgraded to 3.0.7.
Grails is upgraded to 5.2.2.
Spring-boot is upgraded to 2.7.4.
Spring-boot-starter is upgraded to 2.7.0.
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.12 release, support for RHEL 9.1 operating system is added.
SAM Console is now supported on Linux 9.1 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-2001 / 22361668109
DataStore to Elasticsearch migration sizing requirement in M&R.
SMARTA-2081 / 22376027310
Service offering not getting cleared along with problem alarm. Instead of which service offering alarms are getting source notified.
SMARTA-1973 / 22356309208
Smarts AMQP (RabbitMQ) cleartext password vulnerability in setup script.
SMARTA-1566 / 21277447611
With the following commands, the user was unable to discover the device from seedfile and the error message appears:
/opt/InCharge/IP/smarts/bin/sm_tpmgr -s BWIIT-AM-PM-DMZ2-SRB --seed=/opt/InCharge/IP/smarts/local/conf/seed-dmz-srb.txt
sm_tpmgr: import topology from seed file /opt/InCharge/IP/smarts/local/conf/seed-dmz-srb.txtSMARTA-1826 / 22330548905
Timeout value for the Smarts Console to timeout does not work.
SMARTA-2011 / 22357123108
ASL error during reconfigure, in IPAM 10.1.2.0.
SMARTA-2013 / 22363650709
While creating OSPF domain, the error message appears repeatedly in the logfile.
SMARTA-2203 / 22392484612
Sub-Interfaces lose instrumentation during post-processing phase of pending discovery and do not come back.
SMARTA-1930 / 22345852107
License Manager is not getting instrumented for Cisco Catalyst 36xx stack-able ethernet switch .1.3.6.1.4.1.9.1.2066.
SMARTA-2054 / 22369140610
User specific Threshold group settings for Memory are not working.
SMARTA-2086 / 22375782410
VMware Smart Assurance release notes documentation update request.
SMARTA-2246 / 23415846003
Issue with NOTIF configuration in SAM 10.1.5 deployment.
SMARTA-2082 / 22343177207
There are mismatches in the vROPS Alarms processed in OI and SAM.
SMARTA-2014 / 22338674906
Duplicate events created for vROPS group objects in SMARTS SAM.
SMARTA-785 / SR-20117290404
Smarts elasticsearch does not start as a service at times.
SMARTA-2172 / SR-22392706512
Cisco ACI device access SNMPAddress keep appending value.
SMARTA-2075/ SR-22374063510
Frontend with the reporting period of one week, when exported to PDF or Excel shows the reporting period of 1 day.
SMARTA-2232/ SR-23409813402
Notification Properties is not working for the alarms having % in its name.
SMARTA-2061/ SR-22370597210
Topology View is Not Opening from Notification Log Console.
SMARTA-2022/ SR-22365149409
Vcenter collector logs having severe error "Entity using counter 411 can't be found in the counters cache".
SMARTA-1804/ SR-22328626205
Security framework of XStream not initialized, XStream is probably vulnerable.
SMARTA-1833/ SR-22333737305
Catalina logs have Severe entries for Login failure even if the User/Password is correct.
SMARTA-2008/ SR-22363204409
SHA256 and AES256 need to supported for SNMP discovery.
SMARTA-1853/ SR-22336789906
In Notifications parent report, all the child reports are not being displayed.
SMARTA-2033 / SR-22361946709
APG portal doesn't show report tree when database is locked for writes.
M&R NCM SP data collection fails when NCM is installed on RHEL 8.6 server with FIPS enabled.
M&R NCM SP with FIPS enabled NCM is not supported yet.
Workaround:
M&R NCM SP can be used with NCM non-FIPS mode.
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 may fail to start.
Workaround:
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:
If Kafka server goes down, a notification for VCD monitoring failure appears in SAM once ESM Server is reconfigured.
When Kafka is brought back, the failure notification is cleared from SAM once ESM server is reconfigured.
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.
Objects deleted in IP are not getting deleted in VMware vRealize Operations even after object deletion time interval.
To delete the objects manually:
Go to Administration > Configuration > Inventory Explorer.
Select the objects to be deleted and click delete button (Bulk deletion is also supported).
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:
ESM - 10.0.0.1 (ESM 10.0 patch 1)
IP - 10.0.0.2 (IP 10.0 Patch 2)
When performing migration only on the above two versions, you need to follow the below procedure:
Collect the backup from the old installation using sm_migrate utility.
Run 'sm_perl sm_migrate.pl --old=<dir> --archive=<tar/zip> --sitemod=<local_directories>' from the old installation.
Perform manual migration on the customized files.
Copy the archive file from ‘step1’ to new host.
Run 'sm_perl sm_migrate.pl --archive=<tar/zip> --new=<dir>' from the new installation.
Once the sm_migrate utility backs up all the customizations under smarts directory (Eg: /opt/InCharge/IP/smarts/.migrate.bkp.10.0.0.2) and prompts for merging the customizations with below options, the user has to select “N” to not merge.
Press 'n' to skip FileMergeUtilty.
Press any other key to start FileMergeUtilty...[y]n
You need to manually copy customizations from backup directory (Eg: /opt/InCharge/IP/smarts/.migrate.bkp.10.0.0.2) to respective local directory and rename the files to remove ‘.local’ extension.
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).
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.
