Avocent DSView® 3
Software Update Patch
This document outlines:
1. Update Instructions
. Language Support Information
. Known Issues
. Change Log
updates DSView 3 software version 3.
Patch Version 3.
ovided as a full installation package.
Note: Since this
is provided as a full installation package,
there is no way to manually remove this patch.
Please see the document entitled “D
SView 3 Server Release 3.7.0.
ry Improvement Settings”, which describes the steps necessary to
improve the memory usage and performance of DSView 3 software.
Please contact Avocent Technical Support for download instructions.
A Replication should be performed on all spokes in the curre
DSView 3 server
See “Manually backing up and
ub servers” section of the online help for additional
needs to be applied to each DSView
ub and each
For installation on a supported Wi
Run the setup.exe and then follow the on screen instructions.
For installation on a Linux
From a command line type ./install.sh and then follow the on
If an upgrade from DSView 3 server
version 18.104.22.168 to 22.214.171.124
is performed, the following steps should be performed prior to
launching the first KVM session to eliminate problems with the Virtual
Close down all
Microsoft Internet Explorer
Go to Tools/Internet Options. Select the Programs panel.
Click on the Manage add
Select the Avocent DSView session launcher and press Delete.
Language Support Informatio
The language supported by this patch is English, Simplified Chinese,
Japanese, and Korean.
Problems have been found with the
Merge Target Endpoints
under the Tools
> Unit Tools page.
When merging targets and
that one of
Drill down to the target device and click on the Merge Target
From the Tools Page on the Units View, select the Merge Target
When merging a KVM target to a
n Avocent Power Management
outlet and t
hen adding it to Power
a second merge of another outlet to the same KVM
target is performed, the data from the two outlets
prevent this issue, m
PDU outlets to
targets before adding the ite
ms to a rack.
The following issues were fixed with this update:
A cascaded AutoView
switch was no
t correctly displaying the number
of ports the AutoView switch owned.
PuTTY session remained open after logging out of DSView 3 software.
Loss Communication (LCM) errors were not being reported properly for
Infrastructure Racks and Rows of Racks.
ing on to a local DSView 3 server as an Single Sign
using “localhost” in the URL, database became inaccessible (unable
to add/delete units).
Cascade Switch Overview page did not allow user to change type to
. A general issue o
ccurred when the user attempts
to update the cascade switch type from the Add Unit Wizard, Resync
Wizard, or Cascade Overview page. This caused the number of cascade
switch ports displayed in the Units View to be shown incorrectly.
s were not closing properly when the
appliance rebooted or the connection between DSView 3 and the
appliance was dropped.
Some connection paths other than “KVM” type returned the tools for
URL encoded report title was mishandling the display
characters in the URL in Internet Explorer 6.
IBM BladeCenters could only be added to DSR
KVM over IP switches
Now they can be added to any KVM type appliance, including AutoView
switches and MergePoint Unity
KVM over IP and serial console
Upgrading from DSView 3
v3.6 to v3.7, and then manually
would display “Management Module” as missing.
Duplicated ‘session started’ event log entries for DirectCommand
sessions were c
reated when a session was launched.
Username was not provided in the event log entries for MergePoint
Incorrect Japanese characters were displayed for error messages in
Could not launch DirectCommand session after enabli
ng SSH Pass
Serial Viewer will not launch when client browser uses JRE
PowerManager Units appearing in “Not Responding State”. Receiving
Critical LCMs Events for PowerManager Units.
Double byte characters were not saving correctly in Bu
An incorrect message appears when VMware viewer called and DSView 3
cannot resolve the ESX IP address from the ESX hostname.
Incorrect mapping of an ISO image that has any capital letters (e.g.
Iso or ISO) in the extension
maps this as a Virtual Floppy and it was not functioning properly.
IBM BladeCenter chassis could not be merged with DSR and AutoView
at the chassis level (fix requires the latest MergePoint SP
When an “IBM BladeCenter H” was added and then merged, if the IBM
BladeCenter was deleted and then rediscovered the merged devices
would still exist.