[OBS-3691] Our Supermicro switches aren't being detected as Supermicro - Observium

Details

Type: Add New Device / OS
Resolution: Fixed
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Description

It looks like observium is using the sysDescr. output to detect the device.

Our output is:
SNMPv2-MIB::sysDescr.0 = STRING: SuperSwitch MBM-XEM-002 Firmware revision: 2.1.0-46

It looks like the current observium matches are:
$config['os'][$os]['sysDescr'][] = "/^Supermicro Switch/";
$config['os'][$os]['sysDescr'][] = "/^(SSE|SBM)-/";

Attachments

Activity

[OBS-3691] Our Supermicro switches aren't being detected as Supermicro

Chris Laffin added a comment - 2021/03/26 10:03 PM

Thanks. I don't think it worked though.

I did svn up and rediscovered one of the switches and got.

"OS changed: supermicro-switch -> generic"

I had a local mod that set them to supermicro-switch that I reverted before doing svn up.

I'm currently at revision 11170

Chris Laffin added a comment - 2021/03/26 10:03 PM Thanks. I don't think it worked though. I did svn up and rediscovered one of the switches and got. "OS changed: supermicro-switch -> generic" I had a local mod that set them to supermicro-switch that I reverted before doing svn up. I'm currently at revision 11170

Mike Stupalov added a comment - 2021/03/26 08:43 PM

Improved in r11169.

Mike Stupalov added a comment - 2021/03/26 08:43 PM Improved in r11169.

Chris Laffin added a comment - 2021/03/25 04:41 PM

Yes, I have attached the output you requested.

Chris Laffin added a comment - 2021/03/25 04:41 PM Yes, I have attached the output you requested.

Mike Stupalov added a comment - 2021/03/25 07:56 AM

Thanks, but there seems to be a whole tree snmpwalk problem on the device.
Make additional walk please:

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > supermicro.snmpwalk

Mike Stupalov added a comment - 2021/03/25 07:56 AM Thanks, but there seems to be a whole tree snmpwalk problem on the device. Make additional walk please: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > supermicro.snmpwalk

Chris Laffin added a comment - 2021/03/25 01:06 AM

I added the snmp output requested.

Chris Laffin added a comment - 2021/03/25 01:06 AM I added the snmp output requested.

Observium Bot added a comment - 2021/03/25 12:43 AM

Please make and attach additional information about the device:

full snmp dump from device:

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

If device not support SNMP version 2c, replace -v2c with -v1.

If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>
./poller.php -d -h <device>

additionally attach device and/or vendor specific MIB files

Note, this comment is added automatically.

Observium Bot added a comment - 2021/03/25 12:43 AM Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

People

Assignee:: Mike Stupalov

Reporter:: Chris Laffin

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2021/03/25 12:43 AM

Updated:: 2021/04/26 06:10 PM

Resolved:: 2021/03/26 08:43 PM