IP Library Patent Application 19233353
Patent Application
App. No. 19/233,353

UPDATING MAPPINGS IN AN AUTHORITATIVE DATABASE

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 None
App. No.
19/233,353
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 (37)

1 . A computer-implemented method, comprising:

maintaining 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;

obtaining a new OID supported by a simple network management protocol (SNMP)-enabled device in the network environment;

determining that the new OID supported by the SNMP-enabled device is excluded from the authoritative database;

based on the new OID being excluded from the authoritative database, obtaining an MIB corresponding to the new OID; and

causing the new OID and the corresponding MIB to be stored in the authoritative database.

2 . The method of claim 1 , further comprising configuring an SNMP-manager or an SNMP-connector with the MIB corresponding with the new OID.

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 new OID is based on the SNMP-enabled device being a new device added to the network environment.

5 . The method of claim 1 , wherein the new OID is based on a hardware or software change to the SNMP-enabled device.

6 . The method of claim 1 , wherein the MIB corresponding to the new OID is obtained from a vendor.

7 . The method of claim 1 , wherein the MIB corresponding to the new OID is obtained from a vendor hosting MIB data on a network server.

8 . The method of claim 1 , wherein the MIB corresponding to the new OID is obtained, via an information collector, using a uniform resource identifier associated with a vendor, the uniform resource identifier provided to the information collector for use in populating the authoritative database.

9 . The method of claim 1 , wherein the MIB corresponding to the new OID is obtained, via an information collector, using a uniform resource identifier associated with the MIB, the uniform resource identifier provided to the information collector for use in populating 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:

maintaining 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;

obtaining a new OID supported by a simple network management protocol (SNMP)-enabled device in the network environment;

determining that the new OID supported by the SNMP-enabled device is excluded from the authoritative database;

based on the new OID being excluded from the authoritative database, obtaining an MIB corresponding to the new OID; and

causing the new OID and the corresponding MIB to be stored in the authoritative database.

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 MIB corresponding with the new OID.

13 . The one or more non-transitory computer-readable media of claim 11 , wherein the authoritative database specifies a set of correspondences between the plurality of MIBs and the plurality of OIDs.

14 . The one or more non-transitory computer-readable media of claim 11 , wherein the new OID is based on the SNMP-enabled device being a new device added to the network environment.

15 . The one or more non-transitory computer-readable media of claim 11 , wherein the new OID is based on a hardware or software change to the SNMP-enabled device.

16 . The one or more non-transitory computer-readable media of claim 11 , wherein the MIB corresponding to the new OID is obtained from a vendor.

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:

maintaining 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;

obtaining a new OID supported by a simple network management protocol (SNMP)-enabled device in the network environment;

determining that the new OID supported by the SNMP-enabled device is excluded from the authoritative database;

based on the new OID being excluded from the authoritative database, obtaining an MIB corresponding to the new OID; and

causing the new OID and the corresponding MIB to be stored in the authoritative database.

18 . The system of claim 17 , wherein the MIB corresponding to the new OID is obtained from a vendor hosting MIB data on a network server.

19 . The system of claim 17 , wherein the MIB corresponding to the new OID is obtained, via an information collector, using a uniform resource identifier associated with a vendor, the uniform resource identifier provided to the information collector for use in populating the authoritative database.

20 . The system of claim 17 , wherein the MIB corresponding to the new OID is obtained, via an information collector, using a uniform resource identifier associated with the MIB, the uniform resource identifier provided to the information collector for use in populating the authoritative database.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 11, 2026
From: SPLUNK LLC
To: CISCO TECHNOLOGY, INC.
Reel/Frame 074735/0375 →
CHANGE OF NAME Recorded Feb 11, 2026
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 074768/0649 →
CORRECTIVE ASSIGNMENT TO CORRECT THE SPELLING OF INVENTORS NAME FROM MAYAR SANJAYBHAI PIPALIYA TO MAYUR SANJAYBHAI PIPALIYA PREVIOUSLY RECORDED ON REEL 71373 FRAME 977. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 17, 2025
From: FAIRCLOTH, RYAN LEE; BHAGAT, ANKIT CHETAN; PIPALIYA, MAYUR SANJAYBHAI; LING, YUAN
To: SPLUNK INC.
Reel/Frame 072038/0715 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 10, 2025
From: FAIRCLOTH, RYAN LEE; BHAGAT, ANKIT CHETAN; PIPALIYA, MAYAR SANJAYBHAI; LING, YUAN
To: SPLUNK INC.
Reel/Frame 071373/0977 →