DSView 3 software Patch Version 3.7.0.156 (July 24th, 2009).

talkassistantΛογισμικό & κατασκευή λογ/κού

30 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

231 εμφανίσεις

Avocent DSView® 3
Management
Software Update Patch

Release 3.
7
.
0
.
156

Ju
ly

2
4
th
, 2009



This document outlines:

1. Update Instructions

2
. Language Support Information

3
. Known Issues

4
. Change Log


===========================================================
============

Update Instructions

=======================================================================

This
patch

updates DSView 3 software version 3.
7
.
0
.
124

(
April 3
, 2009
)
to
DSView 3
software
Patch Version 3.
7
.
0
.
1
56

(
July 24th
, 2009
).
This
patch

is pr
ovided as a full installation package.




Update
Patch

Installation




Note: Since this
patch
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.
15
6

Memo
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
nt
system.



Backup
the
DSView 3 server
.
See “Manually backing up and
restoring
h
ub servers” section of the online help for additional
information.



The patch
needs to be applied to each DSView
3
s
erver (
h
ub and each
s
poke)
.



For installation on a supported Wi
ndows
®

system:

o

Run the setup.exe and then follow the on screen instructions.



For installation on a Linux
®

and Solaris
TM

system
:

o

From a command line type ./install.sh and then follow the on
screen instructions.


Note:
If an upgrade from DSView 3 server
version 3.7.0.124 to 3.7.0.156
is performed, the following steps should be performed prior to
launching the first KVM session to eliminate problems with the Virtual
Media Client.


1.

Close down all
Microsoft Internet Explorer
windows.

2.

Reopen
Internet Explorer
.

3.

Go to Tools/Internet Options. Select the Programs panel.

4.

Click on the Manage add
-
ons button.

5.

Select the Avocent DSView session launcher and press Delete.


=======================================================================

Language Support Informatio
n

=======================================================================

The language supported by this patch is English, Simplified Chinese,
Japanese, and Korean.


=======================================================================

Known Issues

=====
==================================================================





Problems have been found with the

Merge Target Endpoints


feature
under the Tools
-
> Unit Tools page.
When merging targets and
outlets, i
t is
recommended
that one of
these
steps
is follo
wed:


1.

Drill down to the target device and click on the Merge Target
Devices tool.

2.

From the Tools Page on the Units View, select the Merge Target
Devices tool.




When merging a KVM target to a
n Avocent Power Management
Distribution Unit

(
PM

PDU
)

outlet and t
hen adding it to Power
Management rack,
if
a second merge of another outlet to the same KVM
target is performed, the data from the two outlets
is

never
added
together.
To
prevent this issue, m
erge the
PM

PDU outlets to
the
KVM
targets before adding the ite
ms to a rack.



=======================================================================

Change Log

=======================================================================

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.



When logg
ing on to a local DSView 3 server as an Single Sign
-
on user
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
an
AutoView 1x8

switch
. 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.



SSH Pass
-
through session
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
KVM sessions.



URL encoded report title was mishandling the display
of Japanese
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
switches
.



Upgrading from DSView 3
software
v3.6 to v3.7, and then manually
adding a

blade server

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

SP
Manager

sessions.



Incorrect Japanese characters were displayed for error messages in
VMware viewer.



Could not launch DirectCommand session after enabli
ng SSH Pass
-
through.



Serial Viewer will not launch when client browser uses JRE
1.6.0.11+.



PowerManager Units appearing in “Not Responding State”. Receiving
Critical LCMs Events for PowerManager Units.



Double byte characters were not saving correctly in Bu
lk Edit.



An incorrect message appears when VMware viewer called and DSView 3
software
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

occurs and

DSVi
ew 3
software
improperly
maps this as a Virtual Floppy and it was not functioning properly.



IBM BladeCenter chassis could not be merged with DSR and AutoView
switches

at the chassis level (fix requires the latest MergePoint SP
manager
plug
-
ins).



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.