The release notes cover the following topics:
- About Hotfix
- Before You Begin
- Installing Device Services Support(DSr) Hotfix
- Uninstalling Device Services Support (DSr) Hotfix
- Resolved Issues
- Known Issues
About Hotfix
This hotfix provides information detailing changes or enhancements to Network Configuration Manager Device Services Support (DSr). It also includes information on hardware and software requirements, as well as fixed and known issues.
Note: This hotfix can be installed on NCM versions 10.1.4 or lower. 9.6 is the lowest version supported for this DSr installation.
Related publication
VMware Smart Assurance Network Configuration Manager Device Services Support (DSr) 30.0 Support Matrix.
New device drivers
No new driver added.
Modified driver
The following driver that has been modified in this release:
- Cisco Nexus
- Added support for models C93360YC-FX2.
- Cisco IOS Switch
- Added support for OS version 16.6.4.
- Added support for models WS-C3560CX-12PC-S, WS-C4500X-16SFP.
- Cisco FirePower K9
- Added support for models FPR-4112-K9.
- Cisco PIX Firewall
- Added support for model ASA5545, ASA5555.
- Cisco Drivers
- Added support for AES-256.
- Cisco IOSXR
- Added pull support.
- HP Procurve Switch
- Added support for models J9776A, J9625A, J9627A, J9146A.
Software components
This hotfix contains the following third-party software components:
- SHA256
- Sort table
Before You Begin
The following prerequisites are needed to upgrade to Network Configuration Manager Device Services Support (DSr) hotfix:
Platform-specific requirements:
- You must be running Network Configuration Manager Versions 9.5 or later.
- If you are running any other version lower than Network Configuration Manager 9.5, you must first upgrade to Network Configuration Manager Versions 9.5 or later. For additional hardware and software requirements, refer to the VMware Smart Assurance Network Configuration Manager Installation Guide for Red Hat Enterprise Linux 4 and 5 .
Enhancements and changes
Network Configuration Manager Device Services Support (DSr) Version 30.0 Hotfix 1 release have no enhancements and changes into the product.
Installing Device Services Support(DSr) Hotfix
The installation instructions included in this section are for the Linux, CentOS, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2016 operating environments.
Note: In the examples in both the Install and Uninstall instructions, [Product Directory] is used; however you must substitute [Product Directory] with your actual installation directory path. Windows Server 2008 is only supported on NCM releases prior to 9.5:
- For both Linux, you can determine your product installation directory by examining /etc/voyence.conf, and looking for the text VOYENCE_HOME.
- For Windows, you can determine your product installation directory by accessing the Registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Voyence\Control\Configuration\VOYENCE_HOME.
In Windows environment, if the DSr hotfix installation fails with an error message stating that the Java virtual machine could not be found, you must verify that the PATH system variable under Environment Variables contains the location of the Java installation on your computer. The following sections provide details regarding installing the hotfix in different environments.
Installation instructions for a cluster environment
Use the following steps to install this hotfix for a cluster environment on an application or device server.
Note: If any files in the custom package folder conflict with files in the DSr Hotfix, a warning appears. For cluster environment DSR should be installed on both Application Server and Device Server.
On an application server (Linux)
Follow these steps :
| Step | Action | Command |
|---|---|---|
| 1 | Stop the cluster. | clusvcadm -d [service name] For example: clusvcadm -d app_service |
| 2 | Mount the disk | mount [Partition] [Product Directory] For example: mount /dev/sdc1 /opt/smarts-ncm |
| 3 | Run the DSr Hotfix installer (for Linux or Solaris) | bash NCM_Device_Drivers_xx_HFy_Linux.bin |
| 4 | Stop the services. | /etc/init.d/vcmaster stop |
| 5 | Unmount the disk. | umount [Product Directory] ("lsof -l [Product Directory]" and stop processes if the drive is busy). |
| 6 | Start the cluster. | clusvcadm -e [service name] For example: clusvcadm -e app_service |
On a device server (Linux)
Note: Any jobs in progress on the Device Server will be cancelled.
Follow the step:
| Step | Action | Command |
|---|---|---|
| 1 | Run the DSr Hotfix installer for Linux. | bash NCM_Device_Drivers_xx_HFy_Linux.bin Follow the prompts to install. Where xx is the release number and y is the hotfix number. |
Installation instructions for a non-clustered environment
Use the following steps to install this Hotfix for a non-clustered environment on Linux, Solaris, and Windows.
Note: If any files in the custom package folder conflict with files in the DSr Hotfix, a warning appears.
On an application, device, or combination server (Linux)
Note: Any jobs in progress on the Device Server will be cancelled.
Follow the step:
| Step | Action | Command |
|---|---|---|
| 1 | Run the DSr Hotfix installer. | bash NCM_Device_Drivers_xx_HFy_Linux.bin. Where xx is the release number and y is the hotfix number. |
On an application, device, or combination server (Windows Server 2003/2008 R2/2012/2016)
Note: Any jobs in progress on the Device Server will be cancelled.
Follow these steps:
| Step | Action | Command |
|---|---|---|
| 1 | Run the .exe file. | Double-click the NCM_Device_Drivers_xx_HFy_Windows.exe file. Where xx is the release number and y is the hotfix number. |
| 2 | The installer will load. | Follow the prompts by clicking Next. |
| 3 | The install is complete. | Click Done when the install completes. |
Verifying the installation
To verify the Network Configuration Manager Device Services Support (DSr) Hotfix installation, follow these steps:
| Step | Action | Command |
|---|---|---|
| 1 | Open the Help menu. | Click the Help option on the Network Configuration Manager menu bar. |
| 2 | Open the About window. | Select About. The About VMware Smart Assurance Network Configuration Manager window will open. |
| 3 | Verify the version of the Device Services release. | The version of this release is displayed. |
Uninstalling Device Services Support (DSr) Hotfix
The uninstall process reverts all files modified by the Device Services Support (DSr) Hotfix installation to their pre-installation state.
Only use these uninstall procedures if you are sure you want to uninstall Device Services Support (DSr) Hotfix.
Note: In the examples in both the Install and Uninstall instructions, [Product Directory] is used; however you must substitute [Product Directory] with your actual installation directory path.
- For both Linux you can determine your product installation directory by examining /etc/voyence.conf, and looking for the text VOYENCE_HOME.
- For Windows, you can determine your product installation directory by accessing the Registry key at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Voyence\Control\Configuration\VOYENCE_HOME. The following sections provide details regarding installing the hotfix in different environments:
Uninstall instructions for a cluster environment
Use the following steps to uninstall this Hotfix for a clustered environment on Linux and Windows.
On an application server (Linux only)
Follow these steps to uninstall this Hotfix:
| Step | Action | Command |
|---|---|---|
| 1 | Stop the cluster. | clusvcadm -d [service name] For example: clusvcadm -d app_service |
| 2 | Mount the disk. | mount [Partition] [Product Directory] For example: mount /dev/sdc1 /opt/smarts-ncm |
| 3 | Navigate to the Hotfix directory. | cd [Product Directory]/software/Uninstall_Device_Drivers_HF/ |
| 4 | Run the Hotfix Uninstall script. | bash Uninstall_Network_Configuration_Manager_Device_Drivers |
| 5 | Stop the services. | /etc/init.d/vcmaster stop |
| 6 | Navigate to the root directory. | cd/ |
| 7 | Unmount the disk. | umount [Product Directory] ("lsof -l [Product Directory]" and stop processes if the drive is busy) |
| 8 | Start the cluster. | clusvcadm -e [service name] For example: clusvcadm -e app_service |
On a device server
Follow these steps to uninstall this Hotfix:
| Step | Action | Command |
|---|---|---|
| 1 | Navigate to the Hotfix directory. | cd [Product Directory]/software/Uninstall_Device_Drivers_HF/ |
| 2 | Run the Hotfix Uninstall script. | bash Uninstall_Network_Configuration_Manager_Device_Drivers |
Uninstall instructions for a non-clustered environment
Use the following steps to uninstall this Hotfix for a non-clustered environment on Linux and Windows.
On an application, device, or combination server (Linux)
Follow these steps to uninstall this Hotfix:
| Step | Action | Command |
|---|---|---|
| 1 | Navigate to the Hotfix directory. | cd [Product Directory]/software/Uninstall_Device_Drivers_HF/ |
| 2 | Run the Hotfix Uninstall script. | bash Uninstall_Network_Configuration_Manager_Device_Drivers |
On an application, device, or combination server (Linux) for NCM 9.5.1 onwards
Note: This section is only applicable for the NCM base release 9.5.1 onwards.
To uninstall the Hotfix completely, you must extract the jre-dsr.tar.gz files manually before uninstalling the Hotfix.
Follow these steps to uninstall this Hotfix:
| Step | Action | Command |
|---|---|---|
| 1 | Navigate to the Hotfix directory. | cd [Product Directory]/software/Uninstall_Device_Drivers_HF/ |
| 2 | Unzip the folder. | Unzip jre-dsr.tar.gz folder in the following location: $VOYENCE_HOME/jre-dsr.tar.gz |
| 3 | Run the Hotfix Uninstall script. | bash Uninstall_Network_Configuration_Manager_Device_Drivers |
On an application, device, or combination server (Windows only)
Follow these steps to uninstall this Hotfix:
| Step | Action | Command |
|---|---|---|
| 1 | Open Add or Remove Programs. | Open Add or Remove Programs located under the Control Panel in Windows. |
| 2 | Run the Hotfix Uninstaller. |
|
On an application, device, or combination server (Windows) for NCM 9.5.1 onwards
Note: This section is only applicable for the NCM base release 9.5.1 onwards.
To uninstall the Hotfix completely, you must extract the jre-dsr.zip files manually before uninstalling the Hotfix.
Follow these steps to uninstall this Hotfix:
| Step | Action | Command |
|---|---|---|
| 1 | Navigate to the Hotfix directory. | [Product Directory] |
| 2 | Unzip the folder. | Unzip jre-dsr.zip folder. |
| 3 | Navigate to the Hotfix directory. | [Product Directory]/software/Uninstall_Device_Drivers_HF/ |
| 4 | Run the Hotfix Uninstaller | Double-click Uninstall VMware Smart Assurance Network Configuration Manager Device Drivers.exe to start the uninstall process. This portion of the uninstaller may take several minutes |
Verifying the uninstall
To verify Network Configuration Manager Device Services Support (DSr) Hotfix is uninstalled, follow these steps:
| Step | Action | Command |
|---|---|---|
| 1 | Open the Help menu. | Click the Help option on the Network Configuration Manager menu bar. |
| 2 | Open the About window. | Select About. The About VMware Smart Assurance Network Configuration Manager window will open. |
| 3 | Verify the version of the Device Services release. | The previous version of DSr installed on your machine is displayed. |
Troubleshooting and getting help
VMware support, product, and licensing information can be obtained as follows:
Product information - For documentation, release notes, software updates, or information about VMware products, and service, go to the VMware Online Support website (registration required) at: docs.vmware.com
For technical support, go to VMware Online Support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your VMware sales representative for details about obtaining a valid support agreement or with questions about your account.
Resolved Issues
- SMARTA-1214
NCM is unable to pull admin config files from Cisco ASR 9910 Routers.
- SMARTA-1162
SNMPv3 discovery failure on CIsco devices when using AES-256.
Known Issues
- SR 30855404 / CQECC00487503
Out of band accessible devices classes that support SNMP/TFTP to manage configurations cannot be managed by using SNMP/TFTP.
Workaround: Ensure that a working read-write credential is defined and used for SNMP discovery. Without scheduling, update the credentials if the device used only a read-only credential, since this is insufficient for configuration management by this protocol combination.
- CQECC00495460
Devices using SCP for configuration change may require an administrator user account for configuration file transfers to succeed. If an administrator account is not used, configuration pulls and pushes can result in a failed job.
Note: The error message for a failed job of this type may not properly describe the lack of device account privilege necessary.
Workaround: To determine if an administrator account is required for a specific device, perform the configuration file transfer manually from the device server managing the device.
- CQECC00533972
The Hotfix Uninstaller does not update the Help > About dialog box with the correct hotfix number on Windows platform.
- CQECC00634200
The F5 D39 device discovery passes using SNMP, but the discovery fails using Term.
- CQECC00637458
During discovery of devices, Juniper WXC devices are discovered by Samsung Router device class, although the device class list does not include the Juniper WXC device class.
Workaround: Juniper WXC device class must be added to the device class list so that Juniper WXC devices are discovered by Juniper WXC device class.
- CQECC00640576 / CQECC00638268
After running an operating system upgrade on Alcatel EFM devices, sometimes, Network Configuration Manager incorrectly displays that the upgrade has failed even though the operating system was successfully upgraded on the device.
- CQECC00640720
During a pull operation to view the system properties of Covaro device, the serial number is not displayed in NCM.
- CQECC00642312
During a pull operation on Overture devices to view the interfaces, the Infotype for all the interfaces that are pulled shows as Generic type.
- CQECC00642503
SNMP support is enabled in the device driver for Adtran Total Access 924e even though the device does not support SNMP.
Workaround: NCM will support SNMP for the device if the device supports SNMP
- TASC 303409 / IAP Certifications
Model name will be displayed as VirtualControllerIAP when the Aruba IAP device is in virtual controller mode and the exact model of the IAP will not be displayed. Certain device specific information might not be pulled.
There is no workaround for this behaviour. Recertification can be done if more information is received on the VirtualControllerIAP environment.
- IS-12026
Error while installing DSr on Windows platform.Error Message : “Windows error 2 occured while loading Java vm”.
Workaround: During DSr installation on Windows platform, if there is an error then follow the below steps:
- Unzip jre folder in the following location:
$VOYENCE_HOME/jre - Open command prompt.
- Navigate to DSr build directory.
- Invoke the following command to start the installation:
NCM_Device_Drivers_24_HF1_Windows.exe LAX_VM "c:\smarts-ncm\jre\bin\java.exe".
- Unzip jre folder in the following location:
- IS-12026
Error while uninstalling DSr on Windows Platform.Error Message : “Windows error 2 occured while loading Java vm”.
Workaround: During DSr uninstallation on Windows platform, if there is an error then follow the below steps:
- Unzip jre folder in the following location:
$VOYENCE_HOME/jre - Open command prompt.
- Navigate to the directory: $VOYENCE_HOME/software/Uninstall_Device_Driver_HF1
- Run the uninstall VMware Smart Assurance Network Configuration Manager Device Drivers.exe.
- Unzip jre folder in the following location:
