The release notes cover the following topics:
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.
For Security vulnerabilities addressed in NCM, see Network Configuration Manager Security Update for Multiple Vulnerabilities, and security enhancements section in NCM Security Configuration Guide.
Third-party software upgrades are:
- Java is upgraded to OpenJDK 11.0.8.
- Tomcat is upgraded to 9.0.38.
- Dom4j is upgraded to 2.1.3.
- ActiveMQ is upgraded to 5.16.0.
- Gsoap is upgraded to 2.8.104.
- Boost Library is upgraded to 1.70.
For Open Source License(OSL) file open_source_licenses.txt, navigate to <VOYENCE_HOME>/osl directory.
Note: Due to jaxen-1.1.1 internal dependency on dom4j 1.6.1, dom4j-1.6.1 is also present.
In NCM 10.1.3 release, support for RHEL 8 OS is added.
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.3 release, some of the document(s) do not require modification. The older version document(s) are released as it is.
Not able to launch SysAdmin console webpage, post upgrade to 10.1.1.0.
- SMARTA-975 / SR 20157298009:
Cross-Frame scripting issue is reported for setupmgr in Device Server.
- SMARTA-959 / SR 20154490609:
TelnetProxy is not working in NCM 10.1.1.
- SMARTA-1067 / SR 20172465811:
After disabling tests in Automation Library "Resource Not Found" error is thrown.
- SMARTA-1074 / SR 20175658111
Controldaemon is unable to process updates from the device server.
- SMARTA-974/SR 20157228709
Report Advisor web page reported Cross-Frame scripting issue when launched using port 8443.
Follow the below steps to resolve this issue in Remote Report Advisor.
1. After NCM 10.1.3.0 installation in Application Server, copy the script
$VOYENCE_HOME/tools/update_remote_ra.plfrom Application Server to remote Report Advisor (Ex:-9.6.0.X).
2. Run the perl script
- SMARTA-986/SR 20158756309:
Cross-Site Scripting is reported in SysAdmin for the ServerPath field
- SMARTA-906/SR 20136382506
NCM api.device.PartitionInfo and MaskableContentInfo issues occurred when updateOsImage API invoked from C# environment.
- SMARTA-1022/ SR 20166161410
Customer usable driver ID range needs to be updated in DDT help and DDT document
NCM 10.1.0 application launch is breaking on Google Chrome.
Chrome has deprecated the NPAPI support which causes Java plugins to be disabled.
If you have problems accessing Java applications using Chrome, Oracle recommends using Firefox, Internet Explorer, or Safari instead.
Users that need to run Web Start application may launch that application through a web browser such as Internet Explorer, Mozilla Firefox, Apple Safari, or Pale Moon.
The link, https://<ipaddress>:8880/voyence/powerup.jnlp, provides a .jnlp file download you can use to enable the launch of the NCM application.
User is not able to launch NCM MSA on the Firefox version 58 or later.
Use the older version of Firefox (version older than 58), or use Internet Explorer to launch the NCM MSA.
NCM MSA login screen should have a standard login screen with VMware logo.
MSA login page display Grails as the logo, instead of VMWare Network Configuration manager.
Device Server health check log has some warnings.
When UI is launched with the new UI Linux client, Schedule Manager sorting is not happening properly and device properties are not seen.
Workaround: User can use filters to check the details of required job.
Syslog messages are not captured in RHEL 8 Server
Workaround : Follow below steps to receive Syslog messages in RHEL 8 Server:
- Open /etc/rsyslog.conf file
- Uncomment below lines for UDP:
#module(load="imudp") # needs to be done just once
- Uncomment below lines for TCP:
#module(load="imtcp") # needs to be done just once
- Restart rsyslog service using "systemctl restart rsyslog" command