Apparatus, system, and method for distributing management data to network management stations

• US 10,097,400 B1
• Filed: 06/08/2015
• Issued: 10/09/2018
• Est. Priority Date: 06/08/2015
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Tandon, Abhinav
• Primary Examiner(s): Tran, Loc
• Application Number:
  US14/733,310
• Time in Patent Office: 1,219 Days
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]

Abstract

The disclosed apparatus may include (1) a database that stores management data as a set of subtrees and (2) a processing unit having access to the database, wherein the processing unit (A) receives, from an NMS included in a network, a request for at least a portion of the management data, (B) identifies, based at least in part on the request, a subtree within the set of subtrees of management data stored in the database, (C) retrieves all of the management data included in the identified subtree from the database, and then (D) provides all of the management data included in the identified subtree to the NMS that initiated the request for the portion of management data without necessitating another request for any other portion of the management data included in the identified subtree. Various other apparatuses, systems, and methods are also disclosed.

Claims

1. An apparatus comprising:

a database that stores objects as management data; and

a physical processing device having access to the database, wherein the physical processing device;

receives, from a Network Management Station (NMS) included in a network, a set request to create a subtree of certain objects of interest to the NMS;

in response to receiving the set request from the NMS;

identifies, based at least in part on the set request, Object IDentifiers (OIDs) for the certain objects of interest to the NMS that initiated the set request;

creates a table entry within a Management Information Base (MIB) tree included in the database; and

stores, as a subtree in the table entry within the MIB tree, the OIDs for the certain objects of interest to the NMS;

maintains the OIDs included in the subtree in a non-lexicographical order;

receives, from the NMS, a get request for the certain objects of interest to the NMS;

in response to receiving the get request from the NMS;

identifies, within the get request, an OID for a root object of the subtree stored in the table entry within the MIB tree; and

provides, based at least in part on the OID for the root object, all the certain objects whose OIDs are stored as the subtree in the table entry to the NMS that initiated the get request in the non-lexicographical order.

2. The apparatus of claim 1, wherein:

the set request includes an OID for at least a portion of the subtree; and

the physical processing device searches the database for the subtree by using the OID as a database key.

3. The apparatus of claim 2, wherein the physical processing device identifies the subtree by identifying, at a specific location within the database identified by the OID, the certain objects of interest to the NMS.

4. The apparatus of claim 1, wherein the physical processing device retrieves, from the table entry within the MIB tree, all the certain objects whose OIDs are stored as the subtree.

5. The apparatus of claim 1, wherein the subtree further comprises all the certain objects of interest to the NMS.

6. The apparatus of claim 1, wherein the physical processing device:

populates, in response to receiving the set request, the table entry with the subtree in connection with a polling operation performed by the NMS; and

receives another set request from another NMS to populate another table entry within the MIB tree with another subtree in connection with another polling operation performed by the other NMS.

7. The apparatus of claim 1, wherein the physical processing device provides all the certain objects whose OIDs are stored as the subtree by:

in response to the get request;

generating a plurality of responses that each contain at least one of the certain objects whose OIDs are stored as the subtree; and

sending the plurality of responses to the NMS.

8. The apparatus of claim 1, wherein the physical processing device:

updates the subtree by adding an OID for an additional object of interest to the subtree during a polling operation; and

provides, during the polling operation, the additional object of interest to the NMS in connection with the get request received from the NMS without necessitating another get request that includes the OID for the additional object of interest added to the subtree.

9. A router comprising:

a Management Information Base (MIB) tree that stores objects as management data; and

a physical processing device having access to the MIB tree, wherein the physical processing device;

receives, from an NMS included in a network, a set request to create a subtree of certain objects of interest to the NMS;

in response to receiving the set request from the NMS;

identifies, based at least in part on the set request, Object IDentifiers (OIDs) for the certain objects of interest to the NMS that initiated the set request;

creates a table entry within the MIB tree; and

stores, as a subtree in the table entry within the MIB tree, the OIDs for the certain objects of interest to the NMS;

maintains the OIDs included in the subtree in a non-lexicographical order;

receives, from the NMS, a get request for the certain objects of interest to the NMS;

in response to receiving the get request from the NMS;

identifies, within the get request, an OID for a root object of the subtree stored in the table entry within the MIB tree; and

provides, based at least in part on the OID for the root object, all the certain objects whose OIDs are stored as the subtree in the table entry to the NMS that initiated the get request in the non-lexicographical order.

10. The router of claim 9, wherein:

the set request includes an OID for at least a portion of the subtree; and

the physical processing device searches the MIB tree for the subtree by using the OID as a key.

11. The router of claim 10, wherein the physical processing device identifies the subtree by locating, at a specific location within the MIB tree identified by the OID, the certain objects of interest to the NMS.

12. The router of claim 9, wherein the physical processing device retrieves, from the table entry within the MIB tree, all the certain objects whose OIDs are stored as the subtree.

13. The router of claim 12, wherein the subtree further comprises all the certain objects of interest to the NMS.

14. The router of claim 9, wherein the physical processing device:

populates, in response to receiving the set request, the table entry with the subtree in connection with a polling operation performed by the NMS; and

receives another set request from another NMS to populate another table entry within the MIB tree with another subtree in connection with another polling operation performed by the other NMS.

15. The router of claim 9, wherein the physical processing device provides all the certain objects whose OIDs are stored as the subtree by:

in response to the get request;

generating a plurality of responses that each contain at least one of the certain objects whose OIDs are stored as the subtree; and

sending the plurality of responses to the NMS.

16. The router of claim 9, wherein the physical processing device:

updates the subtree by adding an OID for an additional object of interest to the subtree during a polling operation; and

provides, during the polling operation, the additional object of interest to the NMS in connection with the get request received from the NMS without necessitating another get request that includes the OID for the additional object of interest added to the subtree.

17. A method comprising:

receiving, from a Network Management Station (NMS) included in a network, a set request to create a subtree of certain objects of interest to the NMS;

in response to receiving the set request from the NMS;

identifying, based at least in part on the set request, Object Identifiers (OIDs) for the certain objects of interest to the NMS that initiated the set request;

creating a table entry within a Management Information Base (MIB) tree;

and storing, as a subtree in the table entry within the MIB tree, the OIDs for the certain objects of interest to the NMS;

maintaining the OIDs included in the subtree in a non-lexicographical order;

receiving, from the NMS, a get request for the certain objects of interest to the NMS;

in response to receiving the get request from the NMS;

identifying, within the get request, an OID for a root object of the subtree stored in the table entry within the MIB tree; and

providing, based at least in part on the OID for the root object, all the certain objects whose OIDs are stored as the subtree in the table entry to the NMS that initiated the get request in the non-lexicographical order.