KR100798754B1 - Management Method for Real time Monitoring in NMS - Google Patents

Abstract

The present invention discloses a performance management method in a network management system (NMS) that can be monitored in real time using the command line interface (CLI).

The method of the present invention includes a first step of collecting and updating monitoring information of each management object (Port MO) of the MPLS layer through the command line interface; Receiving a monitoring request from a user, the second step of extracting and transmitting only predetermined information from the MPLS_Server to the MPLS_Network; The MPLS_Network finds the management object of the router that matches the predetermined information received from the MPLS_Server and matches the interface ID that is requested to be monitored among the interfaces of the management object (MO) of the corresponding router. A third step of reading the throughput information of the place; And a fourth step of transmitting performance information read by the MPLS network to the user through the MPLS server.

NMS, Real Time Monitoring, Performance Management, Monitoring Object, MPLS

Description

Management Method for Real time Monitoring in NMS

1 is a diagram illustrating a connection relationship between a performance management function module in an MPLS layer according to the present invention;
2 is a diagram illustrating in detail a performance management operation procedure according to the present invention;
3 is a diagram illustrating an association between a monitoring dialog operating in a GUI for performance management and a monitoring object of a core according to the present invention;
4 is a class diagram of a performance management part according to the present invention;

delete

delete

delete

5 is a sequence diagram showing a performance management procedure according to the present invention.

The present invention relates to a network management method, and more particularly, to a performance management method in a network management system (NMS) that can be monitored in real time using a command line interface (CLI).
In general, in order to efficiently manage the network, it is necessary to monitor in real time whether there is an error in the network, notify the administrator when a failure occurs, and recover the failure.
Multiprotocol Label Switch (MPLS) uses a second layer switching technology such as ATM or Frame Relay to speed up packet forwarding, and a third layer that incorporates a third layer routing function to provide network scalability. It is a kind of switching technology. In MPLS, a label swapping method is used to transmit a packet based on a short, fixed length label. In general, an MPLS network is composed of an edge router (LER: Label Edge Router) that is in charge of interworking with a host or another network, and a Label Switch Router (LSR), which performs label swapping at a core. . When an ingress edge router (LER) receives an IP packet, it analyzes the destination IP of the packet, determines the label switched path (LSP) to which the packet will be delivered, inserts a label in the packet, and forwards the packet to the corresponding interface. Receiving a packet with a label, the core router (LSR) examines only the label and exchanges the label. For this purpose, the MPLS shim header consists of a 20-bit label, a 3-bit EXP, a 1-bit S, and an 8-bit Time To Live (TTL).
In this MPLS network, performance management module provides real-time monitoring of LSP and port throughput for continuous network monitoring.
However, various methods for providing real-time monitoring in MPLS have been proposed, but a method using a command line interface (CLI) has not been implemented yet.

The present invention has been proposed to satisfy the above needs, and an object of the present invention is to provide a performance for real-time monitoring in NMS that can monitor the performance of an MPLS network using a CLI (Command Line Interface). It is to provide a management method.

In order to achieve the above object, the present invention includes a first step of collecting and updating monitoring information through the command line interface of each management object (Port MO) of the MPLS layer (MPLS layer); Receiving a monitoring request from a user, the second step of extracting and transmitting only predetermined information from the MPLS_Server to the MPLS_Network; The MPLS_Network finds the management object of the router that matches the predetermined information received from the MPLS_Server and matches the interface ID that is requested to be monitored among the interfaces of the management object (MO) of the corresponding router. A third step of reading the throughput information of the place; And a fourth step of transmitting performance information read by the MPLS network to the user through the MPLS server.
Here, in the third step, the MPLS_Network passes predetermined information to the performance management handler PM_Handler, and the performance management handler PM_Handler generates the monitoring object MonObj based on the predetermined information. Making; The monitoring object MonObj registers predetermined information received from the performance management handler PM_Handler, and sends information of a requested interface to a router that matches the registered information. The router may separately register as an interface ID for monitoring the received interface and update throughput information for the corresponding interface at predetermined time intervals. The predetermined information may include a router ID and an interface to be monitored. ID.
If the management object is a port management object (Port MO), the port information is read through a command line interface (CLI) to update the port information by reading a traffic value passing through itself every predetermined time, and the LSP management object is updated. In this case, the ID of the LSP corresponding to the request for monitoring is separately registered as a variable for monitoring, so that the CLI module sets every port registered in the router and the traffic value through the LSP for which monitoring is requested every predetermined time. Read through the command (show interface account).
Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.
In order to efficiently manage the network, it is necessary to monitor in real time whether there is an error in the network, notify the administrator when a failure occurs and recover the failure. The MPLS network performance management module provides real-time monitoring of the throughput of LSPs and ports for continuous network monitoring.

1 is a connection diagram of a performance management function module in the MPLS layer (MPLS layer) according to the present invention, the physical layer (Physical Layer), MPLS layer (MPLS Layer), VPN / VPLS layer (VPN / VPLS Layer) and moving The connection of the GUI (Mobile GUI) is shown. The MPLS layer includes the MPLS server, MPLS network, PM handler, supervisor, MPLS LSP, MPLS LSR, and MPLS interface.
FIG. 1 shows some of the MPLS classes in the MPLS layer except for a few. Among them, a Performance Management (PM) Handler and a Monitoring Object (MonObj: Monitoring Object) It is the core module of the performance management function. In this case, to avoid confusion, the name of a class is indicated by using an under-bar (for example, MPLS_Server, MPLS_Network, PM_Handler, etc.).
When the user requests a monitoring through the mobile GUI, the request is received from the MPLS server, and only the necessary information is extracted and transmitted to the MPLS network. The necessary information here is an ID of a node to which the selected interface LSP / Port belongs, that is, an MPLS_LSR (or MPLS_LER), and an ID of the selected interface.
If the selected interface is a port, it is a port ID. If it is an LSP, it is a port ID to which the LSP belongs and the ID of the corresponding LSP.
The following Table 1 shows the data format of XML format that is transferred from MPG to MPLS_Server and through this, you can see the information that MPLS_Network obtains.
<? xml version = "1.0"?><Function><FunctionName> RequestPMDataOnPort </ FunctionName><PortNumber> 4500 </ PortNumber><NodeID> 7204_G </ NodeID><PortList><PortAddress> 10.0.0.1 </ PortAddress><PortAddress> 10.0.0.2 </ PortAddress><PortAddress> 10.0.0.3 </ PortAddress></PortList></Function>

delete

delete

delete

delete

delete

The MPLS_Network finds a management object (MO) of the MPLS_LSR (or MPLS_LER) that matches the ID of the MPLS_LSR (or MPLS_LER) received from the MPLS_Server. Then, the performance information of the interface of the LSR (or LER) management object (MO) that matches the interface ID requested for monitoring is read.
2 shows an operation procedure of such a performance management function.

Referring to FIG. 2, the reason why the performance management function module is linked to the MPLS layer includes an LSP, which is a managed object (MO) of the MPLS layer, for monitoring. This is because the port uses information that each has.
Each port MO of the MPLS layer updates port information by reading a traffic value through the command line interface (CLI) every second. This is true even when there is no request for monitoring, for all MPLS_LSR (LER) to monitor the network continuously such as measuring the change in traffic.
Since there can be dozens or hundreds of LSPs, it is not efficient to read information even when there is no request. Therefore, the ID of the LSP is used as a variable for monitoring only when there is a request for monitoring. Register. The CLI module of the core reads every port registered in the router and the traffic value through the LSP requested for monitoring through the "show interface account" command once a second. come.
Looking at the operation procedure of Figure 2 in detail as follows. When a user's request is sent to the MPLS_Server in the GUI as shown in Table 1, the MPLS_Server has a frame ID, which will be described later, and a router ID (LSR or LER) of the requested interface. ID), the interface ID, and the like are transmitted to the MPLS_Network, and the MPLS_Network passes the same information as that received to the PM_Handler to the performance management handler (PM 1). time).
The performance management handler PM_Handler creates one monitoring object MonObj based on the information (2 in FIG. 2). In other words, one monitor object (MonObj) is created for each request. Monitor object (MonObj) registers frame ID (frame ID), router ID (LSR or LER ID) and interface ID (port ID and LSP ID in case of LSP) received from PM_Handler. (3 in FIG. 2), information of the requested interface is sent to the router (LSR or LER) matching the registered information.
MPLS_LSR (LER) separately registers the received interface as an interface ID for monitoring and updates the performance information about them once per second (Fig. 4, FIG. 5).

delete

delete

delete

3 is a diagram illustrating a correlation between a monitoring dialog of a monitoring manager (Monitoring_Manager) operating in a GUI for performance management and a monitoring object (Monitoring_Object) of a performance management handler (PM_Handler) of a core The figure which shows. Whenever there is a monitoring request from the user, the monitoring GUI of Monitoring GUI (Monitoring_Manager) creates one dialog for monitoring, and the core performance management handler (PM_Handler) Creates one monitor object (MonObj). Therefore, the monitoring dialog having the same frame ID and the monitoring object MonObj have a 1: 1 relationship.
As an example of designing and implementing a performance management core function, the performance management handler PM_Handler is operated from a DoumiMan class and is called by an MPLS_Network. When the MPLS_Server receives the request information in XML format from the GUI, it is transferred to the MPLS_Network, and the MPLS_Network transfers the information to the performance management handler PM_Handler.
4 is a class diagram of a performance management part according to the present invention, and FIG. 5 shows a sequence diagram according to the present invention.
Referring to the class diagram of FIG. 4, it can be seen that the performance management handler PM_Handler is associated with a part of classes of the MPLS layer. The performance management handler (PM_Handler) is implemented to allow socket communication by inheriting the helper man socket. Receives monitoring request from MPLS_Server and after that, once every second, XML message to update graph in Monitoring Dialog of Mobile GUI is performed. It is directly sent by the management handler (PM_Handler).
5 is a sequence diagram illustrating the interaction of cores when one request occurs in accordance with the present invention. This shows that the function performed by the core after a monitoring request comes from the mobile GUI and then the performance management handler (PMHandler) directly communicates with the mobile GUI to transmit data. You can check.

delete

delete

delete

As described above, in order to efficiently manage the network, the present invention monitors in real time whether an error occurs in the network, and notifies the administrator when a failure occurs so that the failure can be quickly recovered. To this end, the performance management module of the MPLS network according to the present invention may provide a real-time monitoring function for the throughput of the LSP and the port for continuous network monitoring.

Claims (5)

A first step of collecting and updating monitoring information through each command object interface of each management object Port MO of the MPLS layer; When receiving a monitoring request from the user, MPS server (MPLS_Server) extracts and forwards the router ID and interface ID to be monitored by the MPLS network (MPLS_Network); The MPLS_Network requests the monitoring of the router management object matching the router ID and the interface ID received from the MPLS_Server to the monitoring object interface of the corresponding management object (MO) of the corresponding router. A third step of reading throughput information corresponding to the received interface ID; And And a fourth step of transmitting performance information read by the MPLS_Network to the user through the MPLS_Server. The method of claim 1, wherein the third step, The MPLS_Network passes predetermined information to a performance management handler (PM_Handler), and the performance management handler (PM_Handler) generates a monitoring object (MonObj) based on a router ID and an interface ID to be monitored; The monitoring object MonObj registers the router ID and interface ID to be monitored received from the performance management handler PM_Handler and sends information of the requested interface to the router that matches the registered information; The router separately registers as an interface ID for monitoring the received interface and updates the performance information for the corresponding interface every predetermined time. Performance management method. delete The method according to claim 1 or 2, wherein the management object In the case of a port management object (Port MO), the port information is updated by reading a traffic value passing through itself at a predetermined time through the command line interface (CLI), If it is an LSP management object, the ID of the LSP is registered separately as a variable for monitoring only when a request for monitoring is made, so that all ports registered by the CLI module in the router and traffic values through the LSP for which monitoring is requested are prescribed. Performance management method for real-time monitoring in the NMS, characterized in that for reading through a predetermined command (show interface account) command every time. The method of claim 1 or 2, wherein the user and the MPLS server (MPLS_Server) delivers data in an XML format.

Images