Votes:
hello,
unfortunatly i was unable to locate any sensors for lenovo thinktervers. in particular we would like physical disk smart statuses etc, and general hardware conditions and system health. is there any other way to achieve this?
sincerly
georg franke
10 Replies
Votes:
Hi Georg,
Lenovo just recently aquired the IBM Server line correct? In that case, please take a look at our IBM Server sensors, if SNMP is enabled and the required software is installed, it may work the same way as it would on a IBM server. Please note that required software may have different names since it's now Lenovo's software.
There are our available sensors for IBM Hardware:
SNMP IBM System X Logical Disk Sensor
SNMP IBM System X Physical Disk Sensor
SNMP IBM System X Physical Memory Sensor
SNMP IBM System X System Health Sensor
If you're successful in adding those sensor's, please report back.
Created on May 20, 2015 8:39:48 AM by
Votes:
Hello Georg,
I've found some information on the subject, it's compiled below:
6.6.2.3 ThinkServer SAS SNMP MIB Location
After you install the ThinkServer SAS SNMP Agent package, the MIB file ThinkServer-AdapterSAS.mib is installed under /etc/ThinkServer_mrdsnmp/sas directory.
Please see the following link from Lenovo's documentation, for management of servers that use a LSI RAID Controller.
If that documentation is accurate, it is possible to import the MIB using our SNMP Importer Tool and then adding a SNMP Library Sensor.
You may also need to create/customize a Lookup file to see the correct Ok/Warning/Down status when something fails.
Unfortunately that only regards the RAID Controler/disks, I wasn't able to find any documentation that states that the above mentioned hardware has a proper MIB to monitor the hardware's status.
Created on May 26, 2015 11:18:49 AM by
Votes:
Hello Ariel, thank you for your input.
The issue with the linked files is that they don't follow the SNMP/MIB syntax, that's also why the MIB Importer fails to import it. I did however address the most grotesque issues and created an importable/usable MIB File. It's the Text in the box below, just create a new text (.txt) file copy this text into it and save it as ThinkServer-TSM.mib:
Note: Provided as-is without any warranties. Alternatively, contact the vendor and ask them to correct the MIB Instead. This should be importable and usable with PRTG now.
---------------------------------------------------------------------------
--
-- Title: Systems Management Instrumentation MIB of Lenovo ThinkServer
--
-- Version: 1.0.0
--
-- Release Date: 2014.11.11
--
-- Description: This MIB defines MIB objects that make system instrumentation
-- data available to SNMP management applications.
--
-- Copyright (c) 2013-2014 Lenovo Corp.
-- All Rights Reserved.
--
--
-- OID Format Legend:
-- <a> = attribute ID
-- <i> = index ID
--
---------------------------------------------------------------------------
---------------------------------------------------------------------------
-- Begin MIB
---------------------------------------------------------------------------
ThinkServer-TSM DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-IDENTITY,
OBJECT-TYPE,
Integer32,
Integer32, Opaque, enterprises
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString
FROM SNMPv2-TC;
---------------------------------------------------------------------------
-- Object Identifiers
--------------------------------------------------------------------------
thinkServerMIB MODULE-IDENTITY
LAST-UPDATED "201701090914Z"
ORGANIZATION "Lenovo Group"
CONTACT-INFO "[email protected]"
DESCRIPTION
"EPG-ThinkServer"
REVISION "201701090914Z"
DESCRIPTION
"Fixed upperxlowercase and minor issues (LucianoLingnau @ Paessler AG)"
REVISION "201411110000Z"
DESCRIPTION
"first release"
::= { enterprises 19046 }
platformObjects OBJECT IDENTIFIER ::= { thinkServerMIB 10 }
---bmcObjects OBJECT IDENTIFIER ::= { thinkServerMIB 3 }
---chassisInfoObjects OBJECT IDENTIFIER ::= { thinkServerMIB 4}
---boardInfoObjects OBJECT IDENTIFIER ::= { thinkServerMIB 5}
---productInfoObjects OBJECT IDENTIFIER ::= { thinkServerMIB 6}
---------------------------------------------------------------------------
-- "Float32TC" was used originally(but not importer). Replaced with "Float" and added the tc below.
--------------------------------------------------------------------------
Float ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
""
SYNTAX Opaque (SIZE (7))
---------------------------------------------------------------------------
-- platformName
--------------------------------------------------------------------------
platformName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The server name"
::= { thinkServerMIB 1 }
---------------------------------------------------------------------------
-- systemLocation
--------------------------------------------------------------------------
systemLocation OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The System Location"
::= { thinkServerMIB 2 }
---------------------------------------------------------------------------
-- sensorTable
---------------------------------------------------------------------------
sensorTable OBJECT-TYPE
SYNTAX SEQUENCE OF SensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of sensor entries."
::= { platformObjects 2 }
---------------------------------------------------------------------------
-- sensorEntry
---------------------------------------------------------------------------
sensorEntry OBJECT-TYPE
SYNTAX SensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the sensor table."
INDEX { sensorIndex }
::= { sensorTable 1 }
SensorEntry ::=
SEQUENCE {
sensorIndex Integer32,
sensorName DisplayString,
sensorNumber Integer32,
sensorValue INTEGER
}
sensorIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique value which identifies the sensor."
::= { sensorEntry 1 }
sensorName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual full name assigned to a sensor."
::= { sensorEntry 2 }
sensorNumber OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sensor number."
::= { sensorEntry 3 }
sensorValue OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sensor value."
::= { sensorEntry 4 }
---------------------------------------------------------------------------
-- fRUTables
---------------------------------------------------------------------------
fRUTable OBJECT-TYPE
SYNTAX SEQUENCE OF FRUEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of platform FRU entries."
::= { platformObjects 3 }
---------------------------------------------------------------------------
-- fRUEntry (FRU)
---------------------------------------------------------------------------
fRUEntry OBJECT-TYPE
SYNTAX FRUEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the FRU table."
INDEX { fRUIndex }
::= { fRUTable 1 }
FRUEntry ::=
SEQUENCE {
fRUIndex Integer32,
fRUVendorName Integer32,
fRUVendorPartNumber Integer32,
fRUVendorAssemblyRevision Integer32,
fRUVendorSerialNumber Integer32
}
fRUIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The unique value which identifies the FRU."
::= { fRUEntry 1 }
fRUVendorName OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor name for the FRU."
::= { fRUEntry 2 }
fRUVendorPartNumber OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor part number for the FRU."
::= { fRUEntry 3 }
fRUVendorAssemblyRevision OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor assembley revision for the FRU."
::= { fRUEntry 4 }
fRUVendorSerialNumber OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor serial number for the FRU."
::= { fRUEntry 5 }
END
If it fails to find any compatible data in PRTG (when deploying the SNMP Library sensor), please perform a walk from the following OID with our SNMP Tester and share the results:
| 1.3.6.1.4.1.19046.10 |
If you need a guide to import the MIB, please refer to:
One deal-breaker with this MIB file, is that there's no "syntax definition" for the sensorValue, this may make getting alerts tricky, you'll have to set-up limits to get the sensors alerting.
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Jan 9, 2017 8:23:29 AM by
Last change on Jan 9, 2017 8:29:32 AM by
Votes:
Hi Luciano and thanks for your help.
I've successfully imported the customized MIB file into prtg.
When adding the corresponding snmp library sensor I get "No available interfaces on this device (code: PE049)" error.
snmp tester walk with 1.3.6.1.4.1.19046.10 OID log:
----------------------- New Test ----------------------- Paessler SNMP Tester 5.2.3 Computername: SYSMON Interface: 172.20.0.252 10/01/2017 09:55:29 (1 ms) : Device: 172.20.0.18 10/01/2017 09:55:29 (2 ms) : SNMP V2c 10/01/2017 09:55:29 (3 ms) : Walk 1.3.6.1.4.1.19046.10
----------------------- New Test ----------------------- Paessler SNMP Tester 5.2.3 Computername: SYSMON Interface: 172.20.0.252 10/01/2017 09:56:33 (3 ms) : Device: 172.20.0.18 10/01/2017 09:56:33 (4 ms) : SNMP V1 10/01/2017 09:56:33 (5 ms) : Walk 1.3.6.1.4.1.19046.10 10/01/2017 09:56:33 (8 ms) : Error: 2
Regards, Ariel
Last change on Jan 10, 2017 8:43:06 AM by
Votes:
Hello Ariel,
thank you for your reply and tests.
That's not good I'm afraid. The lack of a reply (or the error 2) basically tells us that this system don't know the polled/walked OID. Have you confirmed that SNMP is enabled on 172.20.0.18?
You can confirm this by doing a walk of 1.3.6.1.2.1.1 or 1.3.6. If you get valid replies to this query, contact Lenovo/IBM and inquiry about why the server isn't responding to queries from the OID that are part of the appropriate MIB.
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Jan 10, 2017 8:54:21 AM by
Votes:
Hello Nolwyn,
thank you for your reply and no worries about updating the 4 months old post.
I had one more look for this subject. This is what I located:
1. First, I began with the system's Datasheet, which claims:
| One of the most important features of the RD440 — and all ThinkServer systems — is that it uses open industry standards and protocols so it integrates easily into your multi-vendor environment. That means you can use your existing management tools with the RD440 or try ours at no additional charge. In addition to a front-side diagnostic panel, the RD440 offers a suite of intuitive ThinkServer lifecycle tools that make management easy so you can focus on IT projects that drive your business. These tools include configuration, firmware, and rack power optimizers, as well as a way to conveniently searchfor, monitor, and manage your servers. |
Which means that there must be a way to monitor these.
2. I've then looked further and stumbled uppon the ThinkServer EasyManage tool. Which is of course proprietary.
3. After a bit more search I've located this document:
If the information from the document above is "True", it's actually quite interesting. There's a table:
| Capability | ThinkServer Management Module | ThinkServer System Manager |
|---|---|---|
| Supported Systems | 3rd and 4th generation ThinkServer Except TS130, TS140, RS140 | 5th generation ThinkServer |
| Supported Standards | IPMI version 2.0, DCMI 1.0 (2P racks only),SMASH-CLI (limited), WS-MAN (limited) | IPMI version 2.0, DCMI 1.0, SMASH-CLI, WS-MAN SNMP v3 (Gets) |
| Embedded Command Line Interface | SMASH-CLI (limited) | SMASH-CLI, PowerShell |
If this is correct (and applies), this is good news for owners of 5th generation ThinkServer servers. This all appears to apply only to the out-of-band interface, but the following should work with PRTG:
Without access to any MIB, Powershell may be the best option. The document mentions the following Powershell cmdlet (which must be imported via some software package):
Invoke-TMMCLI [-CommandName]
<COMMAND_NAME>
[COMMAND_PARAMETERS] [-CommandArgs]
@ {[COMMAND_ARGUMENTS]}
My general advise is: Contact Lenovo/IBM, the features mentioned in this document look very promissing, if all that is true it would offer a lot of flexibility for monitoring with PRTG.
And if you're a PRTG user and got any of this working on your IBM hardware, share your thoughts/comments, they are very welcome.
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Apr 20, 2017 12:56:12 PM by
Add comment