Structure for event reporting in SNMP systems

• US 20040006619A1
• Filed: 07/02/2002
• Published: 01/08/2004
• Est. Priority Date: 07/02/2002
• Status: Abandoned Application

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Network Communications Incorporated (Fujitsu Limited)
• Inventors: Syed, Sharfuddin, Wu, Guoliang, Bryttegard, Robert, Chang, Ted D.
• Application Number:
  US10/189,131
• Publication Number:
  US 20040006619A1
• Time in Patent Office: Days
• 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/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

In a system using simple network management protocol, elements report events to a network management system using a generic trap structure. The trap structure includes fields for identifying details on an object experiencing an event and detailing the event, and potentially includes management information for tracking individual trap messages.

Claims

1. A method for reporting events, the method comprising:

detecting an event in a simple network management protocol (SNMP) system, the event affecting an object;

generating a trap message comprising object information identifying the object and event information comprising a plurality of fields characterizing the event; and

communicating the trap message to a network management system.

2. The method of claim 1, wherein the trap message further comprises management information that includes a sequence number for the trap message.

3. The method of claim 1, wherein the fields comprise an event type, a severity, a condition effect, a service effect, a location, and a direction.

4. The method of claim 1, wherein the object information comprises an object identifier and an object name.

5. The method of claim 4, wherein the object identifier indicates an SNMP object identifier assigned to the object and the object name indicates a translation language 1 (TL1) access identifier (AID) for the object.

6. The method of claim 1, wherein the object comprises a managed element within a network element, the method further comprising receiving the event information from the managed element.

7. The method of claim 1, further comprising storing the trap message in a memory.

8. The method of claim 7, further comprising:

receiving a request to retransmit the trap message;

retrieving the trap message from the memory; and

re-communicating the trap message to the network management system.

9. The method of claim 8, wherein the request to retransmit indicates a sequence number of the trap message.

10. A network element comprising:

a plurality of managed elements; and

a simple network management protocol (SNMP) agent operable to detect an event affecting one of the managed elements, to generate a trap message comprising object information identifying the affected managed element and event information comprising a plurality of fields characterizing the event, and to communicate the trap message to a network management system.

11. The network element of claim 10, wherein the trap message further comprises management information that includes a sequence number for the trap message.

12. The network element of claim 10, wherein the fields comprise an event type, a severity, a condition effect, a service effect, a location, and a direction.

13. The network element of claim 10, wherein the object information comprises an object identifier and an object name.

14. The network element of claim 13, wherein the object identifier indicates an SNMP object identifier assigned to the object and the object name indicates a translation language 1 (TL1) access identifier (AID) for the object.

15. The network element of claim 10, further comprising an event interface operable to receive the event information from the managed element and to relay the event information to the SNMP agent.

16. The network element of claim 10, further comprising a memory, wherein the SNMP agent is further operable to store the trap message in the memory.

17. The network element of claim 16, further comprising:

receiving a request to retransmit the trap message, the request indicating a sequence number of the trap message;

retrieving the trap message from the memory device using the sequence number; and

re-communicating the trap message to the network management system.

18. Logic for reporting events, the logic encoded in a medium and operable when executed to:

detect an event in a simple network management protocol (SNMP) system, the event affecting an object;

generate a trap message comprising object information identifying the object and event information comprising a plurality of fields characterizing the event; and

communicate the trap message to a network management system.

19. The logic of claim 18, wherein the trap message further comprises management information that includes a sequence number for the trap message.

20. The logic of claim 18, wherein the fields comprise an event type, a severity, a condition effect, a service effect, a location, and a direction.

21. The logic of claim 18, wherein the object information comprises an object identifier and an object name.

22. The logic of claim 21, wherein the object identifier indicates an SNMP object identifier assigned to the object and the object name indicates a translation language 1 (TL1) access identifier (AID) for the object.

23. The logic of claim 18, wherein the object comprises a managed element within a network element, the logic further operable to receive the event information from the managed element.

24. The logic of claim 18, further operable to:

store the trap message in a memory;

receive a request to retransmit the trap message, the request indicating a sequence number of the trap message;

retrieve the trap message from the memory device using the sequence number; and

re-communicate the trap message to the network management system.

25. A network element comprising:

means for detecting an event in a simple network management protocol (SNMP) system, the event affecting an object;

means for generating a trap message comprising object information identifying the object and event information comprising a plurality of fields characterizing the event; and

means for communicating the trap message to a network management system.

26. A method for reporting events, the method comprising:

detecting an event in a simple network management protocol (SNMP) system, the event affecting an object;

generating a trap message comprising object information, event information, and a sequence number, the object information comprising an object identifier indicating an SNMP object identifier assigned to the object and an object name indicating a translation language 1 (TL1) access identifier (AID) for the object, the event information comprising an event type, a severity, a condition effect, a service effect, a location, and a direction; and

communicating the trap message to a network management system.