Dell Idrac6 Enterprise For Blade Servers Version 2 0 Owners Manual 2.0 User Guide

2014-11-13

: Dell Dell-Idrac6-Enterprise-For-Blade-Servers-Version-2-0-Owners-Manual-118298 dell-idrac6-enterprise-for-blade-servers-version-2-0-owners-manual-118298 dell pdf

Open the PDF directly: View PDF .
Page Count: 432

Download
Open PDF In Browser	View PDF

Integrated Dell™ Remote Access
Controller 6 (iDRAC6) Enterprise
for Blade Servers
Version 2.0

User Guide

w w w. d e l l . c o m | s u p p o r t . d e l l . c o m

Notes and Cautions
NOTE: A NOTE indicates important information that helps you make better use of
your computer.
CAUTION: A CAUTION indicates potential damage to hardware or loss of data if
instructions are not followed.

___________________
Information in this document is subject to change without notice.
© 2009 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc.
is strictly forbidden.
Trademarks used in this text: Dell, the DELL logo, Dell OpenManage, and PowerEdge, are trademarks
of Dell Inc.; Microsoft, Windows, Windows Server, MS-DOS, Windows Vista, ActiveX and Active
Directory are either trademarks or registered trademarks of Microsoft Corporation in the United States
and/or other countries; Red Hat and Linux are registered trademarks of Red Hat, Inc.; Novell and SUSE
are registered trademarks of Novell Corporation. Intel is a registered trademark of Intel Corporation;
UNIX is a registered trademark of The Open Group in the United States and other countries.
Copyright 1998-2006 The OpenLDAP Foundation. All rights reserved. Redistribution and use in source
and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public
License. A copy of this license is available in the file LICENSE in the top-level directory of the distribution
or, alternatively, at www.OpenLDAP.org/license.html. OpenLDAP is a registered trademark of the
OpenLDAP Foundation. Individual files and/or contributed packages may be copyrighted by other parties
and subject to additional restrictions. This work is derived from the University of Michigan LDAP v3.3
distribution. This work also contains materials derived from public sources. Information about OpenLDAP
can be obtained at www.openldap.org/. Portions Copyright 1998-2004 Kurt D. Zeilenga. Portions
Copyright 1998-2004 Net Boolean Incorporated. Portions Copyright 2001-2004 IBM Corporation.
All rights reserved. Redistribution and use in source and binary forms, with or without modification,
are permitted only as authorized by the OpenLDAP Public License. Portions Copyright 1999-2003
Howard Y.H. Chu. Portions Copyright 1999-2003 Symas Corporation. Portions Copyright 1998-2003
Hallvard B. Furuseth. All rights reserved. Redistribution and use in source and binary forms, with or
without modification, are permitted provided that this notice is preserved. The names of the copyright
holders may not be used to endorse or promote products derived from this software without their specific
prior written permission. This software is provided "as is'' without express or implied warranty. Portions
Copyright (c) 1992-1996 Regents of the University of Michigan. All rights reserved. Redistribution and
use in source and binary forms are permitted provided that this notice is preserved and that due credit is
given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse
or promote products derived from this software without specific prior written permission. This software
is provided "as is'' without express or implied warranty. Other trademarks and trade names may be used
in this document to refer to either the entities claiming the marks and names or their products. Dell Inc.
disclaims any proprietary interest in trademarks and trade names other than its own.
March 2009

Rev. A00

Contents

iDRAC6 Enterprise Overview .

. . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . .

iDRAC6 Management Features
iDRAC6 Security Features .

iDRAC6 Firmware Improvements
Supported Platforms

. . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

Supported Operating Systems .
Supported Web Browsers .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . .

Supported Remote Access Connections
iDRAC6 Ports

. . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

Other Documents You May Need

. . . . . . . . . . . .

Configuring iDRAC6 Enterprise
Before You Begin

. . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

Interfaces for Configuring iDRAC6
Configuration Tasks

. . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . . . . .

Configure the Management Station
Configure iDRAC6 Networking
Configure iDRAC6 Users

Configure Active Directory .

. . . . . . . . . . . .

Configure IP Filtering and IP Blocking

. . . . . . .

Contents

42
42

Configure Platform Events

. . . . . . . . . . . . .

Enabling or Disabling Local Configuration
Access . . . . . . . . . . . . . . . . . .
Configure iDRAC6 Services

. . . . .

. . . . . . . . . . . .

. . . . . .

. . . . . . . . . . . . . .

Configure Secure Sockets Layer (SSL)
Configure Virtual Media

Configure a VFlash Media Card

. . . . . . . . . .

Install the Managed Server Software

. . . . . . .

Configure the Managed Server for the
Last Crash Screen Feature . . . . . . .

44
44

Configuring Networking Using the CMC
Web Interface . . . . . . . . . . . . . .

. . . . . . . .

Launching the iDRAC6 Web-based
Interface From the CMC . . . . . .

. . . . . . . .

Configuring Networking for iDRAC6

. . . . . . . .

. . . . . . . . .

. . . . . . . . . . . . . . .

Updating iDRAC6 Firmware

Downloading the Firmware or
Update Package . . . . . . .

. . . . . . . . . . .

Executing the Firmware Update

. . . . . . . . . .

Using the DOS Update Utility

. . . . . . . . .

51
52

. . . . . . . . . . .

. . . . . . . . . . . .

Verifying the Digital Signature
Clear Your Browser’s Cache

. . . . . . . . . . . .

Using the iDRAC6 Web Interface .

Updating the USC Repair Package

Contents

. . . . . .

Viewing FlexAddress Mezzanine Card
Fabric Connections . . . . . . . . . .

. . . . . . . . . . .

Configuring iDRAC6 For Use With IT Assistant .
Using the iDRAC6 Configuration Utility to
Enable Discovery and Monitoring . . . .

. . . .

. . . . .

Using the iDRAC6 Web Interface to
Enable Discovery and Monitoring .

. . . . . . . .

Using IT Assistant to View iDRAC6
Status and Events . . . . . . . . .

. . . . . . . .

. . . . . . . . .

. . . . . . . . . . .

Configuring the Management
Station . . . . . . . . . . . . . . . . . .
Management Station Set Up Steps

Management Station Network Requirements

. . . . .

. . . . . . . .

. . . . . . . . . . . .

Configuring a Supported Web Browser
Opening Your Web Browser

Configuring Your Web Browser to Connect
to the Web Interface . . . . . . . . . . . .
Adding iDRAC6 to the List of
Trusted Domains . . . . . .

. . . .

. . . . . . . . . . . .

Viewing Localized Versions of the
Web Interface . . . . . . . . . .
Setting the Locale in Linux

. . . . . . . . .

. . . . . . . . . . . . .

. . . . .

. . . . . . . . . . . .

. . . . . . . . . . . . . . . . .

Disabling the Whitelist Feature in Firefox
Installing a Java Runtime Environment (JRE)
Installing Telnet or SSH Clients .
Telnet with iDRAC6

Configuring the Backspace Key
For Telnet Sessions . . . . . .
SSH With iDRAC6
Installing a TFTP Server

. . . . . . . . . .

. . . . . . . . . . . . . . . . .

Installing Dell OpenManage IT Assistant

. . . . . . .

Contents

Configuring the Managed Server

. . . . . .

Installing the Software on the Managed Server

. . . .

. . . . . .

. . . . . . . . . . .

Configuring the Managed Server to Capture
the Last Crash Screen . . . . . . . . . . . .
Disabling the Windows Automatic
Reboot Option . . . . . . . . . . .

Configuring iDRAC6 Enterprise
Using the Web Interface . . . . .

. . . . . . . .

. . . . . . . . . . . . . .

Logging In

. . . . . . . . . . . . . . . . . . . . .

Logging Out

. . . . . . . . . . . . . . . . . . . . .

Accessing the Web Interface

Using Multiple Browser Tabs and
Windows . . . . . . . . . . . . .
Configuring the iDRAC6 NIC .

. . . . . . . . .

. . . . . . . . . . . . . .

Configuring the Network and
IPMI LAN Settings . . . . . .

. . . . . . . . . . .

Configuring Platform Events .

. . . . . . . . . . . . . .

Configuring Platform Event Filters (PEF)

. . . . . .

Configuring Platform Event Traps (PET)

. . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . .

Configuring E-Mail Alerts
Configuring IPMI Over LAN

Adding and Configuring iDRAC6 Users

. . . . . . . . .

Securing iDRAC6 Communications Using SSL
and Digital Certificates . . . . . . . . . . . .
Secure Sockets Layer (SSL)

. . . . .

. . . . . . . . . . . .

Certificate Signing Request (CSR)

Contents

. . . . . .

Configuring IP Filtering and IP Blocking

. . . . . . . . .

Accessing the SSL Main Menu

Generating a New Certificate Signing
Request . . . . . . . . . . . . . . . .

. . . . . . .

. . . . . . . . . .

. . . . . . . . . . . .

Uploading a Server Certificate .
Viewing a Server Certificate

Configuring and Managing Active
Directory Certificates . . . . . . .

. . . . . .

101

. . . . . . . . . . .

104

. . . . . . . . . . . .

105

. . . . . . . . . . . . . .

105

Uploading an Active Directory
CA Certificate . . . . . . . .
Viewing an Active Directory
CA Certificate . . . . . . .

Enabling Local Configuration Access

. . . . . . .

105

Disabling Local Configuration Access

. . . . . . .

106

. . . . . . . . . . . . . .

106

. . . . . . . . . . . . . . .

109

Configuring iDRAC6 Services
Updating iDRAC6 Firmware

Updating iDRAC6 Firmware
Using the CMC . . . . . . .

100

. . . . . . . . . . .

Configuring Active Directory (Standard
Schema and Extended Schema) . . . .

Enabling or Disabling Local
Configuration Access . . . .

. . . . . . . . . .

111

. . . . . . . . . . . .

Using iDRAC6 With Microsoft
Active Directory . . . . . . . . . .
Prerequisites for Enabling Active
Directory Authentication for iDRAC6

. . . . . . . .

113

. . . . . . . . . .

Supported Active Directory Authentication
Mechanisms . . . . . . . . . . . . . . . . .

. . . . . .

Contents

114

Extended Schema Active Directory Overview
Extending the Active Directory Schema

. . . . .

115

. . . . . .

115

. . . . . . .

115

Overview of the iDRAC6 Schema
Extensions . . . . . . . . . . . .

. . . . . . . . .

116

Active Directory Object Overview

. . . . . . . . .

116

. . . . . . . . . .

118

Active Directory Schema Extensions

Accumulating Privileges Using
Extended Schema . . . . . . .

Configuring Extended Schema Active
Directory to Access iDRAC6 . . . . .

. . . . . . .

Installing the Dell Extension to the Active
Directory Users and Computers Snap-In
Adding iDRAC6 Users and Privileges to
Active Directory . . . . . . . . . . . .

. . . . .

125

. . . . . .

126

Configuring Active Directory With Extended
Schema Using the iDRAC6 Web-Based
Interface . . . . . . . . . . . . . . . . . . .
Configuring Active Directory With
Extended Schema Using RACADM

. . .

128

. . . . . . . .

130

Standard Schema Active Directory Overview
Single Domain Versus Multiple Domain
Scenarios . . . . . . . . . . . . . . . .

132

. . . . . .

134

. . . . . . .

134

Configuring Active Directory With
Standard Schema Using the iDRAC6
Web-Based Interface . . . . . . . .

. . . . . . .

134

. . . . . . . .

137

. . . . . . . . . . . . . . .

139

Testing Your Configurations

Enabling SSL on a Domain Controller .

. . . . . . . . .

Exporting the Domain Controller Root
CA Certificate to iDRAC6 . . . . . . .
Importing the iDRAC6 Firmware
SSL Certificate . . . . . . . . .
Contents

. . . . .

Configuring Standard Schema Active
Directory to Access iDRAC6 . . . . .

Configuring Active Directory With
Standard Schema Using RACADM .

119

140

. . . . . . .

140

. . . . . . . . . .

141

Using Active Directory to Log In to iDRAC6
Frequently Asked Questions

. . . . . .

142

. . . . . . . . . . . . . .

143

Active Directory Log In Issues

. . . . . .

146

. . . . . . . . .

146

. . . . . . . . . . . . . . . . . . .

147

Extended and Standard Schema .
Miscellaneous

Viewing the Configuration and
Health of the Managed Server
System Summary

149

. . . . . . . . . . . . . .

Integrated Dell Remote Access
Controller 6 - Enterprise . . . .

149
149

. . . . . . . . . .

150

. . . . . . . . . . . . . . . . . .

151

. . . . . . . . . . . . . . . . . . . . . .

151

. . . . . . . . . . . . . . . . . . . . . . .

151

. . . . . . . . . . . . . . . . . . . . . . . .

151

WWN/MAC Summary
System Health
iDRAC6

Batteries

. . . . . . . . . . . . . . . . . . . . . .

Voltages

152

. . . . . . . . . . . . . . . . . . .

152

. . . . . . . . . . . . . . . . . . . . . .

152

Temperatures

. . . . . . . . . . . . . . . . .

152

. . . . . . . . . . . . . . . . . . . . . . . . .

152

Power Monitoring
CPU

. . . . . . .

. . . . . . . . . . . . . . . . . . . .

Main System Enclosure

CMC

143

. . . . . . . . . . .

Active Directory Certificate Validation .

POST

. . . . . . . . . . . . . . . . . . . . . . . .

Misc Health

. . . . . . . . . . . . . . . . . . . .

Contents

153
153

Power Monitoring and Power
Management . . . . . . . . . . . . .
Configuring and Managing Power
Power Monitoring

155

. . . . . . . . . . . . . . . . . . . .

156

. . . . . . . . . . . . .

156

. . . . . . . . . . . . . . . . . . . .

158

Viewing Power Budget

. . . . . . . . . . . . . . .

159

. . . . . . . . . . . . . . . . . . . . . .

160

Executing Power Control
Operations on the Server .

. . . . . . . . . . . . .

Configuring and Using Serial
Over LAN . . . . . . . . . . . . . . . .
Enabling Serial Over LAN in the BIOS

Using Serial Over LAN (SOL)

. . . . . . . . . . .

164

. . . . . . . . . . . . . .

167

. . . . . . . . . .

167

. . . . . . . . . . . . . .

168

. . . . .

168

. . . . . .

168

. . . . . . . . . . . . . . .

169

Model for Redirecting SOL Over IPMItool
Disconnecting SOL session in SM-CLP
Using SOL over PuTTY

Using SOL over Telnet with Linux

. . . . . . . . .

Using SOL over IPMItool

170

. . . . . . .

170

. . . . . . . . . . . . . .

171

Using SOL over OpenSSH with Linux .
Opening SOL with SOL proxy

Contents

163
163

Model for Redirecting SOL Over
Telnet or SSH . . . . . . . . . .
Model for the SOL Proxy

. . . . . . . .

160

. . . . . . . . .

Configuring Serial Over LAN in the
iDRAC6 Web GUI . . . . . . . . . .

158

. . . . . . . . .

Viewing Power Budget Threshold
Power Control

155

. . . . . . . . . . .

Viewing Power Monitoring
Power Budgeting

. . . . . . . .

. . . . . . . . . . . .

171

Operating System Configuration

. . . . . . . .

177

. . . . . . . . . . . . .

182

Linux Enterprise Operating System
Windows 2003 Enterprise

10 Using GUI Console Redirection .
Overview

177

. . . . . . . . . . . .

. . . . . .

185
185

. . . . . . . . . . . . . . . . . . . . . . . .

Using Console Redirection

Supported Screen Resolutions and
Refresh Rates . . . . . . . . . . .

186

. . . . . . . .

Configuring the Management Station

186

. . . . . . .

Configuring Console Redirection and
Virtual Media in the iDRAC6 Web Interface

. . . .

187

. . . . .

189

. . . . . . . . . . . . . . . . .

191

Opening a Console Redirection Session .
Using the Video Viewer

185

. . . . . . . . . . . . . . .

Synchronizing the Mouse Pointers

. . . . . . .

195

. . . . . . . . . . . . . .

196

Disabling or Enabling Local Console .
Frequently Asked Questions

11 Configuring a VFlash Media Card
for Use With iDRAC6 . . . . . . . . . .
Installing a VFlash Media Card

. . . . .

201

. . . . . . . . . . . . .

Removing a VFlash Media Card

. . . . . . . . . .

Configuring the VFlash Media Card Using the
iDRAC6 Web Interface . . . . . . . . . . . .
Enabling or Disabling the VFlash
Media Card . . . . . . . . . . . .

201
202

. . . . .

202

. . . . . . . . .

202

. . . . . . . .

203

. . . . . . . . . . . . . . .

203

Formatting the VFlash Media Card .
Uploading Disk Image

194

. . . . . . . .

Viewing the VFlash Key Size

. . . . . . . . . . . .

Contents

203

Configuring the VFlash Media Card
Using RACADM . . . . . . . . . .

. . . . . . . . . . .

Enabling or Disabling the VFlash
Media Card . . . . . . . . . . .

. . . . . . . . . .

Formatting the VFlash Media Card

12 Configuring and Using
Virtual Media . . . . . . . .
Overview .

. . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

Windows-Based Management Station

205
205
206
207

. . . . . . . . . . . . . . .

208

. . . . . . . . . . . . . . . . .

209

Booting From Virtual Media

. . . . . . . . . . . .

211

Installing Operating Systems
Using Virtual Media . . . .

. . . . . . . . . . . .

212

Using Virtual Media When the Server’s
Operating System Is Running . . . . . .
Frequently Asked Questions

. . . . . .

212

. . . . . . . . . . . . . .

213

13 Using the Local RACADM
Command Line Interface .
Using the RACADM Command
RACADM Subcommands

. . . . . . . . . . .

219

. . . . . . . . . . . . .

219

. . . . . . . . . . . . . . . .

220

Using the RACADM Utility to Configure iDRAC6
Displaying Current iDRAC6 Settings

. . . .

221

. . . . . . . .

221

. . . . . .

222

. . . . . . . . . . . . . .

223

Managing iDRAC6 Users with RACADM
Adding an iDRAC6 User

Contents

204

. . . . . .

Configuring Virtual Media .

204

. . . . . . . .

Linux-Based Management Station .

Running Virtual Media .

204

Enabling an iDRAC6 User With Permissions .

. . .

224

. . . . . . . . . . . . .

224

. . . . . . . . . . . . . . .

225

Removing an iDRAC6 User
Testing E-mail Alerting

Testing the iDRAC6 SNMP
Trap Alert Feature . . . .

225

. . . . . . . . . . . . .

Configuring iDRAC6 Network Properties

. . . . .

225

. . . . . . . . . . . .

227

Configuring PEF

. . . . . . . . . . . . . . . . . .

229

Configuring PET

. . . . . . . . . . . . . . . . . .

229

Configuring IPMI Over LAN

Configuring IP Filtering (IP Range) .

. . . . . . . .

231

Configuring IP Filtering .

. . . . . . . . . . . . . .

232

Configuring IP Blocking

. . . . . . . . . . . . . .

234

Configuring iDRAC6 Telnet and
SSH Services Using Local RACADM .
Using an iDRAC6 Configuration File

. . . . . . .

236

. . . . . . . . . .

236

Creating an iDRAC6 Configuration File .
Configuration File Syntax

. . . . . .

237

. . . . . . . . . . . . .

237

Modifying the iDRAC6 IP Address in a
Configuration File . . . . . . . . . . .

. . . .

240

. . . . . . . . . . . . . .

241

Loading the Configuration File Into iDRAC6
Configuring Multiple iDRACs

14 Using iDRAC6 Enterprise
SM-CLP Command Line Interface
System Management With SM-CLP .

243
243

. . . . . . . . . . . . . . . .

244

. . . . . . . . . . . . . . . . . . . .

244

Navigating the MAP Address Space
Targets

. . . .

. . . . . . . . . .

iDRAC6 SM-CLP Support
SM-CLP Features

239

. . . . . .

. . . . . . . . . .

247

. . . . . . . . . . . . . . . . . . . . . . .

248

Contents

Using the Show Verb

. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . .

249

. . . . . . . . . . . . . . .

249

Using the -display Option .
Using the -level Option

. . . . . . . . . . . . . .

249

. . . . . . . . . . . . . . .

250

Using the -output Option
iDRAC6 SM-CLP Examples

. . . . . . . . . . . .

250

. . . . . . . . . . . . . . . . .

251

Server Power Management
SEL Management .

MAP Target Navigation

. . . . . . . . . . . . . .

Setting the iDRAC6 IP Address,
Subnet Mask, and Gateway Address

. . . . . . .

Updating iDRAC6 Firmware Using SM-CLP

15 Deploying Your Operating
System Using iVMCLI . . .
Before You Begin

. . . . . . . . . . . . . . . . . . . .

Network Requirements .

253
255

257
257

. . . . . . . . . . .

257
257

. . . . . . . . . . . . .

Creating an Image File for Linux Systems

258

. . . . .

258

. . . . . . . . . . . . .

258

. . . . . . . . . . . . . . . .

258

Creating an Image File for
Windows Systems . . . .
Preparing for Deployment

253

. . . . . . . . . . . . . .

Creating a Bootable Image File

Configuring the Remote Systems .
Deploying the Operating System

Contents

. . . .

. . . . . . . . . . .

Remote System Requirements

249

. . . . . . . . .

258

. . . . . . . . . . . .

259

Using the Virtual Media Command
Line Interface Utility . . . . . . .

260

. . . . . . . . . . . .

261

. . . . . . . . . . . . . .

262

. . . . . . . . . . . . . . . .

262

Installing the iVMCLI Utility
Command Line Options .
iVMCLI Parameters

. . . . . . . . . . .

iVMCLI Operating System Shell Options

16 Using the iDRAC6
Configuration Utility
Overview

265

. . . . .

. . . . . . . . . . . . . . .

267
267

. . . . . . . . . . . . . . . . . . . . . . . .

Starting the iDRAC6 Configuration Utility

. . . . . . .

268

. . . . . . . .

268

. . . . . . . . . . . . . . . . . . . .

269

Using the iDRAC6 Configuration Utility .
iDRAC6 LAN

IPMI Over LAN

LAN Parameters

272

. . . . . . . . . . . .
. . . . . . . . . .

272

. . . . . . . . . . . . . .

273

. . . . . . . . . . . . . . . . . .

273

System Services Configuration
LAN User Configuration
System Event Log Menu

274

. . . . . . . . . . . . . .

Exiting the iDRAC6 Configuration Utility

17 Recovering and Troubleshooting
the Managed Server . . . . . . . . . .
Safety First–For You and Your System
Trouble Indicators

270

. . . . . . . . . . . . . . . . . .

Virtual Media Configuration

Reset to Default

269

. . . . . . . . . . . . . . . . . . .

274

. . . . . .

. . . . .

275

. . . . . . . . .

275

. . . . . . . . . . . . . . . . . . . .

276

LED Indicators

. . . . . . . . . . . . . . . . . . .

Other Trouble Indicators

276

. . . . . . . . . . .

277

. . . . . . . . . . . . . .

277

Hardware Trouble Indicators

Contents

Problem Solving Tools .

. . . . . . . . . . . . . . . . .

Checking the System Health

. . . . . . . . . . . .
. . . . . . .

279
279

Viewing the Last System Crash Screen

. . . . . .

281

. . . . . . . .

282

. . . . . . . . . . . . . .

290

Checking the Server Status Screen
for Error Messages . . . . . . . . .
Viewing System Information

. . . . . . . . . . . .

Identifying the Managed Server in
the Chassis . . . . . . . . . . . . .
Using the Diagnostics Console .

. . . . . . . .

293
294

. . . . . .

Troubleshooting and Frequently Asked Questions

A RACADM Subcommand Overview

. . . . .

296

301
301

. . . . . . . . . . . . . . . . . . . . . . . . . .

302

getconfig

. . . . . . . . . . . . . . . . . . . . . . . . .

304

getssninfo

. . . . . . . . . . . . . . . . . . . . . . . .

306

getsysinfo

. . . . . . . . . . . . . . . . . . . . . . . .

307

getractime

. . . . . . . . . . . . . . . . . . . . . . . .

310

setniccfg

. . . . . . . . . . . . . . . . . . . . . . . . .

311

getniccfg

. . . . . . . . . . . . . . . . . . . . . . . . .

312

getsvctag .
racreset
Contents

. . .

295

. . . . . . . . . . . . . . . . . . . . . . . . . . .

config

291

. . . . . . . . . .

Managing Power on a Remote System

help

280

. . . .

Viewing the Most Recent Boot Sequences

Viewing the iDRAC6 Log

278

. . . . . . . . . . . . .

Checking the System Event Log (SEL)
Checking the Post Codes .

278

. . . . . . . . . . . . . . . . . . . . . . . .

313

. . . . . . . . . . . . . . . . . . . . . . . . .

313

racresetcfg

. . . . . . . . . . . . . . . . . . . . . . .

314

serveraction

. . . . . . . . . . . . . . . . . . . . . . .

315

getraclog

. . . . . . . . . . . . . . . . . . . . . . . .

316

clrraclog

. . . . . . . . . . . . . . . . . . . . . . . . .

317

getsel

. . . . . . . . . . . . . . . . . . . . . . . . . .

317

clrsel .

. . . . . . . . . . . . . . . . . . . . . . . . . .

319

gettracelog
sslcsrgen

. . . . . . . . . . . . . . . . . . . . . . .

319

. . . . . . . . . . . . . . . . . . . . . . . .

321

sslcertupload

. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .

323

. . . . . . . . . . . . . . . . . . . . . . .

324

. . . . . . . . . . . . . . . . . . . . . . . .

326

. . . . . . . . . . . . . . . . . . . . . . . . .

328

sslcertdownload
sslcertview
testemail .
testtrap .

322

vmdisconnect
clrasrscreen

. . . . . . . . . . . . . . . . . . . . . .

329

. . . . . . . . . . . . . . . . . . . . . . .

329

localconredirdisable

. . . . . . . . . . . . . . . . . .

329

vmkey

. . . . . . . . . . . . . . . . . . . . . . . . . .

330

version

. . . . . . . . . . . . . . . . . . . . . . . . . .

330

Contents

B iDRAC6 Enterprise Property
Database Group and
Object Definitions . . . . . . . .
Displayable Characters
idRacInfo .

. . . . . . . . .

. . . . . . . . . . . . . . . . .

331

. . . . . . . . . . . . . . . . . . . . . . . .

331

idRacProductInfo (Read Only)

. . . . . . . . . . .

idRacDescriptionInfo (Read Only)
idRacBuildInfo (Read Only) .

332

. . . . . . . . . . .

332
333

. . . . . . . . . . . . . .

333

. . . . . . . . . . . . . . .

333

. . . . . . . . . . . . . . . . . . . . . . .

334

idRacName (Read Only)
idRacType (Read Only)
cfgOobSnmp

cfgOobSnmpAgentCommunity
(Read/Write) . . . . . . . . .

. . . . . . . . . . .

cfgLanNetworking .

334

. . . . . .

334

. . . . . . . . . . . . . . . . . . .

335

cfgOobSnmpAgentEnable (Read/Write)

cfgDNSDomainNameFromDHCP
(Read/Write) . . . . . . . . . . .

. . . . . . . . .

335

. . . . . . . .

335

. . . . . . . . . .

336

cfgDNSDomainName (Read/Write)
cfgDNSRacName (Read/Write)

cfgDNSRegisterRac (Read/Write)

. . . . . . . . .
. . . . .

336
337

. . . . . . . . . . .

337

. . . . . . . . . . . .

338

cfgDNSServer1 (Read/Write)
cfgDNSServer2 (Read/Write)
cfgNicEnable (Read/Write) .

336

. . . . . . . . . . .

cfgDNSServersFromDHCP (Read/Write) .

cfgNicIpAddress (Read/Write)

. . . . . . . . . . .

338

cfgNicNetmask (Read/Write)

. . . . . . . . . . .

338

cfgNicGateway (Read/Write)

. . . . . . . . . . .

339

cfgNicUseDhcp (Read/Write)

. . . . . . . . . . .

339

cfgNicMacAddress (Read Only)

Contents

332

. . . . . . . . .

. . . . . . . . . . . .

idRacVersionInfo (Read Only)

331

. . . . . . . . . .

340

cfgUserAdmin

. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . .

340

. . . . . . . . . .

341

cfgUserAdminIndex (Read Only) .
cfgUserAdminIpmiLanPrivilege
(Read/Write) . . . . . . . . . .

cfgUserAdminPrivilege (Read/Write)

. . . . . . .

342

. . . . . . .

343

. . . . . . . . . . . . . . .

343

cfgUserAdminPassword (Write Only)

. . . . . . . . . . . . . .

344

. . . . . . . . . . . . . . . . . . . . . .

344

cfgUserAdminSolEnable
cfgEmailAlert

cfgEmailAlertIndex (Read Only)

. . . . . . . . . .

cfgEmailAlertAddress

. . . . . . . . .

344
345

. . . . . . . . . . . . .

345

. . . . . . . . . . . . . . . .

345

cfgEmailAlertCustomMsg
cfgSessionManagement

344

. . . . . . . . . . . . . . .

cfgEmailAlertEnable (Read/Write)

cfgSsnMgtConsRedirMaxSessions
(Read/Write) . . . . . . . . . . . .

. . . . . . . .

cfgSsnMgtSshIdleTimeout (Read/Write)

346

. . .

346

. . . . .

346

cfgSsnMgtWebserverTimeout (Read/Write)

. . . .

347

. . . . . . . . . . . . . . . . . . . . . . . . .

348

cfgSsnMgtTelnetIdleTimeout (Read/Write)
cfgSerial

341

. . . . . .

cfgUserAdminUserName (Read/Write)
cfgUserAdminEnable .

340

cfgSerialSshEnable (Read/Write)

. . . . . . . . .
. . . . . . . .

348

. . . . . . . . . . . . . . . . . . . . .

348

cfgSerialTelnetEnable (Read/Write)
cfgRemoteHosts

cfgRhostsSmtpServerIpAddr (Read/Write)
cfgUserDomain

348

. . . .

349

. . . . . . . . . . . . . . . . . . . . .

349

cfgUserDomainIndex (Read Only)

. . . . . . . . .

cfgUserDomainName (Read/Write)

. . . . . . . .

Contents

349
349

cfgServerPower

. . . . . . . . . . . . . . . . . . . . .
. . . . . . . .

350

. . . . . . . . .

350

cfgServerPowerStatus (Read Only)
cfgServerPowerServerAllocation
(Read Only) . . . . . . . . . . . .

cfgServerPowerActualPowerConsumption
(Read Only) . . . . . . . . . . . . . . . . .

. . . .

350

. . . . .

351

. . . . . .

351

. . . . . . . .

351

cfgServerPowerPeakPowerConsumption
(Read Only) . . . . . . . . . . . . . . . .
cfgServerPowerPeakPowerTimestamp
(Read Only) . . . . . . . . . . . . . . .
cfgServerPowerConsumptionClear
(Write Only) . . . . . . . . . . . . .

cfgServerPowerCapWatts (Read Only)

. . . . . .

352

cfgServerPowerCapBtuhr (Read Only) .

. . . . . .

352

. . . . .

352

. . . . . . . . . . . . . . . . . . . . . .

353

cfgServerPowerCapPercent (Read Only)
cfgRacTuning

cfgRacTuneHttpPort (Read/Write)

. . . . . . . . .

353

cfgRacTuneHttpsPort (Read/Write)

. . . . . . . .

353

. . . . . . . . . . . .

354

cfgRacTuneIpRangeAddr .

. . . . . . . . . . . . .

354

cfgRacTuneIpRangeMask

. . . . . . . . . . . . .

354

. . . . . . . . . . . . . .

355

cfgRacTuneIpRangeEnable

cfgRacTuneIpBlkEnable

cfgRacTuneIpBlkFailCount

. . . . . . . . . . . . .
. . . . . . . . . . .

355

cfgRacTuneIpBlkPenaltyTime

. . . . . . . . . . .

356

. . . . . . . . .

356

. . . . .

356

cfgRacTuneTelnetPort (Read/Write)

. . . . . . . .

357

cfgRacTuneConRedirEncryptEnable
(Read/Write) . . . . . . . . . . . .

. . . . . . . .

357

cfgRacTuneConRedirEnable (Read/Write)

. . . . . .

357

. . . . . . . . . .

358

cfgRacTuneConRedirPort (Read/Write)
cfgRacTuneConRedirVideoPort
(Read/Write) . . . . . . . . . .

cfgRacTuneAsrEnable (Read/Write)

Contents

355

cfgRacTuneIpBlkFailWindow

cfgRacTuneSshPort (Read/Write)

350

. . . . . . . .

358

cfgRacTuneWebserverEnable
(Read/Write) . . . . . . . . .

. . . . . . . . . . .

358

cfgRacTuneLocalServerVideo
(Read/Write) . . . . . . . . .

. . . . . . . . . . .

359

cfgRacTuneLocalConfigDisable
(Read/Write) . . . . . . . . . .
ifcRacManagedNodeOs .

. . . . . . . . . .

359

. . . . . . . . . . . . . . . .

360

. . . . . . . .

360

. . . . . . . . .

360

. . . . . . . . . . . . . . . . . . . . .

360

ifcRacMnOsHostname (Read Only)
ifcRacMnOsOsName (Read Only)
cfgRacSecurity

cfgSecCsrCommonName (Read/Write)

. . . . . .

cfgSecCsrOrganizationName (Read/Write)

. . . . .

361
361

. . . . . . . .

362

cfgSecCsrLocalityName (Read/Write) .
cfgSecCsrCountryCode (Read/Write)
cfgSecCsrEmailAddr (Read/Write) .

. . . . . . .

362

. . . . . . . .

362

. . . . . . . . . .

363

. . . . . . . . . . . . . . . . . . . . . .

363

cfgSecCsrKeySize (Read/Write)
cfgRacVirtual

361

. . . . . .

cfgSecCsrOrganizationUnit (Read/Write)
cfgSecCsrStateName (Read/Write)

361

. . . .

cfgVirMediaAttached (Read/Write)

. . . . . . . .

363

cfgVirMediaBootOnce (Read/Write) .

. . . . . . .

364

cfgVirMediaKeyEnable (Read/Write)

. . . . . . .

364

. . . . . . . . .

365

. . . . . . . . . . . . . . . . . . .

365

cfgFloppyEmulation (Read/Write)
cfgActiveDirectory

. . . . . . . . . .

365

. . . . . . . . . . .

366

. . . . . . . . . . . . .

366

cfgADRacDomain (Read/Write)
cfgADRacName (Read/Write)
cfgADEnable (Read/Write)

cfgADAuthTimeout (Read/Write) .

. . . . . . . . .

366

cfgADDomainController1 (Read/Write)

. . . . . .

367

cfgADDomainController2 (Read/Write)

. . . . . .

367

cfgADDomainController3 (Read/Write)

. . . . . .

367

Contents

cfgADGlobalCatalog1 (Read/Write)

. . . . . . . .

368

cfgADGlobalCatalog2 (Read/Write)

. . . . . . . .

368

cfgADGlobalCatalog3 (Read/Write)

. . . . . . . .

368

. . . . . . . . . . . . . .

369

cfgADType (Read/Write)

. . . . .

369

. . . . . . . . . . . . . . . . . . .

369

cfgADCertValidationEnable (Read/Write)
cfgStandardSchema

cfgSSADRoleGroupIndex (Read Only)

. . . . . . .

cfgSSADRoleGroupName (Read/Write)

. . . . . .

370

. . . .

370

. . . . . . . . . . . . . . . . . . . . . . . .

371

cfgSSADRoleGroupPrivilege (Read/Write)

cfgIpmiSolEnable (Read/Write)

. . . . . . . . . .

cfgIpmiSolBaudRate (Read/Write)

. . . . . . . . .

cfgIpmiSolMinPrivilege (Read/Write)

. . . . . . .

373

. . . . . . . . . . . . . . . . . . . . . . . .

373

. . . . . . . . . .

cfgIpmiLanPrivLimit (Read/Write)

. . . . . . . . .

cfgIpmiEncryptionKey (Read/Write)

373
373

. . . . . . .

374

. . . . . . . .

374

cfgIpmiLanAlertEnable (Read/Write) .

. . . . .

374

. . . . . . . . . . . . . . . . . . . . . . . .

375

cfgIpmiPetCommunityName (Read/Write)

Contents

372
372

cfgIpmiLanEnable (Read/Write)

372

. . .

cfgIpmiSolSendThreshold (Read/Write)

cfgIpmiPef

371

. . . . . .

cfgIpmiSolAccumulateInterval (Read/Write)

cfgIpmiLan

370

. . . . .

cfgSSADRoleGroupDomain (Read/Write)

cfgIpmiSol

369

cfgIpmiPefName (Read Only)

. . . . . . . . . . .

375

cfgIpmiPefIndex (Read Only)

. . . . . . . . . . . .

375

cfgIpmiPefAction (Read/Write)

. . . . . . . . . .

376

cfgIpmiPefEnable (Read/Write)

. . . . . . . . . .

376

cfgIpmiPet

376

. . . . . . . . . . . . . . . . . . . . . . . .

cfgIpmiPetIndex (Read/Write)

. . . . .

377

. . . . . . .

377

cfgIpmiPetAlertDestIpAddr (Read/Write)
cfgIpmiPetAlertEnable (Read/Write) .

C iDRAC6 SM-CLP Property Database
/system1/sp1/account<1-16>
userid (Read Only)

376

. . . . . . . . . . .

. . .

379

. . . . . . . . . . . . . .

379

. . . . . . . . . . . . . . . . .

379

username (Read/Write)

. . . . . . . . . . . . . .

oemdell_ipmilanprivileges (Read/Write) .
password (Write Only)

380

. . . . . . . . . . . . . . .

380

. . . . . . . . . . . . .

381

. . . . . . . . . . . . . .

381

enabledstate (Read/Write)
solenabled (Read/Write)

. . . .

381

. . . . . . . . . . . . . . . .

383

oemdell_extendedprivileges (Read/Write)
/system1/sp1/enetport1/*

379

. . . . .

macaddress (Read Only)

. . . . . . . . . . . . . .
. . . . . .

383

. . . . . . . . .

383

. . . . . . . . . . . . . .

384

/system1/sp1/enetport1/lanendpt1/ipendpt1
oemdell_nicenable (Read/Write)
ipaddress (Read/Write)

subnetmask (Read/Write)

. . . . . . . . . . . . .

384

. . . . . . . . . .

384

. . . . . . . . . . . . . .

385

oemdell_usedhcp (Read/Write)
committed (Read/Write)

383

/system1/sp1/enetport1/lanendpt1/
ipendpt1/dnsendpt1 . . . . . . . .

. . . . . . . . . . .

oemdell_domainnamefromdhcp
(Read/Write) . . . . . . . . . .

. . . . . . . . . .

385

. . . . . .

386

. . . . . . .

386

. . . . . . . .

386

oemdell_dnsdomainname (Read/Write)
oemdell_dnsregisterrac (Read/Write)
oemdell_dnsracname (Read/Write)

385

oemdell_serversfromdhcp (Read/Write)

. . . . .

Contents

387

/system1/sp1/enetport1/lanendpt1/
ipendpt1/dnsendpt1/remotesap1 .

. . . . . . . . . . .
. . . . . . . . . .

387

. . . . . . . . . . .

388

dnsserveraddress (Read/Write)
/system1/sp1/enetport1/lanendpt1/
ipendpt1/dnsendpt1/remotesap2 .

. . . . . . . . . .

388

. . . . . . . . . . .

388

dnsserveraddress (Read/Write)
/system1/sp1/enetport1/lanendpt1/
ipendpt1/remotesap1 . . . . . . .

. . . . . . .

388

. . . . . . . . . . . . . . . .

388

defaultgatewayaddress (Read/Write)
/system1/sp1/group<1-5>

oemdell_groupname (Read/Write)

. . . . . . . . .

oemdell_groupdomain (Read/Write)

. . . . . . . .

. . . . . . . . . . .

390

. . . . . . . . . . . . .

390

oemdell_adracname (Read/Write)

. . . . . . . . .

391

. . . . . . .

391

. . . . . . . . . . .

392

oemdell_adrootdomain (Read/Write)
oemdell_timeout (Read/Write)

. . . . . . . .

392

. . . . . . . . . .

392

oemdell_schematype (Read/Write)
oemdell_adspecifyserverenable
(Read/Write) . . . . . . . . . .

. . . .

393

. . . . . .

393

. . . . . . . . . .

393

. . . . . . . . . . . .

393

oemdell_addomaincontroller (Read/Write)
oemdell_adglobalcatalog (Read/Write)
/system1/sp1/oemdell_racsecurity1
commonname (Read/Write)

391

. . . . . . . .

oemdell_adracdomain (Read/Write)

organizationname (Read/Write)

. . . . . . . . . .

394

. . . . . . . .

394

. . . . . . . . .

395

oemdell_localityname (Read/Write)
oemdell_statename (Read/Write)

394

. . . . . .

oemdell_organizationunit (Read/Write)

Contents

389
389

/system1/sp1/oemdell_adservice1
enabledstate (Read/Write)

389

. . . . . . .

oemdell_groupprivilege (Read/Write)

387

oemdell_countrycode (Read/Write)

. . . . . . . .

395

. . . . . . .

395

. . . . . . . . . . .

396

/system1/sp1/oemdell_ssl1

. . . . . . . . . . . . . . .

396

generate (Read/Write)

. . . . . . . . . . . . . . .

396

oemdell_emailaddress (Read/Write)
oemdell_keysize (Read/Write)

oemdell_status (Read Only)

. . . . . . . . . .

397

. . . . . . . . . . .

397

. . . . . . . . . . . . .

397

oemdell_certtype (Read / Write)
/system1/sp1/oemdell_vmservice1
enabledstate (Read/Write)

396

. . . . . . . . . . . .

oemdell_singleboot (Read/Write)

398

. . . . . . . . .

oemdell_floppyemulation (Read/Write)

398

. . . . . .
. . . . .

399

portnumber (Read/Write)

. . . . . . . . . . . . .

399

portnumber (Read/Write)

. . . . . . . . . . . . .

400

/system1/sp1/oemdell_vmservice1/tcpendpt1

oemdell_sslenabled (Read Only) .

D RACADM and SM-CLP
Equivalencies . . . . . . .

400

. . . . . . . . .

. . . . . . . . . . . . .

401

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

423

Contents

iDRAC6 Enterprise Overview
The Integrated Dell™ Remote Access Controller (iDRAC6) is a systems
management hardware and software solution that provides remote
management capabilities, crashed system recovery, and power control
functions for Dell PowerEdge™ systems.
iDRAC6 uses an integrated System-on-Chip microprocessor for the remote
monitor/control system, and co-exists on the system board with the managed
PowerEdge server. The server operating system is concerned with executing
applications; iDRAC6 is concerned with monitoring and managing the
server’s environment and state outside of the operating system.
You can configure iDRAC6 to send you an e-mail or Simple Network
Management Protocol (SNMP) trap alert for warnings or errors. To help you
diagnose the probable cause of a system crash, iDRAC6 can log event data
and capture an image of the screen when it detects that the system has
crashed.
Managed servers are installed in a Dell M1000e system enclosure (chassis)
with modular power supplies, cooling fans, and a chassis management
controller (CMC). The CMC monitors and manages all components
installed in the chassis. A redundant CMC can be added to provide hot
failover if the primary CMC fails. The chassis provides access to iDRAC6
devices through its LCD display, local console connections, and its Web
interface.
All network connections to iDRAC6 are through the CMC network interface
(CMC RJ45 connection port labelled "Gb"). The CMC routes traffic to the
iDRAC6 devices on its servers through a private, internal network. This
private management network is outside of the server’s data path and outside
of the operating system’s control—that is, out-of-band. The managed servers’
inband network interfaces are accessed through I/O modules (IOMs) installed
in the chassis.

iDRAC6 Enterprise Overview

The iDRAC6 network interface is disabled by default. It must be configured
before iDRAC6 is accessible. After iDRAC6 is enabled and configured on the
network, it can be accessed at its assigned IP address with the iDRAC6 Web
interface, telnet or SSH, and supported network management protocols,
such as Intelligent Platform Management Interface (IPMI).

iDRAC6 Management Features
iDRAC6 provides the following management features:

•

Dynamic Domain Name System (DDNS) registration

•

Remote system management and monitoring using a Web interface,
the local RACADM command line interface via console redirection,
and the SM-CLP command line over a telnet/SSH connection

•

Support for Microsoft Active Directory® authentication — Centralizes
iDRAC6 user IDs and passwords in Active Directory using the standard
schema or an extended schema

•

Console Redirection — Provides remote system keyboard, video,
and mouse functions

•

Virtual Media — Enables a managed server to access a local media drive on
the management station or ISO CD/DVD images on a network share

•

Monitoring — Provides access to system information and status of
components

•

Access to system logs — Provides access to the system event log,
the iDRAC6 log, and the last crash screen of the crashed or unresponsive
system that is independent of the operating system state

•

Dell OpenManage™ software integration — Enables you to launch the
iDRAC6 Web interface from Dell OpenManage Server Administrator
or IT Assistant

•

Boot capture — Provides up to three boot capture screens for later
debugging

•

iDRAC6 alert — Alerts you to potential managed node issues through an
e-mail message or SNMP trap

•

Remote power management — Provides remote power management
functions, such as shutdown and reset, from a management console

iDRAC6 Enterprise Overview

•

Single Sign-On from CMC Web interface — Once you log into CMC,
you can access any IDRAC6 in the chassis without having to log in again

•

One-To-Many Firmware Update — Enables automated update of more
than one iDRAC6 without operator intervention

•

Intelligent Platform Management Interface (IPMI) support

•

Secure Sockets Layer (SSL) encryption — Provides secure remote system
management through the Web interface

•

Password-level security management — Prevents unauthorized access to a
remote system

•

Role-based authority — Provides assignable permissions for different
systems management tasks

iDRAC6 Security Features
iDRAC6 provides the following security features:
•

User authentication through Microsoft Active Directory (optional) or
hardware-stored user IDs and passwords

•

Role-based authority, which enables an administrator to configure specific
privileges for each user

•

User ID and password configuration through the Web interface, SM-CLP,
and local RACADM

•

SM-CLP and Web interfaces, which support 128-bit and 40-bit encryption
(for countries where 128 bit is not acceptable), using the SSL 3.0 standard

•

Session time-out configuration (in seconds) through the Web interface or
SM-CLP

•

Configurable IP ports (where applicable)
NOTE: Telnet does not support SSL encryption.

•

Secure Shell (SSH), which uses an encrypted transport layer for higher
security

•

Limited IP address range for clients connecting to iDRAC6

iDRAC6 Enterprise Overview

iDRAC6 Firmware Improvements
In addition, important improvements have been made to the code:
•

Major improvements in Active Directory lookup performance

•

Improved responsiveness of TCP-IP networking stack

•

Improved health status interface between iDRAC6 and CMC

•

Security improvements using multiple third-party analysis tools

Supported Platforms
iDRAC6 supports the following PowerEdge systems in the Dell PowerEdge
M1000e system enclosure:
•

PowerEdge M610

•

PowerEdge M710

See the iDRAC6 Readme file located on the Dell Support website at
support.dell.com/manuals for the latest supported platforms.

Supported Operating Systems
Table 1-1 lists the operating systems that support iDRAC6.
See the Dell Systems Software Support Matrix located on the Dell Support
website at support.dell.com/manuals for the latest information.

iDRAC6 Enterprise Overview

Table 1-1.

Supported Operating Systems

Operating System
Family

Operating System

Microsoft®
Windows®

Microsoft Windows Server® 2003 R2 Standard and Enterprise
(32-bit x86) Editions with SP2
Microsoft Windows Server 2003 Web, Standard and Enterprise
(32-bit x86) Editions with SP2
Microsoft Windows Server 2003 Standard and Enterprise (x64)
Editions with SP2
Microsoft Windows Storage Server 2003 R2 Express, Workgroup,
Standard, and Enterprise x64 Editions
Microsoft Windows Server 2008 Web, Standard, and Enterprise
(32-bit x86) Editions
Microsoft Windows Server 2008 Web, Standard, Enterprise and
Datacenter (x64) Editions
MS HyperV 2008

NOTE: When installing Windows Server 2003 with Service Pack 1,
be aware of changes to DCOM security settings. For more
information, see article 903220 from the Microsoft Support website
at support.microsoft.com/kb/903220.
Enterprise Linux WS, ES, and AS (version 4) (x86 and x86_64)
Red Hat®
Enterprise Linux® Enterprise Linux 5 (x86 and x86_64)
SUSE® Linux

Enterprise Server 10 (Gold) (x86_64)

VMware

ESX 3.5 U4

Supported Web Browsers
Table 1-2 lists the Web browsers that are supported as iDRAC6 clients.
See the iDRAC6 Readme file and the Dell Systems Software Support Matrix
located on the Dell Support website at support.dell.com/manuals for the
latest information.
NOTE: Due to serious security flaws, support for SSL 2.0 has been discontinued.
For your browser to work properly, you must enable SSL 3.0.

iDRAC6 Enterprise Overview

Table 1-2.

Supported Web Browsers

Operating System

Supported Web Browser

Windows

Internet Explorer® 6.0 with Service Pack 2 (SP2) for Windows
XP and Windows 2003 R2 SP2 only
Internet Explorer 7.0 for Windows Vista®, Windows XP,
Windows 2003 R2 SP2, and Windows Server 2008 only
Mozilla Firefox 2.0/3.0 for Windows (Java vKVM/vMedia
console only)

Linux

Mozilla Firefox 2.0/3.0 on Red Hat Enterprise Linux 4 and 5
(32-bit or 64-bit) and SUSE Linux Enterprise Server 10 (32-bit
or 64-bit)

Supported Remote Access Connections
Table 1-3 lists the connection features.
Table 1-3.

Supported Remote Access Connections

Connection

Features

iDRAC6 NIC

• 10Mbps/100Mbs/1Gbps Ethernet via CMC Gb Ethernet port
• DHCP support
• SNMP traps and e-mail event notification
• Support for SM-CLP (telnet or SSH) command shell for
operations such as iDRAC6 configuration, system boot, reset,
power on, and shutdown commands
• Support for IPMI utilities, such as IPMItool and ipmish

iDRAC6 Enterprise Overview

iDRAC6 Ports
Table 1-4 lists the ports on which iDRAC6 listens for connections. Table 1-5
identifies the ports that iDRAC6 uses as a client. This information is required
when opening firewalls for remote access to an iDRAC6.
Table 1-4.

iDRAC6 Server Listening Ports

Port Number

Function

22*

Secure Shell (SSH)

23*

Telnet

80*

HTTP

443*

HTTPS

623

RMCP/RMCP+

3668*, 3669*

Virtual Media Service

3770*, 3771*

Virtual Media Secure Service

5900*

Console Redirection keyboard/mouse

5901*

Console Redirection video

* Configurable port

Table 1-5.

iDRAC6 Client Ports

Port Number

Function

SMTP

DNS

DHCP-assigned IP address

TFTP

162

SNMP trap

636

LDAPS

3269

LDAPS for global catalog (GC)

iDRAC6 Enterprise Overview

Other Documents You May Need
In addition to this User Guide, the following documents provide additional
information about the setup and operation of iDRAC6 in your system:
•

The iDRAC6 online help provides information about using the
Web interface.

•

The Dell Chassis Management Controller Firmware Version 2.0 User Guide
and the Dell Chassis Management Controller Firmware Version 2.0
Administrator Reference Guide provide information about using the
controller that manages all modules in the chassis containing your
PowerEdge server.

•

The Dell OpenManage IT Assistant User’s Guide provides information
about using IT Assistant.

•

The Dell OpenManage Server Administrator User’s Guide provides
information about installing and using Server Administrator.

•

The Dell Update Packages User’s Guide provides information about
obtaining and using Dell Update Packages as part of your system
update strategy.

•

The Dell Unified Server Configurator User’s Guide provides information on
installing and running the Unified Server Configurator.

The following system documents are also available to provide more
information about the system in which iDRAC6 is installed:

•

The safety instructions that came with your system provide important
safety and regulatory information. For additional regulatory information,
see the Regulatory Compliance home page at www.dell.com/
regulatory_compliance. Warranty information may be included within
this document or as a separate document.

•

The Getting Started Guide provides an overview of system features,
setting up your system, and technical specifications.

•

The Hardware Owner’s Manual provides information about system
features and describes how to troubleshoot the system and install or
replace system components.

•

Systems management software documentation describes the features,
requirements, installation, and basic operation of the software.

iDRAC6 Enterprise Overview

•

Operating system documentation describes how to install (if necessary),
configure, and use the operating system software.

•

Documentation for any components you purchased separately provides
information to configure and install these options.

•

Updates are sometimes included with the system to describe changes to
the system, software, and/or documentation.
NOTE: Always read the updates first because they often supersede
information in other documents.

•

Release notes or readme files may be included to provide last-minute
updates to the system or documentation or advanced technical reference
material intended for experienced users or technicians.

iDRAC6 Enterprise Overview

Configuring iDRAC6 Enterprise
This section provides information about how to establish access to iDRAC6
and to configure your management environment to use iDRAC6.

Before You Begin
Gather the following items prior to configuring iDRAC6:
•

Dell Chassis Management Controller Firmware User Guide

•

Dell Systems Management Tools and Documentation DVD

The Dell Systems Management Tools and Documentation DVD includes the
following components:
•

DVD root — Contains the Dell Systems Build and Update Utility,
which provides server setup and system installation information

•

SYSMGMT — Contains the systems management software products
including Dell OpenManage Server Administrator

•

DOCS — Contains documentation for systems management software
products, peripherals, and RAID controllers

•

SERVICE — Contains the tools you need to configure your system, and
delivers the latest diagnostics and Dell-optimized drivers for your system

For more information, see the Server Administrator User’s Guide,
the IT Assistant User’s Guide, and the Unified Server Configurator User Guide
available on the Dell Support website at support.dell.com\manuals.

Configuring iDRAC6 Enterprise

Interfaces for Configuring iDRAC6
You can configure iDRAC6 using the iDRAC6 Configuration Utility,
the iDRAC6 Web interface, the local RACADM CLI, or the SM-CLP CLI.
The local RACADM CLI is available after you have installed the operating
system and the Dell OpenManage software on the managed server. Table 2-1
describes these interfaces.
For greater security, access to iDRAC6 configuration through the iDRAC6
Configuration Utility or Local RACADM CLI can be disabled by means of a
RACADM command (see "RACADM Subcommand Overview") or from the
GUI (see "Enabling or Disabling Local Configuration Access").
NOTE: Using more than one configuration interface at the same time may generate
unexpected results.
Table 2-1. Configuration Interfaces
Interface

Description

iDRAC6 Configuration
Utility

Accessed at boot time, the iDRAC6
Configuration Utility is useful when installing
a new PowerEdge server. Use it for setting up
the network and basic security features and
for enabling other features.

iDRAC6 Web Interface

The iDRAC6 Web interface is a browser-based
management application that you can use to
interactively manage iDRAC6 and monitor the
managed server. It is the primary interface for
day-to-day tasks, such as monitoring system
health, viewing the system event log,
managing local iDRAC6 users, and launching
the CMC Web interface and console
redirection sessions.

CMC Web Interface

In addition to monitoring and managing the
chassis, the CMC Web interface can be used to
view the status of a managed server, configure
iDRAC6 network settings, and to start, stop,
or reset the managed server.

Configuring iDRAC6 Enterprise

Table 2-1.

Configuration Interfaces (continued)

Interface

Description

Chassis LCD Panel

The LCD panel on the chassis containing
iDRAC6 can be used to view the high-level
status of the servers in the chassis.
During initial configuration of the CMC,
the configuration wizard allows you to enable
DHCP configuration of iDRAC6 networking.

Local RACADM

The local RACADM command line interface
runs on the managed server. It is accessed from
either the iKVM or a console redirection
session initiated from the iDRAC6
Web interface. RACADM is installed on
the managed server when you install
Dell OpenManage Server Administrator.
RACADM commands provide access to nearly
all iDRAC6 features. You can inspect sensor
data, system event log records, and the current
status and configuration values maintained in
iDRAC6. You can alter iDRAC6 configuration
values, manage local users, enable and disable
features, and perform power functions such as
shutting down or rebooting the managed
server.

iVMCLI

The iDRAC6 Virtual Media Command Line
Interface (iVM-CLI) provides the managed
server access to media on the management
station. It is useful for developing scripts to
install operating systems on multiple
managed servers.

Configuring iDRAC6 Enterprise

Table 2-1. Configuration Interfaces (continued)
Interface

Description

SM-CLP

SM-CLP is the Server Management
Workgroup Server Management-Command
Line Protocol (SM-CLP) implementation
incorporated in iDRAC6. The SM-CLP
command line is accessed by logging in to
iDRAC6 using telnet or SSH.
SM-CLP commands implement a useful
subset of the local RACADM commands.
The commands are useful for scripting since
they can be executed from a management
station command line. The output of
commands can be retrieved in well-defined
formats, including XML, facilitating scripting
and integration with existing reporting and
management tools.
See "RACADM and SM-CLP Equivalencies"
for a comparison of the RACADM and
SM-CLP commands.

IPMI

IPMI defines a standard way for embedded
management subsystems, such as iDRAC6,
to communicate with other embedded systems
and management applications.
You can use the iDRAC6 Web interface,
SM-CLP, or RACADM commands to configure
IPMI Platform Event Filters (PEF) and
Platform Event Traps (PET).
PEF causes iDRAC6 to perform specific
actions (for example, rebooting the managed
server) when it detects a condition. PET
instructs iDRAC6 to send e-mail or IPMI alerts
when it detects specified events or conditions.
You can also use standard IPMI tools such as
IPMItool and ipmish with iDRAC6 when you
enable IPMI Over LAN.

Configuring iDRAC6 Enterprise

Configuration Tasks
This section is an overview of the configuration tasks for the management
station, iDRAC6, and the managed server. The tasks to be performed include
configuring iDRAC6 so that it can be used remotely, configuring iDRAC6
features you want to use, installing the operating system on the managed
server, and installing management software on your management station and
the managed server.
The configuration tasks that can be used to perform each task are listed
beneath the task.
NOTE: Before performing configuration procedures in this guide, the CMC and I/O
modules must be installed in the chassis and configured, and the PowerEdge server
must be physically installed in the chassis.

Configure the Management Station
Set up a management station by installing the Dell OpenManage software,
a Web browser, and other software utilities. See "Configuring the
Management Station."

Configure iDRAC6 Networking
Enable the iDRAC6 network and configure IP, netmask, gateway, and DNS
addresses.
NOTE: Access to iDRAC6 configuration through the iDRAC6 Configuration Utility
or Local RACADM CLI can be disabled by means of a RACADM command
(see "RACADM Subcommand Overview") or from the GUI (see "Enabling or Disabling
Local Configuration Access").
NOTE: Changing the iDRAC6 network settings terminates all current network
connections to iDRAC6.
NOTE: The option to configure the server using the LCD panel is available only
during the CMC initial configuration. Once the chassis is deployed, the LCD panel
cannot be used to reconfigure iDRAC6.
NOTE: The LCD panel can be used to enable DHCP to configure the iDRAC6
network. If you want to assign static addresses, you must use the iDRAC6
Configuration Utility or the CMC Web interface.

Configuring iDRAC6 Enterprise

•

Chassis LCD Panel — See the Dell Chassis Management Controller
Firmware User Guide

•

iDRAC6 Configuration Utility — See "Using the iDRAC6 Configuration
Utility"

•

CMC Web interface — See "Configuring Networking Using the CMC
Web Interface"

•

RACADM — See "cfgLanNetworking"

Configure iDRAC6 Users
Set up the local iDRAC6 users and permissions. iDRAC6 holds a table of
sixteen local users in firmware. You can set usernames, passwords, and roles
for these users.
•

iDRAC6 Configuration Utility (configures administrative user only) —
See "LAN User Configuration"

•

iDRAC6 Web interface — See "Adding and Configuring iDRAC6 Users"

•

RACADM — See "Adding an iDRAC6 User"
NOTE: When using iDRAC6 in an Active Directory environment, the user names you
create must conform to the Active Directory naming convention in force.

Configure Active Directory
In addition to the local iDRAC6 users, you can use Microsoft® Active
Directory® to authenticate iDRAC6 user logins.
For more information, see "Using iDRAC6 With Microsoft Active Directory."
NOTE: When using iDRAC6 in an Active Directory environment, be sure your user
names conform to the Active Directory naming convention in force.

Configure IP Filtering and IP Blocking
In addition to user authentication, you can prevent unauthorized access by
rejecting connection attempts from IP addresses outside of a defined range
and by temporarily blocking connections from IP addresses where
authentication has failed multiple times within a configurable timespan.

•

iDRAC6 Web interface — See "Configuring IP Filtering and IP Blocking"

•

RACADM — See "Configuring IP Filtering (IP Range)" and "Configuring
IP Blocking"
Configuring iDRAC6 Enterprise

Configure Platform Events
Platform events occur when iDRAC6 detects a warning or critical condition
from one of the managed server’s sensors.
Configure Platform Event Filters (PEF) to choose the events you want to
detect, such as rebooting the managed server, when an event is detected.
•

iDRAC6 Web interface — See "Configuring Platform Event Filters (PEF)"

•

RACADM — See "Configuring PEF"

Configure Platform Event Traps (PET) to send alert notifications to an
IP address, such as a management station with IPMI software or to send an
e-mail to a specified e-mail address.
•

iDRAC6 Web interface — See "Configuring Platform Event Traps (PET)"

•

RACADM — See "Configuring PET"

Enabling or Disabling Local Configuration Access
Access to critical configuration parameters, such as network configuration
and user privileges, can be disabled. Once disabled, the setting remains
persistent across reboots. Configuration write access is blocked for both the
Local RACADM program and the iDRAC6 Configuration Utility (at boot).
Web access to configuration parameters is unimpeded and configuration data
is always available for viewing. For information about the iDRAC6 Web
interface, see "Enabling or Disabling Local Configuration Access."
For cfgRacTuning commands, see "cfgRacTuning."

Configure iDRAC6 Services
Enable or disable iDRAC6 network services — such as telnet, SSH, and the
Web server interface — and reconfigure ports and other service parameters.
•

iDRAC6 Web interface — See "Configuring iDRAC6 Services"

•

RACADM — See "Configuring iDRAC6 Telnet and SSH Services Using
Local RACADM"

Configuring iDRAC6 Enterprise

Configure Secure Sockets Layer (SSL)
Configure SSL for the iDRAC6 Web server.
•

iDRAC6 Web interface — See "Secure Sockets Layer (SSL)"

•

RACADM — See "cfgRacSecurity," "sslcsrgen," "sslcertupload,"
"sslcertdownload," and "sslcertview"

Configure Virtual Media
Configure the virtual media feature so that you can install the operating
system on the PowerEdge server. Virtual media allows the managed server to
access media devices on the management station or ISO CD/DVD images on
a network share as if they were devices on the managed server.
•

iDRAC6 Web interface — See "Configuring and Using Virtual Media"

•

iDRAC6 Configuration Utility — See "Virtual Media Configuration"

Configure a VFlash Media Card
Install and configure a VFlash Media card for use with iDRAC6.
•

iDRAC6 Web interface — See "Configuring a VFlash Media Card for Use
With iDRAC6"

Install the Managed Server Software
Install the operating system on the PowerEdge server using virtual media and
then install the Dell OpenManage software on the managed PowerEdge
server and set up the last crash screen feature.
•

Console redirection — See "Installing the Software on the Managed Server"

•

iVMCLI — See "Using the Virtual Media Command Line Interface Utility"

Configure the Managed Server for the Last Crash Screen Feature
Set up the managed server so that iDRAC6 can capture the screen image after
an operating system crash or freeze.
•

Managed server — See "Configuring the Managed Server to Capture the
Last Crash Screen" and "Disabling the Windows Automatic Reboot Option"

Configuring iDRAC6 Enterprise

Configuring Networking Using the CMC Web
Interface
NOTE: You must have Chassis Configuration Administrator privilege to set up
iDRAC6 network settings from the CMC.
NOTE: The default CMC user is root and the default password is calvin.
NOTE: The CMC IP address can be found in the iDRAC6 Web interface by clicking
System→ Remote Access→ CMC. You can also launch the CMC Web interface
from this screen.

Launching the iDRAC6 Web-based Interface From the CMC
The CMC provides limited management of individual chassis components,
such as servers. For complete management of these individual components, the
CMC provides a launch point for the server’s iDRAC6 Web-based interface.
To launch iDRAC6 from the Servers screen:
1 Log in to the CMC Web interface.
2 In the system tree, select Servers.
The Servers Status screen appears.
3 Click the Launch iDRAC GUI icon for the server you want to manage.
You can also launch the iDRAC6 Web-based interface for a single server using
the Servers list in the system tree:
1 Log in to the CMC Web interface.
2 Expand Servers in the system tree.
All of the servers (1–16) appear in the expanded Servers list.
3 Click the server you want to view.
The Server Status screen for the server you selected displays.
4 Click the Launch iDRAC GUI icon.

Configuring iDRAC6 Enterprise

Single Sign-On

Using the single sign-on feature, you can launch the iDRAC6 Web-based
interface from the CMC without having to log in a second time. Single
sign-on policies are described below.
•

CMC user who has Server Administrator set under User Privileges will
automatically be logged in to the iDRAC6 Web-based interface using
single sign-on. After logging in, the user is automatically granted iDRAC6
Administrator privileges. This is true even if the same user does not have
an account on iDRAC6, or if the account does not have the
Administrator’s privileges.

•

CMC user who does not have Server Administrator set under
User Privileges, but has the same account on iDRAC6, will automatically
be logged in to iDRAC6 using single sign-on. Once logged in to the
iDRAC6 Web-based interface, this user is granted the privileges that were
created for the iDRAC6 account.
NOTE: In this context, "the same account" means that the user has the same
login name and password for CMC as for iDRAC6. A user who has the same
login name but a different password will not be recognized as a valid user.

•

CMC user who does not have Server Administrator set under User
Privileges, or the same account on iDRAC6, will not be automatically
logged in to iDRAC6 using single sign-on. This user is directed to the
iDRAC6 log in screen after clicking Launch iDRAC GUI.
NOTE: In this case, users may be prompted to log in to iDRAC6.
NOTE: If the iDRAC6 network LAN is disabled (LAN Enabled = No),
single sign-on is not available.

NOTE: If the server is removed from the chassis, the iDRAC6 IP address is
changed, or the iDRAC6 network connection experiences a problem,
then clicking the Launch iDRAC GUI icon may display an error screen.

Configuring iDRAC6 Enterprise

Configuring Networking for iDRAC6
1 Click the System→ Remote Access→ iDRAC.
2 Click the Network/Security tab:
To enable or disable Serial Over LAN:
a

Click Serial Over LAN.
The Serial Over LAN screen appears.

Select the Enable Serial Over LAN check box. You may also change
the Baud Rate and Channel Privilege Level Limit settings.

Click Apply.

To enable or disable IPMI Over LAN:
a

Click Network.
The Network Configuration screen appears.

Click IPMI LAN Settings.

Select the Enable IPMI Over LAN check box. You may also change
the Channel Privilege Level Limit and Encryption Key settings.

Click Apply.

To enable or disable DHCP:
a

Click Network.
The Network Configuration screen appears.

Click Network Settings.
•

To use DHCP for NIC IP address, select the Use DHCP (for NIC
IP Address) check box.

•

To use DHCP to obtain DNS server addresses, select the Use
DHCP to obtain DNS server addresses check box.

Click Apply.
NOTE: If you choose not to enable DHCP, you must enter the static
IP address, netmask, and default gateway for the server.

Configuring iDRAC6 Enterprise

Viewing FlexAddress Mezzanine Card Fabric
Connections
The M1000e includes FlexAddress, an advanced multilevel, multistandard
networking system. FlexAddress allows the use of persistent, chassis-assigned
World Wide Names and MAC addresses (WWN/MAC) for each managed
server port connection.
NOTE: In order to avoid errors that may lead to an inability to power on the
managed server, you must have the correct type of mezzanine card installed for
each port and fabric connection.
Configuration of the FlexAddress feature is performed using the CMC Web
interface. For more information on the FlexAddress feature and its configuration,
see your Dell Chassis Management Controller Firmware Version 2.0 User Guide.
After the FlexAddress feature has been enabled and configured for the chassis,
click System→ Properties→ WWN/MAC to view a list of installed mezzanine
cards, the fabrics and ports to which they are connected, the fabric port location,
type of fabric, and server-configured or chassis-assigned MAC addresses for each
installed embedded Ethernet and optional mezzanine card port.
To view a list of installed mezzanine cards, the type of mezzanine cards
installed, and if FlexAddress is configured, click System→ Properties→
Summary.

Updating iDRAC6 Firmware
Updating iDRAC6 firmware installs a new firmware image in flash memory.
You can update the firmware using any of the following methods:

•

SM-CLP load command

•

iDRAC6 Web interface

•

Dell Update Package (for Linux or Microsoft Windows)

•

DOS iDRAC6 Firmware update utility

•

CMC Web interface

Configuring iDRAC6 Enterprise

Downloading the Firmware or Update Package
Download the firmware from support.dell.com. The firmware image is available
in several different formats to support the different update methods available.
To update iDRAC6 firmware using the iDRAC6 Web interface or SM-CLP,
or to recover iDRAC6 using the CMC Web interface, download the binary
image, packaged as a self-extracting archive.
To update iDRAC6 firmware from the managed server, download the
operating system-specific Dell Update Package (DUP) for the operating
system running on the server whose iDRAC6 you are updating.
To update iDRAC6 firmware using the DOS iDRAC6 Firmware update
utility, download both the update utility and the binary image, which are
packaged in self-extracting archive files.

Executing the Firmware Update
NOTE: When the iDRAC6 firmware update begins, all existing iDRAC6 sessions
are disconnected and new sessions are not permitted until the update process
is completed.
NOTE: The chassis fans run at 100% during the iDRAC6 firmware update. When the
update is complete, normal fan speed regulation resumes. This is normal behavior,
designed to protect the server from overheating during a time when it cannot send
sensor information to the CMC.
To use a Dell Update Package for Linux or Microsoft Windows, execute the
operating-specific DUP on the managed server.
When using the SM-CLP load command, place the firmware binary image in
a directory where a Trivial File Transfer Protocol (TFTP) server can serve it to
iDRAC6. See "Updating iDRAC6 Firmware Using SM-CLP."
When using the iDRAC6 Web interface or the CMC Web interface, place
the firmware binary image on a disk that is accessible to the management
station from which you are running the Web interface. See "Updating
iDRAC6 Firmware."
NOTE: The iDRAC6 Web interface also allows you to reset iDRAC6 configuration to
the factory defaults.

Configuring iDRAC6 Enterprise

You can use the CMC Web interface or CMC RACADM to update the
iDRAC6 firmware. This feature is available both when iDRAC6 firmware is in
Normal mode, as well as when it is corrupted. See "Updating iDRAC6
Firmware Using the CMC."
NOTE: After the CMC updates iDRAC6 firmware, iDRAC6 generates new SHA1 and
MD5 keys for the SSL certificate. Because the keys are different from those in the
open Web browser, all browser windows that are connected to iDRAC6 must be
closed after the firmware update is complete. If the browser windows are not
closed, an Invalid Certificate error message is displayed.
NOTE: If you are rolling back iDRAC6 firmware to an earlier version, you must
delete the existing Internet Explorer ActiveX® browser plugin on any
Windows-based Management Station to allow the firmware to install a compatible
version of the ActiveX plugin. See "Deleting the ActiveX Plugin" for more
information.
Deleting the ActiveX Plugin

You must delete the existing Internet Explorer ActiveX browser plugin on any
Windows-based Management Station to allow the firmware to install a
compatible version of the ActiveX plugin.
To delete the ActiveX plugin in Internet Explorer 6:
1 Go to C:\WINDOWS\Downloaded Program Files.
2 Delete the file DELL IDRAC 11G AVCView.
To delete the ActiveX plugin in Internet Explorer 7:
1 Open Internet Explorer 7.
2 Press the key to display the menu bar, if necessary.
3 Click Tools→ Manage Add-ons→ Enable or Disable Add-ons.
4 In the Manage Add-ons window, select Downloaded ActiveX Controls
(32-bit) from the Show drop-down menu.
5 In the Enabled list, click DELL IDRAC 11G AVCView, then click the
Delete button in the Delete ActiveX section.
6 Click OK.

Configuring iDRAC6 Enterprise

Using the iDRAC6 Web Interface
CAUTION: If iDRAC6 firmware becomes corrupted, as could occur if the iDRAC6
firmware update progress is interrupted before it completes, you can recover
iDRAC6 using the iDRAC6 Web interface.
NOTE: The firmware update, by default, retains the current iDRAC6 settings.
During the update process, you have the option to reset iDRAC6 configuration to the
factory defaults. If you set the configuration to the factory defaults, external
network access will be disabled when the update completes. You must enable and
configure the network using the iDRAC6 Configuration Utility.
1 Start the iDRAC6 Web interface.
2 In the system tree, select System→ Remote Access→ iDRAC.
3 Click the Update tab.
The Firmware Update screen appears.
NOTE: To update the firmware, iDRAC6 must be placed in an update mode.
Once in this mode, iDRAC6 will automatically reset, even if you cancel the
update process.

4 In the Upload (Step 1 of 4) section, click Browse to locate the firmware
image that you downloaded. You can also enter the path in the text field.
For example:
C:\Updates\V2.0\.
The default firmware image name is firmimg.imc.
5 Click Upload.
The file uploads to iDRAC6. This may take several minutes to complete.
NOTE: During the upload process, you abort the firmware upgrade process
by clicking Cancel. Clicking Cancel resets iDRAC6 to normal operating mode.

When the upload is complete, the Firmware Update - Validation (page 2
of 4) screen displays.
•

If the image file uploaded successfully and passed all verification checks,
a message appears indicating that the firmware image has been verified.

•

If the image did not upload successfully, or it did not pass the
verification checks, the firmware update returns to the Firmware
Update screen. You can try upgrading iDRAC6 again or click Cancel
to reset iDRAC6 to normal operating mode.
Configuring iDRAC6 Enterprise

NOTE: If you deselect the Preserve Configuration check box, iDRAC6 resets
to its default settings. In the default settings, the LAN is disabled, and you
cannot log in to the iDRAC6 Web interface. You must reconfigure the
LAN settings using the iDRAC6 Configuration Utility during BIOS POST.

6 By default, the Preserve Configuration option is enabled (checked) to preserve
the current settings on iDRAC6 after an upgrade. If you do not want the
settings to be preserved, clear the Preserve Configuration check box.
7 Click Begin Update to start the upgrade process. Do not interrupt the
upgrade process.
8 The Firmware Update - Updating (page 3 of 4) window, you will see the
status of the upgrade. The progress of the firmware upgrade operation,
measured in percentages, will appear in the Progress column.
9 Once the firmware update is complete, the Firmware Update - Update
Results (page 4 of 4) window will appear and iDRAC6 will reset
automatically. You must close the current browser window and reconnect
to iDRAC6 using a new browser window.

Using the DOS Update Utility
To update iDRAC6 firmware using the DOS update utility, boot the managed
server to DOS, and execute the idrac16d command. The syntax for the
command is:
idrac16d [-f] [-i=] [-l=]
When executed with no options, the idrac16d command updates iDRAC6
firmware using the firmware image file firmimg.imc in the current directory.
The options are as follows:

•

-f — Forces the update. The -f option can be used to downgrade the
firmware to an earlier image.

•

-i= — Specifies the file name of the firmware image.
This option is required if the firmware file name has been changed from
the default name firmimg.imc.

•

-l= — Logs output from the update activity. This option is
used for debugging.

Configuring iDRAC6 Enterprise

NOTE: If you enter incorrect arguments to the idrac16d command, or supply
the -h option, you may notice an additional option, -nopresconfig in the
usage output. This option is used to update the firmware without preserving any
configuration information. You should not use this option unless explicitly told to do
so by a Dell Support Representative, because it deletes all of your existing iDRAC6
configuration information such as IP addresses, users, and passwords.

Verifying the Digital Signature
A digital signature is used to authenticate the identity of the signer of a file
and to certify that the original content of the file has not been modified since
it was signed.
If you do not already have it installed on your system, you must install the
Gnu Privacy Guard (GPG) to verify a digital signature. To use the standard
verification procedure, perform the following steps:
1 Download the Dell Linux public GnuPG key, if you do not already have it,
by navigating to lists.us.dell.com and clicking the Dell Public GPG key
link. Save the file to your local system. The default name is linux-securitypublickey.txt.
2 Import the public key to your gpg trust database by running the following
command:
gpg --import
NOTE: You must have your private key to complete the process.
3 To avoid a distrusted-key warning, change the trust level for the Dell
Public GPG key.
a

Enter the following command:
gpg --edit-key 23B66A9D

Within the GPG key editor, enter fpr. The following message
appears:
pub 1024D/23B66A9D 2001-04-16 Dell, Inc.
(Product Group)
Primary key fingerprint: 4172 E2CE 955A 1776
A5E6 1BB7 CA77 951D 23B6 6A9D
If the fingerprint of your imported key is the same as above, you have a
correct copy of the key.

Configuring iDRAC6 Enterprise

While still in the GPG key editor, enter trust. The following menu
appears:
Please decide how far you trust this user to
correctly verify other users' keys (by looking
at passports, checking fingerprints from
different sources, etc.)
1
2
3
4
5
m

=
=
=
=
=
=

I don't know or won't say
I do NOT trust
I trust marginally
I trust fully
I trust ultimately
back to the main menu

Your decision?
d

Enter 5, then press . The following prompt appears:
Do you really want to set this key to ultimate
trust? (y/N)

Enter y to confirm your choice.

Enter quit to exit the GPG key editor.

You must import and validate the public key only once.
4 Obtain the package you need, for example the Linux DUP or selfextracting archive) and its associated signature file from the Dell Support
website at support.dell.com/support/downloads.
NOTE: Each Linux Update Package has a separate signature file, which is
shown on the same Web page as the Update Package. You need both the
Update Package and its associated signature file for verification. By default,
the signature file is named the same as the DUP filename with a .sign
extension. For example, the iDRAC6 firmware image has an associated .sign
file (IDRAC_FRMW_LX_2.0.BIN.sign), which is included in the self-extracting
archive with the firmware image (IDRAC_FRMW_LX_2.0.BIN). To download
the files, right-click on the download link and use the Save Target As…
file option.

Configuring iDRAC6 Enterprise

5 Verify the Update Package:
gpg --verify
The following example illustrates the steps that you should follow to verify a
Dell PowerEdge™ M610 iDRAC Update Package:
1 Download the following two files from support.dell.com:
•

IDRAC_FRMW_LX_2.0.BIN.sign

•

IDRAC_FRMW_LX_2.0.BIN

2 Import the public key by running the following command line:
gpg --import
The following output message appears:
gpg: key 23B66A9D: "Dell Computer Corporation
(Linux Systems Group) " not changed
gpg: Total number processed: 1
gpg: unchanged: 1
3 Set the GPG trust level for the Dell public key, if you haven’t done so
previously.
a

Enter the following command:
gpg --edit-key 23B66A9D

At the command prompt, enter the following commands:
fpr
trust

Enter 5, then press to choose I trust ultimately
from the menu.

Enter y to confirm your choice.

Enter quit to exit the GPG key editor.

This completes validation of the Dell public key.

Configuring iDRAC6 Enterprise

4 Verify the PowerEdge M610 iDRAC package digital signature by running
the following command:
gpg --verify IDRAC_FRMW_LX_2.0.BIN.sign
IDRAC_FRMW_LX_2.0.BIN
The following output message appears:
gpg: Signature made Fri Jul 11 15:03:47 2008
CDT using DSA key ID 23B66A9D
gpg: Good signature from "Dell, Inc. (Product
Group) "
NOTE: If you have not validated the key as shown in step 3, you will receive
additional messages:

gpg: WARNING: This key is not certified with a
trusted signature!
gpg: There is no indication that the signature
belongs to the owner.
Primary key fingerprint: 4172 E2CE 955A 1776
A5E6 1BB7 CA77 951D 23B6 6A9D

Clear Your Browser’s Cache
To be able to use the features in the latest iDRAC6, you must clear the
browser’s cache to remove/delete any old Web pages that may be stored on
the system.
Internet Explorer 6

1 Start Internet Explorer.
2 Click Tools, and then click Internet Options.
The Internet Options window appears.
3 Click the General tab.
4 Under Temporary Internet files, click Delete Files.
The Delete Files window appears.
5 Click to check Delete all offline content, and then click OK.
6 Click OK to close the Internet Options window.

Configuring iDRAC6 Enterprise

Internet Explorer 7

1 Start Internet Explorer.
2 Click Tools, and then click Internet Options...
The Internet Options window appears.
3 Click the General tab.
4 Under Browsing history, click Delete...
The Delete Files window appears.
5 Click Delete files next to Temporary Internet Files.
6 Click Close, and then click OK to exit the Internet Options window.
Firefox

1 Start Firefox.
2 Click Edit→ Preferences.
3 Click the Privacy tab.
4 Click the Clear Cache Now.
5 Click Close.

Updating the USC Repair Package
See the Dell Unified Server Configurator User Guide for information on
updating the USC repair package from the iDRAC6 Web interface.

Configuring iDRAC6 For Use With IT Assistant
Dell OpenManage IT Assistant can discover managed devices that comply
with Simple Network Management Protocol (SNMP) v1and v2c and
Intelligent Platform Management Interface (IPMI) v2.0.
iDRAC6 complies with IPMI v2.0. This section describes the steps necessary
to configure iDRAC6 for discovery and monitoring by IT Assistant. There are
two ways to accomplish this: through the iDRAC6 Configuration Utility and
through the iDRAC6 graphical Web interface.

Configuring iDRAC6 Enterprise

Using the iDRAC6 Configuration Utility to Enable Discovery and
Monitoring
To set up iDRAC6 for IPMI discovery and alert trap sending at the iDRAC6
Configuration Utility level, restart your managed server (blade) and observe
its power-up using the iKVM and either a remote monitor and console
keyboard or a Serial over LAN (SOL) connection. When Press
for Remote Access Setup displays, press .
When the iDRAC Configuration Utility screen appears, use the arrow keys
to scroll down.
1 Enable IPMI over LAN.
2 Enter your site's RMCP+ Encryption Key, if used.
NOTE: See your senior Network Administrator or CIO to discuss implementing
this option because it adds valuable security protection and must be implemented
site-wide in order to function properly.
3 At LAN Parameters, press to enter the sub-screen. Use Up and
Down arrows to navigate.
4 Toggle LAN Alert Enabled to On using the spacebar.
5 Enter the IP address of your Management Station into Alert Destination 1.
6 Enter a name string into iDRAC6 Name with a consistent naming convention
across your data center. The default is iDRAC6-{Service Tag}.
Exit the iDRAC6 Configuration Utility by pressing , , and then
pressing to save your changes. Your server will now boot into normal
operation, and it will be discovered during IT Assistant's next scheduled
Discovery pass.

Using the iDRAC6 Web Interface to Enable Discovery and Monitoring
IPMI Discovery can also be enabled through the remote Web interface:
1 Open a supported Web browser window.
2 Log in to the iDRAC6 Web-based interface using a login and password
with Administrator rights.
3 In the system tree, select System→ Remote Access→ iDRAC.
4 Click the Network/Security tab.
The Network Configuration screen appears.
58

Configuring iDRAC6 Enterprise

5 Click IPMI LAN Settings.
6 Ensure the Enable IPMI over LAN check box is selected (checked).
7 Select Administrator from the Channel Level Privileges drop-down
menu.
8 Enter your site's RMCP+ Encryption Key, if used.
9 Click Apply if you made any changes on this screen.
10 In the system tree, select System.
11 Click the Alert Management tab, and then click Platform Events.
The Platform Events screen appears, displaying a list of events for which
you can configure iDRAC6 to generate email alerts.
12 Enable email alerts for one or more events by selecting the check box in
the Generate Alerts column.
13 Click Apply if you made any changes on this screen.
14 Click Trap Settings.
The Platform Event Alert Destinations screen appears.
15 In the first available Destination IP Address field in the IPv4 Destination
List section, select the Enabled check box, and then enter the IP address
of your Management Station.
16 Click Apply if you made any changes on this screen.
You can now send a test trap by clicking the Send link in the Test Trap column.
Dell highly recommends that for security purposes you create a separate User
for IPMI commands with its own user name, IPMI over LAN privileges,
and password:
1 In the system tree, select System→ Remote Access→ iDRAC.
2 Click the Network Security tab, and then click Users.
The Users screen appears, displaying a list of all users (defined or
undefined).
3 Click the User ID of an undefined User.
The User Configuration screen for the selected User ID appears.
4 Select the Enable User check box, and then enter the user’s name
and password.
Configuring iDRAC6 Enterprise

5 In the IPMI LAN Privilege section, ensure that Maximum LAN User
Privilege Granted is set to Administrator.
6 Set other user privileges as needed.
7 Click Apply to save the new User settings.

Using IT Assistant to View iDRAC6 Status and Events
After discovery is complete, the iDRAC6 devices appear in the Servers
category of the ITA Devices detail screen, and iDRAC6 information can be
seen by clicking on the iDRAC6 name. This is different than DRAC5 systems,
where the management card shows up in the RAC group. This is due to the
fact that iDRAC6 uses IPMI discovery as opposed to SNMP.
iDRAC6 error and warning traps can now be seen in the primary Alert Log of
IT Assistant. They will show up in the Unknown category, but the trap
description and severity will be accurate.
For more information on using IT Assistant to manage your data center,
see the Dell OpenManage IT Assistant User's Guide.

Configuring iDRAC6 Enterprise

Configuring the Management
Station
A management station is a computer used to monitor and manage the
PowerEdge servers and other modules in the chassis. This section describes
software installation and configuration tasks that set up a management
station to work with iDRAC6 Enterprise. Before you begin configuring
iDRAC6, follow the procedures in this section to ensure that you have
installed and configured the tools you will need.

Management Station Set Up Steps
To set up your Management Station, perform the following steps:
1 Set up the management station network.
2 Install and configure a supported Web browser.
3 Install a Java Runtime Environment (JRE) (optional for Windows).
4 Install telnet or SSH clients, if required.
5 Install a TFTP server, if required.
6 Install Dell OpenManage IT Assistant (optional).

Management Station Network Requirements
To access iDRAC6, the management station must be on the same network as
the CMC RJ45 connection port labelled "GB1". It is possible to isolate the
CMC network from the network the managed server is on, so that your
management station may have LAN access to iDRAC6 but not to the
managed server.

Configuring the Management Station

Using the iDRAC6 console redirection feature (see "Configuring and Using
Serial Over LAN"), you can access the managed server’s console even if you
do not have network access to the server’s ports. You can also perform several
management functions on the managed server, such as rebooting the
computer, using iDRAC6 facilities. To access network and application services
hosted on the managed server, however, you may need an additional NIC in
the management computer.

Configuring a Supported Web Browser
The following sections provide instructions for configuring the supported
Web browsers for use with the iDRAC6 Web interface. For a list of supported
Web browsers, see "Supported Web Browsers."

Opening Your Web Browser
The iDRAC6 Web interface is designed to be viewed in a supported Web
browser at a minimum screen resolution of 800 pixels wide by 600 pixels high.
In order to view the interface and access all features, ensure that your
resolution is set to at least 800 by 600 pixels and/or resize your browser, as
needed.
NOTE: In some situations, most often during the first session after a firmware
update, users of Internet Explorer 6 may see the message Done, with errors
displayed in the browser status bar along with a partially rendered screen in the
main browser window. This error can also occur if you are experiencing
connectivity problems. This is a known issue with Internet Explorer 6. Close the
browser and start again.

Configuring Your Web Browser to Connect to the Web Interface
If you are connecting to the iDRAC6 Web interface from a management
station that connects to the Internet through a proxy server, you must
configure the Web browser to access the Internet from this server.
To configure the Internet Explorer Web browser to access a proxy server,
perform the following steps:
1 Open a Web browser window.
2 Click Tools, and click Internet Options.
The Internet Options window appears.

Configuring the Management Station

3 Select Tools→ Internet Options→ Security→ Local Network.
4 Click the Custom Level.
5 Select Medium-Low from the drop-down menu and click Reset. Click OK
to confirm. You will need to re-enter the Custom Level dialog by clicking
its button.
6 Then, scroll down to the section labeled ActiveX controls and plug-ins and
check each setting, as different versions of IE have differing settings in
Medium-Low state:
•

Automatic prompting for ActiveX controls: Enable

•

Binary and script behaviors: Enable

•

Download signed ActiveX controls: Prompt

•

Initialize and script ActiveX controls not marked as safe: Prompt

•

Run ActiveX controls and plug-ins: Enable

•

Script ActiveX controls marked safe for scripting: Enable

In the section on Downloads:
•

Automatic prompting for file downloads: Enable

•

File download: Enable

•

Font download: Enable

In the Miscellaneous section:
•

Allow META-REFRESH: Enable

•

Allow scripting of Internet Explorer Web browser control: Enable

•

Allow script-initiated windows without size or position constraints:
Enable

•

Don't prompt for client certificate selection when no certificates or
only one certificate exists: Enable

•

Launching programs and files in an IFRAME: Enable

•

Open files based on content, not file extension: Enable

•

Software channel permissions: Low safety

•

Submit nonencrypted form data: Enable

•

Use Pop-up Blocker: Disable

Configuring the Management Station

In the Scripting section:
•

Active scripting: Enable

•

Allow paste operations via script: Enable

•

Scripting of Java applets: Enable

7 Select Tools→ Internet Options→ Advanced.
8 Make sure the following items are checked or unchecked:
In the Browsing section:
•

Always send URLs as UTF-8: checked

•

Disable script debugging (Internet Explorer): checked

•

Disable script debugging: (Other): checked

•

Display a notification about every script error: unchecked

•

Enable Install On demand (Other): checked

•

Enable page transitions: checked

•

Enable third-party browser extensions: checked

•

Reuse windows for launching shortcuts: unchecked

In the HTTP 1.1 settings section:
•

Use HTTP 1.1: checked

•

Use HTTP 1.1 through proxy connections: checked

In the Java (Sun) section:
•

Use JRE 1.6.x_yz: checked (optional; version may differ)

In the Multimedia section:
•

Enable automatic image resizing: checked

•

Play animations in Web pages: checked

•

Play videos in Web pages: checked

•

Show pictures: checked

In the Security section:

•

Check for publishers' certificate revocation: unchecked

•

Check for signatures on downloaded programs: unchecked

Configuring the Management Station

•

Check for signatures on downloaded programs: checked

•

Use SSL 2.0: unchecked

•

Use SSL 3.0: checked

•

Use TLS 1.0: checked

•

Warn about invalid site certificates: checked

•

Warn if changing between secure and not secure mode: checked

•

Warn if forms submittal is being redirected: checked
NOTE: If you choose to alter any of the above settings, Dell recommends that
you learn and understand the consequences of doing so. For example, if you
choose to block pop-ups, portions of the iDRAC6 Web interface will not
function properly.

9 Click Apply, then OK.
10 Click the Connections tab.
11 Under Local Area Network (LAN) settings, click LAN Settings.
12 If the Use a proxy server box is selected, select the Bypass proxy server for
local addresses box.
13 Click OK twice.
14 Close and restart your browser to make sure all changes take effect.

Adding iDRAC6 to the List of Trusted Domains
When you access the iDRAC6 Web interface through the Web browser,
you may be prompted to add the iDRAC6 IP address to the list of trusted
domains if the IP address is missing from the list. When completed,
click Refresh or relaunch the Web browser to establish a connection to the
iDRAC6 Web interface.

Viewing Localized Versions of the Web Interface
The iDRAC6 Web interface is supported on the following operating system
languages:
•

English (en-us)

•

French (fr)

•

German (de)

Configuring the Management Station

•

Spanish (es)

•

Japanese (ja)

•

Simplified Chinese (zh-cn)

The ISO identifiers in parentheses denote the specific language variants
which are supported. Use of the interface with other dialects or languages is
not supported and may not function as intended. For some supported
languages, resizing the browser window to 1024 pixels wide may be necessary
in order to view all features.
The iDRAC6 Web interface is designed to work with localized keyboards for
the specific language variants listed above. Some features of the iDRAC6
Web interface, such as Console Redirection, may require additional steps to
access certain functions/letters. For more details on how to use localized
keyboards in these situations, see "Using the Video Viewer." Use of other
keyboards is not supported and may cause unexpected problems.
Internet Explorer 6.0 (Windows)

To view a localized version of the iDRAC6 Web interface in Internet Explorer,
perform the following steps:
1 Click the Tools menu and select Internet Options.
2 In the Internet Options window, click Languages.
3 In the Language Preference window, click Add.
4 In the Add Language window, select a supported language.
To select more than one language, press .
5 Select your preferred language and click Move Up to move the language to
the top of the list.
6 In the Language Preference window, click OK.
7 Click OK.
Firefox 2.0 (Linux or Windows)

To view a localized version of the iDRAC6 Web interface in Firefox 2.0,
perform the following steps:
1 Click Tools→ Options, and then click the Advanced tab.
2 Under Language, click Choose.
The Languages window appears.
66

Configuring the Management Station

3 In the Select a language to add... drop down menu, click to highlight a
supported language, and then click Add.
4 Click to select your preferred language, and then click Move Up until the
language appears a the top of the list.
5 Click OK to close the Languages window.
6 Click OK to close the Options window.

Setting the Locale in Linux
The console redirection viewer requires a UTF-8 character set to display
correctly. If your display is garbled, check your locale and reset the character
set if needed.
To set the character set on a Linux client with a Simplified Chinese GUI:
1 Open a command terminal.
2 Enter locale and press . Output similar to the following
output appears:
LANG=zh_CN.UTF-8
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=
3 If the values include zh_CN.UTF-8, no changes are required. If the
values do not include zh_CN.UTF-8, go to step 4.
4 Edit the /etc/sysconfig/i18n file with a text editor.

Configuring the Management Station

5 In the file, apply the following changes:
Current entry:
LANG="zh_CN.GB18030"
SUPPORTED="zh_CN.GB18030:zh_CH.GB2312:zh_CN:zh"
Updated entry:
LANG="zh_CN.UTF-8"
SUPPORTED="zh_CN.UTF8:zh_CN.GB18030:zh_CH.GB2312:zh_CN:zh"
6 Log out and then log in to the operating system.
When you switch from any other language, ensure that this fix is still valid.
If not, repeat this procedure.

Disabling the Whitelist Feature in Firefox
Firefox has a "whitelist" security feature that requires user permission to
install plugins for each distinct site that hosts a plugin. If enabled, the
whitelist feature requires you to install a console redirection viewer for each
iDRAC6 you visit, even though the viewer versions are identical.
To disable the whitelist feature and avoid unnecessary plugin installations,
perform the following steps:
1 Open a Firefox Web browser window.
2 In the address field, enter about:config and press .
3 In the Preference Name column, locate and double-click
xpinstall.whitelist.required.
The values for Preference Name, Status, Type, and Value change to
bold text. The Status value changes to user set and the Value value
changes to false.
4 In the Preferences Name column, locate xpinstall.enabled.
Ensure that Value is true. If not, double-click xpinstall.enabled to set
Value to true.

Configuring the Management Station

Installing a Java Runtime Environment (JRE)
NOTE: If you use the Internet Explorer browser, an ActiveX control is provided for
the console viewer. You can also use the Java console viewer with Internet
Explorer if you install a JRE and configure the console viewer in iDRAC6 Web
interface before you launch the viewer. See "Configuring Console Redirection and
Virtual Media in the iDRAC6 Web Interface" for more information.
You can choose to use the Java viewer instead before you launch the viewer.
If you use the Firefox browser you must install a JRE (or a Java Development
Kit [JDK]) to use the console redirection feature. The console viewer is a
Java application that is downloaded to the management station from the
iDRAC6 Web interface and then launched with Java Web Start on the
management station.
Go to java.sun.com to install a JRE or JDK. Version 1.6 (Java 6.0) or higher is
recommended.
The Java Web Start program is automatically installed with the JRE or JDK.
The file jviewer.jnlp is downloaded to your desktop and a dialog box prompts
you for what action to take. It may be necessary to associate the .jnlp
extension type with the Java Web Start application in your browser.
Otherwise, click Open with and then select the javaws application, which is
located in the bin subdirectory of your JRE installation directory.
NOTE: If the .jnlp file type is not associated with Java Web Start after installing JRE
or JDK, you can set the association manually. For Windows (javaws.exe) click
Start→ Control Panel→ Appearance and Themes→ Folder Options. Under the File
Types tab, highlight .jnlp under Registered file types, and then click Change. For
Linux (javaws), start Firefox, and click Edit→ Preferences→ Downloads, and then
click View and Edit Actions.
For Linux, once you have installed either JRE or JDK, add a path to the Java
bin directory to the front of your system PATH. For example, if Java is
installed in /usr/java, add the following line to your local .bashrc or /etc/
profile:
PATH=/usr/java/bin:$PATH; export PATH
NOTE: There may already be PATH-modification lines in the files. Ensure that the
path information you enter does not create conflicts.

Configuring the Management Station

Installing Telnet or SSH Clients
By default, the iDRAC6 telnet service is disabled and the SSH service is
enabled. Since telnet is an insecure protocol, you should use it only if you
cannot install an SSH client or your network connection is otherwise secured.
NOTE: There can be only one active telnet or SSH connection to iDRAC6 at a time.
When there is an active connection, other connection attempts are denied.

Telnet with iDRAC6
Telnet is included in Windows and Linux operating systems, and can be run
from a command shell. You may also choose to install a commercial or freely
available telnet client with more convenience features than the standard
version included with your operating system.
If your management station is running Windows XP SP1 or Windows 2003,
you may experience an issue with the characters in an iDRAC6 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.
NOTE: The hotfix is needed only for Windows XP SP1 and Windows 2003.
Windows XP SP2 fixed the issue.

Configuring the Backspace Key For Telnet Sessions
Depending on the telnet client, using the 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
key.
To configure Microsoft telnet clients to use the key,
perform the following steps:
1 Open a command prompt window (if required).
2 If you are not running a telnet session, enter:
telnet
If you are running a telnet session, press <]>.

Configuring the Management Station

3 At the prompt, enter:
set bsasdel
The following message appears:
Backspace will be sent as delete.
To configure a Linux telnet session to use the key, perform the
following steps:
1 Open a shell and enter:
stty erase ^h
2 At the prompt, enter:
telnet

SSH With iDRAC6
Secure Shell (SSH) is a command line connection with the same capabilities
as a telnet session, but with session negotiation and encryption to improve
security. iDRAC6 supports SSH version 2 with password authentication.
SSH is enabled by default on iDRAC6.
You can use PuTTY (Windows) or OpenSSH (Linux) on a management
station to connect to the managed server’s iDRAC6. When an error occurs
during the login procedure, the ssh client issues an error message.
The message text is dependent on the client and is not controlled
by iDRAC6.
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 one telnet or SSH session is supported at any given time. The session
timeout is controlled by the cfgSsnMgtSshIdleTimeout property as
described in "iDRAC6 Enterprise Property Database Group and Object
Definitions."
iDRAC6 SSH implementation supports multiple cryptography schemes,
as shown in Table 3-1.
NOTE: SSHv1 is not supported.

Configuring the Management Station

Table 3-1.

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

Installing a TFTP Server
NOTE: If you use only the iDRAC6 Web interface to transfer SSL certificates and
upload new iDRAC6 firmware, no TFTP server is required.
Trivial File Transfer Protocol (TFTP) is a simplified form of the File Transfer
Protocol (FTP). It is used with the SM-CLP and RACADM command line
interfaces to transfer files to and from iDRAC6.
The only times when you need to copy files to or from iDRAC6 are when you
update iDRAC6 firmware or install certificates on iDRAC6. If you choose to
use SM-CLP or RACADM when you perform these tasks, a TFTP server must
be running on a computer iDRAC6 can access by IP number or DNS name.

Configuring the Management Station

You can use the netstat -a command on Windows or Linux operating systems
to see if a TFTP server is already listening. Port 69 is the TFTP default port.
If no server is running, you have the following options:
•

Find another computer on the network running a TFTP service

•

If you are using Linux, install a TFTP server from your distribution

•

If you are using Windows, install a commercial or free TFTP server

Installing Dell OpenManage IT Assistant
Your system includes the Dell OpenManage System Management Software
Kit. This kit includes, but is not limited to, the following components:
•

Dell Systems Management Tools and Documentation DVD

•

Dell Support website and Readme files — Check Readme files and the
Dell Support website at support.dell.com for the most recent information
about your Dell products.

Use the Dell Systems Management Tools and Documentation DVD to install the
management console software, including Dell OpenManage IT Assistant,
on the management station. For instructions on installing this software,
see your Dell OpenManage Software Quick Installation Guide.

Configuring the Management Station

Configuring the Managed Server
This section describes tasks to set up the managed server to enhance
your remote management capabilities. These tasks include installing the
Dell Open Manage Server Administrator software and configuring the
managed server to capture the last crash screen.

Installing the Software on the Managed Server
The Dell management software includes the following features:
•

Local RACADM CLI — Allows you to configure and administer iDRAC6
from the managed server. It is a powerful tool for scripting configuration
and management tasks.

•

Server Administrator — Is required to use the iDRAC6 last-crash-screen
feature.

•

Server Administrator Instrumentation Service — Provides access to
detailed fault and performance information gathered by industry-standard
systems management agents and allows remote administration of
monitored systems, including shutdown, startup, and security.

•

Server Administration Storage Management Service — Provides storage
management information in an integrated graphical view.

•

Server Administrator Logs — Displays logs of commands issued to or by
the system, monitored hardware events, POST events, and system alerts.
You can view logs on the home page, print or save them as reports,
and send them by e-mail to a designated service contact.

Use the Dell Systems Management Tools and Documentation DVD to install
Server Administrator. For instructions on installing this software, see your
Quick Installation Guide.

Configuring the Managed Server

Configuring the Managed Server to Capture the
Last Crash Screen
iDRAC6 can capture the last crash screen so that you can view it in the Web
interface to help troubleshoot the cause of the managed server crash.
Follow these steps to enable the last crash screen feature.
1 Install the managed server software. For more information about installing
the managed server software, see the Dell OpenManage Server
Administrator User’s Guide.
2 If you are running Windows, ensure that Automatically Reboot is
deselected in the Windows Startup and Recovery Settings. See "Disabling
the Windows Automatic Reboot Option."
3 Enable the Last Crash Screen (disabled by default) in the iDRAC6
Web interface.
To enable the Last Crash Screen in the iDRAC6 Web interface,
click System→ Remote Access→ iDRAC→ Network/Security→ Services,
then check the Enable checkbox under the Automatic System Recovery
Agent Settings heading.
To enable the Last Crash Screen using local RACADM, open a command
prompt on the managed server and enter the following command:
racadm config -g cfgRacTuning -o
cfgRacTuneAsrEnable 1
4 In the Server Administrator Web-based interface, enable the Auto
Recovery timer and set the Auto Recovery action to Reset, Power Off,
or Power Cycle.
For information about how to configure the Auto Recovery timer, see the
Server Administrator User's Guide. To ensure that the last crash screen can
be captured, the Auto Recovery timer should be set to 60 seconds.
The default setting is 480 seconds.
The last crash screen is not available when the Auto Recovery action is set
to Shutdown or Power Cycle if the managed server is powered off.

Configuring the Managed Server

Disabling the Windows Automatic Reboot Option
To ensure that iDRAC6 can capture the last crash screen, disable the
Automatic Reboot option on managed servers running Windows Server or
Windows Vista.
1 Open the Windows Control Panel and double-click the System icon.
2 Click the Advanced tab.
3 Under Startup and Recovery, click Settings.
4 Deselect the Automatically Reboot check box.
5 Click OK twice.

Configuring the Managed Server

Configuring iDRAC6 Enterprise
Using the Web Interface
iDRAC6 provides a Web interface that enables you to configure iDRAC6
properties and users, perform remote management tasks, and troubleshoot a
remote (managed) system for problems. For everyday systems management,
use the iDRAC6 Web interface. This chapter provides information about how
to perform common systems management tasks with the iDRAC6 Web
interface and provides links to related information.
Most Web interface configuration tasks can also be performed with local
RACADM commands or with SM-CLP commands.
Local RACADM commands are executed from the managed server. For more
information about local RACADM, see "Using the Local RACADM
Command Line Interface."
SM-CLP commands are executed in a shell that can be accessed remotely
with a telnet or SSH connection. For more information about SM-CLP,
see "Using iDRAC6 Enterprise SM-CLP Command Line Interface."

Configuring iDRAC6 Enterprise Using the Web Interface

Accessing the Web Interface
To access the iDRAC6 Web interface, perform the following steps:
1 Open a supported Web browser window.
See "Supported Web Browsers" for more information.
2 In the Address field, enter https:// and
press .
If the default HTTPS port number (port 443) has been changed, enter:
https://:
where iDRAC-IP-address is the IP address for iDRAC6 and port-number is
the HTTPS port number.
The iDRAC6 Login window appears.

Logging In
You can log in as either an iDRAC6 user or as a Microsoft® Active Directory®
user. The default user name and password are root and calvin, respectively.
You must have been granted Login to iDRAC privilege by the administrator
to log in to iDRAC6.
To log in, perform the following steps:
1 In the Username field, enter one of the following:
•

Your iDRAC6 user name.
The user name for local users is case sensitive. Examples are root,
it_user, or john_doe.

•

Your Active Directory user name.
You can use any of the following forms for Active Directory names:
\, /, or
@. They are not case sensitive. Examples are
dell.com\john_doe, or JOHN_DOE@DELL.COM. Alternatively,
you can enter the domain in the Domain field.

2 In the Password field, enter your iDRAC6 user password or Active
Directory user password. Passwords are case sensitive.
3 Click OK or press .
80

Configuring iDRAC6 Enterprise Using the Web Interface

Logging Out
1 In the upper-right corner of the main window, click Logout to close the
session.
2 Close the browser window.
NOTE: The Logout button does not appear until you log in.
NOTE: Closing the browser without gracefully logging out may cause 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 may remain active until the
session timeout is reached.
NOTE: Closing the iDRAC6 Web interface within 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, located at support.microsoft.com.

Using Multiple Browser Tabs and Windows
Different versions of Web browsers exhibit different behaviors when opening
new tabs and windows. Each window is a new session, but each new tab is not.
Microsoft Internet Explorer 6 does not support tabs; therefore, each browser
window opened becomes a new iDRAC6 Web interface session. Internet
Explorer 7 has the option to open tabs as well as windows. Each tab inherits
the characteristics of the most recently opened tab. For example, if a user logs
in with Power User privileges on one tab, and then logs in as Administrator on
another tab, both open tabs then have Administrator privileges. Closing any
one tab expires all iDRAC6 Web interface tabs.
Tab behavior in Firefox 2 is the same as Internet Explorer 7; new tabs are new
sessions. Window behavior in Firefox is different. Firefox windows will
operate with the same privileges as the latest window opened. For example,
if one Firefox window is open with a Power User logged in and another
window is opened with Administrator privileges, both users will now have
Administrator privileges.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-1.

User Privilege Behavior in Supported Browsers

Browser

Tab Behavior

Window Behavior

Microsoft Internet
Explorer 6

Not applicable

New session

Microsoft Internet
Explorer 7

From latest session opened New session

Firefox 2

From latest session opened From latest session opened

Configuring the iDRAC6 NIC
This section assumes that iDRAC6 has already been configured and is
accessible on the network. See "Configure iDRAC6 Networking" for help with
the initial iDRAC6 network configuration.

Configuring the Network and IPMI LAN Settings
NOTE: You must have Configure iDRAC6 privilege to perform the following steps.
NOTE: Most DHCP servers require a server to store a client identifier token in its
reservations table. The client (iDRAC, for example) must provide this token during
DHCP negotiation. iDRAC6 supplies the client identifier option using a one-byte
interface number (0) followed by a six-byte MAC address.
1 Click System→ Remote Access→ iDRAC.
2 Click the Network/Security tab.
The Network Configuration screen appears.
3 Configure network and IPMI LAN settings as needed. See Table 5-2 and
Table 5-3 for descriptions of the Network Settings and IPMI LAN
Settings options.
4 Click Apply.
5 Click the appropriate button to continue. See Table 5-4.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-2.

Network Settings

Setting

Description

Enable NIC

When checked, indicates that the NIC is enabled and activates
the remaining controls in this group. When a NIC is disabled,
all communication to and from iDRAC6 via the network is
blocked.
The default is off.

MAC Address

Displays the Media Access Control (MAC) address that
uniquely identifies each node in a network. The MAC address
cannot be changed.

Use DHCP (For
NIC IP Address)

Prompts iDRAC6 to obtain an IP address for the NIC from the
Dynamic Host Configuration Protocol (DHCP) server.
Also deactivates the Static IP Address, Static Subnet Mask, and
Static Gateway controls.
The default is off.

Static IP Address

Allows you to enter or edit a static IP address for the iDRAC6
NIC. To change this setting, deselect the Use DHCP (For NIC
IP Address) checkbox.

Static Subnet Mask Allows you to enter or edit a subnet mask for the iDRAC6 NIC.
To change this setting, first deselect the Use DHCP (For NIC
IP Address) checkbox.
Static Gateway

Allows you to enter or edit a static gateway for the iDRAC6 NIC.
To change this setting, first deselect the Use DHCP (For NIC
IP Address) checkbox.

Use DHCP to
obtain DNS server
addresses

Enable DHCP to obtain DNS server addresses by selecting the
Use DHCP to obtain DNS server addresses checkbox. When
not using DHCP to obtain the DNS server addresses, provide
the IP addresses in the Static Preferred DNS Server and Static
Alternate DNS Server fields.
The default is off.

NOTE: When the Use DHCP to obtain DNS server addresses
checkbox is selected, IP addresses cannot be entered into the
Static Preferred DNS Server and Static Alternate DNS Server
fields.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-2.

Network Settings (continued)

Setting

Description

Static Preferred
DNS Server

Allows the user to enter or edit a static IP address for the
preferred DNS server. To change this setting, first deselect the
Use DHCP to obtain DNS server addresses checkbox.

Static Alternate
DNS Server

Uses the secondary DNS server IP address when Use DHCP to
obtain DNS server addresses is not selected. Enter an IP address
of 0.0.0.0 if there is no alternate DNS server.

Registers the iDRAC6 name on the DNS server.

DNS iDRAC
Name

Displays the iDRAC6 name only when Register iDRAC on DNS
is selected. The default name is idrac-service_tag, where
service_tag is the service tag number of the Dell server.
For example: idrac-00002.

Use DHCP for
DNS Domain
Name

Uses the default DNS domain name. When the box is not
selected and the Register iDRAC on DNS option is selected,
modify the DNS domain name in the DNS Domain Name field.

The default is Disabled.

NOTE: To select the Use DHCP for DNS Domain Name checkbox,
also select the Use DHCP (For NIC IP Address) checkbox.
DNS Domain
Name

Table 5-3.

The default DNS Domain Name is blank. When the
Use DHCP for DNS Domain Name checkbox is selected,
this option is grayed out and the field cannot be modified.

IPMI LAN Settings

Setting

Description

Enable IPMI
Over LAN

When checked, indicates that the IPMI LAN channel is enabled.
The default is off.

Channel
Privilege Level
Limit

Configures the maximum privilege level, for the user, that can be
accepted on the LAN channel. Select one of the following options:
Administrator, Operator, or User. The default is Administrator.

Encryption Key Configures the encryption key: 0 to 20 hexadecimal characters
(with no blanks allowed). The default is blank.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-4.

Network Configuration Buttons

Button

Description

Advanced Settings

Opens the Network Security screen, allowing the user to enter
IP Range, and IP Blocking attributes.

Prints the Network Configuration values that appear on the
screen.

Refresh

Reloads the Network Configuration screen.

Apply

Saves any new settings made to the network configuration
screen.

NOTE: Changes to the NIC IP address settings will close all user
sessions and require users to reconnect to the iDRAC6 Web
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.

Configuring IP Filtering and IP Blocking
NOTE: You must have Configure iDRAC permission to perform the following steps.
1 Click System→ Remote Access→ iDRAC.
2 Click the Network/Security tab.
The Network Configuration screen appears.
3 Click Advanced Settings.
The Network Security screen appears.
4 Configure IP filtering and blocking settings as needed. See Table 5-5 for
descriptions of the IP filtering and blocking settings.
5 Click Apply.
6 Click the appropriate button to continue. See Table 5-6.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-5.

Network Security Settings

Settings

Description

IP Range Enabled

Enables the IP Range checking feature, which defines a range of
IP addresses that can access iDRAC6. The default is off.

IP Range Address

Determines the acceptable IP subnet address. The default is
192.168.1.0.

IP Range Subnet
Mask

Defines the significant bit positions in the IP address.
The subnet mask should be in the form of a netmask, where the
more significant bits are all 1's with a single transition to all
zeros in the lower-order bits. The default is 255.255.255.0.

IP Blocking
Enabled

Enables the IP address blocking feature, which limits the
number of failed login attempts from a specific IP address for a
preselected time span. The default is off.

IP Blocking Fail
Count

Sets the number of login failures attempted from an IP address
before the login attempts are rejected from that address.
The default is 10.

IP Blocking Fail
Window

Determines the time span in seconds within which IP Block
Fail Count failures must occur to trigger the IP Block Penalty
Time. The default is 3600.

IP Blocking Penalty The time span in seconds that login attempts from an
Time
IP address with excessive failures are rejected. The default
is 3600.

Table 5-6.

Network Security Buttons

Button

Description

Prints the Network Security values that appear on the screen.

Refresh

Reloads the Network Security screen.

Apply

Saves any new settings that you made to the Network
Security screen.

Go Back to
Network Page

Returns to the Network screen.

Configuring iDRAC6 Enterprise Using the Web Interface

Configuring Platform Events
Platform event configuration provides a mechanism for configuring iDRAC6
to perform selected actions on certain event messages. The actions include no
action, reboot system, power cycle system, power off system, and generate an
alert (Platform Event Trap [PET] and/or e-mail).
The filterable platform events are listed in Table 5-7.
.

Table 5-7.

Filterable Platform Events

Index

Platform Event

Battery Warning Assert

Battery Critical Assert

Discrete Voltage Critical Assert

Temperature Warning Assert

Temperature Critical Assert

Redundancy Degraded

Redundancy Lost

Processor Warning Assert

Processor Critical Assert

Processor Absent Assert

Event Log Critical Assert

Watchdog Critical Assert

When a platform event occurs (for example, a battery warning assert),
a system event is generated and recorded in the System Event Log (SEL).
If this event matches a platform event filter (PEF) that is enabled and you
have configured the filter to generate an alert (PET or e-mail), then a PET or
e-mail alert is sent to one or more configured destinations.
If the same platform event filter is also configured to perform an action
(such as rebooting the system), the action is performed.

Configuring iDRAC6 Enterprise Using the Web Interface

Configuring Platform Event Filters (PEF)
NOTE: Configure platform event filters before you configure the platform event
traps or e-mail alert settings.
1 Log in to the iDRAC6 Web interface.
2 Click System, and then click the Alert Management tab.
The Platform Events screen appears.
3 Select the Generate Alert check box beside each event for which you want
an alert generated.
NOTE: You can enable or disable alert generation for all events by selecting or
deselected the check box next to the Generate Alert column heading.
4 Select the radio button below the action you would like to enable for each
event. You can only select one action for each event.
5 Click Apply.
NOTE: Generate Alert must be enabled for an alert to be sent to any valid,
configured destination (PET or e-mail).

Configuring Platform Event Traps (PET)
NOTE: You must have Configure iDRAC permission to add or enable/disable an
SNMP alert. The following options will not be available if you do not have Configure
iDRAC permission.
1 Log in to the iDRAC6 Web interface.
2 Ensure that you followed the procedures in "Configuring Platform Event
Filters (PEF)."
3 Click System, and then click the Alert Management tab.
The Platform Events screen appears.
4 Click Trap Settings.
The Platform Event Alert Destinations screen appears.
5 Configure your PET destination IP address:
a

Select the Enable check box next to the Destination Number you
would like to activate.

Enter an IP address in the Destination IP Address box.
NOTE: The destination community string must be the same as the iDRAC6
community string.

Configuring iDRAC6 Enterprise Using the Web Interface

Click Apply.
NOTE: To successfully send a trap, configure the Community String value on
the Network Configuration screen. The Community String value indicates the
community string to use in a Simple Network Management Protocol (SNMP)
alert trap sent from iDRAC6. SNMP alert traps are transmitted by iDRAC6
when a platform event occurs. The default setting for the Community String is
Public.

To test the configured alert, click Send.

To add an additional destination IP address, repeat Step a through
Step d. You may specify up to four destination IP addresses.

Configuring E-Mail Alerts
1 Log in to the iDRAC6 Web interface.
2 Ensure that you followed the procedures in "Configuring Platform Event
Filters (PEF)."
3 Click System, and then click the Alert Management tab.
The Platform Events screen appears.
4 Click Email Alert Settings.
The Email Alert Settings screen appears.
5 Configure your e-mail alert destination.
a

Select the Enabled check box for the first undefined email alert.

Enter a valid email address in the Destination Email Address field.

Click Apply.
NOTE: To successfully send a test e-mail, the SMTP Server Address must be
configured in the SMTP (e-mail) Server Address Settings section of the Email
Alert Settings screen. The IP address of the SMTP Server communicates with
iDRAC6 to send e-mail alerts when a platform event occurs.

Click Send to test the configured e-mail alert (if desired).

To add an additional email alert destination, repeat Step a through
Step d. You may specify up to four email alert destinations.

Configuring iDRAC6 Enterprise Using the Web Interface

Configuring IPMI Over LAN
1 Log in to the iDRAC6 Web interface.
2 Configure IPMI over LAN:
a

Click System→ Remote Access→ iDRAC, and then click the
Network/Security tab.
The Network Configuration screen appears.

Click IPMI LAN Settings.

Select the Enable IPMI Over LAN check box.

Update the IPMI LAN channel privileges, if required:
NOTE: This setting determines the IPMI commands that can be executed
from the IPMI over LAN interface. For more information, see the IPMI 2.0
specifications.

Under IPMI LAN Settings, click the Channel Privilege Level Limit
drop-down menu, select Administrator, Operator, or User, and then
click Apply.
e

Set the IPMI LAN channel encryption key, if required.
NOTE: The iDRAC6 IPMI supports the RMCP+ protocol.
NOTE: The encryption key must consist of an even number of hexadecimal
characters with a maximum length of 20 characters.

Under IPMI LAN Settings in the Encryption Key field, enter the
encryption key.
f

Click Apply.

3 Configure IPMI Serial over LAN (SOL):
a

Click System→ Remote Access→ iDRAC, and then click the
Network/Security tab.
The Network Configuration screen appears.

Open the Serial Over LAN screen.

Select the Enable Serial Over LAN check box.

Configuring iDRAC6 Enterprise Using the Web Interface

Update the IPMI SOL baud rate, if needed, by selecting a data speed
from the Baud Rate drop-down menu.
NOTE: To redirect the serial console over the LAN, ensure that the SOL baud
rate is identical to your managed server’s baud rate.

Click Apply.

Adding and Configuring iDRAC6 Users
To manage your system with iDRAC6 and maintain system security, create
unique users with specific administrative permissions (or role-based authority).
To add and configure iDRAC6 users, perform the following steps:
NOTE: You must have Configure iDRAC permission to perform the following steps.
1 Click System→ Remote Access→ iDRAC and then click the Network/
Security tab.
2 Open the Users screen to configure users.
The Users screen displays each user’s User ID, State, Username,
IPMI LAN Privileges, iDRAC Privileges, and Serial Over LAN.
NOTE: User-1 is reserved for the IPMI anonymous user and is not configurable.
3 In the User ID column, click a user ID number.
4 On the User Configuration screen, configure the user’s properties and
privileges.
Table 5-8 describes the General settings for configuring an iDRAC6 user
name and password.
Table 5-9 describes the IPMI LAN Privileges for configuring the user’s
LAN privileges.
Table 5-10 describes the User Group permissions for the IPMI LAN
Privileges and the iDRAC User Privileges settings.
Table 5-11 describes the iDRAC Group permissions. If you add an iDRAC
User Privilege to the Administrator, Power User, or Guest User, the
iDRAC Group will change to the Custom group.
5 When completed, click Apply.
6 Click the appropriate button to continue. See Table 5-12.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-8.

General Properties

Property

Description

User ID

Contains one of 16 preset User ID numbers. This field
cannot be edited.

Enable User

When checked, indicates that the user’s access to
iDRAC6 is enabled. When unchecked, user access
is disabled.

Username

Specifies an iDRAC6 user name with up to 16 characters.
Each user must have a unique user name.

NOTE: User names on iDRAC6 cannot include the / (forward
slash) or . (period) characters.

NOTE: If the user name is changed, the new name will not
appear in the user interface until the next user login.
Change Password

Enables the New Password and Confirm New Password
fields. When unchecked, the user’s Password cannot be
changed.

New Password

Enables editing the iDRAC6 user’s password. Enter a
Password with up to 20 characters. The characters will
not display.

Confirm New Password

Re-enter the iDRAC6 user’s password to confirm.

Table 5-9.

IPMI LAN User Privileges

Property

Description

Maximum LAN User
Privilege Granted

Specifies the user’s maximum privilege on the IPMI LAN
channel to one of the following user groups: None,
Administrator, Operator, or User.

Enable Serial Over LAN

Allows the user to use IPMI Serial Over LAN.
When checked, this privilege is enabled.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-10.

iDRAC6 User Privileges

Property

Description

iDRAC Group

Specifies the user’s maximum iDRAC6 user privilege as
one of the following: Administrator, Power User, Guest
User, Custom, or None.
See Table 5-11 for iDRAC6 Group permissions.

Enables the user to log in to iDRAC6.

Configure iDRAC

Enables the user to configure iDRAC6.

Configure Users

Enables the user to allow specific users to access the
system.

Clear Logs

Enables the user to clear the iDRAC6 logs.

Execute Server Control
Commands

Enables the user to execute RACADM commands.

Access Console
Redirection

Enables the user to run Console Redirection.

Access Virtual Media

Enables the user to run and use Virtual Media.

Test Alerts

Enables the user to send test alerts (e-mail and PET) to a
specific user.

Execute Diagnostic
Commands

Enables the user to run diagnostic commands.

Table 5-11.

iDRAC6 Group Permissions

User Group

Permissions Granted

Administrator

Login to iDRAC, Configure iDRAC, Configure Users, Clear
Logs, Execute Server Control Commands, Access Console
Redirection, Access Virtual Media, Test Alerts, Execute
Diagnostic Commands

Power User

Login to iDRAC, Clear Logs, Execute Server Control
Commands, Access Console Redirection, Access Virtual
Media, Test Alerts

Guest User

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-11. iDRAC6 Group Permissions (continued)
User Group

Permissions Granted

Custom

Selects any combination of the following permissions: Login to
iDRAC, Configure iDRAC, Configure Users, Clear Logs,
Execute Server Action Commands, Access Console
Redirection, Access Virtual Media, Test Alerts, Execute
Diagnostic Commands

None

No assigned permissions

Table 5-12. User Configuration Buttons
Button

Action

Prints the User Configuration values that appear on the
screen.

Refresh

Reloads the User Configuration screen.

Apply

Saves any new settings made to the user configuration.

Go Back To Users
screen

Returns to the Users screen.

Securing iDRAC6 Communications Using SSL and
Digital Certificates
This section provides information about the following data security features
that are incorporated in iDRAC6:

•

Secure Sockets Layer (SSL)

•

Certificate Signing Request (CSR)

•

Accessing the SSL main menu

•

Generating a new CSR

•

Uploading a server certificate

•

Viewing a server certificate

Configuring iDRAC6 Enterprise Using the Web Interface

Secure Sockets Layer (SSL)
iDRAC6 includes a Web server that is configured to use the industry-standard
SSL security protocol to transfer encrypted data over a network. Built upon
public-key and private-key encryption technology, SSL is a widely accepted
technology for providing authenticated and encrypted communication
between clients and servers to prevent eavesdropping across a network.
An SSL-enabled system can perform the following tasks:
•

Authenticate itself to an SSL-enabled client

•

Allow the client to authenticate itself to the server

•

Allow both systems to establish an encrypted connection

The encryption process provides a high level of data protection. iDRAC6
employs the 128-bit SSL encryption standard, the most secure form of
encryption generally available for Internet browsers in North America.
The iDRAC6 Web server has a Dell self-signed SSL digital certificate
(Server ID) by default. To ensure high security over the Internet, replace the
Web server SSL certificate with a certificate signed by a well-known
certificate authority. To initiate the process of obtaining a signed certificate,
you can use the iDRAC6 Web interface to generate a Certificate Signing
Request (CSR) with your company’s information. You can then submit the
generated CSR to a CA such as VeriSign or Thawte.

Certificate Signing Request (CSR)
A CSR is a digital request to a Certificate Authority (CA) for a secure server
certificate. Secure server certificates allow clients of the server to trust the
identity of the server they have connected to and to negotiate an encrypted
session with the server.
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 a CSR, they review and verify the information
the CSR contains. If the applicant meets the CA’s security standards, the
CA issues a digitally-signed certificate that uniquely identifies that applicant
for transactions over networks and on the Internet.

Configuring iDRAC6 Enterprise Using the Web Interface

After the CA approves the CSR and sends the certificate, upload the
certificate to the iDRAC6 firmware. The CSR information stored on iDRAC6
firmware must match the information contained in the certificate.

Accessing the SSL Main Menu
1 Click System→ Remote Access→ iDRAC, then click the Network/
Security tab.
2 Click SSL to open the SSL Main Menu screen.
Use the SSL Main Menu screen to generate a CSR to send to a CA. The CSR
information is stored on the iDRAC6 firmware.
Table 5-13 describes the options available when generating a CSR.
Table 5-14 describes the available buttons on the SSL Main Menu screen.
Table 5-13. SSL Main Menu Options
Field

Description

Generate a New
Certificate Signing
Request (CSR)

Select the option and click Next to open the Generate
Certificate Signing Request (CSR) screen.

NOTE: Each new CSR overwrites any previous 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 Server
Certificate

Select the option and click Next to open the Certificate
Upload screen and upload the certificate sent to you by
the CA.

NOTE: Only X509, Base 64-encoded certificates are accepted
by iDRAC6. DER-encoded certificates are not accepted.
View Server Certificate Select the option and click Next to open the View Server
Certificate screen and view an existing server certificate.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-14.

SSL Main Menu Buttons

Button

Description

Prints the SSL Main Menu values that appear on
the screen.

Refresh

Reloads the SSL Main Menu screen.

Processes the information on the SSL Main Menu screen
and continues to the next step.

Generating a New Certificate Signing Request
NOTE: Each new CSR overwrites any previous CSR data stored in the firmware.
The CSR in the firmware must match the certificate returned from the CA.
Otherwise, iDRAC6 will not accept the certificate.
1 On the SSL Main Menu screen, select Generate a New Certificate
Signing Request (CSR) and click Next.
2 On the Generate Certificate Signing Request (CSR) screen, enter a value
for each CSR attribute.
Table 5-15 describes the Generate Certificate Signing Request (CSR)
screen options.
3 Click Generate to create the CSR.
4 Click Download to save the CSR file to your local computer.
5 Click the appropriate button to continue. See Table 5-16.
Table 5-15.

Generate Certificate Signing Request (CSR) Options

Field

Description

Common Name

The exact name being certified (usually the Web server's
domain name, for example, www.xyzcompany.com).
Only alphanumeric characters, hyphens, underscores,
and periods are valid. Spaces are not valid.

Organization Name

The name associated with this organization (for example,
XYZ Corporation). Only alphanumeric characters,
hyphens, underscores, periods and spaces are valid.

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-15. Generate Certificate Signing Request (CSR) Options (continued)
Field

Description

Organization Unit

The name associated with an organizational unit, such as a
department (for example, Information Technology).
Only alphanumeric characters, hyphens, underscores,
periods, and spaces are valid.

Locality

The city or other location of the entity being certified
(for example, Round Rock). Only alphanumeric characters
and spaces are valid. Do not separate words using an
underscore or other character.

State Name

The state or province where the entity who is applying
for a certification is located (for example, Texas).
Only alphanumeric characters and spaces are valid. Do not
use abbreviations.

Country Code

The name of the country where the entity applying for
certification is located.

The e-mail address associated with the CSR. Enter the
company’s e-mail address, or any e-mail address associated
with the CSR. This field is optional.

Uploading a Server Certificate
Table 5-16. Generate Certificate Signing Request (CSR) Buttons
Button

Description

Prints the Generate Certificate Signing Request values
that appear on the screen.

Refresh

Reloads the Generate Certificate Signing Request screen.

Generate

Generates a CSR and then prompts the user to save it to a
specified directory.

Download

Downloads the certificate to the local computer.

Go Back to SSL Main
Menu

Returns the user to the SSL Main Menu screen.

Configuring iDRAC6 Enterprise Using the Web Interface

1 In the SSL Main Menu screen, select Upload Server Certificate and click
Next.
The Certificate Upload screen appears.
2 In the File Path field, enter the path to the certificate or click Browse to
navigate to the certificate file.
NOTE: The File Path value displays the file path of the certificate you are uploading.
You must enter the file path, which includes the full path and the complete file name
and file extension.
3 Click Apply.
4 Click the appropriate button to continue. See Table 5-17.
Table 5-17.

Certificate Upload Buttons

Button

Description

Prints the values that appear on the Certificate Upload screen

Refresh

Reloads the Certificate Upload screen

Apply

Applies the certificate to iDRAC6 firmware

Go Back to SSL Main Returns the user to the SSL Main Menu screen
Menu

Viewing a Server Certificate
1 On the SSL Main Menu screen, select View Server Certificate and click Next.
Table 5-18 describes the fields and associated descriptions listed in the
Certificate window.
2 Click the appropriate button to continue. See Table 5-19.
Table 5-18.

Certificate Information

Field

Description

Serial Number

Certificate serial number

Subject Information

Certificate attributes entered by the subject

Issuer Information

Certificate attributes returned by the issuer

Valid From

Issue date of the certificate

Valid To

Expiration date of the certificate
Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-19. View Server Certificate Buttons
Button

Description

Prints the View Server Certificate values that appear
on the screen.

Refresh

Reloads the View Server Certificate screen.

Go Back to SSL Main Menu

Return to the SSL Main Menu screen.

Configuring and Managing Active Directory
Certificates
NOTE: You must have Configure iDRAC permission to configure Active Directory
and upload, download, and view an Active Directory certificate.
NOTE: For more information about Active Directory configuration and how to
configure Active Directory with the standard schema or an extended schema,
see "Using iDRAC6 With Microsoft Active Directory."
To access the Active Directory Main Menu:
1 Click System→ Remote Access→ iDRAC, and then click the Network/
Security tab.
2 Click Active Directory to open the Active Directory Main Menu screen.
Table 5-20 lists the Active Directory Main Menu options.
3 Click the appropriate button to continue. See Table 5-20.
Table 5-20. Active Directory Main Menu Options
Field

Description

Configure Active
Directory

Configures the Active Directory ROOT Domain Name,
Active Directory Authentication Timeout, Active Directory
Schema Selection, iDRAC Name, iDRAC Domain Name,
Role Groups, Group Name, and Group Domain settings.

Upload Active
Directory CA
Certificate

Uploads an Active Directory certificate to iDRAC6.

View Active Directory
CA Certificate

Displays an Active Directory Certificate that has been
uploaded to iDRAC6.

100

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-21.

Active Directory Main Menu Buttons

Button

Definition

Prints the Active Directory Main Menu values that appear
on the screen.

Refresh

Reloads the Active Directory Main Menu screen.

Processes the information on the Active Directory Main
Menu screen and continues to the next step.

Configuring Active Directory (Standard Schema and Extended Schema)
1 On the Active Directory Main Menu screen, select Configure Active
Directory and click Next.
2 On the Active Directory Configuration screen, enter the Active
Directory settings.
Table 5-22 describes the Active Directory Configuration and
Management settings.
3 Click Apply to save the settings.
4 Click the appropriate button to continue. See Table 5-23.
5 To configure the Role Groups for Active Directory Standard Schema,
click on the individual Role Group (1-5). See Table 5-24 and Table 5-25.
NOTE: To save the settings on the Active Directory Configuration screen,
click Apply before proceeding to the Custom Role Group screen.
Table 5-22.

Active Directory Configuration Settings

Setting

Description

Enable Active
Directory

When checked, enables Active Directory. The default is
disabled.

ROOT Domain Name The Active Directory ROOT domain name. This default
is blank.
The name must be a valid domain name consisting of x.y,
where x is a 1-254 character ASCII string with no spaces
between characters, and y is a valid domain type such as
com, edu, gov, int, mil, net, or org. The default is blank.

Configuring iDRAC6 Enterprise Using the Web Interface

101

Table 5-22. Active Directory Configuration Settings (continued)
Setting

Description

Timeout

The time, in seconds, to wait for Active Directory queries to
complete. Minimum value is equal to or greater than
15 seconds. The default value is 120.

Use Standard Schema

Uses standard schema with Active Directory.

Use Extended Schema Uses the extended schema with Active Directory.
iDRAC Name

The name that uniquely identifies iDRAC6 in Active
Directory. This default is blank.
The name must be a 1-254 character ASCII string with no
spaces between characters.

iDRAC Domain Name The DNS name of the domain, where the Active Directory
iDRAC6 object resides. This default is blank.
The name must be a valid domain name consisting of x.y,
where x is a 1-254 character ASCII string with no spaces
between characters, and y is a valid domain type such as
com, edu, gov, int, mil, net, or org.
Role Groups

The list of role groups associated with iDRAC6.
To change the settings for a role group, click their role group
number, in the role groups list.

Group Name

The name that identifies the role group in the Active
Directory associated with iDRAC6. This default is blank.

Group Domain

The domain type where the Role Group resides.

Table 5-23. Active Directory Configuration Buttons
Button

Description

Prints the Active Directory Configuration values that
appear on the screen.

Refresh

Reloads the Active Directory Configuration screen.

Apply

Saves any new settings made to the Active Directory
Configuration screen.

Go Back to Active
Returns to the Active Directory Main Menu screen.
Directory Main Menu

102

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-24.

Role Group Privileges

Setting

Description

Role Group Privilege Level

Specifies the user’s maximum iDRAC6 user
privilege as one of the following:
Administrator, Power User, Guest User, None,
or Custom.
See Table 5-25 for Role Group permissions.

Allows the group log in access to iDRAC6.

Configure iDRAC

Allows the group permission to configure
iDRAC6.

Configure Users

Allows the group permission to configure
users.

Clear Logs

Allows the group permission to clear logs.

Execute Server Control Commands Allows the group permission to execute server
control commands.
Access Console Redirection

Allows the group access to Console
Redirection.

Access Virtual Media

Allows the group access to Virtual Media.

Test Alerts

Allows the group to send test alerts (e-mail and
PET) to a specific user.

Execute Diagnostic Commands

Allows the group permission to execute
diagnostic commands.

Table 5-25.

Role Group Permissions

Property

Description

Administrator

Login to iDRAC, Configure iDRAC,
Configure Users, Clear Logs, Execute Server
Control Commands, Access Console
Redirection, Access Virtual Media,
Test Alerts, Execute Diagnostic Commands

Power User

Login to iDRAC, Clear Logs, Execute Server
Control Commands, Access Console
Redirection, Access Virtual Media, Test Alerts

Configuring iDRAC6 Enterprise Using the Web Interface

103

Table 5-25. Role Group Permissions (continued)
Property

Description

Guest User

Custom

Selects any combination of the following
permissions: Login to iDRAC, Configure
iDRAC, Configure Users, Clear Logs, Execute
Server Action Commands, Access Console
Redirection, Access Virtual Media, Test
Alerts, Execute Diagnostic Commands

None

No assigned permissions

Uploading an Active Directory CA Certificate
1 On the Active Directory Main Menu screen, select Upload Active
Directory CA Certificate and click Next.
2 On the Certificate Upload screen, enter the file path of the certificate in
the File Path field, or click Browse to navigate to the certificate file.
NOTE: The File Path value displays the file path of the certificate you are uploading.
You must enter the file path, which includes the full path and the complete file name
and file extension.
Ensure that the domain controller’s SSL certificates have been signed by the
same Certificate Authority and that this Certificate is available on the
management station accessing iDRAC6.
3 Click Apply.
4 Click the appropriate button to continue. See Table 5-26.
Table 5-26. Certificate Upload Buttons
Button

Description

Prints the Certificate Upload values that appear on
the screen

Refresh

Reloads the Certificate Upload screen

Apply

Applies the certificate to iDRAC6 firmware

Go Back to Active
Returns to the Active Directory Main Menu screen
Directory Main Menu

104

Configuring iDRAC6 Enterprise Using the Web Interface

Viewing an Active Directory CA Certificate
Use the Active Directory Main Menu screen to view a CA server certificate
for iDRAC6.
1 On the Active Directory Main Menu screen, select View Active Directory
CA Certificate and click Next.
Table 5-27 describes the fields and associated descriptions listed in the
Certificate window.
2 Click the appropriate button to continue. See Table 5-28.
Table 5-27.

Active Directory CA Certificate Information

Field

Description

Serial Number

Certificate serial number.

Subject Information

Certificate attributes entered by the subject.

Issuer Information

Certificate attributes returned by the issuer.

Valid From

Certificate issue date.

Valid To

Certificate expiration date.

Table 5-28.

View Active Directory CA Certificate Buttons

Button

Description

Prints the Active Directory CA Certificate values that
appear on the screen.

Refresh

Reloads the Active Directory CA Certificate screen.

Go Back to Active
Returns the user to the Active Directory Main Menu
Directory Main Menu screen.

Enabling or Disabling Local Configuration Access
NOTE: The default setting for local configuration access is Enabled.

Enabling Local Configuration Access
1 Click System→ Remote Access→ iDRAC→ Network/Security.
2 Under Local Configuration, click to uncheck Disable iDRAC local USER
Configuration Updates to enable access.
Configuring iDRAC6 Enterprise Using the Web Interface

105

3 Click Apply.
4 Click the appropriate button to continue. See Table 5-34.

Disabling Local Configuration Access
1 Click System→ Remote Access→ iDRAC→ Network/Security.
2 Under Local Configuration, click to check Disable iDRAC local USER
Configuration Updates to disable access.
3 Click Apply.
4 Click the appropriate button to continue. See Table 5-34.

Configuring iDRAC6 Services
NOTE: To modify these settings, you must have Configure iDRAC permission.
NOTE: When you apply changes to services, the changes take effect immediately.
Existing connections may be terminated without warning.
NOTE: There is a known issue with the Telnet client supplied with Microsoft
Windows communicating with a BMU. Use another Telnet client such as
HyperTerminal or PuTTY.
1 Click System→ Remote Access→ iDRAC, and then click the Network/
Security tab.
2 Click Services to open the Services configuration screen.
3 Configure the following services, as required:
•

Web server — see Table 5-29 for Web server settings

•

SSH — see Table 5-30 for SSH settings

•

Telnet — see Table 5-31 for telnet settings

•

SNMP Agent — see Table 5-32 for SNMP Agent settings

•

Automated System Recovery Agent — see Table 5-33 for Automated
System Recovery Agent settings

4 Click Apply.
5 Click the appropriate button to continue. See Table 5-34.

106

Configuring iDRAC6 Enterprise Using the Web Interface

Table 5-29.

Web Server Settings

Setting

Description

Enabled

Enables or disables the iDRAC6 Web server.
When checked, indicates that the Web server is enabled.
The default value is enabled.

Max Sessions

The maximum number of simultaneous sessions allowed
for this system. This field is not editable. There can be four
simultaneous sessions.

Current Sessions

The number of current sessions on the system, less than or
equal to the Max Sessions. This field is not editable.

Timeout

The time, in seconds, that a connection is allowed to
remain idle. The session is cancelled when the timeout is
reached. Changes to the timeout setting take affect
immediately and will reset the Web server. Timeout range is
60 to 10800 seconds. The default is 1800 seconds.

HTTP Port Number

The port on which iDRAC6 listens for a browser
connection. The default is 80.

HTTPS Port Number

The port on which iDRAC6 listens for a secure browser
connection. The default is 443.

Table 5-30.

SSH Settings

Setting

Description

Enabled

Enables or disables SSH. When checked, the checkbox
indicates that SSH is enabled.

Max Sessions

The maximum number of simultaneous sessions allowed
for this system. Only one session is supported.

Active Sessions

The number of current sessions on the system.

Timeout

The secure shell idle timeout, in seconds. Timeout range is
60 to 10800 seconds. Enter 0 seconds to disable the
Timeout feature. The default is 1800.

Port Number

The port on which iDRAC6 listens for an SSH connection.
The default is 22.

Configuring iDRAC6 Enterprise Using the Web Interface

107

Table 5-31. Telnet Settings
Setting

Description

Enabled

Enables or disables telnet. When checked, telnet is
enabled. The default value is disabled.

Max Sessions

The maximum number of simultaneous sessions allowed
for this system. Only one session is supported.

Active Sessions

The number of current sessions on the system.

Timeout

The telnet idle timeout, in seconds. Timeout range is 60 to
10800 seconds. Enter 0 seconds to disable the Timeout
feature. The default is 1800.

Port Number

The port on which iDRAC6 listens for a telnet connection.
The default is 23.

Table 5-32. SNMP Agent
Setting

Description

Enabled

Enables or disables email alerts.

SNMP Community
Name

The name of the community that contains the IP address
for the SNMP Alert destination. The Community Name
may be up to 31 non-blank characters in length.
Default=public.

Table 5-33. Automated System Recovery Agent Setting
Setting

Description

Enabled

Enables the Automated System Recovery Agent.

Table 5-34. Services Buttons
Button

Description

Prints the Services screen.

Refresh

Refreshes the Services screen.

Apply Changes

Applies the Services screen settings.

108

Configuring iDRAC6 Enterprise Using the Web Interface

Updating iDRAC6 Firmware
NOTE: If iDRAC6 firmware becomes corrupted, as could occur if the iDRAC6
firmware update progress is interrupted before it completes, you can recover
iDRAC6 using the CMC. See your CMC Firmware User Guide for instructions.
NOTE: The firmware update, by default, retains the current iDRAC6 settings.
During the update process, you have the option to reset iDRAC6 configuration to the
factory defaults. If you set the configuration to the factory defaults external network
access will be disabled when the update completes. You must enable and configure
the network using the iDRAC6 Configuration Utility or the CMC Web interface.
1 Start the iDRAC6 Web interface.
2 Click System→ Remote Access→ iDRAC, then click the Update tab.
NOTE: To update the firmware, iDRAC6 must be placed in an update mode.
Once in this mode, iDRAC6 will automatically reset, even if you cancel the
update process.

3 On the Firmware Update screen, click Next to start the update process.
4 In the Firmware Update - Upload (page 1 of 4) window, click Browse,
or enter the path to the firmware image that you downloaded.
For example:
C:\Updates\V2.0\.
The default firmware image name is firmimg.imc.
5 Click Next.
•

The file will be uploaded to iDRAC6. This may take several minutes
to complete.
OR

•

You can click Cancel at this time, if you would like to end the
firmware upgrade process. Clicking Cancel will reset iDRAC6 to
normal operating mode.

Configuring iDRAC6 Enterprise Using the Web Interface

109

6 In the Firmware Update - Validation (page 2 of 4) window, you will see
the results of the validation performed on the image file you uploaded.
•

If the image file uploaded successfully and passed all verification
checks, a message will appear indicating that the firmware image has
been verified.
OR

•

If the image did not upload successfully, or it did not pass the
verification checks, the firmware update will return to the Firmware
Update - Upload (page 1 of 4) window. You can attempt to upgrade
iDRAC6 again or click Cancel to reset iDRAC6 to normal operating
mode.

NOTE: If you deselect the Preserve Configuration checkbox, iDRAC6 will be reset
to its default settings. In the default settings, the LAN is disabled. You will not be
able to log in to the iDRAC6 Web interface. You will have to reconfigure the LAN
settings using the CMC Web interface or iKVM using the iDRAC6 Configuration
Utility during BIOS POST.
7 By default the Preserve Configuration checkbox is checked, to preserve
the current settings on iDRAC6 after an upgrade. If you do not want the
settings to be preserved, deselect the Preserve Configuration checkbox.
8 Click Begin Update to start the upgrade process. Do not interrupt the
upgrade process.
9 In the Firmware Update - Updating (page 3 of 4) window, you will see the
status of the upgrade. The progress of the firmware upgrade operation,
measured in percentages, will appear in the Progress column.
10 Once the firmware update is complete, the Firmware Update - Update
Results (page 4 of 4) window will appear and iDRAC6 will reset
automatically. You must close the current browser window and reconnect
to iDRAC6 using a new browser window.

110

Configuring iDRAC6 Enterprise Using the Web Interface

Updating iDRAC6 Firmware Using the CMC
Typically, iDRAC6 firmware is updated using iDRAC6 utilities, such as the
iDRAC6 Web interface or operating system specific update packages
downloaded from support.dell.com.
You can use the CMC Web interface or CMC RACADM to update the
iDRAC6 firmware. This feature is available both when iDRAC6 firmware is in
Normal mode, as well as when it is corrupted. See "Updating iDRAC6
Firmware Using the CMC."]
NOTE: See the Chassis Management Controller Firmware User Guide for
instructions for using the CMC Web interface.
To update iDRAC6 firmware, perform the following steps:
1 Download the latest iDRAC6 firmware to your management computer
from support.dell.com.
2 Log in to the CMC Web-based interface.
3 Click Chassis in the system tree.
4 Click the Update tab. The Updatable Components screen appears.
5 Click server-n, where n is the number of the server whose iDRAC6 you
want to update.
6 Click Browse, navigate to the iDRAC6 firmware image you downloaded,
and then click Open.
7 Click Begin Firmware Update.
After the firmware image file has been uploaded to the CMC, iDRAC6 will
update itself with the image.

Configuring iDRAC6 Enterprise Using the Web Interface

111

112

Configuring iDRAC6 Enterprise Using the Web Interface

Using iDRAC6 With Microsoft
Active Directory
A directory service maintains a common database of all information needed for
controlling users, computers, printers, etc. on a network. If your company already
uses the Microsoft® Active Directory® service software, you can configure the
software to provide access to iDRAC6, allowing you to add and control iDRAC6
user privileges to your existing users in your Active Directory software.
NOTE: Using Active Directory to recognize iDRAC6 users is supported on the
Microsoft Windows 2000, Windows Server 2003, and Windows Server 2008
operating systems.
Table 6-1 shows the nine iDRAC6 Active Directory user privileges.
Table 6-1.

iDRAC6 User Privileges

Privilege

Description

Enables the user to log in to iDRAC6

Configure iDRAC

Enables the user to configure iDRAC6

Configure Users

Enables the user to allow specific users to access
the system

Clear Logs

Enables the user to clear the iDRAC6 logs

Execute Server Control
Commands

Enables the user to execute RACADM commands

Access Console Redirection

Enables the user to run Console Redirection

Access Virtual Media

Enables the user to run and use Virtual Media

Test Alerts

Enables the user to send test alerts (e-mail and PET)
to a specific user

Execute Diagnostic Commands Enables the user to run diagnostic commands

Using iDRAC6 With Microsoft Active Directory

113

Prerequisites for Enabling Active Directory
Authentication for iDRAC6
To use the Active Directory authentication feature of iDRAC6, you must
have already deployed an Active Directory infrastructure. See the Microsoft
website for information on how to set up an Active Directory infrastructure,
if you don't already have one.
iDRAC6 uses the standard Public Key Infrastructure (PKI) mechanism to
authenticate securely into the Active Directory; therefore, you would also
require an integrated PKI into the Active Directory infrastructure.
See the Microsoft website for more information on the PKI setup.
To correctly authenticate to all the domain controllers, you also need to enable
the Secure Socket Layer (SSL) on all domain controllers that iDRAC6 connects
to. See "Enabling SSL on a Domain Controller" for more specific information.

Supported Active Directory Authentication
Mechanisms
You can use Active Directory to define user access on iDRAC6 through two
methods: you can use the extended schema solution, which Dell has
customized to add Dell-defined Active Directory objects. Or, you can use the
standard schema solution, which uses Active Directory group objects only.
See the sections that follow for more information about these solutions.
When using Active Directory to configure access to iDRAC6, you must
choose either the extended schema or the standard schema solution.
The advantages of using the extended schema solution are:
•

All of the access control objects are maintained in Active Directory.

•

Maximum flexibility is provided in configuring user access on different
iDRAC6 cards with varying privilege levels.

The advantage of using the standard schema solution is that no schema
extension is required because all of the necessary object classes are provided
by Microsoft’s default configuration of the Active Directory schema.

114

Using iDRAC6 With Microsoft Active Directory

Extended Schema Active Directory Overview
Using the extended schema solution requires the Active Directory schema
extension, as described in the following section.

Extending the Active Directory Schema
Important: The schema extension for this product is different from the previous
generations of Dell Remote Management products. You must extend the new
schema and install the new Active Directory Users and Computers Microsoft
Management Console (MMC) Snap-in on your directory. The old schema
does not work with this product.
NOTE: Extending the new schema or installing the new extension to Active Directory
User and Computer Snap-in has no impact on previous versions of the product.
The schema extender and Active Directory Users and Computers MMC
Snap-in extension are available on the Dell Systems Management Tools and
Documentation DVD. For more information, see "Extending the Active
Directory Schema" and "Installing the Dell Extension to the Active Directory
Users and Computers Snap-In." For further details on extending the schema
for iDRAC6 and installing the Active Directory Users and Computers MMC
Snap-in, see the Dell OpenManage Installation and Security User’s Guide
available on support.dell.com\manuals.
NOTE: When you create iDRAC6 Association Objects or iDRAC6 Device Objects,
be certain to select Dell Remote Management Object Advanced.

Active Directory Schema Extensions
The Active Directory data is a distributed database of Attributes and Classes.
The Active Directory schema includes the rules that determine the type of
data that can be added or included in the database. The user class is one
example of a Class that is stored in the database. Some example user class
attributes can include the user’s first name, last name, phone number, and so
on. Companies can extend the Active Directory database by adding their own
unique Attributes and Classes to solve environment-specific needs. Dell has
extended the schema to include the necessary changes to support remote
management Authentication and Authorization.
Each Attribute or Class that is added to an existing Active Directory Schema
must be defined with a unique ID. To maintain unique IDs across the
industry, Microsoft maintains a database of Active Directory Object
Using iDRAC6 With Microsoft Active Directory

115

Identifiers (OIDs) so that when companies add extensions to the schema,
they can be guaranteed to be unique and not to conflict with each other.
To extend the schema in Microsoft's Active Directory, Dell received unique
OIDs, unique name extensions, and uniquely linked attribute IDs for our
attributes and classes that are added into the directory service.
•

Dell extension is: dell

•

Dell base OID is: 1.2.840.113556.1.8000.1280

•

RAC LinkID range is: 12070 to 12079

Overview of the iDRAC6 Schema Extensions
To provide the greatest flexibility in the multitude of customer environments,
Dell provides a group of properties that can be configured by the user
depending on the desired results. Dell has extended the schema to include an
Association, Device, and Privilege property. The Association property is used
to link together the users or groups with a specific set of privileges to one or
more iDRAC6 devices. This model provides an Administrator maximum
flexibility over the different combinations of users, iDRAC6 privileges, and
iDRAC6 devices on the network without adding too much complexity.

Active Directory Object Overview
For each physical iDRAC6 device on the network that you want to integrate
with Active Directory for Authentication and Authorization, create at least
one Association Object and one iDRAC6 Device Object. You can create
multiple Association Objects, and each Association Object can be linked to as
many users, groups of users, or iDRAC6 Device Objects as required. The users
and iDRAC6 user groups can be members of any domain in the enterprise.
However, each Association Object can be linked (or, may link users, groups
of users, or iDRAC6 Device Objects) to only one Privilege Object.
This example allows an Administrator to control each user’s privileges on
specific iDRAC6 devices.
The iDRAC6 Device object is the link to the iDRAC6 firmware for querying
Active Directory for authentication and authorization. When iDRAC6 is added
to the network, the Administrator must configure iDRAC6 and its device
object with its Active Directory name so users can perform authentication and
authorization with Active Directory. Additionally, the Administrator must add
iDRAC6 to at least one Association Object in order for users to authenticate.
116

Using iDRAC6 With Microsoft Active Directory

Figure 6-1 illustrates that the Association Object provides the connection
that is needed for all of the Authentication and Authorization.
Figure 6-1. Typical Setup for Active Directory Objects

iDRAC
Association Object

User(s)
Group(s)

Privilege Object

iDRAC
Device Object(s)

You can create as many or as few association objects as required. However,
you must create at least one Association Object, and you must have one
iDRAC6 Device Object for each iDRAC6 device on the network that you
want to integrate with Active Directory for Authentication and Authorization
with iDRAC6.
The Association Object allows for as many or as few users and/or groups as
well as iDRAC6 Device Objects. However, the Association Object only
includes one Privilege Object per Association Object. The Association Object
connects the Users who have Privileges on the iDRAC6 devices.
The Dell extension to the ADUC MMC Snap-in only allows associating the
Privilege Object and iDRAC6 Objects from the same domain with the
Association Object. The Dell extension does not allow a group or an iDRAC6
object from other domains to be added as a product member of the
Association Object.
Users, user groups, or nested user groups from any domain can be added into
the Association Object. Extended Schema solutions support any user group
type and any user group nesting across multiple domains allowed by
Microsoft Active Directory.

Using iDRAC6 With Microsoft Active Directory

117

Accumulating Privileges Using Extended Schema
The Extended Schema Authentication mechanism supports Privilege
Accumulation from different privilege objects associated with the same user
through different Association Objects. In other words, Extended Schema
Authentication accumulates privileges to allow the user the super set of all
assigned privileges corresponding to the different privilege objects associated
with the same user.
Figure 6-2 provides an example of accumulating privileges using Extended
Schema.
Figure 6-2. Privilege Accumulation for a User
Domain 1

Domain 2
A01

Group1

User1

User2

A02

Priv1

Priv2

iDRAC1

iDRAC2

The figure shows two Association Objects—A01 and A02. User1 is associated
to iDRAC2 through both association objects. Therefore, User1 has
accumulated privileges that are the result of combining the privileges set for
objects Priv1 and Priv2 on iDRAC2.
For example, Priv1 has these privileges: Login, Virtual Media, and Clear Logs
and Priv2 has these privileges: Login to iDRAC, Configure iDRAC, and Test
Alerts. As a result, User1 now has the privilege set: Login to iDRAC,
Virtual Media, Clear Logs, Configure iDRAC, and Test Alerts, which is the
combined privilege set of Priv1 and Priv2.
118

Using iDRAC6 With Microsoft Active Directory

Extended Schema Authentication accumulates privileges to allow the user
the maximum set of privileges possible considering the assigned privileges of
the different privilege objects associated to the same user.
In this configuration, User1 has both Priv1 and Priv2 privileges on iDRAC2.
User1 has Priv1 privileges on iDRAC1 only. User2 has Priv1 privileges on both
iDRAC1 and iDRAC2. In addition, this figure shows that User1 can be in a
different domain and can be a member of a group.

Configuring Extended Schema Active Directory to Access iDRAC6
Before using Active Directory to access iDRAC6, configure the Active
Directory software and iDRAC6 by performing the following steps in order:
1 Extend the Active Directory schema (see "Extending the Active Directory
Schema").
2 Extend the Active Directory Users and Computers Snap-in (see "Installing
the Dell Extension to the Active Directory Users and Computers Snap-In").
3 Add iDRAC6 users and their privileges to Active Directory (see "Adding
iDRAC6 Users and Privileges to Active Directory").
4 Enable SSL on each of your domain controllers (see "Enabling SSL on a
Domain Controller").
5 Configure iDRAC6 Active Directory properties using either the iDRAC6
Web-based interface or the RACADM (see "Configuring Active Directory
With Extended Schema Using the iDRAC6 Web-Based Interface" or
"Configuring Active Directory With Extended Schema Using RACADM").
Extending your Active Directory schema adds a Dell organizational unit,
schema classes and attributes, and example privileges and association objects
to the Active Directory schema. Before you extend the schema, ensure that
you have Schema Admin privileges on the Schema Master Flexible Single
Master Operation (FSMO) Role Owner of the domain forest.
You can extend your schema using one of the following methods:
•

Dell Schema Extender utility

•

LDIF script file

If you use the LDIF script file, the Dell organizational unit will not be added
to the schema.

Using iDRAC6 With Microsoft Active Directory

119

The LDIF files and Dell Schema Extender are located on your Dell Systems
Management Tools and Documentation DVD in the following respective
directories:
•

DVD drive:\SYSMGMT\ManagementStation\support\OMActiveDirectory_
Tools\Remote_Management_Advanced\LDIF_Files

•

:\SYSMGMT\ManagementStation\support\OMActiveDirecto
ry_Tools\Remote_Management_Advanced\Schema Extender

To use the LDIF files, see the instructions in the readme included in the
LDIF_Files directory. To use the Dell Schema Extender to extend the Active
Directory Schema, see "Using the Dell Schema Extender."
You can copy and run the Schema Extender or LDIF files from any location.
Using the Dell Schema Extender

CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file.
To ensure that the Dell Schema Extender utility functions properly, do not modify
the name of this file.
1 In the Welcome screen, click Next.
2 Read and understand the warning and click Next.
3 Select Use Current Log In Credentials or enter a user name and password
with schema administrator rights.
4 Click Next to run the Dell Schema Extender.
5 Click Finish.
The schema is extended. To verify the schema extension, use the MMC
and the Active Directory Schema Snap-in to verify that the following exist:
•

Classes (see Table 6-2 through Table 6-7)

•

Attributes (Table 6-8)

See your Microsoft documentation for details about using the MMC and
the Active Directory Schema Snap-in.

120

Using iDRAC6 With Microsoft Active Directory

Table 6-2.

Class Definitions for Classes Added to the Active Directory Schema

Class Name

Assigned Object Identification Number (OID)

delliDRACDevice

1.2.840.113556.1.8000.1280.1.7.1.1

delliDRACAssociation 1.2.840.113556.1.8000.1280.1.7.1.2
dellRAC4Privileges

1.2.840.113556.1.8000.1280.1.1.1.3

dellPrivileges

1.2.840.113556.1.8000.1280.1.1.1.4

dellProduct

1.2.840.113556.1.8000.1280.1.1.1.5

Table 6-3.

dellRacDevice Class

OID

1.2.840.113556.1.8000.1280.1.7.1.1

Description

Represents the Dell iDRAC6 device. iDRAC6 must be
configured as delliDRACDevice in Active Directory.
This configuration enables iDRAC6 to send Lightweight
Directory Access Protocol (LDAP) queries to Active Directory.

Class Type

Structural Class

SuperClasses

dellProduct

Attributes

dellSchemaVersion
dellRacType

Table 6-4.

delliDRACAssociationObject Class

OID

1.2.840.113556.1.8000.1280.1.7.1.2

Description

Represents the Dell Association Object. The Association Object
provides the connection between the users and the devices.

Class Type

Structural Class

SuperClasses

Group

Attributes

dellProductMembers
dellPrivilegeMember

Using iDRAC6 With Microsoft Active Directory

121

Table 6-5.

dellRAC4Privileges Class

OID

1.2.840.113556.1.8000.1280.1.1.1.3

Description

Defines the privileges (Authorization Rights) for iDRAC6

Class Type

Auxiliary Class

SuperClasses

None

Attributes

dellIsLoginUser
dellIsCardConfigAdmin
dellIsUserConfigAdmin
dellIsLogClearAdmin
dellIsServerResetUser
dellIsConsoleRedirectUser
dellIsVirtualMediaUser
dellIsTestAlertUser
dellIsDebugCommandAdmin

Table 6-6.

dellPrivileges Class

OID

1.2.840.113556.1.8000.1280.1.1.1.4

Description

Used as a container Class for the Dell Privileges (Authorization Rights).

Class Type

Structural Class

SuperClasses

User

Attributes

dellRAC4Privileges

Table 6-7.

dellProduct Class

OID

1.2.840.113556.1.8000.1280.1.1.1.5

Description

The main class from which all Dell products are derived.

Class Type

Structural Class

SuperClasses

Computer

Attributes

dellAssociationMembers

122

Using iDRAC6 With Microsoft Active Directory

Table 6-8.

List of Attributes Added to the Active Directory Schema

Attribute Name/Description

Assigned OID/Syntax Object Identifier

Single
Valued

dellPrivilegeMember

1.2.840.113556.1.8000.1280.1.1.2.1

FALSE

List of dellPrivilege Objects that
belong to this Attribute.

Distinguished Name (LDAPTYPE_DN
1.3.6.1.4.1.1466.115.121.1.12)

dellProductMembers

1.2.840.113556.1.8000.1280.1.1.2.2

List of dellRacDevice and
DelliDRACDevice Objects that
belong to this role. This attribute
is the forward link to the
dellAssociationMembers
backward link.

Distinguished Name (LDAPTYPE_DN
1.3.6.1.4.1.1466.115.121.1.12)

FALSE

Link ID: 12070
dellIsLoginUser

1.2.840.113556.1.8000.1280.1.1.2.3

TRUE

TRUE if the user has Login rights Boolean (LDAPTYPE_BOOLEAN
on the device.
1.3.6.1.4.1.1466.115.121.1.7)
dellIsCardConfigAdmin

1.2.840.113556.1.8000.1280.1.1.2.4

TRUE if the user has Card
Configuration rights on
the device.

Boolean (LDAPTYPE_BOOLEAN
1.3.6.1.4.1.1466.115.121.1.7)

dellIsUserConfigAdmin

1.2.840.113556.1.8000.1280.1.1.2.5

TRUE if the user has User
Configuration rights on the
device.

Boolean (LDAPTYPE_BOOLEAN
1.3.6.1.4.1.1466.115.121.1.7)

delIsLogClearAdmin

1.2.840.113556.1.8000.1280.1.1.2.6

TRUE

TRUE if the user has Log Clearing Boolean (LDAPTYPE_BOOLEAN
rights on the device.
1.3.6.1.4.1.1466.115.121.1.7)
dellIsServerResetUser

1.2.840.113556.1.8000.1280.1.1.2.7

TRUE

TRUE if the user has Server Reset Boolean (LDAPTYPE_BOOLEAN
rights on the device.
1.3.6.1.4.1.1466.115.121.1.7)
dellIsConsoleRedirectUser

1.2.840.113556.1.8000.1280.1.1.2.8

TRUE if the user has Console
Redirection rights on the device.

Boolean (LDAPTYPE_BOOLEAN
1.3.6.1.4.1.1466.115.121.1.7)

Using iDRAC6 With Microsoft Active Directory

TRUE

123

Table 6-8.

List of Attributes Added to the Active Directory Schema (continued)

Attribute Name/Description

Assigned OID/Syntax Object Identifier

Single
Valued

dellIsVirtualMediaUser

1.2.840.113556.1.8000.1280.1.1.2.9

TRUE

TRUE if the user has Virtual
Media rights on the device.

Boolean (LDAPTYPE_BOOLEAN
1.3.6.1.4.1.1466.115.121.1.7)

dellIsTestAlertUser

1.2.840.113556.1.8000.1280.1.1.2.10

TRUE if the user has Test Alert
User rights on the device.

Boolean (LDAPTYPE_BOOLEAN
1.3.6.1.4.1.1466.115.121.1.7)

dellIsDebugCommandAdmin

1.2.840.113556.1.8000.1280.1.1.2.11

TRUE if the user has Debug
Command Admin rights on
the vdevice.

Boolean (LDAPTYPE_BOOLEAN
1.3.6.1.4.1.1466.115.121.1.7)

dellSchemaVersion

1.2.840.113556.1.8000.1280.1.1.2.12

The Current Schema Version is
used to update the schema.

Case Ignore String
(LDAPTYPE_CASEIGNORESTRING
1.2.840.113556.1.4.905)

dellRacType

1.2.840.113556.1.8000.1280.1.1.2.13

TRUE

This attribute is the Current RAC Case Ignore String
(LDAPTYPE_CASEIGNORESTRING
Type for the delliDRACDevice
1.2.840.113556.1.4.905)
object and the backward link to
the dellAssociationObjectMembers
forward link.

dellAssociationMembers

1.2.840.113556.1.8000.1280.1.1.2.14

List of

Distinguished Name (LDAPTYPE_DN

dellAssociationObjectMembers that 1.3.6.1.4.1.1466.115.121.1.12)
belong to this Product. This

attribute is the backward link to
the dellProductMembers linked
attribute.
Link ID: 12071

124

Using iDRAC6 With Microsoft Active Directory

FALSE

Installing the Dell Extension to the Active Directory Users and
Computers Snap-In
When you extend the schema in Active Directory, you must also extend the
Active Directory Users and Computers Snap-in so the administrator can
manage iDRAC6 devices, Users and User Groups, iDRAC6 Associations,
and iDRAC6 Privileges.
When you install your systems management software using the Dell Systems
Management Tools and Documentation DVD, you can extend the Snap-in by
selecting the Active Directory Users and Computers Snap-in option during
the installation procedure. See the Dell OpenManage Software Quick
Installation Guide for additional instructions about installing systems
management software. For 64-bit Windows Operating Systems, the Snap-in
installer is located under:
:\SYSMGMT\ManagementStation\support\OMActiveDirect
ory_SnapIn64
For more information about the Active Directory Users and Computers
Snap-in, see your Microsoft documentation.
Installing the Administrator Pack

You must install the Administrator Pack on each system that is managing the
Active Directory iDRAC6 Objects. If you do not install the Administrator
Pack, you cannot view the Dell iDRAC6 Object in the container.
See "Opening the Active Directory Users and Computers Snap-In" for more
information.
Opening the Active Directory Users and Computers Snap-In

To open the Active Directory Users and Computers Snap-in:
1 If you are logged in to the domain controller, click Start Admin Tools→
Active Directory Users and Computers.
If you are not logged in to the domain controller, you must have the
appropriate Microsoft Administrator Pack installed on your local system. To
install this Administrator Pack, click Start→ Run, enter MMC, and press Enter.
The MMC appears.
2 In the Console 1 window, click File (or Console on systems running
Windows 2000).
Using iDRAC6 With Microsoft Active Directory

125

3 Click Add/Remove Snap-in.
4 Select the Active Directory Users and Computers Snap-in and click Add.
5 Click Close and click OK.

Adding iDRAC6 Users and Privileges to Active Directory
Using the Dell-extended Active Directory Users and Computers Snap-in, you
can add iDRAC6 users and privileges by creating iDRAC6, Association, and
Privilege objects. To add each object type, perform the following procedures:
•

Create an iDRAC6 device Object

•

Create a Privilege Object

•

Create an Association Object

•

Add objects to an Association Object

Creating an iDRAC6 Device Object

1 In the MMC Console Root window, right-click a container.
2 Select New→ Dell Remote Management Object Advanced.
The New Object window appears.
3 Enter a name for the new object. The name must be identical to the
iDRAC6 name that you will enter in Step A of "Configuring Active
Directory With Extended Schema Using the iDRAC6 Web-Based
Interface."
4 Select iDRAC Device Object.
5 Click OK.
Creating a Privilege Object

NOTE: A Privilege Object must be created in the same domain as the related
Association Object.
1 In the Console Root (MMC) window, right-click a container.
2 Select New→ Dell Remote Management Object Advanced.
The New Object window appears.
3 Enter a name for the new object.
4 Select Privilege Object.
126

Using iDRAC6 With Microsoft Active Directory

5 Click OK.
6 Right-click the privilege object that you created, and select Properties.
7 Click the Remote Management Privileges tab and select the privileges
that you want the user or group to have (see Table 5-10).
Creating an Association Object

NOTE: The iDRAC6 Association Object is derived from Group and its scope is set to
Domain Local.
1 In the Console Root (MMC) window, right-click a container.
2 Select New→ Dell Remote Management Object Advanced.
This opens the New Object window.
3 Enter a name for the new object.
4 Select Association Object.
5 Select the scope for the Association Object.
6 Click OK.
Adding Objects to an Association Object

Using the Association Object Properties window, you can associate users or
user groups, privilege objects, and iDRAC6 devices or iDRAC6 device groups.
You can add groups of Users and iDRAC6 devices. The procedure for creating
Dell-related groups and non-Dell-related groups is identical.
Adding Users or User Groups

1 Right-click the Association Object and select Properties.
2 Select the Users tab and click Add.
3 Enter the user or User Group name and click OK.
Adding Privileges

1 Select the Privileges Object tab and click Add.
2 Enter the Privilege Object name and click OK.
Click the Privilege Object tab to add the privilege object to the association that
defines the user’s or user group’s privileges when authenticating to an iDRAC6
device. Only one privilege object can be added to an Association Object.
Using iDRAC6 With Microsoft Active Directory

127

Adding iDRAC6 Devices or iDRAC6 Device Groups

To add iDRAC6 devices or iDRAC6 device groups:
1 Select the Products tab and click Add.
2 Enter iDRAC6 devices or iDRAC6 device group name and click OK.
3 In the Properties window, click Apply and click OK.
Click the Products tab to add one iDRAC6 device connected to the network
that is available for the defined users or user groups. You can add multiple
iDRAC6 devices to an Association Object.

Configuring Active Directory With Extended Schema Using the iDRAC6
Web-Based Interface
1 Open a supported Web browser window.
2 Log in to the iDRAC6 Web-based interface.
3 In the system tree, select System→ Remote Access→ iDRAC.
The iDRAC Information screen appears.
4 Click the Network Security tab, and then click Active Directory.
The Active Directory Configuration and Management screen appears.
5 Scroll to the bottom of the screen and click Configure Active Directory.
The Step 1 of 4 Active Directory Configuration and Management screen
appears.
6 To validate the SSL certificate of your Active Directory servers, select the
Enable Certificate Validation check box under Certificate Settings.
If you don’t want to validate the SSL certificate of your Active Directory
servers, take no action, and skip to step 8.
7 Under Upload Active Directory CA Certificate, enter the file path of the
certificate or browse to find the certificate file, and then click Upload.
NOTE: You must enter the absolute file path, which includes the full path and
the complete file name and file extension.

The certificate information for the Active Directory CA certificate that you
uploaded appears in the Current Active Directory CA Certificate section.

128

Using iDRAC6 With Microsoft Active Directory

8 Click Next.
The Step 2 of 4 Active Directory Configuration and Management
screen appears.
9 Select the Enable Active Directory check box.
10 Click Add to enter the user domain name, enter the user domain name in
the text field, and then click OK.
11 Type the user domain name in the prompt and click OK. Note that this
step is optional. If you configure a list of user domains, the list will be
available in the Web-based interface login screen. You can choose from
the list, and then you only need to enter the user name.
12 In the Timeout field, enter the number of seconds you want iDRAC6 to
wait for Active Directory responses. The default is 120 seconds.
13 Enter the Domain Controller Server Address. You can enter up to three
Active Directory servers for login processing, but you must configure at
least one server by entering the IP address or the fully qualified domain
name (FQDN). iDRAC6 attempts to connect to each configured server
until a connection is established.
NOTE: The FQDN or IP address that you specify in this field should match the
Subject or Subject Alternative Name field of your domain controller
certificate if you have certificate validation enabled.

14 Click Next.
The Step 3 of 4 Active Directory Configuration and Management
screen appears.
15 Under Schema Selection, select the Extended Schema check box.
16 Click Next.
The Step 4 of 4 Active Directory Configuration and Management
screen appears.
17 Under Extended Schema Settings, enter the iDRAC6 name and iDRAC6
domain name to configure the iDRAC6 device object and its location in
Active Directory.
18 Click Finish to save your changes, and then Done.
The main Active Directory Configuration and Management appears.
Next, you must test the Active Directory settings you just configured.

Using iDRAC6 With Microsoft Active Directory

129

19 Scroll to the bottom of the screen and click Test Settings.
The Test Active Directory Settings screen appears.
20 Enter your iDRAC6 user name and password, and then click Start Test.
Test results and the test log display. For additional information, see
"Testing Your Configurations."
NOTE: You must have a DNS server configured properly on iDRAC6 to support
Active Directory log in. Navigate to the Network Configuration screen (click
System→ Remote Access→ iDRAC, and then click the Network/Security tab) to
configure DNS server(s) manually or use DHCP to get DNS server(s).
You have completed the Active Directory configuration with Extended Schema.

Configuring Active Directory With Extended Schema Using RACADM
Use the following commands to configure the iDRAC6 Active Directory
feature with Extended Schema using the RACADM command line interface
(CLI) tool instead of the Web-based interface.
1 Open a command prompt and enter the following RACADM commands:
racadm config -g cfgActiveDirectory -o cfgADEnable 1
racadm config -g cfgActiveDirectory -o cfgADType 1
racadm config -g cfgActiveDirectory -o
cfgADRacName
racadm config -g cfgActiveDirectory -o
cfgADRacDomain
racadm config -g cfgActiveDirectory -o
cfgDomainController1
racadm config -g cfgActiveDirectory -o
cfgDomainController2
racadm config -g cfgActiveDirectory -o
cfgDomainController3

130

Using iDRAC6 With Microsoft Active Directory

NOTE: You must configure at least one of the three addresses. iDRAC6
attempts to connect to each of the configured addresses one-by-one until a
successful connection is made. With Extended Schema, these are the FQDN
or IP addresses of the domain controllers where this iDRAC6 device is
located. Global catalog servers are not used in extended schema mode at all.

If you want to disable the certificate validation during SSL handshake,
enter the following RACADM command:
racadm config -g cfgActiveDirectory -o
cfgADCertValidationEnable 0
In this case, you do not have to upload a CA certificate.
If you want to enforce the certificate validation during SSL handshake,
enter the following RACADM command:
racadm config -g cfgActiveDirectory -o
cfgADCertValidationEnable 1
In this case, you must upload a CA certificate using the following
RACADM command:
racadm sslcertupload -t 0x2 -f
Using the following RACADM command may be optional. See "Importing
the iDRAC6 Firmware SSL Certificate" for additional information.
racadm sslcertdownload -t 0x1 -f
2 If DHCP is enabled on iDRAC6 and you want to use the DNS provided by
the DHCP server, enter the following RACADM command:
racadm config -g cfgLanNetworking -o
cfgDNSServersFromDHCP 1
3 If DHCP is disabled in iDRAC6 or you want to manually input your DNS
IP address, enter the following RACADM commands:
racadm config -g cfgLanNetworking -o
cfgDNSServersFromDHCP 0
racadm config -g cfgLanNetworking -o cfgDNSServer1

racadm config -g cfgLanNetworking -o cfgDNSServer2

Using iDRAC6 With Microsoft Active Directory

131

4 If you want to configure a list of user domains so that you only need to
enter the user name during log in to the iDRAC6 Web-based interface,
enter the following command:
racadm config -g cfgUserDomain -o
cfgUserDomainName -i
You can configure up to 40 user domains with index numbers between
1 and 40.
See "Using Active Directory to Log In to iDRAC6" for details about user
domains.
5 Press Enter to complete the Active Directory configuration with
Extended Schema.

Standard Schema Active Directory Overview
As shown in Figure 6-3, using standard schema for Active Directory
integration requires configuration on both Active Directory and iDRAC6.
Figure 6-3. Configuration of iDRAC6 with Microsoft Active Directory and
Standard Schema
Configuration on Active
Directory Side

Role
Group

Configuration on
iDRAC Side

Role
Group Name
and Domain
Name

User

132

Using iDRAC6 With Microsoft Active Directory

Role
Definition

On the Active Directory side, a standard group object is used as a role group.
A user who has iDRAC6 access will be a member of the role group. To give
this user access to a specific iDRAC6 card, the role group name and its
domain name need to be configured on the specific iDRAC6 card. Unlike the
extended schema solution, the role and the privilege level is defined on each
iDRAC6 card, not in the Active Directory. Up to five role groups can be
configured and defined in each iDRAC6. Table 6-9 shows the default role
group privileges.
Table 6-9.

Default Role Group Privileges

Role
Groups

Default Privilege Permissions Granted
Level

Bit Mask

Role
Group 1

Administrator

Login to iDRAC, Configure iDRAC,
Configure Users, Clear Logs,
Execute Server Control Commands,
Access Console Redirection,
Access Virtual Media, Test Alerts,
Execute Diagnostic Commands

0x000001ff

Role
Group 2

Operator

Login to iDRAC, Configure iDRAC,
Execute Server Control Commands,
Access Console Redirection,
Access Virtual Media, Test Alerts,
Execute Diagnostic Commands

0x000000f9

Role
Group 3

Read Only

0x00000001

Role
Group 4

None

No assigned permissions

0x00000000

Role
Group 5

None

No assigned permissions

0x00000000

NOTE: The Bit Mask values are used only when setting Standard Schema with
the RACADM.

Using iDRAC6 With Microsoft Active Directory

133

Single Domain Versus Multiple Domain Scenarios
If all of the login users and role groups, as well as the nested groups, are in the
same domain, then only the domain controllers’ addresses must be configured
on iDRAC6. In this single domain scenario, any group type is supported.
If all of the login users and role groups, or any of the nested groups, are from
multiple domains, then Global Catalog server addresses are required to be
configured on iDRAC6. In this multiple domain scenario, all of the role
groups and nested groups, if any, must be Universal Group type.

Configuring Standard Schema Active Directory to Access iDRAC6
You must perform the following steps to configure Active Directory before an
Active Directory user can access iDRAC6:
1 On an Active Directory server (domain controller), open the Active
Directory Users and Computers Snap-in.
2 Create a group or select an existing group. The name of the group and the
name of this domain must be configured on iDRAC6 by using either the
Web-based interface or RACADM (see "Configuring Active Directory
With Standard Schema Using the iDRAC6 Web-Based Interface" or
"Configuring Active Directory With Standard Schema Using RACADM").
3 Add the Active Directory user as a member of the Active Directory group
to access iDRAC6.

Configuring Active Directory With Standard Schema Using the iDRAC6
Web-Based Interface
1 Open a supported Web browser window.
2 Log in to the iDRAC6 Web interface.
3 In the system tree, select System→ Remote Access→ iDRAC.
4 Click the Network Security tab, and then click Active Directory.
The Active Directory Configuration and Management screen appears.
5 Scroll to the bottom of the screen and click Configure Active Directory.
The Step 1 of 4 Active Directory Configuration and Management
screen appears.
6 Under Certificate Settings, select Enable Active Directory.
134

Using iDRAC6 With Microsoft Active Directory

7 Under Upload Active Directory CA Certificate, enter the file path of the
certificate or browse to find the certificate file, and then click Upload.
NOTE: You must enter the absolute file path, which includes the full path and
the complete file name and file extension.

The certificate information for the Active Directory CA certificate that you
uploaded appears in the Current Active Directory CA Certificate section.
8 Click Next.
The Step 2 of 4 Active Directory Configuration and Management
screen appears.
9 Select the Enable Active Directory check box.
10 Click Add to enter the user domain name, enter the user domain name in
the text field, and then click OK.
11 In the Timeout field, enter the number of seconds you want iDRAC6 to
wait for Active Directory responses. The default is 120 seconds.
12 Enter the Domain Controller Server Address. You can enter up to three
Active Directory servers for login processing, but you must configure at
least one server by entering the IP address or the fully qualified domain
name (FQDN). iDRAC6 attempts to connect to each configured server
until a connection is established.
13 Click Next.
The Step 3 of 4 Active Directory Configuration and Management
screen appears.
14 Under Schema Selection, select the Standard Schema check box.
15 Click Next.
The Step 4a of 4 Active Directory Configuration and Management
screen appears.
16 Under Standard Schema Settings, enter the Global Catalog
Server Address(es).
NOTE: The Global Catalog server is only required for standard schema when
the user accounts and role groups are in different domains. And, in this
multiple domain case, only the Universal Group can be used.

17 Click a Role Group button to add a role group.
The Step 4b of 4 Configure Role Group 1 screen appears.
Using iDRAC6 With Microsoft Active Directory

135

18 Enter the Group Name. The group name identifies the role group in the
Active Directory associated with iDRAC6.
19 Enter the Group Domain. The Group Domain is the fully qualified root
domain name for the forest.
20 In the Role Group Privileges section, set the group privileges. Refer to
Table 5-11 on page 93 for information on role group privileges.
NOTE: If you modify any of the permissions, the existing role group privilege
(Administrator, Power User, or Guest User) will change to either the Custom
Group or the appropriate role group privilege based on the permissions you
modified.

21 Click OK to save the role group settings.
An alert dialog appears, indicating that your settings are changed.
Click OK to return to the Step 4a of 4 Active Directory Configuration
and Management screen.
22 To add an additional role group, repeat step 17 through step 21.
23 Click Finish, and the click Done.
The main Active Directory Configuration and Management appears.
Next, you must test the Active Directory settings you just configured.
24 Scroll to the bottom of the screen and click Test Settings.
The Test Active Directory Settings screen appears.
25 Enter your iDRAC6 user name and password, and then click Start Test.
Test results and the test log display. For additional information,
see "Testing Your Configurations."
NOTE: You must have a DNS server configured properly on iDRAC6 to support
Active Directory login. Navigate to Remote Access→ Configuration→ Network
page to configure DNS server(s) manually or use DHCP to get DNS server(s).
You have completed the Active Directory configuration with Standard Schema.

136

Using iDRAC6 With Microsoft Active Directory

Configuring Active Directory With Standard Schema Using RACADM
Use the following commands to configure the iDRAC6 Active Directory
Feature with Standard Schema using the RACADM CLI instead of the
Web-based interface.
1 Open a command prompt and enter the following RACADM commands:
racadm config -g cfgActiveDirectory -o
cfgADEnable 1
racadm config -g cfgActiveDirectory -o cfgADType 2
racadm config -g cfgStandardSchema -i -o
cfgSSADRoleGroupName
racadm config -g cfgStandardSchema -i -o
cfgSSADRoleGroupDomain
racadm config -g cfgStandardSchema -i -o
cfgSSADRoleGroupPrivilege
NOTE: For Bit Mask Number values, see Table B-1.
racadm config -g cfgActiveDirectory -o
cfgDomainController1
racadm config -g cfgActiveDirectory -o
cfgDomainController2
racadm config -g cfgActiveDirectory -o
cfgDomainController3
NOTE: Enter the FQDN of the domain controller, not the FQDN of the domain.
For example, enter servername.dell.com instead of dell.com.
NOTE: At least one of the 3 addresses is required to be configured. iDRAC6
attempts to connect to each of the configured addresses one-by-one until a
successful connection is made. With Standard Schema, these are the
addresses of the domain controllers where the user accounts and the role
groups are located.

Using iDRAC6 With Microsoft Active Directory

137

racadm config -g cfgActiveDirectory -o cfgGlobal
Catalog1
racadm config -g cfgActiveDirectory -o cfgGlobal
Catalog2
racadm config -g cfgActiveDirectory -o cfgGlobal
Catalog3
NOTE: The Global Catalog server is only required for standard schema when
the user accounts and role groups are in different domains. And, in this
multiple domain case, only the Universal Group can be used.

NOTE: The FQDN or IP address that you specify in this field should match the
Subject or Subject Alternative Name field of your domain controller certificate
if you have certificate validation enabled.

138

Using iDRAC6 With Microsoft Active Directory

2 If DHCP is enabled on iDRAC6 and you want to use the DNS provided by
the DHCP server, enter the following RACADM commands:
racadm config -g cfgLanNetworking -o
cfgDNSServersFromDHCP 1
3 If DHCP is disabled on iDRAC6 or you want manually to input your DNS
IP address, enter the following RACADM commands:
racadm config -g cfgLanNetworking -o
cfgDNSServersFromDHCP 0
racadm config -g cfgLanNetworking -o cfgDNSServer1

racadm config -g cfgLanNetworking -o cfgDNSServer2

4 If you want to configure a list of user domains so that you only need to
enter the user name when logging in to the Web-based interface, enter the
following command:
racadm config -g cfgUserDomain -o
cfgUserDomainName -i
Up to 40 user domains can be configured with index numbers between
1 and 40.
See "Using Active Directory to Log In to iDRAC6" for details about
user domains.

Testing Your Configurations
If you want to verify whether your configuration works, or if you need to
diagnose the problem with your failed Active Directory log in, you can test
your settings from the iDRAC6 Web-based interface.
After you finish configuring settings in the iDRAC6 Web-based interface,
click Test Settings at the bottom of the screen. You will be required to enter a
test user's name (for example, username@domain.com) and password to run
the test. Depending on your configuration, it may take some time for all of
the test steps to complete and display the results of each step. A detailed test
log will display at the bottom of the results screen.

Using iDRAC6 With Microsoft Active Directory

139

If there is a failure in any step, examine the details in the test log to identify
the problem and a possible solution. For most common errors, see
"Frequently Asked Questions."
If you need to make changes to your settings, click the Active Directory tab
and change the configuration step-by-step.

Enabling SSL on a Domain Controller
When iDRAC6 authenticates users against an Active Directory domain
controller, it starts an SSL session with the domain controller. At this time,
the domain controller should publish a certificate signed by the Certificate
Authority (CA)—the root certificate of which is also uploaded into iDRAC6.
In other words, for iDRAC6 to authenticate to any domain controller—
whether it is the root or the child domain controller—that domain controller
should have an SSL-enabled certificate signed by the domain’s CA.
If you are using Microsoft Enterprise Root CA to automatically assign all your
domain controllers to an SSL certificate, perform the following steps to
enable SSL on each domain controller:
1 Enable SSL on each of your domain controllers by installing the SSL
certificate for each controller.
a

Click Start→ Administrative Tools→ Domain Security Policy.

Expand the Public Key Policies folder, right-click Automatic
Certificate Request Settings and click Automatic Certificate Request.

In the Automatic Certificate Request Setup Wizard, click Next and
select Domain Controller.

Click Next and click Finish.

Exporting the Domain Controller Root CA Certificate to iDRAC6
NOTE: If your system is running Windows 2000, the following steps may vary.
NOTE: If you are using a standalone CA, the following steps may vary.
1 Locate the domain controller that is running the Microsoft Enterprise
CA service.
2 Click Start→ Run.
3 In the Run field, enter mmc and click OK.
140

Using iDRAC6 With Microsoft Active Directory

4 In the Console 1 (MMC) window, click File (or Console on Windows 2000
systems) and select Add/Remove Snap-in.
5 In the Add/Remove Snap-In window, click Add.
6 In the Standalone Snap-In window, select Certificates and click Add.
7 Select Computer account and click Next.
8 Select Local Computer and click Finish.
9 Click OK.
10 In the Console 1 window, expand the Certificates folder, expand the
Personal folder, and click the Certificates folder.
11 Locate and right-click the root CA certificate, select All Tasks, and click
Export...
12 In the Certificate Export Wizard, click Next, and select No do not export
the private key.
13 Click Next and select Base-64 encoded X.509 (.cer) as the format.
14 Click Next and save the certificate to a directory on your system.
15 Upload the certificate you saved in step 14 to iDRAC6.
To upload the certificate using RACADM, see "Configuring Active
Directory With Standard Schema Using RACADM."
To upload the certificate using the Web-based interface, see "Configuring
Active Directory With Standard Schema Using the iDRAC6 Web-Based
Interface."

Importing the iDRAC6 Firmware SSL Certificate
NOTE: If the Active Directory Server is set to authenticate the client during an SSL
session initialization phase, you need to upload the iDRAC6 Server certificate to the
Active Directory Domain controller as well. This additional step is not required if the
Active Directory does not perform a client authentication during an SSL session’s
initialization phase.
Use the following procedure to import the iDRAC6 firmware SSL certificate
to all domain controller trusted certificate lists.
NOTE: If your system is running Windows 2000, the following steps may vary.
NOTE: If the iDRAC6 firmware SSL certificate is signed by a well-known CA and the
certificate of that CA is already in the domain controller's Trusted Root Certificate
Authority list, you are not required to perform the steps in this section.
Using iDRAC6 With Microsoft Active Directory

141

The iDRAC6 SSL certificate is the identical certificate used for the iDRAC6
Web server. All iDRAC6 controllers are shipped with a default self-signed
certificate.
To download the iDRAC6 SSL certificate, run the following RACADM
command:
racadm sslcertdownload -t 0x1 -f
1 On the domain controller, open an MMC Console window and select
Certificates→ Trusted Root Certification Authorities.
2 Right-click Certificates, select All Tasks and click Import.
3 Click Next and browse to the SSL certificate file.
4 Install the iDRAC6 SSL Certificate in each domain controller’s Trusted
Root Certification Authority.
If you have installed your own certificate, ensure that the CA signing your
certificate is in the Trusted Root Certification Authority list. If the
Authority is not in the list, you must install it on all your Domain Controllers.
5 Click Next and select whether you would like Windows to automatically
select the certificate store based on the type of certificate, or browse to a
store of your choice.
6 Click Finish and click OK.

Using Active Directory to Log In to iDRAC6
You can use Active Directory to log in to iDRAC6 using one of the following
methods:
•

Web-based interface

•

Local RACADM

•

SSH or telnet console for SM-CLP CLI

The login syntax is the same for all three methods:

or
\ or /
where username is an ASCII string of 1–256 bytes.

142

Using iDRAC6 With Microsoft Active Directory

White space and special characters (such as \, /, or @) cannot be used in the
user name or the domain name.
NOTE: You cannot specify NetBIOS domain names, such as Americas, because
these names cannot be resolved.
If you log in from the Web-based interface and you have configured user
domains, the Web-based interface log in screen will list all the user domains in
the pull-down menu for your to choose. If you select a user domain from the
pull-down menu, you should only enter the user name. If you select
This iDRAC, you can still log in as an Active Directory user if you use the login
syntax described above in "Using Active Directory to Log In to iDRAC6."

Frequently Asked Questions
Active Directory Log In Issues
My Active Directory log in failed. What do I do?

iDRAC6 provides a diagnostic tool in the Web-based interface.
1 Log in as a local user with administrator privilege from the Web-based
interface.
2 In the system tree, select System→ Remote Access→ iDRAC.
3 Click the Network/Security tab, and then click the Active Directory sub-tab.
The Active Directory Configuration and Management screen appears.
4 Scroll to the bottom of the screen and click Test Settings.
The Test Active Directory Settings screen appears.
5 Enter a test user name and password, and then click Start Test.
iDRAC6 runs the tests step-by-step and displays the result for each step.
iDRAC6 also logs a detailed test result to help you resolve any problems.
If problems persist:
a

On the Test Settings screen, click the Active Directory sub-tab to return
to the Active Directory Configuration and Management screen.

Scroll to the bottom of the screen and click Configure Active Directory.

Change your user configuration, and run the test again until the test
user passes the authorization step.

Using iDRAC6 With Microsoft Active Directory

143

I enabled certificate validation but I failed my Active Directory log in. I ran the
diagnostics from the GUI and the test result shows the following error message:

ERROR: Can't contact LDAP server,
error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify failed: Please check the correct
Certificate Authority (CA) certificate has been
uploaded to iDRAC. Please also check if the iDRAC
date is within the valid period of the
certificates and if the Domain Controller Address
configured in iDRAC matches the subject of the
Directory Server Certificate.
What could the problem be and how do I fix it?

If certificate validation is enabled, iDRAC6 uses the uploaded CA certificate
to verify the directory server certificate when iDRAC6 establishes the SSL
connection with the directory server. The most common reasons for failing
certification validation are:

144

•

The iDRAC6 date is not within the valid period of the server certificate or
CA certificate. Check the iDRAC6 time and the valid period of
your certificate.

•

The Domain Controller Addresses configured in iDRAC6 do not match
the Subject or Subject Alternative Name of the directory server certificate.
–

If you are using an IP address, see "I'm using an IP address for a
Domain Controller Address, and I failed certificate validation. What's
the problem?".

–

If you are using FQDN, ensure you are using the FQDN of the domain
controller, and not the domain itself. For example, use
servername.example.com and not example.com.

Using iDRAC6 With Microsoft Active Directory

What should I check if I cannot log in to iDRAC6 using Active Directory?

First, diagnose the problem using the Test Settings feature. For directions,
see "My Active Directory log in failed. What do I do?"
Then, fix the specific problem indicated by the test results. For additional
information, see "Testing Your Configurations."
Most common issues are explained in this section. However, in general,
you should check the following:
1 Ensure that you use the correct user domain name during a log in and not
the NetBIOS name.
2 If you have a local iDRAC6 user account, log in to iDRAC6 using your
local credentials.
3 Check the following settings:
a

Navigate to the Active Directory Configuration and Management
screen. Select System→ Remote Access→ iDRAC, click the Network/
Security tab, and then click the Active Directory subtab.

Ensure that the Active Directory Enabled check box is checked.

If you enabled certificate validation, ensure that you have uploaded
the correct Active Directory root CA certificate to iDRAC6. The
certificate appears in the Active Directory CA Certificate area.
Ensure that the iDRAC6 time is within the valid period of the CA
certificate.

If you are using the Extended Schema, ensure that the iDRAC Name
and iDRAC Domain Name match your Active Directory environment
configuration.
If you are using the Standard Schema, ensure that the Group Name
and Group Domain Name match your Active Directory configuration.

Navigate to the Network Configuration screen. Select System→
Remote Access→ iDRAC, and then click Network/Security.
Ensure that the DNS settings are correct.

Check the Domain Controller SSL certificates to ensure that the
iDRAC6 time is within the valid period of the certificate.

Using iDRAC6 With Microsoft Active Directory

145

Active Directory Certificate Validation
I'm using an IP address for a Domain Controller Address, and I failed certificate
validation. What's the problem?

Check the Subject or Subject Alternative Name field of your domain controller
certificate. Usually Active Directory uses the hostname, not the IP address,
of the domain controller in the Subject or Subject Alternative Name field of
the domain controller certificate. You can fix the problem by taking any of
the following actions:
•

Configure the hostname (FQDN) of the domain controller as the domain
controller address(es) on iDRAC6 to match the Subject or Subject
Alternative Name of the server certificate.

•

Re-issue the server certificate to use an IP address in the Subject or
Subject Alternative Name field so it matches the IP address configured
in iDRAC6.

•

Disable certificate validation if you choose to trust this domain controller
without certificate validation during the SSL handshake.

Why does iDRAC6 enable certificate validation by default?

iDRAC6 enforces strong security to ensure the identity of the domain
controller that iDRAC6 connects to. Without certificate validation, a hacker
could spoof a domain controller and hijack the SSL connection. If you choose
to trust all the domain controllers in your security boundary without
certificate validation, you can disable it through the GUI or the CLI.

Extended and Standard Schema
I'm using extended schema in a multiple domain environment. How do I configure
the domain controller address(es)?

Use the host name (FQDN) or the IP address of the domain controller(s) that
serves the domain in which the iDRAC6 object resides.
Do I need to configure Global Catalog Address(es)?

If you are using extended schema, you cannot configure global catalog
addresses, because they are not used with extended schema.

146

Using iDRAC6 With Microsoft Active Directory

If you are using standard schema, and users and role groups are from different
domains, you must configure global catalog address(es). In this case, you can
use only Universal Group.
If you are using standard schema, and all the users and all the role groups are
in the same domain, you are not required to configure global catalog
address(es).
How does standard schema query work?

iDRAC6 connects to the configured domain controller address(es) first. If the
user and role groups reside in that domain, the privileges are saved.
If global controller address(es) is configured, iDRAC6 continues to query the
Global Catalog. If additional privileges are retrieved from the Global Catalog,
these privileges are accumulated.

Miscellaneous
Does iDRAC6 always use LDAP over SSL?

Yes. All the transportation is over secure port 636 and/or 3269.
During test setting, iDRAC6 does a LDAP CONNECT only to help isolate
the problem, but it does not do an LDAP BIND on an insecure connection.
Does iDRAC6 support the NetBIOS name?

Not in this release.

Using iDRAC6 With Microsoft Active Directory

147

148

Using iDRAC6 With Microsoft Active Directory

Viewing the Configuration and
Health of the Managed Server
System Summary
Click System→ Properties→ Summary to obtain information about the
Main System Enclosure and the Integrated Dell Remote Access Controller.

Main System Enclosure
System Information

This section of the iDRAC6 Web interface provides the following basic
information about the managed server:
•

Description — The model number or name of the managed server

•

BIOS Version — The version number of the managed server's BIOS

•

Service Tag — The Service Tag number of the managed server

•

Host Name — The DNS hostname associated with the managed server

•

OS Name — The name of the operating system installed on the
managed server

I/O Mezzanine Card

This section of the iDRAC6 Web interface provides the following
information about the I/O Mezzanine cards installed on the managed server:
•

Connection — Lists the I/O Mezzanine card(s) installed on the
managed server

•

Card Type — The physical type of the installed Mezzanine card/connection

•

Model Name — The model number, type, or description of the installed
Mezzanine card(s)
Viewing the Configuration and Health of the Managed Server

149

Integrated Storage Card

This section of the iDRAC6 Web interface provides information about the
integrated Storage Controller Card installed on the Managed Server:
•

Card Type — shows the model name of the installed storage card

Auto Recovery

This section of the iDRAC6 Web interface details the current mode of
operation of the Auto Recovery feature of the managed server as set by
Open Manage Server Administrator:
•

Recovery Action — Action to be performed when a system fault or hang is
detected. Available actions are No Action, Hard Reset, Power Down,
or Power Cycle.

•

Initial Countdown — The amount of time (in seconds) after a system
hang is detected at which time iDRAC6 performs a recovery action.

•

Present Countdown — The current value (in seconds) of the
countdown timer.

Integrated Dell Remote Access Controller 6 - Enterprise
iDRAC6 Information

This section of the iDRAC6 Web interface provides the following
information about iDRAC6 itself:

150

•

Date/Time — The current date and time (as of last page refresh) of iDRAC6

•

Firmware Version — The current version of iDRAC6 firmware installed on
the managed server

•

Firmware Updated — The date and time of the last successful iDRAC6
firmware update

•

Hardware Version — The version number of the primary planar
(circuit board) of the managed server

•

IP Address — The IP address associated with iDRAC6 (not the
managed server)

•

Gateway — The IP address of the network gateway configured for iDRAC6

•

Subnet Mask — The TCP/IP Subnet Mask configured for iDRAC6

•

MAC Address — The MAC address associated with the LOM (LAN on
Motherboard) Network Interface Controller of iDRAC6
Viewing the Configuration and Health of the Managed Server

•

DHCP Enabled — Enabled if iDRAC6 is set to fetch its IP address and
associated info from a DHCP server

•

Preferred DNS Address 1 — Set to the currently active primary DNS server

•

Alternate DNS Address 2 — Set to the alternate DNS server address
NOTE: This information is also available at iDRAC→ Properties→ iDRAC Information.

WWN/MAC Summary
Click System→ Properties→ WWN/MAC to view the current configuration
of installed I/O Mezzanine cards and their associated network fabrics. If the
FlexAddress feature is enabled, the globally assigned (Chassis-Assigned)
persistent MAC addresses supersede the hardwired values of each LOM.

System Health
Click System→ Properties→ Health to view important information about
the health of iDRAC6 and components monitored by iDRAC6. The Severity
column shows the status for each component. For a list of status icons and
their meaning, see Table 17-3. Click the component name in the Component
column for more detailed information about the component.
NOTE: Component information can also be obtained by clicking the component
name in the left pane of the window. Components remain visible in the left pane
independent of the tab/screen that is selected.

iDRAC6
The iDRAC6 Information screen lists a number of important details about
iDRAC6, such as health status, name, firmware revision, and network
parameters. Additional details are available by clicking the appropriate tab at
the top of the screen.

CMC
The CMC screen displays the health status, firmware revision, and IP address
of the Chassis Management Controller. You can also launch the CMC Web
interface by clicking the Launch the CMC Web Interface button. See the
Chassis Management Controller Firmware User Guide.

Viewing the Configuration and Health of the Managed Server

151

Batteries
The Batteries screen displays the status and values of the system board
coin-cell battery that maintains the Real-Time Clock (RTC) and CMOS
configuration data storage of the managed system.

Temperatures
The Temperature Probes Information screen displays the status and readings
of the on-board ambient temperature probe. Minimum and maximum
temperature thresholds for warning or failure states are shown, along with the
current health status of the probe.

Voltages
The Voltage Probes Information screen displays the status and reading of the
Voltage probes, providing such information as the status of the on-board
voltage rail and CPU core sensors.
NOTE: Depending on the model of your server, temperature thresholds for warning
or failure states and/or the health status of the probe may not be displayed.

Power Monitoring
The Power Monitoring screen enables you to view the following monitoring
and power statistics information:
•

Power Monitoring — Displays the amount of power being used (in watts)
by the server as reported by the System Board Current Monitor.

•

Power Tracking Statistics — Displays information about the amount of
power used by the system since the Measurement Start Time was last
reset.

•

Peak Statistics — Displays information about the peak amount of power
used by the system since the Measurement Start Time was last reset.

CPU
The CPU Information screen reports the health of each CPU on the
managed server. This health status is a roll-up of a number of individual
thermal, power, and functional tests.

152

Viewing the Configuration and Health of the Managed Server

POST
The Post Code screen displays the last system post code (in hexadecimal)
prior to booting the operating system of the managed server.

Misc Health
The Misc Health screen provides access to the following system logs:
•

System Event Log — Displays system-critical events that occur on the
managed system.

•

Post Code — Displays the last system post code (in hexadecimal) prior to
booting the operating system of the managed server.

•

Last Crash — Displays the most recent crash screen and time.

•

Boot Capture — Provides playback of the last three boot screens.
NOTE: This information is also available at System→ Properties→ Logs.

Viewing the Configuration and Health of the Managed Server

153

154

Viewing the Configuration and Health of the Managed Server

Power Monitoring and Power
Management
Dell™ PowerEdge™ systems incorporate many new and enhanced power
management features. The entire platform, from hardware to firmware to
systems management software, has been designed with a focus on power
efficiency, power monitoring, and power management.
PowerEdge systems provide many features for monitoring and managing power:
•

Power Monitoring: iDRAC6 collects a history of power measurements
and calculates running averages, peaks, and so on. Using the iDRAC6
Web-based interface, you can view the information on the Power
Monitoring screen. You can also view the information in graph form by
clicking Show Graph at the bottom of the Power Monitoring screen.
See "Power Control" for more information.

•

Power Budgeting: At boot, a system inventory enables a system power
budget of the current configuration to be calculated. See "Power
Monitoring" for more information.

•

Power Control: iDRAC6 enables you to remotely perform several
power management actions on the managed system. See "Power Control"
for more information.

Configuring and Managing Power
You can use the iDRAC6 Web-based interface and RACADM command line
interface (CLI) to manage and configure power controls on the PowerEdge
system. Specifically, you can:
•

View the power status of the server. See "Viewing Power Monitoring."

•

View power budget information for the server, including the minimum and
maximum potential power consumption. See "Viewing Power Budget."

Power Monitoring and Power Management

155

•

View power budget threshold for the server. See "Viewing Power Budget
Threshold."

•

Execute power control operations on the server (for example, power on,
power off, system reset, power cycle). See "Executing Power Control
Operations on the Server."

Power Monitoring
iDRAC6 monitors the power consumption in PowerEdge servers continuously.
iDRAC6 calculates the following power values and provides the information
through its Web-based interface or RACADM CLI:
•

Cumulative power

•

Average, minimum, and maximum power

•

Power consumption (also shown in graphs in the Web-based interface)

•

Power budget thresholds

Viewing Power Monitoring
Using the Web Interface

To view the power monitoring data:
1 Log in to the iDRAC6 Web interface.
2 In the system tree, select Power Monitoring.
The Power Monitoring screen appears, displaying the following information:
Power Monitoring

•

Status: A green check indicates that the power status is normal, Warning
indicates that a warning alert was issued, and Severe indicates a failure
alert was issued.

•

Probe Name: System Board System Level. This description indicates the
probe is being monitored by its location in the system.

•

Reading: The current power consumption in Watts.

Amperage

156

•

Location: System Board Current Monitor Current

•

Reading: The current power consumption in Amps
Power Monitoring and Power Management

Power Tracking Statistics

•

Statistic:
–

Cumulative System Power displays the current cumulative energy
consumption (in KWh) for the server. The value represents the total
energy used by the system. You can reset this value to 0 by clicking
Reset at the end of the table row.

–

System Peak Power specifies the system peak value in Watts within
the interval specified by the Measurement Start Time and Measure
Current Time. You can reset this value to 0 by clicking Reset at the
end of the table row.

–

System Peak Amperage specifies the system peak amperage within the
interval specified by the Measurement Start Time and Measure
Current Time. You can reset this value to 0 by clicking Reset at the
end of the table row.

•

Measurement Start Time displays the date and time recorded when the
system energy consumption value was last cleared and the new
measurement cycle began. For Cumulative System Power, System Peak
Amperage, and System Peak Power statistics, you can reset each value to 0
by clicking Reset at the end of the table row; however, it will persist
through a system reset or CMC failover operation.

•

Measurement Current Time for Cumulative System Power displays the
current date and time when the system energy consumption was
calculated for display. For System Peak Amperage and System Peak Power,
the Peak Time fields display the time when these peaks occurred.

•

Reading: The amount of power (in KWh) used since the counter was started.
NOTE: Power Tracking Statistics are maintained across system resets and so reflect
all activity in the interval between the stated Start and Finish Times.The Reset Max
Peaks button will reset to peak statistics value. In the next table, Power Consumption
data is not maintained across system resets and so will reset back to peak statistics
value. The power values displayed are cumulative averages over the respective time
interval (previous minute, hour, day and week). Since the Start to Finish time intervals
here may differ from those of the Power Tracking Statistics ones, peak power values
(Max Peak Watts versus Max Power Consumption) may differ.

Power Monitoring and Power Management

157

Power Consumption

•

Average Power Consumption: Average over previous minute, previous
hour, previous day and previous week.

•

Max Power Consumption and Min Power Consumption: The maximum
and minimum power consumptions observed within the given time interval.

•

Max Power Time and Min Power Time: The times (by minute, hour, day,
and week) when the maximum and minimum power consumptions occurred.

Show Graph

Click Show Graph to display graphs illustrating iDRAC6 power consumption
in Watts over the last hour, 24 hours, three days, and one week. Use the
drop-down menu provided above the graph to select the time period.
NOTE: Each data point plotted on the graphs represents the average of readings
over a 5 minute period. As a result, the graphs may not reflect brief fluctuations in
power or current consumption.

Power Budgeting
iDRAC6 can be configured to enforce the minimum and maximum power
threshold limits, as set by the CMC, for the current system configuration.
The Power Budget screen displays these power threshold limits, which cover the
range of AC power consumptions a thresholded system under heavy workload will
present to the datacenter. These limits are not configurable.

Viewing Power Budget
The server provides power budget status overviews of the power subsystem on the
Power Budget Information screen.
Using the Web Interface

NOTE: To perform power management actions, you must have Administrative
privilege.
1 Log in to the iDRAC6 Web-based interface.
2 In the system tree, select System.
3 Click the Power Management tab, and then click Power Budget.
The Power Budget Information screen appears.
158

Power Monitoring and Power Management

The Power Budget Information table displays the minimum and maximum
limits of power thresholds for the current system configuration. These cover
the range of AC power consumptions a thresholded system under heavy
workload will present to the datacenter.
•

Minimum Potential Power Consumption represents the lowest Power
Budget Threshold value.

•

Maximum Potential Power Consumption represents the highest Power
Budget Threshold value. This value is also the current system
configuration's absolute maximum power consumption.

Using RACADM

On a Managed Node, open a command line interface and enter:
racadm getconfig -g cfgServerPower
NOTE: For more information about cfgServerPower, including output details,
see "cfgServerPower."

Viewing Power Budget Threshold
Power Budget Threshold, if enabled, enforces power limits for the system.
System performance is dynamically adjusted to maintain power consumption
near the specified threshold.
NOTE: Power budget threshold is read-only and cannot be enabled or configured
in iDRAC6.
Actual power consumption may be less for light workloads and momentarily
exceed the threshold until performance adjustments have completed.
Using the Web-Based Interface

1 Log in to the iDRAC6 Web-based interface.
2 In the system tree, select System.
3 Click the Power Management tab, and then click Power Budget.
The Power Budget Information screen appears.
4 Click Power Budget Threshold.

Power Monitoring and Power Management

159

The Power Budget Threshold table displays the power limit information for
the system:
•

Enabled indicates whether the system enforces the power budget threshold.

•

Threshold in Watts and Threshold in BTU/hr display the limit in Watts
and BTU/hr, respectively.

•

Threshold Percentage displays the percentage of power range.

Using RACADM

On a Managed Node, open a command line interface and enter:
racadm getconfig -g cfgServerPower -o
cfgServerPowerCapWatts
racadm getconfig -g cfgServerPower -o
cfgServerPowerCapBTUhr
racadm getconfig -g cfgServerPower -o
cfgServerPowerCapPercent
NOTE: For more information about cfgServerPower, including output details,
see "cfgServerPower."

Power Control
iDRAC6 enables you to remotely perform a power-on, reset, graceful shutdown,
non-masking interruption (NMI), or power cycle. Use the Power Control screen
to perform an orderly shutdown through the operating system when rebooting and
powering on or off.

Executing Power Control Operations on the Server
NOTE: To perform power management actions, you must have Chassis Control
Administrator privilege.
iDRAC6 enables you to remotely perform a power-on, reset, graceful shutdown,
NMI, or power cycle.
Using the Web Interface

1 Log in to the iDRAC6 Web interface.
2 In the system tree, select System.
160

Power Monitoring and Power Management

3 Click the Power Management tab.
The Power Control screen displays.
4 Select one of the following Power Control Operations by clicking its
radio button:
–

Power On System turns on the server (the equivalent of pressing the
power button when the server power is off). This option is disabled if
the system is already powered on.

–

Power Off System turns off the server. This option is disabled if the
system is already powered off.

–

NMI (Non-Masking Interrupt) generates an NMI to halt system
operation. An NMI sends a high-level interrupt to the operating
system, which causes the system to halt operation to allow for critical
diagnostic or troubleshooting activities.

–

Graceful Shutdown attempts to cleanly shutdown the operating
system, then powers off the system. Graceful shutdown requires an
ACPI (Advanced Configuration and Power Interface)-aware operating
system, which allows for system directed power management.

–

Reset System (warm boot) reboots the system without powering off.
This option is disabled if the system is already powered off.

–

Power Cycle System (cold boot) powers off and then reboots the system.
This option is disabled if the system is already powered off.

5 Click Apply.
A dialog box appears requesting confirmation.
6 Click OK to execute the power management action you selected.
Using RACADM

Open a Managed Node open command line interface text console to the server,
log in, and enter:
racadm serveraction
where is powerup, powerdown, powercycle, hardreset,
or powerstatus.
NOTE: For more information about serveraction, including output details,
see "serveraction."

Power Monitoring and Power Management

161

162

Power Monitoring and Power Management

Configuring and Using Serial
Over LAN
Serial Over LAN (SOL) is an IPMI feature that allows a managed server’s text
based console data that would traditionally be sent to the serial I/O port to be
redirected over the iDRAC’s dedicated Out of Band Ethernet management
network. The SOL out-of-band console enables system administrators to
remotely manage the blade server’s text-based console from any location with
network access. Benefits of SOL are as follows:
•

Remotely access operating systems with no timeout.

•

Diagnose host systems on Emergency Management Services (EMS) or
Special Administrator Console (SAC) for Windows or in a Linux shell.

•

View the progress of a blade server during POST and reconfigure the BIOS
setup program (while redirected to a serial port).

Enabling Serial Over LAN in the BIOS
To configure the server for Serial Over LAN, the following configuration steps
are required and will be explained in detail.
1 Configure Serial Over LAN in BIOS (disabled by default)
2 Configure iDRAC6 for Serial over LAN
3 Select a method to initialize Serial Over LAN (SSH, telnet, SOL Proxy, or
IPMI Tool)
4 Configure the OS for SOL

Configuring and Using Serial Over LAN

163

Serial communication is off by default in BIOS. In order to redirect the host
text console data to Serial over LAN, you must enable console redirection via
COM1. To change the BIOS setting, perform the following steps:
1 Boot the managed server.
2 Press to enter the BIOS setup utility during POST.
3 Scroll down to Serial Communication and press .
In the pop-up window, the serial communication list is presented with the
following options:
•

Off

•

On without console redirection

•

On with console redirection via COM1

Use the arrow keys to navigate between options.
4 Ensure that On with console redirection via COM1 is enabled.
5 Ensure that the Failsafe Baud Rate is identical to SOL baud rate that is
configured on iDRAC. The default value for both the failsafe baud rate
and the iDRAC’s SOL baud rate setting is 115.2 kbps.
6 Enable the Redirection After Boot (the default value is DISABLED).
This option enables BIOS SOL redirection across subsequent reboots.
7 Save the changes and exit.
The managed server reboots.

Configuring Serial Over LAN in the iDRAC6
Web GUI
1 Open the Serial Over LAN Configuration screen by selecting System→
Remote Access→ iDRAC→ Network/Security→ Serial Over LAN.
2 Ensure the Enable Serial Over LAN option is selected (enabled). By
default it is enabled.
3 Update the IPMI SOL baud rate by selecting a data speed from the Baud
Rate drop-down menu. The options are 19.2 kbps, 57.6 kbps, and 115.2
kbps. The default value is 115.2 kbps.
NOTE: Ensure that the SOL baud rate is identical to the Failsafe Baud Rate
that was set in BIOS.

164

Configuring and Using Serial Over LAN

4 Click Apply if you have made any changes.
Table 9-1.

Serial Over LAN Configuration Settings

Setting

Description

Enable Serial
Over LAN

When selected, the checkbox indicates that Serial Over LAN is
enabled.

Baud Rate

Indicates the data speed. Select a data speed of 19.2 kbps, 57.6
kbps, or 115.2 kbps.

Table 9-2.

Serial Over LAN Configuration Buttons

Button

Description

Prints the Serial Over LAN Configuration values that appear on
the screen.

Refresh

Reloads the Serial Over LAN Configuration screen.

Advanced
Settings

Opens the Serial Over LAN Configuration Advanced Settings
screen.

Apply

Supplies any new settings that you make while viewing the Serial
Over LAN Configuration screen.

5 Change the configuration on the Advanced Settings screen, if necessary.
Dell recommends using the default values. Advanced Settings allows you
to adjust SOL performance by changing the Character Accumulate
Interval and Character Send Threshold values. For optimal performance,
use the default settings of 10 milliseconds and 250 characters, respectively.

Configuring and Using Serial Over LAN

165

Table 9-3.

Serial Over LAN Configuration Advanced Settings

Setting

Description

Character
Accumulate
Interval

The typical amount of time iDRAC6 waits before sending a partial
SOL data packet. This parameter is specified in milliseconds and
increments by 10 milliseconds.

Character Send
Threshold

Specifies the number of characters per SOL data packet. As soon
as the number of characters accepted by iDRAC6 is equal to or
greater than the Character Send Threshold value, iDRAC6 starts
transmitting SOL data packets that contain numbers of characters
equal to or less than the Character Send Threshold value. If a
packet contains fewer characters than this value, it is defined to be
a partial SOL data packet.

NOTE: If you change these values to lower values, the console redirection
feature of SOL may experience a reduction in performance. Furthermore,
the SOL session must wait to receive an acknowledgement for each packet
before sending the next packet. As a result, the performance is
significantly reduced.
Table 9-4.

Serial Over LAN Configuration Advanced Settings Buttons

Button

Description

Prints the Serial Over LAN Configuration Advanced
Settings values that appear on the screen.

Refresh

Reloads the Serial Over LAN Configuration Advanced
Settings screen.

Apply

Saves any new settings that you make while viewing the
Serial Over LAN Configuration Advanced Settings screen.

Go Back To Serial Over Returns the user to the Serial Over LAN Configuration
LAN Configuration
screen.
Page

6 Configure SSH/Telnet for SOL at System→ Remote Access→ iDRAC→
Network/Security→ Services.
NOTE: Each blade server only supports one active SOL session through
SSH or Telnet protocol.

166

Configuring and Using Serial Over LAN

NOTE: SSH protocol is enable by default. Telnet protocol is disabled
by default.

7 Click Services to open the SSH and Telnet Configuration screen.
NOTE: SSH and Telnet programs both provide access on a remote machine.
8 Click Enable on either SSH or Telnet as required.
9 Click Apply.
NOTE: SSH is a recommended method due to better security and
encryption mechanisms.

NOTE: SSH/Telnet session duration can be infinite as long as the timeout
value is set to 0. The default timeout value is 1800 seconds.

10 Enable iDRAC6 Out-of-Band interface (IPMI over LAN) by selecting
System→ Remote Access→ iDRAC→ Network/Security→ Network.
11 Enable the IPMI Over LAN option under IPMI LAN Settings.
IPMI Over LAN functionality is disabled by default.
12 Click Apply.

Using Serial Over LAN (SOL)
This section provides several methods to initialize a Serial-Over-LAN session
including a Telnet program, an SSH client, IPMItool, and SOL Proxy.
The purpose of Serial Over LAN feature is to redirect the serial port of the
managed server through iDRAC6 into the console of your management station.

Model for Redirecting SOL Over Telnet or SSH
Telnet (port 23)/ SSH (port 22) client ←→ WAN connection ←→
iDRAC6 server
The IPMI-based SOL over SSH/Telnet implementation eliminates the need for
an additional utility because the serial to network translation happens within the
iDRAC. The SSH or Telnet console that you use should be able to interpret and
respond to the data arriving from the managed server's serial port. The serial port
usually attaches to a shell that emulates an ANSI- or VT100- terminal. The serial
console is automatically redirected to your SSH or Telnet console. The SOL
redirection can then be started from the /system/soll target.
See "Installing Telnet or SSH Clients" for more information about using
Telnet and SSH clients with iDRAC.
Configuring and Using Serial Over LAN

167

Model for the SOL Proxy
Telnet Client (port 623) ←→ WAN connection ←→ SOL Proxy ←→
iDRAC6 server
When the SOL Proxy communicates with the Telnet client on a management
station, it uses the TCP/IP protocol. However, SOL proxy communicates with
the managed server's iDRAC6 over the RMCP/IPMI/SOL protocol, which is a
UDP-based protocol. Therefore if you communicate with your managed
system's iDRAC6 from SOL Proxy over a WAN connection, you may
experience network performance issues. The recommended usage model is to
have the SOL Proxy and the iDRAC6 server on the same LAN. The
management station with the Telnet client can then connect to the SOL
Proxy over a WAN connection. In this usage model, SOL Proxy will function
as desired.

Model for Redirecting SOL Over IPMItool
IPMItool ←→ WAN connection ←→ iDRAC6 server
The IPMI-based SOL utility, IPMItool, uses RMCP+ protocol delivered
using UDP datagrams to port 623. iDRAC6 requires this RMCP+ connection
to be encrypted. The encryption key (KG key) must contains characters of
zero or NULL that can be configured in the iDRAC6 Web GUI or in the
iDRAC6 Configuration Utility. You can also wipe out the encryption key by
pressing the backspace key so that iDRAC6 will provide NULL characters as
the encryption key by default. The advantage of using RMCP+ is improved
authentication, data integrity checks, encryption, and the ability to carry
multiple types of payloads. See "Using SOL over IPMItool" or the IPMItool
website for more information: http://ipmitool.sourceforge.net/
manpage.html.

Disconnecting SOL session in SM-CLP
When using SSH or Telnet protocols to access the Serial Over LAN
functionality, you first will be first connecting into the iDRAC’s SM-CLP
service, from which you will launch the SOL session with an SM-CLP
command (start /system1/sol1). Thus, users wanting to disconnect
an SOL session must first terminate the SOL session from SM-CLP.
Commands to disconnect a SOL session are utility oriented. Read this section
carefully. Only when a SOL session is terminated fully can you exit the utility.

168

Configuring and Using Serial Over LAN

When you are ready to quit SOL redirection from SM-CLP, press ,
, and then (press the keys in sequence, one after the other).
The SOL session will close.
NOTE: If a SOL session is not closed successfully in the utility, more SOL sessions
may not be available. The way to resolve this situation is to delete the SMASH
console in the Web GUI under System→Remote Access→iDRAC→ Network/
Security→Sessions.

Using SOL over PuTTY
To start SOL from PuTTY on a Windows management station, follow
these steps:
NOTE: If required, you can change the default SSH/telnet timeout at System→
Remote Access→ iDRAC → Network/Security → Services.
1 Connect to iDRAC6 with the following command in the command
prompt:
putty.exe [-ssh | -telnet] @
NOTE: The port number is optional. It is required only when the port number is
reassigned.

2 Enter the following command in the SM-CLP prompt to start SOL:
start /system1/sol1
NOTE: This connects you to the managed server's serial port. The SM-CLP
commands are no longer available to you. You cannot return to SM-CLP once
you have started SOL. You must quit the SOL session using the command
sequence detailed in "Disconnecting SOL session in SM-CLP," and start a new
one to use SM-CLP.

Configuring and Using Serial Over LAN

169

Using SOL over Telnet with Linux
To start SOL from Telnet on a Linux management station, follow these steps:
NOTE: If required, you can change the default Telnet timeout at System→ Remote
Access→ iDRAC→ Network/Security→ Services.
1 Start a shell.
2 Connect to iDRAC6 with the following command:
telnet
NOTE: If you have changed the port number for the Telnet service from the
default (port 23), add the port number to the end of the telnet command.

3 Input iDRAC's username and password in order to connect to iDRAC6
SM-CLP.
4 Enter the following command in the SM-CLP prompt to start SOL:
start /system1/sol1
5 To quit a SOL session from Telnet on Linux, press +] (hold down
the control key, press the right-square-bracket key, and then release).
A telnet prompt displays. Enter quit to exit telnet.

Using SOL over OpenSSH with Linux
OpenSSH is an open source utility for using the SSH protocol. To start SOL
from OpenSSH on a Linux management station, follow these steps:
NOTE: If required, you can change the default SSH session timeout at System→
Remote Access→ iDRAC→ Network/Security→ Services.
1 Start a shell.
2 Connect to iDRAC6 with the following command:
ssh -l
3 Enter the following command in the SM-CLP prompt to start SOL:
start /system1/sol1
NOTE: This connects you to the managed server's serial port. The SM-CLP
commands are no longer available to you. You cannot return to SM-CLP once
you have started SOL. You must quit the SOL session (refer to "Disconnecting
SOL session in SM-CLP" to close an active SOL session), and start a new one
to use SM-CLP.

170

Configuring and Using Serial Over LAN

Using SOL over IPMItool
The Dell Systems Management Tools and Documentation DVD provides
IPMItool, which can be installed on various operating systems. To start SOL
with IPMItool on a management station, follow these steps:
NOTE: If required, you can change the default SOL timeout at System→ Remote
Access→ iDRAC→ Network/Security→ Services.
1 Locate IPMItool.exe under the proper directory.
The default path in Windows is C:\Program Files\Dell\SysMgt\bmc.
2 Ensure the Encryption Key is all zeroes at System→ Remote Access→
iDRAC→ Network/Security→ Network→ IPMI LAN Settings.
3 Enter the following command in the Windows command prompt or in the
Linux shell prompt to start SOL from iDRAC:
ipmitool -H -I lanplus -U
-P sol activate
This connects you to the managed server's serial port.
4 To quit a SOL session from IPMItool, press <~> and <.> (press the tilde
and period keys in sequence, one after the other). The SOL session will close.
NOTE: If a user does not terminate the SOL session correctly, enter the
following command to reboot iDRAC. Allow iDRAC6 1-2 minutes to complete
booting. See "RACADM Subcommand Overview" for more details.

racadm racreset

Opening SOL with SOL proxy
Serial-Over-LAN Proxy (SOL Proxy) is a telnet daemon that allows
LAN-based administration of remote systems using the Serial over LAN
(SOL) and IPMI protocols. Any standard telnet client application, such as
HyperTerminal on Microsoft Windows or telnet on Linux, can be used to
access the daemon's features. SOL can be used either in the menu mode or
command mode. The SOL protocol coupled with the remote system's BIOS
console redirection allows administrators to remotely view and change a
managed system's BIOS settings over a LAN. The Linux serial console and
Microsoft's EMS/SAC interfaces can also be accessed over a LAN using SOL.

Configuring and Using Serial Over LAN

171

NOTE: All versions of the Windows operating system include HyperTerminal
terminal emulation software. However, the included version does not provide many
functions required during console redirection. Instead, you can use any terminal
emulation software that supports VT100 or ANSI emulation mode. One example of a
full VT100 or ANSI terminal emulator that supports console redirection on your
system is HyperTerminal Private Edition 6.1 or later.
NOTE: See your system's User's Guide for more information about console
redirection, including hardware and software requirements and instructions for
configuring host and client systems to use console redirection.
NOTE: HyperTerminal and telnet settings must be consistent with the settings on the
managed system. For example, the baud rates and terminal modes should match.
NOTE: The Windows telnet command that is run from a MS-DOS® prompt
supports ANSI terminal emulation, and the BIOS needs to be set for ANSI emulation
to display all the screens correctly.

Before Using SOL proxy

Before using SOL proxy, see the Baseboard Management Controller Utilities
User's Guide to learn how to configure your management stations before
using SOL proxy. By default, BMC Management Utility is installed in the
following directory on Windows operating systems:
C:\Program Files\Dell\SysMgt\bmc
The installation program copies the files to the following locations on Linux
Enterprise Operating Systems:
/etc/init.d/SOLPROXY.cfg
/etc/SOLPROXY.cfg
/usr/sbin/dsm_bmu_solproxy32d
/usr/sbin/solconfig
/usr/sbin/ipmish

172

Configuring and Using Serial Over LAN

Initiating the SOL Proxy session
For Windows 2003

To start the SOL Proxy service on Windows system after installation, you can
reboot the system (SOL Proxy automatically starts on a reboot). Or, you can
start the SOL Proxy service manually by completing the following steps:
1 Right-click My Computer and click Manage.
The Computer Management window is displayed.
2 Click Services and Applications and then click Services.
Available services are displayed to the right.
3 Locate DSM_BMU_SOLProxy in the list of services and right-click to
start the service.
Depending on the console you use, there are different steps for accessing SOL
Proxy. Throughout this section, the management station where the SOL
Proxy is running is referred as the SOL Proxy Server.
For Linux

The SOL Proxy will start automatically during system startup. Alternatively,
you can go to directory /etc/init.d and use the following commands to
manage the SOL Proxy service:
solproxy status
dsm_bmu_solproxy32d start
dsm_bmu_solproxy32d stop
solproxy restart

Configuring and Using Serial Over LAN

173

Using Telnet with SOL Proxy

This assumes that the SOL Proxy service is already up and running on the
management station.
For Windows 2003:

1 Open a Command Prompt window on your management station.
2 Enter the telnet command in the command-line and provide
localhost as the IP address if the SOL Proxy server is running in the
same machine and the port number that you specified in the SOL Proxy
installation (the default value is 623). For example:
telnet localhost 623
For Linux:

1 Open a Linux shell on your management station.
2 Enter the telnet command and provide localhost as the IP address
of the SOL Proxy server and the port number that you specified in the
SOL Proxy installation (the default value is 623). For example:
telnet localhost 623
NOTE: Whether your host operating system is Windows or Linux, if the SOL Proxy
server is running on a different machine than your management station, input SOL
Proxy server IP address instead of localhost.
telnet 623
Using HyperTerminal with SOL Proxy

1 From the remote station, open HyperTerminal.exe.
2 Choose TCPIP(Winsock).
3 Enter host address localhost and port number 623.
Connecting to the Remote Managed System's BMC

After a SOL Proxy session is established successfully, you are presented with
the following choices:
1. Connect to the Remote Server's BMC
2. Configure the Serial-Over-LAN for the Remote
Server
174

Configuring and Using Serial Over LAN

3. Activate Console Redirection
4. Reboot and Activate Console Redirection
5. Help
6. Exit
NOTE: While multiple SOL sessions can be active at the same time, only one
console redirection session can be active at any given time for a managed system.
NOTE: To exit an active SOL session, use the <~><.> character sequence.
This sequence terminates SOL and returns you to the top-level menu.
1 Select option 1 in the main menu.
2 Enter the iDRAC IP Address of the remote managed system.
3 Provide the iDRAC6 Username and Password for iDRAC6 on the managed
system. The iDRAC6 username and password must be assigned and stored
in the iDRAC6 non-volatile storage.
NOTE: Only one SOL console redirection session with iDRAC6 is permitted at
one time.

NOTE: If required, extend SOL session duration to infinite by changing the
Telnet timeout value to zero in the iDRAC6 Web GUI under System→ Remote
Access→ iDRAC→ Network/Security→ Services.

4 Provide the IPMI encryption key if it was configured in the iDRAC.
NOTE: You can locate the IPMI encryption key in the iDRAC6 GUI on
System→ Remote Access→ iDRAC→ Network/Security→ Network→ IPMI
LAN Settings→ Encryption Key.

NOTE: The default IPMI encryption key is all zeros. If you press for
the encryption option, iDRAC6 will use this default encryption key.

Configuring and Using Serial Over LAN

175

5 Select Configure the Serial-Over-LAN for the Remote Server (option 2)
in the main menu.
The SOL configuration menu appears. According to the current SOL
status, the content of the SOL configuration menu varies:
•

If SOL is already enabled, the current settings are displayed and you
are presented with three choices:
1. Disable Serial-Over-LAN
2. Change Serial-Over-LAN settings
3. Cancel

•

If SOL is enabled, ensure that the SOL baud rate is consistent with
the iDRAC's and the minimum iDRAC6 user privilege level of
administrator is required for activating console redirection.

•

If SOL is currently disabled, enter Y to enable SOL or N to keep
SOL disabled.

6 Select Activate Console Redirection (option 3) in the main menu
The remote managed system's text console is redirected to your
management station.
7 Select Reboot and Activate Console Redirection (option 4) in the main
menu (optional).
The power state of the remote managed system is confirmed. If power is
on, you are asked to decide between a graceful or forceful shutdown.
The power state is monitored until the state changes to On. Console
redirection begins, and the remote managed system text console is
redirected to your management station.
While the managed system reboots, you can enter BIOS system setup
program to view or configure BIOS settings.
8 Select Help (option 5) in the main menu to display a detailed description
for each option.
9 Select Exit (option 6) in the main menu to end your telnet session and
disconnect from SOL Proxy.
NOTE: If a user does not terminate the SOL session correctly, issue the
following command to reboot iDRAC. Allow iDRAC6 1-2 minutes to complete
booting. Refer to "RACADM Subcommand Overview" for more details.

racadm racreset
176

Configuring and Using Serial Over LAN

Operating System Configuration
Complete the steps below to configure generic Unix-like operating systems.
This configuration is based on default installations of Red Hat Enterprise Linux
5.0, SUSE Linux Enterprise Server 10 SP1, and Windows 2003 Enterprise.

Linux Enterprise Operating System
1 Edit the /etc/inittab file to enable hardware flow control and to allow users
to log in through the SOL console. Add the line below to the end of #Run
gettys in standard runlevels section.
7:2345:respawn:/sbin/agetty -h 115200 ttyS0 vt220
Example of original /etc/inittab:
______________________________________________________________
#
# inittab

This file describes how the INIT process should set up

the system in a certain run-level.

#
SKIP this part of file
# Run gettys in standard runlevels
1:2345:respawn:/sbin/migetty tty1
2:2345:respawn:/sbin/migetty tty1
3:2345:respawn:/sbin/migetty tty1
4:2345:respawn:/sbin/migetty tty1
5:2345:respawn:/sbin/migetty tty1
6:2345:respawn:/sbin/migetty tty1
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon

______________________________________________________________

Configuring and Using Serial Over LAN

177

Example of modified /etc/inittab:
______________________________________________________________
#
# inittab

This file describes how the INIT process should set up

the system in a certain run-level.

#
SKIP this part of file
# Run gettys in standard runlevels
1:2345:respawn:/sbin/migetty tty1
2:2345:respawn:/sbin/migetty tty1
3:2345:respawn:/sbin/migetty tty1
4:2345:respawn:/sbin/migetty tty1
5:2345:respawn:/sbin/migetty tty1
6:2345:respawn:/sbin/migetty tty1
7:2345:respawn:/sbin/agetty -h ttyS0 115200 vt220
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon

______________________________________________________________
2 Edit the /etc/securetty file to allow users to log in as root user through
the SOL console. Add the following line after console:
ttyS0

Example of original /etc/securetty:
______________________________________________________________
console
vc/1
vc/2
vc/3
vc/4

SKIP the rest of file

______________________________________________________________
178

Configuring and Using Serial Over LAN

Example of modified /etc/securetty:
______________________________________________________________
Console
ttyS0
vc/1
vc/2
vc/3
vc/4
SKIP the rest of file

______________________________________________________________
3 Edit the /boot/grub/grub.conf or /boot/grub/menu.list file to add boot
options for SOL:
a

Comment out the graphical display lines in the various Unix-like
operating systems:
•

splashimage=(had0,0)/grub/splash.xpm.gz in
RHEL 5

•

gfxmenu (hda0,5)/boot/message in SLES 10

Add the following line before the first title= … line:

# Redirect OS boot via SOL
c

Append the following entry to the first title= … line:

SOL redirection
d

Append the following text to the kernel/… line of the first title=
…:

console=tty1 console=ttyS0,115200
NOTE: /boot/grub/grub.conf in Red Hat Enterprise Linux 5 is a symbolic link to /
boot/grub/menu.list. You can change the settings in either one of them.

Configuring and Using Serial Over LAN

179

Example of original /boot/grub/grub.conf in RHEL 5:
______________________________________________________________
# grub.conf generated by anaconda
#
# Note that you do not have to return grub after making changes
to this
# file
# NOTICE: You have a /boot partition. This means that
#
eg.

all kernel and initrd paths are relative to /boot/,

root (hd0,0)

#
LogVol00

kernel /vmlinux-version ro root=/dev/VolGroup00/

initrd /initrd-version.img

#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm/gz
hiddenmenu
title Red Hat Enterprise Linux 5
root (hd0,0)
kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/
LogVol00 rhgb quiet
initrd /initrd-2.6.18-8.el5.img

______________________________________________________________
Example of modified /boot/grub/grub.conf:
______________________________________________________________
# grub.conf generated by anaconda
#
# Note that you do not have to return grub after making changes
to this
# file
# NOTICE: You have a /boot partition. This means that

180

Configuring and Using Serial Over LAN

#
eg.

all kernel and initrd paths are relative to /boot/,

root (hd0,0)

#
LogVol00

kernel /vmlinux-version ro root=/dev/VolGroup00/

initrd /initrd-version.img

#boot=/dev/sda
default=0
timeout=5
#splashimage=(hd0,0)/grub/splash.xpm/gz
hiddenmenu
# Redirect the OS boot via SOL
title Red Hat Enterprise Linux 5 SOL redirection
root (hd0,0)
kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/
LogVol00 rhgb quiet console=tty1 console=ttyS0,115200
initrd /initrd-2.6.18-8.el5.img

______________________________________________________________
Example of original /boot/grub/menu.list in SLES 10:
______________________________________________________________
#Modified by YaST2. Last modification on Sat Oct 11 21:52:09
UTC 2008
Default 0
Timeout 8
gfxmenu (hd0.5)/boot/message
###Don't change this comment - YaST2 identifier: Original name:
linux###
title SUSE Linux Enterprise Server 10 SP1
root (hd0,5)
kernel /boot/vmlinux-2.6.16-46-0.12-bigsmp root=/dev/disk/
by-id/scsi-35000c5000155c resume=/dev/sda5 splash=silent
showopts
initrd /boot/initrd-2.6.16.46-0.12-bigsmp

______________________________________________________________
Configuring and Using Serial Over LAN

181

Example of modified /boot/grub/menu.list in SLES 10:
______________________________________________________________
#Modified by YaST2. Last modification on Sat Oct 11 21:52:09
UTC 2008
Default 0
Timeout 8
#gfxmenu (hd0.5)/boot/message
###Don't change this comment - YaST2 identifier: Original name:
linux###
title SUSE Linux Enterprise Server 10 SP1 SOL redirection
root (hd0,5)
kernel /boot/vmlinux-2.6.16-46-0.12-bigsmp root=/dev/disk/
by-id/scsi-35000c5000155c resume=/dev/sda5 splash=silent
showopts console=tty1 console=ttyS0,115200
initrd /boot/initrd-2.6.16.46-0.12-bigsmp

______________________________________________________________

Windows 2003 Enterprise
1 Find out the boot entry ID by entering bootcfg in the Windows
command prompt. Locate the boot entry ID for the section with the OSfriendly name Windows Server 2003 Enterprise. Press to display
the boot options on the management station.
2 Enable EMS at a Windows command prompt by entering:
bootcfg /EMS ON /PORT COM1 /BAUD 115200 /ID
NOTE: is the boot entry ID from step 1.
3 Press to verify that the EMS console setting takes effect.

182

Configuring and Using Serial Over LAN

Example of original bootcfg setting:
______________________________________________________________
Boot Loader Settings
-------------------timeout:30
default:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
Boot Entries
-----------Boot entry ID:

Os Friendly Name: Winodws Server 2003, Enterprise
Path:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

OS Load Options:
redirect

/nonexecute=optout /fastdetect /usepmtimer /

______________________________________________________________
Example of modified bootcfg setting:
______________________________________________________________
Boot Loader Settings
-------------------timeout:

default:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

redirect:

COM1

redirectbaudrate:115200
Boot Entries
-----------Boot entry ID:

Os Friendly Name: Windows Server 2003, Enterprise
Path:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

OS Load Options:
redirect

/nonexecute=optout /fastdetect /usepmtimer /

______________________________________________________________

Configuring and Using Serial Over LAN

183

184

Configuring and Using Serial Over LAN

Using GUI Console Redirection
This section provides information about using the iDRAC6 console
redirection feature.

Overview
The iDRAC6 console redirection feature enables you to remotely access local
consoles in graphic or text mode, allowing you to control one or more
iDRAC6-enabled systems from a single location.

Using Console Redirection
NOTE: When you open a console redirection session, the managed server does not
indicate that the console has been redirected.
The Console Redirection screen enables you to manage the remote system by
using the keyboard, video, and mouse on your local management station to
control the corresponding devices on a remote managed server. This feature
can be used in conjunction with the Virtual Media feature to perform remote
software installations.
The following rules apply to a console redirection session:
•

A maximum of two simultaneous console redirection sessions are supported.
Both sessions view the same managed server console simultaneously.

•

A console redirection session should not be launched from a Web browser
on the managed system.

•

A minimum available network bandwidth of 1 MB/sec is required.

If a second user requests a console redirection session, the first user is notified
and is given the option to refuse access, allow only video, or allow full shared
access. The second user is notified that another user has control. The first
user must respond within thirty seconds or full access is automatically granted
to the second user. During the time that two sessions are concurrently active,
Using GUI Console Redirection

185

each user sees a message in the upper-right corner of the screen that identifies
the other user with an active session. A third active session is not permitted.
If a third user requests a console redirection session, access is denied without
interruption to the first or second user’s session.
If the neither the first or second user has administrator privileges, termination
of the first user's active session automatically results in termination of the
second user's session.

Supported Screen Resolutions and Refresh Rates
Table 10-1 lists the supported screen resolutions and corresponding refresh
rates for a console redirection session that is running on the managed server.
Table 10-1. Supported Screen Resolutions and Refresh Rates
Screen Resolution

Refresh Rate (Hz)

720x400

640x480

60, 72, 75, 85

800x600

60, 70, 72, 75, 85

1024x768

60, 70, 72, 75, 85

1280x1024

Configuring the Management Station
To use Console Redirection on the management station, perform the
following procedures:
1 Install and configure a supported Web browser. See "Supported Web
Browsers" and "Configuring a Supported Web Browser."
2 If you are using Firefox or want to use the Java Viewer with Internet
Explorer, install a Java Runtime Environment (JRE). See "Installing a Java
Runtime Environment (JRE)."
3 Dell recommends that you configure your monitor display resolution to
1280x1024 pixels.
NOTE: If you have an active console redirection session and a lower resolution
monitor is connected to the iKVM, the server console resolution may reset if the
server is selected on the local console. If the server is running a Linux operating
system, an X11 console may not be viewable on the local monitor.
Pressing at the iKVM will switch Linux to a text console.
186

Using GUI Console Redirection

Configuring Console Redirection and Virtual Media in the iDRAC6 Web
Interface
To configure console redirection in the iDRAC6 Web interface, perform the
following steps:
1 Click System and then click the Console tab.
2 Click Configuration to open the Console Redirection Configuration screen.
3 Configure the console redirection properties. Table 10-2 describes the
settings for console redirection.
4 When completed, click Apply.
5 Click the appropriate button to continue. See Table 10-3.
Table 10-2.

Console Redirection Configuration Properties

Property

Description

Enabled

Click to enable or disable Console Redirection.
Checked indicates that Console Redirection is enabled.
Unchecked indicates that Console Redirection is disabled.
The default is enabled.

Max Sessions

Displays the maximum number of Console Redirection
sessions that are possible, 1 or 2. Use the drop-down
menu to change the maximum number of Console
Redirection sessions allowed. The default is 2.

Active Sessions

Displays the number of Active Console sessions.
This field is read-only.

Keyboard and Mouse Port The network port number used for connecting to the
Number
Console Redirection Keyboard/Mouse option.
This traffic is always encrypted. You may need to change
this number if another program is using the default port.
The default is 5900.
Video Port Number

The network port number used for connecting to the
Console Redirection Screen service. You may need to
change this setting if another program is using the
default port. The default is 5901.

Using GUI Console Redirection

187

Table 10-2. Console Redirection Configuration Properties (continued)
Property

Description

Video Encryption Enabled Checked indicates that video encryption is enabled.
All traffic going to the video port is encrypted.
Unchecked indicates that video encryption is disabled.
Traffic going to the video port is not encrypted.
The default is Encrypted. Disabling encryption can
improve performance on slower networks.
Mouse Mode

Choose Windows if the managed server is running on a
Windows operating system.
Choose Linux if your server is running on Linux.
Choose No Access if your server is not running on a
Windows or Linux operating system.

NOTE: You must select No Access Mouse Mode in
HyperV, Dell Diagnostics, or USC.
The default is Windows.
Console Plug-In Type for IE When using Internet Explorer on a Windows operating
system, you can choose from the following viewers:
ActiveX - The ActiveX Console Redirection viewer
Java - Java Console Redirection viewer

NOTE: Depending on your version of Internet Explorer,
additional security restrictions may need to be turned off
(see "Configuring and Using Virtual Media").

NOTE: You must have the Java runtime environment
installed on your client system to use the Java viewer.
Local Server Video
Enabled

Checked indicates that output to the iKVM monitor is
enabled during console redirection. Unchecked
indicates that the tasks you perform using Console
Redirection will not be visible on the managed server’s
local monitor.

NOTE: For information about using Virtual Media with Console Redirection, see
"Configuring and Using Virtual Media."

188

Using GUI Console Redirection

The buttons in Table 10-5 are available on the Console Redirection
Configuration screen.
Table 10-3.

Console Redirection Configuration Buttons

Button

Definition

Prints the Console Redirection Configuration screen

Refresh

Reloads the Console Redirection Configuration screen

Apply

Saves any new settings made to the console redirection

Opening a Console Redirection Session
When you open a console redirection session, the Dell Virtual KVM Viewer
Application starts and the remote system’s desktop appears in the viewer.
Using the Virtual KVM Viewer Application, you can control the remote
system’s mouse and keyboard functions from your local management station.
To open a console redirection session in the Web interface, perform the
following steps:
1 Click System and then click the Console tab.
2 In the Console Redirection screen, use the information in Table 10-4 to
ensure that a console redirection session is available.
If you wish to reconfigure any of the property values displayed,
see "Configuring Console Redirection and Virtual Media in the iDRAC6
Web Interface."
Table 10-4.

Console Redirection Information

Property

Description

Console Redirection
Enabled

Yes/No

Video Encryption Enabled Yes/No
Max Sessions

Displays the maximum number of supported Console
Redirection sessions.

Current Sessions

Displays the current number of active console
redirection sessions.

Using GUI Console Redirection

189

Table 10-4. Console Redirection Information (continued)
Property

Description

Mouse Mode

Displays the mouse acceleration currently in effect.
Mouse Acceleration mode should be chosen based on
the type of operating system installed on the managed
server.

Console Plug-in Type

Shows the plug-in type currently configured.
ActiveX — An Active-X viewer will be launched.
Active-X viewer will only work on Internet Explorer
while running on a Windows Operating System.
Java — A Java viewer will be launched. The Java viewer
can be used on any browser including Internet Explorer.
If your client runs on an operating system other than
Windows, then you must use the Java Viewer. If you are
accessing iDRAC6 using Internet Explorer while
running on a Windows operating system, you may
choose either Active-X or Java as the plug-in type.

Local Server Video
Enabled

Checked indicates that output to the iKVM monitor is
enabled during console redirection. Unchecked ensures
that the tasks you perform using Console Redirection
will not be visible on the managed server’s local monitor.

NOTE: For information about using Virtual Media with Console Redirection,
see "Configuring and Using Virtual Media."
The buttons in Table 10-5 are available on the Console Redirection screen.
Table 10-5. Console Redirection Buttons
Button

Definition

Refresh

Reloads the Console Redirection Configuration screen

Launch Viewer

Opens a console redirection session on the targeted
remote system

Prints the Console Redirection Configuration screen

190

Using GUI Console Redirection

3 If a console redirection session is available, click Launch Viewer.
NOTE: Multiple message boxes may appear after you launch the application.
To prevent unauthorized access to the application, you must navigate through
these message boxes within three minutes. Otherwise, you will be prompted
to relaunch the application.

NOTE: If one or more Security Alert windows appear in the following steps,
read the information in the window and click Yes to continue.

The management station connects to iDRAC6 and the remote system’s
desktop appears in the Dell Digital KVM Viewer Application.
4 Two mouse pointers appear in the viewer window: one for the remote
system and one for your local system. You must synchronize the two mouse
pointers so that the remote mouse pointer follows your local mouse
pointer. See "Synchronizing the Mouse Pointers."

Using the Video Viewer
The Video Viewer provides a user interface between the management station
and the managed server, allowing you to see the managed server’s desktop and
control its mouse and keyboard functions from your management station.
When you connect to the remote system, the Video Viewer starts in a
separate window.
The Video Viewer provides various control adjustments such as color mode,
mouse synchronization, snapshots, keyboard macros, and access to Virtual
Media. Click Help for more information on these functions.
When you start a console redirection session and the Video Viewer appears,
you may need to adjust the color mode and synchronize the mouse pointers.
Table 10-6 describes the menu options that are available for use in the viewer.

Using GUI Console Redirection

191

Table 10-6. Viewer Menu Bar Selections
Menu Item

Item

Description

Video

Pause

Temporarily pauses console redirection.

Resume

Resumes console redirection.

Refresh

Redraws the viewer screen image.

Capture
Captures the current remote system screen to a .bmp
Current Screen file on Windows or a .png file on Linux. A dialog box
is displayed that allows you to save the file to a
specified location.

Keyboard

Full Screen

To make the Video Viewer expand into full screen
mode, select Full Screen from the Video menu.

Exit

When you have finished using the Console and have
logged out (using the remote system's logout
procedure), select Exit from the Video menu to close
the Video Viewer window.

Hold Right Alt Select this item before typing keys you want to
Key
combine with the right key.
Hold Left Alt
Key

Select this item before typing keys you want to
combine with the left key.

Left Windows
Key

Select Hold Down before typing characters you want
to combine with the left Windows key. Select Press
and Release to send a left Windows key keystroke.

Right Windows Select Hold Down before typing characters you want
Key
to combine with the right Windows key. Select Press
and Release to send a right Windows key keystroke.

192

Using GUI Console Redirection

Table 10-6.
Menu Item

Viewer Menu Bar Selections (continued)
Item

Description

Macros

When you select a macro, or enter the hotkey
specified for the macro, the action is executed on the
remote system. The Video Viewer provides the
following macros:
• Ctrl-Alt-Del
• Alt-Tab
• Alt-Esc
• Ctrl-Esc
• Alt-Space
• Alt-Enter
• Alt-Hyphen
• Alt-F4
• PrtScn
• Alt-PrtScn
• F1
• Pause
• Alt+m

Mouse

Options

Keyboard
Pass-through

The Keyboard pass-through mode allows all keyboard
functions on the client to be redirected to the server.

Synchronize
Cursor

Synchronizes the cursor so that the mouse on the
client is redirected to the mouse on the server.

Hide Local
Cursor

Only the cursor from the KVM will be displayed.
Dell recommends this setting when running USC in
a vKVM.

Color Mode

Allows you to select a color depth to improve
performance over the network. For example, if you are
installing software from virtual media, you can choose
the lowest color depth (3-bit gray), so that less network
bandwidth is used by the console viewer leaving more
bandwidth for transferring data from the media.
The color mode can be set to 15-bit color, 7-bit color,
4-bit color, 4-bit gray, and 3-bit gray.

Using GUI Console Redirection

193

Table 10-6. Viewer Menu Bar Selections (continued)
Menu Item

Item

Description

Media

Virtual Media
Wizard

The Media menu provides access to the Virtual
Media Wizard, which allows you to redirect to a
device or image such as a:
• Floppy drive
• CD
• DVD
• Image in ISO format
• USB Flash drive
For information about the Virtual Media feature,
see "Configuring and Using Virtual Media."
You must keep the Console Viewer window active
when using Virtual Media.

Help

N/A

Activates the Help menu.

Synchronizing the Mouse Pointers
When you connect to a remote PowerEdge system using Console
Redirection, the mouse acceleration speed on the remote system may not
synchronize with the mouse pointer on your management station, causing
two mouse pointers to appear in the Video Viewer window.
To synchronize the mouse pointers click Mouse→ Synchronize cursor or
press .
The Synchronize cursor menu item is a toggle. Ensure that there is a check
mark next to the item in the menu so that the mouse synchronization is active.
When using Red Hat Enterprise Linux or Novell SUSE Linux, be sure to
configure the mouse mode for Linux before you launch the viewer. See
"Configuring Console Redirection and Virtual Media in the iDRAC6 Web
Interface" for help with configuration. The operating system’s default mouse
settings are used to control the mouse arrow in the iDRAC6 Console
Redirection screen.

194

Using GUI Console Redirection

Disabling or Enabling Local Console
You can configure iDRAC6 to disallow iKVM connections using the iDRAC6
Web interface. When the local console is disabled, a yellow status dot appears
in the list of servers (OSCAR) to indicate that the console is locked in
iDRAC6. When the local console is enabled, the status dot is green.
If you want to ensure that you have exclusive access to the managed server
console, you must disable the local console and reconfigure the Max Sessions
to 1 on the Console Redirection screen.
NOTE: The local console feature is supported on all x9xx PowerEdge systems
except PowerEdge SC1435 and 6950.
NOTE: By disabling (turning off) the local video on the server, the monitor,
keyboard, and mouse connected to the iKVM are disabled.
To disable or enable the local console, perform the following procedure:
1 On your management station, open a supported Web browser and log in to
iDRAC6. See "Accessing the Web Interface" for more information.
2 Click System, click the Console tab, and then click Configuration.
3 If you want to disable (turn off) local video on the server, in the Console
Redirect Configuration screen, uncheck Local Server Video Enabled and
then click Apply. The default value is Enabled (checked).
4 If you want to enable (turn on) local video on the server, in the Console
Redirect Configuration screen, check Local Server Video Enabled and
then click Apply.
The Console Redirection screen displays the status of the Local Server Video.

Using GUI Console Redirection

195

Frequently Asked Questions
Table 10-7 lists frequently asked questions and answers.
Table 10-7. Using Console Redirection: Frequently Asked Questions
Question

Answer

Can a new remote
console video session
be started when the
local video on the
server is turned off?

Yes.

Why does it take
It gives a local user an opportunity to take any action before
15 seconds to turn off the video is switched off.
the local video on the
server after requesting
to turn off the local
video?
Is there a time delay
when turning on the
local video?

No, once a local video turn ON request is received by
iDRAC6 the video is turned on instantly.

Can the local user also Yes, a local user can use the local RACADM CLI to turn off
turn off the video?
the video.
Can the local user also No. Once the local console is disabled, the local user’s
turn on the video?
keyboard and mouse are disabled and they are unable to
change any settings.
Does switching off the Yes.
local video also switch
off the local keyboard
and mouse?
Does turning off the
local console turn off
the video on the
remote console
session?

196

No, turning the local video on or off is independent of the
remote console session.

Using GUI Console Redirection

Table 10-7.

Using Console Redirection: Frequently Asked Questions (continued)

Question

Answer

What privileges are
Any user with iDRAC6 configuration privileges can turn the
needed for an iDRAC6 local console on or off.
user to turn on or off
the local server video?
How can I get the
current status of the
local server video?

The status is displayed on the Console Redirection
Configuration screen of the iDRAC6 Web interface.
The RACADM CLI command racadm getconfig –g
cfgRacTuning displays the status in the object
cfgRacTuneLocalServerVideo.
The status is also seen on the iKVM OSCAR display. When
the local console is enabled, a green status appears next to
the server name. When disabled, a yellow dot indicates that
the local console is locked by iDRAC6.

I cannot see the
bottom of the system
screen from the
Console Redirection
window.

Ensure that the management station’s monitor resolution is
set to 1280x1024.

The console window is The console viewer on Linux requires a UTF-8 character set.
garbled.
Check your locale and reset the character set if needed.
See "Setting the Locale in Linux" for more information.
Why do I get a blank
screen on the
managed server when
loading the
Windows 2000
operating system?

The managed server does not have the correct ATI video
driver. You must update the video driver by using the
Dell PowerEdge Installation and Server Management CD.

Using GUI Console Redirection

197

Table 10-7. Using Console Redirection: Frequently Asked Questions (continued)
Question

Answer

Why doesn’t the
mouse sync in DOS
when performing
Console Redirection?

The Dell BIOS is emulating the mouse driver as a PS/2
mouse. By design, the PS/2 mouse uses relative position for
the mouse pointer, which causes the lag in syncing. iDRAC6
has a USB mouse driver, which allows absolute position and
closer tracking of the mouse pointer. Even if iDRAC6 passes
the USB absolute mouse position to the Dell BIOS, the BIOS
emulation would convert it back to relative position and the
behavior would remain. To fix this problem, set the mouse
mode to No Access in the Console Redirection
configuration.

Why doesn’t the
Virtual KVM requires the USB mouse driver, but the USB
mouse sync under the mouse driver is available only under the X-Window operating
Linux text console?
system.
I am still having issues Ensure that the correct mouse is selected for your operating
with mouse
system before starting a console redirection session.
synchronization.
Ensure that Synchronize Mouse is checked in the Mouse
menu. Press or select Mouse→ Synchronize
mouse to toggle mouse synchronization. When
synchronization is enabled, a check mark appears next to the
selection in the Mouse menu.
Why can't I use a
keyboard or mouse
while installing a
Microsoft® operating
system remotely by
using iDRAC6
Console Redirection?

When you remotely install a supported Microsoft operating
system on a system with Console Redirection enabled in the
BIOS, you receive an EMS Connection Message that requires
that you select OK before you can continue. You cannot use
the mouse to select OK remotely. You must either select OK
on the local system or restart the remotely managed server,
reinstall, and then turn Console Redirection off in the BIOS.
This message is generated by Microsoft to alert the user that
Console Redirection is enabled. To ensure that this message
does not appear, always turn off Console Redirection in the
BIOS before installing an operating system remotely.

198

Using GUI Console Redirection

Table 10-7.

Using Console Redirection: Frequently Asked Questions (continued)

Question

Answer

Why doesn’t the Num
Lock indicator on my
management station
reflect the status of
the Num Lock on the
remote server?

When accessed through iDRAC6, the Num Lock indicator
on the management station does not necessarily coincide
with the state of the Num Lock on the remote server. The
state of the Num Lock is dependent on the setting on the
remote server when the remote session is connected,
regardless of the state of the Num Lock on the management
station.

Why do multiple
You are configuring a console redirection session from the
Session Viewer
local system. This is not supported.
windows appear when
I establish a console
redirection session
from the local host?
If I am running a
No. If a local user accesses the system, you both have control
console redirection
of the system.
session and a local user
accesses the managed
server, do I receive a
warning message?
How much bandwidth Dell recommends a 5 MB/sec connection for good
do I need to run a
performance. A 1 MB/sec connection is required for minimal
console redirection
performance.
session?
What are the
minimum system
requirements for my
management station
to run console
redirection?

The management station requires an Intel Pentium III
500 MHz processor with at least 256 MB of RAM.

Using GUI Console Redirection

199

200

Using GUI Console Redirection

Configuring a VFlash Media Card for
Use With iDRAC6
The VFlash media card is a Secure Digital (SD) card that plugs into the
optional iDRAC6 Enterprise card slot at the back corner of the system.
It provides storage space that behaves like a common USB Flash Key device.

Installing a VFlash Media Card
NOTE: Dell-branded vFlash media is required for the virtual flash partition.
1 Remove the blade from the chassis.
2 Locate the VFlash media slot at the back corner of the system.
NOTE: You do not need to remove the blade cover to install or remove
the card.

Configuring a VFlash Media Card for Use With iDRAC6

201

3 With the label side facing up, insert the contact-pin end of the SD card
into the card slot on the module.
NOTE: The slot is keyed to ensure correct insertion of the card.
4 Press inward on the card to lock it into the slot.
5 Place the blade back in the chassis.

Removing a VFlash Media Card
To remove the VFlash media, push inward on the card to release it, and pull
the card from the card slot.

Configuring the VFlash Media Card Using the
iDRAC6 Web Interface
Enabling or Disabling the VFlash Media Card
NOTE: The VFlash Enable check box is active only if a VFlash card is present.
If card is not present, the following message displays:
SD Card not inserted. Please insert an SD card of
size greater than 256MB.
1 Ensure that the VFlash card has been installed.
2 Open a supported Web browser window.
3 Log in to the iDRAC6 Web interface.
4 In the system tree, select System.
5 Click the VFlash tab.
The VFlash screen appears.
6 Select the Enable VFlash check box to enable the VFlash Media Card.
To disable, deselect the check box.
7 Click Apply.

202

Configuring a VFlash Media Card for Use With iDRAC6

Formatting the VFlash Media Card
NOTE: The Format option is active only if a VFlash card is present.
1 Log in to the iDRAC6 Web interface.
2 In the system tree, select System.
3 Click the VFlash tab.
The VFlash screen appears.
4 Ensure that VFlash is disabled. The VFlash Enable check box should be
cleared (unchecked).
5 Click Format.
An alert box appears, warning that any existing image on the card will be
erased during formatting and requesting confirmation. Click OK to continue.
A status bar appears, indicating formatting progress.

Uploading Disk Image
1 Ensure the image file has the extension .img and that the image is not
larger than 256 MB.
NOTE: Though your VFlash card may be larger than 256 MB, only 256 MB is
accessible at this time.

2 Log in to the iDRAC6 Web interface.
3 In the system tree, select System.
4 Click the VFlash tab.
The VFlash screen appears.
5 Ensure that VFlash is disabled. The VFlash Enable check box should be
cleared (unchecked).
6 In the VFlash Drive section, enter the path to the image file or click
Browse to navigate to its location on your system.
Click Upload.
A status bar appears, indicating upload progress.

Viewing the VFlash Key Size
The Virtual Flash Key Size drop-down menu displays the current size setting.
Configuring a VFlash Media Card for Use With iDRAC6

203

Configuring the VFlash Media Card Using
RACADM
Enabling or Disabling the VFlash Media Card
Open a local console to the server, log in, and enter:
racadm cfgRacVirtual cfgVirMediaKeyEnable [ 1 or 0 ]
where 1 is enabled and 0 is disabled.
NOTE: For more information about cfgRacVirtual, including output details, see
"cfgRacVirtual."

Formatting the VFlash Media Card
Open a Telnet/SSH text console to the server, log in, and enter:
racadm vmkey reset
CAUTION: Formatting the VFlash media card deletes all existing data.
NOTE: For more information about vmkey, see "vmkey."

204

Configuring a VFlash Media Card for Use With iDRAC6

Configuring and Using Virtual Media
Overview
The Virtual Media feature, accessed through the console redirection viewer,
provides the managed server access to media connected to a remote system
on the network. Figure 12-1 shows the overall architecture of Virtual Media.
Figure 12-1.

Overall Architecture of Virtual Media

Managed Server

Management Station

Modular Server
Remote CD/DVD/USB

Network
Remote Floppy

Configuring and Using Virtual Media

205

Using Virtual Media, administrators can remotely boot their managed
servers, install applications, update drivers, or even install new operating
systems remotely from the virtual CD/DVD and diskette drives.
NOTE: Virtual media requires a minimum available network bandwidth of 128 Kbps.
Virtual media defines two devices for the managed server’s operating system
and BIOS: a floppy disk device and an optical disk device.
The management station provides the physical media or image file across the
network. When Virtual Media is connected, all virtual CD/floppy drive
access requests from the managed server are directed to the management
station across the network. Connecting Virtual Media appears the same as
inserting media into physical devices. When virtual media is not connected,
virtual devices on the managed server appear as two drives without media
installed in the drives.
Table 12-1 lists the supported drive connections for virtual floppy and virtual
optical drives.
NOTE: Changing Virtual Media while connected could stop the system
boot sequence.
Table 12-1. Supported Drive Connections
Supported Virtual Floppy Drive
Connections

Supported Virtual Optical Drive
Connections

Legacy 1.44 floppy drive with a 1.44
floppy diskette

CD-ROM, DVD, CDRW, combination
drive with CD-ROM media

USB floppy drive with a 1.44 floppy
diskette

CD-ROM/DVD image file in the ISO9660
format

1.44 floppy image

USB CD-ROM drive with CD-ROM media

USB removable disk (minimum size
128 MB)

Windows-Based Management Station
To run the Virtual Media feature on a management station running the
Windows operating system, install a supported version of Internet Explorer
with the ActiveX Control plug-in (see "Supported Web Browsers"). Set the
browser security to Medium or a lower setting to enable Internet Explorer to
download and install signed ActiveX controls.
206

Configuring and Using Virtual Media

Depending on your version of Internet Explorer, a custom security setting for
ActiveX may be required:
1 Start Internet Explorer.
2 Click Tools→ Internet Options, and then click the Security tab.
3 Under Select a Web content zone to specify its security settings, click to
select the desired zone.
4 Under Security level for this zone, click Custom Level.
The Security Settings window appears.
5 Under ActiveX controls and plugins, ensure that the following settings are
set to Enable:
•

Allow Scriptlets

•

Automatic prompting for ActiveX controls

•

Download signed ActiveX controls

•

Download unsigned ActiveX controls

6 Click OK to save any changes and close the Security Settings window.
7 Click OK to close the Internet Options window.
8 Restart Internet Explorer.
You must have administrator rights to install ActiveX. Before installing the
ActiveX control, Internet Explorer may display a security warning.
To complete the ActiveX control installation procedure, accept the ActiveX
control when Internet Explorer prompts you with a security warning.

Linux-Based Management Station
To run the virtual media feature on a management station running the Linux
operating system, install a supported version of Firefox. See "Supported Web
Browsers" for more information.
A Java Runtime Environment (JRE) is required is required to run the console
redirection plugin. You can download a JRE from java.sun.com. JRE
version 1.6 or above is recommended.

Configuring and Using Virtual Media

207

Configuring Virtual Media
1 Log in to the iDRAC6 Web interface.
2 Click the Console/Media tab.
3 Click Configuration, and then click Virtual Media.
The Console Redirection Configuration screen appears.
4 Click Virtual Media.
5 In the Virtual Media section, select values for the settings. See Table 12-2
for information on Virtual Media configuration values.
6 Click Apply to save your settings.
An alert dialog appears with the following message: You are about
to change device configuration. All existing
redirection sessions will be closed. Do you want
to continue?
7 Click OK to continue.
An alert dialog appears with the following message: Virtual Media
Configuration successfully set.
Table 12-2. Virtual Media Configuration Values
Attribute

Value

Attach Virtual Media

Attach — Immediately attaches Virtual Media to the
server.
Detach — Immediately detaches Virtual Media from
the server.
Auto-Attach — Attaches Virtual Media to the server
only when a virtual media session is started.

Maximum Sessions

Displays the maximum number of Virtual Media
sessions allowed. This value is always 1.

NOTE: Only one virtual media user session is allowed;
however, multiple devices can be attached in a single
session. See "Running Virtual Media."
Active Sessions

208

Displays the current number of Virtual Media sessions.

Configuring and Using Virtual Media

Table 12-2.

Virtual Media Configuration Values (continued)

Attribute

Value

Virtual Media Encryption
Enabled

Enables (checked) or disables (not checked)
encryption on Virtual Media connections.

Virtual Media Port Number

The network port number used for connecting to the
Virtual Media service without encryption.
Two consecutive ports starting from the port number
specified are used to connect to the Virtual Media
service. The port number following the specified port
must not be configured for any other iDRAC6 service.
The default is 3668.

Virtual Media SSL Port
Number

The network port number used for encrypted
connections to the Virtual Media service.
Two consecutive ports starting from the port number
specified are used to connect to the Virtual Media
service. The port number following the specified port
must not be configured for any other iDRAC6 service.
The default is 3670.

Floppy Emulation

Indicates whether the Virtual Media appears as a
floppy drive or as a USB key to the server. If Floppy
Emulation is checked, the Virtual Media device
appears as a floppy device on the server. If it is
unchecked, it appears as a USB Key drive.

Enable Boot Once

Enables (checked) or disables (not checked) the
boot-once option, which automatically terminates the
Virtual Media session after the server has booted once.
This option is useful for automated deployments.

Running Virtual Media
CAUTION: Do not issue a racreset command when running a Virtual Media
session. Otherwise, undesirable results may occur, including data loss.
NOTE: The Console Viewer window application must remain active while you
access the virtual media.
1 Open a supported Web browser on your management station.
2 Log in to the iDRAC6 Web interface.

Configuring and Using Virtual Media

209

3 Click the Console/Media tab.
The Console Redirection and Virtual Media screen appears.
To change the values of any of the displayed attributes, see "Configuring
Virtual Media."
NOTE: The Floppy Image File under Floppy Drive (if applicable) may appear,
as this device can be virtualized as a virtual floppy. You can select one optical
drive and one floppy at the same time, or a single drive.

NOTE: The virtual device drive letters on the managed server do not coincide
with the physical drive letters on the management station.

NOTE: Virtual Media may not function properly on Windows operating system
clients that are configured with Internet Explorer Enhanced Security.
To resolve this issue, see your Microsoft operating system documentation or
contact your administrator.

4 Click Launch Viewer.
NOTE: On Linux, the file jviewer.jnlp is downloaded to your desktop and a
dialog box will ask what to do with the file. Choose the option to Open with
program and then select the javaws application, which is located in the bin
subdirectory of your JRE installation directory.

The iDRACView application launches in a separate window.
5 Select Media → Virtual Media Wizard…
The Media Redirection Wizard appears.
6 View the Status window at the bottom of the Wizard screen. If media is
connected, you must disconnect it before connecting a different media
source. To disconnect media, click the Disconnect button next to the
media in the Status window.
7 Select the radio button next to the media types you want to connect.
You can select both the Floppy Image radio button and one of the radio
buttons in the CD/DVD Drive section.
To connect a floppy image or ISO image, enter the path to the image
location on your local computer, or click the Browse button to navigate to
the image location.

210

Configuring and Using Virtual Media

8 Click the Connect button next to each selected media type.
The media is connected and the Status window is updated.
9 Click Close.
Disconnecting Virtual Media

1 Select Media → Virtual Media Wizard…
The Media Redirection Wizard appears.
2 Click Disconnect next to the media you wish to disconnect.
The media is disconnected and the Status window is updated.
3 Click Close.

Booting From Virtual Media
The system BIOS enables you to boot from virtual optical drives or virtual
floppy drives. During POST, enter the BIOS setup window and verify that the
virtual drives are enabled and listed in the correct order.
To change the BIOS setting, perform the following steps:
1 Boot the managed server.
2 Press to enter the BIOS setup window.
3 Scroll to the boot sequence and press .
In the pop-up window, the virtual optical drives and virtual floppy drives
are listed with the standard boot devices.
4 Ensure that the virtual drive is enabled and listed as the first device with
bootable media. If required, follow the on-screen instructions to modify
the boot order.
5 Save the changes and exit.
The managed server reboots.
The managed server attempts to boot from a bootable device based on the
boot order. If the virtual device is connected and a bootable media is
present, the system boots to the virtual device. Otherwise, the system
overlooks the device—similar to a physical device without bootable media.

Configuring and Using Virtual Media

211

Installing Operating Systems Using Virtual Media
This section describes a manual, interactive method to install the operating
system on your management station that may take several hours to complete.
A scripted operating system installation procedure using Virtual Media may
take fewer than 15 minutes to complete. See "Deploying the Operating
System" for more information.
1 Verify the following:
•

The operating system installation DVD/CD is inserted in the
management station’s DVD/CD drive.

•

The local DVD/CD drive is selected.

•

You are connected to the virtual drives.

2 Follow the steps for booting from the virtual media in the "Booting From
Virtual Media" section to ensure that the BIOS is set to boot from the
DVD/CD drive from which you are installing.
3 Follow the on-screen instructions to complete the installation.

Using Virtual Media When the Server’s Operating System Is Running
Windows-Based Systems

On Windows systems, the virtual media drives are automounted if they are
attached and configured with a drive letter.
Using the virtual drives from within Windows is similar to using your physical
drives. When you connect to the media using the Virtual Media wizard,
the media is available at the system by clicking the drive and browsing
its content.
Linux-Based Systems

Depending on the configuration of the software on your system, the virtual
media drives may not be automounted. If your drives are not automounted,
manually mount the drives using the Linux mount command.

212

Configuring and Using Virtual Media

Frequently Asked Questions
Table 12-3 lists frequently asked questions and answers.
Table 12-3.

Using Virtual Media: Frequently Asked Questions

Question

Answer

Sometimes, I notice my
Virtual Media client
connection drop. Why?

When a network time-out occurs, iDRAC6
firmware drops the connection, disconnecting the
link between the server and the Virtual Drive.
If the Virtual Media configuration settings are
changed in the iDRAC6 Web interface or by local
RACADM commands, any connected media is
disconnected when the configuration change
is applied.
To reconnect to the Virtual Drive, use the Virtual
Media wizard.

Which operating systems
support iDRAC6?

See "Supported Operating Systems" for a list of
supported operating systems.

Which Web browsers support
iDRAC6?

See "Supported Web Browsers" for a list of
supported Web browsers.

Why do I sometimes lose my
client connection?

• You can sometimes lose your client connection if
the network is slow or if you change the CD in the
client system CD drive. For example, if you
change the CD in the client system’s CD drive,
the new CD might have an autostart feature.
If this is the case, the firmware can time out and
the connection can be lost if the client system
takes too long before it is ready to read the CD.
If a connection is lost, reconnect from the
GUI and continue the previous operation.
• When a network timeout occurs, iDRAC6
firmware drops the connection, disconnecting the
link between the server and the Virtual Drive.
Also, someone may have altered the Virtual Media
configuration settings in the Web interface or by
entering RADACM commands. To reconnect to
the Virtual Drive, use the Virtual Media feature.

Configuring and Using Virtual Media

213

Table 12-3. Using Virtual Media: Frequently Asked Questions (continued)
Question

Answer

An installation of the Windows
operating system seems to take
too long. Why?

If you are installing the Windows operating system
using the Dell PowerEdge Installation and Server
Management CD and a slow network connection,
the installation procedure may require an extended
amount of time to access the iDRAC6 Web
interface due to network latency. While the
installation window does not indicate the
installation progress, the installation procedure is
in progress.

I am viewing the contents of a
floppy drive or USB memory key.
If I try to establish a Virtual
Media connection using the
same drive, I receive a
connection failure message and
am asked to retry. Why?

Simultaneous access to Virtual Floppy drives is not
allowed. Close the application used to view the
drive contents before you attempt to virtualize
the drive.

How do I configure my virtual
device as a bootable device?

On the managed server, access the BIOS Setup and
navigate to the boot menu. Locate the virtual CD,
Virtual Floppy, or Virtual Flash and change the
device boot order as needed. For example, to boot
from a CD drive, configure the CD drive as the
first drive in the boot order.

214

Configuring and Using Virtual Media

Table 12-3.

Using Virtual Media: Frequently Asked Questions (continued)

Question

Answer

What types of media can I boot iDRAC6 allows you to boot from the following
from?
bootable media:
• CDROM/DVD Data media
• ISO 9660 image
• 1.44 Floppy disk or floppy image
• A USB key that is recognized by the operating
system as a removable disk (minimum size 128
MB)
• A USB key image
How can I make my USB key
bootable?

Search support.dell.com for the Dell Boot Utility, a
Windows program you can use to make your Dell
USB key bootable.
You can also boot with a Windows 98 startup disk
and copy system files from the startup disk to your
USB key. For example, from the DOS prompt,
enter the following command:

sys a: x: /s
where x: is the USB key you want to make bootable.
You can also use the Dell boot utility to create a
bootable USB key. This utility is only compatible
with Dell-branded USB keys. To download the
utility, open a Web browser, navigate to the Dell
Support website located at support.dell.com,
and search for R122672.exe.

Configuring and Using Virtual Media

215

Table 12-3. Using Virtual Media: Frequently Asked Questions (continued)
Question

Answer

I cannot locate my Virtual
Floppy device on a system
running Red Hat® Enterprise
Linux® or the SUSE® Linux
operating system. My Virtual
Media is attached and I am
connected to my remote floppy.
What should I do?

Some Linux versions do not automount the Virtual
Floppy Drive and the Virtual CD drive in a similar
manner. To mount the Virtual Floppy Drive,
locate the device node that Linux assigns to the
Virtual Floppy Drive. Perform the following
steps to correctly find and mount the Virtual
Floppy Drive:
1 Open a Linux command prompt and run the
following command:
grep "Virtual Floppy" /var/log/
messages
2 Locate the last entry to that message and note the
time.
3 At the Linux prompt, run the following
command:
grep "hh:mm:ss" /var/log/messages
where:

hh:mm:ss is the time stamp of the message
returned by grep in step 1.
4 In step 3, read the result of the grep command
and locate the device name that is given to the
Dell Virtual Floppy.
5 Ensure that you are attached and connected to
the Virtual Floppy Drive.
6 At the Linux prompt, run the following
command:
mount /dev/sdx /mnt/floppy
where:

/dev/sdx is the device name found in step 4
/mnt/floppy is the mount point.

216

Configuring and Using Virtual Media

Table 12-3.

Using Virtual Media: Frequently Asked Questions (continued)

Question

Answer

What file system types are
supported on my Virtual
Floppy Drive?

Your Virtual Floppy Drive supports FAT16 or
FAT32 file systems.

When I performed a firmware
update remotely using the
iDRAC6 Web interface, my
virtual drives at the server were
removed. Why?

Firmware updates cause iDRAC6 to reset, drop the
remote connection, and unmount the virtual
drives. The drives will reappear when the iDRAC6
reset is complete.

Configuring and Using Virtual Media

217

218

Configuring and Using Virtual Media

Using the Local RACADM Command
Line Interface
The local RACADM command line interface (CLI) provides access to
iDRAC6 management features from the managed server. RACADM provides
access to the same features as the iDRAC6 Web interface. However,
RACADM can be used in scripts to ease configuration of multiple servers and
iDRACs, where the Web interface is more useful for interactive management.
Local RACADM commands do not use network connections to access
iDRAC6 from the managed server. This means that you can use local
RACADM commands to configure the initial iDRAC6 networking.
For more information about configuring multiple iDRACs, see "Configuring
Multiple iDRACs."
This section provides the following information:
•

Using RACADM from a command prompt

•

Configuring iDRAC6 using the racadm command

•

Using the RACADM configuration file to configure multiple iDRACs

Using the RACADM Command
You run RACADM commands locally (on the managed server) from a
command prompt or shell prompt.
Log in to the managed server, start a command shell, and enter local
RACADM commands in the following format:
racadm -g -o

Dell Idrac6 Enterprise For Blade Servers Version 2 0 Owners Manual 2.0 User Guide

Navigation menu

Versions of this User Manual:

Views

Navigation