Red Hat NETWORK 4.1.0 - Guide d'installation Page 13

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 20
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 12
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
Vue de la page 12
1 2 ... 8 9 10 11 12 13 14 15 16 17 18 19 20

Commentaires sur ces manuels

Pas de commentaire