Sorry, I re-post an old (2019) mailing list post
I need to monitor an old Force10 S55 switch. I wish to monitor ports (it works) but also PSU, FANS and CPU.
Some already monitored Force10 S55 (FTOS 8.3.5.6h)
Replying to Marcel (Sorry - 6 months later 
) my checkmk version is Raw 1.6.0p11
Any suggestion?
Davide
Hello davidemiccone,
the first and foremost thing would be to poll the OIDs described in this article with snmpget.
Then you could just copy an existing psu/fan/cpu snmp check and adjust the OIDs.
Hello simun-muller,
thank you to point me in the right direction!
P.S.: does anyone already has a ready to use Force10 S55 monitoring plugin? It seems that checkmk support Force10 S55 PSU, FANS and CPU checking but it don’t works…
First check what is inside the following OID on your system .1.3.6.1.2.1.1.2.0.
With the result we can have a look if there are already checks present inside CMK supporting your device. I don’t think so.
The next step would be to consult your documentation to find the right OID’s for PSU, FAN and CPU on your system.
With this OID’s we can look if checks for other devices query the same OID’s and if this happens the other check can be extended with your model indentification. (This would be the easiest way)
If no check is found using the same OID’s as your devices then the only option is to write an own check for the device.
Hi Andreas,
.1.3.6.1.2.1.1.2.0 return the value (OID): .1.3.6.1.4.1.6027.1.3.13
.1.3.6.1.4.1.6027.3.10.1.2 is the chSysObjects that contains several useful informations:
.1.3.6.1.4.1.6027.3.10.1.2.1 chSwitchTypeTable "A list of supported switch types. "
.1.3.6.1.4.1.6027.3.10.1.2.2 chStackUnitTable "A list of stack units configured in the chassis. The StackUnit table contains the management information of each stacked unit in the chassis. "
.1.3.6.1.4.1.6027.3.10.1.2.3 chSysPowerSupplyTable “A list of power supply resident in the S-series chassis.”
.1.3.6.1.4.1.6027.3.10.1.2.4 chSysFanTrayTable “A list of fan tray resident in the S-series chassis.”
.1.3.6.1.4.1.6027.3.10.1.2.5 chSysPortTable “A list of ports in the S-series chassis.”
.1.3.6.1.4.1.6027.3.10.1.2.6 chSysPortTable “A list of stack ports in the S-series chassis.”
.1.3.6.1.4.1.6027.3.10.1.2.7 chSysProcessorTable “A list of Processors resident in the S-series chassis.”
.1.3.6.1.4.1.6027.3.10.1.2.8 chSysSwModuleTables “A list of software version information in a processor.”
.1.3.6.1.4.1.6027.3.10.1.2.9 chStackUnitUtilTable “A table listing the cpu and memory utilization in the stack unit.”
I think that chStackUnitTable chSysPowerSupplyTable chSysPowerSupplyTable chSysPowerSupplyTable is what we need.
Here the link to the MIB of the Force10 found on Dell site: http://poweredgec.dell.com/cps/CPS_P_1803/Tools/AFM/MIBs/f10MIB_8.3.5.5.zip
Ok he system description OID looks good.
Can you check if your device answers a query on OID .1.3.6.1.4.1.674.10895.3000.1.2.110.7?
This is the sensor table for Dell powerconnect devices. These devices are using the system description OID .1.3.6.1.4.1.6027.1.3.22. As this is nearly the same a test would be good 
Hi Andreas,
unluckily .1.3.6.1.4.1.674.10895.3000.1.2.110.7 get “No such object”
Here the complete snmpwalk on .1.3.6.1.4.1: https://pastebin.com/nnwtnv9e
Ok then there is no check for your devices included in CheckMK at the moment.
Your SNMP walk has the relevant data
PSU Table 1.3.6.1.4.1.6027.3.10.1.2.3
FAN Table 1.3.6.1.4.1.6027.3.10.1.2.4
But now someone has to write a check.
Yes 
The informations are there but we have to get into checkmk…
Thank you
I searched everywhere for a nagios check for my Force10 S55 with FTOS 8.3.5.6h.
Only found a check for FTOS 9 (without support for stacked units) that don’t works because different OIDs (I try to arrange but the differences are too big).
I also tried to adapt “huawei_switch_fan” “huawei_switch_psu”, etc. I think that starting from this check is the most similar to FTOS 8.3.5.6h
But - at the moment - it is to hard for me
Does some people know about a plugin for Force S55 FTOS 8.3.5.6h ?
Any suggestion are welcome
Can you provide a complete output from these two tables?
I mean one SNMPwalk over these OIDs
With my old check templates this should be fairly easy to make a check.
https://github.com/Yogibaer75/Check_MK-Things/tree/master/templates/snmp_multi_item_check_and_wato/checks
PS: for actual templates i wait until the new API is finalized.
Hello Andreas,
if MIB is needed http://poweredgec.dell.com/cps/CPS_P_1809/Tools/AFM/MIBs/f10MIB_8.3.5.5.zip
If needed I can give access to the switch with a public address (actually they are not in production).
Thank you very much for your help.
**On a stack composed of 2 switch units Force10 S55:**
snmpwalk on 1.3.6.1.4.1.6027.3.10.1.2.3
(here the MIB decoded: https://pastebin.com/c3baQNGF)
.1.3.6.1.4.1.6027.3.10.1.2.3.1.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.1.1.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.3.1.1.2.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.1.2.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.3.1.2.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.2.1.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.2.2.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.2.2.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.3.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.3.1.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.3.2.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.3.2.2 = INTEGER: 1
snmpwalk on 1.3.6.1.4.1.6027.3.10.1.2.4
(here the MIB decoded: https://pastebin.com/99dy7SbE)
.1.3.6.1.4.1.6027.3.10.1.2.4.1.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.1.1.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.4.1.1.2.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.1.2.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.4.1.2.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.2.1.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.2.2.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.2.2.2 = INTEGER: 1
snmpwalk on .1.3.6.1.4.1.6027.3.10.1.2.9 give the CPU load data
(here the MIB decoded: https://pastebin.com/E4jB6dBs)
.1.3.6.1.4.1.6027.3.10.1.2.9.1.1.1 = INTEGER: 5
.1.3.6.1.4.1.6027.3.10.1.2.9.1.1.2 = INTEGER: 5
.1.3.6.1.4.1.6027.3.10.1.2.9.1.2.1 = Gauge32: 15
.1.3.6.1.4.1.6027.3.10.1.2.9.1.2.2 = Gauge32: 0
.1.3.6.1.4.1.6027.3.10.1.2.9.1.3.1 = Gauge32: 17
.1.3.6.1.4.1.6027.3.10.1.2.9.1.3.2 = Gauge32: 0
.1.3.6.1.4.1.6027.3.10.1.2.9.1.4.1 = Gauge32: 17
.1.3.6.1.4.1.6027.3.10.1.2.9.1.4.2 = Gauge32: 0
.1.3.6.1.4.1.6027.3.10.1.2.9.1.5.1 = Gauge32: 7
.1.3.6.1.4.1.6027.3.10.1.2.9.1.5.2 = Gauge32: 6
snmpwalk on .1.3.6.1.4.1.6027.3.10.1.2.2.1 give the overall status (several info, for example TEMP .1.3.6.1.4.1.6027.3.10.1.2.2.1.14 and Unit status .1.3.6.1.4.1.6027.3.10.1.2.2.1.30)
(here the MIB decoded: https://pastebin.com/tp37vwRW)
.1.3.6.1.4.1.6027.3.10.1.2.2.1.2.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.2.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.3.1 = INTEGER: -1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.3.2 = INTEGER: -1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.4.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.4.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.5.1 = INTEGER: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.5.2 = INTEGER: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.6.1 = INTEGER: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.6.2 = INTEGER: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.7.1 = STRING: "S55-01-GE-44T"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.7.2 = STRING: "S55-01-GE-44T"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.8.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.8.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.9.1 = STRING: "48-port E/FE/GE (SD)"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.9.2 = STRING: "48-port E/FE/GE (SD)"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.10.1 = STRING: "8.3.5.6h"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.10.2 = STRING: "8.3.5.6h"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.11.1 = ""
.1.3.6.1.4.1.6027.3.10.1.2.2.1.11.2 = ""
.1.3.6.1.4.1.6027.3.10.1.2.2.1.12.1 = STRING: "GCDL148500039"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.12.2 = STRING: "GCDL126600075"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.13.1 = Timeticks: (784279900) 90 days, 18:33:19.00
.1.3.6.1.4.1.6027.3.10.1.2.2.1.13.2 = Timeticks: (79485100) 9 days, 4:47:31.00
.1.3.6.1.4.1.6027.3.10.1.2.2.1.14.1 = Gauge32: 39
.1.3.6.1.4.1.6027.3.10.1.2.2.1.14.2 = Gauge32: 38
.1.3.6.1.4.1.6027.3.10.1.2.2.1.15.1 = Gauge32: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.15.2 = Gauge32: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.16.1 = INTEGER: 21
.1.3.6.1.4.1.6027.3.10.1.2.2.1.16.2 = INTEGER: 21
.1.3.6.1.4.1.6027.3.10.1.2.2.1.17.1 = STRING: "07"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.17.2 = STRING: "07"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.18.1 = STRING: "01322014"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.18.2 = STRING: "01232012"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.19.1 = Hex-STRING: 00 01 E8 8C 07 B7
.1.3.6.1.4.1.6027.3.10.1.2.2.1.19.2 = Hex-STRING: 00 01 E8 8B 56 0F
.1.3.6.1.4.1.6027.3.10.1.2.2.1.20.1 = STRING: "7590009002"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.20.2 = STRING: "7590009002"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.21.1 = STRING: "E"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.21.2 = STRING: "D"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.22.1 = STRING: "0TR7CT4850039A01DTPB0Z101"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.22.2 = STRING: "0PXXFV2660075A004Q0P9T101"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.23.1 = STRING: "02"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.23.2 = STRING: "02"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.24.1 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.24.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.25.1 = INTEGER: 48
.1.3.6.1.4.1.6027.3.10.1.2.2.1.25.2 = INTEGER: 48
.1.3.6.1.4.1.6027.3.10.1.2.2.1.26.1 = INTEGER: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.26.2 = INTEGER: 0
.1.3.6.1.4.1.6027.3.10.1.2.2.1.27.1 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.27.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.28.1 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.28.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.29.1 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.29.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.2.1.30.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.30.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.31.1 = STRING: "CN-0TR7CT-28298-485-0039"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.31.2 = STRING: "CN-0PXXFV-28298-266-0075"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.32.1 = STRING: "A01"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.32.2 = STRING: "A00"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.33.1 = STRING: "DTPB0Z1"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.33.2 = STRING: "4Q0P9T1"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.34.1 = STRING: "300 941 943 49"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.34.2 = STRING: "102 804 290 29"
.1.3.6.1.4.1.6027.3.10.1.2.2.1.35.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.2.1.35.2 = INTEGER: 1
**On a single switch units Force10 S55:**
snmpwalk on 1.3.6.1.4.1.6027.3.10.1.2.3
(here the MIB decoded: https://pastebin.com/aD5phSXe)
.1.3.6.1.4.1.6027.3.10.1.2.3.1.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.1.1.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.3.1.2.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.2.1.2 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.3.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.3.1.3.1.2 = INTEGER: 1
snmpwalk on 1.3.6.1.4.1.6027.3.10.1.2.4
(here the MIB decoded: https://pastebin.com/fGqFLkDy)
.1.3.6.1.4.1.6027.3.10.1.2.4.1.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.1.1.2 = INTEGER: 2
.1.3.6.1.4.1.6027.3.10.1.2.4.1.2.1.1 = INTEGER: 1
.1.3.6.1.4.1.6027.3.10.1.2.4.1.2.1.2 = INTEGER: 1I found that Observium correctly detect Force10 S55 both single unit or stacked units.
It has a very complete inventory for this switch.
I don’t understand if Observium developed a specific inventory for Force10 S55 or using a generic template Observium can get so precise informations regarding this switch.
Yes there are some checks created inside Observium.
I made two small checks for PSU and Fan.
You can find the two files here.
These files must be copied to your “~/local/share/check_mk/checks/” folder.
Then test if the check is working with “cmk --debug -vvI hostname” and look if something new is found. If yes you can continue with “cmk --debug -vvn hostname” to test the check function.
It works like a charm!
Thanks a lot Andreas
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
