Owner's Manual

SYSCFG Issues
• In DRAC 5, the --virtualmedia and --vflash options do not work if there is an active virtual media session.
Disconnect the virtual media using the DRAC GUI. Log into DRAC. Click Media > Virtual Media > Disconnect.
• The syscfg --bootseq command detects CD-ROM with SAS/SATA controllers as unk.emb.1.
• On R815, syscfg power --profile option allows to set to apc, though apc is not supported on R815. syscfg does not
throw an error message.
• On Windows PE 3.0, when you run the syscfg command to list all available options, if you press CTR + C before the
command fully executes, an error message is displayed. Click OK. You can ignore the message.
• The option for "powerctl," which is "softshutdown," does not work on Windows PE.
• The "--solbitrate" option in "solcfgparams" and the "--mgscommbitrate" option in "serialcfgparams" accept a baud
rate of 57600, but tools such as "ipmish" and "solproxy" do not function at that baud rate for PowerEdge systems.
• The legacy attribute values enable/disable are also supported for 12G systems for backward compatibility. In
future releases, these arguments might be deprecated. Try to use the values shown in help message for BIOS
options for 12G server.
RACADM Issues
• If you use virtual media to boot into Windows PE, executing certain RACADM commands may cause Windows PE to
crash.
• After generating the rac configuration file using the "racadm getconfig -f <file_name>" command, comment out
the following properties in the configuration file before you update a configuration using the "racadm config -f
<file_name>" command:
o #cfgRacTuneCtrlEConfigDisable=0
o #cfgRacTuneLocalConfigDisable=0
• VLAN objects (cfgNicVLanEnable, cfgNicVLanId, and cfgNicVLanPriority) displayed using the local RACADM
command "racadm getconfig -g cfgLanNetworking" or VLAN objects generated in the configuration file using the
local RACADM command "racadm getconfig -f <file name>" do not contain the leading "#" symbol which indicates
that they are read-only.
Windows PE Installation Issues
• If virtual flash is enabled and does not contain a valid image (for example, if the virtual flash contains a corrupt or
random image), you may not be able to install Windows 2000 or Windows 2003, locally or remotely. To fix this
issue, install a valid image on virtual flash or disable virtual flash if it will not be used during the installation
procedure.