Dell OpenManage Server Administrator Version 5.1 User Manual

Dell OpenManage™

Server Administrator

Version 5.1

Command Line Interface

User's Guide

www.dell.com | support.dell.com

Notes and Notices

NOTE: A NOTE indicates important information that helps you make better use of your computer.

NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

____________________

Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, PowerEdge, and Dell OpenManage are trademarks of Dell Inc.; Microsoft, Windows,

MS-DOS, and Windows NT are registered trademarks and Windows Server is a trademark of Microsoft Corporation; SUSE is a registered trademark of Novell, Inc. in the United States and other countries; Red Hat is a registered trademarks of Red Hat, Inc.; Intel and Pentium are registered trademarks and Itanium and Intel386 are trademarks of Intel Corporation; VESA is a registered trademark of Video Electronic Standards Association; UNIX is a registered trademark of The Open Group in the United States and other countries; OS/2 is a registered trademark of International Business Machines Corporation.

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.

May 2006

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What's New for Version 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using CLI Commands from Windows Command Prompts

Primary CLI Commands

CLI Error Checking and Error Messages

Success Messages Failure Messages

Scripting and Comparing With the CLI

Command Syntax Overview

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

. . . . . . . . . . . . . . . . . . . . . 15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

. . . . . . . . . . . . . . . . . . . . . 17

. . . . . . . . . . . . . . . . . . . . . . . . . . . 17

. . . . . . . . . . . . 14

2 omhelp: Getting Help With CLI Commands . . . . . . . . . . . . 19

Example Help Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 omreport: Viewing System Status Using the Instrumentation

Service

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 21

omreport Command Summary

Help With the omreport Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

. . . . . . . . . . . . . . . . . . . . . . . . . . 21

. . . . . . . . . . . . . . . . . . . . . . . . 25

omreport about

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

omreport chassis Commands

omreport chassis

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

omreport chassis acswitch omreport chassis batteries omreport chassis bios omreport chassis biossetup omreport chassis bmc omreport chassis currents omreport chassis fans

. . . . . . . . . . . . . . . . . . . . . . . . . . 26

. . . . . . . . . . . . . . . . . . . . . . . . . 26

. . . . . . . . . . . . . . . . . . . . . . . . . 27

. . . . . . . . . . . . . . . . . . . . . . . . . . . 27

. . . . . . . . . . . . . . . . . . . . . . . . 27

. . . . . . . . . . . . . . . . . . . . . . . . . . . 29

. . . . . . . . . . . . . . . . . . . . . . . . . 30

. . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Contents 3

omreport chassis fancontrol . . . . . . . . . . . . . . . . . . . . . . . . 30

omreport chassis firmware omreport chassis frontpanel omreport chassis fru omreport chassis info omreport chassis intrusion omreport chassis leds omreport chassis memory omreport chassis nics omreport chassis ports omreport chassis processors omreport chassis pwrsupplies omreport chassis remoteaccess omreport chassis slots omreport chassis temps omreport chassis volts

. . . . . . . . . . . . . . . . . . . . . . . . . 31

. . . . . . . . . . . . . . . . . . . . . . . . 31

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

. . . . . . . . . . . . . . . . . . . . . . . . . 32

. . . . . . . . . . . . . . . . . . . . . . . . . . . 33

. . . . . . . . . . . . . . . . . . . . . . . . . 33

. . . . . . . . . . . . . . . . . . . . . . . . . . . 34

. . . . . . . . . . . . . . . . . . . . . . . . 35

. . . . . . . . . . . . . . . . . . . . . . . 37

. . . . . . . . . . . . . . . . . . . . . . 37

. . . . . . . . . . . . . . . . . . . . . . . . . . . 37

. . . . . . . . . . . . . . . . . . . . . . . . . . 38

. . . . . . . . . . . . . . . . . . . . . . . . . . . 38

omreport system Commands

omreport system Commands for Viewing Logs omreport system alertaction omreport system assetinfo omreport system events omreport system operatingsystem omreport system pedestinations omreport system platformevents omreport system recovery omreport system shutdown omreport system summary omreport system thrmshutdown omreport system version

. . . . . . . . . . . . . . . . . . . . . . . . . . . 38

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

. . . . . . . . . . . . . . . . . . . . . . . . 39

. . . . . . . . . . . . . . . . . . . . . . . . 40

. . . . . . . . . . . . . . . . . . . . . . . . . 41

. . . . . . . . . . . . . . . . . . . . . . . . . . 41

. . . . . . . . . . . . . . . . . . . . . 42

. . . . . . . . . . . . . . . . . . . . . . 42

. . . . . . . . . . . . . . . . . . . . . . 44

. . . . . . . . . . . . . . . . . . . . . . . . . 44

. . . . . . . . . . . . . . . . . . . . . . 47

. . . . . . . . . . . . . . . . . . . . . . . . . . 48

4 omconfig: Managing Components Using the Instrumentation

Service

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 49

omconfig Command Summary

Help With the omconfig Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

. . . . . . . . . . . . . . . . . . . . . . . . . . 49

. . . . . . . . . . . . . . . . . . . . . . . 52

4 Contents

omconfig about

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

omconfig chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

omconfig chassis biossetup omconfig chassis bmc omconfig chassis currents omconfig chassis fans omconfig chassis fancontrol omconfig chassis frontpanel omconfig chassis info omconfig chassis leds omconfig chassis memorymode omconfig chassis remoteaccess omconfig chassis temps omconfig chassis volts

. . . . . . . . . . . . . . . . . . . . . . . . 54

. . . . . . . . . . . . . . . . . . . . . . . . . . . 59

. . . . . . . . . . . . . . . . . . . . . . . . . 68

. . . . . . . . . . . . . . . . . . . . . . . . . . . 69

. . . . . . . . . . . . . . . . . . . . . . . . 70

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

. . . . . . . . . . . . . . . . . . . . . . . . . . . 72

. . . . . . . . . . . . . . . . . . . . . . 72

. . . . . . . . . . . . . . . . . . . . . . 73

. . . . . . . . . . . . . . . . . . . . . . . . . . 82

. . . . . . . . . . . . . . . . . . . . . . . . . . . 83

omconfig preferences

omconfig preferences cdvformat omconfig preferences dirservice omconfig preferences snmp omconfig preferences useraccess

omconfig system

omconfig system alertaction Commands for Clearing Logs omconfig system pedestinations omconfig system platformevents omconfig system events omconfig system webserver omconfig system recovery omconfig system shutdown omconfig system thrmshutdown

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

. . . . . . . . . . . . . . . . . . . . . . 84

. . . . . . . . . . . . . . . . . . . . . . . . 85

. . . . . . . . . . . . . . . . . . . . . 86

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

. . . . . . . . . . . . . . . . . . . . . . . . 87

. . . . . . . . . . . . . . . . . . . . . . . . 89

. . . . . . . . . . . . . . . . . . . . . . 90

. . . . . . . . . . . . . . . . . . . . . . . . . . 92

. . . . . . . . . . . . . . . . . . . . . . . . 94

. . . . . . . . . . . . . . . . . . . . . . . . . 95

. . . . . . . . . . . . . . . . . . . . . . 96

5 omconfig system assetinfo: Editing Cost of Ownership Values 99

omconfig System Asset Info Overview . . . . . . . . . . . . . . . . . . . . . 99

User Level Required for Adding Asset Information

Adding Acquisition Information

. . . . . . . . . . . . . . . . . . . . . . . . . 99

Example Commands for Adding Acquisition Information

. . . . . . . . . . . . . 99

. . . . . . . . 100

Adding Depreciation Information

. . . . . . . . . . . . . . . . . . . . . . . 101

Example Commands for Adding Depreciation Information

. . . . . . . . 101

Contents 5

Adding Extended Warranty Information. . . . . . . . . . . . . . . . . . . . 102

Example Command for Adding Extended Warranty Information

. . . . . 102

Adding Lease Information

Example Command for Adding Lease Information

Adding Maintenance Information

Example Command for Adding Maintenance Information

Adding Outsource Information

Example Command for Adding Outsource Information

Adding Owner Information

Example Command for Adding Owner Information

Adding Service Contract Information

Example Command for Adding Service Information

Adding Support Information

Example Command for Adding Support Information

Adding System Information

Example Command for Adding System Information

Adding Warranty Information

Example Command for Adding Warranty Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . 103

. . . . . . . . . . . . 103

. . . . . . . . . . . . . . . . . . . . . . . 104

. . . . . . . . 104

. . . . . . . . . . . . . . . . . . . . . . . . . 105

. . . . . . . . . . 105

. . . . . . . . . . . . . . . . . . . . . . . . . . . 106

. . . . . . . . . . . . 106

. . . . . . . . . . . . . . . . . . . . . 107

. . . . . . . . . . . 107

. . . . . . . . . . . . . . . . . . . . . . . . . . 108

. . . . . . . . . . . 108

. . . . . . . . . . . . . . . . . . . . . . . . . . 109

. . . . . . . . . . . 109

. . . . . . . . . . . . . . . . . . . . . . . . . 109

. . . . . . . . . . 110

6 omreport rac: Viewing Remote Access Controller Components

111

6 Contents

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . 111

omreport rac Command Summary

Help With the omreport rac Command

omreport rac authentication

Example Command for omreport rac authentication

omreport rac dialinusers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

omreport rac dialoutusers

omreport rac network

omreport rac modem

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

. . . . . . . . . . . . . . . . . . . . . . . 111

. . . . . . . . . . . . . . . . . . . . 112

. . . . . . . . . . . . . . . . . . . . . . . . . . 112

. . . . . . . . . . . 113

. . . . . . . . . . . . . . . . . . . . . . . . . . . 113

omreport rac remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

omreport rac snmptraps

omreport rac users

omreport rac viewcertificate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

. . . . . . . . . . . . . . . . . . . . . . . . . 115

7 omconfig rac: Managing the Remote Access Controller . 117

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . 117

omconfig rac Command Summary

Help With the omconfig rac Command

omconfig rac authentication

Local Operating System Authentication Example Command for omconfig rac authentication

omconfig rac dialinusers

Example Commands

omconfig rac dialoutusers

Example Commands

omconfig rac generatecert

omconfig rac modem

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

. . . . . . . . . . . . . . . . . . . . . . . 117

. . . . . . . . . . . . . . . . . . . . 119

. . . . . . . . . . . . . . . . . . . . . . . . . . 119

. . . . . . . . . . . . . . . . . 119

. . . . . . . . . . . 120

. . . . . . . . . . . . . . . . . . . . . . . . . . . 120

. . . . . . . . . . . . . . . . . . . . . . . . . . . 121

. . . . . . . . . . . . . . . . . . . . . . . . . . . 122

. . . . . . . . . . . . . . . . . . . . . . . . . . 122

omconfig rac network

Example Command

omconfig rac snmptraps

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Example Commands

omconfig rac remote

Example Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

omconfig rac rmdialinuser

Example Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

omconfig rac rmdialoutuser

Example Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

omconfig rac rmsnmptrap

Example Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

. . . . . . . . . . . . . . . . . . . . . . . . . . . 126

. . . . . . . . . . . . . . . . . . . . . . . . . . . 127

. . . . . . . . . . . . . . . . . . . . . . . . . . 128

. . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Contents 7

omconfig rac rmuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Example Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

omconfig rac reset

omconfig rac uploadcert

omconfig rac users

Example Command

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

8 Using the Storage Management Service . . . . . . . . . . . . 133

CLI Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Syntax for Required, Optional, and Variable Command Elements

User Privileges for omreport storage and omconfig storage

omreport Command

omreport Storage Help

omreport Controller Status

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

. . . . . . . . . . . . . . . . . . . . . . . . 136

omreport Global Information (Smart Thermal Shutdown Status) omreport Battery Status omreport Connector Status omreport Enclosure Status omreport Temperature Probe Status omreport Fan Status omreport Power Supply Status omreport EMM Status omreport Physical Disk Status omreport Virtual Disk Status

. . . . . . . . . . . . . . . . . . . . . . . . . 137

. . . . . . . . . . . . . . . . . . . . . . . . 137

. . . . . . . . . . . . . . . . . . . . . . . . 138

. . . . . . . . . . . . . . . . . . . 138

. . . . . . . . . . . . . . . . . . . . . . . . . . . 139

. . . . . . . . . . . . . . . . . . . . . . 140

. . . . . . . . . . . . . . . . . . . . . . . . . . 140

. . . . . . . . . . . . . . . . . . . . . . 141

. . . . . . . . . . . . . . . . . . . . . . . 142

. . . . . . 134

. . . . . . . . . 135

. . . . 137

8 Contents

omconfig Global Commands

. . . . . . . . . . . . . . . . . . . . . . . . . . 142

omconfig Global Enable Smart Thermal Shutdown omconfig Global Disable Smart Thermal Shutdown omconfig Global Rescan Controller

omconfig Controller Commands

omconfig Rescan Controller omconfig Global Rescan Controller omconfig Enable Controller Alarm omconfig Disable Controller Alarm omconfig Quiet Controller Alarm

. . . . . . . . . . . . . . . . . . . . 143

. . . . . . . . . . . . . . . . . . . . . . . . 144

. . . . . . . . . . . . . . . . . . . . . . . 145

. . . . . . . . . . . . . . . . . . . . 145

. . . . . . . . . . . . . . . . . . . . 146

. . . . . . . . . . . . . . . . . . . . . 146

. . . . . . . . . . . 142

. . . . . . . . . . . 143

omconfig Test Controller Alarm. . . . . . . . . . . . . . . . . . . . . . 147

omconfig Reset Controller Configuration omconfig Create Virtual Disk

. . . . . . . . . . . . . . . . . . . . . . . 148

omconfig Set Controller Rebuild Rate omconfig Set Background Initialization Rate omconfig Set Reconstruct Rate omconfig Set Check Consistency Rate omconfig Export the Controller Log omconfig Import Foreign Configuration omconfig Clear Foreign Configuration omconfig Set Patrol Read Mode omconfig Start Patrol Read omconfig Stop Patrol Read

. . . . . . . . . . . . . . . . . . . . . . . . 155

. . . . . . . . . . . . . . . . . 147

. . . . . . . . . . . . . . . . . . 152

. . . . . . . . . . . . . . . 152

. . . . . . . . . . . . . . . . . . . . . 153

. . . . . . . . . . . . . . . . . . 153

. . . . . . . . . . . . . . . . . . . . 153

. . . . . . . . . . . . . . . . . 154

. . . . . . . . . . . . . . . . . . 154

. . . . . . . . . . . . . . . . . . . . . 155

omconfig Virtual Disk Commands

omconfig Blink Virtual Disk

. . . . . . . . . . . . . . . . . . . . . . . . 157

omconfig Unblink Virtual Disk omconfig Initialize Virtual Disk omconfig Cancel Initialize Virtual Disk omconfig Fast Initialize Virtual Disk omconfig Slow Initialize Virtualize Disk omconfig Cancel Background Initialize omconfig Restore Dead Segments omconfig Split Mirror omconfig Unmirror

. . . . . . . . . . . . . . . . . . . . . . . . . . . 159

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

omconfig Assign Dedicated Hot Spare omconfig Unassign Dedicated Hot Spare omconfig Check Consistency omconfig Cancel Check Consistency omconfig Pause Check Consistency omconfig Resume Check Consistency omconfig Delete Virtual Disk

. . . . . . . . . . . . . . . . . . . . . . . 163

omconfig Format Virtual Disk omconfig Reconfiguring Virtual Disks omconfig Change Virtual Disk Policy omconfig Rename Virtual Disk

. . . . . . . . . . . . . . . . . . . . . . . 156

. . . . . . . . . . . . . . . . . . . . . . 157

. . . . . . . . . . . . . . . . . . 158

. . . . . . . . . . . . . . . . . . . 158

. . . . . . . . . . . . . . . . . 158

. . . . . . . . . . . . . . . . . 159

. . . . . . . . . . . . . . . . . . . . 159

. . . . . . . . . . . . . . . . . . 160

. . . . . . . . . . . . . . . . 161

. . . . . . . . . . . . . . . . . . . . . . . 162

. . . . . . . . . . . . . . . . . . . 162

. . . . . . . . . . . . . . . . . . 163

. . . . . . . . . . . . . . . . . . . . . . . 164

. . . . . . . . . . . . . . . . . . 164

. . . . . . . . . . . . . . . . . . . 164

. . . . . . . . . . . . . . . . . . . . . . 165

omconfig Physical Disk Commands

omconfig Blink Physical Disk

. . . . . . . . . . . . . . . . . . . . . . . 166

omconfig Unblink Physical Disk omconfig Prepare to Remove Physical Disk

. . . . . . . . . . . . . . . . . . . . . . 166

. . . . . . . . . . . . . . . . . . . . . . 167

. . . . . . . . . . . . . . . 167

Contents 9

omconfig Initialize Physical Disk . . . . . . . . . . . . . . . . . . . . . 168

omconfig Offline Physical Disk omconfig Offline Physical Disk omconfig Online Physical Disk omconfig Assign Global Hot Spare omconfig Unassign Global Hot Spare omconfig Rebuild Physical Disk omconfig Cancel Rebuild Physical Disk omconfig Remove Dead Segments omconfig Clear Physical Disk omconfig Cancel Clear Physical Disk

. . . . . . . . . . . . . . . . . . . . . . 168

. . . . . . . . . . . . . . . . . . . . . . 169

. . . . . . . . . . . . . . . . . . . . 170

. . . . . . . . . . . . . . . . . . 171

. . . . . . . . . . . . . . . . . . . . . . 171

. . . . . . . . . . . . . . . . . 172

. . . . . . . . . . . . . . . . . . . . 172

. . . . . . . . . . . . . . . . . . . . . . . 173

. . . . . . . . . . . . . . . . . . . 173

omconfig Battery Commands

omconfig Recondition Battery omconfig Start Battery Learn Cycle omconfig Delay Battery Learn Cycle

omconfig Connector Commands

omconfig Rescan Connector

omconfig Enclosure Commands

omconfig Enable Enclosure Alarm omconfig Disable Enclosure Alarm omconfig Enable Smart Thermal Shutdown omconfig Disable Smart Thermal Shutdown omconfig Set Enclosure Asset Tag omconfig Set Enclosure Asset Name omconfig Set Temperature Probe Thresholds omconfig Reset Temperature Probe Thresholds omconfig Set All Temperature Probe Thresholds omconfig Reset All Temperature Probe Thresholds omconfig Blink

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

. . . . . . . . . . . . . . . . . . . . . . . . . 174

. . . . . . . . . . . . . . . . . . . . . . 174

. . . . . . . . . . . . . . . . . . . 175

. . . . . . . . . . . . . . . . . . . . . . . . 176

. . . . . . . . . . . . . . . . . . . . . . . 176

. . . . . . . . . . . . . . . . . . . . . . . . 176

. . . . . . . . . . . . . . . . . . . . 177

. . . . . . . . . . . . . . . . . . . . 178

. . . . . . . . . . . . . . . 178

. . . . . . . . . . . . . . . . . . . . 178

. . . . . . . . . . . . . . . . . . . 179

. . . . . . . . . . . . . . 180

. . . . . . . . . . . . . 180

. . . . . . . . . . . . 181

. . . . . . . . . . . 181

9 Working With CLI Command Results . . . . . . . . . . . . . . . 183

10 Contents

Output Options for Command Results . . . . . . . . . . . . . . . . . . . . . 183

Controlling Command Output Display Writing Command Output to a File Selecting a Format for Your CLI Command Output

. . . . . . . . . . . . . . . . . . . 183

. . . . . . . . . . . . . . . . . . . . 183

. . . . . . . . . . . . 185

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Index

Contents 11

12 Contents

Introduction

Whether you are using the graphical user interface (GUI) or the command line interface (CLI), Dell OpenManage

The reporting and viewing features allow retrieval of overall health status for systems on your network. At the component level, you can view information about the voltages, temperatures, current, fan RPM, memory functioning, and many other critical component details. You see a detailed account of many relevant cost of ownership (COO) facts about your system in summary view. Version information for BIOS, firmware, operating system, and all installed software is easy to retrieve.

Configuration features allow the Server Administrator to perform essential tasks described in detail in the following sections.

NOTE: You can use the CLI instead of the Server Administrator home page, and turn the Server Administrator

Web server off if you have security concerns. The CLI does not use the Web server. Use the omconfig system webserver action=stop command to turn off the Web server. The Web server starts automatically after a reboot, so this command must be issued every time a system starts up. See "omconfig system webserver" for more information.

What's New for Version 5.1

• Diagnostics is no longer available through Server Administrator. To run diagnostics on your system, install Dell

Utilities

support.dell.com

without installing Server Administrator.

• Added support for SUSE Technology (Intel EM64T) systems.

• Added support for Microsoft

™ Server Administrator performs essential systems management tasks.

™

PowerEdge™ Diagnostics from your

CD or download and install Dell PowerEdge Diagnostics from the Dell Support website

. Dell PowerEdge Diagnostics is a stand-alone application that can be run

LINUX Enterprise Server (version 10) on Intel® Extended Memory 64

Windows® Small Business Server 2003 R2 on Intel EM64T systems.

Dell PowerEdge Service and Diagnostic

Introduction 13

Using CLI Commands from Windows Command Prompts

If you are running the Windows operating system, use the 32-bit command prompt to issue a Server Administrator CLI command. You can access the 32-bit command prompt by clicking the Start button

and pointing to Programs→ Accessories→ Command Prompt shortcut, or by clicking the Start button and selecting Run, then typing cmd.exe in the Run dialog box.

Do not type command into the Run dialog box to launch a command line window; this activates the MS-DOS problems with the CLI.

emulator command.com, which has environment variable limitations that can cause subtle

Primary CLI Commands

The commands that carry out the functions of Server Administrator are:

•

omconfig

•

omhelp

•

omreport

The omconfig command writes values that you assign to an object's properties. You can specify values for warning thresholds on components or prescribe what action your system is to take when a certain warning or failure event occurs. You can also use the omconfig command to assign specific values to your system's asset information parameters, such as the purchase price of the system, the system's asset tag, or the system's location.

The omhelp command displays short text help for CLI commands. The shorthand equivalent of omhelp is the command for which you want help followed by -?. For example, to display help for the omreport command, type one of the following commands:

omhelp omreport omreport -?

The omreport command produces reports of your system’s management information.

NOTE: For an overall summary of CLI commands, type omhelp.

14 Introduction

Table 1-1 lists the primary CLI commands used by Server Administrator. This guide contains a section for each primary command.

Table 1-1. CLI Commands and Sections in This Guide

Primary CLI Command

omconfig omconfig: Managing Components Using the

omhelp omhelp: Getting Help With CLI Commands

omreport omreport: Viewing System Status Using

NOTE: Omupdate commands are no longer supported in Server Administrator and are replaced by Dell Update

Package or Server Update Utility commands. To update the different components, download the Dell Update Package

and run <package name> /s [/f]. See the Dell Update Packages for Microsoft Windows Operating Systems User’s Guide, the DellUpdate Packages for Red Hat

for more information on corresponding CLI syntax.

Section Title Related Sections

omconfig system assetinfo: Editing

Instrumentation Service

the Instrumentation Service

Enterprise Linux User’ s Guide, or the Server Update Utility User’s Guide

Cost of Ownership Values

omreport rac: Viewing Remote Access Controller Components

Additional useful topics about the CLI include:

• Working With CLI Command Results

• Glossary

CLI Error Checking and Error Messages

The CLI checks your commands for correct syntax when you enter them. If you enter a command and the command is executed successfully, a message displays, stating that your command has been successful.

Success Messages

For a successful omreport command, data about the component displays. When data for the component displays, your command is successful.

The following omconfig command examples show valid CLI commands and their success messages:

Command:

omconfig chassis temps index=0 warnthresh=default

Message:

Temperature probe warning threshold value(s) set successfully.

Command:

omconfig chassis biossetup attribute=speaker setting=on

Introduction 15

Message:

BIOS setup configured successfully.

Command:

omconfig system assetinfo info=depreciation duration=6

Message:

Asset information set successfully.

Failure Messages

CLI failure messages provide reasons why some commands do not succeed. Some common reasons why commands fail include syntax errors and components that are not present. Many error messages provide syntax information that you can use to execute the command successfully.

If you try to execute a command for a component or feature that is not present in your system configuration, the error message states that the component is not present.

Command:

omreport chassis currents

Example message:

Error! No current probes found on this system.

Command:

omconfig chassis volts index=3 minwarnthresh=3.3000

Example message:

Error! Number with up to 3 digits after decimal point expected, read

3.3000 The value given by the command specifies more than 3 digits after the

decimal point. A valid minimum warning threshold value for volts contains up to 3 digits after the decimal point.

Ty p e :

omconfig chassis volts index=3 minwarnthresh=3.300

When you enter the revised command with three decimal points, you receive another error message:

Error! This voltage probe min warning threshold must be between

11.400 and 12.480.

Revised command:

omconfig chassis volts index=3 minwarnthresh=11.500

Message:

Voltage probe warning threshold(s) set successfully.

16 Introduction

Scripting and Comparing With the CLI

The Server Administrator CLI allows administrators to write batch programs or scripts to be executed by the operating system. For an enterprise with many systems, an administrator could write a configuration script that specified the warning thresholds for each major component of a system and also specified a set of actions that the administrator wants each system to take in case of a warning or failure event. In the most critical cases, the administrator could write a script so that the system shuts down to prevent damage. The administrator could then distribute and execute the script to many managed systems at the same time. Such a scenario facilitates configuring any number of new systems acquired by a company and makes implementation of new system administration policies easier across many existing systems that require reconfiguration.

A similar scenario could be used to populate a large number of newly acquired systems with detailed asset information. Much of the information would be the same, such as the manufacturer or lessor of the system, whether support for the system is outsourced, name of the system's insurance company, method of depreciation, and so on. Any variable that is common to all systems could be scripted, sent to all managed systems, and executed. Asset information that is unique to a system could be scripted as a group and sent to that managed node for execution. For example, a script could specify values for all unique variables such as owner, primary user phone number, asset tag, and so on. Scripts to populate unique values would set all unique variables at once rather than one by one through the system's command line.

In many cases, the CLI allows a user with a very well-defined task in mind to retrieve information about the system rapidly. If a user wants to review a comprehensive summary of all system components and save that summary information to a file for comparison with later system states, the CLI is ideal.

Using CLI commands, administrators can write batch programs or scripts to execute at specific times. When these programs execute, they can capture reports on components of interest, such as fan RPMs during periods of high system usage compared with the same measurements at times of lowest system usage. Command results can be routed to a file for later analysis. Reports can help administrators gain information that can be used to adjust usage patterns, to justify purchasing new system resources, or to focus on the health of a problem component.

Command Syntax Overview

Commands vary in complexity. The simplest command has only command level 1. The omhelp command is a simple command. When you type omhelp, a list of the main CLI commands is displayed.

The next level of complexity includes commands that contain command levels 1 and 2. All of the about commands are examples of command level 2 complexity. The omconfig about and omreport about commands cause a very brief summary to display. The summary shows version information for the systems management software installed on your system; for example, Server Administrator 1.x.

Some commands have command level 1 and command level 2 and one name=value pair. Consider the following example command that instructs Server Administrator for more details about the environment for Server Administrator:

omreport about details=true

Introduction 17

Command level 1 is omreport, command level 2 is about, and the name=value pair is details=true.

Many commands use command level 1, command level 2, and command level 3, but do not require any parameters (name=value pairs). Most omreport commands are of this type. For example:

omreport system alertaction

causes a list of alert actions that are configured for components on your system to be displayed.

The most complex commands have all three command levels and can have multiple name=value pairs. An example of two name=value pairs:

omconfig system assetinfo info=depreciation duration=3

An example of nine name=value pairs:

omconfig system assetinfo info=acquisition purchasecost=

mmddyy

> ponum=<n> signauth=<

expensed=<

<n> waybill=<n> installdate=<

text

yes | no

> costcenter=<

text

mmddyy

> purchasedate=

In each section, command syntax and other information about commands is formatted with any of the following fields that apply:

command level 1 command level 2 command level 3 name=value pair 1 name=value pair 2

18 Introduction

omhelp: Getting Help With CLI Commands

The omhelp command and its equivalent, <command> -?, accesses the CLI's detailed help text interface. You can get help at several levels of detail.

Each fully qualified CLI command may have a variable number of distinct parts: the command (command level 1), one or more subcommands (command level 2 and command level 3, if present), and one or more name=value pair(s).

By appending -? (space-dash-question mark) to any command, you can get help on the command.

Example Help Commands

When you type omconfig -?, you get general help about the omconfig command. The help at this level lists the available subcommands for omconfig:

•about

•preferences

• chassis

• system

When you type omconfig system -?, CLI help lists all of the subcommands that are available for omconfig system:

• alertaction

• alertlog

• assetinfo

• cmdlog

• esmlog

•events

• recovery

• shutdown

• thrmshutdown

• webserver

Figure 2-1 shows the levels of help for a command.

omhelp: Getting Help With CLI Commands 19

Figure 2-1. Different Levels of Help for a Command

You can also parse the omconfig system assetinfo command as follows:

<command level 1 command level 2 command level 3> <name=value pair 1> [name=value pair 2]

where command levels 1, 2, and 3 are represented by omconfig system assetinfo, name=value pair 1 is represented by info=depreciation, and name=value pair 2 is represented by method=straightline.

To set your depreciation method to straight line, type:

omconfig system assetinfo info=depreciation method=straightline

The CLI responds with the following message:

Asset information set successfully.

When you type omconfig system assetinfo -?, the help that displays provides information about assigning values for the name and option fields. Partial results for the request omconfig system assetinfo -? are as follows:

assetinfo Set asset information.

For one info value, specify one or more optional parameter(s). Table 2-1 displays the optional parameters for info=acquisition:

Table 2-1. Optional Parameters

Info Value Optional parameters

Info=acquisition purchasecost=<num>

waybill=<num> installdate=<mmddyy> purchasedate=<mmddyy> ponum=<num> signauth=<text> expensed=<yes|no> costcenter=<text> info=depreciation method=<text> duration=<num> percent=<percent> unit=<months|years|unknown>

20 omhelp: Getting Help With CLI Commands

omreport: Viewing System Status Using the Instrumentation Service

The omreport command allows you to see detailed information about your system components. You can retrieve summaries for many system components at one time, or you can get details about a specific component. This chapter shows you how to get reports with the level of detail that you want.

Commands documented in this chapter vary in whether they define the fields that appear in the results of a particular omreport command. Fields are defined only if they have a special or less familiar use.

As with all other components, you can use omreport to view component status, and omconfig to manage a component. For information on how to configure components for management, see "omconfig: Managing Components Using the Instrumentation Service."

Often you can use omreport commands to get information you need to execute an omconfig command. For example, if you want to edit the minimum temperature for a warning event on a temperature probe, you need to know the index of the probe you want to configure. You can use omreport chassis temps to display a list of probes and their indexes.

Conventions for Parameter Tables

When listing the parameters that a command can take, the parameters are listed in alphabetical order instead of the order in which they appear in the command line interface.

The symbol |, often called pipe, is the logical exclusive or operator. For example, enable | disable means that you can enable or disable the component or feature, but you cannot simultaneously enable and disable the component or feature.

omreport Command Summary

NOTE: Although this chapter lists all possible omreport commands, the commands available on your system

depend on your system configuration. The results that display for the omreport command vary from one system to another. Data displays for installed components only.

NOTE: When a system includes an external chassis, the displayed results vary by operating system.

SUSE

On external chassis information in a separate section after the main chassis information. On Microsoft Windows

LINUX

systems, data about the external chassis does not appear in omreport output.

Enterprise Server and Red Hat® Enterprise Linux systems, omreport commands display

omreport: Viewing System Status Using the Instrumentation Service 21

Table 3-1 is a high-level summary of the omreport command. The column titled "Command level 1" shows the omreport command at its most general. "Command level 2" shows the major objects or components that you can view using omreport (about, chassis, storage, system, and rac). "Command level 3" lists the specific objects and components for which you can view reports. "User privilege required" refers to the type of privilege you need to perform the command, where U=User, P=Power User, and A= Administrator. "Use" is a very general statement about the actions that can be performed using omreport. More details about syntax and use of the command appear later in this section.

Table 3-1 shows the omreport commands available for about, system, and main system chassis. For information about viewing storage components, see "omreport: Viewing System Status Using the Instrumentation Service."

Table 3-1. omreport Command Level 1, Level 2, and Level 3

Command level 1

omreport

Command level 2

about U, P, A Shows version number and properties for the

chassis U, P, A Shows a general status for all main components.

Command level 3

details=true U, P, A Displays information for all of the Server

acswitch U, P, A Shows failover settings where redundant AC

batteries U, P, A Shows properties set for batteries.

bios U, P, A Shows BIOS facts such as manufacturer, version,

biossetup U, P, A Shows BIOS setup properties configured during

bmc U, P, A Shows general information on remoteaccess.

User privilege required

Use

Server Administrator program.

Administrator programs that are installed.

power lines are supported in a system.

and date last updated.

system boot.

NOTE: This subcommand will be phased-out in

future releases. It will be replaced by the subcommand remoteaccess.

currents U, P, A Shows the status and thresholds for the system

current sensors.

fancontrol U, P, A Shows properties set for fan speed.

fans U, P, A Shows status and thresholds for system fans.

firmware U, P, A Shows firmware properties such as version, date

of last update, and whether the firmware is updatable.

22 omreport: Viewing System Status Using the Instrumentation Service

Table 3-1. omreport Command Level 1, Level 2, and Level 3 (continued)

Command level 1

Command level 2

storage U, P, A See "Using the Storage Management Service."

system U, P, A Shows a high-level summary of system

Command level 3

frontpanel U, P, A Shows whether the front panel button settings,

fru U, P, A Shows the Field Replaceable Unit (FRU)

info U, P, A Shows a status summary for main system chassis

intrusion U, P, A Shows the status of the system’s intrusion

leds U, P, A Shows the properties you have set for LEDs to

memory U, P, A Shows properties of your system's memory arrays.

nics U, P, A Shows number of NICs installed in your system,

ports U, P, A Shows properties for your system’s parallel and

processors U, P, A Shows properties of your system’s processors,

pwrsupplies U, P, A Shows properties of power supplies.

remoteaccess U, P, A Shows general information on remote access.

slots U, P, A Shows properties of your system’s expansion slots

temps U, P, A Shows the status and thresholds for the system

volts U, P, A Shows the status and thresholds for the system

User privilege required

Use

such as for the Power button and/or Nonmasking Interrupt (NMI) button (if present on the system), are enabled or disabled.

information.

components.

sensor(s).

flash under various alert conditions.

NIC vendor, NIC description, IP address, and connection status.

serial ports, such as I/O address, IRQ level, connector type, and maximum speed.

including speed, manufacturer, and processor family.

and other slot types.

temperature sensors.

voltage sensors.

components.

omreport: Viewing System Status Using the Instrumentation Service 23

Table 3-1. omreport Command Level 1, Level 2, and Level 3 (continued)

Command level 1

Command level 2

rac U, P, A See "omreport rac: Viewing Remote Access

Command level 3

alertaction U, P, A Shows warning and failure threshold values, as

alertlog U, P, A Allows the administrator to show the alert log.

assetinfo U, P, A Shows cost of ownership information for

cmdlog U, P, A Allows the administrator to show the

esmlog U, P, A Allows the administrator to show the

events U, P, A Shows the system’s Simple Network

operatingsystem U, P, A Shows the name and version of your

pedestinations U, P, A Shows destinations where alerts for platform

platformevents U, P, A Shows the system’s response for each listed

postlog U, P, A Shows your system’s POST log.

recovery U, P, A Shows how your system is configured to respond

shutdown U, P, A Shows how the shutdown action is to be

summary U, P, A Shows key facts for all system components,

thrmshutdown U, P, A Shows what shutdown action, if any, is to be

version U, P, A Shows a summary for all updatable components

User privilege required

Use

well as actions that have been configured when an essential component detects a warning or failure state.

your system.

command log.

hardware log.

Management Protocol (SNMP) event settings.

operating system.

events are configured to be sent.

platform event.

to a hung operating system.

performed.

including main system chassis, software, and storage.

taken when a temperature warning or failure condition is detected.

on your system.

Controller Components."

24 omreport: Viewing System Status Using the Instrumentation Service

Help With the omreport Command

Use the omreport -? command to get a list of the available commands for omreport.

Use omreport <command level 2> -? to get help on the level 2 commands about, chassis, and system. The following information on omreport system -? applies equally to getting help for the omreport chassis command.

To see a list of valid commands for omreport system, type:

omreport system -? | more

omreport about

Use the omreport about command to learn the product name and version number of the systems management application installed on your system. The following is an example output from the omreport about command:

Product name Version Copyright Company

For even more details about the environment for Server Administrator, type:

omreport about details=true

Server Administrator includes a number of services, each of which has a version number of its own. The Contains field reports version numbers for the services as well as other useful details. The output below is an example, and can change depending on your configuration and the version of Server Administrator that is installed on your system:

Contains: Instrumentation Service 5.

x.x

Storage Management Service 3.x. Sun JRE - OEM Installed Version 3.x. Secure Port Server 1.x. Core Service 1.x. Instrumentation Service Integration Layer 1.x. Storage Management Service Integration Layer 1.x. Server Administrator 5.x.

omreport: Viewing System Status Using the Instrumentation Service 25

omreport chassis Commands

Use omreport chassis commands to view details for the entire chassis or for a particular component.

omreport chassis

When you type:

omreport chassis

Server Administrator displays a general status for your main system chassis components.

NOTE: When you issue CLI commands to a server module in a modular system, chassis refers only to the

server module.

NOTE: As with all output shown in this guide, the following output is an example and may vary depending on your

system configuration.

SEVERITY : COMPONENT Ok : Fans Critical : Intrusion Ok : Memory Ok : Power Supplies Ok : Temperatures Ok : Voltages

omreport chassis acswitch

Use the omreport chassis acswitch command if your system has redundant AC power lines that are configured in a failover arrangement. When you type:

omreport chassis acswitch

Server Administrator displays the following output:

AC Failover Switch AC Switch Redundancy

Redundancy Status : Full Number of devices required for full

redundancy Redundancy Mode : Redundancy Configuration : Input Source Line 1,

26 omreport: Viewing System Status Using the Instrumentation Service

upon redundancy restoration, return to Line 1

AC Power Lines Status : Ok Location : AC Power Line 1 AC Present : Power Present Active Source : Active Status : Ok Location : AC Power Line 2 AC Present : Power Present Active Source : Not Active

Server Administrator reports values for the Redundancy Status and Redundancy Mode fields.

omreport chassis batteries

Use the omreport chassis batteries command to view battery properties.

omreport chassis bios

Use the omreport chassis bios command to view current BIOS information. When you type:

omreport chassis bios

Server Administrator displays a summary of your system’s BIOS information.

omreport chassis biossetup

Use the omreport chassis biossetup command to view BIOS setup parameters that are normally available only during system boot.

Ty p e :

omreport chassis biossetup

Table 3-2 displays the BIOS setup parameters that are available:

NOTE: Not all the parameters are displayed. Only those BIOS setup properties that are configured during system

boot are displayed.

omreport: Viewing System Status Using the Instrumentation Service 27

Table 3-2. BIOS Setup Parameters

Parameters Description

Bezel Displays whether the bezel removal intrusion check during system

reboot is enabled or disabled.

Bootsequence Displays the device that is used to boot the system.

Console Redirection Displays if the BIOS screen is redirected over a particular serial port

or if it is turned off.

Console Redirection After Boot Displays whether console redirection after system reboot is enabled

or disabled.

Diskette Displays whether the diskette is disabled, auto enabled, or read only.

Demand Based Power Management (DBS)

Dual NIC Displays whether NIC 1 and NIC 2 with PXE is enabled or disabled.

External Serial Connector Displays whether the external serial connector is mapped to COM

Console Redirection Failsafe Baud Rate

IDE Displays whether the drive is enabled or disabled.

IDE Primary Drive 0 Displays whether the device is automatically detected and enabled

IDE Primary Drive 1 Displays whether the device is automatically detected and enabled

Intrusion Displays whether the intrusion check is enabled or disabled during

Mouse Displays whether the mouse is enabled or disabled.

NIC and NIC 2 Displays whether the first and second NICs are enabled (with or

Numlock Displays whether the keypad can be used as number keys.

Parallel port address Displays whether the address is located on LPT1, LPT2, and LPT3,

Parallel port mode Displays the setting associated with the parallel port.

Primary SCSI Displays whether the device is on or off.

RAID on motherboard Displays whether RAID-on-motherboard is detected as a RAID

RAID Channel A Displays whether RAID-on-motherboard Channel A is detected as a

Displays whether DBS is enabled or disabled on the system.

port 1 or COM port 2 or a Remote Access Device.

Displays the setting for console redirection failsafe baud rate.

or if the device is disabled.

system boot.

without PXE) or disabled during system boot.

or if it is disabled.

device, a SCSI device, or if the device is disabled during system boot.

RAID device or a SCSI device.

28 omreport: Viewing System Status Using the Instrumentation Service

Table 3-2. BIOS Setup Parameters (continued)

Parameters Description

RAID Channel B Displays whether RAID-on-motherboard Channel B is detected as a

RAID device or a SCSI device.

SATA Displays whether the onboard SATA controller is set to ATA mode,

RAID mode, or is disabled.

SATA port Displays if the SATA port is enabled or disabled.

Secondary SCSI Displays whether the device is enabled or disabled.

Serial Communications Displays whether COM port 1 and COM port 2 are enabled or

disabled with or without console redirection.

Serial Port 1 Displays whether serial port 1 is mapped to a COM port, a

COM port 1, a COM port 3, a COM1 BMC, a BMC Serial, a BMC NIC, a BMC RAC, or is disabled.

Serial Port 2 Displays whether serial port 2 is mapped to a COM port, a

COM port 2, a COM port 4, or is disabled.

Speaker Displays whether the speaker is on or off.

USB or USBB Displays whether the USB port is enabled or disabled.

User accessible USB Displays whether the user-accessible USB port is enabled or disabled.

omreport chassis bmc

NOTE: This command will be phased-out in future releases. It will be replaced by the command omreport chassis

remoteaccess.

Use the omreport chassis bmc command to view baseboard management controller (BMC) general information.

Ty p e :

omreport chassis bmc

The output from the omreport chassis bmc command lists each of the valid parameters. Table 3-3 shows the available settings.

omreport: Viewing System Status Using the Instrumentation Service 29

Table 3-3. omreport chassis bmc

name=value pair Description

config=advsol Reports advanced BMC information on a serial over local area network (LAN) connection.

config=nic Reports BMC information for the LAN.

config=serial Reports serial port information for BMC.

config=serialoverlan Reports BMC information on a serial over LAN connection.

config=terminalmode Reports terminal mode settings for the serial port.

config=user Reports information on BMC users.

omreport chassis currents

Use the omreport chassis currents command to view current (amperage) probe status and settings. When you type:

omreport chassis currents index=

the index parameter is optional. If you do not specify the index, Server Administrator displays a summary of status, readings, and thresholds set for all current probes present on your system. If you specify the index, Server Administrator displays a summary for a specific current probe.

omreport chassis fans

Use the omreport chassis fans command to view fan probe status and settings. When you type:

omreport chassis fans index=

the index parameter is optional. If you do not specify the index, Server Administrator displays a summary of status, readings, and thresholds set for any fan probes that might be present on your system. If you specify the index, Server Administrator displays a summary for a specific fan probe.

omreport chassis fancontrol

Use the omreport chassis fancontrol command to see how fan speed is set on your system. Fan speed can be set to optimize speed for cooling or for quiet operation. Table 3-4 shows the available settings.

Table 3-4. Fan Control Settings

name=value pair Description

speed=quiet Set fan speed for quiet operation.

speed=maxcool Set fan speed for maximum cooling.

30 omreport: Viewing System Status Using the Instrumentation Service

+ 192 hidden pages