SNMP trap and inform shaping mechanism

• US 20030195922A1
• Filed: 04/10/2002
• Published: 10/16/2003
• Est. Priority Date: 04/10/2002
• Status: Abandoned Application

• Current Assignee: Alcatel SA (Nokia Corporation)
• Original Assignee: Alcatel SA (Nokia Corporation)
• Inventors: Butler, Clive, Andrews, Ken
• Application Number:
  US10/118,894
• Publication Number:
  US 20030195922A1
• Time in Patent Office: Days
• US Class Current: 709/202
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 43/0811 by checking connectivity

Abstract

At system initialization, the core routers and the edge routers will begin to exchange routing information that is required for the network to become operational. The notification shaping method of the present invention can be used to prevent the core router from flooding the edge routers with notifications while the edge routers are trying to process routing updates. In the present invention, notifications are sent in a steady flow, and not in bursts. The notification shaping method uses a timer to process the notifications stored in the notification queue. In addition, the notification shaping method comprises three basic steps. Step 1 comprises putting an entry on the notification queue. Step 2 comprises timer expiration. Step 3 comprises responding to an inform.

Claims

1. A router, comprising:

a rack;

at least one line card operably connected to said rack;

at least one switching fabric card operably connected to said at least one line card;

a management server comprising management software stored in a first memory operably connected to said at least one switching fabric card;

a route server comprising routing software stored in a second memory operably connected to said line cards; and

a database operably connected to said management server.

2. The router according to claim 1, wherein said management server comprises a master agent-subagent architecture.

3. The router according to claim 2, wherein said master agent-subagent architecture comprises:

a manager; and

a master agent-subagent operably connected to said manager, comprising;

a notification generator;

a notification queue operably connected to said notification generator;

a timer operably connected to said notification queue; and

a retransmission queue operably connected to said timer.

4. The router according to claim 3, further comprising a notification root operably connected to said notification queue, whereby notifications stored in said notification queue are pointed to.

5. The router according to claim 3, further comprising a retransmission root operably connected to said retransmission queue, whereby notifications stored in said retransmission queue are pointed to.

6. The router according to claim 3, wherein said routing software comprise protocols that hold IP addresses and create routing tables containing routes to each of said IP addresses.

7. The router according to claim 3, wherein said line cards are SONET cards.

8. The router according to claim 3, wherein said line cards are Ethernet cards.

9. The router according to claim 3, wherein a system configuration is stored in said database.

10. The router according to claim 3, wherein said manager comprises a management protocol.

11. The router according to claim 3, wherein said manager is a simple network browser protocol manager.

12. The router according to claim 10, wherein said management protocol is a simple network browser protocol.

13. The router according to claim 12, further comprising:

a notification root operably connected to said notification queue, whereby notifications stored in said notification queue are pointed to;

a retransmission root operably connected to said retransmission queue, whereby notifications stored in said retransmission queue are pointed to; and

wherein said routing software comprise protocols that hold IP addresses and create routing tables containing routes to each of said IP addresses, wherein said line cards are SONET cards, wherein said line cards are Ethernet cards, wherein a system configuration is stored in said database, and wherein said manager is a simple network browser protocol manager.

14. An apparatus to control the flow of notifications, comprising:

a manager; and

a master agent-subagent operably connected to said manager, comprising;

a notification generator;

a notification queue operably connected to said notification generator;

a timer operably connected to said notification queue; and

a retransmission queue operably connected to said timer.

15. The apparatus according to claim 14, further comprising a notification root operably connected to said notification queue, whereby notifications stored in said notification queue are pointed to.

16. The apparatus according to claim 14, further comprising a retransmission root operably connected to said retransmission queue, whereby notifications stored in said retransmission queue are pointed to.

17. The apparatus according to claim 14, wherein said manager comprises a management protocol.

18. The apparatus according to claim 14, wherein said manager is a simple network browser protocol manager.

19. The apparatus according to claim 14, wherein said manager comprises a simple network browser management protocol.

20. The apparatus according to claim 15, further comprising:

a retransmission root operably connected to said retransmission queue, whereby notifications stored in said retransmission queue are pointed to; and

wherein said manager comprises a simple network browser protocol and is a simple network browser protocol manager.

21. An apparatus to control the flow of notifications, comprising:

an agent, comprising;

a notification generator;

a notification queue operably connected to said notification generator;

a timer operably connected to said notification queue; and

a retransmission queue operably connected to said timer.

22. The apparatus according to claim 21, further comprising a notification root operably connected to said notification queue, whereby notifications stored in said notification queue are pointed to.

23. The apparatus according to claim 21, further comprising a retransmission root operably connected to said retransmission queue, whereby notifications stored in said retransmission queue are pointed to.

24. The apparatus according to claim 21, wherein said agent is operably connected to a manager comprising a management protocol.

25. The apparatus according to claim 21, wherein said agent is a simple network browser protocol agent.

26. The apparatus according to claim 24, wherein said manager comprises a simple network browser management protocol.

27. The apparatus according to claim 22, further comprising:

a retransmission root operably connected to said retransmission queue, whereby notifications stored in said retransmission queue are pointed to; and

a manager operably connected to said agent comprising a simple network browser protocol.

28. A method of controlling the flow of notifications, comprising the steps of:

putting an entry on a notification queue;

expiring a timer; and

responding to an inform.

29. The method controlling the flow of notifications according to claim 28, wherein said step of putting an entry on a notification queue further comprises:

acknowledging said entry if it is an inform;

transmitting the notification if a transmission rate is below a threshold;

discarding the notification if said transmission rate is above said threshold and said notification queue is full; and

adding the notification to said notification queue if said transmission rate above said threshold and said notification queue is not full.

30. The method of controlling the flow of notifications according to claim 28, wherein said step of expiring a timer further comprises:

finding a first notification pointed to by a notification root;

removing and sending said first notification;

checking if a notification window is open;

removing and sending another notification if said notification window is open;

checking if there are any said notifications on said queue if said notification window is not open;

logging a warning if said notification window is not open and there are no said notifications on said queue; and

setting another timer if said notification window is not open and there are said notifications on said queue.

31. The method of controlling the flow of notifications according to claim 28, wherein said step of responding to an inform further comprises:

receiving the inform; and

locating and destroying any queued retransmissions.

32. The method of controlling the flow of notifications according to claim 29, wherein said step of expiring a timer further comprises:

finding a first notification pointed to by a notification root;

removing and sending said first notification;

checking if a notification window is open;

removing and sending another notification if said notification window is open;

checking if there are any said notifications on said queue if said notification window is not open;

logging a warning if said notification window is not open and there are no said notifications on said queue; and

setting another timer if said notification window is not open and there are said notifications on said queue; and

wherein said step of responding to an inform further comprises;

receiving the inform; and

locating and destroying any queued retransmissions.

33. The method according to claim 32, further comprising the step of putting said inform on a retransmission list.

34. The method according to claim 32, further comprising the step of adding a timer entry if transmission rate above a threshold and notification queue is not full and a timer is not set.

35. The method according to claim 32, further comprising the step of determining if said transmission rate is above a threshold by counting the number of notifications sent in the last second.

36. The method according to claim 32, wherein said step of locating and destroying any queued retransmissions further comprises the step of removing an entry from a retransmission queue that has been responded to.