Title of Invention: System and method to manage set history for simple network management protocol
Abstract: A system and method to manage a SET history of a simple network management protocol (SNMP), the system including an SNMP manager to access a network apparatus and to request an object ID, and an SNMP agent to set the object ID in response to the request and to transmit corresponding set information to a plurality of SNMP managers connected to a network so that a set history of the object ID can be stored and managed with respect to each SNMP manager.
Detailed Description: Part general_description_paragraphs: Part CROSS-REFERENCE TO RELATED APPLICATIONS: This application claims the benefit of Korean Patent Application No. 2005-43763, filed on May 24, 2005, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein in its entirety by reference.
Part BACKGROUND OF THE INVENTION: 1. Field of the Invention
The present general inventive concept relates to a method of managing a simple network management protocol (SNMP), and more particularly, to a system and method to manage a set history for an SNMP.
2. Description of the Related Art
FIG. 1 illustrates a basic communication operation of an SNMP. Referring to FIG. 1, an SNMP manager manages a network through three types of commands: GET commands, SET commands, and TRAP commands. A GET command allows the SNMP manager to retrieve an object ID from an SNMP agent. A SET command allows the SNMP manager to change the object ID of the SNMP agent. A TRAP command informs the SNMP manager of a specific condition in the SNMP agent or in the network. For example, a TRAP command may be a warning or error message transmitted from the SNMP agent to the SNMP manager to notify the SNMP manager about the SNMP agent's condition. Unlike GET and SET commands, TRAP commands are asynchronous and are not solicited by the SNMP manager.
Referring to FIG. 1, the SNMP manager retrieves an object ID from the SNMP agent using a GET-REQUEST command. In addition, the SNMP manager retrieves a further object ID subsequent to the object ID that the SNMP manager has previously-retrieved, or a subsequent index when the object ID is a table, using a GETNEXT-REQUEST command.
When a GET-RESPONSE command is transmitted by the SNMP agent, the SNMP agent returns the object ID corresponding to the request of the SNMP manager. The SNMP manager requests the SNMP agent to change the object ID using a SET-REQUEST command. The SNMP agent reports a specific condition in the SNMP agent to the SNMP manager using a TRAP command.
FIG. 2 is a flowchart illustrating a procedure in which a conventional SNMP manager sets an object ID. In operation 200, the SNMP manager accesses a network apparatus having an SNMP agent and requests the SNMP agent to set a particular object value using a SET-REQUEST command. In operation 210, an SNMP agent sets the object ID according to the SET-REQUEST of the SNMP manager. In operation 220, the SNMP agent transmits set information corresponding to the set object ID to the SNMP manager using a GET-RESPONSE command.
Conventionally, when an SNMP manager changes or sets an object ID of an SNMP agent on a network using a SET-REQUEST command, the SNMP agent transmits the corresponding set information in a GET-RESPONSE command only to that SNMP manager (i.e., only to the SNMP manager that transmitted the SET-REQUEST to the SNMP agent). Other SNMP managers on the network do not receive the GET-RESPONSE command from the SNMP agent, and therefore do not receive the set information. Although, these other SNMP managers on the network can determine a current object value of the SNMP agent (i.e., the set object value based on the SET-REQUEST), these other SNMP managers cannot obtain past set-information (i.e., set information based on previous SET-REQUEST commands by one or more different SNMP managers). For example, when set information such as the name of a network apparatus that is difficult to memorize has been changed by one or more SNMP managers, it is not known what specific SNMP manager set the changed/current name of the network apparatus. Furthermore, even if the specific SNMP manager that set the changed/current name is known, it is inconvenient to return the name from the changed/current name to a past name because a complicated apparatus name must be directly/manually input into the corresponding SNMP agent.
Part SUMMARY OF THE INVENTION: The present general inventive concept provides a system and method of storing and managing a set history of an object ID for each SNMP manager by transmitting set information set by an SNMP agent to all SNMP managers connected to a network, thereby overcoming the inconvenience of manually inputting past object ID information, since the past object ID information is not known after the SNMP manager requests the SNMP agent to set an object ID.
Additional aspects and advantages of the present general inventive concept will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the general inventive concept.
“Set information” refers to various types of information relating to an SNMP manager requesting an SNMP agent to set an object ID. For example, “set information” may include one or more of: an SNMP management information base (MIB) object ID with respect to a host name that has been set, an IP address of the SNMP manager that transmitted the SET-REQUEST command to the SNMP agent, and a time and a date when the host name was set based on the SET-REQUEST. “Set history” refers to a collection of set information for a given SNMP agent, and includes set information resulting from one or more SET-REQUESTS transmitted by one or more SNMP managers to the given SNMP agent.
The foregoing and/or other aspects and utilities of the present general inventive concept may be achieved by providing a system for managing a set history of an SNMP, the system including an SNMP manager to access a network apparatus and to request an object ID, and an SNMP agent to set the object ID in response to the request and to transmit corresponding set information to a plurality of SNMP managers connected to a network.
The SNMP agent may transmit the set information to the plurality of SNMP managers using a TRAP command.
The system may further include a storage unit to store a set history.
The storage unit may be one of a set history log file and a database.
The SNMP manager may include a controller to receive the set information from the SNMP agent and to store the set information in the storage unit.
The SNMP manager may further include a reader to read the set history stored in the storage unit.
The SNMP manager may further include a selector to select an item to be applied from the set history read by the reader; and a controller to request the SNMP agent to set an object ID of the item selected by the selector.
The foregoing and/or other aspects and utilities of the present general inventive concept may also be achieved by providing a method to manage a set history of an SNMP, the method including accessing a network apparatus containing an SNMP agent and requesting an object ID from the SNMP agent using an SNMP manager, and setting the object ID in response to the request and transmitting corresponding set information to a plurality of SNMP managers connected to a network using an SNMP agent.
The transmitting the corresponding set information may include transmitting the corresponding set information to the plurality of SNMP managers using a TRAP command.
The method may further include receiving the set information from the SNMP agent and storing the set information in a storage unit.
The storage unit may store a set history.
The storage unit may be one of a set history log file and a database.
The method may further include reading the set history stored in the storage unit.
The method may further include, selecting an item to be applied from the set history using a SNMP manager, and accessing the network apparatus and requesting the SNMP agent to set an object ID of the selected item.
The foregoing and/or other aspects and utilities of the present general inventive concept may also be achieved by providing a method of managing an SNMP, the method comprising requesting an SNMP agent to set an object ID, setting the object ID, and transmitting corresponding set information to a plurality of networked SNMP managers. The transmitting corresponding set information may transmit using a TRAP command. The method may further comprise storing the set information as set history in one or more of the plurality of networked SNMP managers.
The foregoing and/or other aspects and utilities of the present general inventive concept may also be achieved by providing an SNMP apparatus comprising at least one SNMP agent and a plurality of SNMP managers comprising a plurality of storage units to store set information obtained from the at least one SNMP agent. The at least one SNMP agent may be configured to transmit set information using a TRAP command. At least one of the plurality of storage units may comprise a set history of the SNMP agent.
The foregoing and/or other aspects and utilities of the present general inventive concept may also be achieved by providing a computer readable recording medium, comprising instructions for an SNMP agent to transmit set information to at least one SNMP manager, and instructions for a plurality of SNMP managers to store the set information. The computer readable recording medium may further comprise instructions for the SNMP agent to transmit the set information to the at least one SNMP manager using a TRAP command.
Part DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS: Reference will now be made in detail to the embodiments of the present general inventive concept, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below in order to explain the present general inventive concept by referring to the figures.
FIG. 3 is a block diagram illustrating a system to manage a set history of a simple network management protocol (SNMP) according to an embodiment of the present general inventive concept. Referring to FIG. 3, the system includes an SNMP manager 300 and an SNMP agent 310.
The SNMP manager 300 accesses an SNMP agent 310 of a network apparatus and requests the SNMP agent 310 to set an object ID. Since the SNMP manager 300 requests the SNMP agent 310 to set the object ID, a SET-REQUEST command may be used.
In response to the SET-REQUEST, the SNMP agent 310 sets the object ID, thereby changing the object ID from a previous object ID to a changed object ID. The SNMP agent 310 transmits corresponding set information to each of SNMP managers 300, 301, and 302 connected to a network. In this embodiment, the SNMP agent 310 transmits the set information using a TRAP command to each of SNMP managers 300, 301, and 302.
Conventionally, a TRAP command is used by the SNMP agent 310 to report a condition of the SNMP agent 310 (such as a warning or error message) to each of the SNMP managers 300, 301, and 302. For example, when a network resource is used in an amount exceeding a threshold amount, this fact is reported to each of the SNMP managers 300, 301, and 302 by the SNMP agent 310 using a TRAP command. Unlike GET and SET commands, TRAP commands are asynchronous and are not solicited by an SNMP manager. Because the SNMP agent 310 sets the object ID in response to the SET-REQUEST of the SNMP manager 300 (a synchronous command), this situation is not a situation that would be reported by the SNMP agent 310 to the SNMP manager 300 using a TRAP command. In contrast, a GET-RESPONSE instead of a TRAP command would be used by the SNMP agent 310 to report the set information exclusively to the SNMP manager 300.
However, in this embodiment and in contrast to a conventional SNMP, the SNMP agent 310 reports the set information of the object ID to each of the SNMP managers 300, 301, and 302 using a TRAP command so that a set history can be managed for each of the SNMP managers 300, 301, and 302.
Referring to FIG. 3, the system to manage a set history of an SNMP may further include storage units 320, 321, and 322 respectively-connected to the SNMP managers 300, 301, and 302. The storage units 320, 321, and 322 store a set history for the SNMP agent 310. The storage units 320, 321, and 322 may be included within the respective SNMP managers 300, 301, and 302, or externally-connected thereto. The storage units 320, 321, and 322 may be implemented in a form of a set history log file or a database.
The SNMP managers 300, 301, and 302 may also respectively include readers 330, 331, and 332, selectors 340, 341, and 342, and controllers 350, 351, and 352. The readers 330, 331, and 332 respectively read a set history or set histories stored in the storage units 320, 321, and 322.
FIG. 5 illustrates a user interface to execute a function of the readers 330, 331, and 332 according to an embodiment of the present general inventive concept. Referring to FIG. 5, device information of a printer can be viewed on the user interface. In detail, the user interface displays an Internet Protocol (IP) address, a subnet mask, and a gateway address, which correspond to a host name (SEC0000f0ae5408). When a set history button 500 implementing the reader 330, 331, or 332 is clicked, a host will read the set history of the SNMP agent 310 from the storage unit 320, 321, or 322.
The selectors 340, 341, and 342 select an item to be applied from the set history read from the readers 330, 331, and 332, respectively.
FIG. 6 illustrates a user interface to execute a function of the selectors 330, 331, and 332 according to an embodiment of the present general inventive concept. When the set history button 500 illustrated in FIG. 5 is clicked, a set history is displayed on the user interface illustrated in FIG. 6. Here, “OID” is an SNMP management information base (MIB) object ID with respect to a host name that has been set and a “Set value” is a value of the host name. “Manager's IP address” is an IP address of a SNMP manager that made a SET-REQUEST. “Modified time” indicates a time and a date when the host name was set based on a SET-REQUEST.
When a desired item in a set history is clicked, the item (e.g., an inverted region 600) is selected. Thereafter, when an apply button is clicked, device information corresponding to the selected item is selected.
The controllers 350, 351, and 352 store messages received from the SNMP agent 310 in the storage units 320, 321, and 322, respectively. In addition, the controllers 350, 351, and 352 request the SNMP agent 310 to set object IDs of items selected by the selectors 340, 341, and 342, respectively.
FIG. 4 is a flowchart illustrating a method of managing a set history of an SNMP according to an embodiment of the present general inventive concept. The method illustrated in FIG. 4 will be described with reference to FIG. 3.
Referring to FIGS. 3 and 4, when one of the SNMP managers 300, 301, and 302 (e.g., the SNMP manager 300) changes an object ID of the SNMP agent 310, in operation 400 the reader 330 reads set history information from the storage unit 320 and displays the set history on a screen. In operation 410, an item to be set is selected from the set history and is applied using the selector 340. In operation 420, the controller 350 of the SNMP manager 300 accesses a network apparatus containing the SNMP agent 310, and requests the SNMP agent 310 to set an object ID corresponding to the item selected by the selector 340. In operation 430, the SNMP agent 310 sets the object ID according to the request. In operation 440, the SNMP agent 310 transmits the set information to each of the SNMP managers 300, 301, and 302 connected to the network using a TRAP command. In operation 450, upon receiving the set information of the object ID through the TRAP command, the controllers 350, 351, and 352 of the respective SNMP managers 300, 301, and 302 store the set information in the storage units 320, 321, and 322, respectively.
Embodiments of the present general inventive concept can be written as computer programs and can be implemented in general-use digital computers that execute the programs using a computer readable recording medium. Examples of the computer readable recording medium include magnetic storage media such as ROM, floppy disks, hard disks, etc., optical recording media such as CD-ROMs and DVDs, and storage media.
According to the present general inventive concept, when an SNMP manager requests an SNMP agent to set an object ID, the SNMP agent sets the object ID and transmits set information to all SNMP managers connected to a network so that a set history of the object ID can be stored and managed with respect to each SNMP manager. Accordingly, an SNMP manager can easily select and reset information in the SNMP agent that the SNMP manager had not previously-set (i.e., information that had been previously-set by another, different, SNMP manager).
Although a few embodiments of the present general inventive concept have been shown and described, it will be appreciated by those skilled in the art that changes may be made in these embodiments without departing from the principles and spirit of the general inventive concept, the scope of which is defined in the appended claims and their equivalents.


{'bibliographic_information': "{'country': 'US', 'doc-number': '11419240', 'kind': 'B2', 'date': '20060519', 'extension': '1159', 'invention_title': 'System and method to manage set history for simple network management protocol'}", 'source_file': './grant/2014/ipg140204.xml', 'source_data': 'USPTO-Grant'}