Avocent Advanced Console Server ACS 6000 Notas de lançamento - Página 9

Procurar online ou descarregar pdf Notas de lançamento para Hardware de rede Avocent Advanced Console Server ACS 6000. Avocent Advanced Console Server ACS 6000 15 páginas. Universal management gateway

Imprimir página



Each SPAccess session launched to blades in a blade chassis using blade-through-chassis (use of the

single sign-on feature of the chassis to access the blades indirectly through the chassis) opens a separate

session on the chassis, so it is possible that all active sessions for the chassis may be consumed if multiple

sessions are launched in a short period of time. If this happens, please logout of active blade sessions and

allow time for the chassis to timeout its sessions.

IBM RSA-II



When a vKVM session is connected on an RSA-II server, a second login with the same user ID will cause the

original vKVM session to be disconnected. This includes a second login through the Avocent® Universal

Management Gateway appliance which will use the same user ID. This behavior is by design in the RSA-II

servers.



Intermittent load failures of the vKVM and Virtual Media applets on RSA-II servers have been recorded when the

JRE is allowed to keep temporary files on the computer. When using these vKVM and Virtual Media applications

on RSA-II servers, Avocent recommends setting the JRE to disallow temporary file storage through the Java

Control Panel.



vKVM operation to RSA-II servers is incompatible with JRE-6u13. Clients should use JRE-6u14 or later for these

applications.



The native browser UI for the IBM 3950 RSA-II server will not allow login if the password contains special

characters unless the SP firmware is upgraded to A3EP40A or later.

IBM BladeCenter and Blades



If the SP discovery feature is used to manage the IBM BladeCenter, the IBM BladeCenter needs to be

configured so that its "lockout period after 5 login failures" is one minute, if this setting is consistent with

corporate security requirements. This setting is located within the IBM BladeCenter web interface under

System-MM Control-Login Profiles-Global Login Settings. Otherwise, the IBM BladeCenter must be manually

added to the appliance.



When adding an IBM BladeCenter to an Avocent® Universal Management Gateway appliance, the user

account of the IBM BladeCenter provided to the Avocent® Universal Management Gateway appliance

must have its "Maximum simultaneous active sessions" set to 0.



The IBM BladeCenter Virtual Media applet fails when launched using the VGA console of the Avocent®

Universal Management Gateway appliance. Please use the remote Web interface from a Windows client

for these operations.

IBM IMM Monolithics



IMM-based monolithic servers purchased with the "IMM Standard" option do not support vKVM. The

Avocent® Universal Management Gateway appliance cannot detect the "IMM Standard" configuration prior

to web interface login, so the user is not notified until after the vKVM login attempt.



The IMM Monolithic servers do not support use of the special characters ':', '&', '\' and '<' in login

passwords.



If the SP discovery feature is used to manage any type of IBM IMM or BC server, the IMM needs to be

configured so that its "lockout period 5 login failures" is one minute. This setting is located within the IMM

web user interface under System -IMM Control-Login Profiles-Global Login Settings.



SPs may deny login requests if there are too many users/connections; this can result in 500-Internal Server

Error messages being displayed when starting SPAccess sessions to the IMM. Check if there are multiple

sessions connected to the SP using the SP's native Web interface and close them. It may also be

necessary to reset the SP to restore connectivity.



Remote Control sessions launched from the IMM's native Web Page in an SPAccess Browser or AutoLogin

session may fail to start using the Chrome browser. If this issue is seen, try using Firefox or IE9.