Installation guide
Table Of Contents
- COPYRIGHT
- TABLE OF CONTENTS
- INTRODUCTION
- Support OS - VM ESX
- PRE-REQUISITES
- ADDITIONAL INFORMATION
- WHAT’S NEW IN VOYENCECONTROL 4.1.0
- FIXED ISSUES
- (20112) – Cut-Through not offering a "more" Option when Viewing Configuration
- (21536) – User passwords – Visible in commmrg.log when using Cut-through
- (21555) – Device Data Fields- Cleared Despite no User Input
- (21618) – Network Navigation Tree – Problem with Display
- (21661) – Network Navigation Tree – Right-Click Options not Working Properly
- (21690) – Network Navigation Window – Right-Click Options – Working Intermittently
- (21759) – Pulled Cisco IOS Devices – Self-Check rule Failed
- (21834) – Database Size - More Space than Required
- (21878) – Failed Policies – Not Displaying in the Comments Section
- (21994) – Customize Column Sizing not being Maintained
- (22062) – Clicking "Schedule" after running Compliance Audit – Devices Missing
- (22147) – Repeated Error Message - Server and jboss logs
- (22157) – Audit Trail – Incorrect Hierarchy
- (22319) – Graphical User Interface - Slow Response/Jboss stuck at 100% CPU
- (22407) – Cannot Schedule OS Update for Multiple Devices
- (22521) – Large Auto Discovery Jobs do not Complete
- (22534) – Random "Resource Not Found" Error at Login
- (23074) – Compliance Error When Attempting to Execute Compliance Audit on Nokia Appliance
- KNOWN ISSUES
- (22192) – Data Field Names – New Data Field Names are not Replacing the Old Data Field names after Migration
- (22386) – Disabling SNMP causes Failing Request
- (22556) – Schedule Configuration Change - conflict with Velocity Template Commands
- (22579) – Upgrading from VoyenceControl 4.0.1 to 4.1.0 causes Exception on UI Load
- (22595) – Intermittent deadlock - Importing/Exporting Automation Library items.
- (22607) – Compliance Steps – Existing RegEx Compliance Test
- (22883) – SAML Enable Script - Source /etc/voyence.conf before Installation
- (22906) – Connection to SSH Proxy Fails
- (22943) – "Error: Version Already Installed" Message after a Failed install or Upgrade
- (23027) – Upgrading a Device Server from VoyenceControl 3.6.2 to 4.1.0 does not Retain Multi-Level Mode
- (23089) – Upgrading to VoyenceControl 4.1.0 - Report Advisor URL Points to "http:///web"
- (23118) – System Management Console - Password gets reset to 'sysadmin' after Upgrading (Windows Only)
- (23150) – Config Pulls After Auto Discovery - Not Getting Scheduled when Using a Remote Device Server
- (23542) – Installing from a Read Only File System – Components Needed
- (23548) – Can Not Install Integration Modules under the VoyenceControl 4.1 API in VoyenceControl version 4.1.0
- INSTALLING VOYENCECONTROL 4.1.0
- UPGRADING TO VOYENCECONTROL 4.1.0
- WHERE TO GET HELP
EMC VoyenceControl – Release Notes
KNOWN ISSUES
The following are known issues in VoyenceControl 4.1.0. Unless otherwise noted, issues
listed here apply to Linux, Windows, and Solaris environments.
Note: The number displayed within parenthesis is used for internal quality tracking purposes.
(22192) – Data Field Names – New Data Field Names are not Replacing the
Old Data Field names after Migration
When migrating from VoyenceControl 3.6.x or 4.0.1 to VoyenceControl 4.1.0, the data field
names that are migrated during the upgrade to 4.1.0 are not replaced in the template editor’s
reference variables. The data field names continue to work correctly within the application, but
the actual display names in the editor do not change.
(22386) – Disabling SNMP causes Failing Request
The Identity and System Properties are now always pulled on each request. Some devices do
not support both term and SMNP for Identity and System Properties. Therefore, it is possible
for these actions to fail or return 'best guess' results if the device credentials enabled do not
exactly match what is in the package for the CU. For example, the F5 driver only supports
SNMP pulls for Identity and System Properties. If a F5 device is configured with SNMP
disabled, then all pulls will at best, return a warning.
(22556) – Schedule Configuration Change - conflict with Velocity Template
Commands
VoyenceControl does not support device configurations that conflict with Velocity template
commands.
Workaround
You must use #literal, followed by #end around the config text that you want to push. For
example:
#literal
anytext that collides with velocity syntax
#end
(22579) – Upgrading from VoyenceControl 4.0.1 to 4.1.0 causes Exception
on UI Load
The generated JNLP file in VoyenceControl specifies 1.6+, but if a user has a 4.0.1 generated
file in their browser and java web start cache, the cache must be cleared before using the
upgraded product.
Release Notes Version 4.1.0
Page 13