Snmp - get/bulk/getnext/walk show warnings when mibs are used

Bug #1992826 reported by Agustin Carranza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Low
Agustin Carranza

Bug Description

Brief Description

Apparently the changes introduced by https://review.opendev.org/c/starlingx/snmp-armada-app/+/814634 requires not only to remove the top node for the TMS MIB structure but also the child node OID definitions depicted at:

---------------------------------------------------------------------------
-- TMS OID Definitions
---- TMS Major MIB Categories
    idb OBJECT IDENTIFIER ::= { tms 1 } -- IDB MIBs
    tmsGeneric OBJECT IDENTIFIER ::= { tms 2 } -- TMS Generic MIBs
    oemSwapi OBJECT IDENTIFIER ::= { tms 3 } -- OEM swAPI MIBs
    oemProd OBJECT IDENTIFIER ::= { tms 4 }

-- OEM Product MIBs-- TMS IDB Internal Module MIBs
    rmonMib OBJECT IDENTIFIER ::= { idb 1 }
-- garpMib OBJECT IDENTIFIER ::= { idb 2 } SMIv2
-- stpMib OBJECT IDENTIFIER ::= { idb 3 } SMIv2

-- TMS Generic MIBs
-- tmsCommonMib OBJECT IDENTIFIER ::= { tmsGeneric 1 } SMIv2
-- tmsL3Mib OBJECT IDENTIFIER ::= { tmsGeneric 2 } SMIv2

-- OEM swAPI MIBs
-- pmSwapi OBJECT IDENTIFIER ::= { oemSwapi 1 } SMIv2
-- bcmSwapi OBJECT IDENTIFIER ::= { oemSwapi 2 } SMIv2
-- pcSwapi OBJECT IDENTIFIER ::= { oemSwapi 3 } SMIv2

-- OEM Product MIBs
-- pm3575 OBJECT IDENTIFIER ::= { oemProd 1 } SMIv2
-- bcm5600 OBJECT IDENTIFIER ::= { oemProd 2 } SMIv2
-- pcSwitch OBJECT IDENTIFIER ::= { oemProd 3 } SMIv2

Severity

<Minor: System/Feature is usable with minor issue>

Steps to Reproduce

Run any snmp command (get, bulk, getnext) that requires using wrs mibs. e.g:

user% snmpget -v2c -c testcommunity 10.20.1.3:161 WRS-ALARM-MIB::wrsEventReasonText.1

Expected Behavior

No warnings are returned.

user% snmpget -v2c -c testcommunity 10.20.1.3:161 WRS-ALARM-MIB::wrsEventReasonText.1
WRS-ALARM-MIB::wrsEventReasonText.1 = STRING: controller-0 is now 'online'

Actual Behavior

Several warnings are returned.

user% snmpget -v2c -c testcommunity 10.20.1.3:161 WRS-ALARM-MIB::wrsEventReasonText.1
Unlinked OID in WRS-ENTERPRISE-REG-MIB: oemProd ::= { tms 4 }
Undefined identifier: tms near line 84 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
Unlinked OID in WRS-ENTERPRISE-REG-MIB: oemSwapi ::= { tms 3 }
Undefined identifier: tms near line 83 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
Unlinked OID in WRS-ENTERPRISE-REG-MIB: tmsGeneric ::= { tms 2 }
Undefined identifier: tms near line 82 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
Unlinked OID in WRS-ENTERPRISE-REG-MIB: idb ::= { tms 1 }
Undefined identifier: tms near line 81 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
WRS-ALARM-MIB::wrsEventReasonText.1 = STRING: controller-0 is now 'online'

Reproducibility

100% Reproducible

System Configuration
--------------------
One node system, ipv4

Branch/Pull Time/Commit
-----------------------
stx7.0 and master

Last Pass
---------

Timestamp/Logs
--------------

user% snmpget -v2c -c testcommunity 10.20.1.3:161 WRS-ALARM-MIB::wrsEventReasonText.1
Unlinked OID in WRS-ENTERPRISE-REG-MIB: oemProd ::= { tms 4 }
Undefined identifier: tms near line 84 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
Unlinked OID in WRS-ENTERPRISE-REG-MIB: oemSwapi ::= { tms 3 }
Undefined identifier: tms near line 83 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
Unlinked OID in WRS-ENTERPRISE-REG-MIB: tmsGeneric ::= { tms 2 }
Undefined identifier: tms near line 82 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
Unlinked OID in WRS-ENTERPRISE-REG-MIB: idb ::= { tms 1 }
Undefined identifier: tms near line 81 of /usr/share/snmp/mibs/wrsEnterpriseReg.mib.txt
WRS-ALARM-MIB::wrsEventReasonText.1 = STRING: controller-0 is now 'online'

Test Activity
-------------
Regression Testing

Workaround
-------------
Just ignore the warnings.

Changed in starlingx:
assignee: nobody → Agustin Carranza (acarranz)
summary: - Snmp - get - bulk - getnext -walk show warnings
+ Snmp - get/bulk/getnext/walk show warnings when mibs are used
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to snmp-armada-app (master)
Changed in starlingx:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to snmp-armada-app (master)

Reviewed: https://review.opendev.org/c/starlingx/snmp-armada-app/+/861206
Committed: https://opendev.org/starlingx/snmp-armada-app/commit/9f42416c15d0a8e2dbb2af73d712879ce1538a9f
Submitter: "Zuul (22348)"
Branch: master

commit 9f42416c15d0a8e2dbb2af73d712879ce1538a9f
Author: Agustin Carranza <email address hidden>
Date: Thu Oct 13 13:26:41 2022 -0300

    Remove orphan node OID definitions from mibs

    Apparently the changes introduced by
    https://review.opendev.org/c/starlingx/snmp-armada-app/+/814634
    requires not only to remove the top node for the TMS MIB structure
    but also the child node OID definitions.
    If not, several warnings are returned when issuing any tipe of snmp
    commands.

    Test Plan
    PASS: Install mibs on user host.
          Issue snmpget/snmpwalk/snmpgetnext/snmpbulkget commands to a
          deployment with snmp application uploaded and applied.
          No warnings related to OID parent 'TMS' are shown.

    Closes-bug: 1992826

    Signed-off-by: Agustin Carranza <email address hidden>
    Change-Id: Ib9553b74e8afcc4b7d40ae8d78158c63cb08618d

Changed in starlingx:
status: In Progress → Fix Released
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Low
tags: added: stx.8.0 stx.fault
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.