The release notes cover the following topics:

• What's New in this Release
• Third-party Support
• Platform Support
• Resolved Issues
• Known Issues

What's New in this Release

With Smart Assurance 10.1.0 release,we introduce the following features, enhancements,and changes:

• Introduce support for Cisco ACI SDN:

  • Monitoring Single POD and Multi-POD Cisco ACI SDNs. All the components of Cisco ACI Fabric Switches are monitored, such as Ports, CPU, Cards, etc..

  • Monitor Cisco Leaf, Spine, and traditional SNMP Switch connected to Leaf.

  • Monitor Application Policy Infrastructure controller (APIC),which is the control plane of Cisco ACI SDN.

  • Monitor performance of ports associated to Cisco ACI Fabric switches.

  • Essentially with this release, Smarts Availability and Performance Manager will have the capability to monitor network devices via REST along with traditional SNMP/ICMP mechanisms.

• Introduce support for Cloud Management with VMware vCloud Director:

  • Tenant awareness by discovering vCD managed components, i.e. Organizations, OrganizationVDC, ProviderVDC, vApps, and creating their relationships.

  • Associating vCD managed components to vCenter and NSX virtual components for propagating the impact of virtual resource failures to vCD components.

  • Monitoring of OrganizationVDC and vApps for any resource related issues.

• Enhanced Monitoring for SD-WAN by VMware VeloCloud:

  • Support for MSP and Enterprise Users along with Operator users.

  • For MSP and Operator user type, the Tenant that needs to be managed, can be filtered.

  • A new map is added to the legacy SAM console for VeloCloud Tenant instances. The name of the new map is “SDWAN VCO Connectivity”, other map types are not applicable for VeloCloud Tenant.  The map displays all the VEdge and VGateway for the selected Tenant. The logical relationships between Tenant, VEdge, VGateway and VCO are shown as logical connection.

• Enhancements to VSA Management Pack:

  • In this release, based on VSA and vCenter Management Pack data, vROPs dashboards will now have the capability to represent end to end mapping between the physical, virtual and vIMS VNF service network topology, metrics and health in a single pane.

• [ER-1091]: Data Collector Framework (DCF) & Monitoring and Reporting (M&R) Integration Framework:

  • The integration framework introduced in this release will now allow collected data available in M&R database to show performance reports for Cisco ACI, VeloCloud SD-WAN, vCloud Director and Clearwater vIMS Physical and Virtual infrastructure data.

• Miscellaneous enhancements:

  • [ER-660]:The new time out and maximum number of logon features has been introduced in SAM console. If there is no activity on the console window for the time defined by the user, then the domain session gets disconnected from the console.

  • [ER-1142]: VSA IP Domain Manager is now able to associate the Interface where duplicateIP was configured. A new relationship has been added to the DuplicateIP class name : “DuplicatedOn” which lists the Interfaces where this duplicateIP is configured.

  • [ER-1136]: LAG connection between CISCO-JUNIPER based on LACP: VSA IP Domain Manager would rely on the LACP data to identify the LAG endpoints and then form connection with all the members of the LAG endpoints thus accomplishing end to end physical and logical connectivity representation in VSA IP Domain Manager topology.

  • [ER-1113]: Connection between Cisco Lightweight Access Point (LAP) and Switch is now created based on CISCO-LWAPP-CDP-MIB data in VSA IP Domain Manager.

  • [VM-ER-15]: NPM product is now able to process Cisco specific BGP-4 mibs and set the BGPSession attributes to generate the DOWN and Disconnected events.

  • OTM now supports:
    • Correlating aggregate SD (IsSignalDegrade detected) with downstream LOS, LOF, and SD on non-aggregate (Transponder) ports.
    • Inclusion of Transmission port (Output port) level failures in RCA correlation with respect to UpStream/DownStream failures.

  • [VM-ER-4]: SAM Global console is now supported on MS Edge browser. Refer, VSA support matrix for more information.

  • [VM-ER-6]: VSA prodcuts are now supported on 64 bit version of Java installer.

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

Third-party support 10.1 changes

• Oracle Java SE is upgraded to Java 1.8u212.
• Apache Tomcat is upgraded to 9.0.20.

Platform Support

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.

Resolved Issues

The resolved issues are grouped as follows.

• Resolved Issue in NPM
• Resolved Issues in IP
• Resolved Issues in OTM

Resolved Issue in NPM

• SA1-271

  SSH Login is not working.

  There was a mismatch in Telnet new() function arguments. Hence, Telnet was returning NULL object. Telnet new function has been modified.

Resolved Issues in IP

• SA1-184

  When the filesystem is full, existing RedHat driver incorrectly calculates AvailableSpace and AvailableSpace becomes abnormally large numerical value.

  Code has been modified to handle the issue, when the filesystem is full, AvailableSpace displays correct value.

• SA1-563

  Due to duplicate SNMP_WalkFE::Performance-Avocent-Driver-FE for different Avocent drivers, incorrect discovery and instrumentation issue detected.

  Unique FE drivers has been written for different drivers for Avocent devices. Hence, correct drivers picked for discovery and monitoring.

• SA1-426

  Connection between Cisco Nexus 5K switch to Host is missing.

  Code changes are done to reflect the MAC address of the host to the Switch by enabling EnableEthernetBonding and LinuxBondingInterfacePattern to form the connection.

Resolved Issues in OTM

• SMARTA-148

  OTM 9.6 domain is crashing and core dumping, The crash took place after a topology update of FiberLink where DownstreamLink attribute was populated with other FiberLink(s) for alarm correlation. After that, a dmctl command was causing the topology server to crash.

  There was a loop in the relationship while computing the LOS on FiberLink scenario. The code has been modified to remove the  loop in the relationship on FiberLink.

Known Issues

The known issues are grouped as follows.

• Known Issues in SAM
• Known Issues in ESM
• Known Issues in IP
• Known Issues in MPLS
• Known Issues in NPM
• Known Issues in Smart Assurance UI
• Common Issues to all Products
• Known Issues in Smart Assurance Management Pack

Known Issues in SAM

• SMAR-1567

  Installing SAM console on the Linux platform is not creating applications "VMware Smarts Global Console" icon for quick launch. User needs to go to install directory and type sm_gui command only, the icon option is not available. This appears when previous version 9.5.1. or 9.6 console is already installed.

• SA1-883

  The map icons for VEdge and VGateway are missing for “SDWAN VCO Connectivity” in the 10.0 SAM console.

  Workaround:

  User has to either use 10.1 SAM console or edit map icons for VEdge and VGateway classes.

• 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.

• 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

Known Issues in ESM

• SMAR-1558

  Clearwater SNMP collector does not support SNMP V3, Clearwater supports SNMP v2c and UDP protocol.

• SMAR-1539

  Whenever user performs discoverAll in ESM, it triggers the discovery for all the hosts in the ESM Server and as well all the underlying INCHARGE-AM-PM servers. The host discovery triggers an Orchestrator discovery. Also the INCHARGE-AM-PM discovery triggers another Orchestrator discovery. So if there is a Orchestrator discovery which is InProgress, then if there another request  for the same orchestrator discovery, then this request will be blocked and the device will be moved to the pending list.

  There is no functionality impact as one of the discovery is completed successfully. 

• SMAR-1121

  Badge Reports are having negative value in vIMS performance reports in vROps.

• SMAR-1112

  Manage/Unmanage option is not available for NetworkConnection Class instances.

  Workaround:

  To Unmanage the NetworkConnection, user needs to Unmanage one of the connected interface of that NetworkConnection.

• 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.

• SMAR-1666

  Manage / Unmanage option is not available for network connection class instances, However the Instrumented by relationship is available with NetworkConnection_Fault class.

• SMAR-1470

  While deploying clearwater collector through DCC, user have an option to provide Community string and  port through clientConnect.conf, but it is limited to only one. The user can update the community string in  agents-groups.xml file of DCF collector, however string does not get encrypted. 

• 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.

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.

• SMAR-1441

  Special characters are present after migration from Windows to Linux.

• 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.

• SA1-380

  Null pointer exceptions are observed in IP server log file after Cisco ACI Discovery.

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 from Windows to Linux, 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.

Known Issues in Smart Assurance UI

• SMAR-1118

  Null Value filtering is not possible form log view Filter.

• SMAR-1108

  When we scroll the scroll bar in notification window, the column name must not be hide, it must be fridge. Working fine in Chrome, but in IE, the column name is hiding. 

• SMAR-932

  In case number of notification is 0 or 1 in Smart Assurance UI, the edit field in filter pop up is not visible.

• SMAR-1615

  The Smart Assurance UI fails to display live notifications above 10,000.

• SMAR-1223

  Expanded notification view does not provide distinguish between parent and child(impacted) notifications.

• SMAR-1671

  During Smarts Metric collector installation, if user wants to collect only Metrics or Topology data separately, and selects option 2 or 3 as displayed below:

  [1] AM/PM Topology & Metrics
  [2] AM/PM Metrics
  [3] AM/PM Topology

  The installation fails with errors. 

  Workaround:

  During the collector installation user needs to select the default Option 1 to collect both metric and topology data. Once the installation is complete:

  1. To collect only the Metric data, open   <DCF Install Location>/Collecting/Collector-Manager/<Collector Name>/conf/collecting.xml
  2. Change the value enabled="false" in the following line <collector enabled="true" name="smarts-INCHARGE-AM-PM-Install-0-topo" next="Kafka File" type="Smarts-Collector" config="Smarts-Collector/topology/conf/smarts-INCHARGE-AM-PM-Install-0-topo.xml" /> 
  3. To collect only the Topology data, open <DCF Install Location>/Collecting/Collector-Manager/<Collector Name>/conf/collecting.xml
  4. Change the value enabled="false" in the following line <collector enabled="true" name="smarts-INCHARGE-AM-PM-Install-0-metrics" next="Kafka File" type="Smarts-Collector" config="Smarts-Collector/topology/conf/smarts-INCHARGE-AM-PM-Install-0-metrics.xml" />
  5. Restart the collector process. 

Common Issues to all Products

• SMAR-1377

  During product upgrade, patch folder is not highlighted.

• 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.

• SA1-419

  Exception appears in Collector logs when Orchestrator closes connection during discovery.

   

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.