CBS250 SNMP does not fetch all values

I’m currently looking into an issue with our Cisco CBS250 devices. On the predicessor (SG350) LibreNMS was able to display data like POE power usage and SFP status. On CBS250 these data seemd to be missing.

I dug a little into the issue and found the following problem with the POE-Power usage:
From my understanding the data are gathered with this file: opt\librenms\includes\discovery\sensors\power\ciscosb.inc.php

I added a debug output for the $temp array and found that only the first 10 values are fetched:

Power: CiscoSB: 
Array
(
    [1.1] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.2] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.3] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.4] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.5] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.6] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.7] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.8] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.9] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

    [1.10] => Array
        (
            [rlPethPsePortOutputPower] => 0
        )

)

A manual snmpwalk works:

snmpwalk -v 2c -c xxxxx -m /opt/librenms/mibs/cisco/CISCOSB-POE-MIB 192.168.177.34 .1.3.6.1.4.1.9.6.1.101.108.1.1
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.2 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.3 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.4 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.5 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.6 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.7 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.8 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.9 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.10 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.11 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.12 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.13 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.14 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.15 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.16 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.17 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.18 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.19 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.20 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.21 = INTEGER: 1728
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.22 = INTEGER: 4921
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.23 = INTEGER: 0
SNMPv2-SMI::enterprises.9.6.1.101.108.1.1.5.1.24 = INTEGER: 0

If I add the MIB and OID to the \opt\librenms\includes\definitions\discovery\ciscosb.yaml I also get the same problem:


Any ideas? The SG350X works witth the same parameters.

Discovery output with debug ennabled: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.07.24 23:05:12 =~=~=~=~=~=~=~=~=~=~=~=p - Pastebin.com
validate.php gives no error.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.