CESSATION OF SENDING NETWORK STATUS MESSAGES TO A SERVER

• US 20110099236A1
• Filed: 10/28/2009
• Published: 04/28/2011
• Est. Priority Date: 10/28/2009
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: FORD, Daniel E., VUONG, Anh Tuan
• Granted Patent: US 8,612,524 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 41/0627 by acting on the notification or alarm source
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring

Abstract

A system comprises a processor, a network interface coupled to the processor, and storage accessible to the processor. The network interface is configured to receive network status messages from a plurality of agents across a network. Each network status message indicates a status of a network. The storage comprises a plurality of queues with each queue corresponding to one of the agents. The network status messages from a given agent are stored in a queue corresponding to that agent pending processing by the processor. Upon a number of network status messages in a queue for a particular agent exceeding an agent high water mark, the processor sends a stop message through the network interface to such agent to cause such agent to cease sending network status messages.

Claims

1. A system, comprising:

a processor;

a network interface coupled to said processor, said network interface configured to receive network status messages from a plurality of agents across a network, each network status message indicates a status of a network; and

storage accessible to said processor and said network interface, said storage comprising a plurality of queues with each queue corresponding to one of said agents, and wherein network status messages from a given agent are stored in a queue corresponding to said agent pending processing by said processor;

wherein, upon a number of network status messages in a queue for a particular agent exceeding an agent high water mark, said processor sends a stop message through said network interface to such agent to cause such agent to cease sending network status messages.

2. The system of claim 1 wherein, upon the number of network status messages in said queue falls below an agent low water mark, said processor sends a start message through said network interface to such agent to cause such agent to again send network status messages.

3. The system of claim 1 further comprising a global high water mark corresponding to said system and wherein, upon an aggregate number of network status messages in all of said queues exceeds said global high water mark, said processor sends a stop message through said network interface to each of said agents to cause each agent to cease sending network status messages.

4. The system of claim 3 further comprising a global low water mark corresponding to said system and wherein, upon the aggregate number of network status messages in all of said queues falls below said global low water mark, said processor sends a start message through said network interface to each of said agents to cause each agent to again send network status messages.

5. The system of claim 1 further comprising, for each queue, an agent high water mark and an agent low water mark, the agent high and low water marks being separately configurable for each queue.

6. A system, comprising:

a processor;

a network interface coupled to said processor, said network interface configured to receive network status messages from a plurality of agents across a network, each network status message indicates a status of a network; and

storage accessible to said processor and said network interface, said storage comprising a plurality of queues with each queue corresponding to one of said agents, and wherein network status messages from a given agent are stored in a queue corresponding to said agent pending processing by said processor;

wherein, upon a number of network status messages in a queue for a particular agent exceeding an agent high water mark, said processor sends a stop message through said network interface to such agent to cause such agent to cease sending network status messages and, upon said number of network status messages in said queue falling below an agent low water mark said processor sends a start message to such agent to again send network status messages; and

wherein, upon an aggregate number of network status messages in all of said queues exceeding a global high water mark, said processor sends a stop message through said network interface to all of said agents to cause all of said agents to cease sending network status messages.

7. The system of claim 6 further comprising a global low water mark wherein, upon the aggregate number of network status messages in all of said queues falls below said global low water mark, said processor sends a start message through said network interface to each of said agents to cause each agent to again send network status messages.

8. The system of claim 6 wherein said agent low and high water marks comprise thresholds and the threshold of the high water mark is greater than the threshold of the low water mark.

9. A method, comprising:

adding a network status message received over a network from a remote agent into a queue associated with said remote agent;

upon adding said network status message to said queue, determining if a number of network status messages in said queue exceeds an agent-specific upper threshold;

when said number of network status messages exceeds said agent-specific upper threshold, sending a stop message to said remote agent over said network, said stop message requesting the remote agent to cease sending network status messages;

removing a network status message from said queue for processing;

upon removing said network status message from said queue, determining if the number of network status messages in said queue falls below an agent-specific lower threshold;

when said number of network status messages falls below said agent-specific lower threshold, sending a start message to said remote agent, said start message requesting the remote agent to again send network status messages.

10. The method of claim 9 wherein said upper threshold corresponds to just the remote agent associated with said queue.

11. The method of claim 9 further comprising, upon adding said network status message to said queue, determining if an aggregate number of network status messages in a plurality of queues exceeds a global upper threshold.

12. The method of claim 11 wherein when the aggregate number of network status messages exceeds said global upper threshold, sending a stop message to all remote agents in the network to cease sending network status messages.

13. The method of claim 11 wherein when the aggregate number of network status messages exceeds said global upper threshold, sending a stop message to at least one remote agent in the network to cease sending network status messages.

14. The method of claim 9 further comprising, upon removing said network status message to said queue, determining if an aggregate number of network status messages in a plurality of queues is below a global lower threshold.

15. The method of claim 14 wherein when the aggregate number of network status messages is below said global lower threshold, sending a start message to at least one remote agent in the network to start sending network status messages.