Om Config

11/23/2017 Dell server utility : omreport / omcong Hall Of Tips
Hall Of Tips
Search
/Bash /Admin /Linux /Network /Security /DB /Misc
Dell server utility : omreport / omconfig

By Pier April 27, 2012 Linux, Sysadmin 9 Comments
Introduction
This post is a
[hide]
comprehensive
introduction to Dells Introduction
omreport and 1 Generalities
omconfig command 1.1 The command
line utilities. level
1.2 The different
omreport is the command line tool that allow us to domains
check server setup, when omconfig is the tool with 1.2.1 The
which we will modify the server setup. system
domain
Note : please refer to the Omreport script example page for a
1.2.2 The
comprehensive example about the omreport utility usage in a
chassis
shell script.
domain
1.2.3 The

storage
domain
http://cavepopo.hd.free.fr/wordpress/linux/dell-server-utility-omreport/ 1/23
1.3 The omreport

help
1.4 The severity
status
1 Generalities 2 Syntax & practical

examples
2.1 General
1.1 The command level commands
2.2 System domain
The omreport utility syntax is divided in multiples levels,
commands
three to be accurate.
2.3 Chassis domain
Those levels are defined as shown in the following commands
examples : 2.4 Storage domain
commands
3 Formatting the
example 1 omreport chassis nic omreport output
4 The omconfig utility
example 2 omreport system esmlog
4.1 Clearing logs
4.1.1 About
the impact of
As a general rule we may state that : log in
reported state
is the command utility (may be omreport of a server
or omconfig for example) 4.2 Miscellaneous
omconfig
is the domain to which the level 1 utility commands
applies
mainly contains either an option or a

parameter passed to the level 2 domain. This is used to change (typical omconfig
usage) or request (typical omreport usage) a value. It might also be used as a way to
define a more specific field within the given domain (as in example 1: the nic (network
interface) which belongs to the chassis domain)
1.2 The different domains

The omreport utility can be used to access multiples hardware components (controller cards,
network interfaces etc) as well as software components (server purchasing cost, dell service tag etc).
All those components are sorted in 3 different categories (which will be used as a syntax
element), i call them domains in this post. In this section i list those domains and their corresponding
objects.
1.2.1 The system domain

This domain is a kind of summary for the two other domains, it also about software pieces,
see the following list for some of the available components. To get a health status of your
whole server you will use this domain (see Retrieving an health status for the whole system).
1. Logs
2. Shutdown actions
3. Threshold
4. Ownership information
5. Recovery actions configuration informations
6. SNMP (traps setup)
1.2.2 The chassis domain

This domain is mainly about hardware devices, see the following list for some of the
available components.
1. Fans
2. Server chassis
3. Memory
4. Power supplies
5. Temperature sensors
6. Voltage sensors
7. BIOS
8. BMC network card (remote access administration network interface)
9. Network interface(s)
10. Parallel and/or serial port(s)
11. Processor(s)
1.2.3 The storage domain

As its name suggests this domain is about storage devices and storage related components,
please report to the following list for informations.
1. Physical disk(s)
2. Virtual disk(s)
3. Controller (such as PERC controller)
4. Enclosure
5. Battery (the controller battery)
6. Connector(s)
1.3 The omreport help

The omreport utility may provides you with help (and a quick description) for the any
command (level 1, 2 or 3 commands). In order to get this there is two syntax :
1. Using omhelp utility
omhelp<level_1_command><level_2_command><level_3_command
Note : Any of the level_[1-3] parameters are optional
2. Using -? option (a kind of -h or --help bash equivalent)
<level_1_command><level_2_command><level_3_command>?
Note : with this syntax only command of level_2 or level_3 are optional
From my point of view the second syntax is much more intuitive, but it is up to you and
your needs.
Help usage examples

omhelp
#omhelpomreportchassismemory
memorySystemmemoryconfiguration.
Validparametersare:
index=<number>Displaysmemorydevicepropertiesfora

-?
#omreportchassismemory?
Validparametersare:
index=<number>Displaysmemorydevicepropertiesfora
1.4 The severity status

Severity could be one of the following values :
1. Ok # everything is OK
2. Non-Critical # A warning occurs, it does not run your system a straight forward risk
but it needs attention. Your system may not be in optimum conditions.
3. Critical # your system is in bad condition! you may fix whatever causes this error
ASAP.
2 Syntax & practical examples

As said in Chapter 1 there is 3 different domains for the omreport command line utility: ,
and . There is quite some commands applicable to each domains. You will find here
is some of the commands you may need as an administrator. They are sorted by domains.
2.1 General commands

Check your tool version and other information
This command will display version of the actual omreport product utilities and components.
#omreportaboutdetails=true
Productname:ServerAdministrator
Version:6.5.0
Copyright:Copyright(C)DellInc.19952011Allrights
Company:DellInc.

Contains:AlibraryforparsingGNUstylecommandline

[...]

:SystemUtilitiesPackage/LibsysfsforLSIsto
:iDRACCommandInterface6.5.0
2.2 System domain commands

This command will display all available commands within the given domain.
#omreportsystem?

systemSystemcomponentproperties.

Theavailablecommand(s)are:

CommandDescription
alertactionAlertaction(s)properties.
alertlogViewalertlog.
assetinfoAssetinformation.
cmdlogViewcommandlog.
esmlogViewhardware(EmbeddedSystemManagement)
eventsVieweventsenable/disablesettings.
operatingsystemOperatingsystemproperties.
platformeventsPlatformeventreport.
pedestinationsPlatformeventdestinations.
postlogViewPowerOnSelfTest(POST)log.
recoveryAutorecoveryproperties.
shutdownShutdownproperties.
thrmshutdownThermalshutdownproperties.
summarySummaryofallsystemcomponents.
versionVersionreportforallupdateablecomponent
Note : having a command listed here DOES NOT mean that the corresponding feature is
available on your system!
This command display information about components such as processor, memory, PCI slot,
server model, name and service tag and more

Note : The following excerpt is not complete, i just extracted some information, you
will get more than this when launching the system summary command.
#omreportsystemsummary

[...]

ChassisInformation
ChassisModel:PowerEdgeR710
ChassisServiceTag:BDF1P4J
ExpressServiceCode:24755939443
ChassisLock:Present
ChassisAssetTag:

RemoteAccessInformation
RemoteAccessDevice:iDRAC6Enterprise
vFlashMedia:Absent

Processor1
ProcessorBrand:Intel(R)Xeon(R)CPU
ProcessorVersion:Model26Stepping5
Voltage:1200mV

Processor2
ProcessorBrand:Intel(R)Xeon(R)CPU
ProcessorVersion:Model26Stepping5
Voltage:1200mV

[...]

Memory
TotalInstalledCapacity:4096MB
MemoryAvailabletotheOS:3943MB
TotalMaximumCapacity:196608MB
MemoryArrayCount:1

[...]

BIOSInformation
Manufacturer:DellInc.
Version:1.3.6
ReleaseDate:10/30/2009
: The storage domain will NOT be checked by the following

command, for info about checking the storage health status please refer to 2.4
Storage domain commands.
This command display a unique health status for all system AND chassis components.
#omreportsystem
If everything is fine :
#omreportsystem
Health

SEVERITY:COMPONENT
Ok:MainSystemChassis

Forfurtherhelp,typethecommandfollowedby?
If anything is wrong you will get the status as : (with the location of the failing
component)
#omreportsystem
Health

SEVERITY:COMPONENT
Critical:MainSystemChassis

Note : When something bad like this is happening, you may want to get more
details about the failing component :
In this case the domains where the failure occurs is Main System Chassis which
corresponds to the Chassis domain, so you should now ask the omreport to report
about this very component (see Retrieving the health status for the chassis).
This command will list all firmwares / drivers version related to updateable components.
#omreportsystemversion
VersionReport

MainSystemChassis

Name:BIOS
Version:2.6.1
Updateable:N/A

Name:BMC
Version:2.37
Updateable:N/A

Software

Name:RedHatEnterpriseLinuxServer
Version:release5.4(Tikanga)Kernel2.6.18164.el5(x8
Updateable:N/A

Name:DellServerAdministrator
Version:5.3.0
Updateable:N/A

PERCFirmware

Name:PERC5/iIntegrated
Version:5.1.10040
Updateable:N/A
I will not be listing all possible commands and their output, but from what i found
useful was:
1. Display the Hardware logs
omreportsystemesmlog#thefirstlineofthisreportre
2. The alert log
omreportsystemalertlog
3. The postlog (messages from the POST: Power On Self Test)
omreportsystempostlog
2.3 Chassis domain commands

#omreportchassis?

chassisChassiscomponentproperties.


CommandDescription
pwrmonitoringPowermonitoringproperties.
pwrmanagementPowermanagementproperties.
hwperformanceHardwareperformanceinformation.
acswitchACswitchsettings.
biosBIOSproperties.
biossetupBIOSsetupconfiguration.
bmcRemoteAccessinformation.
SUBCOMMANDDEPRECATIONWARNING:
Thissubcommandisdeprecatedandwillbe
asubsequentrelease.
Usethesubcommand"remoteaccess"instead
fansFanprobe(s)properties.
fruSystemComponents(FRU)information.
ledsChassisLEDsettings.
firmwareFirmwareproperties.
infoChassisinformation.
intrusionChassisintrusionstatus.
nicsNetworkinterfacecard(s)andTeamInterfac
portsPort(s)properties.
frontpanelFrontpanelbuttoncontrolsettings.
processorsProcessor(s)properties.
pwrsuppliesPowersupply(s)properties.
slotsSlot(s)properties.
tempsTemperatureprobe(s)properties.
voltsVoltageprobe(s)properties.
remoteaccessRemoteAccessinformation.
batteriesBattery(s)properties.
removableflashmediaRemoveableflashMediaproperties
Note : having a command listed here DOES NOT mean that the corresponding feature is
available on your system!
if everything is OK :
#omreportchassis
Health

MainSystemChassis

SEVERITY:COMPONENT
Ok:Fans
Ok:Intrusion
Ok:Memory
Ok:PowerSupplies
Ok:Processors
Ok:Temperatures
Ok:Voltages
Ok:HardwareLog
Ok:Batteries

If anything is not really OK! :
#omreportchassis
Health

MainSystemChassis

SEVERITY:COMPONENT
Ok:Fans
Ok:Intrusion
Ok:Memory
Critical:PowerSupplies
Ok:Processors
Ok:Temperatures
Ok:Voltages
Ok:HardwareLog
Ok:Batteries

Note : Unfortunately omreport does not use the return code facility, which means that
regardless of how the health of the checked domain was reported you will only get a 0
status if the command went ok. So to use the omreport command within script you
will have to search for specific patterns inside the output, one good news is that you
can easily format the output of omreport comman (see Formatting the omreport
output section)
omconfigchassisbiossetupattribute=nic1setting=enabledwit
2.4 Storage domain commands

#omreportstorage?

storageDisplaystoragecomponentproperties.


CommandDescription
adiskDisplayarraydisk(s)properties.DEPRECATE
pdiskDisplayphysicaldisk(s)properties.
vdiskDisplayvirtualdisk(s)properties.
controllerDisplaycontroller(s)properties.
enclosureDisplayenclosureproperties.
batteryDisplaybatteryproperties.
globalinfoDisplayglobalstorageproperties.
connectorDisplayconnectorproperties.
cachecadeDisplaycachecade(s)properties.
In order to be able to get the list of physical HDDs for your system, your first need to
know the number of controller(s) and their respective ID. You can get a list of
available controller(s) ID by issuing :
omreportstoragecontroller|grepID
This should gives you this kind of output :
ID:0
SlotID:Embedded
SCSIInitiatorID:NotApplicab
In this case there is only one controller, its type is embedded (this means it is an
integrated controller, a e.g : PERC5/I, the I at the end actually means Integrated).
Now, with the previously retrieved controller ID, we are able to get the list of physical
HDDs per controller :
omreportstoragepdiskcontroller=0
This should gives you this kind of output :
1 ID:0:0:0
2 MirrorSetID:NotApplicable
3 UsedRAIDDiskSpace:931.00GB(999653638144b
4 AvailableRAIDDiskSpace:0.00GB(0bytes)
5 VendorID:ATA
6 ProductID:WDCWD10EARS00MVWB0
7 ID:0:0:1
11 VendorID:ATA
12 ProductID:WDCWD10EARS00MVWB0
13 ID:1:0:4
17 VendorID:DELL
18 ProductID:ST31000340NS
19 ID:1:0:5
23 VendorID:DELL
24 ProductID:ST31000340NS
In this example we can see that there are 4 physical HDDs (as there are 4 different ID
lines @lines n1,7,13,19), each ID lines are followed by 5 other lines including
informations about HDDs.
In case you only want to know how many HDDs there are without other information,
you can use this :
omreportstoragepdiskcontroller=0|grepw"^ID"
Which gives :
ID:0:0:0
ID:0:0:1
ID:1:0:4
ID:1:0:5
The RAID configuration is actually nothing but the virtual disk architecture, this is
why we can use the following command to retrieve it :
omreportstoragevdiskcontroller=0
Note : To achieve this you need to know the controller(s) ID, see the previous item (Retrieve the
list of physical HDDs) to find it out.
This should print something like :
ListofVirtualDisksonControllerPERC5/iIntegrated(Emb

ControllerPERC5/iIntegrated(Embedded)
ID:0
Status:Ok
Name:system
State:Ready
Encrypted:NotApplicable
Layout:RAID1
Size:931.00GB(999653638144bytes)
DeviceName:/dev/sda
BusProtocol:SATA
Media:HDD
ReadPolicy:NoReadAhead
WritePolicy:WriteThrough
CachePolicy:NotApplicable
StripeElementSize:64KB
DiskCachePolicy:Enabled

ID:1
Status:Ok
Name:Seances
State:Ready
Layout:RAID0
Size:1,862.00GB(1999307276288bytes)
DeviceName:/dev/sdb
BusProtocol:SATA
Media:HDD
ReadPolicy:NoReadAhead
WritePolicy:WriteThrough
CachePolicy:NotApplicable
StripeElementSize:64KB
DiskCachePolicy:Enabled
From the omreport command line tool it is possible to do that for a given virtual disk.
We first need to get the ID of each available virtual disk(s) for each controller ID of our
system, which has already been shown in the Retrieve the RAID configuration.
Once we got this list of virtual disk, we can just use those information to get the full
list of physical disk(s) for a given virtual disk, as :
omreportstoragepdiskcontroller=0vdisk=0
Which print something like :
ListofPhysicalDisksbelongingtosystem

ControllerPERC5/iIntegrated(Embedded)
ID:0:0:0
Status:Ok
Name:PhysicalDisk0:0:0
State:Online
PowerStatus:NotApplicable
BusProtocol:SATA
Media:HDD
Revision:51.0AB51
FailurePredicted:No
Certified:NotApplicable
EncryptionCapable:No
Progress:NotApplicable
MirrorSetID:NotApplicable
Capacity:931.00GB(999653638144bytes)
UsedRAIDDiskSpace:931.00GB(999653638144bytes)
AvailableRAIDDiskSpace:0.00GB(0bytes)
HotSpare:No
VendorID:ATA
ProductID:WDCWD10EARS00MVWB0
SerialNo.:WDWCAZA904698846988
PartNumber:NotAvailable
NegotiatedSpeed:NotAvailable
CapableSpeed:NotAvailable
ManufactureDay:NotAvailable
ManufactureWeek:NotAvailable
ManufactureYear:NotAvailable
SASAddress:1221000000000000

ID:0:0:1
Status:Ok
Name:PhysicalDisk0:0:1
State:Online
PowerStatus:NotApplicable
BusProtocol:SATA
Media:HDD
Revision:51.0AB51
FailurePredicted:No
Certified:NotApplicable
EncryptionCapable:No
Progress:NotApplicable
MirrorSetID:NotApplicable
Capacity:931.00GB(999653638144bytes)
UsedRAIDDiskSpace:931.00GB(999653638144bytes)
AvailableRAIDDiskSpace:0.00GB(0bytes)
HotSpare:No
VendorID:ATA
ProductID:WDCWD10EARS00MVWB0
SerialNo.:WDWCAZA948818988189
PartNumber:NotAvailable
NegotiatedSpeed:NotAvailable
CapableSpeed:NotAvailable
ManufactureDay:NotAvailable
ManufactureWeek:NotAvailable
ManufactureYear:NotAvailable
SASAddress:1221000001000000
There are quiet a lot of info in there and i am sure you know which one you want
3 Formatting the omreport output

The omreport utility allows you to format the output as you wish, here is a quick guide to use this
ability.
Check the available formatting option using the -? command, as :
[root@machine~]#omreport?

[...]

fmt<lst|tbl|ssv|cdv|xml>Formatforoutputresults,default
Where:lstListformat.
tblTableformat.
ssvSemicolonseparatedfor
cdvCustomdelimitersepara
xmlRawXMLformat.
outc<file>Redirectoutputtofile,deleteoldifexists
OR
outa<file>Redirectoutputtofile,appendtooldifexi
OR
OutputmayalsoberedirectedusingOperatingSystemfacilitie
This output shows quite straight forward usable formatting option. One good news is the
cdv option that allows you to specify your own separator (sweet). To specify this
customized separator you just need to use the following command :
omconfigpreferencescdvformatdelimiter=<separator>
Where separator can be any of :
Note : the default cdv is set to the .
4 The omconfig utility
This section is about miscellaneous omconfig and hopefully handy commands. omconfig is the
command used to modify machine setup, when omreport is the tool that allow us to only check the
same machine setup.
4.1 Clearing logs

Here is a quick (but no so dirty?) summary about the clear log facility provided by omconfig.
The following command can be customized to clear any logs, you will just have to
adapt the log name according to the omconfig system -?output
omconfigsystem<log_to_be_cleared>action=clear
As i am a really cool guy i did it and i offer it to you

Possible values (logs) for omconfig systemcommand
alertlog
This is the log where alerts (!) are stored
cmdlog
This where the launched commands (such as root login) are stored
esmlog
This the hardware log, any hardware failure will be stored in there.
example with the hardware log (esmlog)
[root@test~]#omconfigsystemesmlogaction=clear
EmbeddedSystemManagement(ESM)logclearedsuccessfully.
4.1.1 About the impact of log in reported state

of a server
Clearing logs (especially the hardware log) can be mandatory to get the actual state of a
given server, as long as you keep a log containing faulty hardware the report tool will
report a NON-OK state in both Hardware log and Main System Chassis section.
As a demonstration for the above statement check this out :

This server is not faulty anymore, i do fix the issue (which was a dead Physical drive inside
a RAID1 array), but as you can see it is still reported as Faulty by the script (see Omreport :
script example to understand how is buit this output).
Reported as faulty
Thisisanautomaticallygeneratedemailby"/Admin/bin/Hard

~~~~~~~~~~~SYSTEM~~~~~~~~~~~

[MainSystemChassis]>[Critical]<

~~~~~~~~~~~CHASSIS~~~~~~~~~~~

[Fans]>[Ok]
[Intrusion]>[Ok]
[Memory]>[Ok]
[PowerSupplies]>[Ok]
[Processors]>[Ok]
[Temperatures]>[Ok]
[Voltages]>[Ok]
[HardwareLog]>[Critical]<
[Batteries]>[Ok]

~~~~~~~~~~~STORAGE~~~~~~~~~~~

[vdisk_0]>[Ok]
[enclosure_0]>[Ok]
[battery_0]>[Ok]
[controller_0]>[Ok]
[pdisk_0]>[Ok]
[pdisk_1]>[Ok]
[connector_0]>[Ok]
[connector_1]>[Ok]
Now i clear the esmlog
[root@TestComputer~]#omconfigsystemesmlogaction=clear
EmbeddedSystemManagement(ESM)logclearedsuccessfully.
Here is how the same computer is now reported
Thisisanautomaticallygeneratedemailby"/Admin/bin/Hard

~~~~~~~~~~~SYSTEM~~~~~~~~~~~

[MainSystemChassis]>[Ok]

~~~~~~~~~~~CHASSIS~~~~~~~~~~~

[Fans]>[Ok]
[Intrusion]>[Ok]
[Memory]>[Ok]
[PowerSupplies]>[Ok]
[Processors]>[Ok]
[Temperatures]>[Ok]
[Voltages]>[Ok]
[HardwareLog]>[Ok]
[Batteries]>[Ok]

~~~~~~~~~~~STORAGE~~~~~~~~~~~

[vdisk_0]>[Ok]
[enclosure_0]>[Ok]
[battery_0]>[Ok]
[controller_0]>[Ok]
[pdisk_0]>[Ok]
[pdisk_1]>[Ok]
[connector_0]>[Ok]
[connector_1]>[Ok]
4.2 Miscellaneous omconfig commands

This section will show some omconfig commands.
Change power management settings to
omconfigchassispwrmanagementprofile=maxperformance
Activate the CPUs
omconfigchassisbiossetupattribute=cpuhtsetting=enabled
Activate the CPUs
omconfigchassisbiossetupattribute=cputurbomodesetting=en
Change the NIC settings : Activate the
omconfigchassisbiossetupattribute=nic1setting=enabledwit
Select the display text

Set the LCD to its default value :

omconfigchassisfrontpanellcdindex=1config=default
On my testing poweredge 2950 the default value was
Set the LCD to a custom text :
omconfigchassisfrontpanellcdindex=1config=customtext
This would set the LCD display to
Generate a (such as a PERC 6/E controller)

In the following example you choose the controller using its ID (check the available
controllers IDs with the omreport storage controller command), the log is then
generated in /var/log/ directory. In my case the name was lsi_0318.log, i assume
the log name is built under the following pattern :
<controller_brandORname>_short-date.log
omconfigstoragecontrolleraction=exportlogcontroller=1
Tagged on: deleting old omreport error messages, dell, omconfig, omconfig tutorial,
omreport, omreport tutorial, open manage, poweredge, server, sysadmin
Linux command tips : find
Bash scripts examples : Omreport script
9 thoughts on Dell server utility : omreport /

omconfig
Maaz Khalid
October 30, 2017 at 10:35
1. Very Informative, Thanks a ton.

Reply

Pier Post author
October 30, 2017 at 11:47
A. Youre very welcome !

Reply
Tim
January 16, 2017 at 16:02
2. Im finding that running the omconfig commands to clear the logs is not working. I
get a response back saying that the log has been cleared, yet events are still
present.?
Reply
Pier Post author

January 18, 2017 at 19:02
A. Hi Tim,
I do not have any dell server available at the moment, but I will check asap, and
post the answer (if I happen to find one :) ) here.
Regards
Reply
3. Pingback: Install Dell Open Manage software on Linux Server Linux notes
Youssef ASEBRIY
November 26, 2014 at 13:09
4. This is very detailed

Nice Tutorial!
Thanks.
Reply
Pier Post author

November 26, 2014 at 17:32
A. Youre welcome Youssef !

Reply
DannetStudio
May 5, 2014 at 00:59
5. Thank you very much, really usefull guide!

Reply
6. Pingback: About omreport | Miscellaneous musings in beta
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment
Name *
Email *
Website
This site supports SyntaxHighlighter via WP SyntaxHighlighter. It can highlight your code.
Paste your code in the comment form, select it and then
click the language link button below. This will wrap your code in a <pre> tag and format it
when submitted.

Bash shell | C | C# | C++ | CSS | Diff | HTML | Java | JavaScript | PHP | Patch | Perl | Plain Text |
PowerShell | Python | Ruby | Ruby on Rails | SQL | Shell | XHTML | XML | XSLT |
Post Comment
NAVIGATION CATEGORIES
Welcome to the Hall of Tips ! Select Category
Site Map
All posts on one page !
Copyright 2017 Hall Of Tips | Theme by: Theme Horse | Powered by:
WordPress
17d14h 5m # 0.05-0.06-0.1

Om Config

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Om Config

Încărcat de

Drepturi de autor:

Formate disponibile

11/23/2017 Dell server utility : omreport / omcong Hall Of Tips

/Bash /Admin /Linux /Network /Security /DB /Misc

Dell server utility : omreport / omconfig

1.3 The omreport

1 Generalities 2 Syntax & practical

mainly contains either an option or a

1.2 The different domains

1.2.1 The system domain

1.2.2 The chassis domain

1.2.3 The storage domain

1.3 The omreport help

1. Using omhelp utility

Note : Any of the level_[1-3] parameters are optional

2. Using -? option (a kind of -h or --help bash equivalent)

Help usage examples

1.4 The severity status

2 Syntax & practical examples

2.1 General commands

2.2 System domain commands

: The storage domain will NOT be checked by the following

2. The alert log

3. The postlog (messages from the POST: Power On Self Test)

2.3 Chassis domain commands

If anything is not really OK! :

2.4 Storage domain commands

This should gives you this kind of output :

This should gives you this kind of output :

Which print something like :

3 Formatting the omreport output

Check the available formatting option using the -? command, as :

Where separator can be any of :

Note : the default cdv is set to the .

4 The omconfig utility

4.1 Clearing logs

As i am a really cool guy i did it and i offer it to you

example with the hardware log (esmlog)

4.1.1 About the impact of log in reported state

As a demonstration for the above statement check this out :

Now i clear the esmlog

Here is how the same computer is now reported

4.2 Miscellaneous omconfig commands

Change power management settings to

Activate the CPUs

Activate the CPUs

Change the NIC settings : Activate the

Select the display text

On my testing poweredge 2950 the default value was

Set the LCD to a custom text :

This would set the LCD display to

Generate a (such as a PERC 6/E controller)

Linux command tips : find

Bash scripts examples : Omreport script

9 thoughts on Dell server utility : omreport /

1. Very Informative, Thanks a ton.

October 30, 2017 at 11:47

A. Youre very welcome !

Pier Post author

4. This is very detailed

Pier Post author

A. Youre welcome Youssef !

5. Thank you very much, really usefull guide!

6. Pingback: About omreport | Miscellaneous musings in beta

S-ar putea să vă placă și