Method and system for managing multiple management protocols in a network element

• US 6,708,207 B1
• Filed: 06/03/1999
• Issued: 03/16/2004
• Est. Priority Date: 06/03/1999
• Status: Expired due to Term

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Network Communications Incorporated (Fujitsu Limited)
• Inventors: Chang, Ted D., Clouthier, Terry A., Sabelhaus, Michael G.
• Primary Examiner(s): Jean, Frantz B.
• Application Number:
  US09/325,683
• Time in Patent Office: 1,748 Days
• Field of Search: 709/223, 709/224, 709/226, 709/238, 709/233, 709/246, 370/389, 370/390, 370/466, 345/733, 345/744
• 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/0226 Mapping or translating multiple network management protocols
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04Q 3/0062 Provisions for network management

Abstract

In accordance with one embodiment of the present invention, a network element comprises a first subsystem operable to receive management transactions in a first management protocol and to map the transactions to a common management protocol. A second subsystem is operable to receive management transactions in a second management protocol and to map the transactions to the common management protocol. A common management information base (MIB) includes a dataset and a common interface to the dataset. The common interface is operable to access the dataset to process transactions received from the first and second subsystems in the common management protocol.

Claims

1. A network element, comprising:

a first subsystem operable to receive management transactions in a first management protocol and to map the management transactions to a common management protocol;

a second subsystem operable to receive management transactions in a second management protocol and to map the second transactions to the common management protocol; and

a common management information base (MIB) comprising a dataset and a common interface to the dataset, the interface comprising software stored in a computer-readable medium and operable to access the dataset to process transactions from the first and second subsystems in the common management protocol.

2. The network element of claim 1, further comprising:

a third subsystem operable to receive management transactions in a third management protocol and to map the transactions to the common management protocol; and

the common interface operable to access the dataset to process transactions received from the third subsystem in the common management protocol.

3. The network element of claim 2, further comprising:

the first subsystem operable to receive management transactions in a Common Management Information Service Element (CMISE) protocol and to map the transactions to the common management protocol;

the second subsystem operable to receive management transactions in a simple network management protocol (SNMP) and to map the transactions to the common management protocol; and

the third subsystem operable to receive management transactions in a Transaction Language One (TL-1) protocol and to map the transactions to the common management protocol.

4. The network element of claim 1, further comprising the first subsystem operable to receive management transactions in a Common Management Information Service Element (CMISE) protocol and to map the transaction to the common management protocol.

5. The network element of claim 1, further comprising the first subsystem operable to receive management transactions in a simple network management protocol (SNMP) and to map the transactions to the common management protocol.

6. The network element of claim 1, further comprising the first subsystem operable to receive management transactions in a Transaction Language One (TL-1) protocol and to map the transactions to the common management protocol.

7. The network element of claim 1, wherein the dataset is stored in a table format.

8. The network element of claim 1, the common management information base (MIB) further comprising:

a function set; and

the common interface operable to execute the common functions to process transactions received from the first and second subsystems in the common management protocol.

9. The network element of claim 1, the common management information base (MIB) further comprising:

a queue operable to store transactions received from the first and second subsystems in the common management protocol; and

the common interface operable to serially process transactions from the queue.

10. The network element of claim 1, the common management information base (MIB), further comprising:

a first subsystem queue operable to store responses to transactions received from the first subsystem in the common management protocol;

a second subsystem queue operable to store responses to transactions received from the second subsystem in the common management protocol; and

the common interface operable to generate responses to transactions and to store each response in the subsystem queue of a subsystem from which the transaction was received.

11. A method for managing a network element, comprising:

receiving at the network element from an external management station a first set of element management transactions in a first management protocol;

receiving at the network element from an external management station a second set of element management transactions in a second management protocol;

mapping the first set of management transactions to a common management protocol;

mapping the second set of management transactions to the common management protocol;

storing management information in a common dataset; and

accessing the common dataset to process transactions in the common management protocol.

12. The method of claim 11, further comprising mapping management transactions received in a third management protocol to the common management protocol.

13. The method of claim 12, further comprising:

mapping management transactions received in a Common Management Information Service Element (CMISE) protocol to the common management protocol;

mapping management transactions received in a simple network management protocol (SNMP) to the common management protocol; and

mapping management transactions received in a Transaction Language One (TL-1) protocol to the common management protocol.

14. The method of claim 11, further comprising:

storing a dataset in a non-volatile memory; and

accessing the dataset in the non-volatile memory to process transactions in the common management protocol.

15. The method of claim 11, further comprising:

storing a common function set; and

accessing the common function set to process transactions received in the common management protocol.

16. The method of claim 11, further comprising serially processing transactions in the common management protocol.