SELECTIVE DATA COLLECTION USING A MANAGEMENT SYSTEM

• US 20160234108A1
• Filed: 02/11/2015
• Published: 08/11/2016
• Est. Priority Date: 02/11/2015
• Status: Active Grant

• Current Assignee: Quest Software, Inc.
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: McAleer, David
• Granted Patent: US 9,690,576 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/00 Arrangements for program control, e.g. control units program control for peripheral devices G06F13/10
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 41/0645 by additionally acting on or stimulating the network after receiving notifications
• CPC Class Codes: H04L 41/0677 Localisation of faults
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities

Abstract

A management system sends a first request for first data associated with multiple network entities. If the first request times out, the first request is split to create multiple smaller requests and the multiple smaller requests sent, requesting data from a subset of the multiple network entities. Based on responses to the multiple smaller requests, the management system identifies a particular network entity that caused the first request to time out and adds the particular network entity to a set of problematic entities. The management system sends a second request that requests second data from a portion of the multiple network entities that excludes the particular network entity. The multiple network entities may include one or more of a virtual machine (VM), a host node (to host VMs), a storage device, a network link, another type of network entity, or any combination thereof.

Claims

1. A computer-implemented method, comprising:

sending, from a management system, a first request to provide first data associated with a plurality of network entities;

in response to determining that the first request timed out, creating a plurality of smaller requests based on the first request;

sending the plurality of smaller requests, each of the plurality of smaller requests requesting data from a subset of the plurality of network entities;

identifying a particular network entity of the plurality of network entities that caused the first request to time out based on responses to the plurality of smaller requests;

adding the particular network entity to a set of confirmed problematic entities; and

sending a second request to provide second data associated with a portion of the plurality of network entities that excludes the particular network entity.

2. The computer-implemented method of claim 1, wherein the plurality of network entities comprises at least one of:

a plurality of virtual machines hosted by a plurality of host nodes,

a plurality of network links,

a plurality of storage devices, or

a sub-network comprising a portion of the plurality of network entities.

3. The computer-implemented method of claim 1, further comprising:

sending, after a predetermined period of time, a third request to provide third data associated with the plurality of network entities including the particular network entity.

4. The computer-implemented method of claim 3, further comprising:

in response to receiving a response to the third request, removing the particular network entity from the set of confirmed problematic entities.

5. The computer-implemented method of claim 3, further comprising:

in response to the response to the third request timing out, maintaining the particular network entity in the set of confirmed problematic entities.

6. The computer-implemented method of claim 1, wherein the particular network entity is added to the set of confirmed problematic entities in response to determining that the particular network entity has caused a predetermined number of requests to time out.

7. The computer-implemented method of claim 1, wherein the first request:

identifies the plurality of network entities, and

identifies one or more types of data to request from the plurality of network entities.

8. One or more non-transitory computer-readable media, comprising instructions that are executable by one or more processors to perform operations comprising:

sending, from a management system, a first request to provide first data associated with a plurality of network entities comprising a plurality of virtual machines hosted by a plurality of host nodes;

in response to determining that no response to the first request was received within a predetermined time interval, splitting the first request to create a plurality of smaller requests;

sending the plurality of smaller requests, individual smaller requests of the plurality of smaller requests requesting data from a portion of the plurality of network entities;

identifying a particular network entity of the plurality of network entities that caused the first request to time out based on responses to the plurality of smaller requests;

adding the particular network entity to a set of confirmed problematic entities; and

sending a second request to provide second data associated with a portion of the plurality of network entities that excludes the particular network entity.

9. The one or more non-transitory computer-readable media of claim 8, wherein the plurality of network entities further comprises:

a plurality of network links,

a plurality of storage devices, and

a plurality of sub-networks.

10. The one or more non-transitory computer-readable media of claim 8, further comprising:

sending, after a predetermined period of time, a third request to provide third data associated with the plurality of network entities including the particular network entity; and

in response to receiving a response to the third request, removing the particular network entity from the set of confirmed problematic entities.

11. The one or more non-transitory computer-readable media of claim 10, further comprising:

in response to the response to the third request timing out, continuing to include the particular network entity in the set of confirmed problematic entities.

12. The one or more non-transitory computer-readable media of claim 8, further comprising:

incrementing a counter associated with the particular network entity in response to determining that the particular network entity caused a subsequent request to time out; and

adding the particular network entity to the set of confirmed problematic entities in response to determining that the counter satisfies a predetermined threshold.

13. The one or more non-transitory computer-readable media of claim 8, wherein the first request:

identifies the plurality of network entities, and

identifies one or more types of data to request from the plurality of network entities.

14. A computing device, comprising:

one or more processors; and

one or more non-transitory computer-readable media storing instructions that are executable by the one or more processors to perform operations comprising;

sending, from a management system, a first request to provide first data associated with a plurality of network entities;

in response to determining that the first request timed out, creating a plurality of smaller requests based on the first request;

sending the plurality of smaller requests, each of the plurality of smaller requests requesting data from a subset of the plurality of network entities;

identifying a particular network entity of the plurality of network entities that caused the first request to time out based on responses to the plurality of smaller requests;

adding the particular network entity to a set of confirmed problematic entities; and

sending a second request to provide second data associated with a portion of the plurality of network entities that excludes the particular network entity.

15. The computing device of claim 14, wherein the network entities comprise at least one of:

a plurality of virtual machines hosted by a plurality of host nodes,

a plurality of network links,

a plurality of storage devices, or

a plurality of sub-networks.

16. The computing device of claim 14, further comprising:

sending, after a predetermined period of time, a third request to provide third data associated with the plurality of network entities including the particular network entity.

17. The computing device of claim 15, further comprising:

in response to receiving a response to the third request, removing the particular network entity from the set of confirmed problematic entities.

18. The computing device of claim 15, further comprising:

in response to the response to the third request timing out, continuing to include the particular network entity in the set of confirmed problematic entities.

19. The computing device of claim 14, further comprising:

incrementing a counter associated with the particular network entity in response to determining that the particular network entity caused a subsequent request to time out; and

placing the particular network entity on the blacklist in response to determining that the counter satisfies a predetermined threshold.

20. The computing device of claim 14, wherein the first request comprises:

an identifier associated with each of the plurality of network entities, and

specifies one or more types of data to request from the plurality of network entities.