Back to Contents Page

Advanced Configuration of the DRAC 5

Dell™ Remote Access Controller 5 Firmware Version 1.40 User's Guide

Before You Begin   Configuring DRAC 5 Properties   Configuring the DRAC 5 Using the Web User Interface   Enabling and Configuring the Managed System to Use a Serial or Telnet Console   Using a Serial or Telnet Console   Configuring Serial and Terminal Modes   Connecting to the Managed System Through the Local Serial Port or Telnet       Management Station (Client System)   Connecting the DB-9 or Null Modem Cable for the Serial Console   Configuring the Management Station Terminal Emulation Software   Using a Serial or Telnet Console

Using the Secure Shell (SSH)   Configuring the DRAC 5 Network Settings   Accessing the DRAC 5 Through a Network   Configuring the DRAC 5 NIC   Using RACADM Remotely   RACADM Synopsis   Enabling and Disabling the racadm Remote Capability   Configuring Multiple DRAC 5 Cards   Frequently Asked Questions

This section provides information about advanced DRAC 5 configuration and is recommended for users with advanced knowledge of systems management and who want to customize the DRAC environment to suit their specific needs.

Before You Begin

You should have completed the basic installation and setup of your DRAC 5 hardware and software. See "Basic Installation of the DRAC 5" for more information.

Configuring DRAC 5 Properties

You can configure the DRAC 5 properties (network, users, and so on) by using either the Web-based interface or the RACADM.

The DRAC 5 provides a Web-based interface and RACADM (a command-line interface) that enables you to configure the DRAC 5 properties and users, perform remote management tasks, and troubleshoot a remote (managed) system for problems. For everyday systems management, use the DRAC 5 Web-based interface. This chapter provides information about how to perform common systems management tasks with the DRAC 5 Web-based interface and provides links to related information.

All Web-based interface configuration tasks can also be performed with RACADM.

Configuring the DRAC 5 Using the Web User Interface

See your DRAC 5 online help for context sensitive information about each Web-based interface page.

Accessing the Web-Based Interface

To access the DRAC 5 Web-based interface:

1. Open a supported Web browser window. 
   
   

For a list of supported Web browsers, see the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com.

1. In the Address field, type the following and press <Enter>: 
   
   

https://<IP address>

If the default HTTPS port number (port 443) has been changed, type:

https://<IP address>:<port number>

where IP address is the IP address for the DRAC 5 and port number is the HTTPS port number.

The DRAC 5 Log in window appears.

NOTE: When you use Internet Explorer version 6 SP2 or version 7 to log into the DRAC 5 Web GUI and the client is on a private network, but without access to the Internet, you may experience a delay of up to 30 seconds. To resolve this issue:

1. Disable the phishing filter.

https://phishingfilter.microsoft.com/faq.aspx.

2. Disable CRL fetching:

a. Click Tools→ Options→ Advanced tab→ Security.

b. Deselect Check for publisher's certificate revocation.

Logging In

You can log in either as a DRAC 5 user or as a Microsoft® Active Directory® user. The default user name and password are root and calvin, respectively.

Before you log in to the DRAC 5, verify that you have Log In to DRAC 5 permission. Speak to your organization's DRAC or network administrator to confirm your access privileges.

To log in:

1. In the User Name field, type one of the following: 
   
   
   • Your DRAC 5 user name.
     
     

For example, <username>

The DRAC 5 user name for local users is case sensitive

• • Your Active Directory user name.
    
    

For example, <domain><username>, <domain>/<username>, or <user>@<domain>.

Examples of an Active Directory user name are: dell.comjohn_doe or john_doe@dell.com.

The Active Directory user name is not case sensitive.

1. In the Password field, type your DRAC 5 user password or Active Directory user password. 
   
   

This field is case sensitive.

1. Click OK or press <Enter>. 
   
   

Logging Out

1. In the upper-right corner of the DRAC 5 Web-based interface window, click Log Out to close the session. 
   
   
2. Close the browser window. 
   
   

NOTE: The Log Out button does not appear until you log in.

NOTE: Closing the browser without gracefully logging out causes the session to remain open until it times out. It is strongly recommended that you click the logout button to end the session; otherwise, the session remains active until the session timeout is reached.

NOTE: Closing the DRAC 5 Web-based interface within Microsoft Internet Explorer using the close button ("x") at the top right corner of the window may generate an application error. To fix this issue, download the latest Cumulative Security Update for Internet Explorer from the Microsoft Support website, at support.microsoft.com.

Enabling and Configuring the Managed System to Use a Serial or Telnet Console

The following subsections provide information about how to enable and configure a serial/telnet/ssh console on the managed system.

Using the connect com2 Serial Command

When using the connect com2 serial command, ensure that the following are configured properly:

• The Serial Communication→ Serial Port setting in the BIOS Setup program.
  
  
• The DRAC configuration settings.
  
  

When a telnet session is established to the DRAC 5 and these settings are incorrect, connect com2 may display a blank screen.

Configuring the BIOS Setup Program for a Serial Connection on the Managed System

Perform the following steps to configure your BIOS Setup program to redirect output to a serial port.

NOTE: You must configure the System Setup program in conjunction with the connect com2 command.

1. Turn on or restart your system. 
   
   
2. Press <F2> immediately after you see the following message: 
   
   

<F2> = System Setup

1. Scroll down and select Serial Communication by pressing <Enter>. 
   
   
2. Set the Serial Communication screen as follows: 
   
   

External Serial Connector — Remote Access Device

Redirection After Boot — Disabled

1. Press <Esc> to exit the System Setup program to complete the System Setup program configuration. 
   
   

Using the Remote Access Serial Interface

When establishing a serial connection to the RAC device, the following interfaces are available:

• IPMI serial interface. See "Using the IPMI Remote Access Serial Interface."
  
  
• RAC serial interface
  
  

RAC Serial Interface

RAC also supports a serial console interface (or RAC Serial Console) that provides a RAC CLI, which is not defined by IPMI. If your system includes a RAC card with Serial Console enabled, the RAC card will override the IPMI serial settings and display the RAC CLI serial interface.

To enable the RAC serial terminal interface, set the cfgSerialConsoleEnable property to 1 (TRUE).

For example:

racadm config -g cfgSerial -o cfgSerialConsoleEnable 1

See "cfgSerialConsoleEnable (Read/Write)" for more information.

Table 4-1 provides the serial interface settings.

Table 4-1. Serial Interface Settings 

IPMI Mode	RAC Serial Console	Interface
Basic	Disabled	Basic Mode
Basic	Enabled	RAC CLI
Terminal	Disabled	IPMI Terminal Mode
Terminal	Enabled	RAC CLI

Configuring Linux for Serial Console Redirection During Boot

The following steps are specific to the Linux GRand Unified Bootloader (GRUB). Similar changes would be necessary if you use a different boot loader.

NOTE: When you configure the client VT100 emulation window, set the window or application that is displaying the redirected console to 25 rows x 80 columns to ensure proper text display; otherwise, some text screens may be garbled.

Edit the /etc/grub.conf file as follows:

1. Locate the General Setting sections in the file and add the following two new lines: 
   
   

serial --unit=1 --speed=57600
terminal --timeout=10 serial

1. Append two options to the kernel line: 
   
   

kernel ............. console=ttyS1,57600

1. If the /etc/grub.conf contains a splashimage directive, comment it out. 
   
   

Table 4-2 provides a sample /etc/grub.conf file that shows the changes described in this procedure.

Table 4-2. Sample File: /etc/grub.conf

# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes  # to this file # NOTICE:  You do not have a /boot partition.  This means that #          all kernel and initrd paths are relative to /, e.g. #          root (hd0,0) #          kernel /boot/vmlinuz-version ro root= /dev/sdal #          initrd /boot/initrd-version.img # #boot=/dev/sda default=0 timeout=10 #splashimage=(hd0,2)/grub/splash.xpm.gz serial --unit=1 --speed=57600 terminal --timeout=10 serial title Red Hat Linux Advanced Server (2.4.9-e.3smp)    root (hd0,0)    kernel /boot/vmlinuz-2.4.9-e.3smp ro root= /dev/sda1 hda=ide-scsi console=ttyS0 console= ttyS1,57600    initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3)    root (hd0,00)    kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 s    initrd /boot/initrd-2.4.9-e.3.im

When you edit the /etc/grub.conf file, use the following guidelines:

1. Disable GRUB's graphical interface and use the text-based interface; otherwise, the GRUB screen will not be displayed in RAC console redirection. To disable the graphical interface, comment out the line starting with splashimage. 
   
   
2. To enable multiple GRUB options to start console sessions through the RAC serial connection, add the following line to all options: 
   
   

console=ttyS1,57600

Table 4-2 shows console=ttyS1,57600 added to only the first option.

Enabling Login to the Console After Boot

Edit the file /etc/inittab as follows:

Add a new line to configure agetty on the COM2 serial port:

co:2345:respawn:/sbin/agetty -h -L 57600 ttyS1 ansi

Table 4-3 shows a sample file with the new line.

Table 4-3. Sample File: /etc/innitab 

# # inittab  This file describes how the INIT process should set up #          the system in a certain run-level. # # Author:  Miquel van Smoorenburg  #          Modified for RHS Linux by Marc Ewing and Donnie Barnes # # Default runlevel. The runlevels used by RHS are: #   0 - halt (Do NOT set initdefault to this) #   1 - Single user mode #   2 - Multiuser, without NFS (The same as 3, if you do not have #       networking) #   3 - Full multiuser mode #   4 - unused #   5 - X11 #   6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6

# Things to run in every runlevel. ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few # minutes of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have power installed and your # UPS is connected and working correctly.  pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"

# Run gettys in standard runlevels co:2345:respawn:/sbin/agetty -h -L 57600 ttyS1 ansi 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 # Run xdm in runlevel 5 # xdm is now a separate service x:5:respawn:/etc/X11/prefdm -nodaemon

Edit the file /etc/securetty as follows:

Add a new line with the name of the serial tty for COM2:

ttyS1

Table 4-4 shows a sample file with the new line.

Table 4-4. Sample File: /etc/securetty

vc/1                    vc/2                    vc/3                    vc/4                    vc/5                    vc/6                    vc/7                    vc/8                    vc/9                    vc/10                   vc/11                   tty1                    tty2                    tty3                    tty4                    tty5                    tty6                    tty7                    tty8                    tty9                    tty10                  tty11                   ttyS1

Enabling the DRAC 5 Serial/Telnet/SSH Console

The serial/telnet/ssh console can be enabled locally or remotely.

Enabling the Serial/Telnet/SSH Console Locally

NOTE: You (the current user) must have Configure DRAC 5 permission in order to perform the steps in this section.

To enable the serial/telnet/ssh console from the managed system, type the following local RACADM commands from a command prompt:

racadm config -g cfgSerial -o cfgSerialConsoleEnable 1

racadm config -g cfgSerial -o cfgSerialTelnetEnable 1

racadm config -g cfgSerial -o cfgSerialSshEnable 1

Enabling the Serial/Telnet/SSH Console Remotely

To enable the serial/telnet/ssh console remotely, type the following remote RACADM commands from a command prompt:

racadm -u <username> -p <password> -r <DRAC 5 IP address> config -g cfgSerial -o cfgSerialConsoleEnable 1

racadm -u <username> -p <password> -r <DRAC 5 IP address> config -g cfgSerial -o cfgSerialTelnetEnable 1

racadm -u <username> -p <password> -r <DRAC 5 IP address> config -g cfgSerial -o cfgSerialSshEnable 1

NOTE: When you use Internet Explorer version 6 SP2 or version 7 to log into a managed system on a private network, but without access to the Internet, you may experience a delay of up to 30 seconds while using remote RACADM commands.

Using the RACADM Command to Configure the Settings for the Serial and Telnet Console

This subsection provides steps to configure the default configuration settings for serial/telnet/ssh console redirection.

To configure the settings, type the RACADM config command with the appropriate group, property, and property value(s) for the setting that you want to configure.

You can type RACADM commands locally or remotely. When using RACADM commands remotely, you must include the user name, password, and managed system DRAC 5 IP address.

Using RACADM Locally

To type RACADM commands locally, type the following command from a command prompt on the managed system:

racadm config -g <group> -o <property> <value>

To view a list of properties, type the following command from a command prompt on the managed system:

racadm getconfig -g <group>

Using RACADM Remotely

To use RACADM commands remotely, type the following command from a command prompt on a management station:

racadm -u <username> -p <password> -r <DRAC 5 IP address> config -g <group> -o <property> <value>

Ensure that your web server is configured with a DRAC 5 card before you use RACADM remotely. Otherwise, RACADM times out and the following message appears:

Unable to connect to RAC at specified IP address.

To enable your web server using Secure Shell (SSH), telnet or local RACADM, type the following command from a command prompt on a management station:

racadm config -g cfgRacTuning -o cfgRacTuneWebServerEnable 1

Displaying Configuration Settings

Table 4-5 provides the actions and related commands to display your configuration settings. To run the commands, open a command prompt on the managed system, type the command, and press <Enter>.

Table 4-5. Displaying Configuration Settings

Action	Command
List the available groups.	racadm getconfig -h
Display the current settings for a particular group.	racadm getconfig -g <group> For example, to display a list of all cfgSerial group settings, type the following command: racadm getconfig -g cfgSerial
Display the current settings for a particular group remotely.	racadm -u <user> -p <password> -r <DRAC 5 IP address> getconfig -g cfgSerial For example, to display a list of all of the settings for the cfgSerial group remotely, type: racadm -u root -p calvin -r 192.168.0.1 getconfig -g cfgSerial

Configuring the Telnet Port Number

Type the following command to change the telnet port number on the DRAC 5.

racadm config -g cfgRacTuning -o cfgRacTuneTelnetPort <new port number>

Using a Serial or Telnet Console

You can run the serial commands in Table 4-19 remotely using RACADM or from the serial/telnet/ssh console command prompt.

Logging in to the DRAC 5

After you have configured your management station terminal emulator software and managed node BIOS, perform the following steps to log into the DRAC 5:

1. Connect to the DRAC 5 using your management station terminal emulation software. 
   
   
2. Type your DRAC 5 user name and press <Enter>. 
   
   

You are logged into the DRAC 5.

Starting a Text Console

After you have logged into the DRAC 5 through your management station terminal software with telnet or SSH, you can redirect the managed system text console by using connect com2, which is a telnet/SSH command. Only one connect com2 client is supported at a time.

To connect to the managed system text console, open a DRAC 5 command prompt (displayed through a telnet or SSH session) and type:

connect com2

From a serial session, you can connect to the managed system's serial console by pressing <Esc><Shift><Q>, which connects the managed system's serial port directly to the servers' COM2 port and bypasses the DRAC 5. To reconnect the DRAC 5 to the serial port, press <Esc><Shift><9>. The managed node COM2 port and the DRAC 5 serial port baud rates must be identical.

The connect -h com2 command displays the contents of the serial history buffer before waiting for input from the keyboard or new characters from the serial port.

NOTE: When using the -h option, the client and server terminal emulation type (ANSI or VT100) must be identical; otherwise, the output may be garbled. Additionally, set the client terminal row to 25.

The default (and maximum) size of the history buffer is 8192 characters. You can set this number to a smaller value using the command:

racadm config -g cfgSerial -o cfgSerialHistorySize <number>

Configuring Serial and Terminal Modes

Configuring IPMI and RAC Serial

1. Expand the System tree and click Remote Access. 
   
   
2. Click the Configuration tab and then click Serial. 
   
   
3. Configure the IPMI serial settings. 
   
   

See Table 4-6 for description of the IPMI serial settings.

1. Configure the RAC serial settings. 
   
   

See Table 4-7 for description of the RAC serial settings.

1. Click Apply Changes. 
   
   
2. Click the appropriate Serial Configuration page button to continue. See Table 4-8 for description of the serial configuration page settings. 
   
   

Table 4-6. IPMI Serial Settings 

Setting	Description
Connection Mode Setting	Direct Connect Basic Mode - IPMI Serial Basic Mode Direct Connect Terminal Mode - IPMI Serial Terminal Mode
Baud Rate	Sets the data speed rate. Select 9600 bps, 19.2 kbps, 57.6 kbps, or 115.2 kbps.
Flow Control	None — Hardware Flow Control Off RTS/CTS — Hardware Flow Control On
Channel Privilege Level Limit	Administrator Operator User

Table 4-7. RAC Serial Settings 

Setting	Description
Enabled	Enables or disables the RAC serial console. Checked=Enabled; Unchecked=Disabled
Maximum Sessions	The maximum number of simultaneous sessions allowed for this system.
Timeout	The maximum number of seconds of line idle time before the line is disconnected. The range is 60 to 1920 seconds. Default is 300 seconds. Use 0 seconds to disable the Timeout feature.
Redirect Enabled	Enables or disables Console Redirection. Checked=Enabled; Unchecked=Disabled
Baud Rate	The data speed on the external serial port. Values are 9600 bps, 28.8 kbps, 57.6 kbps, and 115.2 kbps. Default is 57.6 kbps.
Escape Key	Specifies the <Esc> key. The default are the ^ characters.
History Buffer Size	The size of the serial history buffer, which holds the last characters written to the console. The maximum and default = 8192 characters.
Login Command	The DRAC command line to be executed upon valid login.

Table 4-8. Serial Configuration Page Settings

Button	Description
Print	Print the Serial Configuration page.
Refresh	Refresh the Serial Configuration page.
Apply Changes	Apply the IPMI and RAC serial changes.
Terminal Mode Settings	Opens the Terminal Mode Settings page.

Configuring Terminal Mode

1. Expand the System tree and click Remote Access. 
   
   
2. Click the Configuration tab and then click Serial. 
   
   
3. In the Serial Configuration page, click Terminal Mode Settings. 
   
   
4. Configure the terminal mode settings. 
   
   

See Table 4-9 for description of the terminal mode settings.

1. Click Apply Changes. 
   
   
2. Click the appropriate Terminal Mode Settings page button to continue. See Table 4-10 for description of the terminal mode settings page buttons. 
   
   

Table 4-9. Terminal Mode Settings 

Setting	Description
Line Editing	Enables or disables line editing.
Delete Control	Select one of the following: BMC outputs a <bksp><sp><bksp> character when <bksp> or <del> is received — BMC outputs a <del> character when <bksp> or <del> is received —
Echo Control	Enables or disables echo.
Handshaking Control	Enables or disables handshaking.
New Line Sequence	Select None, <CR-LF>, <NULL>, <CR>, <LF-CR>, or <LF>.
Input New Line Sequence	Select <CR> or <NULL>.

Table 4-10. Terminal Mode Settings Page Buttons

Button	Description
Print	Print the Terminal Mode Settings page.
Refresh	Refresh the Terminal Mode Settings page.
Go Back to Serial Port Configuration	Return to the Serial Port Configuration page.
Apply Changes	Apply the terminal mode settings changes.

Connecting to the Managed System Through the Local Serial Port or Telnet Management Station (Client System)

The managed system provides access between the DRAC 5 and the serial port on your system to enable you to power on, power off, or reset the managed system, and access logs.

The serial console is available on the DRAC 5 through the managed system external serial connector. Only one serial client system (management station) may be active at any given time. The telnet and SSH consoles are available on the DRAC 5 through the DRAC modes (see "DRAC Modes"). Up to four telnet client systems and four SSH clients may connect at any given time. The management station connection to the managed system serial or telnet console requires management station terminal emulation software. See "Configuring the Management Station Terminal Emulation Software" for more information.

The following subsections explain how to connect your management station to the managed system using the following methods:

• A managed system external serial port using terminal software and a DB-9 or a null modem cable
  
  
• A telnet connection using terminal software through the managed system DRAC 5 NIC or the shared, teamed NIC
  
  

Connecting the DB-9 or Null Modem Cable for the Serial Console

To access the managed system using a serial text console, connect a DB-9 null modem cable to the COM port on the managed system. Not all DB-9 cables carry the pinout/signals necessary for this connection. The DB-9 cable for this connection must conform to the specification shown in Table 4-11.

NOTE: The DB-9 cable can also be used for BIOS text console redirection.

Table 4-11. Required Pinout for DB-9 Null Modem Cable 

Signal Name	DB-9 Pin (server pin)	DB-9 Pin (workstation pin)
FG (Frame Ground)	–	–
TD (Transmit data)	3	2
RD (Receive Data)	2	3
RTS (Request To Send)	7	8
CTS (Clear To Send)	8	7
SG (Signal Ground)	5	5
DSR (Data Set Ready)	6	4
CD (Carrier Detect)	1	4
DTR (Data Terminal Ready)	4	1 and 6

Configuring the Management Station Terminal Emulation Software

Your DRAC 5 supports a serial or telnet text console from a management station running one of the following types of terminal emulation software:

• Linux Minicom in an Xterm
  
  
• Hilgraeve's HyperTerminal Private Edition (version 6.3)
  
  
• Linux Telnet in an Xterm
  
  
• Microsoft® Telnet
  
  

Perform the steps in the following subsections to configure your type of terminal software. If you are using Microsoft Telnet, configuration is not required.

Configuring Linux Minicom for Serial Console Emulation

Minicom is the serial port access utility for Linux. The following steps are valid for configuring Minicom version 2.0. Other Minicom versions may differ slightly but require the same basic settings. Use the information in "Required Minicom Settings for Serial Console Emulation" to configure other versions of Minicom.

Configuring Minicom Version 2.0 for Serial Console Emulation

NOTE: To ensure that the text displays properly, Dell recommends that you use an Xterm window to display the telnet console instead of the default console provided by the Linux installation.

1. To start a new Xterm session, type xterm & at the command prompt. 
   
   
2. In the Xterm window, move your mouse arrow to the lower right-hand corner of the window and resize the window to 80 x 25. 
   
   
3. If you do not have a Minicom configuration file, go to the next step. 
   
   

If you have a Minicom configuration file, type minicom <Minicom config file name> and skip to step 17.

1. At the Xterm command prompt, type minicom -s. 
   
   
2. Select Serial Port Setup and press <Enter>. 
   
   
3. Press <a> and select the appropriate serial device (for example, /dev/ttyS0). 
   
   
4. Press <e> and set the Bps/Par/Bits option to 57600 8N1. 
   
   
5. Press <f> and set Hardware Flow Control to Yes and set Software Flow Control to No. 
   
   
6. To exit the Serial Port Setup menu, press <Enter>. 
   
   
7. Select Modem and Dialing and press <Enter>. 
   
   
8. In the Modem Dialing and Parameter Setup menu, press <Backspace> to clear the init, reset, connect, and hangup settings so that they are blank. 
   
   
9. Press <Enter> to save each blank value. 
   
   
10. When all specified fields are clear, press <Enter> to exit the Modem Dialing and Parameter Setup menu. 
    
    
11. Select Save setup as config_name and press <Enter>. 
    
    
12. Select Exit From Minicom and press <Enter>. 
    
    
13. At the command shell prompt, type minicom <Minicom config file name>. 
    
    
14. To expand the Minicom window to 80 x 25, drag the corner of the window. 
    
    
15. Press <Ctrl+a>, <z>, <x> to exit Minicom. 
    
    

NOTE: If you are using Minicom for serial text console redirection to configure the managed system BIOS, it is recommended to turn on color in Minicom. To turn on color, type the following command:minicom -c on

Ensure that the Minicom window displays a command prompt such as [DRAC 5root]#. When the command prompt appears, your connection is successful and you are ready to connect to the managed system console using the connect serial command.

Required Minicom Settings for Serial Console Emulation

Use Table 4-12 to configure any version of Minicom.

Table 4-12. Minicom Settings for Serial Console Emulation 

Setting Description	Required Setting
Bps/Par/Bits	57600 8N1
Hardware flow control	Yes
Software flow control	No
Terminal emulation	ANSI
Modem dialing and parameter settings	Clear the init, reset, connect, and hangup settings so that they are blank
Window size	80 x 25 (to resize, drag the corner of the window)

Configuring HyperTerminal for Serial Console Redirection

HyperTerminal is the Microsoft Windows serial port access utility. To set the size of your console screen appropriately, use Hilgraeve's HyperTerminal Private Edition version 6.3.

To configure HyperTerminal for serial console redirection:

1. Start the HyperTerminal program. 
   
   
2. Type a name for the new connection and click OK. 
   
   
3. Next to Connect using:, select the COM port on the management station (for example, COM2) to which you have connected the DB-9 null modem cable and click OK. 
   
   
4. Configure the COM port settings as shown in Table 4-13. 
   
   
5. Click OK. 
   
   
6. Click File → Properties, and then click the Settings tab. 
   
   
7. Set the Telnet terminal ID: to ANSI. 
   
   
8. Click Terminal Setup and set Screen Rows to 26. 
   
   
9. Set Columns to 80 and click OK. 
   
   

Table 4-13. Management Station COM Port Settings 

Setting Description	Required Setting
Bits per second	57600
Data bits	8
Parity	None
Stop bits	1
Flow control	Hardware

The HyperTerminal window displays a command prompt such as [DRAC 5root]#. When the command prompt appears, your connection is successful and you are ready to connect to the managed system console using the connect com2 serial command.

Configuring Linux XTerm for Telnet Console Redirection

Use the following guidelines when performing the steps in this section:

• When you are using the connect com2 command through a telnet console to display the System Setup screens, set the terminal type to ANSI in System Setup and for the telnet session.
  
  
• To ensure that the text is properly displayed, Dell recommends that you use an Xterm window to display the telnet console instead of the default console provided by the Linux installation.
  
  

To run telnet with Linux:

1. Start a new Xterm session. 
   
   

At the command prompt, type xterm &

1. Click on the lower right-hand corner of the XTerm window and resize the window to 80 x 25. 
   
   
2. Connect to the DRAC 5 in the managed system. 
   
   

At the Xterm prompt, type telnet <DRAC 5 IP address>

Enabling Microsoft Telnet for Telnet Console Redirection

NOTE: Some telnet clients on Microsoft operating systems may not display the BIOS setup screen correctly when BIOS console redirection is set for VT100 emulation. If this issue occurs, update the display by changing BIOS console redirection to ANSI mode. To perform this procedure in the BIOS setup menu, select Console Redirection → Remote Terminal Type → ANSI.

1. Enable Telnet in Windows Component Services. 
   
   
2. Connect to the DRAC 5 in the management station. 
   
   

Open a command prompt, type the following, and press <Enter>:

telnet <IP address>:<port number>

where IP address is the IP address for the DRAC 5 and port number is the telnet port number (if you are using a new port).

Configuring the Backspace Key For Your Telnet Session

Depending on the telnet client, using the <Backspace> key may produce unexpected results. For example, the session may echo ^h. However, most Microsoft and Linux telnet clients can be configured to use the <Backspace> key.

To configure Microsoft telnet clients to use the <Backspace> key:

1. Open a command prompt window (if required). 
   
   
2. If you are not running a telnet session, type: 
   
   

telnet

If you are running a telnet session, press <Ctrl><]>.

1. At the prompt, type: 
   
   

set bsasdel

The following message appears:

Backspace will be sent as delete.

To configure a Linux telnet session to use the <Backspace> key:

1. Open a command prompt and type: 
   
   

stty erase ^h

1. At the prompt, type: 
   
   

telnet

Using a Serial or Telnet Console

Serial and telnet commands, and RACADM CLI can be typed in a serial or telnet console and executed on the server locally or remotely. The local RACADM CLI is installed for use by a root user only.

Running Telnet Using Windows XP or Windows 2003

If your management station is running Windows XP or Windows 2003, you may experience an issue with the characters in a DRAC 5 telnet session.This issue may occur as a frozen login where the return key does not respond and the password prompt does not appear.

To fix this issue, download hotfix 824810 from the Microsoft Support website at support.microsoft.com. See Microsoft Knowledge Base article 824810 for more information.

Running Telnet Using Windows 2000

If your management station is running Windows 2000, you cannot access BIOS setup by pressing the <F2> key. To fix this issue, use the telnet client supplied with the Windows Services for UNIX® 3.5—a recommended free download from Microsoft. Go to www.microsoft.com/downloads/ and search for "Windows Services for UNIX 3.5."

Using the Secure Shell (SSH)

It is critical that your system's devices and device management are secure. Embedded connected devices are the core of many business processes. If these devices are compromised, your business may be at risk, which requires new security demands for command line interface (CLI) device management software.

Secure Shell (SSH) is a command line session that includes the same capabilities as a telnet session, but with improved security. The DRAC 5 supports SSH version 2 with password authentication. SSH is enabled on the DRAC 5 when you install or update your DRAC 5 firmware.

You can use either PuTTY or OpenSSH on the management station to connect to the managed system's DRAC 5. When an error occurs during the login procedure, the secure shell client issues an error message. The message text is dependent on the client and is not controlled by the DRAC 5.

NOTE: OpenSSH should be run from a VT100 or ANSI terminal emulator on Windows. Running OpenSSH at the Windows command prompt does not result in full functionality (that is, some keys do not respond and no graphics are displayed).

Only four SSH sessions are supported at any given time. The session time-out is controlled by the cfgSsnMgtSshIdleTimeout property as described in the "DRAC 5 Property Database Group and Object Definitions."

To enable the SSH on the DRAC 5, type:

racadm config -g cfgSerial -o cfgSerialSshEnable 1

To change the SSH port, type:

racadm config -g cfgRacTuning -o cfgRacTuneSshPort <port number>

For more information on cfgSerialSshEnable and cfgRacTuneSshPort properties, see "DRAC 5 Property Database Group and Object Definitions."

The DRAC 5 SSH implementation supports multiple cryptography schemes, as shown in Table 4-14.

Table 4-14. Cryptography Schemes

Scheme Type	Scheme
Asymmetric Cryptography	Diffie-Hellman DSA/DSS 512-1024 (random) bits per NIST specification
Symmetric Cryptography	AES256-CBC RIJNDAEL256-CBC AES192-CBC RIJNDAEL192-CBC AES128-CBC RIJNDAEL128-CBC BLOWFISH-128-CBC 3DES-192-CBC ARCFOUR-128
Message Integrity	HMAC-SHA1-160 HMAC-SHA1-96 HMAC-MD5-128 HMAC-MD5-96
Authentication	Password

NOTE: SSHv1 is not supported.

Configuring the DRAC 5 Network Settings

NOTICE: Changing your DRAC 5 Network settings may disconnect your current network connection.

Configure the DRAC 5 network settings using one of the following tools:

• Web-based Interface — See "Configuring the DRAC 5 NIC"
  
  
• RACADM CLI — See "cfgLanNetworking"
  
  
• Dell Remote Access Configuration Utility — See "Configuring Your System to Use a DRAC 5"
  
  

NOTE: If you are deploying the DRAC 5 in a Linux environment, see "Installing RACADM".

Accessing the DRAC 5 Through a Network

After you configure the DRAC 5, you can remotely access the managed system using one of the following interfaces:

• Web-based interface
  
  
• RACADM
  
  
• Telnet Console
  
  
• SSH 
  
  
• IPMI
  
  

Table 4-15 describes each DRAC 5 interface.

Table 4-15. DRAC 5 Interfaces 

Interface	Description
Web-based interface	Provides remote access to the DRAC 5 using a graphical user interface. The Web-based interface is built into the DRAC 5 firmware and is accessed through the NIC interface from a supported Web browser on the management station. For a list of supported Web browsers, see the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com.
RACADM	Provides remote access to the DRAC 5 using a command line interface. RACADM uses the managed system's IP address to execute RACADM commands (racadm remote capability option [-r]). NOTE: The racadm remote capability is supported only on management stations. For a list of supported Web browsers, see the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com. NOTE: When using the racadm remote capability, you must have write permission on the folders where you are using the racadm subcommands involving file operations, for example: racadm getconfig -f <file name> or: racadm sslcertupload -t 1 -f c:certcert.txt subcommands
Telnet Console	Provides access through the DRAC 5 to the server RAC port and hardware management interfaces through the DRAC 5 NIC and provides support for serial and RACADM commands includingpowerdown, powerup, powercycle, and hardreset commands. NOTE: Telnet is an unsecure protocol that transmits all data—including passwords—in plain text. When transmitting sensitive information, use the SSH interface.
SSH Interface	Provides the same capabilities as the telnet console using an encrypted transport layer for higher security.
IPMI Interface	Provides access through the DRAC 5 to the remote system's basic management features. The interface includes IPMI over LAN, IPMI over Serial, and Serial over LAN. See the Dell OpenManage Baseboard Management Controller User's Guide for more information.

NOTE: The DRAC 5 default user name is root and the default password is calvin.

You can access the DRAC 5 Web-based interface through the DRAC 5 NIC by using a supported Web browser, or through Server Administrator or IT Assistant.

For a list of supported Web browsers, see the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com.

To access the DRAC 5 remote access interface using Server Administrator, launch Server Administrator. From the system tree on the left pane of the Server Administrator home page, click System→ Main System Chassis→ Remote Access Controller. For more information, see your Server Administrator User's Guide.

Configuring the DRAC 5 NIC

Configuring the Network and IPMI LAN Settings

NOTE: You must have Configure DRAC 5 permission to perform the following steps.

NOTE: Most DHCP servers require a server to store a client identifier token in its reservations table. The client (DRAC 5, for example) must provide this token during DHCP negotiation. For RACs, the DRAC 5 supplies the client identifier option using a one-byte interface number (0) followed by a six-byte MAC address.

NOTE: If your managed system DRAC is configured in Shared or Shared with Failover mode and the DRAC is connected to a switch with Spanning Tree Protocol (STP) enabled, network clients will experience a 20-30 second delay in connectivity when the management station's LOM link state changes during the STP convergence.

1. In the System tree, click Remote Access. 
   
   
2. Click the Configuration tab and then click Network. 
   
   
3. In the Network Configuration page, configure the DRAC 5 NIC settings. 
   
   

Table 4-16 and Table 4-17 describes the Network Settings and IPMI Settings on the Network Configuration page.

1. When completed, click Apply Changes. 
   
   
2. Click the appropriate Network Configuration page button to continue. See Table 4-18. 
   
   

Table 4-16. Network Settings 

Setting	Description
NIC Selection	Displays the selected NIC mode (Dedicated, Shared with Failover, or Shared). The default setting is Dedicated.
MAC Address	Displays the DRAC 5 MAC address.
Enable NIC	Enables the DRAC 5 NIC and activates the remaining controls in this group. The default setting is Enabled.
Use DHCP (For NIC IP Address)	Enables Dell OpenManage™ Server Administrator to obtain the DRAC 5 NIC IP address from the Dynamic Host Configuration Protocol (DHCP) server. Selecting the check box deactivates the Static IP Address, Static Gateway, and Static Subnet Mask controls. The default setting is Disabled.
Static IP Address	Specifies or edits the static IP address for the DRAC 5 NIC. To change this setting, deselect the Use DHCP (For NIC IP Address) check box.
Static Gateway	Specifies or edits the static gateway for the DRAC 5 NIC. To change this setting, deselect the Use DHCP (For NIC IP Address) check box.
Static Subnet Mask	Specifies or edits the static subnet mask for the DRAC 5 NIC. To change this setting, deselect the Use DHCP (For NIC IP Address) check box.
Use DHCP to obtain DNS server addresses	Obtains the primary and secondary DNS server addresses from the DHCP server instead of the static settings. The default setting is Disabled.
Static Preferred DNS Server	Uses the primary DNS server IP address only when Use DHCP to obtain DNS server addresses is not selected.
Static Alternate DNS Server	Uses the secondary DNS server IP address when Use DHCP to obtain DNS server addresses is not selected. You may enter an IP address of 0.0.0.0 if you do not have an alternate DNS server.
Register DRAC on DNS	Registers the DRAC 5 name on the DNS server. The default setting is Disabled.
DNS DRAC Name	Displays the DRAC 5 name only when Register DRAC 5 on DNS is selected. The default DRAC 5 name is RAC-service tag, where service tag is the service tag number of the Dell server (for example, RAC-EK00002).
Use DHCP for DNS Domain Name	Uses the default DNS domain name. When the box is not selected and the Register DRAC 5 on DNS option is selected, you can modify the DNS domain name in the DNS Domain Name field. The default setting is Disabled.
DNS Domain Name	The default DNS domain name is MYDOMAIN. When the Use DHCP for DNS Domain Name check box is selected, this option is grayed out and you cannot modify this field.
Auto Negotiation	Determines whether the DRAC 5 automatically sets the Duplex Mode and Network Speed by communicating with the nearest router or hub (On) or allows you to set the Duplex Mode and Network Speed manually (Off).
Network Speed	Sets the network speed to 100 Mb or 10 Mb to match your network environment. This option is not available if Auto Negotiation is set to On.
Duplex Mode	Sets the duplex mode to full or half to match your network environment. This option is not available if Auto Negotiation is set to On.

Table 4-17. IPMI LAN Settings 

Setting	Description
Enable IPMI Over LAN	Enables the IPMI LAN channel.
Channel Privilege Level Limit	Configures the user's maximum privilege level that can be accepted on the LAN channel. Select one of the following options: Administrator, Operator, or User.
Encryption Key	Configures the encryption key character format: 0 to 20 hexadecimal characters (no blanks allowed). The default setting is 00000000000000000000.
Enable VLAN ID	Enables the VLAN ID. If enabled, only matched VLAN ID traffic is accepted.
VLAN ID	The VLAN ID field of 802.1g fields.
Priority	The Priority field of 802.1g fields.

Table 4-18. Network Configuration Page Buttons 

Button	Description
Print	Prints the Network Configuration page
Refresh	Reloads the Network Configuration page
Advanced Settings	Displays the Network Security page.
Apply Changes	Saves the changes made to the network configuration. NOTE: Changes to the NIC IP address settings will close all user sessions and require users to reconnect to the DRAC 5 Web- based interface using the updated IP address settings. All other changes will require the NIC to be reset, which may cause a brief loss in connectivity.

See "Configuring the Network Security Settings Using the DRAC 5 GUI" for more information.

Using RACADM Remotely

NOTE: Configure the IP address on your DRAC 5 before using the racadm remote capability. For more information about setting up your DRAC 5 and a list of related documents, see "Basic Installation of the DRAC 5".

RACADM provides a remote capability option (-r) that allows you to connect to the managed system and execute racadm subcommands from a remote console or management station. To use the remote capability, you need a valid user name (-u option) and password (-p option), and the DRAC 5 IP address.

NOTE: If the system from where you are accessing the remote system does not have a DRAC certificate in its default certificate store, a message is displayed when you type a racadm command.

Security Alert: Certificate is invalid - Name on Certificate is invalid or does not match site name

Continuing execution. Use –S option for racadm to stop the execution on certificate-related errors.

racadm continues to execute the command. However, if you use the –S option, racadm stops executing the command and displays the following message:

Security Alert: Certificate is invalid - Name on Certificate is invalid or does not match site name

Racadm not continuing execution of the command.

EORROR: Unable to connect to RAC at specified IP address

NOTE: The racadm remote capability is supported only on management stations. For more information, see the Dell Systems Software Support Matrix on the Dell Support website at support.dell.com for more information.

NOTE: When using the racadm remote capability, you must have write permissions on the folders where you are using the racadm subcommands involving file operations, for example:

racadm getconfig -f <file name>

or

racadm sslcertupload -t 1 -f c:certcert.txt subcommands

RACADM Synopsis

racadm -r <RAC IP Address> -u <username> -p <password> <subcommand> <subcommand options>

racadm -i -r <RAC IP Address> <subcommand> <subcommand options>

For example:

racadm -r 192.168.0.120 -u root -p calvin getsysinfo

racadm -i -r 192.168.0.120 getsysinfo

If the HTTPS port number of the RAC has been changed to a custom port other than the default port (443), the following syntax must be used:

racadm -r <RAC IP Address>:<port> -u <username> -p <password> <subcommand> <subcommand options>

racadm -i -r <RAC IP Address>:<port> <subcommand> <subcommand options>

RACADM Options

Table 4-19 lists the options for the racadm command.

Table 4-19. racadm Command Options 

Option	Description
-r <racIpAddr> -r <racIpAddr>:<port number>	Specifies the controller's remote IP address. Use :<port number> if the DRAC 5 port number is not the default port (443)
-i	Instructs racadm to interactively query the user for user name and password.
-u <usrName>	Specifies the user name that is used to authenticate the command transaction. If the -u option is used, the -p option must be used, and the -i option (interactive) is not allowed.
-p <password>	Specifies the password used to authenticate the command transaction. If the -p option is used, the -i option is not allowed.
-S	Specifies that racadm should check for invalid certificate errors. racadm stops the execution of the command with an error message if it detects an invalid certificate.

Enabling and Disabling the racadm Remote Capability

NOTE: It is recommended that you run these commands on your local system.

The racadm remote capability is enabled by default. If disabled, type the following racadm command to enable:

racadm config -g cfgRacTuning -o cfgRacTuneRemoteRacadmEnable 1

To disable the remote capability, type:

racadm config -g cfgRacTuning -o cfgRacTuneRemoteRacadmEnable 0

RACADM Subcommands

Table 4-20 provides a description of each racadm subcommand that you can run in RACADM. For a detailed listing of racadm subcommands including syntax and valid entries, see "RACADM Subcommand Overview."

When entering a RACADM subcommand, prefix the command with racadm. For example:

racadm help

Table 4-20. RACADM Subcommands 

Command	Description
help	Lists DRAC 5 subcommands.
help <subcommand>	Lists usage statement for the specified subcommand.
arp	Displays the contents of the ARP table. ARP table entries may not be added or deleted.
clearasrscreen	Clears the last ASR (crash) screen (last blue screen).
clrraclog	Clears the DRAC 5 log. A single entry is made to indicate the user and time that the log was cleared.
config	Configures the RAC.
getconfig	Displays the current RAC configuration properties.
coredump	Displays the last DRAC 5 coredump.
coredumpdelete	Deletes the coredump stored in the DRAC 5.
fwupdate	Executes or displays status on DRAC 5 firmware updates.
getssninfo	Displays information about active sessions.
getsysinfo	Displays general DRAC 5 and system information.
getractime	Displays the DRAC 5 time.
ifconfig	Displays the current RAC IP configuration.
netstat	Displays the routing table and the current connections.
ping	Verifies that the destination IP address is reachable from the DRAC 5 with the current routing-table contents.
setniccfg	Sets the IP configuration for the controller.
getniccfg	Displays the current IP configuration for the controller.
getsvctag	Displays service tags.
racdump	Dumps DRAC 5 status and state information for debug.
racreset	Resets the DRAC 5.
racresetcfg	Resets the DRAC 5 to the default configuration.
serveraction	Performs power management operations on the managed system.
getraclog	Displays the RAC log.
clrsel	Clears the System Event Log entries.
gettracelog	Displays the DRAC 5 trace log. If used with -i, the command displays the number of entries in the DRAC 5 trace log.
sslcsrgen	Generates and downloads the SSL CSR.
sslcertupload	Uploads a CA certificate or server certificate to the DRAC 5.
sslcertdownload	Downloads a CA certificate.
sslcertview	Views a CA certificate or server certificate in the DRAC 5.
testemail	Forces the DRAC 5 to send a test e-mail over the DRAC 5 NIC to check the e-mail configuration.
testtrap	Forces the DRAC 5 to send a test SNMP trap over the DRAC 5 NIC to check the trap configuration.
vmdisconnect	Forces a virtual media connection to close.
vmkey	Resets the virtual flash size to its default size (16 MB).

Frequently Asked Questions About RACADM Error Messages

After performing a DRAC 5 reset (using the racadm racreset command), I issue a command and the following message is displayed:

racadm <command name> Transport: ERROR: (RC=-1)

What does this message mean?

You must wait until the DRAC 5 completes the reset before issuing another command.

When I use the racadm commands and subcommands, I get errors that I don't understand.

You may encounter one or more of the following errors when using the racadm commands and subcommands:

• Local racadm error messages — Problems such as syntax, typographical errors, and incorrect names.
  
  
• Remote racadm error messages—Problems such as incorrect IP Address, incorrect username, or incorrect password.
  
  

When I ping the DRAC IP address from my system and then switch my DRAC 5 card between Dedicated and Shared modes during the ping response, I do not receive a response.

Clear the ARP table on your system.

Configuring Multiple DRAC 5 Cards

Using RACADM, you can configure one or more DRAC 5 cards with identical properties. When you query a specific DRAC 5 card using its group ID and object ID, RACADM creates the racadm.cfg configuration file from the retrieved information. By exporting the file to one or more DRAC 5 cards, you can configure your controllers with identical properties in a minimal amount of time.

NOTE: Some configuration files contain unique DRAC 5 information (such as the static IP address) that must be modified before you export the file to other DRAC 5 cards.

To configure multiple DRAC 5 cards, perform the following procedures:

1. Use RACADM to query the target DRAC 5 that contains the appropriate configuration. 
   
   

NOTE: The generated .cfg file does not contain user passwords.

Open a command prompt and type:

racadm getconfig -f myfile.cfg

NOTE: Redirecting the RAC configuration to a file using getconfig -f is only supported with the local and remote RACADM interfaces.

1. Modify the configuration file using a simple text editor (optional). 
   
   
2. Use the new configuration file to modify a target RAC. 
   
   

In the command prompt, type:

racadm config -f myfile.cfg

1. Reset the target RAC that was configured. 
   
   

In the command prompt, type:

racadm reset

The getconfig -f racadm.cfg subcommand requests the DRAC 5 configuration and generates the racadm.cfg file. If required, you can configure the file with another name.

You can use the getconfig command to enable you to perform the following actions:

• Display all configuration properties in a group (specified by group name and index)
  
  
• Display all configuration properties for a user by user name
  
  

The config subcommand loads the information into other DRAC 5s. Use config to synchronize 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 create this file, type the following at the command prompt:

racadm getconfig -f myfile.cfg

NOTICE: It is recommended that you edit this file with a simple text editor. The racadm utility uses an ASCII text parser. Any formatting confuses the parser, which may corrupt the racadm database.

Creating a DRAC 5 Configuration File

The DRAC 5 configuration file <filename>.cfg is used with the racadm config -f <filename>.cfg command. You can use the configuration file to build a configuration file (similar to an .ini file) and configure the DRAC 5 from this file. You may use any file name, and the file does not require a .cfg extension (although it is referred to by that extension name in this subsection).

The .cfg file can be:

• Created
  
  
• Obtained from a racadm getconfig -f <filename>.cfg command
  
  
• Obtained from a racadm getconfig -f <filename>.cfg command, and then edited
  
  

NOTE: See "getconfig" for information about 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 that detected the error, and a simple message explains the problem. The entire file is parsed for correctness, and all errors are displayed. Write commands are not transmitted to the DRAC 5 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 a write operation to the DRAC 5.

Use the following guidelines when you create a .cfg file:

• If the parser encounters an indexed group, it is the value of the anchored object that differentiates the various indexes. 
  
  

The parser reads in all of the indexes from the DRAC 5 for that group. Any objects within that group are simple modifications when the DRAC 5 is configured. If a modified object represents a new index, the index is created on the DRAC 5 during configuration.

• You cannot specify an index of your choice in a .cfg file.
  
  

Indexes may be created and deleted, so over time the group may become fragmented with used and unused indexes. If an index is present, it is modified. If an index is not present, the first available index is used. This method allows flexibility when adding indexed entries where you do not need to make exact index matches between all the RACs being managed. New users are added to the first available index. A .cfg file that parses and runs correctly on one DRAC 5 may not run correctly on another if all indexes are full and you must add a new user.

• Use the racresetcfg subcommand to configure all DRAC 5 cards with identical properties.
  
  

Use the racresetcfg subcommand to reset the DRAC 5 to original defaults, and then run the racadm config -f <filename>.cfg command. Ensure that the .cfg file includes all required objects, users, indexes, and other parameters.

NOTICE: Use the racresetcfg subcommand to reset the database and the DRAC 5 NIC settings to the original default settings and remove all users and user configurations. While the root user is available, other users' settings are also reset to the default settings.

Parsing Rules

• 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 include # characters in its string. An escape character is not required. You 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 5, without adding escape characters.

Example:

#

# This is 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 include an associated group name generate an error. The configuration data is organized into groups as defined in "DRAC 5 Property Database Group and Object Definitions."

The following example displays a group name, object, and the object's property value.

Example:

[cfgLanNetworking] -{group name}

cfgNicIpAddress=143.154.133.121 {object name}

• All parameters are specified as "object=value" pairs with no white space between the object, =, or value. 
  
  

White spaces that are included after the value are ignored. A white space inside a value string remains unmodified. Any character to the right of the '=' is taken as is (for example, a second '=', or a '#', '[', ']', and so forth). These characters are valid modem chat script characters.

See the example in the previous bullet.

• The .cfg parser ignores an index object entry.
  
  

You cannot specify which index is used. If the index already exists, it is either used or 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, allowing the user to see the included comments.

NOTE: You may create an indexed group manually using the following command:  racadm config -g <groupName> -o <anchored object> -i <index 1-16> <unique anchor name>

• The line for an indexed group cannot be deleted from a .cfg file. 
  
  

You must remove an indexed object manually using the following command:

racadm config -g <groupName> -o <objectName> -i <index 1-16> ""

NOTE: A NULL string (identified by two "" characters) directs the DRAC 5 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>

If you type racadm getconfig -f <myexample>.cfg, the command builds a .cfg file for the current DRAC 5 configuration. This configuration file can be used as an example and as a starting point for your unique .cfg file.

Modifying the DRAC 5 IP Address

When you modify the DRAC 5 IP address in the configuration file, remove all unnecessary <variable>=value entries. Only the actual variable group's label with "[" and "]" remains, including the two<variable>=value entries pertaining to the IP address change.

For example:

#

# 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 the file and identifies any errors by line number. A correct file will update the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update.

Use this file to download company-wide changes or to configure new systems over the network.

NOTE: "Anchor" is an internal term and should not be used in the file.

Configuring DRAC 5 Network Properties

To generate a list of available network properties, type the following:

racadm getconfig -g cfgLanNetworking

To use DHCP to obtain an IP address, use the following command to write the object cfgNicUseDhcp and enable this feature:

racadm config -g cfgLanNetworking -o cfgNicUseDHCP 1

The commands provide the same configuration functionality as the option ROM at boot-up when you are prompted to type <Ctrl><e>. For more information about configuring network properties with the option ROM, see "Configuring DRAC 5 Network Properties."

The following is an example of how the command may be used to configure desired LAN network properties.

racadm config -g cfgLanNetworking -o cfgNicEnable 1

racadm config -g cfgLanNetworking -o cfgNicIpAddress 192.168.0.120

racadm config -g cfgLanNetworking -o cfgNicNetmask 255.255.255.0

racadm config -g cfgLanNetworking -o cfgNicGateway 192.168.0.120

racadm config -g cfgLanNetworking -o cfgNicUseDHCP 0

racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0

racadm config -g cfgLanNetworking -o cfgDNSServer1 192.168.0.5

racadm config -g cfgLanNetworking -o cfgDNSServer2 192.168.0.6

racadm config -g cfgLanNetworking -o cfgDNSRegisterRac 1

racadm config -g cfgLanNetworking -o cfgDNSRacName RAC-EK00002

racadm config -g cfgLanNetworking -o cfgDNSDomainNameFromDHCP 0

racadm config -g cfgLanNetworking -o cfgDNSDomainName MYDOMAIN

NOTE: If cfgNicEnable is set to 0, the DRAC 5 LAN is disabled even if DHCP is enabled.

DRAC Modes

The DRAC 5 can be configured in one of three modes:

• Dedicated
  
  
• Shared
  
  
• Shared with failover
  
  

Table 4-21 provides a description of each mode.

Table 4-21. DRAC 5 NIC Configurations

Mode	Description
Dedicated	The DRAC uses its own NIC (RJ-45 connector) and the BMC MAC address for network traffic.
Shared	The DRAC uses Broadcom LOM1 on the planar.
Shared with failover	The DRAC uses Broadcom LOM1 and LOM2 as a team for failover. The team uses the BMC MAC address.

Frequently Asked Questions

When accessing the DRAC 5 Web-based interface, I get a security warning stating the hostname of the SSL certificate does not match the hostname of the DRAC 5.

The DRAC 5 includes a default DRAC 5 server certificate to ensure network security for the Web-based interface and remote racadm features. When this certificate is used, the Web browser displays a security warning because the default certificate is issued to DRAC 5 default certificate which does not match the host name of the DRAC 5 (for example, the IP address).

To address this security concern, upload a DRAC 5 server certificate issued to the IP address of the DRAC 5. When generating the certificate signing request (CSR) to be used for issuing the certificate, ensure that the common name (CN) of the CSR matches the IP address of the DRAC 5 (for example, 192.168.0.120) or the registered DNS DRAC name.

To ensure that the CSR matches the registered DNS DRAC name:

1. In the System tree, click Remote Access. 
   
   
2. Click the Configuration tab and then click Network. 
   
   
3. In the Network Settings page: 
   
   
   1. Select the Register DRAC on DNS check box. 
      
      
   1. In the DNS DRAC Name field, enter the DRAC name. 
      
      
4. Click Apply Changes. 
   
   

See "Securing DRAC 5 Communications Using SSL and Digital Certificates" for more information about generating CSRs and issuing certificates.

Why are the remote racadm and Web-based services unavailable after a property change?

It may take a while for the remote RACADM services and the Web-based interface to become available after the DRAC 5 Web server resets.

The DRAC 5 Web server is reset after the following occurrences:

• When the network configuration or network security properties are changed using the DRAC 5 Web user interface
  
  
• When the cfgRacTuneHttpsPort property is changed (including when a config -f <config file> changes it)
  
  
• When racresetcfg is used
  
  
• When the DRAC 5 is reset
  
  
• When a new SSL server certificate is uploaded
  
  

Why doesn't my DNS server register my DRAC 5?

Some DNS servers only register names of 31 characters or fewer.

When accessing the DRAC 5 Web-based interface, I get a security warning stating the SSL certificate was issued by a certificate authority (CA) that is not trusted.

DRAC 5 includes a default DRAC 5 server certificate to ensure network security for the Web-based interface and remote racadm features. This certificate was not issued by a trusted CA. To address this security concern, upload a DRAC 5 server certificate issued by a trusted CA (for example, Thawte or Verisign). See "Securing DRAC 5 Communications Using SSL and Digital Certificates" for more information about issuing certificates.

Back to Contents Page