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
(22595) – Intermittent deadlock - Importing/Exporting Automation Library
items.
When using the Automation Library and left clicking on the Import button, the applications
deadlocks intermittently. This is a Java bug. The following are the Java defect IDs you may
want to use for tracking purposes.
http://bugs.sun.com/view_bug.do?bug_id=6741890
http://bugs.sun.com/view_bug.do?bug_id=6789084
http://bugs.sun.com/view_bug.do?bug_id=6744953
Note: This deadlock condition may occur in the application anytime a user opens a file dialog
window.
(22607) – Compliance Steps – Existing RegEx Compliance Test
Users should be aware that when an existing RegEx compliance test is migrated in
VoyenceControl 4.1.0, the preconditions (if any) become the first Step in the migrated test,
and each check pattern becomes a subsequent Step. If there are no preconditions, then the
first check pattern becomes the first Step, followed by the rest of the check patterns as
subsequent Steps.
(22883) – SAML Enable Script - Source /etc/voyence.conf before
Installation
Java must be configured in your environment.
Linux/Solaris
Java must be correctly configured in this environment. Source /etc/voyence.conf prior to
invoking the enableSaml.pl script. Type 'source /etc/voyence.conf' to source this file,
which sets the 'JAVA_HOME' variable needed by the script.
Windows
Java must be correctly configured in this environment. Ensure the location of your Java
installation is in the Windows 'CLASSPATH' system variable, and that your 'JAVA_HOME'
system variable is correctly defined.
(22906) – Connection to SSH Proxy Fails
For an SSH Client to successfully connect with SSH Proxy on VoyenceControl, X11 forwarding
should be disabled on the SSH Client.
Release Notes Version 4.1.0
Page 14