IP Library Granted Patent US 12,362,985
Granted Patent B1
US 12,362,985 · App. 18/625,112 · Granted Jul 15, 2025

Enhanced simple network management protocol (SNMP) connector

Inventors: Ryan Lee Faircloth (DeLand, FL); Ankit Chetan Bhagat (Santa Clara, CA); Mayur Sanjaybhai Pipaliya (San Francisco, CA); Yuan Ling (San Francisco, CA)
H04L41/0213H04L41/048H04L67/306
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,362,985
App. No.
18/625,112
Granted
Jul 15, 2025
Kind
B1
Abstract

Techniques are described for automating the configuration of a simple network management protocol (SNMP) manager device for enabling collection of SNMP data from one or more SNMP-enabled devices. Based upon SNMP object identifiers (OIDs) received from an SNMP-enabled device, processing is performed to map the OIDs to one or more SNMP management information bases (MIBs) corresponding to the OIDs. The identification of the OIDs and mapping the OIDs to one or more MIBs is performed in an automated manner and substantially free of any human or manual intervention. The identified one or more MIBs are then used to configure the SNMP manager to enable SNMP communications between the SNMP-enabled device and the SNMP manager. In certain implementations, the identified one or more MIBs are loaded into system memory by the SNMP manager.

Claims (45)

1. A computer-implemented method, comprising:

populating an authoritative database with a plurality of management information bases (MIBs) and a plurality of object identifiers (OIDs) received from one or more vendors, the authoritative database being stored in a network environment;

receiving a list of OIDs generated by one or more simple network management protocol (SNMP)-enabled devices in the network environment;

querying the authoritative database to identify matching OIDs in the authoritative database that match the OIDs in the list of OIDs;

identifying, based on a subset of correspondences, a set of one or more MIBs included in the authoritative database corresponding to the matching OIDs; and

causing the set of one or more MIBs corresponding to the matching OIDs to be stored in an MIBs list in the network environment.

2. The method of claim 1 , further comprising configuring an SNMP-manager or an SNMP-connector with the set of one or more MIBs included in the MIBs list.

3. The method of claim 1 , wherein the authoritative database specifies a set of correspondences between the plurality of MIBs and the plurality of OIDs.

4. The method of claim 1 , wherein the MIBs list does not include the list of OIDs.

5. The method of claim 1 , further comprising updating the list of OIDs with an updated OID list upon identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

6. The method of claim 1 , further comprising querying the authoritative database to identify additional matching OIDs that match OIDs included in an updated list of OIDs generated in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

7. The method of claim 1 , further comprising querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

8. The method of claim 1 , further comprising:

querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment; and

configuring an SNMP-manager or an SNMP-connector with the MIBs included in the updated MIBs list.

9. The method of claim 1 , further comprising:

querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment; and

collecting updated MIB data from at least one of the one or more vendors in response to determining that MIB data corresponding to the one or more additional SNMP-enabled devices or the at least one of the one or more SNMP-enabled devices is not included in the authoritative database.

10. The method of claim 1 , wherein the network environment is a local network.

11. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of:

populating an authoritative database with a plurality of management information bases (MIBs) and a plurality of object identifiers (OIDs) received from one or more vendors, the authoritative database being stored in a network environment;

receiving a list of OIDs generated by one or more simple network management protocol (SNMP)-enabled devices in the network environment;

querying the authoritative database to identify matching OIDs in the authoritative database that match the OIDs in the list of OIDs;

identifying, based on a subset of correspondences, a set of one or more MIBs included in the authoritative database corresponding to the matching OIDs; and

causing the set of one or more MIBs corresponding to the matching OIDs to be stored in an MIBs list in the network environment.

12. The one or more non-transitory computer-readable media of claim 11 , further comprising configuring an SNMP-manager or an SNMP-connector with the set of one or more MIBs included in the MIBs list.

13. The one or more non-transitory computer-readable media of claim 11 , further comprising updating the list of OIDs with an updated OID list upon identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

14. The one or more non-transitory computer-readable media of claim 11 , further comprising querying the authoritative database to identify additional matching OIDs that match OIDs included in an updated list of OIDs generated in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

15. The one or more non-transitory computer-readable media of claim 11 , further comprising querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

16. The one or more non-transitory computer-readable media of claim 11 , further comprising:

querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment; and

collecting updated MIB data from at least one of the one or more vendors in response to determining that MIB data corresponding to the one or more additional SNMP-enabled devices or the at least one of the one or more SNMP-enabled devices is not included in the authoritative database.

17. A system comprising:

a memory storing an application; and

a processor, coupled to the memory, that executes the application by performing the steps of:

populating an authoritative database with a plurality of management information bases (MIBs) and a plurality of object identifiers (OIDs) received from one or more vendors, the authoritative database being stored in a network environment;

receiving a list of OIDs generated by one or more simple network management protocol (SNMP)-enabled devices in the network environment;

querying the authoritative database to identify matching OIDs in the authoritative database that match the OIDs in the list of OIDs;

identifying, based on a subset of correspondences, a set of one or more MIBs included in the authoritative database corresponding to the matching OIDs; and

causing the set of one or more MIBs corresponding to the matching OIDs to be stored in an MIBs list in the network environment.

18. The system of claim 17 , wherein the processor further performs the steps of updating the list of OIDs with an updated OID list upon identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

19. The system of claim 17 , wherein the processor further performs the steps of querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment.

20. The system of claim 17 , wherein the processor further performs the steps of:

querying the authoritative database to update the MIBs list with an updated MIBs list in response to identifying one or more additional SNMP-enabled devices being added to the network environment or identifying a hardware or software change to at least one of the one or more SNMP-enabled devices in the network environment; and

collecting updated MIB data from at least one of the one or more vendors in response to determining that MIB data corresponding to the one or more additional SNMP-enabled devices or the at least one of the one or more SNMP-enabled devices is not included in the authoritative database.

Assignments (4)
CHANGE OF NAME Recorded Jul 22, 2025
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 072170/0599 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 22, 2025
From: SPLUNK LLC
To: CISCO TECHNOLOGY, INC.
Reel/Frame 072173/0058 →
CHANGE OF NAME Recorded Jan 6, 2025
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 069826/0065 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 5, 2024
From: FAIRCLOTH, RYAN LEE; BHAGAT, ANKIT CHETAN; PIPALIYA, MAYU SANJAYBHAI; LING, YUAN
To: SPLUNK INC.
Reel/Frame 067919/0381 →
Continuity (2)
Continuation 17387811 · Jul 28, 2021
Provisional Application 63172226 · Apr 8, 2021
References Cited (22)
US 7822836B1 · Saparoff · 2010 [cited by applicant]
US 7904588B2 · Clemm et al. · 2011 [cited by applicant]
US 7937344B2 · Baum et al. · 2011 [cited by applicant]
US 8112425B2 · Baum et al. · 2012 [cited by applicant]
US 8244843B1 · Primerano et al. · 2012 [cited by applicant]
US 8667113B2 · Veerabhadrappa · 2014 [cited by applicant]
US 8751529B2 · Zhang et al. · 2014 [cited by applicant]
US 8788525B2 · Neels et al. · 2014 [cited by applicant]
US 9215240B2 · Merza et al. · 2015 [cited by applicant]
US 9286413B1 · Coates et al. · 2016 [cited by applicant]
US 9413615B1 · Singh et al. · 2016 [cited by applicant]
US 10127258B2 · Lamas et al. · 2018 [cited by applicant]
US 11949547B2 · Faircloth · 2024 [cited by examiner]
US 20060010488A1 · Fujimori · 2006 [cited by applicant]
US 20090132719A1 · Fujimori · 2009 [cited by applicant]
US 20190095367A1 · Kakio et al. · 2019 [cited by applicant]
US 20190098106A1 · Mungel et al. · 2019 [cited by applicant]
Splunk Enterprise 8.0.0 Overview, available online, retrieved on May 20, 2020 from docs.splunk.com, 17 pages. [cited by applicant]
Splunk Cloud 8.0.2004 User Manual, available online, retrieved on May 20, 2020 from docs.splunk.com, 66 pages. [cited by applicant]
Splunk Quick Reference Guide, updated 2019, available online at https://www.splunk.com/pdfs/solution-guides/splunk-quick-reference-guide.pdf, retrieved on May 20, 2020, 6 pages. [cited by applicant]
Carraso, David, “Exploring Splunk,” published by CITO Research, New York, NY, Apr. 2012, 156 pages. [cited by applicant]
Bitincka et al., “Optimizing Data Analysis with a Semi-structured Time Series Database,” self-published, first presented at “Workshop on Managing Systems via Log Analysis and Machine Learning Techniques (SLAML)”, Vancou… [cited by applicant]