The DRAC 4 provides a Web-based interface and the racadm CLI (command-line interface) that allows you to configure the DRAC 4 properties and users, perform remote management tasks, and troubleshoot a remote (managed) system for problems. For everyday systems management, you will use the DRAC 4 Web-based interface. This chapter provides information about how to perform common systems management tasks with the DRAC 4 Web-based interface and provides links to the information you may need.
All Web-based interface configuration tasks can also be performed with the racadm CLI. For a list of all racadm CLI and serial/telnet console commands that can be used to perform the text-based equivalents of each task, see "Using the serial and racadm Commands."
NOTE: When you are working in the Web-based interface, see your DRAC 4 online help for context sensitive information about each Web-based interface page.
Accessing the Web-Based Interface
To link to the DRAC 4 remote Web-based interface Log in window, open your Web browser and type https://<IP address>:<port number> (where IP address is the IP address for the DRAC 4 and port number is the HTTPS port number if it has been changed) in the address field and press <Enter>. The DRAC 4 Log in window appears.
Logging In
NOTE: To log in, you must have Log In to DRAC 4 permission.
You can log in as either a DRAC 4 user or as an Active Directory user. To log in, perform the following steps.
NOTE: The default user name and password are "root" and "calvin."
In the User Name field, enter either your DRAC 4 user name as <username>, or Active
Directory user name as <domain>\<username>, <domain>/<username>, or
<user>@<domain>. The DRAC 4 user name for local users is case sensitive; the Active
Directory user name is not case sensitive. Examples of an Active Directory user name are:
dell.com\john_doe or john_doe@dell.com.
In the Password field, enter your DRAC 4 user password or Active Directory user password.
This field is case sensitive. You can also use the <Tab> key to navigate to this field.
Click OK or press <Enter>.
Logging Out
Click Log Out in the upper-right corner of the main window.
NOTE: The Log Out button does not appear until you log in.
Adding and Configuring DRAC 4 Users and Alerts
To manage your system with the DRAC 4, you may want to create unique users with specific administrative permissions (role-based authority). You can also configure alerts to be emailed to different users.
This section provides instructions about how to perform the following tasks:
Use the Add/Configure DRAC 4 User page to configure the user name, password, access
permissions, and email alert settings for a new or existing DRAC 4 user.
Configuring a New User Name and Password
Use Table 4-1 to configure a new or existing DRAC 4 user name and password.
Table 4-1. User Properties
Property
Description
User Name
Allows you to specify a DRAC 4 user name. (Once the user name is specified, you cannot change it. A new user must be created with a different user name.)
NOTE: User names on the local DRAC 4 must not contain the / (forward slash)or . (period) characters.
Password
Allows you to specify or edit the DRAC 4 user's password.
Confirm New Password
Requires you to retype the DRAC 4 user's password to confirm.
Configuring User Permissions
Under User Permissions, click the User Group drop-down menu and select the permissions group for the user.
Use Table 4-2 to determine the User Group (permissions) for the user.
Table 4-2. User Group Permissions
User Group
Permissions Granted
Administrator
Login to DRAC 4, Configure DRAC 4, Configure Users, Clear Logs, Execute Server Control Commands, Access Console Redirection, Access Virtual Media, Test Alerts, Execute Diagnostic Commands, and receive email alerts (if Enabled)
Power User
Login to DRAC 4, Clear Logs, Execute Server Control Commands, Access Console Redirection, Access Virtual Media, Test Alerts, and receive email alerts (if Enabled)
Guest User
Login to DRAC 4, and receive email alerts (if Enabled)
email Alerts Only
Receive email alerts (if Enabled)
Custom
Allows you to select any combination of the following permissions: Login to DRAC 4, Configure DRAC 4, Configure Users, Clear Logs, Execute Server Action Commands, Access Console Redirection, Access Virtual Media, Test Alerts, Execute Diagnostic Commands, and receive email alerts (if Enabled)
Configuring User email Alerts
Enabling User email Alerts
Use the information in Table 4-3 to enable email alerts.
Table 4-3. Enable email Alert Properties
Property
Description
Enable email Alerts
Enables the DRAC 4 email alerts feature and allows you to select which events, according to their severity, will cause an email alert to be sent.
email Address
Allows you to specify the email address to which alerts are sent.
Message
Allows you to specify the email message text.
Configuring email Alerts by Severity
The information under email Alerts in the Web-based interface enables you to select which events, according to their severity, will cause an email alert to be sent. Select the severity of the temperature, voltage, fan, or miscellaneous sensor for which you want an email alert generated. You can specify three severities: Informational (lowest severity), Warning (medium severity), and Severe (highest severity). Alerts will be sent to the email address you typed in Enabling User email Alerts. For information about each email alert severity type, see Table 4-4.
Table 4-4. email Alert Severity
Severity
Description
Informational
Select the check boxes in this column to cause the DRAC 4 to send an alert if the corresponding event listed under Alert Description occurs with a severity of Informational.
Warning
Select the check boxes in this column to cause the DRAC 4 to send an alert if the corresponding event listed under Alert Description occurs with a severity of Warning.
Severe
Select the check boxes in this column to cause the DRAC 4 to send an alert if the corresponding event listed under Alert Description occurs with a severity of Severe.
Alert Description
Lists the following events monitored by the DRAC 4. A specified alert (either Informational, Warning, or Severe) is sent when the event is triggered at the level of severity you selected in the check boxes to the left.
Select All — Monitors all of the sensors available on the system.
System Temperature Sensors — Monitors the system temperature sensors.
System Voltage Sensors — Monitors the system voltage sensors.
System Fan Sensors — Monitors the system fan speed (RPM).
System Miscellaneous Sensors — Monitors other available system sensors such as chassis intrusion.
Apply Changes
Adds a new DRAC 4 user or commits changes made to the current DRAC 4 user.
Go Back To User Configuration Page
Opens the DRAC 4 Users page.
Printing the Page
Click the Print button in the top-right corner of the screen if you want to print the Add/Configure DRAC 4 User page.
Configuring the DRAC 4 NIC
Click the Configuration tab and select Network.
Use the Network Configuration page to configure the DRAC 4 NIC settings and configure
email alert settings. Table 4-5 describes each setting on the Network Configuration page.
Table 4-6 describes the NetworkConfigurationpage buttons.
NOTE: To change any of the settings on the Network Configuration page, you must have Configure DRAC 4 permission.
NOTE: Assigning a predefined IP address to the DRAC 4 using a DHCP server: most DHCP servers require a client identifier token to be stored in the server's reservations table. The client (DRAC 4, for example) has to provide that token during the DHCP negotiation phase. In the case of RACs, the DRAC 4 supplies the client identifier option as follows: a one-byte interface number (0) followed by a six-byte MAC address.
Enables the DRAC 4 NIC and activates the remaining controls in this group.
Use DHCP (For NIC IP Address) (check box is not selected: default)
Causes Server Administrator to obtain the IP address for the DRAC 4 NIC from the Dynamic Host Configuration Protocol (DHCP) server; selecting the check box deactivates the Static IP Address, Static Gateway,and Static Subnet Mask controls.
Static IP Address
Specifies or edits the static IP address for the DRAC 4 NIC. To change this setting, you must first deselect the Use DHCP (For NIC IP Address) check box.
Static Gateway
Specifies or edits the static gateway for the DRAC 4 NIC. To change this setting, you must first deselect the Use DHCP (For NIC IP Address) check box.
Static Subnet Mask
Specifies or edits the static subnet mask for the DRAC 4 NIC. To change this setting, you must first deselect the Use DHCP (For NIC IP Address) check box.
Use DHCP to obtain DNS server addresses (check box is not selected: default)
Causes the primary and secondary DNS server addresses to be obtained from the DHCP server, rather than the static settings, when TRUE.
Static Preferred DNS Server
Causes the IP address of the primary DNS server to be used only when Use DHCP to obtain DNS server addresses is not selected.
Static Alternate DNS Server
Causes the IP address of the secondary DNS server to be used 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 4 on DNS(check box is not selected: default)
Enables registering the DRAC 4 name on the DNS server. If you enable this option by checking the check box, the DRAC 4 name is registered on the DNS server.
DNS DRAC 4 Name
Displays the DRAC 4 name only when Register DRAC 4 on DNS is selected. The default DRAC 4 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 (check box is not selected: default)
Specifies using the default DNS domain name when the check box is not selected. When the check box is not selected and the Register DRAC 4 on DNS check box is selected, you can modify the DNS domain name in the DNS Domain Name field.
DNS Domain Name
The default DNS domain name is MYDOMAIN. When the Use DHCP for DNS Domain Name check box is selected, you cannot modify this field and it is "dimmed-out." If the check box is not selected, you can modify the DNS domain name.
Auto Negotiation
Determines whether the DRAC 4 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).
Duplex Mode
Enables you to set the duplex mode to full or half to match your network environment. This option is not available if Auto Negotiation is set to On.
Network Speed
Enables you to set 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.
GUI Session Time-out
Enables you to specify the time (from 5 to 60 minutes in 5-minute intervals) before the session screen is locked. You must re-type your password to unlock and resume the session.
Apply
Saves the changes made to the network configuration.
Email Alert Settings
Enables email messaging and activates the SMTP (email) Server Address control.
Enable Email Alerts (check box is selected: default)
Enables email messaging.
SMTP (Email) Server Address
Specifies or edits the IP address of the SMTP server to which you want all email messages to be sent.
Saves the changes made to the network configuration.
Adding and Configuring SNMP Alerts
NOTE: You must have Configure DRAC 4 permission to add or delete an SNMP alert; otherwise, these options will not be available.
Click the Configuration tab and select Alerts.
Use the Add/Configure SNMP Alerts page to add, delete, configure, and test SNMP alerts.
NOTE: The DRAC 4 supports three severity levels: Informational, Warning, and Severe. Some events support only the informational severity level because they deliver only a message.
Adding an Alert
Locate an available Destination IP Address in the Destination IP Address column.
If all Destination IP Addresses are filled with existing IP addresses, you have configured all of your existing alerts and must delete one to continue.
Click [Available] to open the Add/Configure SNMP Alerts page.
Use Table 4-7 to configure the following properties under General.
Table 4-7. Alert Properties
Property
Description
Enable SNMP Alert
Determines whether you want to enable the current SNMP alert.
Community
Specifies or edits the community name to which the destination IP address belongs.
IP Address
Specifies or edits the destination IP address to which the alert is sent.
Apply Changes
Commits changes made to the current alert.
Go Back To SNMP Alerts Page
Returns you to the Configure SNMP Alerts page.
Configuring Alerts by Severity
Use the Severity Configuration section to select which events, according to their severity, will
cause an SNMP alert to be sent to the IP address you typed in Configuring Alert Properties.
Place a check under the severity of the sensor for which you want an SNMP alert generated.
Use Table 4-8 to decide which events you want to cause an SNMP alert.
Table 4-8. Severity Options
Option
Description
Informational
Select the check boxes in this column to cause the DRAC 4 to send an alert if the corresponding event listed under Alert Description occurs with a severity of Informational (lowest severity).
Warning
Select the check boxes in this column to cause the DRAC 4 to send an alert if the corresponding event listed under Alert Description occurs with a severity of Warning (medium severity).
Severe
Select the check boxes in this column to cause the DRAC 4 to send an alert if the corresponding event listed under Alert Description occurs with a severity of Severe (highest severity).
Alert Description
Lists the following events monitored by the DRAC 4. An alert (specified as either informational, warning, or severe) is sent when the event is triggered at the level of severity you selected in the check boxes to the left.
NOTE: For information about how to manage events, see the Server Administrator User's Guide.
Select All — Monitors all of the sensors available on the system.
System Temperature Sensors — Monitors the temperature sensors on the system.
System Voltage Sensors — Monitors the voltage sensors on the system.
System Fan Sensors — Monitors the system fan speed (RPM).
System Miscellaneous Sensors — Monitors other available system sensors such as chassis intrusion.
Viewing Information About Existing Alerts
Click an alert in the SNMP Alert List todisplay the following properties for existing SNMP alerts. See Table 4-9 for descriptions.
NOTE: During the first 40 seconds after a DRAC 4 reset, the DRAC 4 is synchronizing with the system BMC and the managed system service. If an alert is generated during this time, some of the values may be reported as "unknown." The time field contains the number of seconds since DRAC 4 startup. After synchronization has completed, all values are reported correctly.
Table 4-9. SNMP Alert Properties
Property
Description
Enabled?
Displays (Yes or No) whether you have enabled SNMP alerts on the Add/Configure SNMP Alerts page.
Destination IP Address
If the Available link appears under Destination IP Address, click the link to open the Add/Configure SNMP Alerts page, which enables you to configure a new alert.
Displays the destination IP address to which the corresponding alert is sent. Click the IP address to open the Add/Configure SNMP Alerts window.
Community
Displays the SNMP community to which the Destination IP Address belongs.
Testing an Alert
NOTE: You must have Test Alert permission to test an alert, otherwise this option will not be available.
You can force an alert to be sent to the specified destination IP address. In the SNMP Alert List, click Test Alert next to the alert you want to test.
NOTE: Only users with Test Alerts permission will have the Test Alert option available next to their names.
Deleting an Alert
In the SNMP Alert List, click Remove Alert next to the alert you want to delete.
Other Options
The SNMP Alerts and Add/Configure SNMP Alerts pages provide the buttons in Table 4-10 in the top-right corner of the screen.
Table 4-10. SNMP Alerts Page Buttons (Top Right)
Button
Action
Print
Prints the SNMP Alerts page
Refresh
Reloads the SNMP Alerts page
Managing a Remote System
This section provides instructions about how to perform the following systems management tasks to manage a remote system:
Use the Firmware Update page to update the DRAC 4 firmware to the latest revision.
The following data is included in the DRAC 4 firmware package:
Compiled DRAC 4 firmware code and data
Expansion ROM image
Web-based interface, JPEG, and other user interface data files
Default configuration files
NOTE: The firmware update retains the current DRAC 4 settings.
NOTE: Before beginning the firmware update, you must first acquire the latest firmware version and save it on your local system. For more information about how to update your DRAC 4 firmware remotely, see your Dell Remote Access Controller 4 User's Guide.
Type the system path where the firmware image file resides (for example:
C:\Updates\V1.0\<image_name>). The default firmware image name is firmimg.dm1.
Click Update Firmware.
The update may take several minutes. When the update is completed, a dialog box appears.
Click OK to close the session and automatically log out.
After the DRAC 4 resets, click Log In to log in to the DRAC 4 again.
Ensuring DRAC 4 Network Security
The DRAC 4 uses certificate management to ensure security for your DRAC 4 network communications.
Certificate Management Overview
A CSR is a digital request to a CA for a secure server certificate. Secure server certificates ensure the identity of a remote system and ensure that information exchanged with the remote system cannot be viewed or changed by others. To ensure the security for your DRAC 4, it is strongly recommended that you generate a CSR, submit the CSR to a CA, and upload the certificate returned from the CA.
A certificate authority is a business entity that is recognized in the IT industry for meeting high standards of reliable screening, identification, and other important security criteria. Examples of CAs include Thawte and VeriSign. After the CA receives your CSR, they review and verify the information the CSR contains. If the applicant meets the CA's security standards, the CA issues a certificate to the applicant that uniquely identifies that applicant for transactions over networks and on the Internet.
After the CA approves the CSR and sends you a certificate, you must upload the certificate to the DRAC 4 firmware. The CSR information stored on the DRAC 4 firmware must match the information contained in the certificate.
NOTE: Using the DRAC 4 default certificate for SSL generates a host mismatch warning in Netscape. You must upload a CA-generated SSL certificate to the DRAC 4 for proper security.
Viewing a Server Certificate
Use the Server Certificate Information page to view a server certificate for your DRAC 4. Table 4-11 provides information about the server certificate.
Table 4-11. Server Certificate Information
Field
Description
Attribute
Value
Type
Type of certificate; server certificate
Serial
Certificate serial number
Key Size
Encryption key size
Valid From
Issuance date of the certificate
Valid To
Expiration date of the certificate
Subject
Certificate attributes entered by the subject
Issuer
Certificate attributes returned by the issuer
The buttons in Table 4-12 are available on the Viewing a Server Certificate page.
Table 4-12. View Server Certificate Page Buttons
Button
Action
Print
Prints the contents of the open window to your default printer
Go Back to Certificate Management Page
Returns to the previous page
Generating, Uploading, and Viewing a Server Certificate
Click the Configuration tab and click Security.
Use the Certificate Management page options (see Table 4-13) to generate a certificate
signing request (CSR) to send to a certificate authority (CA). The CSR information is stored
on the DRAC 4 firmware.
NOTE: You must have Configure DRAC 4 permission to generate or upload a server certificate.
Table 4-13. Certificate Management Page Options
Option
Action
Generate a New CSR
Click Next to open the Certificate Signing Request Generation page that enables you to generate a CSR to send to a CA to request a secure Web certificate.
NOTICE: Each new CSR overwrites any pervious CSR on the firmware. For a CA to accept your CSR, the CSR in the firmware must match the certificate returned from the CA.
Upload Certificate
Click Next to upload an existing certificate that your company has title to, and uses to control access to the DRAC 4.
NOTICE: Only X509, Base 64 encoded certificates are accepted by the DRAC 4. DER encoded certificates are not. Upload a new certificate to replace the default certificate you received with your DRAC 4.
View Server Certificate
Click Next to view an existing server certificate.
Generating a Certificate Signing Request
Type a value in the field for each CSR attribute. Table 4-14 describes what values are valid for
each required field.
The Email Address field is optional. You may type your company's email address, or any email address that you want to have associated with the CSR.
NOTICE: Each new CSR overwrites any previous CSR on the firmware. Before a certificate authority (CA) can accept your CSR, the CSR in the firmware must match the certificate returned from the CA, or the DRAC 4 will not upload the certificate.
Table 4-14. Required CSR Fields
Field
Description
Common Name (CN)
The exact name being certified (usually the Web server's domain name, for example, www.xyzcompany.com). Only alpha-numeric characters, hyphens, underscores, and periods are valid. Spaces are not valid.
Organization Unit (OU)
The name associated with an organizational unit, such as a department (for example, Enterprise Group). Only alpha-numeric characters, hyphens, underscores, periods, and spaces are valid.
Organization (O)
The name associated with this organization (for example, XYZ Corporation). Only alphanumeric characters, hyphens, underscores, periods and spaces are valid.
Country Code (C)
The name of the country where the entity applying for certification is located. Use the drop-down menu to select the country.
Locality (L)
The city or other location of the entity being certified (for example, Round Rock). Only alpha-numeric characters and spaces are valid. Do not separate words using an underscore or some other character.
State (S)
The state or province where the entity who is applying for a certification is located (for example, Texas). Only alpha-numeric characters and spaces are valid. Do not use abbreviations.
The buttons in Table 4-15 are available on the Certificate Signing Request Generation page.
Prints the contents of the window's data area using the default printer for your system.
Go Back to Certificate Management Page
Returns to the previous page.
Generate
Generates a CSR and then prompts you to either open it or save it in the directory you specify.
Uploading a Certificate
To upload your server certificate to the DRAC 4 firmware, type the file path of the certificate or browse to the certificate file, and click Upload.
NOTE: The File Path value displays the file path of the certificate to be uploaded. You must type the absolute file path (for example, the full path and the complete file name including the file extension).
The buttons in Table 4-16 are available on the Certificate Management page.
Table 4-16. Certificate Management Page Buttons
Button
Action
Print
Prints the contents of the Upload Certificate page data.
Go Back to Certificate Management Page
Returns to the previous page.
Upload
Uploads the certificate to the DRAC 4 firmware.
Viewing System Information
The System Summary page displays system information (see Table 4-17 through Table 4-20) and DRAC 4 session information (see Table 4-21).
NOTE: Use the scroll bar to view the entire page.
System Information
This section provides information about the types of system information.
Table 4-17. Types of System Information
Field
Description
DRAC 4 Information
Information about the DRAC 4 firmware and hardware.
System Information
Information about the system on which the DRAC 4 is installed.
Watchdog Information
Information about configured watchdog events; actions taken by the system when specific system events occur. To receive watchdog information, you must have DRAC 4 services installed on the managed system. The watchdog settings must be configured using Server Administrator. For more information, see the Server Administrator User's Guide.
Watchdog provides the same functionality as the automatic recovery feature. It is recommended that you use watchdog and disable the automatic recovery feature.
DRAC 4 Information
Table 4-18. DRAC 4 Information Fields
Field
Description
DRAC 4 Date/Time
DRAC 4 internal clock setting.
Firmware Version
Current firmware version level.
Firmware Updated
Date and time that the firmware was last updated.
Hardware Version
DRAC 4 hardware version level.
MAC Address
MAC address assigned to the DRAC 4.
Current IP Address
IP address assigned to the DRAC 4 NIC.
Current IP Gateway
IP address of the switch or router servicing the DRAC 4 NIC.
Current IP Netmask
IP address of the subnet to which the DRAC 4 is connected.
DHCP Enabled? (Default No)
Yes if DHCP is enabled on the DRAC 4. No if DHCP is disabled.
Use DHCP to Obtain DNS Server Addresses
If TRUE, the primary and secondary DNS server addresses are obtained from the DHCP server (rather than the static settings).
Static Preferred DNS Server Address
If Use DHCP to Obtain DNS Server Addresses is FALSE, the IP address of the primary DNS server is used.
Static Alternate DNS Server Address
If Use DHCP to Obtain DNS Server Addresses is FALSE, IP address of the secondary DNS server is used.
System Information
To receive OS Type, Host Name, and OS Name information, you must have DRAC 4 services installed on the managed system.
Table 4-19. System Information Fields
Field
Description
System ID
System identifier
System Model
System model and type
BIOS Version
BIOS version level
Service Tag
System service tag number, if assigned
OS Type
Type of operating system installed on the system
Host Name
Name of the managed system where the DRAC 4 is installed
OS Name
Name of the operating system installed on the DRAC 4 managed system, including version, build, and service pack information
BMC Version
Managed system firmware version
Watchdog Information
Table 4-20. Watchdog Information Fields
Field
Description
Recovery Action
Specifies whether to reset, power cycle, shut down, or to not take action if the system hangs.
Present countdown value
Number of seconds remaining before the watchdog initiates the recovery action. This value may fluctuate because it is displayed in real time.
Initial countdown value
Number of seconds from where the countdown begins.
Session Information
This section provides information about DRAC 4 sessions.
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.
Session Status
Table 4-21. Session Status Fields
Field
Description
Valid Sessions
Current number of DRAC 4 Web-based interface sessions (equal to the number of users that are logged on to the DRAC 4)
Unused Sessions
Current number of unused sessions. The DRAC 4 is capable of supporting up to 4 concurrent sessions (maximum of 4 Web sessions, 4 Telnet sessions, 1 Serial session, and 4 remote racadm CLI sessions.
Session Type
Current session type (Web, Telnet, or Serial).
Session User
Name of the user initiating the session
User's IP Address
IP address of the system from which the user is connecting to the DRAC 4
Login Date/Time
Time and date that the user logged in according to the DRAC 4 internal clock
Active Consoles
One of the following consoles per session:
Console Redirect — A console redirection session is active.
Virtual Media — A virtual media session is active.
Recovering and Troubleshooting the Managed System
This section explains how to perform tasks related to recovering and troubleshooting a crashed remote system using the DRAC 4 Web-based interface. For information about troubleshooting your DRAC 4, see "Troubleshooting."
The DRAC 4 allows you to remotely perform several power management actions on the managed system to try and recover after a system crash or other problem. Use the Server Control page to perform an orderly shutdown through the operating system when rebooting, and power the system on or off.
NOTE: You must have Execute Server Action Commands permission to perform power management actions.
Selecting Server Control Actions
Select whether to perform an Operating System Shutdown (only for the Reboot System, and
Power OffSystem,Server Control Actions).
If you want to make the system perform an orderly shutdown through the operating system before the selected Server Control Action, select Operating System Shutdown.
NOTE: To use the Operating System Shutdown option, you must first install the DRAC 4 managed system software, otherwise this option will be unavailable. For more information, see your DRAC 4 User's Guide.
Select one of the following Server Control Actions.
Reboot System — Resets the system (equivalent to pressing the reset button); the power is not turned off by using this function.
Power Cycle System — Turns off the system power and turns it on again (equivalent to pressing the power button twice).
Power Off System — Turns off the system power (equivalent to pressing the power button).
Power On System — Turns on the system power (equivalent to pressing the power button).
Click Apply to perform the power management action (for example, cause the system to
power cycle).
Other Options
The Server Control page provides buttons (see Table 4-22) in the top-right corner of the screen.
Table 4-22. Server Control Page Buttons (Top Right)
Button
Action
Print
Prints the Server Control page
Refresh
Reloads the Server Control page
Using the SEL
The System Event Log (SEL) page displays system-critical events that occur on the managed system. The SEL is generated by the Baseboard Management Controller (BMC) on the managed system and by the DRAC 4 if you have configured it to monitor any managed system events. This page displays the date, time, and a description of each event generated by the BMC and other instrumentation on the managed system. You can configure the DRAC 4 to send email or SNMP alerts when specified events occur.
The SEL displays the event severity information in Table 4-23.
The DRAC 4 Log provides the following information.
Table 4-23. Status Indicator Icons
A green check mark indicates a healthy (normal) status condition.
A yellow triangle containing an exclamation point indicates a warning (noncritical) status condition.
A red X indicates a critical (failure) status condition.
A blank space indicates that the status is unknown.
Date/Time
The date and time that the event occurred
Description
A brief description of the event
The SEL provides buttons (see Table 4-24) in the top-right corner of the screen.
NOTE: The Clear Log button only appears if you have Clear Logs permission.
Table 4-24. SEL Buttons (Top Right)
Button
Action
Print
Prints the SEL.
Clear Log
Clears the SEL.
Save As
Opens a pop-up window that enables you to save the SEL to a directory of your choice.
Refresh
Reloads the SEL page.
Using the DRAC 4 Log
The DRAC 4 Log is a persistent log maintained in the DRAC 4 firmware. The log contains a list of user actions (such as log in and log out) and alerts issued by the DRAC 4. The oldest entries are overwritten when the log becomes full. If the DRAC 4 loses communication with the managed system, all entries that the DRAC 4 would have added to the System Event Log (SEL), such as a power failure, are added to the DRAC 4 Log until communication is re-established.
The DRAC 4 Log provides the information in Table 4-25.
Table 4-25. Status Indicator Icons
A green check mark indicates a healthy (normal) status condition.
A yellow triangle containing an exclamation point indicates a warning (noncritical) status condition.
A red X indicates a critical (failure) status condition.
A blank space indicates that the status is unknown.
Date and Time — The date and time (for example, Sat Dec 19 16:55:47 2004). When the DRAC 4 is unable to communicate with the managed system, the letters DSU (DRAC 4 start up) appear before the time, followed by the time elapsed since the DRAC 4 was started.
User — The name of the user logging into the DRAC 4.
ID — The event identification number of the message displayed.
Description — A brief description of the event.
Using the DRAC 4 Log Page Buttons
The DRAC 4 Log page provides the following buttons (see Table 4-26).
Table 4-26. DRAC 4 Log Buttons
Button
Action
Print
Prints the DRAC 4 Log page.
Clear Log
Clears the DRAC 4 Log entries.
NOTE: The Clear Log button only appears if you have Clear Logs permission.
Save As
Opens a pop-up window that enables you to save the DRAC 4 Log to a directory of your choice.
Refresh
Reloads the DRAC 4 Log page.
Viewing the Last System Crash Screen
NOTICE: To capture the last crash screen, you must have managed system software installed.
Use the Last Crash Screen page to view the most recent crash screen, which allows you to obtain information about events leading up to the system crash. Last system crash information is saved in DRAC 4 memory and is remotely accessible. The date of the system crash appears on the last crash screen.
The Last Crash Screen page provides the following buttons (see Table 4-27) in the top-right corner of the screen:
Table 4-27. Last Crash Screen Page Buttons
Button
Action
Print
Prints the Last Crash Screen page.
Save As
Opens a pop-up window that enables you to save the Last Crash Screen to a directory of your choice.
Refresh
Reloads the Last Crash Screen page.
Delete Last Crash Screen
Deletes the Last Crash Screen page.
NOTE: Due to fluctuations in the watchdog timer, the Last Crash Screen has a higher probability of not being captured when the ASR is set to a value less than 30 seconds. Use Server Administrator or IT Assistant to set the System Reset Timer to at least 30 seconds to ensure that the Last Crash Screen functions properly. See "Configuring the Managed System to Capture the Last Crash Screen" for additional information.
Using the Diagnostic Console
The DRAC 4 provides a standard set of network diagnostic tools, similar to those found on Microsoft® Windows® or Red Hat® Linux-based systems. Using the DRAC 4 Web-based interface, you can access the following network debugging tools by clicking the Diagnostics tab.
The Diagnostic Console allows you to perform debugging tasks and paging. Table 4-28 shows the options that are available on the Diagnostic Console page.
NOTE: After entering one of the following commands, click Submit. The results of the debugging tasks are displayed in the Results of the Diagnostic Command box at the bottom of the page.
Table 4-28. Diagnostic Commands
Command
Description
arp
Displays the contents of the Address Resolution Protocol(ARP) table. ARP entries may not be added or deleted.
ifconfig
Displays the contents of the network interface table.
netstat
Prints the content of the routing table. If the optional interface number is provided in the text field to the right of the netstat option, then netstat prints additional information regarding the traffic across the interface, buffer usage, and other network interface information.
ping <IP Address>
Verifies that the destination IP address is reachable from the DRAC 4 with the current routing-table contents. A destination IP address must be entered in the field to the right of this option. An ICMP (Internet control message protocol) echo packet is sent to the destination IP address based on the current routing-table contents.
getcoredump
Displays the last controller crash, including detailed information such as register values and a memory map recorded when the most recent controller crash occurred; displays the message "No CORE dump available" if no previous controller crash has occurred or if the data has been deleted.
settracelog
Enables you to set debug trace levels to identify the types of messages being sent on the local network. The -d option traces the DHCP packets sent and received. The -i option traces IP packets sent and received. For example, type settracelog -i to trace IP packets sent and received.
gettracelog
Displays a UNIX®-style system log. This log is a volatile, memory-resident log that contains time-stamped entries.
nettrace
Enables you to view your current trace log settings.
The Diagnostic Console page provides buttons (see Table 4-29) in the top-right corner of the screen.
The internal DRAC 4 Trace Log can be used by administrators to debug alerting, or networking from the DRAC 4. The Trace Log can be accessed from the DRAC 4 Web-based interface by clicking the Diagnostics tab, and typing the gettracelog command. The Trace Log will appear and tracks the following information:
DHCP – Traces packets sent to and received from a DHCP server.
IP – Traces IP packets sent and received.
NOTE: In the DRAC 4 Trace Log, nonprintable ASCII characters are translated to printable ASCII characters. If the character code is less than 0x20, or between 0x7f and 0xa0 (inclusive), the value 0x40 is exclusive and the character before printing, after a "^" is added to the beginning. As a result, the ASCII carriage return character, 0xd, is printed as "^M" in the Trace Log.
NOTE: The DRAC 4 will not echo an ICMP (ping) with a packet size larger than 1500 bytes.
The trace log may also contain DRAC 4 operating-system specific error codes (relating to the internal DRAC 4 operating system, not the managed system's operating system). Use Table 4-30 to help diagnose network problems reported by the internal DRAC 4 operating system.
Table 4-30. DRAC 4 Network Error Codes
Error Code
Description
0x5006
ENXIO: No such address.
0x5009
EBADS: The socket descriptor is invalid.
0x500D
EACCESS: Permission denied.
0x5011
EEXIST: Duplicate entry exists.
0x5016
EINVALID: An argument is invalid.
0x5017
ENFILE: An internal table has run out of space.
0x5020
EPIPE: The connection is broken.
0x5023
EWOULDBLOCK: The operation would block; socket is nonblocking.
0x5024
EINPROGRESS: Socket is nonblocking; connection not completed immediately.
0x5025
EALREADY: Socket is nonblocking; previous connection attempt not complete.
0x5027
EDESTADDRREQ: The destination address is invalid.
0x5028
EMSGSIZE: Message too long.
0x5029
EPROTOTYPE: Wrong protocol type for socket.
0x502A
ENOPROTOOPT: Protocol not available.
0x502B
EPROTONO SUPPORT: Protocol not supported.
0x502D
EOPNOTSUPP: Requested operation not valid for this type of socket.
0x502F
EAFNOSUPPORT: Address family not supported.
0x5030
EADDRINUSE: Address is already in use.
0x5031
EADDRNOTAVAIL: Address not available.
0x5033
ENETUNREACH: Network is unreachable.
0x5035
ECONNABORTED: The connection has been aborted by the peer.
0x5036
ECONNRESET: The connection has been reset by the peer.
0x5037
ENOBUFS: An internal buffer is required but cannot be allocated.
0x5038
EISCONN: The socket is already connected.
0x5039
ENOTCONN: The socket is not connected.
0x503B
ETOOMANYREFS: Too many references, cannot splice.
0x503C
ETIMEDOUT: Connection timed out.
0x503D
ECONNREFUSED: The connection attempt was refused.
0x5041
EHOSTUNREACH: The destination host could not be reached.
0x5046
ENIDOWN: NI_INIT returned -1.
0x5047
ENMTU: The MTU is invalid.
0x5048
ENHWL: The hardware length is invalid.
0x5049
ENNOFIND: The route specified cannot be found.
0x504A
ECOLL: Collision in select call; these conditions already selected by another task.
0x504B
ETID: The task ID is invalid.
Troubleshooting Alerting Problems
You can use logged SNMP trap information to troubleshoot a particular type of DRAC 4 alert. SNMP trap deliveries are logged in the Trace Log by default. However, since SNMP does not confirm delivery of traps, it is best to trace the packets on the managed system using a network analyzer or a tool such as Microsoft's snmputil.
DRAC 4 Log Messages
DRAC 4 Log messages can be used by administrators to debug alerting from the DRAC 4. Table 4-31 provides a list of the DRAC 4 log message ID numbers, messages, and suggested actions to take.
NOTE: In Table 4-31, the character "L" is sometimes displayed in the Message ID column. "L" represents the severity level or type of the message, which can be one of the following: W (warning), E (error), S (severe), F (fatal), or A (always).
Table 4-31. DRAC 4 Log Messages
Message ID
Description
Suggested Action
RAC186W
DHCP: no response from server, need LAN address. The NIC cannot be enabled until a response is received from the DHCP server.
Provides information only. No specific corrective action is indicated. Ensure that the DHCP server is operational.
RAC188W
DHCP: no response from server, warm starting with <IP address>.
Provides information only. No specific corrective action is indicated. Ensure that the DHCP server is operational.
RAC189A
Email page successful.
Provides information only. No corrective action is necessary.
RAC191E
SNMP: internal failure during trap generation
Resets the DRAC 4 and retries the operation.
RAC198A
SNMP: trap sent to <IP address>
Provides information only. No corrective action is necessary.
A trace of the SMTP connection may be found in the trace log. Examine the trace log to identify the source of the protocol failure, such as the connection could not be established (SMTP server is down or an invalid IP address), an invalid email destination address, an invalid domain in the email address, or the SMTP server does not support forwarding email. Correct the problem and try again.
Provides information only. No corrective action is necessary, unless the contents of the hardware log indicate a problem. In this case, the corrective action is based on the problem reported.
RAC016A
DRAC 4 log cleared
Provides information only.
RAC030A
DRAC 4 time was set
Provides information only.
RAC048A
DRAC 4 firmware update was initiated.
Provides information only.
RAC049A
DRAC 4 Firmware Update was initiated with config to defaults option.
Provides information only.
RAC064A
clear crash screen
Provides information only.
RAC065A
DRAC 4 hard reset, delay <seconds> was initiated
Provides information only.
RAC066A
DRAC 4 soft reset, delay <seconds> was initiated
Provides information only.
RAC067A
DRAC 4 graceful reset, delay <seconds> was initiated
Provides information only.
RAC068A
DRAC 4 cfg2default reset, delay <seconds> was initiated
Provides information only.
RAC069A
DRAC 4 shutdown was initiated
Provides information only.
RAC114A
Requested server {powerdown|powerup| powercycle|hardreset| graceshutdown|gracereboot| gracereboot}
Provides information only.
RAC115A
Could not log graceful server action to hardware log
Provides information only.
RAC122A
DRAC 4 booted
Provides information only.
RAC138A
Console redirect session enabled
Provides information only.
RAC139A
Console redirect session disabled
Provides information only.
RAC154A
Logout from <IP-address>
Provides information only.
RAC155A
Login from <IP-address>
Provides information only.
RAC156A
Session cancelled from <IP-address>, max log in attempts exceeded.
Provides information only.
RAC157A
Session cancelled from <IP-address>, due to inactivity.
Provides information only.
RAC158A
Nonvalidated session from <IP-address> cancelled.
Provides information only.
RAC159A
Start console redirection.
Provides information only.
RAC160A
End console redirection.
Provides information only.
RAC161E
Maximum sessions exceeded.
Wait until another user closes a session.
RAC162E
Maximum per user connections exceeded.
Close one of your sessions.
RAC163E
User lacks permission.
Close one of your sessions.
Frequently Asked Questions
Table 4-32 lists frequently asked questions and answers.
Table 4-32. Managing and Recovering a Remote System: Frequently Asked Questions
Question
Answer
The following message is displayed for unknown reasons:
Remote Access: SNMP Authentication Failure
Why does this happen?
As part of discovery, IT Assistant attempts to verify the get and set community names of the device. In IT Assistant, you have the get community name = public and the set community name = private. By default, the community name for the DRAC 4 agent is public. When IT Assistant sends out a set request, the DRAC 4 agent generates the SNMP authentication error because it will only accept requests from community = public.
You can change the DRAC 4 community name using the racadm command line utility.
To see the DRAC 4 community name, use the following command:
racadm getconfig -g cfgOobSnmp
To set the DRAC 4 community name, use the following command:
To prevent SNMP authentication traps from being generated, you must input community names that will be accepted by the agent. Since the DRAC 4 only allows one community name, you must input the same get and set community name for IT Assistant discovery setup.
Why are the remote racadm and Web-based services unavailable after a property change?
It may take several minutes for the remote racadm services and the Web-based interface to become available again after a reset of the DRAC 4 Web server
The DRAC 4 Web server is reset after the following occurrences:
When the cfgRacTuneHttpsPort property is changed (including when a config -f <config file> changes it)
When racresetcfg is used
When the DRAC 4 is reset
When accessing the DRAC 4 Web-based interface, I get a security warning stating the hostname of the SSL certificate does not match the hostname of the DRAC 4.
DRAC 4 includes a default DRAC 4 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 RAC default certificate which does not match the host name of the DRAC 4 (for example, the IP address). To address this security concern, upload a DRAC 4 server certificate issued to the IP address of the DRAC 4. 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 4 (for example, 192.168.0.120). See "Ensuring DRAC 4 Network Security" for more information about generating CSRs and issuing certificates.
When accessing the DRAC 4 Web-based interface, I get a security warning stating the SSL certificate was issued by a certificate authority (CA) that is not trusted.
DRAC 4 includes a default DRAC 4 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 4 server certificate issued by a trusted CA (for example, Thawte or Verisign). See "Ensuring DRAC 4 Network Security" for more information about issuing certificates.
Why doesn't my DNS server register my DRAC 4?
Some DNS servers only register names of 31 characters or fewer.
