CheckMK agent not working with storcli: "Deprecated command. Please use the new syntax"

[drosera (Frank Thommen)]

CMK version: 1.6.0
OS version: CentOS 7.0

Problem Description:
When using storcli (version 007.1705.0000.0000) instead of MegaCli, the tool complains about deprecated commands and consequently the agent doesn’t provide any information. See the example of one of the commands executed by the check_mk agent, once run with MegaCli and once run with storcli:

$ ./MegaCli/MegaCli64 -EncInfo -aALL -NoLog
                                     
    Number of enclosures on adapter 0 -- 1

    Enclosure 0:
    Device ID                     : 252
    Number of Slots               : 8
    Number of Power Supplies      : 0
    Number of Fans                : 0
    Number of Temperature Sensors : 0
    Number of Alarms              : 0
    Number of SIM Modules         : 1
    Number of Physical Drives     : 8
    Status                        : Normal
    Position                      : 1
    Connector Name                : Unavailable
    Enclosure type                : SGPIO
    FRU Part Number               : N/A
    Enclosure Serial Number       : N/A 
    ESM Serial Number             : N/A 
    Enclosure Zoning Mode         : N/A 
    Partner Device Id             : Unavailable

    Inquiry data                  :
        Vendor Identification     : LSI     
        Product Identification    : SGPIO           
        Product Revision Level    : N/A 
        Vendor Specific           :                     


Exit Code: 0x00
$ ./storcli/storcli64 -EncInfo -aALL -NoLog
CLI Version = 007.1705.0000.0000 Mar 31, 2021
Operating system = Linux 3.10.0-1160.49.1.el7.x86_64
Status = Failure
Description = Deprecated command. Please use the new syntax.

$ 

As far as I understand, storcli is the successor of MegaCli and it itself also a few years old .

Is there a way to make storcli work with the CheckMK agent and/or what are the plans from the side of check_mk regarding storcli?

Thanks, Frank

[drosera (Frank Thommen)]

It would be great if e.g. the CheckMK developers could give their assessment regarding storcli vs. MegaCli

[Jay2k1]

+1. We just got a new server with onboard Broadcom/LSI 3008 SAS3 (12 Gbps) controller.

MegaCLI does not find it, storcli works, but the agent only “speaks” megacli syntax with storcli, so currently we can’t monitor the RAID array.

I’ll be happy to provide storcli output for the devs. We are using 2.0.0p20 (CRE).

[lkoenig (Lorenz Koenig)]

There is a storcli-Plugin for Windows storcli.bat, maybe the commands work with the same syntax for the Linux-version of storcli. In the Windows-Plugin the commands executed look like this:

storcli /call/eall/sall show
storcli /call/vall show

Do these commands produce an output on your linux system? I unfortunately don’t have a system on hand to test this.

[drosera (Frank Thommen)]

The two command do produce output (CentOS 7.9):

/opt/MegaRAID/storcli/storcli64 /call/eall/sall show
CLI Version = 007.1705.0000.0000 Mar 31, 2021
Operating system = Linux 3.10.0-1160.59.1.el7.x86_64
Controller = 0
Status = Success
Description = Show Drive Information Succeeded.


Drive Information :
=================

------------------------------------------------------------------------------
EID:Slt DID State DG       Size Intf Med SED PI SeSz Model            Sp Type 
------------------------------------------------------------------------------
252:0    21 Onln   0 278.464 GB SAS  HDD N   N  512B ST3300657SS      U  -    
252:1    16 Onln   0 278.464 GB SAS  HDD N   N  512B ST3300657SS      U  -    
252:2     9 Onln   1   3.637 TB SAS  HDD N   N  512B ST4000NM0023     U  -    
252:3     8 Onln   1   3.637 TB SAS  HDD N   N  512B ST4000NM0023     U  -    
252:4    10 Onln   1   3.637 TB SAS  HDD N   N  512B ST4000NM0023     U  -    
252:5    11 Onln   1   3.637 TB SAS  HDD N   N  512B ST4000NM0023     U  -    
252:6    20 Onln   1   3.637 TB SAS  HDD N   N  512B ST4000NM0023     U  -    
252:7    13 Onln   1   3.637 TB SAS  HDD N   N  512B ST4000NM0023     U  -    
------------------------------------------------------------------------------

EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|DG=DriveGroup
DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare
UBad=Unconfigured Bad|Sntze=Sanitize|Onln=Online|Offln=Offline|Intf=Interface
Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info
SeSz=Sector Size|Sp=Spun|U=Up|D=Down|T=Transition|F=Foreign
UGUnsp=UGood Unsupported|UGShld=UGood shielded|HSPShld=Hotspare shielded
CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded
UBUnsp=UBad Unsupported|Rbld=Rebuild

and

/opt/MegaRAID/storcli/storcli64 /call/vall show
CLI Version = 007.1705.0000.0000 Mar 31, 2021
Operating system = Linux 3.10.0-1160.59.1.el7.x86_64
Controller = 0
Status = Success
Description = None


Virtual Drives :
==============

---------------------------------------------------------------
DG/VD TYPE  State Access Consist Cache Cac sCC       Size Name 
---------------------------------------------------------------
0/0   RAID1 Optl  RW     Yes     NRWBD -   ON  278.464 GB      
1/1   RAID6 Optl  RW     Yes     NRWBD -   ON   14.551 TB      
---------------------------------------------------------------

VD=Virtual Drive| DG=Drive Group|Rec=Recovery
Cac=CacheCade|OfLn=OffLine|Pdgd=Partially Degraded|Dgrd=Degraded
Optl=Optimal|dflt=Default|RO=Read Only|RW=Read Write|HD=Hidden|TRANS=TransportReady
B=Blocked|Consist=Consistent|R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack
AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct IO|sCC=Scheduled
Check Consistency

I’d really appreciate a feedback from the CheckMK developers regarding storcli (new syntax!) vs. MegaCli

[drosera (Frank Thommen)]

Any feedback from the side of CheckMK? I find it suboptimal to run a monitoring software with the “enterprise” label (we are running “CheckMK Enterprise”) but still have to stick with very old software: The latest MegaCli I can find is from 2013!