RAC Configuration FileDell™ Remote Access Controller Installation and Setup Guide
Using the racadm Utility to Configure a RAC
The racadm utility is a command-line utility for setting up and configuring a RAC. Specifically, you use the racadm utility to set or retrieve object property values in the RAC properties database.
 |
NOTICE: Commands and code samples in this section are RAC-specific. Some commands or samples may not be applicable to your RAC. For example, lines that contain configuration code for modems, dial-in users, or demand dial-out users are specific to 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 RAC firmware, setting a property to a specific value, and reading the configuration of a RAC.
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 Dell 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 PowerEdge 7150 systems, see the Remote Service Card User's Guide on your documentation CD. |
|
NOTE: To limit the stress load on the managed system and the RAC when using the racadm utility, it is important to add one- or two-second "sleep" or "delay" commands between each racadm command. |
A RAC 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 a RAC 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:
|
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 a RAC 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 writes to a RAC.
Be aware of the following important points:
|
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. |
Example:
#
# This would be a comment
[cfgUserAdmin]
cfgUserAdminPageModemInitString=<Modem init # not a comment>
[cfgLanNetworking]
cfgNicIpAddress=143.154.133.121
See the example in the previous bullet.
|
NOTE: The user may create an indexed group manually using the following command: |
racadm config -g <groupName> -o <anchored object> -i <index 1-16> <unique anchor name>
racadm config -g <groupName> -o <objectName> -i <index 1-16> ""
|
NOTE: A NULL string (two " characters [""]) directs a RAC 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>
[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 RAC configuration. This file can be used as an example and as a starting point for your unique .cfg file. |
|
Command |
Definition |
racadm | Command-line status and configuration utility for RACs |
racadm <options> <subcommand> <subcommand_options>
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.
This command has the following debug options.
|
Option |
Description |
0x1 | Standard out messages |
0x2 | Standard error messages |
0x4 | Debug messages |
Example:
racadm -l 0x3 -L log <subcommand [subcommand_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:
Example:
racadm <subcmd> : ERROR:<message>
Example:
racadm <subcmd> : Transport : ERROR : <message>
Example:
racadm <subcmd> : Firmware : ERROR : <message>
The following subsections provide descriptions of subcommands that you can run under the racadm command-line utility.
Command Definition config Configure a RAC getconfig Get RAC configuration data
Synopsis
racadm config [-s -p -c] -f <filename>
racadm config [-s] -g <groupName> -o <objectName> [-i <index>] <Value>
racadm getconfig [-p] -f <filename>
racadm getconfig -g <groupName> [-i <index>]
racadm getconfig -u <username>
racadm getconfig -h
The configuration subcommand allows the user to set RAC 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 a RAC occurs. If the data is different, that RAC object is written with the new value.
This subcommand generates error output upon encountering either of the following:
If no errors are encountered, this subcommand returns an indication of how many configuration objects that were written out of how many total objects were in the .cfg file.
The getconfig subcommand allows the user to retrieve RAC configuration parameters on an individual basis, or all the configuration groups may be retrieved and saved into a file.
This subcommand generates error output upon encountering either of the following:
If no errors are encountered, this subcommand displays the contents of the specified configuration.
Displays all of the configurations parameters (objects) that are contained in the group cfgLanNetworking.
Sets the cfgNicIpAddress configuration parameter (object) to the value 10.35.10.110. This IP address object is contained in the group cfgLanNetworking.
Reads all of the configuration objects, from all of the RAC group configuration parameters and place them in a file called myrac.cfg.
Configures or reconfigures a RAC. The myrac.cfg file may be created from the command specified in the previous example if a RAC 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. |
Displays a list of the available configuration groups on a RAC.
Displays the configuration parameters for the user named root.
|
Command |
Definition |
clearasrscreen | Clear the last crash screen |
racadm clearasrscreen
This command clears the last crash screen that is in memory. It does not clear the persistent copy in the database.
None
None
|
Command |
Definition |
coredump | Display the last RAC core dump |
racadm coredump
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 a RAC—the data remains in the flash memory of the RAC until either:
See the coredumpdelete command for information on deleting this information.
None
Example output:
Last CORE dump: 2001-01-01 23:00:59 GMT - 14:30
Firmware Version: 1.0
Data Access Abort
--------------------------------------------------------------- -------
CPSR = 80000013 (Nzcv if SVC32) SP =013F3F38 LR =01040D80
R0 =0000000D R1 =0000000C R2 =0000003D R3 =00000000 R4 = 00000000
R5 =013F3F6C R6 =00000080 R7 =00000001 R8 =00000010 R9 = 00000001
R10=00000002 R11=010C9DA4 R12=00000000 USP=013F0B5C ULR= 00000000
SSP=013F3F38 SLR=01040D80 SPSR_svc=20000013
PC =01040DF0-01040DF0:
PROBE+>
Example output (for no data available):
FW d_cmdCoreDump: No CORE dump available.
|
Command |
Definition |
coredumpdelete | Delete the core dump stored in a RAC |
racadm coredumpdelete
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.
None
None
|
Command |
Definition |
racreset | Reset a RAC |
racadm racreset <hard | soft | graceful> [delay]
The racreset subcommand issues a reset to a RAC. 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 RAC log.
|
NOTICE: You must reboot your system after performing a hard reset of a RAC as described in the following table. |
None
Start a RAC soft reset sequence in 1 second.
Start a RAC soft reset sequence after 60 seconds.
|
Command |
Definition |
racdump | Dump status and general RAC information |
racadm racdump
The racdump subcommand provides a single command to get a dump, status, and general RAC board information with a single command.
The following commands are executed as a result of the single racdump subcommand:
None
The output of the individual commands are displayed.
|
Command |
Definition |
racadm racresetcfg | Resets all database configuration parameters to default values; equivalent to a soft reset |
racadm racresetcfg
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, a RAC 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 SNMP. |
None
None
|
Command |
Definition |
fwupdate | Update the firmware on a RAC |
racadm fwupdate -u [-w] [-D]
racadm fwupdate -s
racadm fwupdate -g [-u ] [-w][-D] [-a <IP address>]
[-d <path>]
racadm fwupdate -c
racadm fwupdate -p -d <path> [-u] [-w] [-D]
The fwupdate subcommand allows the caller to update the firmware on a RAC. The user may:
|
Option |
Description |
-u | The -u, or 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. This means that after the firmware update file has been loaded, the update process is started within the same call. At the end of the update, a RAC performs a soft reset. |
-w | The -w, or 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 -s, or status, option returns the current status of your progress 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 -g, or 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 or -d 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 option specifies the IP address of the TFTP server. |
-f | The -f, or filename, option is used for backward compatibility and debug only. It allows the user to specify the exact name of the firmware update file to be loadad. This option is normally used with the -g option to load the file from a TFTP server. It is recommended that the -d option be used, not the -f option. |
-d | The -d, or directory option, specifies the directory path where the firmware update file resides. The actual filename of the update file is not entered by the user. The -d option determines the correct firmware update filename. If the -g option is specified, the RAC loads the update file from the TFTP server. The user has previously set up the root path on the TFTP server. The -d option specifies where the update file is located relative to the root path. If used with the -p option, the -d option specifies the location of the firmware update file on the managed system, which is then transferred to the RAC. |
-c | The -c, or 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. |
-D | After the update is complete, a RAC is reset. Upon boot, a call is made to reset all firmware configuration parameters to their defaults. For more information, see "racresetcfg." |
-p | The -p, or put, option is used to FTP the firmware update file from the managed system to a RAC. The -f option that specifies the filename of the update image must be named firmimg.bin. The update file is FTP'd into a RAC. A checksum then performed on the newly loaded image. 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. |
Displays a message indicating the operation being performed.
In this example, the -g option indicates that the firmware gets the firmware update file from the TFTP server location specified by the -d option. The path specified by the -d option is a continuation from the root path that the user has set up in the TFTP server. The IP address of the TFTP server is specified by the -a option. The update file is loaded into the RAC RAMdisk. No update occurs because the -u option is not present.
This option reads the current status of firmware update.
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.
In this example, the -p option FTPs the update file to the RAC. The -d option directs the command to locate the correct update file for the type of RAC present. The -u option starts the update process when the file is finished loading. If no path is specified after the -d option, the update file needs to be present in the same directory as the racadm command.
|
Command |
Definition |
getssninfo | Retrieve session information for one or more currently active or pending sessions from the Session Manager's session table |
racadm getssninfo [-A] [-u <username> | *]
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:
None.
Session table status:
4 FREE
0 PRELIMINARY
0 UNVALIDATED
1 VALID
0 INVALID
SessionID -------------- | User ----------- | Status ----------- | IP Address ---------------- | Login Date/Time -------------------- | Con ------- |
0x10419A09 | ADMIN | VALID | 143.166.154.86 | 2001-01-01 23:00:59 GMT - 14:30 | N |
4 0 0 1 0
0x10419A09 ADMIN VALID 143.166.154.86 "2001-01-01 23:00:59 GMT - 14:30" N
0x10419A09 ADMIN VALID 143.166.154.86 "2001-01-01 23:00:59 GMT - 14:30" N
|
Command |
Definition |
getsysinfo | Display RAC information, system information, and watchdog status information. |
racadm getsysinfo [-d] [-s] [-w] [-A]
The getsysinfo command returns information about a RAC, system, or watchdog status, depending on the command options. The order of data on output is always the same: RAC information, system information, watchdog information.
If no -d, -s, or -w option is specified, then these three options are used as defaults.
Every data element is output as a string with the exception of the following:
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:
A bitmap defines three subfields for this value, as follows:
0 = 32 bit, 1 = 64 bit
000000 = Windows, 000001 = Linux, 000010 = NetWare®
For Red Hat Linux, will be 0; for Microsoft® Windows®, will be 00000000 = Windows NT or 00000001 = Windows 2000; for Novell® NetWare, will be 0
An enumeration defines the meaning of this value:
"System Info:" "123456" "Dell PowerEdge 7150" "A00" "EF23VQ- 0023" \
"05-10-54" 0 "ssdev16" "Windows NT Terminal Server, Version 5.4" \ "1.3 Dell Computer Corp"
"Watchdog Info:" 1 544 33234
System Information:
System ID = 123456
System Model = Dell PowerEdge 7150
BIOS Version = A00
Asset Tag = EF23VQ-0023
Service Tag = 05-10-54
OS Type = NT
Hostname = ssdev16
OS name = Windows NT Terminal Server, Version 5.4
ESM Version = 1.3 Dell Computer Corp
Watchdog Information:
Recovery Action = Hard reset
Present countdown value = 544
Initial countdown value = 33234
|
Command |
Definition |
getsensors | Get information on the RAC sensors |
racadm getsensors
racadm getsensors -s <sensorNum>
racadm getsensors [-A] [-E] [-s <sensorNum>] [-h]
The getsensor command dumps information about the sensors that are present on a RAC itself, not in the system, or on the BMC/ESM.
Without the -A option:
getsensors [-s <sensorNum>]
This command outputs the following on one line:
<sensorNum> <sensorType> <"sensorName"> <reading> <units> <status> <srcType> <srcStatus> <srcState>
Where <units> and <sensorType> are expanded as strings, and the reading is given as a converted value (in volts or degrees C).
With the -A option:
getsensors -A -s 1
This command outputs the following on one line:
<sensorNum> <sensorType> <"sensorName"> <reading> <units> <status> <srcType> <srcStatus> <srcState>
No headers, hexadecimal output without leading 0x.
With the -E option we get the -A output, plus the following, on one line:
<norm> <min> <max> <lcThresh> <lncThresh> <uncThresh> <ucThresh> <m> <b> <K> <R> <posHyst> <negHyst>
The output translation follows the formula:
y = 10**R(m*X + B*10**K)
The text expansions and enum definitions are as follows; the RAC sensors are implemented with the corresponding data:
The following are 8-bit unsigned raw reading values:
The following constants apply to the conversion formula:
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.
1 Temperature RAC III TEMP 37 degrees-C High-critical Temperature
2 Voltage RAC III BATT VOLT c6 Voltage High-warning Battery 100% Charged
3 Voltage RAC III EXTPWR VOLT eb Voltage Normal Ext pwr ON Connected
4 Voltage RAC III +12PCI VOLT bf Voltage Disabled PCI pwr Unk
5 Voltage RAC III -12PCI VOLT ae Voltage Disabled PCI pwr Unk
6 Voltage RAC III +5PCI VOLT c2 Voltage Disabled PCI pwr Unk
7 Voltage RAC III AUXPCI VOLT 00 Voltage Disabled PCI pwr Unk
2 Voltage RAC III BATT VOLT c6 Voltage High-warning Battery 100% Charged
5 2 "RAC -12PCI VOLT" ae 4 6 1 00 0
1 1 "RAC TEMP " 37 1 5 0 00 0 19 c9 7d 00 14 31 37 3ff 000 0 0 3 3
2 2 "RAC BATT VOLT " c6 4 3 3 64 3 a0 69 b1 5a 7e c6 db 313 000 0 4 5 5
3 2 "RAC EXTPWR VOLT" eb 4 1 4 01 1 e6 c0 ff 98 df ee ff 2fc 000 0 4 4 4
4 2 "RAC +12PCI VOLT" bf 4 6 1 00 0 c0 b8 c8 b3 b8 c8 cc 18f 000 0 4 3 3
5 2 "RAC -12PCI VOLT" ae 4 6 1 00 0 ae aa b2 a8 aa b2 b4 3bb 000 d 4 2 2
6 2 "RAC +5PCI VOLT " c2 4 6 1 00 0 c0 b6 c9 ad b6 c9 d3 2fc 000 0 4 4 4
7 2 "RAC AUXPCI VOLT" 00 4 6 1 00 0 bf ae d1 a2 ae d1 dc 354 000 0 4 6 6
|
Command |
Definition |
setrac | Set RAC parameters from the managed system |
racadm setrac [-t -h -o -T -d]
This command sets time, managed system name, operating system name, or operating system type from the managed system to a RAC. 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 RAC firmware. Any combination of options, or no options, may be entered.
A message is displayed indicting the values obtained from the managed system, and if they are being written to a RAC or only displayed.
All the parameter values are displayed only.
The UTC time and managed system name are taken from the managed system and written to a RAC.
|
Command |
Definition |
syncvncpassword | Set the managed system VNC server password from a RAC |
racadm syncvncpassword
The syncvncpassword subcommand reads the VNC password from the RAC firmware and sets the managed system's RAC VNC server to the same value.
None
None
|
Command |
Definition |
help | List all of the subcommands available to use with racadm and provide a short description for each |
racadm help
racadm help <subcommand>
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.
None
racadm help displays a complete list of subcommands.
racadm help <subcommand> displays usage information for the specified subcommand only.
|
Command |
Definition |
allowEnDisRem | Allows enabling or disabling of the local console. |
racadm allowEnDisRem <TRUE | FALSE>
This command is applicable only to Windows operating systems. When TRUE, a user performing console redirection through the RAC Web-based remote access interface can disable the local keyboard and mouse at the managed system. When FALSE, the local keyboard and mouse cannot be disabled.
None
None
The commands in this subsection are used to test the alert functions of a RAC.
|
Command |
Description |
testemail | Test an e-mail alert |
racadm testemail <-i <index> | -u <username>>
The testemail subcommand forces a RAC to send an e-mail over the RAC NIC.
|
Option |
Description |
-u | The user option specifies the user to send the page to. The necessary properties must be setup to correctly page out. |
-i | Used to specify the index of the user. |
None
|
Command |
Description |
testtrap | Test an SNMP trap |
racadm testtrap [-i <index>]
The testtrap subcommand forces a RAC to send an SNMP trap over the RAC NIC.
|
Option |
Description |
-u | The user option specifies the user to send the page to. The necessary properties must be setup to correctly page out. |
-i | Used to specify the index of the user. |
None
The fastest method to configure a RAC is to use Server Administrator. If Server Administrator is unavailable, or if you prefer command-line or script configuration, a RAC can also be configured using the racadm utility. The racadm utility is installed along with the RAC agents on the managed system.
To configure multiple RACs to contain the same user configuration settings, you can do either of the following:
A RAC allows up to 16 users to be configured into the RAC property database. Before manually adding a RAC user, you need to know which, if any, users exist. If a RAC is new, or the racadm racresetcfg command has been run, then the only user is "root" with the password "calvin." The racresetcfg subcommand resets a RAC 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 RAC do not have the same index number as the same user on a different RAC. |
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>
|
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 file, which includes all RAC 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 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 RACs 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 following two command lines with the new user name and password:
racadm config -g cfgUserAdmin -o cfgUserAdminUserName -i <index> <username>
racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i <index> <password>
Example:
racadm config -g cfgUserAdmin -o cfgUserAdminUserName -i 2 john
racadm config -g cfgUserAdmin -o cfgUserAdminUserName -i 2 123456
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 remote access interface. You can verify this using either of the following two commands:
racadm getconfig -u john
racadm getconfig -g cfgUserAdmin -i 2
All users must be deleted manually. You cannot delete users by specifying them in a racadm.cfg file
To delete the user "john" created above, enter the following command line:
racadm config -g cfgUserAdmin -o cfgUserAdminUserName -i <index> ""
A NULL string (two " characters[""]) indicates to a RAC to delete the index for the specified group.
To add a RAC user that is able to receive e-mail and SNMP traps, first locate an available RAC user index following the steps in "Locating the Proper User Index." The following example has an available user index at index 2.
|
NOTE: See "RAC Property Database Group and Object Definitions," for details on each specific object. |
racadm config -g cfgUserAdmin -o cfgUserAdminUserName -i 2 john
racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i 2 123456
racadm config -g cfgUserAdmin -o cfgUserAdminPageAlphaNumber -i 2 9,18002506325
racadm config -g cfgUserAdmin -o cfgUserAdminPageAlphaPagerId - i 2 415-0722
racadm config -g cfgUserAdmin -o cfgUserAdminPageAlphaBaudRate -i 2 0x4B0
racadm config -g cfgUserAdmin -o cfgUserAdminPageAlphaProtocol -i 2 8N1
racadm config -g cfgUserAdmin -o cfgUserAdminPageAlphaCustomMsg -i 2 "RAC Alpha Page test"
racadm config -g cfgUserAdmin -o cfgUserAdminPageAlphaEnable -i 2 1
racadm config -g cfgUserAdmin -o cfgUserAdminPageNumericNumber -i 2 9,18774150722
racadm config -g cfgUserAdmin -o cfgUserAdminPageNumericMessage -i 2 "111-222-3333"
racadm config -g cfgUserAdmin -o cfgUserAdminPageNumericEnable -i 2 1
racadm config -g cfgUserAdmin -o cfgUserAdmimPageModemInitString -i 2 AT+GCI=B5
racadm config -g cfgUserAdmin -o cfgUserAdminEmailAddress -i 2 "<email address>"
racadm config -g cfgUserAdmin -o cfgUserAdminEmailCustomMsg -i 2 "RAC Alert Email Test"
racadm config -g cfgUserAdmin -o cfgUserAdminEmailEnable -i 2 1
racadm config -g cfgUserAdmin -o cfgUserAdminAlertFilterRacEventMask -i 2 0x0
racadm config -g cfgUserAdmin -o cfgUserAdminAlertFilterSysEventMask -i 2 0x0
racadm config -g cfgTraps -o cfgTrapsSnmpCommunity -i 2 public
racadm config -g cfgTraps -o cfgTrapsEnable -i 2 1
racadm config -g cfgTraps -o cfgTrapsFilterRacEventMask -i 2 0x0
racadm config -g cfgTraps -o cfgTrapsFilterSysEventMask -i 2 0x0
racadm config -g cfgTraps -o cfgTrapsDestIpAddr -i 2 <SNMP trap destination>
racadm config -g cfgDialupNetworking -o cfgDialupDialType 0x1
racadm config -g cfgOobSnmp -o cfgOobSnmpTrapsEnable 1
racadm config -g cfgRemoteHosts -o cfgRhostsSmtpServerIpAddr 143.166.224.254
racadm racreset
You can enter the commands manually, or run a batch file, or build a .cfg file using racadm config -f racadm.cfg. After doing so, you may want to test each of the alerts.
E-mail alerting is enabled by the command that follows. A "0" disables this feature; a "1" enables it.
racadm config -g cfgUserAdmin -o cfgUserAdminEmailEnable -i 2 1
racadm testemail -i 2
SNMP traps are enabled by the command that follows. A "0" disables this feature; a "1" enables it.
racadm config -g cfgTraps -o cfgTrapsEnable -i 2 1
racadm testtrap -i 2
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 RAC Network Properties."
The following is an example of the commands that may be entered to configure desired LAN network properties.
racadm config -g cfgLanNetworking -o cfgNicEnable 1
racadm config -g cfgLanNetworking -o cfgNicIpAddress 192.168.20.1
racadm config -g cfgLanNetworking -o cfgNicNetmask 255.255.255.0
racadm config -g cfgLanNetworking -o cfgNicGateway 192.168.20.1
racadm config -g cfgLanNetworking -o cfgNicUseDhcp 0
You must reset a RAC using the following command before the new configuration parameters will take effect:
racadm racreset
|
NOTE: If cfgNicEnable is set to 0, the RAC LAN is disabled even if DHCP is enabled. |
A RAC 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 a RAC 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 RAC users). The racresetcfg subcommand resets a RAC 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 RAC do not have the same index number as the same user on a different RAC. |
To find out if a dial-in user exists, enter the following command, once for each index of 1 - 16.
racadm getconfig -p -g cfgDialinUsers -i <index>
|
NOTE: An alternative method to obtain this information would be to enter racadm getconfig -f <myfile.cfg>, then simply view or edit myfile.cfg, which will include all RAC 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 RACs 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.
racadm config -g cfgDialinUsers -o cfgDialinUsrPppUserName -i <index> <username>
racadm config -g cfgDialinUsers -o cfgDialinUsrPppUserPassword -i <index> <password>
racadm config -g cfgDialinUsers -o cfgDialinUsrCallbackType -i <index> <callback type>
racadm config -g cfgDialinUsers -o cfgDialinUsrCallbackNumber - i <index> <phone number>
Here is an example configuring dial-in user number 1, with a predefined callback number.
racadm config -g cfgDialinUsers -o cfgDialinUsrPppUserName -i 1 pppaccount
racadm config -g cfgDialinUsers -o cfgDialinUsrPppUserPassword -i 1 pppaccount
racadm config -g cfgDialinUsers -o cfgDialinUsrCallbackType -i 1 0x1
racadm config -g cfgDialinUsers -o cfgDialinUsrCallbackNumber - i 1 5552222
A RAC 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 a RAC is new, or the racadm racresetcfg command has been run, no demand dial-out entries exist. The racresetcfg subcommand resets a RAC 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 n RAC do not have the same index number as the same entry on a different RAC. |
To find out if a demand dial-out entry exists, enter the following command, once for each index of 1 - 16:
racadm getconfig -p -g cfgDemandDial -i <index>
|
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 RAC 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 RACs 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).
racadm config -g cfgDemandDial -i <index> -o cfgDemandDialIpAddr <destination IP address>
racadm config -g cfgDemandDial -i <index> -o cfgDemandDialPhoneNumber <RAS phone number>
racadm config -g cfgDemandDial -i <index> -o cfgDemandDialPppUserName <RAS username>
racadm config -g cfgDemandDial -i <index> -o cfgDemandDialPppPassword <RAS password>
racadm config -g cfgDemandDial -i <index> -o cfgAuthType <authentication type>
Here is an example for configuring demand dial-out destination number 1, with CHAP authentication.
racadm config -g cfgDemandDial -i 1 -o cfgDemandDialIpAddr 143.166.154.1
racadm config -g cfgDemandDial -i 1 -o cfgDemandDialPhoneNumber 555-1212
racadm config -g cfgDemandDial -i 1 -o cfgDemandDialPppUserName pppaccount
racadm config -g cfgDemandDial -i 1 -o cfgDemandDialPppPassword pppaccount
racadm config -g cfgDemandDial -i 1 -o cfgAuthType 2
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, a RAC autogenerates a unique IP address on the 10.0.0.0 network using the MAC address of the RAC 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 RACs autogenerate the same IP address. However, it is still possible that the autogenerated address will collide with another network node on the 10.0.0.0 network if there are network nodes besides a RAC 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:
OR
|
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 following example specifies the necessary objects/properties to configure a RAC for PPP communication. See "RAC Property Database Group and Object Definitions" for information on the property database.
racadm config -g cfgDialupNetworking -0 cfgDialupDialInEnable 1
racadm config -g cfgDialupNetworking -0 cfgDialupDialOutEnable 1
racadm config -g cfgDialupNetworking -0 cfgDialupDialInDhcpEnable 0
racadm config -g cfgDialupNetworking -0 cfgDialupDialInBaseIpAddr <IP Address>
racadm config -g cfgDialupNetworking -0 cfgDialupDialInDfltIpAddr <IP Address>
racadm config -g cfgDialupNetworking -0 cfgDialupDiIdleTimeout 0x3c
racadm config -g cfgDialupNetworking -0 cfgDialupDiMaxConnectTime 0x0
racadm config -g cfgDialupNetworking -0 cfgDialupDialType 0x1
racadm config -g cfgDialupNetworking -0 cfgDialupModemInitString AT+GCI=B5
racadm config -g cfgDialupNetworking -0 cfgDialupModemBaudRate 0x9600
racadm config -g cfgDialupNetworking -0 cfgDialupModemPort 0x8
racadm config -g cfgDialupNetworking -0 cfgDialupDialInAuthType 0x1
racadm config -g cfgDialupNetworking -0 cfgDialupDialOutModemConnectTimeout 0x1e
racadm config -g cfgRacTuning -0 cfgRacTuneDialOutIdleTime 0x28
racadm config -g cfgRacTuning -0 cfgRacTuneDialOutMaxConnectTime 0x0
The RAC property database is a persistent repository of configuration information that you can modify to achieve specific behavior by the RAC firmware. When you use Server Administrator, IT Assistant, or the racadm utility to configure a RAC, you are making changes in the property database.
The RAC 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 "RAC Property Database Group and Object Definitions" for more information on the property database.
The following sections define the user database property members and their default values.
The properties that contain telephone numbers consist of a character string with the characters, as shown in the following table:
All other characters, including <space> are illegal in the property value, and can cause unpredictable results.
The RAC 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 RAC- 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 RAC alert filter operates according to the following general steps:
The alert enable property group ID is cfgUserAdmin. The object IDs are:
If at least one of these object's property values is TRUE, it scans the event masks in the User table.
The following subsections describe the event masks for RAC-generated events and managed-system-generated events defined in the User table and the Trap table.
The cfgUserAdmin cfgUserdminAlertFilter {Rac, Sys} EventMask properties are an unsigned 32-bit integer property that holds the filter information for RAC-generated events. The bit definitions in the following table apply:
where RAC PCI Volt sensors provides the filter mask for the following RAC sensors:
where <senMask> has the following bit definitions:
where <bmcMask> has the following bit definitions:
where <miscMask> has the following bit definitions:
Examples:
the event mask property value to use is 0x02244444. The following is the command to set this property value:
racadm -g cfgUserAdmin -o cfgUserAdminAlertFilterRacEventMask -i1 0x2244444
the even mask property value to use is 0x00064444. The following is the command to set this property value:
racadm -g cfgTraps -o cfgTrapsFilterSysEventMask -i1 0x00064444
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 bit definitions in the following table apply:
where <senMask> has the following bit definitions:
where <statMask> has the following bit definitions:
The alert filter property group ID is cfgUserAdmin. The object IDs are shown in the following table:
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.
Synopsis
racadm testnumpage –n –i <index>
racadm testnumpage –n –u <username>
Alert Data Definitions
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 a RAC to fill in the severity of the alert:
0 = informational/normal
1 = warning (noncritical)
2 = critical
The special character "E" causes a RAC 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 = Hardware log 80% full
010 = Hardware log 90% full
011 = Hardware log 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 a RAC to fill in the sensor number for a system event.
For RAC 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 RAC 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.
Synopsis
racadm testalphapage –a –i <index>
racadm testalphapage –a –u <username>
Alert Data Definitions
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
Message: TEST PAGE
Hostname:53ewy
Event: Email paging test to user 1
Date: 06-jun-2001
Time: 00:01:37
Severity: Info/Normal
Synopsis
racadm testemail –e –i <index>
racadm testemail –e –u <username>
Alert Data Definitions
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
Message: TEST PAGE
Event: Email paging test to user 1
Date: 06-jun-2001
Time: 00:01:37
Severity: Info/Normal
System ID: Bbn
Model: Dell PowerEdge 7150
BIOS version: A00
Asset tag: 181676
Service tag: 6X713
Hostname: P2-750-08
OS Type: 64-bit Linux
OS Name: Linux 7.1 for the Itanium Processor
ESM Version: 1.3 Dell Computer Corp
Synopsis
racadm testtrap –t –i <trap index>
Alert Data Definitions
The "alertMessage" string (up to 1 KB) provides the specific information describing the cause and specific source of the event, which includes:
For more information, see the Server Administrator SNMP Reference Guide.
One of the major features of the racadm utility is the ability to configure a RAC using a configuration file. The racadm utility parses a RAC configuration file, called racadm.cfg, and then sends individual configuration requests to one or more RACs.
This method may be used to configure multiple RAC database properties. You must first run the racadm utility to query a configured RAC 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 RACs.
|
NOTE: Some configuration files contain unique RAC information (such as static IP address) that must be modified before configuring other cards. |
The following are the general steps for this procedure:
The getconfig –f racadm.cfg subcommand requests the configuration of a RAC 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:
The config subcommand loads the information into other RACs. Other options for config enable you to perform such actions as:
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 a RAC. Remove all unnecessary <variable>=value entries. 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.