System and method for providing a script-based collection for devices in a network environment

• US 8,589,544 B2
• Filed: 11/07/2012
• Issued: 11/19/2013
• Est. Priority Date: 07/31/2010
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Banerjee, Pradeep K., Lin, Shyyunn Sheran, Rayes, Ammar, Thompson, Gregory S., Dasgupta, Subrata, Malaviya, Virendra K., McDonnell, James
• Primary Examiner(s): CHRISTENSEN, SCOTT B
• Application Number:
  US13/671,209
• Publication Number:
  US 20130067078A1
• Time in Patent Office: 377 Days
• Field of Search: None
• US Class Current: 709/224
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/04 Network management architectures or arrangements
• CPC Class Codes: H04L 41/34 Signalling channels for network management communication

Abstract

A method is provided in one example and includes verifying a storage capacity of a network element coupled to an end device over a network connection. The method also includes executing script provided in the network element, which is configured for exchanging packets in a network environment. The script initiates a collection of data being retrieved from the end device. The data can be Fault, Configuration, Accounting, Performance, and Security (FCAPS) data associated with the end device. The data collected from the end device is communicated to a next destination.

Claims

1. A method, comprising:

executing a master scheduling script provided in a network element, the network element configured for exchanging packets with a plurality of end devices in a network environment, wherein the master scheduling script is configured to;

parse a seed file that contains the plurality of end devices; and

spawn a collector control script for a selected end device of the plurality of end devices, wherein the spawned collector control script is configured to instruct a collector element to launch a slave collection script to initiate a collection of data from the selected end device, wherein the slave collection script is configured to parse an inventory configuration file (ICF) to gather a set of command line interface (CLI) commands associated with the selected end device;

receiving the data from the selected end device; and

communicating the received data to a next destination.

2. The method of claim 1, wherein all of the plurality of end devices contained in the seed file are selected end devices from which respective data is to be retrieved.

3. The method of claim 2, further comprising:

verifying that an Internet Protocol address of the selected end device in the seed file is reachable by the network element.

4. The method of claim 1, further comprising:

creating, based on a storage capacity of the network element, one or more archives of the data received from the selected end device and other data received from one or more other selected end devices; and

communicating each of the one or more archives to a next destination.

5. The method of claim 4, wherein the communicating includes communicating a part number and a total amount of parts being communicated to the next destination.

6. The method of claim 1, wherein the collection script is further configured to:

parse the inventory configuration file to gather simple network management protocol (SNMP) management information base (MIB) data to be collected from the selected end device.

7. The method of claim 1, wherein the collector element is coincident, collocated, and residing in a same logical element as the network element.

8. The method of claim 1, wherein the collector element is provisioned separately from the network element.

9. The method of claim 1, wherein the network element communicates with the collector element over a secure shell (SSH) connection.

10. One or more non-transitory computer-readable storage media that includes code for execution and when executed by a processor is operable to perform operations comprising:

executing a master scheduling script provided in a network element, the network element configured for exchanging packets with a plurality of end devices in a network environment, wherein the master scheduling script is configured to;

parse a seed file that contains the plurality of end devices; and

spawn a collector control script for a selected end device of the plurality of end devices, wherein the spawned collector control script is configured to instruct a collector element to launch a slave collection script to initiate a collection of data from the selected end device, wherein the slave collection script is configured to parse an inventory configuration file (ICF) to gather a set of command line interface (CLI) commands associated with the selected end device;

receiving the data from the selected end device; and

communicating the received data to a next destination.

11. The one or more non-transitory computer-readable storage media of claim 10, wherein the processor is operable to perform further operations comprising:

creating, based on a storage capacity of the network element, one or more archives of the data received from the selected end device and other data received from one or more other selected end devices; and

communicating each of the one or more archives to a next destination.

12. The one or more non-transitory computer-readable storage media of claim 10, wherein the collection script is further configured to:

parse the inventory configuration file to gather simple network management protocol (SNMP) management information base (MIB) data to be collected from the selected end device.

13. The one or more non-transitory computer-readable storage media of claim 10, wherein the collector element is coincident, collocated, and residing in a same logical element as the network element.

14. An apparatus configured for exchanging packets with a plurality of end devices in a network environment, comprising:

a memory element configured to store data;

a processor operable to execute instructions associated with the data;

a master scheduling script configured to interface with the memory element and the processor to;

parse a seed file that contains the plurality of end devices; and

spawn a collector control script for a selected end device of the plurality of end devices, wherein the spawned collector control script is configured to instruct a collector element to launch a slave collection script to initiate a collection of device-specific data from the selected end device, wherein the memory element is configured to receive the device-specific data from the selected end device, wherein the slave collection script is configured to parse an inventory configuration file (ICF) to gather a set of command line interface (CLI) commands associated with the selected end device; and

a transport module configured to communicate the received device-specific data to a next destination.

15. The apparatus of claim 14 wherein the collector element is coincident, collocated, and residing in a same logical element as the apparatus.

16. The apparatus of claim 14 wherein the collector element is further configured to:

parse the inventory configuration file to gather simple network management protocol (SNMP) management information base (MIB) data to be collected from the selected end device.

17. The apparatus of claim 14, wherein the collector element is provisioned separately from the apparatus, and wherein the apparatus communicates with the collector element over a secure shell (SSH) connection.