Support for Dell Compellent SAN

Btw. Some duplicated output that probably should be fixed;

1. 1. 1. 1. 1. Module Start: os #####

OS CHANGED: freebsd -> compellent
o Device OS changed freebsd -> compellent

Indeed. Thanks!

Check now, it really should be fixed in r7168.

Mike,

sysObjectID for freebsd still "wins". Maybe just remove that and let freebsd matches use discovery_os ?
Still after removing the sysobjectid I have to delete freebsd (on device) from database before it can change to compellent OS.

Sadly no

Previously it worked removing sysObjectID from freebsd os definition. But now that doesn't work either. Will debug more later..

$os = "freebsd";
$config['os'][$os]['text'] = "FreeBSD";
$config['os'][$os]['type'] = "server";
$config['os'][$os]['group'] = "unix";
$config['os'][$os]['discovery_os'] = "freebsd";
$config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.8072.3.2.8";

Should be fixed in r7159.

sysDescr sting;
FreeBSD hostname 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Thu Dec 18 07:47:20 CST 2014 root@es-vb91-1:/work/buildmaster/r06.05.20/R06.05.20.018/06_05_20_018/work/buildmaster/r06.05.20/R06.05.20.018/src/sys/COMPELLENT amd64

Please show sysDescr from device or attach debug for:

./discovery.php -d -m os -h <device>

Guys,
Need help with something. I noticed in my prod environment that Compellents was still recognized as freebsd.
That's because Compellent returns same sysObject ID as freebsd (even though compellent os definition has a sysDescr to match.)
Now, if i removed the sysObjectID from freebsd OS definition, one would think this should trigger OS change, because they no longer match.But that never happend until I cleared OS from DB

Some suggestions;
1) If sysObjectID no longer match anything in OS definition, it should trigger a change.
2) If OS definition has sysDescr, but matches sysIbjectID first it should use sysDescr (or something)

Thank you (but mib missing)