Dell OpenManage Server Administrator Version 2.3 User Manual

Dell OpenManage™

Server Administrator

Version 2.3

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; Red Hat is a registered trademark of Red Hat, Inc.; Intel, P entium, and Xeon 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.

November 2005

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

What's New for Version 2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

. . . . . . . . . . . . . . . . . . . . . 13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

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

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

. . . . . . . . . . . . 11

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

Example Help Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3 omdiag: Using the Diagnostic Service . . . . . . . . . . . . . . . 19

omdiag about. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

omdiag about details=true

omdiag chassis

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

omdiag chassis -? omdiag chassis cmos omdiag chassis memory omdiag chassis modem omdiag chassis network omdiag chassis parallelport omdiag chassis pci omdiag chassis rac omdiag chassis serialport omdiag chassis usbctrl

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

. . . . . . . . . . . . . . . . . . . . . . . . . . 23

. . . . . . . . . . . . . . . . . . . . . . . . . . . 23

. . . . . . . . . . . . . . . . . . . . . . . . . . 24

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

. . . . . . . . . . . . . . . . . . . . . . . . . 28

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

Contents 3

omdiag storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

omdiag storage -? omdiag storage cddvd omdiag storage floppy omdiag storage idedevdiag omdiag storage raidctrl omdiag storage sasdevdiag omdiag storage scsidevdiag

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

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

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

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

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

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

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

omdiag system

omdiag system -?

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

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

4 omreport: Viewing System Status Using the

Instrumentation Service

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 37

omreport Command Summary

Help With the omreport Command

omreport about

omreport chassis Commands

omreport chassis omreport chassis acswitch omreport chassis bios omreport chassis biossetup omreport chassis bmc omreport chassis currents omreport chassis fans omreport chassis fancontrol 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

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . 43

. . . . . . . . . . . . . . . . . . . . . . . . . . . 43

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . 45

. . . . . . . . . . . . . . . . . . . . . . . . . 46

. . . . . . . . . . . . . . . . . . . . . . . . . . . 46

. . . . . . . . . . . . . . . . . . . . . . . . 46

. . . . . . . . . . . . . . . . . . . . . . . . . 46

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . 50

. . . . . . . . . . . . . . . . . . . . . . . . 51

4 Contents

omreport chassis pwrsupplies . . . . . . . . . . . . . . . . . . . . . . . 53

omreport chassis slots omreport chassis temps omreport chassis volts

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . 55

. . . . . . . . . . . . . . . . . . . . . . . . . 56

. . . . . . . . . . . . . . . . . . . . . . . . . . 57

. . . . . . . . . . . . . . . . . . . . . 58

. . . . . . . . . . . . . . . . . . . . . . 58

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . 60

. . . . . . . . . . . . . . . . . . . . . . 63

. . . . . . . . . . . . . . . . . . . . . . . . . . 64

5 omreport storage: Using the Storage Reports. . . . . . . . . . 65

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 65

omreport storage Command Summary

omreport storage Commands

omreport storage arraydisks omreport storage arrays omreport storage enclosureinfo omreport storage enclosures omreport storage osdiskinfo omreport storage osdisks omreport storage volumes

. . . . . . . . . . . . . . . . . . . . . . 65

. . . . . . . . . . . . . . . . . . . . . . . . . . 66

. . . . . . . . . . . . . . . . . . . . . . . . 67

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . 74

6 omconfig: Managing Components Using the

Instrumentation Service

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 75

omconfig Command Summary

. . . . . . . . . . . . . . . . . . . . . . . . . 75

. . . . . . . . . . . . . . . . . . . . . . . . . . 76

Contents 5

Help With the omconfig Command . . . . . . . . . . . . . . . . . . . . . . . 78

omconfig about

omconfig chassis

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

omconfig chassis biossetup omconfig chassis bmc omconfig chassis currents omconfig chassis fans omconfig chassis fancontrol omconfig chassis frontpanel omconfig chassis info

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

omconfig chassis leds omconfig chassis memorymode omconfig chassis temps omconfig chassis volts

omconfig preferences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

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

omconfig system

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

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

. . . . . . . . . . . . . . . . . . . . . . . . 80

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

. . . . . . . . . . . . . . . . . . . . . . . . . 91

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

. . . . . . . . . . . . . . . . . . . . . . . . 93

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . 97

. . . . . . . . . . . . . . . . . . . . . . 98

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

. . . . . . . . . . . . . . . . . . . . 100

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

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . 110

7 omconfig system assetinfo: Editing Cost of

6 Contents

Ownership Values

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

omconfig System Asset Info Overview . . . . . . . . . . . . . . . . . . . . 111

User Level Required for Adding Asset Information

Adding Acquisition Information

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

Example Commands for Adding Acquisition Information

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

. . . . . . . . 112

Adding Depreciation Information . . . . . . . . . . . . . . . . . . . . . . . 113

Example Commands for Adding Depreciation Information

. . . . . . . . 113

Adding Extended Warranty Information

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

Example Command for Adding Extended Warranty Information

Adding Lease Information

Example Command for Adding Lease Information

Adding Maintenance Information

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

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

. . . . . . . . . . . . . . . . . . . . . . . 116

Example Command for Adding Maintenance Information

Adding Outsource Information

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

Example Command for Adding Outsource Information

Adding Owner Information

Example Command for Adding Owner Information

Adding Service Contract Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . 118

. . . . . . . . . . . . 118

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

Example Command for Adding Service Information

Adding Support Information

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

Example Command for Adding Support Information

Adding System Information

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

Example Command for Adding System Information

Adding Warranty Information

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

Example Command for Adding Warranty Information

. . . . . 114

. . . . . . . . 116

. . . . . . . . . . 117

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

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

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

. . . . . . . . . . 122

8 Using the Storage Management Service . . . . . . . . . . . . 123

CLI Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Syntax for Required, Optional, and Variable Command Elements

User Privileges for omreport storage and omconfig storage

omreport Command

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

. . . . . . 124

. . . . . . . . . 126

Contents 7

omreport Storage Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

omreport Controller Status 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 Array Disk Status omreport Virtual Disk Status

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

. . . . 127

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

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . 132

omconfig Global Commands

. . . . . . . . . . . . . . . . . . . . . . . . . . 132

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 omconfig Test Controller Alarm

. . . . . . . . . . . . . . . . . . . . 133

. . . . . . . . . . . . . . . . . . . . . . . . 134

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

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

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

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

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

omconfig Reset Controller Configuration omconfig Create Virtual Disk omconfig Set Controller Rebuild Rate

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

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

omconfig Set Background Initialization Rate omconfig Set Reconstruct Rate

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

omconfig Set Check Consistency Rate omconfig Export the Controller Log

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

omconfig Import Foreign Configuration omconfig Clear Foreign Configuration omconfig Set Patrol Read Mode omconfig Start Patrol Read omconfig Stop Patrol Read

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

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

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

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

. . . . . . . . . . . 132

. . . . . . . . . . . 133

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

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

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

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

8 Contents

omconfig Virtual Disk Commands . . . . . . . . . . . . . . . . . . . . . . . 145

omconfig Blink Virtual Disk 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 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 omconfig Format Virtual Disk omconfig Reconfiguring Virtual Disks omconfig Change Virtual Disk Policy omconfig Rename Virtual Disk

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

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . 149

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

. . . . . . . . . . . . . . . . . . 150

. . . . . . . . . . . . . . . . 150

. . . . . . . . . . . . . . . . . . . . . . . 151

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

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

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

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

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

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

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

omconfig Array Disk Commands

omconfig Blink Array Disk

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

omconfig Unblink Array Disk omconfig Prepare to Remove Array Disk omconfig Initialize Array Disk omconfig Offline Array Disk omconfig Offline Array Disk omconfig Online Array Disk

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

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

omconfig Assign Global Hot Spare omconfig Unassign Global Hot Spare omconfig Rebuild Array Disk omconfig Cancel Rebuild Array Disk omconfig Remove Dead Segments omconfig Clear Array Disk

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

omconfig Cancel Clear Array Disk

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

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

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

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

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

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

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

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

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

Contents 9

omconfig Battery Commands . . . . . . . . . . . . . . . . . . . . . . . . . 165

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9 Working With CLI Command Results . . . . . . . . . . . . . . . 175

Output Options for Command Results . . . . . . . . . . . . . . . . . . . . . 175

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

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

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

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

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Index

10 Contents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Introduction

Whether you are using the graphical user interface (GUI) or the command line interface (CLI), Server Administrator performs essential systems management tasks.

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. You can also run diagnostic tests on system components.

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 2.3

Added Serial Attached SCSI (SAS) support for Dell™ PowerEdge™ 6800 and 6850

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 subtle problems with the CLI.

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

Introduction 11

Primary CLI Commands

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

•

omconfig

•

omdiag

•

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 omdiag command runs diagnostic tests against system hardware to isolate problems.

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.

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

omdiag omdiag: Using the Diagnostic Service

omhelp omhelp: Getting Help With CLI

omreport omreport: Viewing System Status

Section Title Related Sections

Using the Instrumentation Service

Commands

Using the Instrumentation Service

12 Introduction

omconfig system assetinfo: Editing Cost of Ownership Values

omconfig rac: Managing the Remote Access Controller

omreport storage: Using the Storage Reports

omreport rac: Viewing Remote Access Controller Components

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

Sy stems User’s Guide, the Dell Update Packages for Red Hat Utility User’s Guide for more information on corresponding CLI syntax.

Enterprise Linux User’ s Guide, or the Server Update

Windows® Operating

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

Message:

BIOS setup configured successfully.

Command:

omconfig system assetinfo info=depreciation duration=6

Message:

Asset information set successfully.

Introduction 13

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.

14 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

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, omdiag about, and omreport about commands all 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.

omhelp, a list of the main CLI commands is displayed.

Introduction 15

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

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

16 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 17

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>

18 omhelp: Getting Help With CLI Commands

omdiag: Using the Diagnostic Service

The omdiag command allows you to test chassis and storage components such as hard drives, physical memory, communications and printer ports, NICs, CMOS, and more.

Most tests described in this section take less than one minute. Some test can take longer depending on the device being tested. You cannot abort tests you start through the command line interface.

NOTICE: If you run omdiag commands from more than one console when the secure port server (for systems

running Microsoft then the test in the first console will run to completion, but the test(s) in the subsequent console(s) may exit with a "Test was interrupted" message.

NOTE: You can abort a Diagnostic Service test run through the CLI by using the Diagnostic Status window in

the Server Administrator GUI. Click the Diagnostics tab, click Status, and click Abort to stop the currently running test or click Abort All to stop the currently running test and all queued tests.

NOTE: You cannot use <Ctrl-C> to cancel a CLI session from the console. However, tests started from the CLI

can be aborted using the "Abort" link in the "Diagnostic Status" page in the GUI.

NOTE: If the secure port server is not running when you type an omdiag command, there will be a noticeable

delay before the command executes because the system must check the hardware to determine the diagnostic information to display.

NOTE: On systems running the Microsoft Windows operating system, the enumeration process requires that

the Windows Management Instrumentation (WMI) services be running.

Windows®) or omawsd (for systems running Red Hat® Enterprise Linux) is not running,

Table 3-1 is a high-level summary of the omdiag command. The columns titled "Command level 2" and "Command level 3" list the major arguments that can be used with omdiag. The "Use" column provides a very general statement about the actions that can be performed using omdiag. More details about syntax and use of the command appear later in this section.

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

Command level 1

omdiag

Command level 2

about Displays version number and properties for the

Command level 3

details= true

name=value pair

Use

Server Administrator program.

Displays information for all of the Server Administrator programs that are installed.

omdiag: Using the Diagnostic Service 19

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

Command level 1

Command level 2

system any level 3

chassis cmos

Command level 3

command for chassis or storage

memory

modem

network

parallelport

pci

serialport

rac

usbctrl

name=value pair

passes=<n> Runs a test n time(s).

time= <minutes>

quicktest=

haltonerror=

Device=

passes=<n> Runs a test n time(s).

time= <minutes>

quicktest=

haltonerror=

Device=

Use

Runs the test for specified chassis or storage component.

Runs a test for the specified number of minutes <minutes>.

Uses a faster algorithm to conduct a specific test if one is available.

Stops the tests if an error is encountered.

Specifies the device on which to run test.

Runs the CMOS test.

Runs the memory test.

Runs the modem test.

Runs the NIC test.

Runs the parallel port test.

Runs the PCI test.

Runs the serial port test.

Runs the RAC test.

Tests the Universal Serial Bus (USB) controller(s).

Runs a test for no more than the specified number of minutes <minutes>.

Uses a faster algorithm to conduct a specific test if one is available.

Stops the tests if an error is encountered.

Specifies the device on which to run test.

20 omdiag: Using the Diagnostic Service

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

Command level 1

Command level 2

storage cddvd

omdiag about

Command level 3

floppy

raidctrl

idedevdiag

sasdevdiag

scsidevdiag

name=value pair

passes=<n> Runs a test n time(s).

time= <minutes>

quicktest=

haltonerror=

Device=

Use

Runs the CD/DVD drive test.

Runs the diskette drive test.

Runs the RAID control and attached device test.

Runs the IDE disk tests.

Runs Serial Attached SCSI (SAS), SAS RAID controller, and attached device tests.

Runs the SCSI controller and attached tape and hard drive tests.

Runs a test for no more than the specified number of minutes <minutes>.

Uses a faster algorithm to conduct a specific test if one is available.

Stops the tests if an error is encountered.

Specifies the device on which to run the test.

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

Product name : Server Administrator Version : 2.

x.x

Company : Dell Inc.

omdiag: Using the Diagnostic Service 21

omdiag about details=true

Use the omdiag about details=true command to see information about all of the Server Administrator programs that are installed. The following is example output from the omdiag about details=true command:

Product name : Server Administrator Version : 2. Copyright : Copyright (C) Dell Inc.

Company : Dell Inc. Contains : Instrumentation Service 5.

x.x

Storage Management Service 3.x. Diagnostic Service 3.x. Sun JRE - OEM Installed Version 1.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 2.x.

omdiag chassis

Use the omdiag chassis commands to perform tests on nonstorage components of a system, such as the memory, NICs, PCI, and ports.

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

omdiag chassis -?

Use the omdiag chassis -? command to see a list of all chassis components on the system.

omdiag chassis cmos

Use the omdiag chassis cmos command to test the system configuration information in the CMOS settings. The following test is performed:

• Checksum Test — Performs a checksum test on the CMOS memory to determine if any bytes are corrupt. This test scans the CMOS memory and calculates the checksum of the bytes read from the checksum range. The calculated result is compared with the results stored in the CMOS memory. If they match, the test succeeds; otherwise, the test logs errors.

22 omdiag: Using the Diagnostic Service

omdiag chassis memory

Use the omdiag chassis memory command to test the system's RAM. The following test is performed:

NOTE: Shut down all other programs before running this test.

NOTE: Sufficient swap-space (temporary storage space used during a move or reconfiguration) is needed to

support the demands of the memory test.

NOTE: This test checks only memory seen by the operating system on systems that have redundant memory

support (spare bank or mirroring).

• Pattern Test — Checks your system’s memory by using a data patterns test. These patterns test the memory's storage integrity and its ability to store data accurately. This test writes a pattern to each byte in the memory and reads the pattern back. This verifies that the data paths, error-correction circuits, and the memory devices themselves are working correctly.

omdiag chassis modem

Use the omdiag chassis modem command to run tests on all modems.

NOTE: This test runs on analog communication lines (regular telephone lines) and will not test a cable or Digital

Subscriber Link (DSL) modem. Currently, a test is not provided for testing cable or DSL modems; you can, however, test cable or DSL Internet connections. To test an Internet connection that uses a cable or DSL modem, you must use the network test.

NOTE: Shut down all other programs before running this test. If other programs use the modem, the test does not

run and you see "Cannot Run" in the Results window.

• Modem Test — Sends a series of AT command set commands to your modem to see if it is working. The AT command set is a series of industry-standard instructions for the modem to perform.

NOTE: The correct modem drivers, when required, should be installed for the modem diagnostic tests to run

and provide the best results. For systems running Red Hat Enterprise Linux, in some cases, the "setserial" command can be used to configure the modems without drivers.

The modem test performs the following tests:

– Hayes Basic Command Test— Uses the Hayes basic command set to exercise and diagnose the

functionality of the modem. The Hayes basic commands are written to the modem and the result codes are verified and displayed either textually or numerically. Only important commands that are common across different modems are used during this test.

– Hayes Extended Command Test — Uses the extended command group of the Hayes command

set to exercise and diagnose the functionality of the modem. The Hayes extended commands are written to the modem and the result codes are verified and displayed either textually or numerically. Only important commands that are common across different modems are used during this test.

omdiag: Using the Diagnostic Service 23

– S-Registers Test — Uses the selected range of S-Registers to exercise and diagnose the

functionality of the modem. The test saves the current S-register values, sets a new value, verifies that the new value can be read and is correct, and restores the original value. The result codes are verified and displayed either textually or numerically.

NOTE: In cases where the Windows registry with modem drivers is corrupted due to bad installs/uninstalls,

the modem diagnostic might give unexpected results.

• Broadcom Modem Test — Used for both external (for example, connected to a serial port) and internal modems (for example, connected to a PCI slot).

The Broadcom Modem test performs the following tests:

NOTE: The following tests are not supported on systems running a Red Hat Enterprise Linux

operating system.

– Broadcom Modem Dialtone Detection Test — Verifies the correct operation of the codec, DAA,

and control logic on the Broadcom V.92 56K modem. This is accomplished by detecting the presence of a dial tone on the telephone line. A telephone line must be attached to the modem for this test to pass. If a dialtone is not detected, a warning is reported.

– Broadcom Modem Loopback Test — Instructs the Broadcom V.92 56K modem to perform a

standard local analog loopback test. A test pattern is looped back and checked by the modem. The test fails if the modem reports any errors during the test.

– Broadcom Modem AT Command Test — Verifies the correct operation of the AT command

microprocessor and associated control functions on the Broadcom V.92 56K modem. A series of AT commands are issued and the responses are checked for correctness. Each command must correctly return "OK" or an error is reported.

omdiag chassis network

Use the omdiag chassis network command to test the NIC.

• Generic Network Diagnostic Test — The following two tests are available on all Dell™ supported NICs:

– NIC Communication Test — Checks whether the NIC under test is physically connected (wired)

to the network. It also checks whether the NIC has a valid IP address.

NOTE: The network team test is only available on systems running a supported Microsoft Windows

operating system.

– NIC Team Test — Checks whether the NIC under test is in team mode. NIC teaming is one

method for providing high availability and fault tolerance in systems.

The following test runs on the Broadcom NIC:

NOTE: The following Broadcom NIC tests are not supported on systems running a Red Hat Enterprise Linux 4 (for

Intel

x86 and Intel EM64T) operating system.

• Broadcom Network Diagnostic Test — Analyzes overall controller health by checking for I/O conflicts, memory faults, EEPROM operability, and transmit and receive functionality.

24 omdiag: Using the Diagnostic Service

• The following tests are available on Dell supported Broadcom NICs:

– BRCMNetwork Control Registers Test — Tests most of the internal registers on the chip. Each

chip contains many internal registers. Each register can contain some read-only bits and some read/write bits. This diagnostic tests read-only bits that cannot be overwritten, and tests if read/write bits can be written properly.

– BRCMNetwork MII Registers Test — Tests most MII registers on the chip. Each chip contains

many MII registers. Each MII register may contain some read-only bits and some read/write bits. This diagnostic tests read-only bits that cannot be overwritten, and tests if read/write bits can be written properly.

– BRCMNetwork EEPROM Test — Tests the EEPROM checksum of the bootstrap record and the

configuration block on the chip.

– BRCMNetwork Internal Memory Test — Tests most of the internal memory of the chip. Each chip

contains a certain amount of on-chip memory to support on-chip processor operations.

– BRCMNetwork Interrupt Test — Tests the interrupt capability of the chip by verifying that the

NDIS driver is able to receive interrupts from the NIC.

– BRCMNetwork MAC Loop–back Test — Verifies that the NDIS driver is able to send and receive

packets from the NIC. It issues IOCTL (Input Output Controls) to request driver setup (MAC layer loop back) in hardware.

– BRCMNetwork PHY Loop–back Test — Verifies that the NDIS driver is able to send and receive

packets from the NIC. It issues IOCTL (Input Output Controls) to request driver setup (PHY layer loop back) in hardware.

– BRCMNetwork On Chip CPU Test — Tests the internal processor(s) on the chip. The test will

halt all on-chip processors, download an executable binary to the processor memory, and execute the program.

– BRCMNetwork LED Test — Blinks the LEDs on the NIC.

– BRCMNetwork ASF Test — Tests various processor event registers and SMBus control registers.

Exercises ASF related hardware on the chip.

The following tests run on the Intel NIC:

• Intel FIFO Registers Test — Tests FIFO memory on the adapter by writing and reading patterns to and from the FIFO memory.

• Intel Network Diagnostic Test — Analyzes overall controller health by checking for I/O conflicts, memory faults, EEPROM operability, and transmit and receive functionality. The following tests are available on Dell–supported Intel NICs.

NOTE: The Intel PROSet management agent is required for the Intel network adapter diagnostics. If the

management agent is not installed (or partially installed), the Intel vendor tests are not available (only the

default network diagnostics are available). You can access the Intel PROSet from either the Installation and Server Management CD (version 8.x) or from support.dell.com. The Intel PROSet is listed under the Intel PRO

Family of Adapters.

omdiag: Using the Diagnostic Service 25

NOTE: The following tests are only available on systems running a supported Microsoft Windows operating system.

– Intel Control Registers Test — Checks for any conflicts in the I/O address and tests the

accessibility of the registers. This test includes all General Registers, Receive Registers, and Transmit Registers. It does not test the EEPROM Control/Data Register.

– Intel EEPROM Test — Verifies the integrity of data read from the EEPROM. This test completes a

write and read from the EEPROM and then compares the results for consistency.

– Intel Interrupt Test — Uses the Interrupt registers to confirm that all NIC interrupts work.

– Intel MAC Loopback Test — Tests the NIC’s ability to send and receive packets by sending packets to

itself. This test uses the MAC Loopback mode.

NOTE: The Intel MAC Loopback Test is not supported on the Intel PRO/1000 MF and the Intel PRO/1000 MT DP

network cards.

– Intel PHY Loopback Test — Tests the NIC’s ability to send and receive packets by sending packets

to itself. This test uses the PHY Loopback mode. Not all NICs support PHY Loopback.

– Intel Link Test — Checks the network connection, and the NICs send and receive functionality by

sending 1000 proprietary packets out on the network and retrieving those same packets.

The Intel Online Diagnostics tests and the Intel Offline Diagnostics tests are only available on systems running a supported Red Hat Enterprise Linux operating system.

– Intel Online Diagnostics Tests — Performs a limited set of tests without interrupting normal NIC

operation during the tests.

– Intel Offline Diagnostics Tests — Performs a full set of tests. This test might disrupt the normal

operation of the NIC.

omdiag chassis parallelport

Use the omdiag chassis parallelport command to test the parallel port, which is a high-speed communications port for attaching certain devices to your system.

The parallel port test writes a series of characters to the port and then reads it back again. If this test detects differences between the written and read character series it logs an error message and the test fails. The parallel port test performs the following tests:

• Mode Test — Tests the different modes of the Extended Capabilities Port (ECP). The following modes are tested:

– Standard Mode (unidirectional)

– Byte Mode (a bi-directional mode, also called Reverse Mode)

– Parallel Port FIFO Mode (SPP hardware-handshake)

– EPP Mode (may not be available depending on chipset)

– ECP FIFO Mode (ECP hardware-handshake)

26 omdiag: Using the Diagnostic Service

– FIFO Test Mode (test mode to determine FIFO depth)

– Configuration Mode (cnfgX registers are available)

NOTE: The Mode test may disrupt normal operation of a device connected to the parallel port, for example, a

printer that is printing.

• Parallel Port Register Test — Tests the parallel port registers using a write-read strategy, for example, writing some data into the register, reading the data of the same registry and verifying it against the data written (data-pattern, walking-bit). The following registers are tested:

– Standard Parallel Port (SPP) Registers: Control, Data, and Status Port registers

– Extended Parallel Port (EPP) Registers: Address and EPP Data Port registers

– Extended Capabilities Port (ECP) Register: Extended Control Register (ECR)

– ECP Configuration Registers A and B (cnfgA, cnfgB)

• FIFO Test — Configures the parallel port to the FIFO Test Mode. It detects the FIFO's depth, writes different data patterns to the FIFO, and reads the patterns back from the FIFO. If the data written and read are different, the test sends out an appropriate result.

• ECP Protocol Test — ECP protocol includes a simple compression scheme (maximum compression of 64:1) called Run-Length Encoding (consecutive repeated bytes are sent as a single byte with a repeatcount). This test configures the parallel port to FIFO Test Mode, tests if the compression is supported, and sends out an appropriate result.

NOTE: Turn off all connected external devices before running this diagnostic.

omdiag chassis pci

Use the omdiag chassis pci command to test the PCI bus and check all PCI devices.

The PCI test includes the boards configuration test, which checks for the presence of PCI capability and then scans all PCI devices for proper communication. PCI diagnostics enumerate the various kinds of buses on the system board. In addition to the PCI bus, the package enumerates SCSI, IDE, and USB buses. On systems running Microsoft Windows, the enumeration process requires that the WMI (Windows Management Instrumentation) services is running. The following tests are performed by the PCI test:

• PCI Device Configuration Test — Scans through the PCI bus, enumerating all the PCI devices. This test examines the interrupt requests (IRQs) for each PCI device in use and issues a warning for those devices that share the same ones. This test also checks if the driver for the device is loaded and functioning correctly.

omdiag: Using the Diagnostic Service 27

omdiag chassis rac

Use the omdiag chassis rac command to run the tests on the remote access controller (RAC).

The RAC test provides IT administrators with continuous access to their systems, enabling a full range of systems management functions including monitoring, controlling, updating, and recovering. The RAC can be connected to a PCI expansion slot or embedded on the system board. DRAC III and above are enumerated and tested, whereas DRAC II is only enumerated, but not tested.

NOTE: In order to run the diagnostics, all the RAC drivers are required to be installed on the system, and the RAC-

specific services are required to be running on the system.

NOTE: In cases where the Windows registry is corrupted due to bad installs/uninstalls of RAC drivers, the RAC

diagnostic might give unexpected results

The following tests are performed by the RAC test:

• POST Result Test — Runs the power–on self–test (post) on the RAC hardware and firmware, gets the result of the POST operation, and reports any errors.

• In–Band Access Test — Checks the status of the RAC–specific service running on the system that is used for the in–band access of the RAC (through the operating system).

• Out–of–Band Test — Verifies the connectivity to the out–of–band interface of the RAC (the NIC on the RAC). It first checks if the NIC is enabled on the RAC and if a valid IP address is assigned to it. It then checks if it can connect to the HTTPS and FTP services running at this IP address.

omdiag chassis serialport

Use the omdiag chassis serialport command to test all 9-pin (AT) and 25-pin (PC, XT, and PS/2) serial ports. The following tests are performed:

• Serial Port Register Test — Writes different data-patterns to the read-write registers of the serial port, reads them back, and verifies the data against the written data. If this test detects differences between the written and read data, it logs an error message and the test fails.

• Internal Loopback Test — Tests serial ports that have an internal loop-back mode, specifically for testing. This test uses the internal loop-back mode to transmit and receive data and compare that the data received is the same as the data transmitted. The write-only and read-only buffers are tested. Error conditions such as buffer overrun are also detected.

• Baud Rate Test — Verifies the speed of the port against the system clock to ensure that the baud rate is within an acceptable range. The baud rate is controlled by writing appropriate values to the Divisor Latch bytes. The port transmits and receives (in internal loop-back mode) for 2 seconds, and checks whether the number of characters transmitted and received is two times the baud rate divided by 10 (10 bits are used to transfer 1 byte).

• Interrupt Test — Verifies that the serial port is generating or receiving interrupt requests (IRQs) correctly when key events occur. Otherwise error events are generated and the test fails.

NOTICE: This test may disrupt normal operation of a device connected to the serial port, for example, a modem. It

is recommended that any connected external device is turned off when this test is running.

28 omdiag: Using the Diagnostic Service

omdiag chassis usbctrl

Use the omdiag chassis usbctrl command to test the USB controller(s).

The USB test performs the following test:

NOTE: The following test is available on systems running supported Microsoft Windows and Red Hat Enterprise

Linux (version 3) and later operating systems.

NOTE: On systems running supported Red Hat Enterprise Linux operating systems, connecting or removing a USB

device from the server while the diagnostics enumeration is in progress, may cause the system to hang.

• USB Node Detection Test — Scans the USB bus, enumerating all the USB devices connected to the USB controller being tested. USB diagnostics enumerate the various kinds of USB controllers on the system board. In addition to the on-board USB controllers, the package enumerates USB controller cards inserted in the PCI slot and any other USB devices connected to the ports of these USB controllers. This test examines hot plugged and unplugged devices from the tested USB controller.

omdiag storage

Use the omdiag storage commands to perform tests on your system’s storage components, such as the CD drive, DVD drive, diskette drive, hard drive, tape drive, and SCSI or RAID controller.

omdiag storage -?

Use the omdiag storage -? command to see a list of all storage components on the system.

omdiag storage cddvd

Use the omdiag storage cddvd command to test CD and DVD drives.

The CD or DVD drive test runs several tests on a CD or DVD drive to make sure the drive is working properly. This test determines how many CD or DVD drives are in your system and tests only those drives that support the appropriate CD or DVD media. To run this test, you must have a data CD or DVD (such as a program CD or DVD or your system's recovery CD or DVD) in the drive to be tested. Standard music CDs are not suitable for testing.

NOTE: USB CD and DVD drives present at enumeration should not be disconnected at the time of testing if the USB

CD or DVD drive is being tested. A CD must be present in the CD drive being tested.

If there is no data CD or DVD present in the drive to be tested, you will see the following error message:

Media not present in the drive, or the device may have become disconnected, or the cable may be bad. Make sure that the cable is properly connected. Insert media in the drive and run the test again.

omdiag: Using the Diagnostic Service 29

The CD/DVD drive test performs the following tests:

• Extremity Test — Conducts negative testing on the drive. The drive is requested to execute illegal commands to access particular extreme sectors or play illegal lists. The test is expected to fail.

• Driver Mechanism Test — Performs the eject, close, and stop actions to determine if the drive servo mechanism, the door motor, and the spindle motor are operating correctly. Slim CD/DVD drives like those generally available in portable and rack-optimized systems do not allow retracting of the eject tray. This kind of CD/DVD drive cannot be tested for drive mechanism test eject and close functionality.

• Read Exerciser Test — Accesses and reads the actual contents of the media. If the data is in the format of files, the data is read sector by sector into a temporary memory buffer during the first attempt. During subsequent reads, the read pattern will follow a random set of sectors for the quick test and a sequential set of sectors for the complete test. This data is then compared with data that was previously stored in the memory to ensure the correctness of the read operation.

NOTICE: Allow sufficient time for the operating system to detect the presence of media in the drive before running

the CD/DVD diagnostics.

NOTE: This is the longest test in the CD/DVD diagnostics.

NOTE: Multi-session CDs are not supported by this test on supported Red Hat Enterprise Linux operating systems.

If the test fails, insert a different CD without multiple sessions and run the test again.

NOTE: Defective CDs may cause CD drive test failures. If an error occurs, insert a different CD and run the

test again.

omdiag storage floppy

Use the omdiag storage floppy command to test the diskette drive.

The diskette drive test examines your diskette drive using a series of seek and read tests to see if your drive is working correctly. You must insert a diskette into the diskette drive in order to run this test. The diskette test performs the following tests:

• Linear seek Test— Tests the integrity of the diskette drive mechanics. Moves the diskette drive heads continuously, starting from the center of the diskette and moving outward to the maximum track, one track at a time, until the entire disk is tested.

• Random seek Test — Tests the integrity of the diskette drive mechanics. Moves the diskette drive heads to several hundred random locations on the diskette, one track at a time.

• Funnel seek Test — Tests the integrity of the diskette drive mechanics. Moves the diskette drive heads continuously in a funnel fashion. For example, the test moves the heads from the first track on the disk to the last, then to the second track, and from the second to the last track, and then to the third track, and so on.

30 omdiag: Using the Diagnostic Service

+ 186 hidden pages