System and method for traffic management in a network management system

• US 5,922,051 A
• Filed: 05/14/1997
• Issued: 07/13/1999
• Est. Priority Date: 05/14/1997
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: NCR Corporation
• Inventors: Sidey, Michael J.
• Primary Examiner(s): Ramirez, Ellis B.
• Application Number:
  US08/855,691
• Time in Patent Office: 790 Days
• Field of Search: 395/200.32, 395/200.33, 395/200.53, 395/200.54
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/142 using statistical or mathematical methods
• CPC Class Codes: H04L 41/16 using machine learning or artificial intelligence
• CPC Class Codes: H04L 43/103 with adaptive polling, i.e. dynamically adapting the polling rate
• CPC Class Codes: H04L 43/50 Testing arrangements

Abstract

For use in a computer network having a plurality of nodes associated therewith, a data traffic management system for managing data traffic among the plurality of nodes, comprising 1) a polling circuit that retrieves node traffic information from the plurality of nodes; and 2) process logic that compares first selected node traffic information associated with a first selected one of the plurality of nodes with a first threshold level to detect a trend in the first selected node traffic information with respect to the first threshold level.

Claims

1. For use in a computer network having a plurality of nodes associated therewith, a data traffic management system for managing data traffic among said plurality of nodes, comprising:

a polling circuit that retrieves node traffic information from said plurality of nodes; and

process logic that compares first selected node traffic information associated with a first selected one of said plurality of nodes with a first threshold level to detect a trend in said first selected node traffic information with respect to said first threshold level wherein said process logic, in response to a detection of said trend, modifies a polling rate at which said polling circuit retrieves said first selected node traffic information.

2. The data traffic management system as recited in claim 1 wherein said modification is an increase in said polling rate in response to a trend indicating that an error rate of said data traffic is increasing toward said first threshold level.

3. The data traffic management system as recited in claim 1 wherein said modification is a decrease in said polling rate in response to a trend indicating that an error rate of said data traffic is decreasing away from said first threshold level.

4. The data traffic management system as recited in claim 1 wherein said process logic, in response to a determination that said first selected node traffic information has exceeded said first threshold level for only an insignificant period of time, suppresses an alarm indicating that node traffic information has exceeded said first threshold level.

5. The data traffic management system as recited in claim 4 wherein said process logic compares a number of suppressed alarms occurring during a predetermined time interval to a suppressed alarm threshold rate and, in response to a determination that said number of suppressed alarms exceeds said suppressed alarm threshold rate, triggers an alarm indicating that said suppressed alarm threshold rate has been exceeded.

6. The data traffic management system as recited in claim 1 wherein said process logic compares second selected node traffic information associated with a second selected one of said plurality of nodes with a second threshold level to detect a trend in said second selected node traffic information with respect to said second threshold level.

7. The data traffic management system as recited in claim 6 wherein said process logic triggers an urgent alarm in response to a determination that first selected node traffic information and said second selected node traffic information are simultaneously exceeding said first and second threshold levels, respectively.

8. The data traffic management system as recited in claim 1 wherein said process logic alerts a system operator to maintenance activities in said computer network that coincide with faults detected by said process logic.

9. The data traffic management system as recited in claim 1 wherein said process logic alerts a system operator to external disturbances occurring at one of said plurality of nodes that coincide with faults detected by said process logic.

10. The data traffic management system as recited in claim 1 wherein said process logic generates data traffic to test a data traffic capacity of a selected one of said plurality of nodes.

11. The data traffic management system as recited in claim 1 wherein said process logic associates an eventual outcome with said trend, wherein said eventual outcome causes said process logic to alert a system operator to take corrective action.

12. The data traffic management system as recited in claim 1, wherein said node traffic information includes MIB objects.

13. The data traffic management system as recited in claim 12, wherein said MIB objects include statistical information including a number of bad packets received at a particular node.

14. The data traffic management system as recited in claim 1, wherein said process logic is implemented in expert system software.

15. The data traffic management system as recited in claim 1, wherein said trend is an average bad packet frequency rate during a pre-defined timing window and a rate of change for each node.

16. For use in a computer network having a plurality of nodes associated therewith, a method of managing data traffic among said plurality of nodes, comprising the steps of:

retrieving node traffic information from said plurality of nodes; and

comparing first selected node traffic information associated with a first selected one of said plurality of nodes with a first threshold level to detect a trend in said first selected node traffic information with respect to said first threshold level modifying a polling rate at which said polling circuit retrieves said first selected node traffic information in response to a detection of said trend.

17. The method as recited in claim 16 wherein said modifying step includes increasing said polling rate in response to a trend indicating that an error rate of said data traffic is increasing toward said first threshold level.

18. The method as recited in claim 16 wherein said modifying step includes decreasing said polling rate in response to a trend indicating that an error rate of said data traffic is decreasing away from said first threshold level.

19. The method as recited in claim 16 including the further step of suppressing an alarm indicating that node traffic information has exceeded said first threshold level in response to a determination that said first selected node traffic information has exceeded said first threshold level for only an insignificant period of time.

20. The method as recited in claim 19 including the further step of comparing a number of suppressed alarms occurring during a predetermined time interval to a suppressed alarm threshold rate and, in response to a determination that said number of suppressed alarms exceeds said suppressed alarm threshold rate, triggering an alarm indicating that said suppressed alarm threshold rate has been exceeded.

21. The method as recited in claim 16 including the further step of comparing second selected node traffic information associated with a second selected one of said plurality of nodes with a second threshold level to detect a trend in said second selected node traffic information with respect to said second threshold level.

22. The method as recited in claim 21 including the further step of triggering an urgent alarm in response to a determination that first selected node traffic information and said second selected node traffic information are simultaneously exceeding said first and second threshold levels, respectively.

23. The method as recited in claim 16 including the further step of alerting a system operator to maintenance activities in said computer network that coincide with detection of said trend.

24. The method as recited in claim 16 including the further step of alerting a system operator to external disturbances occurring at one of said plurality of nodes that coincide with detection of said trend.

25. The method as recited in claim 16 including the further step of generating data traffic to test a data traffic capacity of a selected one of said plurality of nodes.

26. The method as recited in claim 16 including the further step of causing selected network nodes to block data traffic on a selected communication path between a first selected network node and a second selected network node to thereby cause data traffic to be redirected to an alternate communication path between said first selected network node and said second selected network node.

27. The method as recited in claim 16 including the further step of associating an eventual outcome with said trend, wherein said eventual outcome causes an alert to be communicated to a system operator so that said system operator may take corrective action.

28. The method as recited in claim 16, wherein said node traffic information includes MIB objects.

29. The method as recited in claim 28, wherein said MIB objects include statistical information including a number of bad packets received at a particular node.

30. The method as recited in claim 16, wherein said process logic is implemented in expert system software.

31. The method as recited in claim 16, wherein said trend is an average bad packet frequency rate during a pre-defined timing window and a rate of change for each node.