7
Dell DRAC6 Blades
On the M1000e, occasionally clicking the
Launch iDRAC GUI
button for one of the blades will not complete
a single sign-on login due to a Dell limitation. Please log in manually in these cases.
When M600, M605 or M805 blades are discovered by the appliance as standalone Service Processors,
occasionally the SPAccess Browser and SPAccess Browser-AutoLogin buttons are not enabled in the Web
interface or in the
DSView™ 4 software. If this occurs, please delete the Service Processor from the
appliance, reset the Service Processor, and then add the Service Processor back into the appliance.
Power information is not available from M600, M605 or M805 blades.
Virtual Media connections to the iDRAC6 blade Service Processors are not supported from the appliance
local port interface as the Service Processors do not natively support this environment.
Virtual Media connections from SPAccess sessions using the ActiveX viewer in the
DSView™ software
proxy mode are failing. Please use the Java viewer for these functions, or use the ActiveX viewer through
the appliance Web interface or through the
DSView™ software without enabling the proxy server.
Dell M1000e CMC
The login process for the M1000e may take up to 20 seconds after proper username and credentials are
presented, so it may take several seconds to access some features in the Avocent® Universal
Management Gateway appliance Web interface. For example, displaying power information may take
15-20 seconds for an M1000e chassis.
When connecting an M1000e chassis to a private port of the appliance, SPAccess AutoLogin sessions to
blades either directly or through the chassis may intermittently abort if using FF or IE. If this is seen, try
using Chrome.
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 log out of active blade sessions and
allow time for the chassis to time out its sessions.
SPAccess sessions may now be successfully launched directly to Dell M610/M710 (iDRAC6) blade servers
with iDRAC6 Service Processor firmware 3.50; however, sessions launched through the chassis are still
failing. Please add or discover the individual iDRAC6 blades separately from the chassis (if this has not
already been done), then launch SPAccess sessions directly to the iDRAC6 blade server.
Dell iDRAC7 Monolithics and Blades
SPAccess Browser-only sessions may not work to an iDRAC7 when using the VGA Console. Manually
launch a new tab and browse using (https://<IP>) to the SP using the Browser Tabs on the VGA Console.
The Dell iDRAC7 Service Processor does not natively support Internet Explorer 11 without compatibility
mode set in the browser. Please also set compatibility mode when SPAccess sessions are launched.
FTS iRMC
Power data can be retrieved from FSC iRMC service processors only if their firmware includes the DCMI
IPMI extensions (such as the Intel Node Manager).
FTS iRMC S2
Power data can be retrieved from FSC iRMC S2 service processors only if their firmware includes the
DCMI IPMI extensions (such as the Intel Node Manager).
iRMC S2 SPs that use log in passwords containing the ampersand (&) character cannot be discovered or
managed by the Avocent® Universal Management Gateway appliance. The SP can be discovered and
managed when the login passwords do not contain the ampersand character.
