Smarts Domain Managers 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 Smarts 2.4.0 release, the following features, enhancements, and changes are introduced:
Support for VMware vSphere 8.0u2 in ESM
vSphere 8.0u2, discovery and monitoring are qualified on ESM.
Support for VMware NSX-T 4.1.1,4.1.2 in ESM
Discovery and Monitoring of VMware NSX-T 4.1.1, 4.1.2 have been qualified.
Support for VMware vRealize Operations 8.14.
Discovery and Monitoring of VMware vRealize Operations 8.14 has been qualified.
Upgrade
In place upgrades from 10.1.5, 10.1.7, 10.1.9 and 10.1.12 to 2.4.0 is supported for Smarts.
Migration from 10.1.5, 10.1.7, 10.1.9 and 10.1.12 to 2.4.0 is supported for Smarts.
In Smarts 2.4.0 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 Smarts Domain Managers/Data Collector Framework.
VMware vRealize Operations is rebranded as VMware Aria Operations for Integrations. In Smarts, the rebranding of application takes effect in future release.
Following third-party software components are upgraded in Smarts Domain Managers 2.4.0:
Spring-security-core is upgraded to 6.2.3.
Zlib is upgraded to 1.3.1
Tomcat is upgraded to 9.0.87
Tomcrypt is upgraded to 0.078
Axis is upgraded to 1.4.2
OpenJDK is upgraded to 21.0.3
OpenJDK for SAM console (Windows / Linux) is upgraded to 1.8.0_412.
Xerces is upgraded to 3.2.3
For OSL (Open Source License) file (open_source_license_VMware_Smart_Assurance_GA.txt), navigate to <BASEDIR>/smarts/setup/osl.
In Smarts Domain Managers 2.4.0 release, support for RHEL 9.3 operating system is added.
The 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-1971 / 23454410508
Smarts Global console crashes on startup.
SMARTA-2660 / 24499893302
Post upgrade a new trap_mgr.conf.conflict was created, which has lesser number of trap definitions than the original.
TCO-12177
The timestamps in the SAM audit log file have changed in Smarts 10.1.12.
SMARTA-2358 / 23435821606
In IP version 10.1.2.5, the AM-PM domain crashed with a core file generated.
SMARTA-2382 / 23434279405
After upgrading SAM to 10.1.9.0, Trap Exploder issue appears.
SMARTA-2337 / 23428226405
Trying to configure vROPS adapter to connect to Aria SaaS instance, but alerts are not receiving in OI domain after configuration.
SMARTA-2289 / 23416739303
NARGs lose ComposedOf enrichment data post topo-sync, as interfaces get deleted and re-created.
SMARTA-2336 / 23410567602
Scheduled maintenance notification are not getting cleared after maintenance period is over.
SMARTA-2626 / 23485214712
CallManager Instrumentation failing in Smarts 10.1.7 deployment. VoIP CallManager Down alerts do not clear from SAM console when they are reachable.
SMARTA-2535 / 23470568710
In Smarts ErrorTrafficThreshold is not modified from Polling and Threshold window.
SMARTA-2468 / 23457933208
Smarts ISIS discovery for Nokia - Alcatel devices.
SMARTA-2319 / 23429798105
Smarts 10.1.9 F5 Networks BIG-IP-5250 LoadBalancer Host probe error.
SMARTA-2516 / 23466912109
vROPS to Smarts adapter exception encountered when processing Aria cloud SaaS alerts in Smarts OI domain.
SMARTA-2494 / 23462127109
Monitoring is not as expected in VoIP manager for the CISCO Call manager.
SMARTA-2326 / 23425957904
Smarts BGP alarms Co-relation issue.
SMARTA-2469 / 23446286907
Wrong LLDP connection being created whenever a pending device discovery is initiated and completed.
SMARTA-2440 / 23451961507
Version 10.1.9 is using an old/unsupported version of mfc42.dll (VC++4.2).
SMARTA-2793 / 35225096
Unable to see any power supply alarms on sdna3-edge01.ftn, which is a Nokia 7750-SR Router.
User is unable to use Java 1.8 351 and above to launch Web Console.
The latest Java updates 8.0.351 and above deprecate the use of SHA1 signed jars and treat them as unsigned jars.
Since, the web console utilizes the system's Java, and we have limited control over it, we recommend to use the lower version of Java at client side or apply the workaround mentioned in the KB article. This workaround does not impact the product.
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.
