Dell server utility : omreport / omconfig

dell

Introduction

This post is a comprehensive introduction to Dell’s omreport and omconfig command line utilities.

omreport is the command line tool that allow us to check server setup, when omconfig is the tool with which we will modify the server setup.

Note : please refer to the Omreport script example” page for a comprehensive example about the omreport utility usage in a shell script.

 

 

 

1 Generalities

1.1 The command “level”

The omreport utility syntax is divided in multiples “levels”, three to be accurate.

Those levels are defined as shown in the following examples :

level 1 level 2 level 3
example 1 omreport chassis nic
example 2 omreport system esmlog

 

As a general rule we may state that :

  • Level 1 is the command utility (may be omreport or omconfig for example)
  • Level 2 is the domain to which the level 1 utility applies
  • Level 3 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 level 2 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
      # omhelp omreport chassis memory
      memory           System memory configuration.
      Valid parameters are:
      index=<number>   Displays memory device properties for a particular connector.
    • -?
      # omreport chassis memory -?
      memory           System memory configuration.
      Valid parameters are:
      index=<number>   Displays memory device properties for a particular connector.

 

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: system, chassis and storage. 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.

    # omreport about details=true
    Product name : Server Administrator
    Version      : 6.5.0
    Copyright    : Copyright (C) Dell Inc. 1995-2011 All rights reserved.
    Company      : Dell Inc.
    Contains     : A library for parsing GNU style command line arguments 6.5.0
    
                 [...]
    
                 : System Utilities Package/Libsysfs for LSI storage libraries 2.1.0
                 : iDRAC Command Interface 6.5.0

 

2.2 System domain commands

 

  • Check the available commands on your system
    This command will display all available commands within the given domain.

    # omreport system -?
    
    system           System component properties.
    
    The available command(s) are:
    
    Command          Description
    alertaction      Alert action(s) properties.
    alertlog         View alert log.
    assetinfo        Asset information.
    cmdlog           View command log.
    esmlog           View hardware (Embedded System Management) log.
    events           View events enable/disable settings.
    operatingsystem  Operating system properties.
    platformevents   Platform event report.
    pedestinations   Platform event destinations.
    postlog          View Power On Self Test (POST) log.
    recovery         Auto recovery properties.
    shutdown         Shutdown properties.
    thrmshutdown     Thermal shutdown properties.
    summary          Summary of all system components.
    version          Version report for all updateable components.

Note : having a command listed here DOES NOT mean that the corresponding feature is available on your system!

 

  • Retrieve general system information
    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.

    # omreport system summary
    
    [...]
    
    Chassis Information
    Chassis Model              : PowerEdge R710
    Chassis Service Tag        : BDF1P4J
    Express Service Code       : 24755939443
    Chassis Lock               : Present
    Chassis Asset Tag          :
    
    Remote Access Information
    Remote Access Device       : iDRAC6 Enterprise
    vFlash Media               : Absent
    
    Processor 1
    Processor Brand            : Intel(R) Xeon(R) CPU           X5570  @ 2.93GHz
    Processor Version          : Model 26 Stepping 5
    Voltage                    : 1200 mV
    
    Processor 2
    Processor Brand            : Intel(R) Xeon(R) CPU           X5570  @ 2.93GHz
    Processor Version          : Model 26 Stepping 5
    Voltage                    : 1200 mV
    
    [...]
    
    Memory
    Total Installed Capacity   : 4096  MB
    Memory Available to the OS : 3943  MB
    Total Maximum Capacity     : 196608  MB
    Memory Array Count         : 1
    
    [...]
    
    BIOS Information
    Manufacturer               : Dell Inc.
    Version                    : 1.3.6
    Release Date               : 10/30/2009

 

  • Retrieving the health status for the whole system
    IMPORTANT NOTE
    : 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.

    # omreport system
    • If everything is fine :
      # omreport system
      Health
      
      SEVERITY : COMPONENT
      Ok       : Main System Chassis
      
      For further help, type the command followed by -?
    • If anything is wrong you will get the status as : (with the location of the failing component)
      # omreport system
      Health
      
      SEVERITY : COMPONENT
      Critical : Main System Chassis
      
      For further help, type the command followed by -?

      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“).

 

  • Check for updateable components version
    This command will list all firmwares / drivers version related to updateable components.

    # omreport system version
    Version Report
    
    ---------------------
    Main System Chassis
    ---------------------
    
    Name       : BIOS
    Version    : 2.6.1
    Updateable : N/A
    
    Name       : BMC
    Version    : 2.37
    Updateable : N/A
    
    ----------
    Software
    ----------
    
    Name       : Red Hat Enterprise Linux Server
    Version    : release 5.4 (Tikanga) Kernel 2.6.18-164.el5 (x86_64)
    Updateable : N/A
    
    Name       : Dell Server Administrator
    Version    : 5.3.0
    Updateable : N/A
    
    ---------------
    PERC Firmware
    ---------------
    
    Name       : PERC 5/i Integrated
    Version    : 5.1.1-0040
    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
      omreport system esmlog # the first line of this report reflect the general health status of your system BUT the storage domain
    2. The alert log
      omreport system alertlog
    3. The postlog (messages from the POST: Power On Self Test)
      omreport system postlog

 

 

2.3 Chassis domain commands

 

  • Check the available commands on your system
    # omreport chassis -?
    
    chassis          Chassis component properties.
    
    The available command(s) are:
    
    Command          Description
    pwrmonitoring    Power monitoring properties.
    pwrmanagement    Power management properties.
    hwperformance    Hardware performance information.
    acswitch         AC switch settings.
    bios             BIOS properties.
    biossetup        BIOS setup configuration.
    bmc              Remote Access information.
                       SUBCOMMAND DEPRECATION WARNING:
                       This subcommand is deprecated and will be discontinued in
                       a subsequent release.
                       Use the subcommand "remoteaccess" instead.
    fans             Fan probe(s) properties.
    fru              System Components (FRU) information.
    leds             Chassis LED settings.
    firmware         Firmware properties.
    info             Chassis information.
    intrusion        Chassis intrusion status.
    memory           System memory configuration.
    nics             Network interface card(s) and Team Interface(s) properties.
    ports            Port(s) properties.
    frontpanel       Front panel button control settings.
    processors       Processor(s) properties.
    pwrsupplies      Power supply(s) properties.
    slots            Slot(s) properties.
    temps            Temperature probe(s) properties.
    volts            Voltage probe(s) properties.
    remoteaccess     Remote Access information.
    batteries        Battery(s) properties.
    removableflashmedia        Removeable flash Media properties.

    Note : having a command listed here DOES NOT mean that the corresponding feature is available on your system!

 

  • Retrieving the health status for the chassis
    • if everything is OK :
      # omreport chassis
      Health
      
      Main System Chassis
      
      SEVERITY : COMPONENT
      Ok       : Fans
      Ok       : Intrusion
      Ok       : Memory
      Ok       : Power Supplies
      Ok       : Processors
      Ok       : Temperatures
      Ok       : Voltages
      Ok       : Hardware Log
      Ok       : Batteries
      
      For further help, type the command followed by -?
    • If anything is not really OK! :
      # omreport chassis
      Health
      
      Main System Chassis
      
      SEVERITY : COMPONENT
      Ok       : Fans
      Ok       : Intrusion
      Ok       : Memory
      Critical : Power Supplies
      Ok       : Processors
      Ok       : Temperatures
      Ok       : Voltages
      Ok       : Hardware Log
      Ok       : Batteries
      
      For further help, type the command followed by -?

    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)

  • Change NIC settings (turn on PXE on NIC1)
    omconfig chassis biossetup attribute=nic1 setting=enabledwithpxe

 

 

2.4 Storage domain commands

 

  • Check the available commands on your system
    # omreport storage -?
    
    storage          Display storage component properties.
    
    The available command(s) are:
    
    Command          Description
    adisk            Display array disk(s) properties. DEPRECATED: please use pdisk
    pdisk            Display physical disk(s) properties.
    vdisk            Display virtual disk(s) properties.
    controller       Display controller(s) properties.
    enclosure        Display enclosure properties.
    battery          Display battery properties.
    globalinfo       Display global storage properties.
    connector        Display connector properties.
    cachecade        Display cachecade(s) properties.
  • Retrieve the list of physical HDDs
    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 :

    omreport storage controller |grep ID

    This should gives you this kind of output :

    ID                                            : 0
    Slot ID                                       : Embedded
    SCSI Initiator ID                             : Not Applicable

    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 :

    omreport storage pdisk controller=0

    This should gives you this kind of output :

    ID                        : 0:0:0
    Mirror Set ID             : Not Applicable
    Used RAID Disk Space      : 931.00 GB (999653638144 bytes)
    Available RAID Disk Space : 0.00 GB (0 bytes)
    Vendor ID                 : ATA
    Product ID                : WDC WD10EARS-00MVWB0
    ID                        : 0:0:1
    Mirror Set ID             : Not Applicable
    Used RAID Disk Space      : 931.00 GB (999653638144 bytes)
    Available RAID Disk Space : 0.00 GB (0 bytes)
    Vendor ID                 : ATA
    Product ID                : WDC WD10EARS-00MVWB0
    ID                        : 1:0:4
    Mirror Set ID             : Not Applicable
    Used RAID Disk Space      : 931.00 GB (999653638144 bytes)
    Available RAID Disk Space : 0.00 GB (0 bytes)
    Vendor ID                 : DELL
    Product ID                : ST31000340NS
    ID                        : 1:0:5
    Mirror Set ID             : Not Applicable
    Used RAID Disk Space      : 931.00 GB (999653638144 bytes)
    Available RAID Disk Space : 0.00 GB (0 bytes)
    Vendor ID                 : DELL
    Product ID                : ST31000340NS

    In this example we can see that there are 4 physical HDDs (as there are 4 different ID lines @lines n°1,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 :

    omreport storage pdisk controller=0 |grep -w "^ID"

    Which gives :

    ID                        : 0:0:0
    ID                        : 0:0:1
    ID                        : 1:0:4
    ID                        : 1:0:5
  • Retrieve the RAID configuration
    The RAID configuration is actually nothing but the virtual disk architecture, this is why we can use the following command to retrieve it :

    omreport storage vdisk controller=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 :

    List of Virtual Disks on Controller PERC 5/i Integrated (Embedded)
    
    Controller PERC 5/i Integrated (Embedded)
    ID                  : 0
    Status              : Ok
    Name                : system
    State               : Ready
    Encrypted           : Not Applicable
    Layout              : RAID-1
    Size                : 931.00 GB (999653638144 bytes)
    Device Name         : /dev/sda
    Bus Protocol        : SATA
    Media               : HDD
    Read Policy         : No Read Ahead
    Write Policy        : Write Through
    Cache Policy        : Not Applicable
    Stripe Element Size : 64 KB
    Disk Cache Policy   : Enabled
    
    ID                  : 1
    Status              : Ok
    Name                : Seances
    State               : Ready
    Encrypted           : Not Applicable
    Layout              : RAID-0
    Size                : 1,862.00 GB (1999307276288 bytes)
    Device Name         : /dev/sdb
    Bus Protocol        : SATA
    Media               : HDD
    Read Policy         : No Read Ahead
    Write Policy        : Write Through
    Cache Policy        : Not Applicable
    Stripe Element Size : 64 KB
    Disk Cache Policy   : Enabled
  • Retrieve the physical disk(s) comprised within a RAID array (virtual disk)
    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 :

    omreport storage pdisk controller=0 vdisk=0

    Which print something like :

    List of Physical Disks belonging to system
    
    Controller PERC 5/i Integrated (Embedded)
    ID                        : 0:0:0
    Status                    : Ok
    Name                      : Physical Disk 0:0:0
    State                     : Online
    Power Status              : Not Applicable
    Bus Protocol              : SATA
    Media                     : HDD
    Revision                  : 51.0AB51
    Failure Predicted         : No
    Certified                 : Not Applicable
    Encryption Capable        : No
    Encrypted                 : Not Applicable
    Progress                  : Not Applicable
    Mirror Set ID             : Not Applicable
    Capacity                  : 931.00 GB (999653638144 bytes)
    Used RAID Disk Space      : 931.00 GB (999653638144 bytes)
    Available RAID Disk Space : 0.00 GB (0 bytes)
    Hot Spare                 : No
    Vendor ID                 : ATA
    Product ID                : WDC WD10EARS-00MVWB0
    Serial No.                : WD-WCAZA904698846988
    Part Number               : Not Available
    Negotiated Speed          : Not Available
    Capable Speed             : Not Available
    Manufacture Day           : Not Available
    Manufacture Week          : Not Available
    Manufacture Year          : Not Available
    SAS Address               : 1221000000000000
    
    ID                        : 0:0:1
    Status                    : Ok
    Name                      : Physical Disk 0:0:1
    State                     : Online
    Power Status              : Not Applicable
    Bus Protocol              : SATA
    Media                     : HDD
    Revision                  : 51.0AB51
    Failure Predicted         : No
    Certified                 : Not Applicable
    Encryption Capable        : No
    Encrypted                 : Not Applicable
    Progress                  : Not Applicable
    Mirror Set ID             : Not Applicable
    Capacity                  : 931.00 GB (999653638144 bytes)
    Used RAID Disk Space      : 931.00 GB (999653638144 bytes)
    Available RAID Disk Space : 0.00 GB (0 bytes)
    Hot Spare                 : No
    Vendor ID                 : ATA
    Product ID                : WDC WD10EARS-00MVWB0
    Serial No.                : WD-WCAZA948818988189
    Part Number               : Not Available
    Negotiated Speed          : Not Available
    Capable Speed             : Not Available
    Manufacture Day           : Not Available
    Manufacture Week          : Not Available
    Manufacture Year          : Not Available
    SAS Address               : 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> Format for output results, default is lst.
                           Where: lst  List format.
                                  tbl  Table format.
                                  ssv  Semicolon separated format.
                                  cdv  Custom delimiter separated format.
                                  xml  Raw XML format.
-outc <file>     Redirect output to file, delete old if exists.
  OR
-outa <file>     Redirect output to file, append to old if exists.
  OR
Output may also be redirected using Operating System facilities (e.g. |more).

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 :

omconfig preferences cdvformat delimiter=<separator>

Where separator can be any of : exclamation, semicolon, at, hash, dollar, percent, caret, asterisk, tilde, question, colon, comma, and pipe.

Note : the default cdv is set to the semicolon.

 

 

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
    omconfig system <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 ~]# omconfig system esmlog action=clear
    Embedded System Management (ESM) log cleared successfully.

 

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
    This is an automatically generated email by "/Admin/bin/HardChk.bash" from "TestComputer" (on 07-05-2012 @ 11:34)
    
    ~~~~~~~~~~~ SYSTEM ~~~~~~~~~~~
    
    - [Main System Chassis]     --------------> [Critical] <----------
    
    ~~~~~~~~~~~ CHASSIS ~~~~~~~~~~~
    
    - [Fans]                    --------------> [Ok]
    - [Intrusion]               --------------> [Ok]
    - [Memory]                  --------------> [Ok]
    - [Power Supplies]          --------------> [Ok]
    - [Processors]              --------------> [Ok]
    - [Temperatures]            --------------> [Ok]
    - [Voltages]                --------------> [Ok]
    - [Hardware Log]            --------------> [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 ~]# omconfig system esmlog action=clear
    Embedded System Management (ESM) log cleared successfully.
  • Here is how the same computer is now reported
    This is an automatically generated email by "/Admin/bin/HardChk.bash" from "TestComputer" (on 07-05-2012 @ 12:00)
    
    ~~~~~~~~~~~ SYSTEM ~~~~~~~~~~~
    
    - [Main System Chassis]     --------------> [Ok]
    
    ~~~~~~~~~~~ CHASSIS ~~~~~~~~~~~
    
    - [Fans]                    --------------> [Ok]
    - [Intrusion]               --------------> [Ok]
    - [Memory]                  --------------> [Ok]
    - [Power Supplies]          --------------> [Ok]
    - [Processors]              --------------> [Ok]
    - [Temperatures]            --------------> [Ok]
    - [Voltages]                --------------> [Ok]
    - [Hardware Log]            --------------> [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 “Maximum Performance
    omconfig chassis pwrmanagement profile=maxperformance
  • Activate the CPUs “HyperThreading
    omconfig chassis biossetup attribute=cpuht setting=enabled
  • Activate the CPUs “TURBO Mode
    omconfig chassis biossetup attribute=cputurbomode setting=enabled
  • Change the NIC settings : Activate the pxe boot
    omconfig chassis biossetup attribute=nic1 setting=enabledwithpxe
  • Select the front panel LCD display text
    • Set the LCD to its default value :
      omconfig chassis frontpanel lcdindex=1 config=default

      On my testing poweredge 2950 the default value was  ‘Poweredge 2950

    • Set the LCD to a custom text :
      omconfig chassis frontpanel lcdindex=1 config=custom text='enter here your custom text'

      This would set the LCD display to ‘enter here your custom text

     

  • Generate a controller log file (such as a PERC 6/E controller)
    In the following example you choose the controller using its ID (check the available controllers ID’s 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

    omconfig storage controller action=exportlog controller=1

9 thoughts on “Dell server utility : omreport / omconfig

  1. Tim

    I’m 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….?

    1. Pier Post author

      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

  2. Pingback: Install Dell Open Manage software on Linux Server » Linux notes

  3. Pingback: About omreport | Miscellaneous musings in beta

Leave a Reply

Your email address will not be published. Required fields are marked *

This site supports SyntaxHighlighter via WP SyntaxHighlighter. It can highlight your code.
How to 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.