Dell OpenManage Server Administrator Version 5.0 User Manual

Dell OpenManage™

Server Administrator

Version 5.0

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, Pentium, and Xeon are registered trademarks and Itanium and Intel386 are trademarks of Intel Corporation; VESA is a registered trademark of V ideo 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.

February 2006

Contents

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

What's New for Version 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

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

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

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

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

omdiag about. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

omdiag about details=true

omdiag chassis

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

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

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

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

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

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

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

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

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

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

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

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

Contents 3

omdiag storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . 36

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

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

omdiag system

omdiag system -?

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

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

4 omreport: Viewing System Status Using the

Instrumentation Service

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 41

omreport Command Summary

Help With the omreport Command

omreport about

omreport chassis Commands

omreport chassis omreport chassis acswitch omreport chassis batteries 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

4 Contents

omreport chassis processors. . . . . . . . . . . . . . . . . . . . . . . . 55

omreport chassis pwrsupplies omreport chassis remoteaccess omreport chassis slots omreport chassis temps omreport chassis volts

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

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

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

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

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . 61

. . . . . . . . . . . . . . . . . . . . . . . . . . 61

. . . . . . . . . . . . . . . . . . . . . 62

. . . . . . . . . . . . . . . . . . . . . . 62

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

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

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

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

5 omconfig: Managing Components Using the

Instrumentation Service

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . . 69

omconfig Command Summary

Help With the omconfig Command

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

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

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

omconfig about

omconfig chassis

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

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

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

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

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

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

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

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

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

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

Contents 5

omconfig chassis memorymode . . . . . . . . . . . . . . . . . . . . . . 94

omconfig chassis remoteaccess omconfig chassis temps omconfig chassis volts

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

6 omconfig system assetinfo: Editing Cost of

Ownership Values

omconfig System Asset Info Overview . . . . . . . . . . . . . . . . . . . . 121

User Level Required for Adding Asset Information

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

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

6 Contents

Adding Acquisition Information

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

Example Commands for Adding Acquisition Information

Adding Depreciation Information

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

Example Commands for Adding Depreciation Information

Adding Extended Warranty Information

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

Example Command for Adding Extended Warranty Information

Adding Lease Information

Example Command for Adding Lease Information

Adding Maintenance Information

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

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

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

Example Command for Adding Maintenance Information

. . . . . . . . 122

. . . . . . . . 123

. . . . . 124

. . . . . . . . 126

Adding Outsource Information. . . . . . . . . . . . . . . . . . . . . . . . . 127

Example Command for Adding Outsource Information

. . . . . . . . . . 127

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

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

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

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

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

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

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

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

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

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

. . . . . . . . . . 132

7 omreport rac: Viewing Remote Access

Controller Components

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . 133

omreport rac Command Summary

Help With the omreport rac Command

omreport rac authentication

Example Command for omreport rac authentication

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

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

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

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

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

omreport rac dialinusers

omreport rac dialoutusers

omreport rac network

omreport rac modem

omreport rac remote

omreport rac snmptraps

omreport rac users

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

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

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

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

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

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

omreport rac viewcertificate

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

Contents 7

8 omconfig rac: Managing the Remote

Access Controller

Conventions for Parameter Tables. . . . . . . . . . . . . . . . . . . . . . . 139

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

omconfig rac Command Summary

Help With the omconfig rac Command

omconfig rac authentication

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

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

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

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

omconfig rac network

Example Command

omconfig rac snmptraps

Example Commands

omconfig rac remote

Example Command

omconfig rac rmdialinuser

Example Command

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

8 Contents

omconfig rac rmdialoutuser

Example Command

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

omconfig rac rmsnmptrap

Example Command

omconfig rac rmuser

Example Command

omconfig rac reset

omconfig rac uploadcert

omconfig rac users

Example Command

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

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

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

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

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

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

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

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

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

9 Using the Storage Management Service . . . . . . . . . . . . 155

CLI Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Syntax for Required, Optional, and Variable Command Elements

User Privileges for omreport storage and omconfig storage

omreport Command

omreport Storage Help

omreport Controller Status

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

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

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

. . . . . . . . . 158

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

omconfig Global Commands

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 omconfig Reset Controller Configuration omconfig Create Virtual Disk 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. . . . . . 156

. . . . 159

Contents 9

omconfig Clear Foreign Configuration . . . . . . . . . . . . . . . . . . 177

omconfig Set Patrol Read Mode omconfig Start Patrol Read omconfig Stop Patrol Read

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

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

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

omconfig Virtual Disk Commands

omconfig Blink Virtual Disk

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . 186

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

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

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

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

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

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

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

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

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

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

. . . . . . . . . . . . . . . . . . . . . . . 184

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

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

. . . . . . . . . . . . . . . . . . . . . . . 186

. . . . . . . . . . . . . . . . . . 187

. . . . . . . . . . . . . . . . . . . 187

. . . . . . . . . . . . . . . . . . . . . . 188

10 Contents

omconfig Array Disk Commands

omconfig Blink Array Disk

. . . . . . . . . . . . . . . . . . . . . . . . 188

. . . . . . . . . . . . . . . . . . . . . . . . 189

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

. . . . . . . . . . . . . . . . . . . . . . . . 191

. . . . . . . . . . . . . . . . . . . . . . . . 192

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

. . . . . . . . . . . . . . . . . . . . . . . 189

. . . . . . . . . . . . . . . . . 190

. . . . . . . . . . . . . . . . . . . . . . . 190

. . . . . . . . . . . . . . . . . . . . 193

. . . . . . . . . . . . . . . . . . 193

. . . . . . . . . . . . . . . . . . . . . . . 194

. . . . . . . . . . . . . . . . . . . 195

. . . . . . . . . . . . . . . . . . . . 195

omconfig Clear Array Disk . . . . . . . . . . . . . . . . . . . . . . . . 196

omconfig Cancel Clear Array Disk

. . . . . . . . . . . . . . . . . . . . 196

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

. . . . . . . . . . . . . . . . . . . . . . . . . 197

. . . . . . . . . . . . . . . . . . . . . . 197

. . . . . . . . . . . . . . . . . . . 198

. . . . . . . . . . . . . . . . . . . . . . . . 199

. . . . . . . . . . . . . . . . . . . . . . . 199

. . . . . . . . . . . . . . . . . . . . . . . . 199

. . . . . . . . . . . . . . . . . . . . 200

. . . . . . . . . . . . . . . . . . . . 201

. . . . . . . . . . . . . . . 201

. . . . . . . . . . . . . . . . . . . . 202

. . . . . . . . . . . . . . . . . . . 202

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

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

. . . . . . . . . . . . 204

. . . . . . . . . . . 204

10 Working With CLI Command Results . . . . . . . . . . . . . . . 207

Output Options for Command Results . . . . . . . . . . . . . . . . . . . . . 207

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

. . . . . . . . . . . . . . . . . . . 207

. . . . . . . . . . . . . . . . . . . . 207

. . . . . . . . . . . . 209

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Index

Contents 11

12 Contents

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 5.0

• Added support for SUSE® LINUX Enterprise Server (version 9), SP3 for Intel® Extended Memory 64 Technology (Intel EM64T)

• Added support for the following RAID controllers: PERC 5/i Adapter, PERC 5/i Integrated, and SAS 5/iR Integrated

• Added support for the following Dell™ PowerEdge™ systems: 1900, 1950, 1955, 2900, and 2950

• Added support for the following new commands:

chassis remoteaccess

• Phasing out the following commands:

and

chassis rac,

omconfig chassis rac

omreport chassis bmc, omconfig chassis bmc, omreport

omreport chassis remoteaccess

and

omconfig

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.

Introduction 13

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

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

problems with the CLI.

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

omconfig system assetinfo: Editing

Using the Instrumentation Service

Commands

Using the Instrumentation Service

Cost of Ownership Values

omreport rac: Viewing Remote Access Controller Components

14 Introduction

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

Systems 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 15

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

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 17

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

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

omhelp: Getting Help With CLI Commands 19

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

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:

20 omhelp: Getting Help With CLI Commands

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>

omhelp: Getting Help With CLI Commands 21

22 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, Network Interface Controllers (NICs), CMOS, and more.

Most tests described in this section take less than one minute. Some tests 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 DSM SA Connection Service

(for systems running Microsoft Enterprise Server and Red Hat® Enterprise Linux) is not running, 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 dsm_om_connsvc (for systems running

SUSE® LINUX

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 23

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 the test.

24 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 an example output from the omdiag about command:

Product name : Dell OpenManage Server Administrator Version : 5.

x.x

Company : Dell Inc.

omdiag: Using the Diagnostic Service 25

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 an example output from the omdiag about details=true command:

Product name : Dell OpenManage Server Administrator Version : 5. 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 5.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.

26 omdiag: Using the Diagnostic Service

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.

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.

omdiag: Using the Diagnostic Service 27

• 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.

– 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 ATcommands are issued and the responses are checked for correctness. Each command must correctly return "OK" or an error is reported.

28 omdiag: Using the Diagnostic Service

omdiag chassis network

Use the omdiag chassis network command to test the NIC. Three main categories of diagnostic tests available are:

•

Generic Network Diagnostic Tests

•

Broadcom NIC Diagnostic Tests

•

Intel® NIC Diagnostic Tests

Generic Network Diagnostic Tests

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.

Broadcom NIC Diagnostic Tests

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.

omdiag: Using the Diagnostic Service 29

– 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.

Intel NIC Diagnostic Tests

The following tests are available on Dell supported Intel NICs:

NOTE: For systems that have a PCI-E Intel Network Interface Controller (NIC), Intel PROSet Utility for

Microsoft Device Manager is required for the Intel network adapter diagnostics on systems running a Microsoft Windows operating system. If you have a PCI-X Intel NIC, you may install either the Intel PROSet for Microsoft Device Manager or the Intel PROSet management agent to enable Intel network adapter diagnostics. If you have any other Dell-supported Intel NIC, you should install the Intel PROSet management agent. If these requirements are not met, the Intel vendor tests will not be available (only the default network diagnostics are available). You can access the Intel PROSet for Microsoft Device Manager from either the Dell PowerEdge™ Service and Diagnostic Utilities CD or from the Dell Support website at support.dell.com.

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

operating system.

– Intel FIFO Registers Test — Tests FIFO memory on the adapter by writing and reading patterns

to and from the FIFO memory.

– 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.

30 omdiag: Using the Diagnostic Service

+ 218 hidden pages