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
(23118) – System Management Console - Password gets reset to 'sysadmin'
after Upgrading (Windows Only)
When upgrading to VoyenceControl to 4.1.0 on Windows, the System Management Console
password is reset to 'sysadmin'.
Workaround
1. To set the password, run the [Product Directory]/tools/password-change.pl utility, and
change the password for the 'smc-user' account.
2. For more information on using the password-change.pl utility, refer to the Installing
VoyenceControl on Windows Server 2003.
(23150) – Config Pulls After Auto Discovery - Not Getting Scheduled when
Using a Remote Device Server
In some rare cases, the Config Pull task will not automatically be scheduled after an auto
discovery when using a remote device server.
Workaround
1. Log into the Application Server as root (Linux/Solaris), or Administrator (Windows).
2. Stop the sysadmin service (Linux and Solaris ONLY) using: /etc/init.d/sysadmin stop
3. Stop the JBoss service:
/etc/init.d/jboss stop (Linux/Solaris)
sc stop NCM_JBoss (Windows)
4. Stop the controldaemon service:
/etc/init.d/controldaemon stop (Linux/Solaris)
sc stop NCM_Controldaemon (Windows)
5. Start the controldaemon service:
/etc/init.d/controldaemon start (Linux/Solaris)
sc start NCM_Controldaemon (Windows)
6. Start the JBoss service:
/etc/init.d/jboss start (Linux/Solaris)
sc start NCM_JBoss (Windows)
7. Start the sysadmin service (Linux and Solaris ONLY) using: /etc/init.d/sysadmin start
(23542) – Installing from a Read Only File System – Components Needed
There is an issue when installing from a read-only file system, such as a CD or mounted ISO,
where only the Core component of Voyence Control is installed. Without all of the components,
functionality (such as integrations and discovery) will not work. If this occurs, the remaining
components must be installed separately.
Workaround
1. It is recommended that prior to installation, copy the files to a writeable file system,
such as C:\Installers.
2. Run the install from that location.
Note: If the installation must be done from a read-only file system, the individual components
must be installed individually.
Release Notes Version 4.1.0
Page 17