Avocent MergePoint 5200 Bedienungsanleitung PDF herunterladen (Seite 5)

2. For web browsers in some particular OS (i.e. Linux), if Java Applet in the web browser have no privilege to

listen on Port 443 of local IP address (127.*.*.*), the Browser session, Autologin or vKVM won‟t work. It is

because the Java Applet in web page of Dell DRAC3 uses the hard-coded port 443 to communicate, but

DirectCommand applets of MergePoint appliance can‟t redirect the communication between the web client

and DRAC3 via port 443 due to the privileges.

3. When the maximum number of sessions in DRAC4 or DRAC5 has been reached, the Autologin or KVM will

be failed. You need to reset the firmware of the SP via Telnet or SSH.

The command for reset the SP firmware:

racadm racreset

4. If DirectCommand launches for DRAC5 servers are unsuccessful, insure that the JRE is set to allow

temporary file storage and that previous temporary files are deleted through the Java Control Panel.

5. Sometimes, vKVM DirectCommand launches for DRAC5 servers are unsuccessful and only show a blank

screen when running from the Firefox browser. In this case, we have seen successful operation using the

IE browser.

6. The iLO2 KVM runs with ActiveX in IE browser and with Applet in other browser (e.g. Firefox). The KVM

with ActiveX integrates Virtual Media, while KVM with applet does not.

iLO remote console (vKVM) does not support multi-session in MS IE via DirectCommand.

7. vKVM operation to ELOM servers may conflict with other network services commonly run on server

machines. If conflicts occur, we suggest performing these operations on a workstation computer instead

of a server computer.

8. When a vKVM session is connected on a RSA_II server, a second login with the same userid will cause the

original vKVM session to be disconnected. So, a second login through the MergePoint SP manager will

cause the first vKVM session to be disconnected. This behavior is by design in the RSA_II servers.

9. Intermittent load failures of the vKVM and VM applets on RSA_II servers are seen when the JRE is allowed

to keep temporary files on the computer. When using these vKVM and VM applications on RSA_II servers,

we recommend setting the JRE to disallow temporary file storage through the Java Control Panel.

10. vKVM operation to RSA_II servers launched through a browser login session may not be successful. We

recommend using the vKVM autologin operation.

11. vKVM operation to RSA_II servers is incompatible with JRE-6u13. We recommend using JRE-6u11 or

JRE-6u14 for these applications.

12. When managing RSA_II servers through the MergePoint SP manager using DSView software,

DirectCommand sessions sometimes cannot be successfully launched when using JRE versions above

6u7 without disabling “the next-generation Java Plug-in” setting through the Java Control Panel. If these

issues continue to occur disabling “the next-generation Java Plug-in”, we recommend downgrading the

JRE to 6u7.

13. The Merge Chassis operation of IBM BladeChassis with a DSR® KVM over IP switch within the DSView

software fails to complete when the BladeChassis and blades are all discovered within the MergePoint SP

manager. To work around this issue, we recommend that the BladeChassis and the DSR switch are

discovered and merged within the DSView software and the BladeChassis is discovered within the

MergePoint SP manager, then each blade in the MergePoint SP manager -discovered chassis is

individually merged with the associated blade in the DSView software-discovered chassis.

14. The KVM and vMedia function of IBM Blade is integrated with the KVM/vMedia of IBM BladeCenter‟s

KVM/vMedia. So you can access each blade through KVM applet of BladeCenter.

15. You can visit DRAC/MC‟s digital KVM/vMedia for a blade through “Browser session” ONLY IF the client

can communicate with the digital KVM‟s IP directly.

16. Sometimes, autologin operation to DRAC-MC servers do not complete and display “Internet Explorer

cannot display the webpage” (or blank page if default browser is FF3). The autologin operation has been

observed to complete if the page is refreshed.

17. You can visit KVM/vMedia of a HP Blade through HP BladeCenter‟s “Browser session” or “Autologin”

interface ONLY IF the client can communicate with the Blade‟s IP directly. HP Blade can‟t be accessed

directly from HP OA via DirectCommand. So if you want to visit the HP Blade via BladeCenter, you need to

add every blade as an SP, and then you are able to visit the SP‟s vKVM.

1 2 3 4 5 6

Release Notes 1

Kommentare zu diesen Handbüchern

Keine Kommentare

Avocent MergePoint 5200 Bedienungsanleitung Seite 5

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Prozessoren Avocent MergePoint 5200