Adding OIDs to SNMP Probe and configuring Output

JBark
Tera Expert

So I added two OIDs to Discovery's SNMP System OIDs

SNow_OID_input_10102014.JPG

Ran a Discovery and saw those OIDs in the Discovery log

SNow_OID_disco_output_first_10102014.JPG

SNow_OID_disco_output_second_10102014.JPG

SNow_OID_disco_output_second6_10102014.JPG

 

I think Discovery is pulling the information I need, but I can't get it to output. I've tried creating a field in the form section, but I can't see how I associate that field with the OID. How do I get this to work? Thanks!

1 ACCEPTED SOLUTION

The solution was to create a new SNMP Sensor;



new DiscoverySensor({
process: function(result) {
  var snmp = new SNMPResponse(result);
  var oid_mib2 = 'iso.org.dod.internet.mgmt.mib-2.';
 
  var location = snmp.getOIDText(oid_mib2 + 'system.sysLocation');
  var contact = snmp.getOIDText(oid_mib2 + 'system.sysContact');


        current.u_system_contact = contact + '\n';
        current.u_system_location = location + '\n';
},      
              type: "DiscoverySensor"
});


View solution in original post

7 REPLIES 7

faisal_dadabhoy
Giga Expert

Hello Jeff,



I am thinking perhaps the issue is when you are trying to discover the switches, you are not getting the "oid or sysObjectID" back from the foundry switch.



Please look at the ecc queue "input" (Source should be the IP you are trying to discover), the payload should contain similar to listed below.


"SnmpObjectId">.1.3.6.1.4.1.9.1.444</sysObjectID>



I am thinking the logs you are sharing is outgoing to foundry or SNMP walk logs



If my assumption is correct, please let me know, I suggest few things how you can resolve the issue.



Hope it helps:-) Faisal Dadabhoy


Faisal, thank you for the quick reply. I went thru all the input queues and the only one that had a "SnmpObjectId" line was the one in the second picture I attached to the first post. You can see it on the last line. This was from the input queue named "SNMP - Classify 343OIDs"


Hello Jeff,



I could be wrong but my thought is that even though you have the oid listed in the ECC input queue but that is not the oid parameter system is looking for to determine if that is the switch; therefore, not recognizing as a switch or foundry switch.



As a very temporary measure (maybe first try in DEV), in the Classification Criteria related list, you could say (Source equals "switch IP"), and see if it discovers it.



If you do make that change revert it back as soon as you done.



Thanks, Faisal



find_real_file.png


Interesting, the source table is already set to Switch IP.