Release Notes

file:///T|/htdocs/SOFTWARE/svradmin/5.1/en/readme/readme_sa.txt[10/23/2012 1:31:47 PM]
swapping. The cfgLanNetworking group is configured using the
"racadm config" command.(132894)
* The remote access controller uses FTP protocol to perform some of
the Dell OpenManage commands. If a firewall is installed in the
system, it may cause these commands to fail.
The following Server Administrator CLI commands use FTP protocol to
communicate with the RAC:
"omconfig rac uploadcert"
"omconfig rac generatecert"
The following racadm commands use FTP protocol to communicate with
the RAC:
"racadm sslcertupload"
"racadm sslcsrgen"
"racadm fwupdate"
* If the RAC configuration is reset to factory defaults using the
"racadm racresetcfg" command, the RAC configuration tab in Server
Administrator does not reflect the reset configuration settings
until the system reboots. Also, the RAC configuration page in
Server Administrator cannot be used to make any configuration
changes until the system reboots.
* The RAC does not support local RAC user IDs with special
characters. When adding a local RAC user, use only alphanumeric
characters for the user name.
* While the RAC is being reset, the Instrumentation Service cannot
read sensor data for certain systems. As a result, the voltage,
temperature, and other probes may not be visible on the Server
Administrator home page until the RAC has completed resetting.
* The RAC may not send traps when your system is locked up. To enable
traps to be sent when the system is locked up, you must configure
the watchdog timer using the Server Administrator GUI. In the Server
Administrator GUI, click the "Properties" tab and ensure that
"Auto Recovery" is selected. The default value of the "Action On
Hung Operating System Detection" setting is "None". "None" indicates
that detection will not be performed.
* RAC firmware 2.0 and higher does not support passwords with special
characters (non-alphanumeric) only for RAC user IDs logging in using
the Web-based interface (with Local RAC Authentication). If you
created RAC user IDs using previous versions of the firmware or if
you created user IDs using Server Administrator that is running
version 2.0 firmware on the managed system, you cannot log in to
the RAC.
Use one of the following four methods to correct this issue: