6
The default state of the IPMI/DCMI privilege for IPMI-based SPs managed by the appliance is not
displayed for Service Processors that were discovered prior to appliance firmware upgrade, although any
Service Processor added to the appliance prior to appliance version 2.5.0.8 will use the Administrator
IPMI/DCMI Privilege. Please delete and re-add the Service Processor to restore the correct display.
The Java JRE-7u51 has introduced strict security requirements where native Service Processor vKVM
applets will fail to launch until the Service Processor supports the Java security requirements. The Service
Processor vendor should provide firmware updates to resolve these issues. Until the updates are in place,
consider workaround options that are consistent with your corporate security requirements.
When connecting a Service Processor to a private port of the Avocent® Universal Management Gateway
appliance for discovery, please ensure that the Service Processor has been configured for DHCP address
assignment and reset prior to connection for successful discovery. If the appliance firmware is updated by
USB boot or net boot, it may be necessary to disconnect the Service Processor and power-cycle or reset it,
then reconnect the Service Processor for rediscovery after the appliance is restored to normal operation.
If the Service Processor is reconnected before the appliance is restored, it may be necessary to manually
discover the Service Processor by defining and launching a SP discovery range including the IP address
range for the private port.
After a Service Processor has been added or discovered into the Avocent® Universal Management
Gateway appliance, dynamic data may not be available from the Web interface for up to five minutes and
time-outs may be seen during this initial five minute period, depending on network delays between the
Service Processor and the Avocent® Universal Management Gateway appliance.
Cisco UCS-B Chassis and Blades
Blade Virtual Media launches can only be supported if the blade credentials are passed from the viewer
back to the Service Processor unencrypted. A second Virtual KVM / Media button is presented in the Web
interface to launch the vKVM session so that a Virtual Media session can be launched from the vKVM
session using the unencrypted credentials. There is a confirmation prompt to continue the launch. If the
Virtual KVM button is used to launch the vKVM session, a Virtual Media session launch from that vKVM
session will fail as the Virtual Media credentials will be encrypted. The DSView™ software does not
support the unencrypted Virtual Media launch. Also, launching a blade vKVM through a chassis login does
not support the unencrypted Virtual Media launch.
Chassis autologin sessions are not supported.
SoL configuration for blades is not supported.
Alerts are not generated when a Cisco UCS-B blade is removed or added from the chassis.
Dell DRAC4 and DRAC5
When the maximum number of sessions in DRAC4 or DRAC5 has been reached, a new AutoLogin or
vKVM SPAccess session will fail. The failure can be recovered by resetting the SP via Telnet or SSH. The
command for SP reset is ‘racadm racreset’.
The DRAC5 does not support use of the forward slash (“/”) in login passwords. Avoid use of the forward
slash in the password definition.
DRAC5 firmware supports only IE7 and Firefox2 browsers. SP Access sessions, especially vKVM and
Virtual Media sessions may not work in newer versions of Firefox and Chrome and are not supported. SP
Access to the DRAC5 is possible with IE9.
The Dell DRAC5 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.
Dell DRAC6 Monolithics
Sensor data is not returned from iDRAC6 monolithics when the Dell server is turned off. After the server
power is restored, refresh the Targets/SP/Sensors tab display, if needed, to update the sensor display.
