KR100484492B1 - Network management system for managing of state and problem in router system and method thereof - Google Patents

Abstract

Disclosed are a network management system and method for managing failure and state of a router system. The network management system according to the present invention collects the configuration information of the router system to generate the entity MIB, collects the interface information to generate the interface MIB, and collects the state information by shape and the failure occurrence information by shape to generate the private MIB. And stores the information and provides the required information with reference to the entity MIB, the interface MIB and the private MIB according to an external request, or communicates with the network management agent and the network management agent to notify the outside when a failure occurs. It informs the shape information, interface information, shape status information and shape error information from the network management manager server and the network management manager server which receive the shape information and shape error information and store them in the database as network management information. To the network management manager, and to the request of the network management manager. And a network management manager client which extracts and provides the network management information of the required router system by referring to the database. The network manager is provided by defining a private MIB and providing state information for each configuration to the network management system. Can accurately identify the shape information of the managed system, and can also reduce the load on the network by immediately notifying the manager of the event occurrence history through a trap message.

Description

Network management system for managing failure and state of router system and method thereof {Network management system for managing of state and problem in router system and method

The present invention relates to a network management system, and more particularly, to a network management system and method for managing a failure and state of a router system using a simple network management protocol (SNMP) of a router.

In general, an IP network performs a network management function using a standard protocol such as SNMP. This is a standard standard for network management between a network management agent system for network management and a network management agent of a router system, which is a network management target system. Standard Management Information Base (MIB) for H / W configuration management of router system includes entity MIB defined by Internet Engineering Task Force (IETF). The entity MIB provides information on the H / W shape being operated in the router system, and the information provided here includes information on the occurrence of the fault on the hernia / mounting of the H / W shape and the operation state of the H / W shape. Status information indicating whether it is in an operating state or an abnormal operating state is not known. In the entity MIB, a predetermined trap object (entityMIBTrap) is defined to notify the network management manager when the H / W shape is changed. However, this is an object for notifying when a shape for system operation is changed, and does not provide fault and state information of the shape.

In addition, a trap object is defined that notifies when a network interface port is up or down, but a MIB that provides information about the mounting and mounting of a network card on which an actual port is mounted is not defined. .

Meanwhile, the network management manager performs configuration management, fault management, performance management, account management, and security management functions for the network management target system, and standard MIB defined between the network management manager system and the network management agent system to perform these functions. Perform network management using. However, as described above, standard MIBs for shape and performance management of conventional router systems are defined, but standard MIBs for fault and state management are very limited.

Therefore, when implementing a network management function using conventional standard MIB information, the network management manager system periodically matches the configuration information of the router system stored in the network management manager server with the actual configuration information of the router system. Management information should be retrieved. In this case, there is a problem that the network management manager system may cause a load on the network with periodic traffic, and the network management agent of the router system has to allocate system resources to process a lot of MIB information.

An object of the present invention is to provide a network management system and method for effectively managing failure and state management of a router system by defining a MIB required for failure and state management of a router system.

Another object of the present invention is to provide a recording medium recorded with a program code that can be implemented by a computer on the failure and state management method of the router system.

In order to achieve the above object, the network management system according to the present invention collects the configuration information of the router system to generate the entity MIB, and collects the interface information to generate the interface MIB, the state information by shape and the failure occurrence information by shape Collect and create a private MIB and store it, and communicate with a network management agent or a network management agent that provides the required information by referring to the entity MIB, the interface MIB, and the private MIB according to an external request, or notifies the outside when a failure occurs. Configuration information, interface information, and shape information from a network management manager server and a network management manager server that receive configuration information, interface information, shape status information, and shape error information, and store and manage them in a database as network management information. After receiving the fault information by configuration, it is provided to the network management manager. It is preferable to include a network management manager client which extracts and provides network management information of a requested router system by referring to a database according to a request of the network management manager.

In order to achieve the above object, a network management manager system including a network management manager client and a network management manager server in an IP network and a network management agent implemented in a router system that is a network management target communicate with each other. In the method according to the present invention for performing status and fault management, the network management manager system is network-connected with the network management agent (a), and the network management manager server transmits the shape information and the state-specific state information of the router system to the network management agent. (B) storing and receiving the received shape information and the shape-specific state information in a database in a sequential order, according to whether the network management manager server is in its initial operation, the interface of the router system to the network management agent. Received by requesting information and receiving the interface information In the step (c) of storing in the existing database, when the network management agent is informed of the change of the shape of the router system or the change of the state by shape, the network management manager server requests the shape information and the state information by the shape from the network management agent again and sends the data. (D) updating the base and the network management manager server preferably includes (e) storing the notified failure information in a database when a failure of the router system is reported from the network management agent. .

Hereinafter, a network management system for managing a failure and state of a router system and a method thereof according to the present invention will be described with reference to the accompanying drawings.

1A to 1G illustrate an embodiment of a private MIB for state and fault management of a router system according to the present invention defined for shape and fault management of a router. Specifically, for convenience of description, the MIB shown in FIGS. 1A to 1G defines a private MIB for failure and state management for a tera router and may be similarly applied to other routers. 1A to 1F show state MIBs by shapes constituting the router system, and FIG. 1G shows trap MIBs indicating failure occurrence events by shapes.

In general, a terra router consists of routing processor redundancy, switch redundancy, line card (Slot), network clock redundancy, power triple, and fan redundancy. The MIBs defining the state management are the same as in Figs. 1A to 1F. That is, FIG. 1A is mounted for a routing processor, FIG. 1B is for a switch, FIG. 1C is for a line card, FIG. 1D is for a manipulator, FIG. 1E is for a power module, and FIG. 1F is for a fan module. And a MIB table defining operation state management. In the table shown in FIGS. 1A to 1F, the demounting information (xxFilledState) for each shape indicates whether the corresponding shape is in a filled state or an empty state, and the operating state information (xxOperState) indicates the normal shape of the corresponding shape. Normal, abnormal. The operation mode information xxOperMode indicates the activation or standby operation mode of the corresponding shape. Where xx represents a name for each shape. For example, rp represents a routing processor, a switch represents a switch, a slot represents a line card, nc represents a network, a power represents a power module, and a fan represents a fan module. The network management agent provides shape-specific state information configuring the router system with reference to the MIB tables shown in FIGS. 1A to 1F when the state-specific state information is requested from the network management system.

Meanwhile, the trap MIB illustrated in FIG. 1G defines an object for notifying a network management manager system of failures such as mounting or hernia in each shape in operation. That is, the network management agent collects and stores information about the event of mounting hernia for each shape of the router system in operation and notifies the network management manager system.

FIG. 2 is a diagram illustrating a network management system according to an embodiment of the present invention for managing status and failure of a router system in a tera router. The network management manager client 100, the network management manager server 200, and an SNMP network management agent 300 are illustrated in FIG. It is configured to include.

Referring to FIG. 2, the network management manager client 100 is connected to the network management manager server 200 to provide a GUI (Graphic User Interface) function, and the network management manager server 200 controls and manages the network management function. do. The network management agent 300 is implemented in a managed system, that is, a terra router system. In this case, the network management manager server 200 and the network management manager client 100 use the TCP / IP communication 170 and the SNMP protocol 270 between the network management manager server 200 and the network management agent 300. Communicate with each other.

Meanwhile, the network management manager client 100 may include a network map 110 representing a network configuration diagram, routing information 120 for viewing network management information on a routing protocol, and a MIB for providing MIB information implemented in a managed system. Browser 130, interface monitoring 140 for providing network interface information, event management 150 for providing event occurrence information, and profile manager 160 for user information management.

In addition, the network management manager server 200 is a web server 210 for providing a web-based network management function, router management service 220 for controlling and performing configuration management, performance management, fault management, security management functions, network Database (DB, 230) for storing network management information collected from the management agent 300, management utility 240 for providing a function to remotely access the network management agent 300 or to provide MIB information, network management An SNMP application 250 that collects and monitors traffic and fault information from an agent function, and an SNMP stack 260 that implements an SNMP protocol function are included.

In addition, the network management agent 300 is a function that operates in a routing processor (RP) of the management target system, that is, the terra router system GR160, the system operation management unit function 320, the routing protocol function 330, and the network protocol. The MIB information is processed in conjunction with the function 340. The configuration of the SNMP network management agent 300 includes an SNMP CLI processing function 312 for processing an operator command for an SNMP protocol received from an operator terminal 400, an SNMP protocol transmission and reception function by communicating with the network management manager server 200, and SNMP processing function 314 to perform encoding / decoding functions, MIB 316 to manage management information provided by SNMP network management agent 300, system operation management function 320, routing protocol function 330, network It is composed of a system matching function 318 to perform the read or write MIB information at the request of the network management manager server 200 in conjunction with the protocol function 340.

That is, in the MIB 316 of the SNMP network management agent 300 shown in FIG. 2, as shown in FIGS. 1A to 1G, the state-specific state MIBs and trap MIBs required for shape management and failure management of the router system are provided. The network management agent 300 refers to the MIB 316, and when a failure and a state change occur in each component constituting the router system in the router system, or by the configuration from the network management manager server 200. When requested to provide status information, it can be notified immediately. That is, the network management manager server 200 may be provided with information on a failure occurrence and state change of the router system through the network management agent 300 without periodically accessing the network management agent 300.

FIG. 3 is a flowchart illustrating an embodiment of a failure and state management method of a router system performed in the network management system shown in FIG. 2.

2 and 3, first, the network manager requests network management system manager authentication to the network management manager server 200 through the network management manager client 100 for failure and state management of the router system ( In step 400, if authentication is performed (step 410), the network management manager server 200 is accessed through the web. When the network management manager client 100 is connected to the network management manager server 200, the network management manager client 100 requests the connection of the network management agent 300 of the management target system, that is, the router system (operation 420). ). When a connection of the network management agent 300 is requested from the network management manager client 100, the network management manager server 200 establishes a connection with the network management agent 300 (operation 412). At this time, there are two ways in which the network management manager server 200 is connected to the network management agent 300. In the first method, the network management manager client 100 inputs the IP address of the network management agent 300 (step 422), and the network management manager server 200 connects with the network management agent 300 of the corresponding IP. (Step 424). The second method is a method in which the network management manager server 200 receives a cold start trap message notifying initialization from the network management agent 300 (step 426). In the latter case, the network management manager server 200 transmits a message indicating that the agent system has been initialized to the network management manager client 100 (step 428).

When the network management manager server 200 and the network management agent 300 are connected, the network management manager server 200 may request a predetermined SNMP command (for example, shape information of a terra router system to be managed by the network management agent 300). Request the shape information of the terra router system by transmitting a command, GetRequest or GetNextRequest (step 430). When the configuration information is requested from the network management manager server 200, the network management agent 300 collects entity MIB information to provide the configuration information of the terra router system and sends the configuration information collection result to the network management manager server 200. Transmit (step 440).

When the network management manager server 200 receives the configuration information from the network management agent 300, the network management manager server 200 stores the configuration information in the DB 230 and transmits a message indicating that the configuration information has been changed to the network management manager client 100 (operation 450). ). At this time, the configuration information is provided with configuration information on the board, module, slot to operate the terra router system, and whether or not the normal operation of the system is not provided.

Meanwhile, in order for the network management manager server 200 to obtain the state information for each shape of the terra router, the network management manager server 200 requests a state information for each shape to the network management agent 300 (GetRequest or GetNextRequest command). ) (Step 460). When the state-specific state information is requested from the network management manager server 200, the network management agent 300 retrieves the state-specific MIB information defined in FIGS. 1A to 1F and provides the state-specific state information to the network management manager server. (Step 470). The network management manager server 200 receives the state information for each shape from the network management agent 300, stores the corresponding information in the DB 230, and notifies the network management manager client 100 that the state information for each shape has been changed. (Step 480).

In this case, the network management manager server 200 checks whether the initial operation is performed (operation 490), and requests the interface information from the network management agent 300 (operation 510) if it is the initial operation. When interface information is requested from the network management manager server 200, the network management agent 300 collects the requested interface information as an interface MIB and transmits the requested interface information to the network management manager server 200 (operation 520). The network management manager server 200 stores the interface information transmitted from the network management agent 300 in the DB 230 and notifies the network management manager client 100 that the interface information has been changed (operation 530). If so far, the network management manager client 100 retrieves the shape information stored in the DB 230 and configures and mounts the mounting diagram of the tera router in the GUI window (step 560).

On the other hand, the network management agent 300 notifies the network management manager server 200 a message (entConfigChang Trap) indicating that the shape has been changed with reference to the entity MIB when the system operation shape is changed during the operation of the tera router (step 550). . Then, in order to reconfigure the shape of the terra router, the network management manager server 200 proceeds to step 430 and proceeds to steps 430 to 490 and 510 to 530 again to form information from the network management agent 300. Read again (step 540). At this time, since the network management manager server 200 is not an initial operation in operation 490, it is checked whether the state of the line card is changed (operation 500). If the state of the line card is changed, the process proceeds to steps 510 to 540 again. If the state of the line card is not changed, the process does not need to proceed to the steps 510 to 540 again, and the network management agent 300 or the network management manager client Wait for a message from 100.

On the other hand, if the terra router is restarted without changing the shape during operation, the network management agent 300 sends a message (warmStart Trap) informing the status change of the terra router system to the network management manager server 200 (step 580). ). Then, the network management manager server 200 proceeds to step 460 and proceeds from step 460 to step 530 again to read the state information from the network management agent 300 again to retrieve the state information of the terra router. (Step 570). At this time, when the state of the line card is changed (step 500), as described above, the network management manager server 200 requests and processes interface information from the network management agent 300 again.

In addition, if a specific board or interface link fails during operation of the terra router, or if the failure history is restored, the network management agent 300 refers to the trap MIB as shown in FIG. 1G among the private MIBs and manages the network management manager. The server 200 notifies the failure occurrence message (step 600). Then, the network management manager server 200 stores the failure occurrence information provided from the network management agent 300 in the DB 230 to manage the history of the failure history, and notify the network management manager client 100 of the occurrence of failure. (Step 590). The network management manager client 100 outputs through the GUI window reflecting the state of each shape and the failure details of the terra router system by referring to the failure information stored in the DB 230 (operation 610).

On the other hand, if the network manager wants to change the information of the terra router system, the network management manager client 100 sends a system information change message to the network management manager server 200 (step 620). After operation 620, the network management manager server 200 sends a command SetRequest to the network management agent 300 to request the requested information change from the network management manager client 100 (operation 630). After operation 630, the network management agent 300 changes information of the terra router according to a request of the network management manager server 200, and sends the result to the network management manager server 200 (operation 640). The network management manager server 200 stores the information change result received from the network management agent 300 in the DB 230 and notifies the network management manager client 100 that the information change is completed (step 650).

As described above, the network management agent 300 may define the MIB for the configuration and failure management of the router, and immediately notify the network management manager server 200 when the configuration change and failure of the router. In addition, the network manager server 200 stores and manages the MIB information provided from the network management agent 300 in the DB 230 so that the network manager may request information for network management through the network management manager client 100. Each time, the network management manager server 200 may reduce the traffic of the network by providing the information stored in the DB 230 without requesting the corresponding information from the network management agent 300.

The invention can also be embodied as computer readable code on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, which are also implemented in the form of a carrier wave (for example, transmission over the Internet). It also includes. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The best embodiments have been disclosed in the drawings and specification above. Although specific terms have been used herein, they are used only for the purpose of describing the present invention and are not used to limit the scope of the present invention as defined in the meaning or claims. Therefore, those skilled in the art will understand that various modifications and equivalent other embodiments are possible from this. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

According to the network management system and the method for managing the failure and state of the router system according to the present invention, a private that can provide an event for the failure and state change of the H / W shape during the initialization and operation of the router system to the manager By defining the MIB and providing the information, the network manager can accurately grasp the shape information of the managed system, and can also reduce the load on the network by immediately notifying the manager of the event occurrence through the trap message.

1A to 1G illustrate an embodiment of a private MIB for state and fault management of a router system according to the present invention defined for shape and fault management of a router.

2 is a diagram illustrating a network management system for managing status and failure of a router system in a tera router.

FIG. 3 is a flowchart illustrating an embodiment of a failure and state management method of a router system performed in the network management system shown in FIG. 2.

Claims (22)

In the network management system for a router system, Collects the configuration information of the router system to generate an actual MIB, collects interface information to generate an interface MIB, collects state information by shape and failure occurrence information by shape to generate and store a private MIB, and requests external A network management agent providing information required by referring to the entity MIB, the interface MIB, and the private MIB, or notifying the outside in case of a failure; A network management manager server configured to communicate with the network management agent and receive the shape information, the interface information, the shape-specific state information, and the shape-specific failure information and store the information as network management information in a database; And The configuration information, the interface information, the shape-specific state information and the shape-specific failure information are notified from the network management manager server and provided to the network management manager, and requested by referring to the database according to the request of the network management manager. Network management manager client for extracting and providing network management information of the router system, characterized in that it comprises a network management manager client. The method of claim 1, The network management manager server and the network management manager client communicates through TCP / IP, and the network management manager server and the network management agent communicate through SNMP protocol. Network management system. The method of claim 1, wherein the private MIB is Mounting / mounting information indicating information on mounting / mounting states of respective shapes of the router system; Operating state information indicating whether each shape performs a normal operation or an abnormal operation; And State MIB for each shape including operation mode information indicating the activation or standby operation mode of each shape; And a trap MIB indicating a failure occurrence state for each shape. The method according to claim 3, wherein the state MIB for each shape is Network management system for failure and state management of a router system, characterized in that the access by the network management manager server read-only (read-only). In the IP network, the network management manager system including the network management manager client and the network management manager server and the network management agent implemented in the router system targeted for network management perform state and fault management of the managed router system. In the way, (a) connecting the network management manager system to the network management agent; (b) the network management manager server sequentially requesting and receiving shape information and shape-specific state information of the router system from the network management agent, and storing the received shape information and shape-specific state information in a database. ; (c) the network management manager server requesting and receiving interface information of the router system from the network management agent according to whether the network management manager is in its initial operation, and storing the received interface information in the database; (d) When the network management agent is notified of the shape change or the state change of the router system from the network management agent, the network management manager requests the shape management information and the state information of each shape again to update the database. Making; And (e) when the network management agent is notified of the failure of the router system according to the shape of the router system, storing the notified failure information in the database; and How to manage faults. The method of claim 5, And the network management manager server provides the network management manager client with the information provided from the network management agent in each step. The method of claim 5, The network management manager client configures an implementation diagram of the router system with reference to the shape information and the state information for each shape stored in the database and provides the network management manager to the network management manager. The method of claim 5, The network management manager client extracts the shape information of the router system, the state information for each shape, and the failure occurrence information for each shape by referring to the database, and provides the network management manager to the network management manager. . The method of claim 8, The network management manager client provides the network management manager with shape information, shape-specific state information, and shape-specific failure occurrence information of the router system through a graphical user interface (GUI). Status and fault management methods. The method of claim 5, (f) when the network management manager server requests a change of information of the router system from the network management manager client, requesting the network management agent to change the requested information; And (g) if the information change result of the router system is provided from the network management agent, the network management manager server further comprising storing the information change result in the database and notifying the network management manager client. How to manage the status and failure of a router system. The method of claim 5, wherein step (a) (a1) the network management manager server granting authentication according to a request of the network management manager client and accessing the network management manager client; And (a2) The network management manager server includes a step of establishing a connection with the network management agent according to a request of the network management manager client. The method of claim 11, wherein in step (a2) (a21) the network management manager server receiving an IP address of the network management agent from the network management manager client; And (a22) The network management manager server status and failure management method of the router system, characterized in that the IP connection with the network management agent via the IP address provided from the network management manager client. The method of claim 11, wherein in step (a2) The network management manager server receives the trap message indicating the initialization from the network management agent and establishes a connection with the network management agent. The method of claim 5, wherein in step (b) When the configuration information is requested from the network management manager server, the network management agent collects and provides physical and logical information about shapes configuring the router system as an entity MIB, and manages the status and failure of the router system. Way.  The method of claim 5, wherein in step (b) When the state management information of each shape is requested from the network management manager server, the network management agent collects and provides information necessary to manage the operation state of each shape of the router system as the state-specific MIB. How to manage faults. The method according to claim 15, wherein the shape-specific state MIB is Mounting / mounting information indicating information on mounting / mounting states of respective shapes of the router system; Operating state information indicating whether each shape performs a normal operation or an abnormal operation; And And operating mode information indicating an activation or standby operation mode of each shape. The method of claim 5, wherein step (c) (c1) the network management manager server requesting interface information from the network management agent if the initial operation thereof is performed; (c2) if the network management agent requests interface information from the network management manager server, collecting link information connected to a network as an interface MIB and providing the network management manager server to the network management manager server; And and (c3) the network management manager server storing the interface information transmitted from the network management agent in the database. The method of claim 17, (c4) if it is not an initial operation of the network management manager server, determining whether a state change of a line card constituting the router system has occurred; (c5) if the state change of the line card has not occurred in step (c4), the network management manager server waiting for a message from the network management agent or the network management manager client; (c6) if the state change of the line card occurs in step (c4), the network management manager server requesting interface information from the network management agent again; (c7) The network management manager server further comprises updating the database with interface information provided from the network management agent. The method of claim 5, wherein step (d) (d1) if the network management manager server receives a message indicating that the shape of the router system has been changed from the network management agent, requesting the network management agent again for shape information and shape-specific state information of the router system; (d2) updating the database with shape information and shape-specific state information provided from the network management agent; (d3) If the state change of the line card has not occurred by determining whether a state change of the line card constituting the router system has occurred, the network management manager server receives a message from the network management agent or the network management manager client. Waiting; (d4) if the state change of the line card occurs in step (d3), the network management manager server requesting the interface information from the network management agent again; (d5) the network management agent, if interface information is requested from the network management manager server, collecting link information connected to a network as an interface MIB and providing the network management manager server; And (d6) The network management manager server status and failure management method of the router system comprising the step of updating the database with the interface information transmitted from the network management agent. The method of claim 5, wherein step (d) (d7) when the network management manager server receives a message informing the state change of the router system from the network management agent, requesting the shape management state information from the network management agent again; (d8) updating the database with shape information and shape-specific state information provided from the network management agent; (d9) If it is determined that the state change of the line card constituting the router system has occurred, and the state change of the line card has not occurred, the network management manager server receives a message from the network management agent or the network management manager client. Waiting; (d10) if the state change of the line card occurs in step (d9), the network management manager server requesting the interface information from the network management agent again; (d11) the network management agent, when interface information is requested from the network management manager server, collecting link information connected to a network as an interface MIB and providing the network management manager server to the network management manager server; And (d12) The network management manager server comprises the step of updating the database with the interface information transmitted from the network management agent, the status of the router system and failure management method. The method of claim 5, wherein step (e) (e1) the network management agent collecting and storing failure occurrence information as a trap MIB when a failure by shape or an interface link occurs during operation of the router system, and notifying the network management manager server; (e2) managing, by the network management manager server, a failure occurrence history by storing failure information notified from the network management agent in the database; And (e3) The network management manager server includes a step of notifying the network management manager client of the failure information notified from the network management agent. A recording medium having recorded thereon a program code executable on a computer, the status of the router system according to any one of claims 5 to 21 and a method for managing a failure.