Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Professional Edition
-
Observium 18.9.9429 (10th September 2018)
OS Linux 4.9.0-4-amd64 [amd64] (Debian 9.2)
Apache 2.4.25 (Debian)
PHP 7.0.19-1 (OPcache: ENABLED)
Python 2.7.13
MySQL 10.1.26-MariaDB-0+deb9u1 (extension: mysqli 5.0.12-dev)
SNMP NET-SNMP 5.7.3
RRDtool 1.6.0 (rrdcached 1.6.0: unix:/var/run/rrdcached.sock)
Fping 3.15 (IPv4 and IPv6)Observium 18.9.9429 (10th September 2018) OS Linux 4.9.0-4-amd64 [amd64] (Debian 9.2) Apache 2.4.25 (Debian) PHP 7.0.19-1 (OPcache: ENABLED) Python 2.7.13 MySQL 10.1.26-MariaDB-0+deb9u1 (extension: mysqli 5.0.12-dev) SNMP NET-SNMP 5.7.3 RRDtool 1.6.0 (rrdcached 1.6.0: unix:/var/run/rrdcached.sock) Fping 3.15 (IPv4 and IPv6)
Description
Hello,
Is it possible to improved the hardware detection for EXOS devices when they are in Stack mode?
Since the stack of EXOS devices could be made from different hardware types, they will always replay to sysObjectID:
:/opt/observium/mibs/extreme # snmpwalk -v2c -c public extremex690 1.3.6.1.2.1.1.2 |
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.1916.2.93 |
SNMPv2-MIB::sysObjectID.0 = OID: EXTREME-BASE-MIB::summitVer2Stack |
Which means they are in stack mode, but is possible to go one step and detect the hardware type of the stack using extremeStackMemberType (1.3.6.1.4.1.1916.1.33.2.1.2):
:/opt/observium/mibs/extreme # snmpwalk -v2c -c public extremex690 1.3.6.1.4.1.1916.1.33.2.1.2 |
.1.3.6.1.4.1.1916.1.33.2.1.2.1 = OID: .1.3.6.1.4.1.1916.2.248 |
EXTREME-STACKING-MIB::extremeStackMemberType.1 = OID: EXTREME-BASE-MIB::extremeProduct.248 |
And from the MIB EXTREME-BASE-MIB line 807
x690-48x-4q-2c OBJECT IDENTIFIER ::= { extremeProduct 248 } |
--X690 48 1/10Gb SFP+, 4 10Gb/40Gb QSFP+, 2 10Gb/25Gb/40Gb/50Gb/100Gb QSFP28 |
During the Re-Detect OS If sysObjectID = .1.3.6.1.4.1.1916.2.93 then request 1.3.6.1.4.1.1916.1.33.2.1.2.
:/opt/observium # ./discovery.php -d -m os -h extremex690
|
##### Module Start: os #####
|
CMD[/usr/bin/snmpget -t '5' -v2c -c *** -Pu -OQUv -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'extremex690':'161' sysDescr.0] |
CMD EXITCODE[0] |
CMD RUNTIME[0.0091s] |
STDOUT[
|
ExtremeXOS (Stack) version 22.5.1.7 22.5.1.7 by release-manager on Tue May 22 11:25:12 EDT 2018 |
]
|
SNMP STATUS[TRUE]
|
|
|
CMD[/usr/bin/snmpget -t '5' -v2c -c *** -Pu -OQUvn -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'extremex690':'161' sysObjectID.0] |
|
|
CMD EXITCODE[0] |
CMD RUNTIME[0.0092s] |
STDOUT[
|
.1.3.6.1.4.1.1916.2.93 |
]
|
SNMP STATUS[TRUE]
|
+-------------+-----------------------------------------------------------------------------------------+
|
| OID | |
|
+-------------+-----------------------------------------------------------------------------------------+
|
| sysDescr | ExtremeXOS (Stack) version 22.5.1.7 22.5.1.7 by release-manager on Tue May 22 11:25:12 | |
| | EDT 2018 | |
| sysObjectID | .1.3.6.1.4.1.1916.2.93 | |
+-------------+-----------------------------------------------------------------------------------------+
|
|
|
o Re-Detect OS matched (xos: Extreme XOS):
|
+-------------+---------------------+-----------------------------------------------------------------+
|
| OID | Matched definition | |
|
+-------------+---------------------+-----------------------------------------------------------------+
|
| sysObjectID | .1.3.6.1.4.1.1916.2 | .1.3.6.1.4.1.1916.2.93 | |
| sysDescr | /XOS/ | ExtremeXOS (Stack) version 22.5.1.7 22.5.1.7 by release-manager | |
| | | on Tue May 22 11:25:12 EDT 2018 | |
+-------------+---------------------+-----------------------------------------------------------------+
|
Thanks.
Attachments
Activity
Oh, not sure that this fully correct.
Please attach debug poller for an example device (detected as EnetSwitch):
./poller.php -d -m os -h <device>
|
Hello Mike,
Thanks for the fix. After the update to r9435 all extreme hardware switches are called EnetSwitch?
Is there any particular reason for that name? Is it possible to replace EnetSwitch to Extreme X.......
Thanks.
Thanks, it works.