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
(23027) – Upgrading a Device Server from VoyenceControl 3.6.2 to 4.1.0
does not Retain Multi-Level Mode
Note: This issue only applies to environments where Multi-Level mode is enabled (which is
not common).
When upgrading a VoyenceControl device server that is configured for Multi-Level mode, from
version 3.6.2 to 4.1.0, you must manually create the cutthrumode file. This is not an issue
with upgrading from VoyenceControl 4.x, or an issue with new installations.
To create the cutthrumode file, follow these steps:
1. Log onto the VoyenceControl server as root (Linux, Solaris), or Administrator
(Windows).
2. Create a file named [Product Home]/data/devserver/cm/cache/cutthrumode with the
contents: multilevel
Note: The file should only contain the word "multilevel" without quotes, and without a
carriage return at the end.
3. Repeat for each device server.
(23089) – Upgrading to VoyenceControl 4.1.0 - Report Advisor URL Points to
"http:///web"
When upgrading from VoyenceControl 3.6.2 to 4.1.0, the Report Advisor URL (on the landing
page and client) incorrectly points to "http:///web". The following steps are required for
correcting the problem.
Workaround
1. Determine the IP address of the Report Advisor server. This must be the external IP
address of the server where Report Advisor runs.
2.
Edit the [Product Directory]/ui/html/powerup.jnlp file. Look for the line containing
"reports_advisor_url". Change the value portion of the line so that it contains the valid
URL to the Report Advisor server.
For example:
<property name="reports_advisor_url" value="https://192.168.1.100/web/"/>
3.
Save, and then close the file.
4.
Edit the [Product Directory]/ui/html/index.html file. Look for the line containing "launch
Voyence Report Advisor". Change the href portion of the line so that it contains the valid
URL to the Report Advisor server.
For example:
<a href="https://192.168.1.100/web">launch Voyence Report
Advisor</a>™<br />
5.
Save, and then close the file.
Release Notes Version 4.1.0
Page 16