Method for persisting SNMP MIB data in files

• US 20040204778A1
• Filed: 01/06/2003
• Published: 10/14/2004
• Est. Priority Date: 01/06/2003
• Status: Abandoned Application

• Current Assignee: Hughes Software Systems Ltd. (Kohlberg Kravis Roberts & Company LP)
• Original Assignee: Hughes Software Systems Ltd. (Kohlberg Kravis Roberts & Company LP)
• Inventors: Uddin, Salim, Lalapeth, Harish
• Application Number:
  US10/336,838
• Publication Number:
  US 20040204778A1
• Time in Patent Office: Days
• US Class Current: 700/83
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Abstract

SNMP MIB data is stored in a persistence file where the storage format provides representations of SNMP scalar and table objects and is independent of SNMP protocol.

Claims

1. A method for storing SNMP MIB data in persistence file wherein the storage format of the persistent file provides representation of SNMP scalar and table objects and is independent of SNMP protocol.

2. A method as claimed in claim 1 wherein the persistence file is editable before deployment depending on site specifics.

3. A method as claimed in claim 1 wherein a GUT based tool is provided to take SNMP MIB(s) as input and generate configuration profiles in format(s) suitable for particular deployment.

4. A method as claimed in claim 1 wherein the GUI based tool validates SNMP MIB data stored in different storage formats, on data type and range checks defined in the SNMP MIB.

5. A method as claimed in claim 1 wherein the storage format is based on tags used to identify SNMP objects.

6. A method as claimed in claim 5 wherein the SNMP objects are selected from scalars and tables.

7. A method as claimed in claim 3 wherein new values and updates for the SNMP MIB objects, to be stored in the persistent file is done through the GUT based tool.

8. A method as claimed in claim 2 wherein user options are provided through a GUI based tool to selectively store SNMP MIB objects as required for a particular deployment.

9. A method as claimed in claim 3 wherein user options are provided through the GUT based tool to selectively store SNMP MIB objects as required for a particular deployment.

10. A method as claimed in claim 1 wherein the storage format is SNMP agent toolkit independent.

11. A method as claimed in claim 1 wherein the storage format uses a consistent notation to differentiate between scalar and tabular objects of the SNMP MIB.

12. A method as claimed in claim 3 wherein the default tags used for the storage format can be changed to user defined values through the GUT based tool.

13. A method as claimed in claim 5 wherein the default tags used for the storage format can be changed to user defined values through the GUT based tool.

14. A method as claimed in claim 1 wherein consistency of data is provided across configuration profiles stored in different storage formats

15. A method as claimed in claim 1 wherein the configuration profiles address bulk provisioning requirements

16. A method as claimed in claim 1 wherein the SNMP based configuration profile(s) generated for a given network element is usable by non-SNMP applications.

17. A method as claimed in claim 1 wherein multiple configuration profile(s) are generated dynamically to suit a particular deployment requirement

18. A method as claimed in claim 1 wherein the storage format facilitates reading and writing of file by writing a SNMP MIB object at unique file offset.