Release Notes

file:///T|/htdocs/SOFTWARE/smdrac3/drac4/170/en/readme/readme.txt[10/26/2012 8:38:00 AM]

The following subsections list the known issues regarding the

implementation and operation of the DRAC 4:

* DUP updates will not work with SLES 10 SP1 and SP2.

* vMedia will not work with SLES 10 SP2.

* DUP updates and vMedia will not work with RHEL 5 Update 2.

* While configuring the DRAC 4 using 'racadm config -f <filename>'

command, for configuring options, for example password,

do not use ';' as a character, because racadm treats that as

the beginning of a comment and ignores everything that follows it.

For example "cal;vin" will be configured as "cal" in DRAC 4.

* If you configure the Domain Controller under the "Specify Server"

option on the DRAC and if the Association Object (AO) contains

the user and RAC object on the same domain, the Active Directory

either the user or the RAC object on the association is from

a different domain, and if you provide only the domain controller

information, the Active Directory login using Extended Schema

will fail. In this case, you should configure the global

catalog as well as the AO Domain Option to be able to login.

* Using the Virtual Media feature of DRAC 4 version 1.70 requires

the older virtual media plug-in to be deleted from the browser cache.

After that a download of a fresh plug-in is required to use

Virtual Media.

* When connecting to the DRAC 4 vKVM console, you may receive a

warning message that states that the DRAC's hostname does not

match the certificate host name. DRAC cards ship with a default

server certificate, which has the same hostname for every card.

While you can choose to trust this default certificate,

it is recommended that you generate a CSR

(certificate signing request) with the correct hostname of the

DRAC card, and sign it with a trusted CA (certificate authority).

This signed certificate can be uploaded to the DRAC card,

which will prevent the hostname mismatch warning message from

getting displayed. For more information, see the DRAC 4

User's Guide. (110258)

* When using the DRAC 4 command to restart or shut down a system

running Microsoft Windows Server 2003 R2 that has the R2 IPMI

driver installed, multiple events will be logged in the:

- Hardware Events bucket in Event viewer

- Hardware Log in Server Administrator and

- System Event Log (SEL)

These events are used by the Windows IPMI driver to store the

shutdown comment that describes why the system was shut down or