Product Description

VMware Smart Assurance Network Configuration Manager (NCM) is:

  • An automated compliance, change and configuration management solution that delivers industry-recognized best practices.

  • A collaborative network infrastructure design that controls change processes, provides network device and service configuration transparency, and ensures compliance with corporate and regulatory requirements — to enable you to ensure the security, availability, and operational efficiency of your network.

  • An automated support for all facets of the network infrastructure lifecycle, seamlessly integrating critical design, change, and compliance management requirements.

What's New

With VMware Smart Assurance Network Configuration Manager 10.1.11 release, the following changes are introduced.

  • Third-party software components upgraded to mitigate the vulnerabilities.

  • Added support for Ericssion Minilink device.

  • Addressed security threat in SysAdmin console web page.

  • Modified NCM API URL to address security vulnerability.

  • Added support for RHEL 8.6 platform.

Third-party software component upgrades

Following third-party software components are upgraded in Smart Assurance Network Configuration Manager 10.1.11:

  • Spring-framework is upgraded to 5.3.22

  • Spring-security is upgraded to 5.7.5

  • Spring-webmvc is upgraded to 5.3.20

  • Tomcat is upgraded to 9.0.68

  • Grails is upgraded to 5.2.2

  • OpenJDK-11 is upgraded to 11.0.17

  • OpenJDK-8 is upgraded to 1.8.0_352

  • Zlib is upgraded to 1.2.13

  • Expat is upgraded to 2.5.0

NOTE : Third-party software component upgrade is not applicable for the jars coming from 9.6 Report Advisor and InstallAnywhere.

For Open Source License(OSL) file open_source_licenses.txt, navigate to <VOYENCE_HOME>/osl directory.

Platform Support

The VMware Smart Assurance Network Configure Manager 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 NCM 10.1.11 release, some of the document(s) do not require modification. The older version document(s) are released as it is.

Resolved Issues

  • SMARTA-2010 / SR 22357848308: The exportCredential command creates file starting with '-' for the name.

  • SMARTA-1974 / SR 22344150707: Automation library search feature throws error in NCM GUI.

  • SMARTA-1955 / SR 22351813408: The J2EE Automation library API getAutomationLibraryItemsByKeywords fails to execute.

  • SMARTA-1997 / SR 22361416109: Change the communication port 8881, between Client and ncm-as service to a secure port.

  • SMARTA-1822 / SR 22329996605 : Automation library is not showing operator used in filter upon reopening but clear cache shows it.

  • SMARTA-1977 / SR 22357085008 : Illegal address in string error in Catalina.out.

  • SMARTA-1980 / SR 22356819308 : NCM GUI hangs on TACACS authentication.

  • SMARTA-1967 / SR 22355427908 : Approving system job is not working for test user.

  • SMARTA-1788 / SR 22327451405 : Upgrade NCM From 10.1.1 to 10.1.6 using silent mode fails due to NCM password requirement behaviour.

    Refer, VMware Smart Assurance Network Configuration Management Installation Guide under the section Change NCM passwords.

  • SMARTA-1775 / SR 22326328805: Customer is not able to perform upgrade due to driver issue.

  • SMARTA-1916 / SR 22346098407: NCM SSL certificate instructions need to be updated.

  • SMARTA-1959 / SR 22355870808: Unable to start the application, after successful upgrade from 10.1.4 to 10.1.8.

    Refer, VMware Smart Assurance Network Configuration Management Installation Guide for disk space requirement for upgrade.

  • SMARTA-1947 / SR 22352092208: A security threat detected from WebInspect scan in NCM SysAdmin Console webpage.

Known Issues

  • JMS exception 'Caused by: org.apache.activemq.transport.TransportDisposedIOException: peer (vm://localhost#1) stopped.' occurred in powerup log and server log when the system is rebooted.

    There is no functional impact and the error can be ignored.

  • After rebooting the VM, some vcmaster services are not running.

    This behaviour is inconsistent. Run the command systemctl restart vcmaster after system reboot.

check-circle-line exclamation-circle-line close-line
Scroll to top icon