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
WHAT’S NEW IN VOYENCECONTROL 4.1.0
This section details enhancements in VoyenceControl for the 4.1.0 release.
Addition of RHEL 5 Support
VoyenceControl 4.1.0 now supports Red Hat Enterprise Linux 5, 64-bit.
Java Support
As of this release, any Java 1.6.x, up to and including 1.6.0_12 versions are supported
versions of Java within VoyenceControl 4.1.0.
Automation Library - Quick Steps to Compliance
Previously in the 4.0.1 release, Preconditions and Check Patterns tabs were used
in the Automation Library Editor when creating tests. Now, Scope and Rule tabs are used to
create a test.
These new tabs take the place of the previous tabs. Using the Scope and Rule tabs
allow you to quickly set the operators that qualify the configuration, prior to running
the test, and assist you in further scanning the configuration to locate specific
information from that file.
A Steps Compliance test consists of one or more Steps that are executed in order,
from the first step to the last. Each Step, individually, has all the abilities of
a RegEx test, including:
The ability to define a scope and disqualify the test if the scope is not met, or as an
alternative, generate a remedy if the scope is empty.
The ability to extract stanzas from the steps input for use in the Pattern, or in
subsequent steps.
The ability to execute a Pattern against the configuration.
Each step in a test is logically divided into components, each of which is optional.
However, you must define at least one step, and have content within either the Scope
or Rule tab. These are:
Scope Definition - Defines the textual scope to be used for the rule processing,
and optionally passed to subsequent steps. Scope definition can be sub-divided into
stanza extraction, stanza filtering, and the handling of an empty scope (as either
a disqualified test or the generation of a remedy).
Rule Processing - Includes executing a Regular Expression (RegEx) Pattern against
the stanzas generated by the steps Scope Definition (or against other selectable
inputs); and Remedy Generation, which is executed if the rule processing for a step
determines that the device is not compliant.
Release Notes Version 4.1.0
Page 8