KR20070001525A - Management method for real time monitoring in nms - Google Patents

Management method for real time monitoring in nms Download PDF

Info

Publication number
KR20070001525A
KR20070001525A KR1020050057075A KR20050057075A KR20070001525A KR 20070001525 A KR20070001525 A KR 20070001525A KR 1020050057075 A KR1020050057075 A KR 1020050057075A KR 20050057075 A KR20050057075 A KR 20050057075A KR 20070001525 A KR20070001525 A KR 20070001525A
Authority
KR
South Korea
Prior art keywords
mpls
monitoring
network
information
interface
Prior art date
Application number
KR1020050057075A
Other languages
Korean (ko)
Other versions
KR100798754B1 (en
Inventor
김영탁
신해준
김민지
Original Assignee
영남대학교 산학협력단
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 영남대학교 산학협력단 filed Critical 영남대학교 산학협력단
Priority to KR1020050057075A priority Critical patent/KR100798754B1/en
Publication of KR20070001525A publication Critical patent/KR20070001525A/en
Application granted granted Critical
Publication of KR100798754B1 publication Critical patent/KR100798754B1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0266—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0695—Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0888—Throughput
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

A performance management method for real-time monitoring in an NMS(Network Monitoring System) is provided to enable the performance management module of an MPLS network to supply a real-time monitoring function for the throughput of an LSP(Label Switched Path) and a port, thereby monitoring whether a problem occurs in a network in real time and notifying a manager of generation of a failure when the failure occurs, and restore it. An MPLS_server transmits frame ID(Identification), LSR(LER) ID(Label Switch Router(Label Edge Router) Identification), and requested interface ID to an MPLS_network if user's request is transmitted to an MPLS_server(Multi Protocol Label Switching_server). The MPLS_network transmits the same information as information, which the MPLS_network itself receives, to a PM_handler(Performance Monitoring_handler). The PM_handler generates one MonObj(Monitoring Object) on the basis of the information. The MonObj registers the frame ID, the LSR(LER) ID, and the interface ID received from the PM_handler in itself and transmits information of the requested interface to the LSR(LER) which coincides with the registered information. The MPLS_ LSR(LER) separately registers the received interface as interface ID for monitoring and updates throughput information of the interface ID every second.

Description

엔엠에스에서의 실시간 모니터링을 위한 성능관리 방법{Management Method for Real time Monitoring in NMS}Management Method for Real time Monitoring in NMS

도1은 MPLS layer에서 성능관리 기능의 모듈이 어떠한 방식으로 연결이 되어있는지를 보여준다. 1 shows how the modules of the performance management function are connected in the MPLS layer.

도2의 동작절차를 세부적으로 나타낸다.The operation procedure of Fig. 2 is shown in detail.

도3은 성능관리를 위한 GUI에서 동작하는 Monitoring_Manager의 Monitoring Dialog와 core의 PM_Handler의 Monitoring_Object의 연관관계를 나타낸 그림이다. 3 is a diagram showing the relationship between the Monitoring Dialog of Monitoring_Manager operating in the GUI for performance management and the Monitoring_Object of PM_Handler of the core.

도4는 성능관리 부분의 class diagram4 is a class diagram of a performance management part.

도5는 sequence diagram5 is a sequence diagram

네트워크를 효율적으로 관리하기 위해서는 네트워크에 이상이 발생하는지 실시간으로 감시하여, 장애가 발생하였을 경우 이를 관리자에게 통보하고 장애를 복구하여야 한다. MPLS 망의 성능관리 모듈은 이처럼 지속적인 망의 감시를 위하여 LSP와 Port의 throughput에 대한 실시간 monitoring 기능을 제공한다.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 LSP and port throughput for continuous network monitoring.

현재 이러한 방법에는 여러 가지 방법이 있지만, 본 발명에서는 CLI(Command Line Interface)를 이용, Performance Monitoring 방안을 제안한다.  At present, there are various methods for such a method, but the present invention proposes a performance monitoring method using a command line interface (CLI).

네트워크를 효율적으로 관리하기 위해서는 네트워크에 이상이 발생하는지 실시간으로 감시하여, 장애가 발생하였을 경우 이를 관리자에게 통보하고 장애를 복구하여야 한다. MPLS 망의 성능관리 모듈은 이처럼 지속적인 망의 감시를 위하여 LSP와 Port의 throughput에 대한 실시간 monitoring 기능을 제공한다. 현재 이러한 방법에는 여러 가지 방법이 있지만, 본 발명에서는 CLI(Command Line Interface)를 이용, Performance Monitoring 방안을 제안한다. 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 LSP and port throughput for continuous network monitoring. At present, there are various methods for such a method, but the present invention proposes a performance monitoring method using a command line interface (CLI).

도1은 MPLS layer에서 성능관리 기능의 모듈이 어떠한 방식으로 연결이 되어있는지를 보여준다. 1 shows how the modules of the performance management function are connected in the MPLS layer.

도1은 MPLS layer 내부에 있는 MPLS class들은 일부를 제외하고 표시하였으며, 이 중 PM(Performance Management) Handler 와MonObj(Monitoring Object)가 성능관리 기능의 core 모듈이다. 여기서는 혼동을 피하기 위하여 class의 이름을 지칭할 경우 under-bar를 사용하여 표시하였다(예 MPLS_Server, MPLS_Network, PM_Handler 등). Figure 1 shows some of the MPLS classes in the MPLS layer, except for the PM (Performance Management) Handler and MonObj (Monitoring Object) are core modules of the performance management function. In order to avoid confusion, the name of the class is indicated using under-bar (eg MPLS_Server, MPLS_Network, PM_Handler, etc.).

사용자가 Mobile GUI를 통해 monitoring을 요청하면, 이 요청을 MPLS_Server 에서 수신하여 MPLS_Network로 필요한 정보만을 추출하여 전달한다. 여기서 말하는 필요한 정보란, 선택된 interface (LSP /Port)가 속한 node, 즉 MPLS_LSR(혹은 MPLS_LER)의 ID와, 선택된 interface의 ID이다. When the user requests monitoring through the Mobile GUI, this request is received from the MPLS_Server and only the necessary information is sent to the MPLS_Network. The necessary information here is the ID of the node to which the selected interface (LSP / Port) belongs, that is, the MPLS_LSR (or MPLS_LER), and the ID of the selected interface.

선택된 interface가 port일 경우는 Port ID를, LSP일 경우에는 LSP가 속해있는 Port ID와 해당 LSP의 ID가 된다. <표 1>은 GUI에서 MPLS_Server로 전달되는 XML 형식의 데이터 포맷이며, 이를 통해 MPLS_Network가 얻는 정보도 알 수 있다. 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. <Table 1> is data format of XML format that is transferred from MPG to MPLS_Server, and you can see the information that MPLS_Network gets.

<표 1> GUI에서의 monitoring 요청정보<Table 1> Monitoring request information in GUI

<?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><? 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>

MPLS_Network는 MPLS_Server로부터 전달받은 MPLS_LSR(혹은 MPLS_LER)의 ID와 일치하는 MPLS_ LSR(혹은 MPLS_LER)의 MO를 찾는다. 그런 다음 해당되는 LSR(혹은 LER) MO의 interface들 중 monitoring을 요청 받은 interface ID와 일치하는 곳의 throughput 정보를 읽어온다. 도2는 이러한 성능관리 기능의 동작 절차에 대해 나타내고 있다.MPLS_Network finds the MO of MPLS_LSR (or MPLS_LER) that matches the ID of MPLS_LSR (or MPLS_LER) received from MPLS_Server. Then, the throughput information of the interface of the corresponding LSR (or LER) MO that matches the requested interface ID is read. 2 shows an operation procedure of such a performance management function.

성능관리 기능 모듈이 MPLS layer와 연동이 되는 이유는, monitoring을 위하여 MPLS layer의 MO(Managed Object)인 LSP와 Port, 각각이 가지고 있는 정보를 이 용하기 때문이다. MPLS layer의 각 Port MO들은 매 초마다 자신을 통과하는 traffic의 값을 CLI를 통해 읽어와서 Port 정보를 갱신한다. The reason why the performance management function module is interlocked with the MPLS layer is because the LSP and port, which are MOs (managed objects) of the MPLS layer, are used for monitoring. Each Port MO of the MPLS layer updates the port information by reading the traffic value passing through it every second through the CLI.

이것은 monitoring의 요청이 없을 경우에도 마찬가지이며, 이는 모든 MPLS_LSR(LER)은 traffic의 변화를 측정하는 등의 지속적인 망의 감시를 위함이다. LSP의 경우에는 수십, 수백 개가 존재할 수 있기 때문에 요청이 없을 시에도 정보를 읽어오는 방법은 효율적이지 못하므로 monitoring에 대한 요청이 있을 때에만 해당하는 LSP의 ID를 monitoring을 위한 변수로 따로 등록한다. Core의 CLI module은 router에 등록된 모든 포트와, monitoring이 요청된 LSP를 통과하는 traffic 값을 1초에 한번씩 "show interface account" 명령을 통하여 읽어온다.This is true even if there is no request for monitoring. This is to ensure that all MPLS_LSRs (LER) are constantly monitored, such as measuring traffic changes. In the case of LSP, dozens and hundreds can exist, so it is not efficient to read information even if there is no request. Therefore, the ID of the LSP is registered separately as a variable for monitoring only when there is a request for monitoring. The CLI module of the Core reads all ports registered in the router and the traffic values through the LSP requested by monitoring once a second via the "show interface account" command.

도2의 동작절차를 세부적으로 살펴보면 다음과 같다. 사용자의 요청이 GUI에서 표 1과 같은 형식으로 MPLS_Server에 전달이 되면 MPLS_Server는 frame ID(다음 단원에서 설명), 요청된 interface의 LSR(LER) ID와 interface ID 등을 MPLS_Network로 전달하고 MPLS_Network는 PM_Handler에게 자신이 받은 것과 동일한 정보를 넘겨준다(도2에서의 1번) PM_Handler는 그 정보를 바탕으로 MonObj를 하나 생성한다(2). 즉 하나의 요청이 있을 때 마다 하나의 MonObj가 생성되는 셈이다. MonObj는 PM_Handler로부터 받은 frame ID와 LSR(LER) ID, interface ID (LSP일 경우 port ID와 LSP ID)를 자신에게 등록하고(3), 등록된 정보와 일치하는 LSR(LER)로 요청 받은 interface의 정보를 보낸다. MPLS_LSR(LER)은 전달받은 interface를 monitoring을 위한 interface ID로 별도의 등록하고 이들에 대한 throughput 정보를 1초 마다 한번씩 갱신한다(4, 5). Looking at the operation procedure of Figure 2 in detail as follows. When a user's request is sent to MPLS_Server in the GUI as shown in Table 1, MPLS_Server sends frame ID (described in the next section), LSR (LER) ID and interface ID of the requested interface to MPLS_Network, and MPLS_Network is sent to PM_Handler. Give the same information as it received (No. 1 in Fig. 2) PM_Handler creates a MonObj based on the information (2). That is, one MonObj is created for every request. MonObj registers frame ID and LSR (LER) ID and interface ID (port ID and LSP ID in case of LSP) received from PM_Handler to itself (3) and the requested interface of LSR (LER) matching the registered information. Send the information. MPLS_LSR (LER) separately registers the received interfaces as interface IDs for monitoring and updates throughput information about them once per second (4, 5).

나) GUI 기능과의 연관관계 B) Association with GUI functions

도3은 성능관리를 위한 GUI에서 동작하는 Monitoring_Manager의 Monitoring Dialog와 core의 PM_Handler의 Monitoring_Object의 연관관계를 나타낸 그림이다. 사용자로부터 한번의 monitoring 요청이 있을 때마다 mobile GUI의 Monitoring_Manager는 monitoring을 위한 Dialog를 하나씩 생성하고, core의 PM_Handler는 MonObj를 하나씩 생성한다. 따라서, 동일한 frame ID를 가지고 있는 Monitoring Dialog와 MonObj는 1:1로 정보를 주고 받은 관계인 셈이다. 3 is a diagram showing the relationship between the Monitoring Dialog of Monitoring_Manager operating in the GUI for performance management and the Monitoring_Object of PM_Handler of the core. Whenever there is a monitoring request from the user, Monitoring_Manager of mobile GUI creates one dialog for monitoring, and PM_Handler of core creates MonObj one by one. Therefore, Monitoring Dialog and MonObj having the same frame ID exchanged information 1: 1.

성능관리 core기능의 설계 및 구현의 한예로 PM_Handler는 DoumiMan class로부터 동작되며, MPLS_Network에 의해 호출된다. GUI로부터 XML 형식의 요청정보를 MPLS_Server가 받으면 그것은 MPLS_Network로 전달되고, MPLS_Network는 그 정보를 PM_Handler로 전달한다. 도4는 이러한 성능관리 부분의 class diagram이며 도5는 sequence diagram을 나타낸다. As an example of the design and implementation of the performance management core function, PM_Handler operates from the DoumiMan class and is called by MPLS_Network. When MPLS_Server receives the request information in XML format from the GUI, it is transferred to MPLS_Network, and MPLS_Network transfers the information to PM_Handler. 4 is a class diagram of this performance management part, and FIG. 5 is a sequence diagram.

도4의 class diagram을 살펴보면PM_Handler가 MPLS Layer의 class 들 중 일부분과 연계된다는 것을 알 수 있다. PM_Handler는 DoumiManSocket을 상속받아 socket 통신이 가능하도록 구현되었다. Monitoring 요청을 MPLS_Server로부터 받고 그 이후, 1초 마다 한번씩 Mobile GUI의 Monitoring Dialog에 그래프를 갱신시켜 주기 위한 XML message는 PM_Handler가 직접 보내는 형식이다. Looking at the class diagram of FIG. 4, it can be seen that PM_Handler is associated with a part of classes of the MPLS layer. PM_Handler inherits DoumiManSocket and is implemented to enable socket communication. After receiving a monitoring request from MPLS_Server, the XML message for updating the graph in the monitoring dialog of the Mobile GUI once every second is sent directly by PM_Handler.

도5는 하나의 요청이 발생하였을 때 core의 interaction을 나타낸 sequence diagram이다. 이를 살펴보면 Mobile GUI로부터 monitoring 요청이 온 다음의 core에서 수행하는 기능과, 이후 PMHandler가 직접 mobile GUI와 통신하며 데이터를 전송하는 것을 확인 할 수 있다.5 is a sequence diagram showing interaction of cores when one request occurs. If you look at it, you can check the function that core performs after monitoring request from Mobile GUI, and then PMHandler directly communicates with mobile GUI and transmits data.

본 발명에서는 네트워크를 효율적으로 관리하기 위해서는 네트워크에 이상이 발생하는지 실시간으로 감시하여, 장애가 발생하였을 경우 이를 관리자에게 통보하고 장애를 복구할시 MPLS 망의 성능관리 모듈은 이처럼 지속적인 망의 감시를 위하여 LSP와 Port의 throughput에 대한 실시간 monitoring 기능을 제공하는 효과가 있다.In the present invention, in order to efficiently manage the network to monitor in real time whether there is a problem in the network, if a failure occurs to notify the administrator and when the failure recovery performance management module of the MPLS network LSP for continuous monitoring of the network in this way It is effective to provide real-time monitoring function for throughput of and port.

Claims (1)

NMS에서의 실시간 모니터링을 위한 성능관리 방법Performance Management Method for Real-Time Monitoring in NMS
KR1020050057075A 2005-06-29 2005-06-29 Management Method for Real time Monitoring in NMS KR100798754B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020050057075A KR100798754B1 (en) 2005-06-29 2005-06-29 Management Method for Real time Monitoring in NMS

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020050057075A KR100798754B1 (en) 2005-06-29 2005-06-29 Management Method for Real time Monitoring in NMS

Publications (2)

Publication Number Publication Date
KR20070001525A true KR20070001525A (en) 2007-01-04
KR100798754B1 KR100798754B1 (en) 2008-01-29

Family

ID=37868905

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020050057075A KR100798754B1 (en) 2005-06-29 2005-06-29 Management Method for Real time Monitoring in NMS

Country Status (1)

Country Link
KR (1) KR100798754B1 (en)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100703328B1 (en) * 1999-06-12 2007-04-03 삼성전자주식회사 Method for performance management of atm connection
US7082464B2 (en) * 2001-07-06 2006-07-25 Juniper Networks, Inc. Network management system
KR100706604B1 (en) * 2004-12-03 2007-04-11 한국전자통신연구원 Auto detected fault management method for network service quality guarantee in wireless internet service

Also Published As

Publication number Publication date
KR100798754B1 (en) 2008-01-29

Similar Documents

Publication Publication Date Title
US10992543B1 (en) Automatically generating an intent-based network model of an existing computer network
US10623293B2 (en) Systems and methods for dynamic operations, administration, and management
US7869376B2 (en) Communicating an operational state of a transport service
CN112020844B (en) System, function and interface for interconnected multi-domain network fragmentation control and management
US7860016B1 (en) Method and apparatus for configuration and analysis of network routing protocols
US20170155592A1 (en) Packet Processing Method, Device and Computer Storage Medium
Atlas et al. An architecture for the interface to the routing system
WO2021047011A1 (en) Data processing method and apparatus, and computer storage medium
KR20140117993A (en) Mpls-tp network and method for link failure trace
EP2862315B1 (en) Self-configuring transport network
US20200036571A1 (en) Systems, Methods, and Devices for Networked Media Distribution
KR101990480B1 (en) Method, apparatus and system for managing terminal device in passive optical network
WO2020106449A1 (en) Fabric data plane monitoring
EP3917086B1 (en) Network topology discovery method, device, and system
CN101404594B (en) Hot backup performance test method and apparatus, communication equipment
CN111953413B (en) Optical line terminal OLT system
KR20070001525A (en) Management method for real time monitoring in nms
CA2995561A1 (en) Systems and methods for managing network health
JP2010130113A (en) System and method of network management, manager, and agent
CN100477599C (en) A network management method aiming at network device
CN108768704B (en) Configuration updating method and device
KR100535310B1 (en) Fault management method in network management system
JP2002084279A (en) System and method for managing snmp network
CN117792907A (en) Virtual local area network configuration method, device, electronic equipment and storage medium
Hares et al. Network Working Group A. Atlas Internet-Draft Juniper Networks Intended status: Informational J. Halpern Expires: October 24, 2016 Ericsson

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant
FPAY Annual fee payment

Payment date: 20130107

Year of fee payment: 6

FPAY Annual fee payment

Payment date: 20140106

Year of fee payment: 7

LAPS Lapse due to unpaid annual fee