The release notes cover the following topics:

What's New in this Release

With Smart Assurance 10.1.7 release, the following features, enhancements, and changes are introduced:

  • M&R 7.3.0.5 [build 48]. Following SolutionPacks are qualified with M&R 7.3.0.5 release:
    • Health​
    • Cisco IPSLA
    • Cisco Unified Communication Manager
    • VMware vCenter
    • Traffic Flows
    • VMware Smarts

                  Note: (a) User profile logo feature that can be set at profile creation level has been removed from M&R v6.8 onwards.

                            (b) M&R MIB-Browser module has been deprecated in 7.x and removed in 7.2.0.1.

  • Support for VMware vSphere 7.0.3 in ESM and M&R vCenter SP:

    • ​Discovery and Monitoring of vSphere 7.0.3 is qualified on ESM. Also vSphere 7.0.3 reporting through VMware vCenter SolutionPack has been qualified on M&R 7.3.0.5.

  • Support for VMware NSX-V 6.4.11 in ESM

    • ​Discovery and Monitoring of VMware NSX-V 6.4.11 has been qualified.​

  • Support for VMware NSX-T 3.1.3 in ESM
    • ​Discovery and Monitoring of VMware NSX-T 3.1.3 has been qualified.​

  • Miscellaneous enhancements:​

    • [VM-ER-248]: To support for device type "Smart PDU".
    • [VM-ER-238]: To support for JUNIPER MIB trap processing in Smarts NPM to generate the BGP session Flapping/down alert. 
    • [VM-ER-249]: To support for VMware NSX-V 6.4.11 in ESM.
    • [VM-ER-245]: To support ProcessorUtilizationThreshold > 100% in VSA smarts IP/ESM domain manager.
    • [VM-ER-237]: To support to suppress Duplicate IP event during HSRP IP discovery.
    • [VM-ER-181]: To support SNMPv3 SHA-256 for discovery in IP.
    • [VM-ER-250]: To support for monitoring Cisco licenses feature via ciscoSmartLicMIB.

Note: Check the interoperability of VMware Smart Assurance 10.1.7 release before deploying. You can check interoperability on the Interop Tool.

For security vulnerabilities addressed in Smarts, see Smart Security Update for Multiple Vulnerabilities.

Third-party support

  • Commons-fileupload has been upgraded to 1.4.
  • Log4j has been upgraded to 2.17.0.
  • Mujs has been upgraded to 1.1.3.
  • Netty has been upgraded to 4.1.68.
  • Quartz has been upgraded to 2.3.2.
  • Snappy-java has been upgraded to Uclibc compatible version 2.33.
  • Slf4j has been upgraded to 1.7.32.
  • Snappy-java has been upgraded to Glibc compatible version 2.33.
  • Zlib has been upgraded to 1.2.11.
  • Java has been upgraded to 11.0.12.
  • Java is upgraded to 1.8.0.302 32 bit for SAM console (Windows / Linux).
  • Icu4J has been upgraded to 52.2.
  • Tomcat-catalina has been upgraded to 9.0.45.

For OSL (Open Source License) file (open_source_license_VMware_Smart_Assurance_GA.txt), navigate to <BASEDIR>/smarts/setup/osl.

Platform Support

In VSA 10.1.7 release, support for RHEL 8.4 operating system is added.

Note: SAM Console is not 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.

Note: 

  • In VSA 10.1.7 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 Operations deployment. It is not available for standalone VSA/DCF.

Resolved Issues

  • SMARTA-1309 / SR-21219804905

    Issue in monitoring of multiple Cisco ACI clusters.

    Resolution: Handled the use case of changes in controller node that responds to monitoring requests in scenarios where multiple Cisco ACI instances are discovered and monitored.

  • SMARTA-1283 / SR-21219804905

    Cisco ACI monitoring stops at a point in environment, where multiple ACI clusters are discovered and monitored.

    Resolution: Handled the use case of change in the controller node's IP, that responds to monitoring requests in scenarios where multiple Cisco ACI instances are discovered and monitored.

  • SMARTA-1336 / SR-21218148805

    Cisco APIC hosts are not discovered with seed name using the seedfile discovery.

    Resolution: The host name (if already discovered) is being set as seed name for APIC instances during ACI discovery through seedfile. And, then rediscovery/seedfile discovery will use the host name rather than discovering APIC hosts with IP addresses.

  • SMARTA-1401 / SR-21241263407

    In VMware vCenter monitoring, VMwareDatastore’s NoAccess event is not getting cleared, when the datastore changes state in vCenter from inaccessible to accessible. The alarm stays active for a longer period even though no such alarm presents in vCenter.

    Resolution: The code has been enhanced to obtain the status of the discovered VMwareDatastore instances, and set them to clear in the monitoring cycle when the status changes.

  • VSAC-1092

    Cisco ACI APIC host is being discovered with IP address even though the seed name passed is the hostname and also the name format is set as TM_USESEEDNAME.

    Resolution: The issue has been fixed by checking the name format for the REST discovery and accordingly assigning the hostname as system name in the discovery init flow.

  • SMARTA-1400 / SR-21245870608

    Security vulnerabilities in MySQL 5.7.21 used in M&R 6.8u5 and 7.0u8 versions.

    Resolution: The MySQL in M&R has been upgraded to 5.7.35.

  • SMARTA-1217 / SR-21203394803

    Security vulnerabilities in jQuery used in M&R 6.8u5, 7.0u8, and 7.2.0.1 versions.

    Resolution: The jQuery library in M&R has been upgraded to 3.6.0.

  • SMARTA-1290 / SR-21220527005

    AudibleAlerts on Smarts Notifications report in M&R is not producing any sound on new notifications.

    Resolution: This has been fixed by adapting to HTML5 audio element.

  • SMARTA-1135 / SR-20184041012

    Sorting on LastNotify and LastClear columns are not working as desired in Smarts Notifications in M&R.

    Resolution: This was a minor code issue and has been fixed.

  • SMARTA-1421 / SR-21249551908

    Unable to upgrade M&R from v7.0u8 to v7.2.0.1 through UI (Centralized-Management) in distributed setup.

    Resolution: The update management package in M&R 7.3.0.5 has been enhanced to upgrade the M&R.

  • VSAC-1178

    VMware vCenter related topology instances are deleted and re-created in ESM domain manager while performing DiscoverAll.

    Resolution: This has been fixed by addressing the code flaw that deletes some of the discovered instances during the initial discovery flow in case of topology rediscovery.

  • SMARTA-1579 / SR-21286146012

    Log4j 2.x critical vulnerability CVE-2021-44228 in M&R components

    Resolution: Log4j 2.x versions used in different M&R components have been upgraded to log4j 2.17.0, that fixes the critical vulnerability CVE-2021-44228.

  • SMARTA-1469 / SR- 21235556807

    Smarts TSM 10.1.2 deletes Juniper virtual switches and IP discovery takes longer to put them back in

    Resolution: TSM topo-sync code logic has been handled to ignore the VSS (VirtualSwitchSystem) class while deleting the devices from the underlying domain manager that are not managed by the TSM domain.

  • SMARTA-1417 / SR: 21244495208

    SNMP V3 devices discovery is failing during the pending discovery.

    Resolution: While adding SNMP V3 devices to the pending list, the context parameter has been corrected to add the right context details for the pending list discovery to be successful.  

  • SMARTA-1511 / SR: 21265372110

    Smarts can not discover memory components of windows hosts on APM

    Resolution: Updated the certification discovery logic to discover and monitor the host-resource components of windows host.

  • SMARTA-1470 / SR : 21257821409

    Smarts 10.1.2.5 Customer issue with false cable connections between devices in in different Geographical Locations.

    Resolution: LLDP post processing has been enhanced to handle to honour the remote chassis sub-type for a strict checking on the remote device identification and also added support to exclude the VSS MAC ranges.

  • SMARTA-1455 / SR : 21246067108

    Smarts: 10.1.0. OI domain disconnect CLEAR notification on presentation SAM Continuation of SMARTA-1420.

    Resolution: The root cause was the short disconnect between the different layers of SAM. The code has been modified to handle short disconnect which was affecting HyperNotif driver.

  • SMARTA-1553 / SR : 21276158811

    HostAccessPoint and HostedBy relationship lost on the OI domain - Smarts v10.1.0.1

    Resolution:  Fast dxa code logic has been modified to avoid deletion of Host to IP relationship that is getting imported to the OI domain. 

  • SMARTA-1335 / SR : 21233703406

    Smarts is not able to perform sm_snmpwalk v3, on APC ATS AP4421 device.

    Resolution : The code has been modified to set the “msgAuthenticationParameters” to NULL to handle the APC device for a successful SNMP V3 discovery.

  • SMARTA-1430 / SR : 21250431508

    Smart Failover Manager has issues with SAM and OI domains with migrated rps from and ICS_FeatureVersion_SAM or ICS_FeatureVersion_OI entries

    Resolution: ICS_FeatureVersion_SAM has been updated appropriately and necessary checks has been introduced during migration operation.

  • SMARTA-1393 / SR: 21241632507

    PIM not enabled interface are not getting deleted from MCAST.

    Resolution: Code has been modified to take care of deletion of PIM interfaces while disabling all the PIM interfaces from the device. 

  • SMARTA-1536 / SR: 21265194610

    In OI notification after processing from vROPS alert management, the element and class name appears incorrect .

    Resolution: OccurredOnInstance was derived from getParentInstanceName instead of getInstanceName which was duplicating the alert with different instance name. Code is fixed to consider getInstanceName.

  • VSAC-1633

    Withdraw support for the fifteen SolutionPacks in M&R 7.3.0.5.

    In M&R 7.3.0.5, following SolutionPacks are no longer supported and have been removed from the installer packages. However, in case of upgrade, below SolutionPacks from the previous M&R version would be present, but they are not supported.

    • Blue Coat PacketShaper

    • Cisco ENFV

    • Ericsson IMS CSCF

    • Ericsson IMS HSS SLF

    • Ericsson IMS IPWorks

    • Ericsson IMS MRFP

    • Ericsson IMS MTAS

    • Ericsson IMS SOI

    • Ericsson IMS TSP

    • Ericsson eNodeB

    • Ericsson MGW

    • Ericsson RNC

    • Ericsson SGSN

    • Huawei iManager M2000

    • ip.access nano3G Small Cells

Known Issues

The known issues are grouped as follows.

Known Issues in SAM
  • VSAC-209

    Default DCF password is not working for DCF SAM-OI communication. Notification will not be pulled from vROps to SAM-OI.

    Workaround: 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.

  • SMAR-1444

    All Services are not installed post upgrade for SAM and SAM-Console.

    Workaround:

    Refer Services for the Service Assurance Manager section in VMware Smart Assurance Installation Guide to install services manually.

  • VSAC-1065 

    SAM 10.1.5 installation succeeds even though mandatory rpm package libnsl.x86_64 required for it is not installed in some of the RHEL 8.x machine. 

    Post installation server starts, but not able to attach to SAM GUI, and SAM server log shows following error:

    [August 11, 2021 6:02:45 PM GMT+00:00 +568ms] t@1682732800 InCharge Framework
ASL-W-ERROR_RULE_SOURCE-While executing rule set '/largedisk/InCharge/SAM/smarts/rules/import.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: CALL_PARAMS, Line: 59
ASL-CALL_STACK_RULE- RuleName: CALL_OPERATION, Line: 34
ASL-ERROR_INVOKE-While attempting to invoke operation 'loadModel' of object 'MR_Object::SM-System'
CI-ELIBNOTLOAD-Library "sm_ics_xml_conf" could not be loaded
CI-ESYSINFO-System information:
. libnsl.so.1: cannot open shared object file: No such file or directory
RTLD-SI_ELOADERR-Dynamic loader error

[August 11, 2021 6:02:45 PM GMT+00:00 +569ms] t@1682732800 InCharge Framework
ASL-W-ERROR_RULE_SOURCE-While executing rule set '/largedisk/InCharge/SAM/smarts/rules/import.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: CALL_PARAMS, Line: 59
ASL-CALL_STACK_RULE- RuleName: CALL_OPERATION, Line: 34
ASL-ERROR_INVOKE-While attempting to invoke operation 'loadModel' peof object 'MR_Object::SM-System'
CI-ELIBNOTLOAD-Library "sm_map_xmlconfig" could not be loaded
CI-ESYSINFO-System information:
. libnsl.so.1: cannot open shared object file: No such file or directory
RTLD-SI_ELOADERR-Dynamic loader error

    Resolution: To resolve the issue, install the following missing rpm package:

    yum install libnsl.x86_64 

  • SMAR-1727

    Incase of Console mode installation and upgrade, below irrelevant message is displayed in command prompt which does not have any functional impact:

    cwd: C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\Windows

cmd: "C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\Windows\resource\jre\bin\java.exe" --add-opens java.base/jdk.internal.loader=ALL-UNNAMED -Xms16777216 -Xmx50331648 -classpath "C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\InstallerData\IAClasses.zip;C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\InstallerData\Execute.zip;C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\Windows\InstallerData\Execute.zip;C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\InstallerData\Resource1.zip;C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\Windows\InstallerData\Resource1.zip;C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\InstallerData;C:\Users\Administrator\AppData\Local\Temp\2\I1559131575\Windows\InstallerData;" com.zerog.lax.LAX "C:/Users/Administrator/AppData/Local/Temp/2/I1559131575/Windows/setup-CONSOLE-10_0_0_0-win.lax" "C:/Users/Administrator/AppData/Local/Temp/2/lax827D.tmp" -i console
  • VSAC-32

    The following map error warning message appears for INCHARGE-SA and INCHARGE-OI in respective logs, while starting the server.

    WARNING: register package 'map_error' version 468026d2 failed (0x276f4e00)
[May 11, 2020 2:50:50 AM EDT +804ms] t@375936768 InCharge Framework
FDXAM-*-DXA_TOPOCONC-TopologySync is running in CONCURENT mode with minimum delay=120 seconds.

WARNING: register package 'Map_mm' version a1894c1c failed (0x276f4e00)
[May 11, 2020 2:50:52 AM EDT +072ms] t@375936768 InCharge Framework

    There is no functional impact due to this issue.

  • VSAC-200

    The following ASL error message appears for INCHARGE-SA and INCHARGE-SA-PRES server, while starting the servers.

    [May 11, 2020 2:50:50 AM EDT +710ms] t@881858304 InCharge Framework
ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/INCHARGE10120/SAM/smarts/rules/import.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: INSERT, Line: 181
ASL-CALL_STACK_RULE- RuleName: OBJECT_PROPERTY, Line: 177
ASL-CALL_STACK_RULE- RuleName: OBJECT_PROPERTIES, Line: 171
ASL-CALL_STACK_RULE- RuleName: OBJECT_VALUE, Line: 138
ASL-ERROR_INSERT-While attempting to insert into property 'MapViews' of object 'Map_Containment::Map-Containment'
MR-CALL_OBJ_PROP-Object: Map-Containment property: Map-Containment; in file "/work/redcurrent/DMT-10.1.2.0/3/smarts/repos/mr/obj.c" at line 2102
MR-KEY_DUPLICATION-violation of uniqueness requirement for a key
[May 11, 2020 2:50:52 AM EDT +095ms] t@881858304 InCharge Framework

    There is no functional impact due to this issue.

  • VSAC-250

    The Rabbit MQ service is not started in SAM, due to the following error:

    [root@vmwbgc052 bin]# ./sm_rabbitmq --ignoreme
ERROR: epmd error for host vmwbgc052: address (cannot connect to host/port)
[root@vmwbgc052 bin]#

    Workaround: 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>
  • VSAC-253

    In some hosts, the pre-installed services such as smarts-tomcat and smarts-elasticsearch 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

    Note: If the ic-business-dashboard service in SAM Console does not start, then restart the ic-serviced daemon process by running the earlier commands.

  • VSAC-223

    After SAM 10.1.2.0 upgrade, epmd service-related errors appear in the SAM upgrade log:

    /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)

     

  • VSAC-261

    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.

    Workaround: Connect to the broker where there is less number of domain managers registered.

  • VSAC-1309

    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. 

Known Issues in ESM
  • SMAR-1509

    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 will be shown.

  • SMAR-1668

    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.

  • SA1-576

    When Kafka is not reachable, monitoring failure event appears in SAM after reconfiguration of ESM Server.

    Workaround:

    1. If Kafka server goes down, a notification for VCD monitoring failure appears in SAM once ESM Server is reconfigured.
    2. When Kafka is brought back, the failure notification is cleared from SAM once ESM server is reconfigured.
  • SMAR-1848

    Exception appears when selecting "Tiered application map" by right clicking on any map icon.

  • VSAC-126

    Mapping of ElementName attribute to the device for notification on AggregatePort is missing. ElementName appears as Aggregate Port instance name instead of Device name.

    Workaround: Detach the INCHARGE-AM-PM from SA and underly it again. Once you re-attach INCHARGE-SA-PRES to the domain manager, you may lose all the active notifications. 

  • VSAC-1468

    Few vSwitch and VMKernelPort are not getting deleted when deleting the NSXT-3.0 in ESM Domain Manager.

    Workaround: The stale entries need to be removed manually.

Known Issues in IP
  • SMAR-1555

    Objects deleted in IP are not getting deleted in vROps even after object deletion time interval.

    Workaround:

    To delete the objects manually:

    1. Go to Administration > Configuration > Inventory Explorer. 
    2. Select the objects to be deleted and click delete button (Bulk deletion is also supported). 
  • SMAR-1544

    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. 

    Workaround:

    User can manually delete the reports from the dashboard.

  • SMAR-1543

    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.

    Workaround:

    Edit the credentials  again and update the password filed again and save it.

  • SA1-958

    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.

    Workaround:

    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:

    Step 1: 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.

    Step 2: 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.

                                          a. Press 'n' to skip FileMergeUtilty.

                                          b. Press any other key to start FileMergeUtilty...[y]n

    Step 3: 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.

  • VSAC-1548

    Shutting down IP server with Cisco ACI discovered does not stop ACI Monitoring collector in DCF.

    Workaround: DCF cisco-aci monitoring collector needs to be stopped manually post stopping IP domain.

  • VSAC-1393

    SNMPV3 traps are not parsed with no context data in the trap definition.

    Workaround: Currently there are no workaround for this as the context data is not getting stored in the V3 trap definition.

Known Issues in MPLS
  • SMAR-1535

    ASL error present in INCHARGE-MPLS-TOPOLOGY after starting server from fresh install.

Known Issues in NPM
  • SMAR-1512

    Post migration, EIGRP server is not coming up.

    Workaround: While starting the EIGRP server use option  --ignore-restore-errors.

  • SMAR-1365

    EIGRP classes are not populated in NPM EIGRP, due to ASL error.

Common Issues to all products
  • SMAR-1377

    During product upgrade, patch folder is not highlighted.

  • VSAC-220

    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.

    Note: Issue also detected on some machines with RHEL 7.2 and 7.6

    Workaround: 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.

  • SMAR-1569

    "-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
    • -uninstall
  • SMAR-1463

    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.

Known Issues in Smart Assurance Management Pack
  • SMAR-1583

    Few Log messages are tagged as ERROR in the collector log incorrectly.

  • SA1-719

    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.

  • VSAC-860

    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.

Known Issues in ASAM
  • VSAC-143

    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.

    Workaround: 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).

Known Issues in ACM
  • VSAC-258

    When ACM is upgraded to 10.1.2, ASL error appears while performing full discovery (DiscoverALL) and after restarting the INCHARGE-AM, INCHARGE-OI, and ACM servers. Following error message appears in ACM log:

    ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/InCharge1012ACM/ACM/smarts/rules/app-sig/standard-probe.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: CREATE_TOPOLOGY, Line: 224
ASL-CALL_STACK_RULE- RuleName: START, Line: 73
ASL-ERROR_INVOKE-While attempting to invoke operation 'makeSoftwareServiceOnHost' of object 'Application_SourceObjectFactory::Application-SourceObjectFactory-AS-IANA-smarts-broker_hostname=10.62.72.138-STANDARD'
APPF-NULL_OBJECT-Null Object 'DXA_TopologySource::Application-SourceObjectFactory-AS-IANA-smarts-broker_hostname=10.62.72.138-STANDARD'
check-circle-line exclamation-circle-line close-line
Scroll to top icon