We have some systems using a SNMPv2 credential, connectivity over UDP/161 has been validated, and confirmed the devce (Synology NAS) is exposing
a private MIB (1.3.6.1.4.1.6574.), which we have uploaded to the ServiceNow instance.
Important to remark that in /sysObjectID it identifies as Linux standard, .1.3.6.1.4.1.8072.3.2.10.
So we have creted an SNMP Classification rule that applies to Storage Server table [cmdb_ci_storage_server] including an OID Classification "Starts wth" (1.3.6.1.4.1.6574).
We have created a behavior so we use a specific MID server and only SNMP protocol.
When discovery is run, SNMP-Classify lists 63 OIDs bot in the payload we don't see 6574.
Classify works in the sense that our new patter is run, but it ends with the message "Failed to get SNMP scalar value as OID not found"
Our first step in the pattern is an SNMP Query to standard SNMP v2 MIB.
However if we debug from within the pattern, we Browse and load the private MIB we can ask to the device specific MIB.
What can are we missing here? Is there any previous step so the pattern we have built loads the MIB to be able to use it, as we do when we debug it?
