The racadm utility is a command-line utility for setting up and configuring the DRAC III.
All command switches are case-sensitive. The command interface enables you to use the utility in batch mode. A series of calls to the racadm utility can perform actions such as upgrading the DRAC III firmware, setting a parameter to a specific value, and reading the configuration of a DRAC III.
This utility is available on the Systems Management CD (32-bit systems) or on the Server Management CD (64-bit systems).
NOTE: This command-line utility is supported on PowerEdge 7150 managed systems. However,
when using the utility on these systems, the primary command is "drscadm" instead of "racadm."
For more information on using the drscadm utility on Dell™ PowerEdge™ 7150 systems, see the
Dell OpenManage Remote Service Card User's Guide on your documentation CD.
NOTE: To limit the stress load on the managed system and the DRAC III when using the racadm
utility, it is important to add one- or two-second "sleep" or "delay" commands between each
racadm command.
The first part of this section describes the racadm commands, while the latter part provides procedures for configuring your DRAC III using the racadm utility.
With no options, racadm executes the help command, which displays a list of available tests and a one-line description of each. The racadm help <subcommand> displays any syntax and command-line options.
The argument 0x3 for the log level is the OR of STDOUT and STDERR messages. Both of these message types are written to the file name log. The verbose, or -v, option defaults to 0x3, or STDOUT, STDERR.
When using racadm commands and subcommands, you may encounter one or more of the following errors:
Local error messages – occur when there are problems with syntax, typos, incorrect names, and so on.
Example:
racadm <subcmd> : ERROR:<message>
Transport error messages – occur when the racadm communication paths to the DRAC III are not accessible. Transport error messages occur if Server Administrator is not running when the command is executed, or the remote access service is not up.
Example:
racadm <subcmd> : Transport : ERROR : <message>
DRAC III firmware errors – occur when there is a fault in the DRAC III firmware operation.
The DRAC III configuration file <filename>.cfg is used with the racadm config -f <filename>.cfg command. The configuration file is a simple text file that allows the user to build a configuration file (similar to a .ini file) and configure the DRAC III from this file. You may use any file name, and the file does not require a .cfg ending (although it is referred to by that designation in this subsection). The .cfg file can be:
Built from scratch
Obtained from a racadm getconfig -f <filename>.cfg command
Obtained from a racadm getconfig -f <filename>.cfg command, and then edited
NOTE: See "config / getconfig" for information on the getconfig command.
The .cfg file is first parsed to verify that valid group and object names are present and that some simple syntax rules are being followed. Errors are flagged with the line number in which the error was detected, and a simple message displays explaining the problem. The entire file is parsed for correctness, and all errors are displayed. No writes are performed to the DRAC III if an error is found in the .cfg file. The user must correct ALL errors before any configuration can take place. The -c option may be used in the config subcommand, which verifies syntax only and does not perform any write to the DRAC III.
Be aware of the following important points:
If the parser encounters an indexed group, it is the value of the anchored object that differentiates the various indexes. So the parser reads in all of the indexes from the DRAC III for that group. Any objects within that group are simple modifications at configuration time. If this represents a new index, the index is created on the DRAC III during configuration.
Indexes may be created and deleted, so over time the group may become fragmented with used and unused indexes. The user cannot specify a desired index in a .cfg file. If it is present, it is modified. If it is not present, the first available index is used. This allows flexibility when adding indexed entries, where the user does not need to make exact index matches between all of the DRAC IIIs being managed; they are added to the first available index. So a .cfg file that parses and runs correctly on one DRAC III may not run correctly on another if all of indexes are full and a new one was to be added.
If you want to keep all DRAC IIIs the same, use the racresetcfg subcommand to reset the DRAC III to factory defaults, and then run racadm config -f <file>.cfg. Ensure that the .cfg file has all the desired objects, users, indexes, and other parameters.
NOTICE: Using the racresetcfg subcommand resets the database to the original default
settings and removes all users and user configurations. While the root user is available, these
settings are also reset to the default.
All lines that start with '#' are treated as comments. A comment line must start in column one. A '#' character in any other column is treated as a # character. (Some modem parameters may have # characters as part of their string. No escape character is required. The user may want to generate a .cfg from a racadm getconfig -f <filename.cfg> command, and then perform a racadm config -f <filename.cfg> command to a different DRAC III, without adding escape characters).
Example:
#
# This would be a comment
[cfgUserAdmin]
cfgUserAdminPageModemInitString=<Modem init # not a comment>
All group entries must be surrounded by "[" and "]" characters. The starting "[" character denoting a group name must start in column one. This group name must be specified before any of the objects in that group. Objects that do not have a group name associated with them generate an error. The configuration data is organized into groups as defined in "DRAC III Property Database Group and Object Definitions." The following is an example of a group name, object, and the object's property value:
[cfgLanNetworking]
cfgNicIpAddress=143.154.133.121
All parameters are specified as "object=value" pairs with no white space between the object, =, or value. White spaces after the value are ignored. A white space inside a value string is left unmodified. Any character to the right of the '=' is taken as is. A second '=', a '#', '[', ']', and so forth. All of these characters are valid modem chat script characters.
See the example in the previous bullet.
An indexed object entry is ignored by the .cfg parser. The user cannot specify which index is used. If the index already exists, it is used, or else the new entry is created in the first available index for that group. The racadm getconfig -f <filename.cfg> command places a comment in front of index objects, which allows the user to see which ones are being used.
NOTE: The user may create an indexed group manually using the following command:
NOTE: A NULL string (two " characters [""]) indicates to the DRAC III to delete the index for
the specified group.
To view the contents of an indexed group, use the following command:
racadm getconfig -g <groupName> -i <index 1-16>
For indexed groups the object anchor must be the first object after the "[ ]" pair. The following are examples of the current indexed groups:
[cfgUserAdmin]
cfgUserAdminUserName=<USER_NAME>
"
[cfgTraps]
cfgTrapsDestIpAddr=<IP_ADDRESS>
"
"
[cfgDemandDial]
cfgDemandDialIpAddr=<IP_ADDRESS>
"
[cfgDialinUsers]
cfgDialinUsrPppUserName=<USER_NAME>
'
'
NOTE: Enter the racadm getconfig -f <myexample.cfg> command. This command builds a
.cfg file of the current DRAC III configuration. This file can be used as an example and as a
starting point for your unique .cfg file.
The configuration subcommand allows the user to set DRAC III configuration parameters individually or to batch them as part of a configuration file. After the .cfg file has been correctly parsed, each object is read. If the content is the same, no write to the DRAC III occurs. If the data is different, that DRAC III object is written with the new value.
The -f <filename> option causes <config> to read the contents of the file specified by <filename> and configure the DRAC III. The file must contain data in the format specified in "Parsing Rules."
-s
The -s, or synchronize option, directs <config> to synchronize the user and password database with Dell OpenManage Server Administrator (if any user passwords were modified).
-p
The -p, or password option, directs <config> to delete the password entries contained in the config file "-f <filename>" after the configuration is complete.
-g
The -g <groupName>, or group option, must be used with the -o option. The groupName specifies the group containing the object that is to be set.
-o
The -o <objectName> <Value>, or object option, must be used with the -g option. This option specifies the object name that is written with the string <Value>.
-i
The -i <index>, or index option, is only valid for indexed groups and can be used to specify a unique group. The <index> is a decimal integer from 1–16. Note again that the index is specified here by the index value, not a "named" value.
-c
The check option is used with the config subcommand and allows the user to parse the .cfg file to find syntax errors. If errors are found, the line number and a short description of what is incorrect are displayed. No writes occur to the DRAC III. This is a check only.
This subcommand generates error output upon encountering either of the following:
Invalid syntax, group name, object name, index, or other invalid database members
racadm utility transport failures
If no errors are encountered, this subcommand returns an indication of how many configuration objects were written out of how many total objects were in the .cfg file.
The getconfig subcommand allows the user to retrieve DRAC III configuration parameters on an individual basis, or all the configuration groups may be retrieved and saved into a file.
The -f <filename>, or filename option, causes <getconfig> to create the file <filename>. It then reads all the configuration data from the DRAC III and places it into the file <filename>. The created file is a format that can be used with the command racadm config -f <filename>.
-p
The -p, or password option, causes getconfig to include password information in the file for all passwords except for the user passwords (which are stored encrypted and cannot be decrypted). A # cfgUserAdmPassword line is displayed as an indication that the password is present. But no password text is displayed.
-g
The -g <groupName>, or group option, can be used to display the configuration for a single group. The groupName is the name for the group used in the racadm.cfg files. If the group is an indexed group, the -i option should be used.
-h
The -h, or help option, displays a list of all available configuration groups so the user may enter the desired group. This option is useful when you do not remember exact group names.
-i
The -i <index>, or index option, is valid only for indexed groups and can be used to specify a unique group. The <index> is a decimal integer from 1-16. If -i <index> is not specified, a value of 1 is assumed for groups, which are tables that have multiple entries. Note again that the index is specified by the index value, not a "named" value.
-u
The -u <username>, or user name option, can be used to display the configuration for the specified user. <username> is the log in user name for the user.
Sets the cfgNicIpAddress configuration parameter (object) to the value 10.35.10.110. This IP address object is contained in the group cfgLanNetworking.
racadm getconfig -f myrac.cfg
Reads all of the configuration objects, from all of the DRAC III group configuration parameters and place them in a file called myrac.cfg.
racadm config -f myrac.cfg
Configures or reconfigures the DRAC III. The myrac.cfg file may be created from the command specified in the previous example if the DRAC III has a desired configuration to be replicated. The myrac.cfg file may also be edited manually as long as the parsing rules in this appendix are followed.
NOTE: The myrac.cfg file contains no password information. To include this information in
the file, it must be input manually. If you want to remove password information from the
myrac.cfg file, use the -p option.
racadm getconfig -h
Displays a list of the available configuration groups on the DRAC III.
racadm getconfig -u root
Displays the configuration parameters for the user named root.
The coredump command displays detail information, including register values, recorded when the most recent bus error occurred, or the message No CORE dump available (if no previous bus error has occurred, or if the data has been cleared).
This bus error information is persistent across power cycles of the DRAC III adapter—the data remains in the flash memory of the adapter until either:
It is cleared using the coredumpdelete command
Another bus error occurs, which replaces the previous information with the more recent bus error information.
See the coredumpdelete command for information on deleting this information.
The coredumpdelete command clears the area reserved for persistent storage of bus error information. This operation is performed regardless of whether there actually exists any bus error information currently stored in the area reserved for this information.
See the coredump command for information on displaying the bus error information.
The racreset subcommand issues a reset to the DRAC III. The user is allowed to select how many seconds of delay occur before the reset sequence is started. The reset event is written into the DRAC III log.
A "hard" reset resets the entire DRAC III and is as close to a power-on reset as can be achieved using software. The DRAC III log, database, and selected daemons are shutdown gracefully prior to the reset. A hard reset should be considered as a last-ditch effort. PCI configuration is lost.
NOTICE: You must reboot your system after performing a hard reset of the
DRAC III.
soft
A soft reset is a CPU and CPU subsystem reset that resets the processor core to restart the software. PCI configurations are preserved. The DRAC III log, database, and selected daemons are shutdown gracefully prior to the reset.
graceful
A graceful reset is the same as a soft reset.
<delay>
The user is allowed to select how many seconds of delay occur before the reset sequence is started. A valid delay entry is between 1-60 seconds. The default is 3 seconds.
The racresetcfg command removes all database property entries that have been configured by the user. The database has default properties for all entries that are used to restore the card back to its original default settings. After resetting the database properties the DRAC III resets automatically.
NOTICE: Before using this command, ensure that you want to restore your database to
its original default state with default user root and default password calvin.
NOTE: After issuing a racresetcfg subcommand, you need to stop and then restart the following
services: Server Administrator, Server Administrator Event Monitor, and the SNMP service.
The fwupdate subcommand allows the caller to update the firmware on the DRAC III. The user may:
Start the actual update process of a firmware update file that has previously been loaded into the RAMdisk update area.
Check the status of the firmware update process.
Instruct the DRAC III firmware to get the firmware update file from a TFTP server and load it into the RAMdisk update area. The user may specify the <IP>:<path/file>, or use the default values found in the data base. The user may also specify to start the update after loading, or to terminate and make a separate call to start the update process.
Load the update file into the DRAC III RAMdisk area.
The update option performs a checksum of the firmware update file and starts the actual update process. If this option is entered by itself, it is assumed that a firmware update file has already been loaded into the RAMdisk using the -g, or -p options. This option may also be used along with the -g, or -p options. Meaning after the firmware update file has been loaded, the update process is started within the same call. At the end of the update, the DRAC III performs a soft reset.
-w
The wait option represents a delay in seconds to wait before proceeding with the update. The -w option is only valid with the -u option.
-s
The status option returns the current status of where you are in the update process. This option is always entered by itself. Do not mix the -s options with others. If you do, the only action is the return of the status as if it was the only option entered.
-g
The get option instructs the firmware to get the firmware update file from the TFTP server and place it in the RAMdisk area. The user may also specify the -a, and/or the -f options that are described next. In the absence of the -a, or -f options the defaults are read from properties contained in the group cfgRemoteHosts, using properties cfgRhostsFwUpdateIpAddr and cfgRhostsFwUpdatePath.
-a
The IP Address options specifies the IP address of the TFTP server.
-f
The path/filename option specifies the location on the TFTP server where the firmware update file is found.
-c
The checksum option allows the user to verify an update file that has been loaded into the RAMdisk area. The update file could have been loaded by any one of the two load mechanisms (FTP/TFTP). This option essentially gets the size of the firmware update file and calculates the checksum, and verifies the file token. The TFTP interface verifies the checksum after loading automatically. This option is mainly when using FTP. The -c option is not used with other options. (The -u option will always checksum before programming. It can be used along with the -u option, but is pointless, mainly a option used by development).
-D
After the update is complete, the DRAC III is reset. Upon boot, a call is made to reset all firmware configuration parameters to the default values.For more information, see "racresetcfg."
-p
The put option is used when you want to FTP the firmware update file from the managed system to the DRAC III. For reasons in the librac libraries, the -f option that specifies the filename of the update image must be called firmimg.bin. The update file is FTP'd into the DRAC III. The newly loaded image is then checksummed. If the checksum is not correct, an error message is displayed. The user need not enter the fwupdate -s option to do this. If the -u option is entered on the same command line, the update process starts.
racadm fwupdate -g - a 143.166.154.143 -f firmimg.bin
In this example, the -g option says the firmware gets the firmware update file from the location specified by the -f option from the TFTP server, at the IP address specified by the -a option. It is then loaded into RAMdisk. Since the -u option is not present, no update occurs.
racadm fwupdate -s
This option reads the current status of firmware update.
racadm fwupdate -u
The -u option starts the update process. This command assumes that a valid firmware update file has been previously loaded using the -g or -p options. The update file checksum is verified for correctness before proceeding.
racadm fwupdate -g -u -a 143.166.154.143 -f firmimg.bin
In this example, the -g option indicates that the firmware gets the firmware update file from the location specified by the -f option from the TFTP server, at the IP address specified by the -a option. The -u says to proceed with the update after the load.
The getssninfo command returns a list of currently active or pending users and optionally includes summary session table information. The summary information provides the total number of sessions in each of the defined Session Manager states:
The -A option eliminates the printing of data headers.
-u
The -u < username> user name option limits the printed output to only the detail session records for the given user name. If a "*" is given as the user name, all users are listed. No summary information is printed when this option is specified.
The getsysinfo command returns information about the DRAC III, system, or watchdog status depending on the command options. The order of data on output is always the same: DRAC III information, system information, watchdog information. For more information on these elements, see "Properties."
Every data element is output as a string with the exception of the following:
System information/operating system type
Watchdog info/recovery action
Enumeration values or bitmaps are defined for these elements. When the -A (API) option is included on the command, the enumeration/bit value of the element is listed in the output. Otherwise, the enumeration or bit value is mapped to a string before being output.
The following bullet items define the mapping of values to strings:
System information/operating system type:
A bitmap defines three sub-fields for this value, as defined below:
The sensor option allows the user to specify a single sensor to display. If no -s options is used, all DRAC III sensors are displayed, one per line.
-A
The -A option generates output in API mode. No headers, hex output without leading 0x. The values <units>, <srcType>, <SrtStatus>, and <srcState> are output as hex numbers. The reading (and other values) as displayed as raw values.
-E
The expanded output option is only valid with the -A option, it cannot be used by itself.
-h
The header option displays text prior to dumping the sensor information. There is a lot of information packed on the output line. The header text is somewhat cryptic due to the dense nature, but quite valuable once it is understood.
The text expansions and enum definitions are as follows; the DRAC III sensors are implemented with the corresponding data:
<sensorNum>
<sensorType>
<sensorName>
<srcType>
1
Temperature
TEMP
"Temp"
2
Voltage
BATT VOLT
"Battery"
3
Voltage
EXTPWR VOLT
"Ext Pwr"
4
Voltage
+12PCI VOLT
"PCI Pwr"
5
Voltage
-12PCI VOLT
"PCI Pwr"
6
Voltage
+5PCI VOLT
"PCI Pwr"
7
Voltage
AUXPCI VOLT
"PCI Aux"
<reading> - the 8-bit unsigned raw value. This is converted to actual temp or voltage with the formula: y = 10**R( m*X + B*10**K )
<units> - indicates the units
degrees-C, 1 (used for all temperature sensors)
volts, 4 (used for all voltage sensors)
<sensorType> enums
Temperature, 1
Voltage, 2
<status> enums indicate which region the sensor is in based on the thresholds
unknown, 0 (state at startup before sensors are read)
normal, 1
low-warning, 2 (low-non-critical)
high-warning, 3 (high-non-critical)
low-critical, 4
high-critical, 5
disabled, 6
The following are 8-bit unsigned raw reading values:
<norm> - the normal value of the sensor
<min> - the minimum value of the sensor
<max> - the maximum value of the sensor
<lcThresh> - the lower critical threshold
<lncThresh> - the lower non-critical (warning) threshold
<uncThresh> - the upper non-critical (warning) threshold
<ucThresh> - the upper critical threshold
The following constants apply to the conversion formula:
y = 10**R( m*X + B*10**K )
<m> - slope: 10-bit 2's complement signed
<b> - intercept: 10-bit 2's complement signed
<K> - B-exponent: 4-bit 2's complement signed
<R> - R-exponent (result exponent): 4-bit 2's complement signed
<posHyst> - positive hystersis value
<negHyst> - negative hystersis value
The following table shows the enums and legal values for <srcStatus> and <srcState> as a function of <srcType>:
<srcStatus> and <srcState> are interpreted based on the value of <srcType> in the table below. They indicate the status and state of the source that the sensor is monitoring.
This command sets time, managed system name, operating system name, or operating system type from the managed system to the DRAC III. If no options are entered, all four parameters are set. The -d option allows the user to display the parameters only without actually writing them to the DRAC III firmware. Any combination of options, or no options, may be entered.
Get the "UTC time" from the managed system and set the DRAC III with this time.
-h
Get the "Hostname" from the managed system and write it to the DRAC III. This parameter is available for viewing using the getsysinfo command, and under the object ID interface using config/getconfig as [ifcRacManagedNodeOs]=ifcRacMnOsHostname
-o
Get the "OS Name" from the managed system and write it to the DRAC III. This parameter is available for viewing via the getsysinfo command, and under the object ID interface using config/getconfig as [ifcRacManagedNodeOs]=ifcRacMnOsName
-T
Get the "OS Type" from the managed system and write it to the DRAC III. This parameter is available for viewing via the getsysinfo command, and under the object ID interface using config/getconfig as [ifcRacManagedNodeOs]=ifcRacMnOsOsType.
-d
The Display option allows the user to get the "UTC time," "Hostname," "OS Name," and "OS Type" from the managed system and display it only. No parameters are written to the DRAC III. If the -d option is entered along with other options then those parameters are displayed only.
A message is displayed indicting what the values obtained from the managed system are. And if they are being written to the DRAC III, or displayed only.
The help subcommand lists all of the subcommands that are available under the racadm command along with a one line description. You may also enter a subcommand after help to get the syntax for a specific subcommand.
This command is applicable only to Windows operating systems. When TRUE, a user performing remote console redirection through the DRAC III Web-based interface can disable the local keyboard and mouse. When FALSE, the local keyboard and mouse cannot be disabled.
The fastest method to configure the DRAC III is to use Server Administrator or IT Assistant. If these applications are unavailable, or if you prefer command-line or script configuration, the DRAC III can also be configured using the racadm utility. The racadm utility is installed along with the DRAC III agents on the managed system.
To configure multiple DRAC IIIs to contain the same user configuration settings, you can do either of the following:
Using the racadm utility examples in this section as a guide, create a Windows batch file of racadm commands, and then execute the batch file on each managed system.
Create a DRAC III configuration file as described in "DRAC III Configuration File (racadm.cfg)"; then execute the racadm config subcommand on each managed system using that same configuration file.
The DRAC III allows up to 16 users to be configured into the DRAC III property database. Before manually adding a DRAC III user, you need to know which, if any, users exist. If the DRAC III is new, or the racadm racresetcfg command has been run, then the only user will be "root" with the password "calvin." The racresetcfg subcommand resets the DRAC III back to the original defaults.
NOTICE: Use caution when using this command because all configuration parameters are reset
to the original defaults; any previous changes are lost.
NOTE: Users can be added and deleted over time, so it is very possible that users on a DRAC III
card do not have the same index number as the same user on a different DRAC III.
To find out if a user exists, enter the following command at the command prompt, once for each index of 1 - 16.
racadm getconfig -g cfgUserAdmin -i <index# 1-16>
NOTE: An alternative method to obtain this information would be to enter racadm
getconfig -f <myfile.cfg>, then simply view or edit the myfile.cfg, which will include
all the DRAC III configuration parameters.
Over 20 parameters and object IDs are displayed along with their current values. The two objects of interest are:
# cfgUserAdminIndex=XX
cfgUserAdminUserName=
If the cfgUserAdminUserName has no value, that index number, which is indicated by the cfgUserAdminIndex object, is available for use. If there is a name after the "=," that index is taken by that user name.
NOTE: When you manually add or remove a user with the racadm config subcommand, you
must specify the index number with the -i option. Observe that the cfgUserAdminIndex object
displayed in the example above has a '#' character. Also, if you use the racadm config -f
racadm.cfg command to specify any number of groups/objects to write, the index cannot be
specified. A new user is added to the first available index. This behavior allows more flexibility
in configuring multiple DRAC IIIs with the same settings.
To add a simple user without any alert information, first locate an available user index following the steps in "Locating the Proper User Index." Next, enter the next two command lines with the new user name and password:
A user name "john" with the password of "123456" is created. This user name and password can now be used to log into the Web-based interface. You can verify this using either of the following two commands:
To add a DRAC III user that is able to receive numeric paging, alphanumeric paging, e-mail, and SNMP traps, first locate an available DRAC III user index following the steps in "Locating the Proper User Index." The following example has an available user index at index 2.
You can enter the commands manually, or run a batch file, or build a .cfg file using racadm config -f < >. After doing so, you may want to test each of the alerts.
Enter the command that follows to get a list of the available network properties.
racadm getconfig -g cfgLanNetworking
If you want to use DHCP to obtain an IP address, you can use the command to write the object cfgNicUseDhcp to enable it. You may also enter a static IP address, netmask, and gateway.
The commands provide the same configuration functionality as the option ROM does at boot-up time when prompted to enter <Ctrl-D>. For more information on configuring network properties with the option ROM, see "Configuring the DRAC III Network Settings Using the Option ROM."
The following is an example of the commands that may be entered to configure desired LAN network properties.
The DRAC III allows up to 16 dial-in (PPP) users to be configured. Before manually adding a dial-in user, you need to know which, if any, dial-in users exist. If the DRAC III is new, or the racadm racresetcfg command has been run, no dial-in users exist. Also, there will never be default dial-in users (the only default user and password are "root" and "calvin," which are DRAC III users). The racresetcfg subcommand resets the DRAC III back to the original defaults.
NOTICE: Exercise caution with this command because all configuration parameters are reset
to original defaults; any previous changes are lost.
NOTE: Dial-in users can be added and deleted over time, so it is possible that users on a DRAC
III do not have the same index number as the same user on a different DRAC III.
To find out if a dial-in user exists, enter the following command, once for each index of 1 - 16.
NOTE: An alternative method to obtain this information would be to enter racadm
getconfig -f <myfile.cfg>, then simply view or edit the myfile.cfg, which will include
all the DRAC III configuration parameters.
Five object IDs are displayed along with their current values. The two objects of interest are:
# cfgDialinUsrIndex=XX
cfgDialinUsrPppUserName=
If the cfgDialinUsrPppUserName object has no value, then that index number, which is indicated by the cfgUserAdminIndex object, is available for use. If there is a name after the "=," that index is taken by that user name.
NOTE: When you add or remove a dial-in user with the racadm config subcommand, you must
specify the index number with the -i option. Observe that the cfgDialinUsrIndex object displayed
in the example above has a '#' character. Also, if you use the racadm config -f racadm.cfg
command to specify any number of groups/objects to write, the index cannot be specified. A new
dial-in user is added to the first available index. This behavior allows more flexibility in
configuring multiple DRAC IIIs with the same settings.
To configure the dial-in user database manually. The dial-in user name and password properties have to be set for the dial-in user. You must also set the callback type. If the callback type is 1 (predefined), the callback phone number must be supplied as well. Callback types are: 0=none, 1=pre-specified, 2=user-specified. The <index> must be from 1 to 16, as there are 16 dial-in users supported, and must be the same in each of the configuration commands.
The DRAC III allows up to 16 demand dial-out entries to be configured. Before adding a demand dial-out entry, you need to know which, if any, demand dial-out entries exist. If the DRAC III is new, or the racadm racresetcfg command has been run, no demand dial-out entries exist. The racresetcfg subcommand resets the DRAC III back to factory defaults.
NOTICE: Exercise caution with this command because all configuration parameters are reset
to factory defaults; any previous changes are lost.
NOTE: Demand dial-out entries can be added and deleted over time, so it is possible that entries
on a DRAC III card do not have the same index number as the same entry on a different DRAC
III.
To find out if a demand dial-out entry exists, enter the following command, once for each index of 1 - 16:
NOTE: An alternative method to obtain this information would be to enter racadm
getconfig -f <myfile.cfg>, then simply view or edit the myfile.cfg, which will include
all the DRAC III configuration parameters.
Six parameters or object IDs are displayed along with their current values. The two objects of interest are:
# cfgDemandDialIndex=XX
cfgDemandDialIpAddr=
If the cfgDemandDialIpAddr object has no value then that index number, which is indicated by the cfgDemandDialIndex object, is available for use. If there is an IP address after the "=," that index is already taken. Also, the index "anchor" for the demand dial-out group is not a name, but an IP Address.
NOTE: When you add or remove a demand dial-out entry with the racadm config subcommand,
you must specify the index number with the -i option. Observe that the cfgDemandDialIndex
object displayed in the example above has a '#' character. Also, if you use the racadm config -f
racadm.cfg command to specify any number of groups/objects to write, that the index cannot be
specified. A new demand dial-out entry is added to the first available index. This behavior allows
more flexibility in configuring multiple DRAC IIIs with the same settings.
The following example writes the five objects necessary to add a demand dial-out entry.
The demand dial-out entry remote user name and remote password properties have to be set to match the RAS user name and password. Additionally, the authentication type must be set. Authentication types are: 0=any (including clear text), 1=CHAP, 2=MSCHAP (MSCHAP is not currently supported).
Two IP addresses are needed for dial-in support: a base address, and the base address incremented by one. If the base address ends with either .254 or .255, the base address will be incremented by three or two, respectively.
The base address has a default value of 0.0.0.0. When the base IP address is set to the default, this indicates that the base address will be obtained from cfgDialupDialInDfltIpAddr instead of cfgDialupDialInBaseIpAddr.
The default IP address has a default value of 0.0.0.0. When the default IP address is set to the default, the DRAC III will autogenerate a unique IP address on the 10.0.0.0 network, using the MAC address of the DRAC III NIC.
NOTE: The 10.0.0.0 network has been designated as a "private internet", and cannot be passed
through gateways onto the actual Internet.
This address is unique in the sense that no two DRAC IIIs autogenerate the same IP address. However, it is still possible that the autogenerated address will collide with anther network node on the 10.0.0.0 network if there are network nodes besides DRAC III using the 10.0.0.0 network.
When DHCP is not enabled for dial-in (cfgDialupDialInDhcpEnable is 0), the dial-in base address is obtained from:
cfgDialupDialInBaseIpAddr
OR
cfgDialupDialInDfltIpAddr (if cfgDialupDialInBaseIpAddr has a default value of 0.0.0.0)
NOTE: In this case, the second address required for dial-in is obtained by incrementing the
base address.
When DHCP is enabled for dial-in (cfgDialupDialInDhcpEnable is 1), the two dial-in addresses are obtained from one of the following:
The DHCP server.
The addresses assigned the last time the DHCP server responded (if there is no response from the DHCP server and the prior DHCP lease has not expired).
cfgDialupDialInDfltIpAddr as a base address, and the second address obtained by incrementing the base address (if there are no previous DHCP addresses with unexpired leases and the DHCP server is not responding).
The DRAC III property database is a persistent repository of configuration information that you can modify to achieve specific behavior by the DRAC III firmware. When you use Server Administrator, IT Assistant, or the racadm utility to configure the DRAC III, you are making changes in the property database.
The DRAC III property database is structured as object groups and objects. Objects represent data types called properties (such as integer properties or boolean properties) that have property values. See "DRAC III Property Database Group and Object Definitions," for more information on the property database.
DTMF digits A, B, C, and D. Some countries may prohibit sending of these digits during dialing.
P
Select pulse dialing: pulse dial the numbers that follow until a "T" is encountered. Some countries prevent changing dialing modes after the first digit is dialed
T
Select tone dialing: tone dial the numbers that follow until a "P" is encountered. Some countries prevent changing dialing modes after the first digit is dialed.
!
Flash: the modem will go on-hook for 700ms. Not compatible with all countries.
W
Wait for dial tone: the modem will wait for dial tone before dialing the digits following "W." If dial tone is not detected within 50 seconds, the modem will abort the rest of the sequence, return on-hook, and generate an error message.
@
Wait for silence: the modem will wait for at least 5 seconds of silence in the call progress frequency band before continuing with the next dial string parameter. If the modem does not detect these 5 seconds of silence within 50 seconds, the modem will abort the rest of the sequence, return on-hook, and generate an error message.
&
Wait for credit card dialing tone before continuing with the dial string. If the tone is not detected within 50 seconds, the modem will abort the rest of the sequence, return on-hook, and generate an error message.
,
Dial pause: the modem will pause for two seconds before dialing the digits following the ",".
( )
Ignored: may be used to format the dial string.
-
Ignored: may be used to format the dial string.
All other characters, including <space> are illegal in the property value, and can cause unpredictable results.
The DRAC III alert filter scans the alert enable database properties before it scans the event masks. (An event mask is a bit sequence that specifies information about a DRAC III- or managed-system-generated event, such as the event's origin, type, and severity).
NOTE: Throughout this document, objects are always referred to by group name and object
name, separated by a space.
The DRAC III alert filter operates according to the following general steps:
It scans all of the objects in the alert enable property group.
The alert enable property group ID is cfgUserAdmin. The object IDs are:
cfgUserAdmin cfgUserAdminPageEmailEnable
cfgUserAdmin cfgUserAdminPageAlphaEnable
cfgUserAdmin cfgUserAdminPageNumericEnable
If at least one of these object's property values is TRUE, it scans the event masks in the user table.
It scans the cfgTraps cfgTrapsEnable object. If this object's property value is TRUE, it scans the event masks in the Traps table.
The following subsections describe the event masks for DRAC III-generated events and managed-system-generated events defined in the User table and the Trap table.
The cfgUserAdmin cfgUserAdminAlertFilter {Rac, Sys} EventMask properties are an unsigned 32-bit integer property that holds the filter information for DRAC III-generated events. The bit definitions that apply appear in TableB-2.
The cfgTraps cfgTrapsFilter {Rac, Sys} EventMask properties are an unsigned 32-bit integer property that holds the filter information for managed-system generated events. The following bit definitions in TableB-3 apply.
You can test alerts using four test commands. The racadm command has four subcommands that test the different types of alert interfaces. These object ID sets cause the firmware to execute the subcommand with the option that indicates the test alert type to test. The test message is preset in properties for each test alert type. The four types of alerts are numeric, alphanumeric, e-mail, and trap.
The following subsection describes the command interfaces and the operation of the subcommand for each option.
The contents of the cfgUserAdmin cfgUserAdminPageNumericMessage string are sent following dialing of the cfgUserAdmin cfgUserAdminPageNumericNumber string. Several characters have special meanings. See "Telephone Number Properties."
The special character "S" causes the DRAC III to fill in the severity of the alert:
0 = informational/normal
1 = warning (noncritical)
2 = critical
The special character "E" causes the DRAC III to fill in the event type:
001 = test page (informational/normal)
002 = RAC authentication errors (warning)
003 = lost communication with ESM error (critical)
004 = communication with ESM restored (informational/normal)
005 = detected system power-off (critical)
006 = detected system power-on (informational/normal)
007 = RAC detected that the system watchdog expired (system hang) (critical)
008 = RAC battery charge low (minor)
009 = SEL 80% full
010 = SEL 90% full
011 = SEL 100% full
101 = RAC temperature sensor (informational/warning/critical)
102 = RAC voltage sensor (informational/warning/critical)
201 = System temperature sensor (informational/warning/critical)
202 = System voltage sensor (informational/warning/critical)
203 = System fan sensor (informational/warning/critical)
204 = other system sensor (informational/warning/critical)
The special character "N" causes the DRAC III to fill in the sensor number for a system event.
For DRAC III events, the sensors are numbered as follows:
1 = RAC temp sensor
2 = RAC battery voltage
3 = RAC external power supply voltage
4 = RAC +12 V PCI voltage
5 = RAC –12 V PCI voltage
6 = RAC +5 V PCI voltage
7 = RAC AUX PCI voltage
The special character "I" causes the DRAC III to fill in the IP address of the NIC in dotted-decimal notation, but without the dots.
"999" is prepended to the cfgUserAdmin cfgUserAdminPageNumericMessage object for test pages. The concatenated string is then interpreted as previously described.
The alphanumeric alert contains the following information: message (including test message, if a paging test), event description, date, time, severity, sensor reading, system ID, model, BIOS version, asset tag, service tag, managed system name, operating system type, and operating system name. The following is an example test alphanumeric page:
Subject: Alert from Dell Remote Access Card: 10.35.10.108
The e-mail alert contains the following information: message (including test message, if a paging test), event description, date, time, severity, system ID, model, BIOS version, asset tag, service tag, managed system name, operating system type, and operating system name, and ESM version. The following is an example test e-mail (fields shown are examples only and may not reflect actual observed output for your environment):
Subject: Alert from Dell Remote Access Card: 10.35.10.108
One of the major features of the racadm utility is the ability to configure the DRAC III using a configuration file. The racadm utility parses the DRAC III configuration file, called racadm.cfg, and then sends individual configuration requests to one or more DRAC IIIs.
This method may be used to configure multiple DRAC III database properties. You must first run the racadm utility to query a configured DRAC III for its database properties, which are accessed using their object group IDs and object IDs. The racadm utility creates the racadm.cfg file from the retrieved information. You can then easily configure other cards with the same database information by pushing this file out to the other DRAC IIIs.
NOTE: Some configuration files contain unique DRAC III information (such as static IP
address) that must be modified before configuring other cards.
The following are the general steps for this procedure:
Get the configuration from a DRAC III that contains the appropriate configuration.
Modify the configuration (optional).
Push the configuration to target the DRAC III.
Reset the target DRAC III.
The getconfig –f racadm.cfg subcommand requests the configuration of the DRAC III and generates a
racadm.cfg file (you can choose any name for this file).
Other options for
getconfig enable you to perform such actions as:
Displaying all configuration properties in a group (specified by group name and index).
Displaying all configuration properties for a user by user name.
Including password (other than user password) information in the generated .cfg file.
The config subcommand loads the information into other DRAC IIIs. Other options for
config enable you to perform such actions as:
Removing passwords in the
racadm.cfg file used to configure the card.
Synchronizing the user and password database with Server Administrator.
The initial configuration file, racadm.cfg, is named by the user. In the following example, the configuration file is named
myfile.cfg. To obtain this file, type the following command at the command prompt:
racadm getconfig –f myfile.cfg
NOTICE: Dell recommends that you edit this file with a simple text editor; the racadm utility
uses an ASCII text parser, and any formatting confuses the parser and might corrupt the
racadm database.
The following example describes the IP address of the DRAC III. Remove all unnecessary variable=value pairs. In this case, only the actual variable group's label with "[" and "]" will remain along with the two variable=value entries pertaining to the IP address change.
The file contents are as follows:
#
# Object Group "cfgLanNetworking"
#
[cfgLanNetworking]
cfgNicIpAddress=10.35.10.110
cfgNicGateway=10.35.10.1
This file will be updated as follows:
#
# Object Group "cfgLanNetworking"
#
[cfgLanNetworking]
cfgNicIpAddress=10.35.9.143
# comment, the rest of this line is ignored
cfgNicGateway=10.35.9.1
The command racadm config –f myfile.cfg parses this file and identifies any errors by line number. A correct file will update the proper entries. You may use the same
getconfig command used in the previous example to confirm the update.
This file can be used to download company-wide changes or to configure new systems over the network.
Offers subject to change, not combinable with all other offers. Taxes, shipping, handling and other fees apply. U.S. Dell Home and Home Office new purchases only. Dell reserves the right to cancel orders arising from pricing or other errors.
