The DRAC III property database is populated with objects organized into object groups. The groups and objects that the property database supports as group and object identifiers (IDs) are listed in this section. (That is, the property database allows access to the object groups and object data through these IDs). The following definitions specify object data and indicate whether the database object is readable, writable, or both. This information is used by the racadm utility and Dell OpenManage Server Administrator to send and retrieve data to and from the DRAC III property database.
The following subsections describe the groups and their constituent objects.
This group contains parameters to configure the DRAC III NIC interface on the DRAC III.
One instance of the group is allowed. All objects in this group require a DRAC III reset before they become active. The following subsections describe the objects in this group.
This group contains parameters to configure the capabilities of the DRAC III dial-in and dial-out (demand dial).
One instance of the group is allowed. All objects in this group require a DRAC III reset before they become active. The following subsections describe the objects in this group.
0=Enable, 1=Disable. Get the IP address from the DHCP server to becomes the PPP IP address(es). Depending on the NIC configuration either 1 or 2 DHCP addresses will be used. (DRAC III is the client.)
Static IP base address for PPP. When static addresses are enabled two IP addresses are used. The first is the base, and the second is base+1. When the base IP address is 0.0.0.0, cfgDialupDialInDfltIpAddr is used instead.
Statically configure the IP base address for PPP. Used when either cfgDialupDialInBaseIpAddr is 0, or DHCP fails to obtain IP addresses from the DHCP server (only when DHCP is enabled using cfgDialupDialInDhcpEnable). When 0.0.0.0 a unique address on the 10.0.0.0 network is autogenerated.
The path name pointing to the remote floppy boot image. If this is a file name only, the path needs to be specified in the TFTP server, or the entire path can be specified here.
NOTE: The server may still require you to specify the drive, such as C drive.
The path name pointing to the firmware update binary file. If this is a file name only, then the path needs to be specified in the TFTP server. Otherwise, the entire path can be specified here.
NOTE: The server may still require you to specify the drive, such as C drive.
The name of the user for this index. The user index is created by writing a string into this name field, if the index is empty. Writing a "" string deletes the user at that index. You cannot change the name. You must delete, and recreate.
NOTE: This command is the "anchor" for this indexed group.
A string of digits consisting of the following, 0-9, SENI. In the numeric message, S will be replaced by the decimal value of the message severity. The E is replaced by the three-decimal digit event number. The N is replaced by the two-decimal digit sensor number. The I is replaced by the IP address of the DRAC III (dotted-decimal notation with the dots deleted).
NOTICE: It is possible to overflow the number of digits that a numeric pager can handle.
Therefore, you must first determine the maximum number of digits handled by the paging
service and equipment in use.
This group contains parameters to configure the delivery of SNMP traps.
Sixteen instances of this group are allowed, which represent sixteen unique trap destinations. The following subsections describe the objects in this group.
This group contains parameters to configure dial-out capabilities of the DRAC III.
Sixteen instances of the group are allowed, which represent sixteen dial out destinations. The telephone numbers need not be unique among each index. However, the IP address must be unique; which means multiple IP addresses may use the same telephone number. All objects in this group require a DRAC III reset before they become active. The following subsections describe the objects in this group.
This is the destination IP address. Note, that it may not be the IP address of the machine that responds to the telephone number. However the system that responds to the telephone number must be able to route to the IP address.
NOTE: This object is the "anchor" for this indexed group.
The telephone number of a system that is able to route packets to the IP address set in cfgDemandDialIpAddress. See TableB-1 for valid telephone number characters.
This group contains parameters to configure the dial in PPP authentication capability of the DRAC III.
Sixteen instances of the group are allowed, where each index represents a single PPP dial in user. All objects in this group require a DRAC III reset to become active. The following subsections describe the objects in this group.
This group contains parameters to configure the number of sessions that can connect to the DRAC III.
One instance of the group is allowed. All objects in this group require a DRAC III reset before they become active. The following subsections describe the objects in this group.
The maximum number of simultaneous console redirect sessions that are allowed at one time from the DRAC III Web-based user interface. (Enter hexadecimal values.)
The group contains parameters to tune the DRAC III network configuration.
One instance of the group is allowed. All objects in this group require a DRAC III reset before they become active. The following subsections describe the objects in this group.
The racadm utility may be used to modify the network tuning properties of the DRAC III. It is also possible to use the racadm.cfg file to modify these properties (similar to the manner in which .ini files are used).
NOTICE: Although these parameters can be configured, it is recommended that you not use any
other settings than those detailed here. Other settings may adversely effect the DRAC III's ability
to communicate with other network nodes.
Following the modification of the network tuning, the DRAC III must be reset for the new tuning values to take effect. After the DRAC III has been reset, it should be available for use in a normal or satellite network configuration.
The group contains parameters to configure the SNMP agent and trap capabilities of the DRAC III.
One instance of the group is allowed. All objects require a DRAC III reset before they become active. The following subsections describe the objects in this group.
The port connection from the browser to the firmware console redirection server. This object requires a DRAC III reset before it becomes active. (Enter hexadecimal values.)
0=infinite, otherwise when line is idle for this many seconds, the line is disconnected. This object requires a DRAC III reset before it becomes active. (Enter hexadecimal values.)
0=infinite, otherwise maximum time in seconds that the link will stay connected before the connection is terminated. This object requires a DRAC III reset before it becomes active. (Enter hexadecimal values.)
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.