Exporting management information base data using IPFIX

1. A networking apparatus, comprising:

a network interface;

a processor coupled to the interface;

logic coupled to the processor and encoded in one or more tangible storage media for execution and when executed operable to cause performance of computer implemented steps that comprise:

receiving a command to collect a unique object identifier that represents a unique management information base (MIB) object;

wherein the unique object identifier is a MIB object identifier (OID);

retrieving, in response to receiving the command, a Simple Network Management Protocol (SNMP) MIB variable or table that corresponds to the MIB object;

creating an Internet Protocol Flow Information Export (IPFIX) template record data structure that includes the object identifier;

wherein the object identifier is encoded in the IPFIX template data structure as a string;

wherein the string has a variable length; and

exporting the IPFIX record data structure with the encoded object identifier;

wherein an object value that corresponds to the object identifier that is encoded in the IPFIX template record data structure is exported with the IPFIX record data structure; and

wherein the receiving and exporting steps support a push transmission mode for exporting unsolicited data;

wherein a size of the string is encoded therewith as a prefix, which comprises a variable length information element that conforms to IPFIX variable length encoding.

2. The apparatus as recited in claim 1 further comprising logic which when executed causes storing the IPFIX template record.

3. The apparatus as recited in claim 1 wherein the variable length string conforms to one of a plurality of encoding formats wherein the plurality includes one or more Unicode transformation formats.

4. The apparatus as recited in claim 3 wherein the one or more Unicode transmission formats comprise Unicode Transformation Format 8 (UTF-8).

5. The apparatus as recited in claim 1 wherein the size of the string is stored separately from the apparatus.

6. The apparatus as recited in claim 1 wherein the strings comprise NULL terminated strings.

7. The apparatus as recited in claim 1 wherein content of the variable length string that corresponds to the object identifier encodes a name or a number.

8. The apparatus as recited in claim 1 further comprising logic which when executed causes retrieving using a SNMP ‘GET’ operation.

9. The apparatus as recited in claim 8 wherein the logic, when executed, further causes using an application program interface (API) associated with the SNMP ‘GET’ operation in the retrieving.

10. The apparatus as recited in claim 1 , further comprising:

converting one or more IPFIX information elements into one or more corresponding MIB variables;

wherein exporting the IPFIX record data structure includes exporting the one or more corresponding MIB variables encoded in the IPFIX record data structure.

11. A method for exporting network management information, comprising the steps of:

receiving a command to collect a unique object identifier that represents a unique management information base (MIB) object;

wherein the unique object identifier is a MIB object identifier (OID);

retrieving, in response to receiving the command, a Simple Network Management Protocol (SNMP) MIB variable or table that corresponds to the MIB object;

creating an Internet Protocol Flow Information Export (IPFIX) template data structure that comprises the object identifier;

wherein the object identifier is encoded in the IPFIX template data structure as a string;

wherein the string has a variable length; and

exporting the IPFIX record data structure with the encoded object identifier;

wherein an object value that corresponds to the object identifier that is encoded in the IPFIX template record data structure is exported with the IPFIX record data structure; and

wherein the receiving and exporting steps support a push transmission mode for exporting unsolicited data;

wherein a size of the string is encoded therewith as a prefix, which comprises a variable length information element that conforms to IPFIX variable length encoding;

wherein a router performs the receiving, retrieving, creating, and exporting.

12. The method as recited in claim 11 further comprising storing the IPFIX template record.

13. The method as recited in claim 11 wherein the variable length string conforms to one of a plurality of encoding formats wherein the plurality includes one or more Unicode transformation formats and wherein the one or more Unicode transmission formats comprise Unicode Transformation Format 8 (UTF-8).

14. The method as recited in claim 11 wherein the size of the string is selectively stored separately from the apparatus, or wherein the string comprises a NULL terminated string.

15. The method as recited in claim 14 wherein content of the variable length string that corresponds to the object identifier encodes a name or a number.

16. The method as recited in claim 11 further comprising retrieving using a SNMP ‘GET’ operation;

wherein the retrieving step comprises using an application program interface (API) associated with the SNMP ‘GET’ operation in the retrieving.

17. The method as recited in claim 11 , further comprising the steps of:

converting one or more IPFIX information elements into one or more corresponding MIB variables;

wherein exporting the IPFIX record data structure includes exporting the one or more corresponding MIB variables encoded in the IPFIX record data structure.

18. A networking apparatus, comprising:

one or more processors;

means for receiving a command to collect a unique object identifier that represents a unique management information base (MIB) object;

wherein the unique object identifier is a MIB object identifier (OID);

means for retrieving, in response to the command, a Simple Network Management protocol (SNMP) MIB variable or table that corresponds to the MIB object;

means for creating an Internet Protocol Flow Information Export (IPFIX) template data structure that comprises the object identifier;

wherein the creating means encodes the object identifier in the IPFIX template data structure as a string;

wherein the string has a variable length; and

means for exporting the IPFIX record data structure with the encoded object identifier;

wherein an object value that corresponds to the object identifier that is encoded in the IPFIX template record data structure is exported with the IPFIX record data structure; and

wherein the receiving and exporting means support a push transmission mode for exporting unsolicited data;

wherein a size of the string is encoded therewith as a prefix, which comprises a variable length information element that conforms to IPFIX variable length encoding.

19. A system, comprising:

a network management station communicatively coupled to a network;

a networking device coupled to the network;

logic in the networking device and encoded in one or more tangible media for execution and when executed operable to:

receive a command to collect a unique object identifier that represents a unique management information base (MIB) object;

wherein the unique object identifier is a MIB object identifier (OID);

retrieving, in response to receiving the command, a Simple Network Management Protocol (SNMP) MIB variable or table that corresponds to the MIB object;

creating an Internet Protocol Flow Information Export (IPFIX) template data structure that comprises the object identifier;

wherein the object identifier is encoded in the IPFIX template data structure as a string;

wherein the string has a variable length; and

exporting the IPFIX record data structure with the encoded object identifier;

wherein an object value that corresponds to the object identifier that is encoded in the IPFIX template record data structure is exported with the IPFIX record data structure; and

wherein the receiving and exporting steps support a push transmission mode for exporting unsolicited data;

wherein a size of the string is encoded therewith as a prefix, which comprises a variable length information element that conforms to IPFIX variable length encoding.

20. The system as recited in claim 19 further comprising logic which when executed causes storing the IPFIX template data structure.

21. The system as recited in claim 19 further comprising logic which when executed causes retrieving using a SNMP ‘GET’ operation wherein an application program interface (API) associated with the SNMP ‘GET’ operation is used with the retrieving.