Dell Remote Access Controller 4 Firmware Version 1.30 User's Guide
This chapter provides information about how to install and setup your DRAC 4 hardware and software.
Gather the following items that came with your system prior to installing and configuring the DRAC 4 software.
![]() |
NOTE: The DRAC 4 connection emulates a USB keyboard connection. As a result, when you restart the system, the system will not notify you if your keyboard is not attached. |
The DRAC 4 may be preinstalled on your system, or available separately in a kit. To get started with the DRAC 4 that is already installed on your system, see "Software Installation and Configuration Overview."
If a DRAC 4 is not installed on your system, see the Installing a Remote Access Card document that came with your DRAC 4 kit or see your platform Installation and Troubleshooting Guide for hardware installation instructions before proceeding.
![]() |
NOTE: The removal of expansion cards, such as the DRAC 4, is documented in the Installation and Troubleshooting Guide that came with your system. |
This section provides a high-level overview of the DRAC 4 software installation and configuration process for the DRAC 4. All configuration steps can be performed using the Web-based interface, racadm CLI, or Serial/Telnet console. Network configuration can also be performed using operating system utilities (Option ROM).
For more information about the DRAC 4 software components, see "Installing the Software on the Managed System."
To install your DRAC 4 software, perform the following steps in their numbered order:
To configure your DRAC 4 software, perform the following steps in their numbered order. All configuration steps can be performed using the Web-based interface, racadm CLI, or Serial/Telnet console. Network configuration can also be performed using operating system utilities (Option ROM).
![]() |
NOTICE: Unexpected results may occur if you use more than one of the following configuration methods simultaneously: Web-based interface, racadm CLI, or Option ROM. |
![]() |
NOTE: For basic information about using the Red Hat Enterprise Linux operating system, see "DRAC 4 Software Basics for Red Hat Enterprise Linux." |
![]() |
NOTE: The Sun Java plug-in is only required if you are using the Console Redirection feature. |
Installing software on the managed system is optional. Without managed system software, you will lose the ability to use the racadm CLI locally, and for the system to capture the last crash screen.
To install the managed system software, install the software on the managed system using the Dell Systems Management Consoles CD. For instructions about how to install this software, see your Quick Installation Guide or Server Administrator User's Guide.
Managed system software will install your choices from the following components on the managed system: the appropriate version of Server Administrator and the appropriate DRAC 4 agent or only the DRAC 4 agent.
![]() |
NOTE: Do not install the DRAC 4 management station software and the DRAC 4 managed system software on the same system. |
Depending on the operating system, the DRAC 4 agent consists of either Microsoft Windows services, Novell NLMs, or Red Hat Enterprise Linux agents. The DRAC 4 agent automatically starts when you boot the managed system. If you install only the DRAC 4 agent, you will not have the ability to view the system's last crash screen or use the Watchdog feature. For more information about the last crash screen, see "Viewing the Last System Crash Screen." For more information about the Watchdog feature, see "System Information."
Before the DRAC 4 can capture the last crash screen, you must configure the managed system with the following prerequisites.
The last crash screen is not available when the Watchdog recovery action is set to Shutdown or Power Cycle if the managed system is powered off.
To ensure that the DRAC 4 Web-based interface last crash screen feature works properly, you must disable the Automatic Reboot option on managed systems running the Microsoft Windows Server 2003 and Windows 2000 Server operating systems.
Install the software, including Server Administrator, on the management station using the Dell Systems Management Consoles CD.
For instructions about installing Server Administrator software, see your Server Administrator User's Guide.
You must install the racadm CLI on a management station running Red Hat Enterprise Linux so that the remote racadm functions can be used.
![]() |
NOTE: The racadm CLI utility is installed automatically for all other supported operating systems when you install the Dell Systems Management Consoles CD. |
To install the racadm CLI utility, insert the Dell Systems Management Consoles CD in the management station's CD drive and type the following commands from a command prompt:
mount /mnt/cdrom
cd /mnt/cdrom
rpm -ivh linux/rac/*.rpm
For help with the racadm command, type the man racadm or racadm help command after issuing the previous commands. For more information about the racadm CLI, see "Using the serial and racadm Commands."
You can uninstall the racadm CLI by issuing the following command from a command prompt:
- rpm -e racadm
The following sections provide instructions for configuring the supported Web browsers. For a list of supported Web browsers, see "Supported Web Browsers."
If you are connecting to the DRAC 4 Web-based interface from a management station that connects to the Internet through a proxy server, you need to configure the Web browser to connect properly.
When using Internet Explorer on systems running Microsoft Windows to view localized versions of the DRAC 4 Web-based interface, do the following:
All browsers must have the supported Sun Java plug-in 1.4.2 or later installed to use the DRAC 4 Console Redirection feature.
Prior to using Console Redirection, you must install the supported Sun Java plug-in and also clear and disable the Java cache from the Java plug-in control panel on Windows systems.
To install the Sun java plug-in, go to http:\\java.sun.com, download JRE 1.4.2 or later, and follow the instructions on screen.
To clear the Java cache on a Windows operating system, perform the following steps:
![]() |
NOTE: For a list of the latest supported Java Virtual Machine (JVM) plug-ins, see the racread.txt file on your Dell Systems Management Consoles CD or at the Dell Support website at support.dell.com. |
You must install the Java plug-in 1.4.2 or later to use the DRAC 4 Virtual KVM feature with the Mozilla Web browser. Perform the following steps to install JRE:
chmod a+x j2re-1_4_<version number>-linux-i586-rpm.bin
./j2re-1_4_<version number>-linux-i586-rpm.bin
The script displays a binary license agreement, which you are prompted to accept before continuing the installation. After you have accepted the license agreement, the installation script creates the file j2re-1_4_<version number>-linux-i586.rpm in the current directory.
rpm -iv j2re-1_4<version number>-linux-i586.rpm
Only one Java plug-in can be registered at a time. If you have never registered a Java plug-in, go to the next step; otherwise, go to step 5.
Most Mozilla installations use symbolic links to where the Java plug-in is located. The name of the symbolic link is libjavaplugin_oji.so, which is in the /plugins subdirectory of Mozilla.
For example:
cd /usr/lib/mozilla<version number>/plugins
rm libjavaplugin_oji.so
Locate the libjavaplugin_oji.so file in the j2re1.4<version number> directory. Usually it is located in the /i386/ns600 or /i386/ns610 subdirectory. Use the create a symbolic link feature in Mozilla that points to the libjavaplugin_oji.so file in the /i386/ns610 subdirectory.
For example:
cd <Mozilla>/plugins
ln s j2re1.4<version number>/plugin/i386/ns610/libjavaplugin_oji.so libjavaplugin_oji.so
![]() |
NOTE: Create the link using the /plugins subdirectory of Mozilla. You cannot create the link from <JRE> directory. |
The version of JRE is displayed at the top of the Java Console window. If the version that is shown is not the same as the one you downloaded, then registration did not work. The same is true if the Java Console menu option is grayed out.
You can configure all of the DRAC 4 properties (network, users, alerts, etc.) using the Web-based interface, or racadm CLI.
For more information about how to use the Web-based interface, see "Accessing the Web-Based Interface." For more information about how to use the racadm CLI through a serial or telnet see "Using the serial and racadm Commands."
![]() |
NOTICE: Changing your DRAC 4 Network settings may disconnect your current network connection. |
Configure the DRAC 4 network settings using one of the following tools:
![]() |
NOTE: If you are deploying the DRAC 4 in a Red Hat Enterprise Linux environment, see "Installing the racadm CLI on a Red Hat Enterprise Linux Management Station." |
The DRAC 4 contains an integrated NIC that has a default address of 192.168.0.120 and a default gateway of 192.168.0.1. Perform the following steps to use the DRAC 4 IDE Option ROM utility to configure these settings and a limited number of additional DRAC 4 network settings.
The Setup screen appears. Below the screen title is the Network Interface Properties menu.
Virtual Media settings are on page two. Use the <Page Up> and <Page Down> keys to move between the two pages.
![]() |
NOTE: When modifying any of the following options, you can press <Esc> while typing the value to avoid modifying the current value. If you press <Option Edit> and it toggles a setting (changes the setting between only two possible values), press <Option Edit> again to change the value back to the original setting. Pressing <Esc> will not undo a modification after you type a new value. Toggle options are not affected when you press <Esc>. |
Table 2-1. DRAC 4 IDE Option ROM Utility Properties
IMPORTANT: In order for your changes to take effect, they need to be saved. Your computer will then continue booting normally.
Would you like to save the changes and continue now(<Y> or <N>)?
Or if Virtual Media settings have changed, the following message appears:
IMPORTANT: In order for your changes to take effect, they need
to be saved. For Virtual Media settings to take effect, a reboot is required.
Would you like to save the changes and reboot now (<Y> or <N>)?
![]() |
NOTE: When the DRAC 4 registers with the DNS server, it adds an extra line with a long string of characters. This TXT entry in the database is an encrypted string that is used to uniquely identify the owner of the DDNS entry and to serialize update operations. The TXT entry is associated with the RAC DDNS name. |
![]() |
NOTE: The DRAC 4 DDNS implementation requires that DNS servers be configured to allow non-secure updates. |
Add and configure DRAC 4 users using one of the following tools:
![]() |
NOTE: DRAC 4 Alert information in Management Information Base (MIB) format can be found in the rac_host MIB. |
Add and configure SNMP alerts using one of the following tools:
![]() |
NOTICE: Updating your DRAC 4 firmware may disconnect your current network connection. |
Use one of the following methods to update your DRAC 4 firmware.
![]() |
NOTE: You must add and configure a DRAC 4 user before using the Web-based interface, racadm CLI, or Serial/Telnet consoles to update your firmware. |
![]() |
NOTICE: The Repair utility is only supported when used locally. |
After you perform a firmware upgrade, perform the following instructions to clear the Web browser cache to ensure that all new Web-based interface pages are loaded.
This section provides information about how to access the DRAC 4 after the hardware is installed and the software is configured.
After you configure the DRAC 4, you can remotely access the managed system using one of four remote access interfaces. Table 2-2 describes each of the DRAC 4 interfaces.
|
Interface |
Description |
|---|---|
Enables you to remotely access the managed system using a supported Web browser through the DRAC 4 NIC. For a list of supported Web browsers, see "Supported Web Browsers." | |
Allows you to connect to the managed system and execute racadm commands from a remote console (racadm remote capability option [-r]), or management station using only the IP address of the managed system. NOTE: The racadm remote capability is supported only on management stations running Windows Server 2003, Windows 2000 Server, Windows XP Professional, Windows 2000 Professional, and Red Hat Linux operating systems. | |
Provides access through the DRAC 4 to the server COM1 port, video, and hardware management interfaces through the DRAC 4 NIC and provides support for serial and racadm commands including powerdown, powerup, powercycle, hardreset, graceshutdown, and gracereboot commands. | |
Provides the same capabilities as the telnet console using an encrypted transport layer for higher security. | |
Provides access through the DRAC 4 to the server COM1 port, and hardware management interfaces through the serial connector. The terminal emulation software provides support for serial and racadm commands including powerdown, powerup, powercycle, hardreset, graceshutdown, and gracereboot commands. |
![]() |
NOTE: The DRAC 4 default user name is root and the default password is calvin. |
You can access the DRAC 4 Web-based interface through the DRAC 4 NIC by using a supported Web browser, or through Server Administrator or IT Assistant.
To access the DRAC 4 using a supported Web browser, type the IP address of the DRAC 4. Log in with your DRAC 4 user name and password (the default user name and password are root and calvin respectively). For more information about using the DRAC 4 remote access interface, see the remote access interface online help.
To access the DRAC 4 remote access interface using Server Administrator, first 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 about using Server Administrator remote access features, see your Server Administrator User's Guide.
For information about accessing the DRAC 4 using the racadm CLI, see "Using the serial and racadm Commands."
The DRAC 4 is supported on precompiled kernels that are a part of the Red Hat Enterprise Linux distribution. The DRAC 4 is not supported on recompiled kernels with other configuration options (for example, kernels configured for performance-tuning purposes).
![]() |
NOTICE: Red Hat Enterprise Linux may fail to load when started on recompiled kernels. If this situation occurs, you must either restore the kernel and modules from backup, or you must reinstall the kernel from the Red Hat Package Manager (RPM). |
The following list describes basic software information for using a DRAC 4 with the Red Hat Enterprise Linux operating system:
service racsvc status
service racsvc <action>
where <action> is start, stop, status, or probe.
man racsvc
![]() |
NOTE: All three services (racser, racsrvc, and racvnc) start automatically when they are installed and when the system is booted. These services stop automatically when they are uninstalled or when the system is shut down. |
rpm -q <package_name>
rpm -ql <package_name>
rpm -e <package_name>
The removal of expansion cards, such as the DRAC 4, is documented in the Installation and Troubleshooting Guide that came with your system.
You must uninstall Server Administrator to remove the RAC module that was installed with Server Administrator. Use Add or Remove Programs to uninstall Server Administrator.
You must also remove the RAC drivers from all locations in your device manager. To do so, go to Control Panel and click System → Hardware → Device Manager.
For each of the following drivers, select the device, and then click Action→ Uninstall.
In addition, review all Active Directory RAC Objects associated with the removed DRAC 4 expansion card to ensure proper security.