KR20080020470A - Wbem-based fault management system and method with differentiated path protection for inter-as traffic engineering - Google Patents

Abstract

A fault management system and method using WBEM based differentiated path protection for traffic engineering in an inter-AS environment are provided to generate an indication instance if receiving a trap from a network element where an SNMP(Simple Network Management Protocol) agent is installed, classify faults, find a fault rapidly by performing a differentiated procedure according to the fault, and recover the fault via a differentiated path according to a service class. A fault management system comprises an SNMP provider(350), a fault manager(320), a CIMOM(Common Information Model Object Manager,310), and an inter-AS QoS provider(330). The SNMP provider(350) collects information from network elements as well as receive trap notifications from the network elements. The fault manager(320) classifies fault information received from the SNMP provider(350), and processes the fault information via a corresponding handler. The CIMOM(310) notifies a manager that a fault indication is received from the fault manager(320) and instructs fault recovery. The inter-AS QoS provider(330) provides a fault recovery method for solving the fault according to the fault information of the fault manager(320) and the instruction of the CIMON(310).

Description

{WBEM-based fault management system and method with Differentiated path protection for inter-AS Traffic Engineering}

1 is a diagram illustrating an indication mechanism of a conventional OpenPegasus platform;

2 is a diagram illustrating a management object format (MOF) for a conventional indication layer;

3 is a block diagram illustrating a WBEM / CIM server to which distributed failure management is applied according to the present invention;

4 illustrates a MOF class of a DTMF CIM based MPLS OAM service according to the present invention.

* Explanation of symbols for main parts of the drawings

302: network component 310: common information model object manager

320: fault manager 330: an interfacing QoS provider

350: SNMP provider 321: indication provider

322: classifier 331: method provider

332: Association provider 334: Instance provider

351: SNMP Manager 352: SNMP Trap Handler

The present invention relates to a network management technology in an autonomous manganese environment, and more particularly, to a failure management system and method using differential path protection based on web-based enterprise management for traffic engineering in an autonomous manganese environment.

In general, Web-Based Enterprise Management (WBEM) is based on the management infrastructure standard and various hardware and software management systems in enterprise environments based on the Common Information Model (CIM) of the Distributed Management Task Force (DMTF). It is a technology that provides a standardized approach. Web-based Enterprise Management (WBEM) integrates WBEM discovery and Universal Resource Identifier (URI) mapping using Common Information Model (CIM), CIM-XML, CIM Query Language, and Service Location Protocol (SLP). Include.

FIG. 1 is a diagram illustrating an indication mechanism of a conventional OpenPegasus platform. The conventional indication mechanism includes a management system 110 on the side of generating and delivering an indication and an indication of an indication. It consists of the management system 120 of the consumer side.

Indication generation and delivery management system 110 is CIM-XML protocol adapter 111 and CIM object manager 112, indication provider 113, resources 114, CIM-XML indication handler 115 The reception and consumption management system 120 is composed of a CIM listener 121, the indicator consumer manager 122, the indication consumer 123.

Referring to FIG. 1, the indication consumer 123 and the indication provider 113 should register with the CIM server 112 and the CIM listener 121, respectively. The CIM Client 102 then authenticates to the CIM Server 112 to load the Indication Provider 113. From then on, whenever an event occurs, the indication provider 113 creates an instance of an indication. CIM server 112 checks the filter to allow an instance and to determine if an indication handler 115 can be found. The indication consumer 123 receives information about an indication from the indication handler 115.

FIG. 2 illustrates a managed object format (MOF) for an indication layer. Managed Object Format (MOF) is often used to describe the type of event found. CIM_Indication 201 is an abstract class and is provided as a base class for all indication classes. The CIM_SNMPTrapindication 205 class contains all the necessary information about the trap. Indication filters may include conditions or attributes in the list of fault notifications for sorting indications. If the generated indication does not satisfy the filter, the indication is deleted without being delivered. If the indication filter does not have any questions or conditions for sorting the indication, all indications are passed to all handlers 115 authorized from the filter. The format of the question in the filter depends on the language chosen for the expression. OpenPegasus offers Web Query Language (WQL) and CIM Query Language (CQL).

Simple Network Management Protocol (SNMP) has been developed to provide an application layer protocol that facilitates the exchange of management information between network devices, common network management, and tools for multiple vendors. SNMP is based on a manager / agent model, and to achieve the goal of simple, SNMP has a limited set of command and response management commands. The notification message is called 'trap' and is used to send to the SNMP provider to identify the fault that occurred in the SNMP agent. The SNMP trap PDU (Protocol Data Unit) contains enough information to identify the fault. Traps are sent to the SNMP manager using UDP at the transport layer.

By the way, the filtering mechanism of the WBEM event notification is conventionally limited by the WQL and CQL, there is a problem that can not classify the trap internally. In addition, the MOF modeling structure provided by CIM has not been sufficiently provided as a management object format (MOF) for traffic engineering fault management and differential path protection in inter-AS networks.

The present invention has been proposed to solve the above problems, and an object of the present invention is to guarantee a quality of service (QoS) in the inter-AS environment Diffserv-over-MPLS Traffic Engineering It is to provide a system and method for failure management using differentiated path protection based on web-based enterprise management (WBEM) for distributed failure management and event notification.

In order to achieve the above object, the system of the present invention includes a simple network management protocol (SNMP) provider that not only receives trap notifications from network elements but also collects information from the network elements; A fault manager which classifies the fault information received from the simple network management protocol (SNMP) provider and processes it through a corresponding handler; A common information model object manager (CIMOM) which notifies when a failure indication is received from the fault manager and indicates failure recovery; And an quality of service (QoS) provider that provides a failure recovery method for resolving a failure according to the fault information of the fault manager and the instruction of the common information model object manager.

The Simple Network Management Protocol (SNMP) provider accepts all incoming requests from the common information model object manager, handles SNMP traps polling corresponding network elements according to the request, and all traps generated from the network elements. It consists of an SNMP trap handler that triggers the fault manager, which is responsible for the interface between the network management system and the actual network elements. It consists of a classifier for classifying faults and a number of handlers for handling the classified faults.

In addition, to achieve the above object, the method of the present invention comprises the steps of: SNMP trap handler forwarding the SNMP trap message from the network device provided with the SNMP agent to the indication provider; The indication provider checking the content and generating the required indication instance when a trap is received; The classifier classifies the disorder; Finding a handler corresponding to the classified failure, processing the failure, and delivering the failure to the common information model object manager; And failing back by calling a failure recovery method to be used by the MS quality of service provider.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 3 is a block diagram illustrating a common information model (WBEM / CIM) server based on web-based enterprise management to which distributed failure management is applied.

As shown in FIG. 3, the common information model (WBEM / CIM) server based on the web-based enterprise management to which the distributed failure management is applied, the common information model object manager (CIMOM) 310, and the fault manager ( 320, the interface QoS provider 330 and the SNMP provider 350. The fault manager 320 is composed of an indication provider 321, a classifier 322, a consumer 323, a handler 324, and a CIM client 325, and the interface QoS provider 330 is a method provider 331. , The association provider 332, the instance provider 334, and the CIM client 333, and the SNMP provider 350 includes an SNMP manager 351, an SNMP trap handler 352, and an SNMP network 353. Is connected to the network component 302 through.

Referring to FIG. 3, an SNMP provider 350 including an SNMP trap handler 352 receives an SNMP trap message from a network device 302 provided with an SNMP agent. It then forwards such a trap message to the fault manager 320.

The fault manager 320 receives a trap message or classifies a fault, and leaves or displays the classified information in a file. Depending on the type of fault, the fault manager 320 calls a method provider 331 that includes fault recovery and fault correction of a local or other network management system (NMS). According to the configuration of fault management, the network management system (NMS) is redirected to the user packet flow through the backup label switch path (LSP).

As described above, the present invention extends the functional structures of the fault manager 320 and the SNMP provider 350 to the existing architecture. The SNMP provider 350 not only receives trap notifications but also collects information from the network elements 302. In addition, the SNMP provider 350 plays an important role for the information passing to the WBEM server (CIMOM 310). In particular, the SNMP trap handler 352 portion of the SNMP provider 350 also plays an important role with respect to the traps that are forwarded to the WBEM server (CIMOM) 310.

Classifier 322 acts as a filter in OpenPegasus' indication mechanism. However, the filters extended by additional filtering mechanisms classify whether or not the trap currently needs to invoke path protection. And it can be seen that the log is required by the consumer 206. In addition, in the present invention, an extended management object format (MOF) is designed for traffic engineering failure management and differential path protection in an inter-AS network. Not provided by the Common Information Model (CIM).

The WBEM-based distributed failure management system of the present invention is basically designed for an MPLS network between inter domains. However, the present invention also includes a failure management function for the intra domain, and may be used in distributed failure recovery design (i.e. path recovery) and the like.

If a failure occurs during the link / node / path, the SNMP trap handler 352 receives a trap message from the network device 302. The CIM-XML 340 then transmits a trap message to a fault manager 320 that can classify the trap. The indication provider 321 included in the fault manager 320 checks the content and generates the required indication instance. Once a corresponding indication instance is created, it is subject to being processed by the classifier 322. Classifier (filter) 322 serves as a classifier to classify the disorder. Based on the fault classification and the scope of the fault notification, the fault is forwarded to the corresponding handler 324. On the intra-domain side, faults are handled locally, and if faults require end-to-end path recovery in an inter-domain network environment, they are forwarded to an ingress NMS. The failure is accepted by the CIM object manager 310, and the failure recovery method to be used is called in the inter-AS QoS Provider 330.

The failure management service is defined in the QoS_InterASNet_FMSrv (403) class and has an external method for notification of failure and recovery based on the management object (MO). The QoS_OAMService 402 Management Object Format (MOF) is designed for fault management. QoS_interASNet_PMSrv 404 is used to configure the start and stop of performance monitoring operations and collects the results. QoS_interASNet_FMSrv 403 is used to configure the failure and alarm notification function for abnormal situations in the inter-AS TE-LSP configuration, and is also used for failure recovery.

Most of the classes associated with MPLS traffic engineering (TE) are derived from CIM_EnabledLogicalElement and have a method called RequestStateChange (). For example, when receiving a trap from the SNMP trap handler that the MPLSTunnel is down, the federated class CIM_MPLSCurrenlyAssignedLSP finds and enumerates the associated CIM_MPLSLSPs in a managed object (MO) called CIM_MPLSTunnel. The state of the managed object MO changes according to the current state update.

For each MPLS LSP, the protection path options can be listed according to the protection needs of distinct user traffic such as 1: 1, 1: N, M: N. Backup LS is defined by CIM_MPLSBackupLSP and is related to CIM_MPLSTunnel and CIM_MPLSLSP. During service level agreement (LSA) between providers, the failover method is already connected and the backup path is established. Backup LSPs from ingress NMSs to egress NMSs are usually listed as a Shared Risk Link Group (SRLG).

The failure management service is defined in QoS_interASNet_FMSrv and serves to notify of failure / recovery. QoS_OAMService MOF is also designed for fault management. QoS_interASNet_PMSrv is used to configure the start and stop of performance measurement operations and collect statistics of the results. QoS_interASNet_CMSrv is used to gather connection configuration and traffic engineering information.

Although the present invention has been described in detail through specific embodiments, the present invention is not limited to the above-described embodiments, and various changes may be made by those skilled in the art to which the present invention pertains without departing from the spirit and scope of the present invention. It may be changed and implemented.

As described above, in the present invention, when a trap is received from a network element equipped with an SNMP agent, the present invention creates an indication instance, classifies the failure, performs a differential procedure according to the failure, and quickly finds the failure according to the service grade. Differential recovery procedures can be used to quickly recover from failures.

Claims (5)

A Simple Network Management Protocol (SNMP) provider that not only receives trap notifications from network elements but also collects information from the network elements; A fault manager which classifies the fault information received from the simple network management protocol (SNMP) provider and processes it through a corresponding handler; A common information model object manager (CIMOM) which notifies when a failure indication is received from the fault manager and indicates failure recovery; And Traffic in an autonomous manganese environment, characterized in that it comprises an Internet Quality of Service (QoS) provider that provides a failure recovery method for resolving a failure in accordance with the fault information of the fault manager and the common information model object manager. Fault management system using differential path protection based on web-based enterprise management for engineering. The method of claim 1, wherein the Simple Network Management Protocol (SNMP) provider An SNMP manager that accepts all requests from the common information model object manager and polls corresponding network elements according to the request; It consists of an SNMP trap handler that handles all traps originating from the network element and triggers the fault manager. A failure management system using differential path protection based on web-based enterprise management for traffic engineering in an autonomous network environment characterized by being in charge of the interface between the network management system and the actual network elements. The method of claim 1, wherein the fault manager Autonomy characterized by an indication provider that checks content when a trap is received and generates the required indication instance, a classifier for classifying the fault, and a plurality of handlers for handling the classified fault. A failure management system using differential path protection based on web-based enterprise management for traffic engineering in manganese environment. Forwarding the SNMP trap handler to an indication provider when the SNMP trap handler receives an SNMP trap message from a network device provided with an SNMP agent; The indication provider checking the content and generating the required indication instance when a trap is received; The classifier classifies the disorder; Finding a handler corresponding to the classified failure, processing the failure, and delivering the failure to the common information model object manager; And A failure management method using differential path protection based on web-based enterprise management for traffic engineering in an autonomous manganese environment, comprising the steps of recovering from failure by calling a failure recovery method to be used by an MS service quality provider. The method of claim 4, wherein the failover method is A method for managing failures using web-based enterprise management-based differential path protection for traffic engineering in an autonomous manganese environment, characterized by redirection to user packet flow through a backup label switch path (LSP).

Images