KR100480650B1 - Method for reinitialization in TMN agent - Google Patents

Abstract

The present invention relates to a method of reinitialization of a TMN agent that enables matching of a failure state between an exchange and an agent MIB when the TMN agent is reinitialized.

Conventionally, a failure occurrence event or a failure release event is received from the exchange through the CASS connection module and the failure management interface module and reflected by the TMN agent to the MIB. The TMN agent or the CASS connection module or failure management interface module is down. When the TMN agent loses a report of a failure event or a failure release event occurring at the exchange during the reinitialization of the TMN agent, there is a problem that the state between the MIB of the TMN agent and the exchange resource is inconsistent.

The present invention provides a switch by logging a failure event report or a failure release event report generated at the exchange during reinitialization of the TMN agent, and forwarding the failure event or failure release event report logged when all of the reinitialization is completed. The failure state between the agent and the agent MIB can be matched.

Description

Method for reinitialization in TMN agent

The present invention relates to a method of reinitializing a Telecommunication Agent Network (TMN) agent, and in particular, when reinitializing the TMN agent, reinitialization of the TMN agent to match a failure state between the exchange and the agent Management Information Base (MIB). It is about a method.

In general, a TMN (Telecommunication Management Network) is a network management structure proposed to provide a network service and a network management function, so that various types of operating systems and communication equipments can exchange management information using a standardized interface. It is to.

The exchange of the above-mentioned management information is a function required for a TMN agent that directly manages network elements using a management object. When a failure event message occurs at the exchange, the TMN agent manages a managed object instance corresponding to the failed resource. Reflects the failure status and releases the failure status of the managed object instances corresponding to the resource when the event message is released.The managed object instances are stored in the Management Information Base (MIB) structure and the TMN agent is stored. Managed by

When the TMN agent is started for the first time, the initial state of the MIB is normal, and the initial state is matched by reading all faults currently occurring from the exchange and reflecting them in the MIB. After that, the TMN agent runs to report the failure event in the exchange and declare the status of the corresponding resource stored in the MIB as a failure state. When the failure release event occurs in the exchange, the TMN agent reports and receives the failure state of the corresponding resource stored in the MIB. Declares to be normal.

1 is a flowchart illustrating a failure management method of a conventional TMN agent, when a message outputted from an exchange is received by a connection module of a CASS (Connector for TMN Agent and ATM Switching System) (S10), the received message fails It is determined whether it is about an event (S12). If the message received as a result of the determination in step S12 relates to a fault event, the message received from the exchange is authorized to the fault management interface module (S14), and the fault management interface module receiving the message from the connection module is authorized. A failure event message is constructed using the message (S16).

Subsequently, the failure event message configured in the above process S16 is delivered to the agent (S18), and the agent, which has received the failure event message, reflects the failure state of the corresponding resource in the MIB using the failure event message (S20), and sends it to the manager. Informs the failure state (S22).

As described above, in the related art, a failure occurrence event or a failure release event is received from the exchange through the CASS connection module and the failure management interface module and reflected by the TMN agent to the MIB. Occasionally, the failure management interface module goes down and loses reporting of failure events or failure releases occurring at the exchange while reinitializing the TMN agent.

As described above, if a failure occurrence event or a failure release event report that occurs at the exchange is lost, there is a problem that the state between the MIB of the TMN agent and the exchange resource is inconsistent. For example, if a failure event report is lost, the resource will appear to be normal at the TMN agent. If a failure release event report is lost, the resource will remain at the TMN agent, causing the TMN agent to lose its MIB and exchange resources. There is a problem that the state is inconsistent.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and the failure event or failure that is logged when the reinitialization is completed after logging the failure event report or failure release event report that occurred at the exchange during reinitialization of the TMN agent. It is an object of the present invention to provide a method of reinitialization of a TMN agent that enables a failure state match between an exchange and an agent MIB (Management Information Base) to be delivered to the agent.

A feature of the present invention for achieving the above object is, through a Connector for TMN Agent and ATM Switching System (CAS) having a connection module, a configuration management interface module, and a failure management interface module to a TN agent (TMN) agent In the case of managing the fault information of the exchange by the TMN agent by accessing the exchange, reinitializing the T & M agent for restarting the TMN agent when the connection module or fault management interface module of the CASS is down or the TMN agent is down CLAIMS 1. A method comprising: requesting reinitialization with a failure management interface module and a configuration management interface module; A link failure information reinitialization process in which the configuration management interface module transmits link failure information of the exchange side to the TMN agent according to the reinitialization request to perform reinitialization of link failure information; And a board failure information reinitialization process in which the failure management interface module transmits board failure information of the exchange side to the TMN agent according to the reinitialization request and reinitializes board failure information.

The link failure information reinitialization process may include: transmitting current failure information of each link to a TMN agent by a configuration management interface module according to the reinitialization request; And including the current failure information of each received link in the TMN agent in a management information base (MIB).

The board failure information reinitialization process starts to log a failure event report message transmitted from the exchange in the failure management interface module according to the reinitialization request, retrieves current failure information of each board, and retrieves a failure information file. Configuring and requesting reinitialization with the TMN agent; Configuring a failure information table using the failure information file in a TMN agent according to a request for reinitialization of the failure management interface module; Matching all of the board management objects, which are management objects corresponding to the board retrieved from the MIB, with failure information of the failure information table; Transmitting a reinitialization termination message to the failure management interface module if all of the failure information match; Terminating the logging of the failure event report message transmitted from the exchange by the failure management interface module receiving the reinitialization termination message, and transmitting the logged failure event report message to the TMN agent. .

The matching of all the failure information may include: when there is no failure in the board management object found in the MIB, and a failure exists in the failure information table of the corresponding board, the failure information in the failure information table is stored in the board management object. Reflecting on; Releasing a failure present in the board management object when a failure exists in the board management object and a failure does not exist in the failure information table; If a failure exists in the board management object and a failure exists in the failure information table, determining whether the failure in the board management object is the same as the type of failure in the failure information table; If it is determined that the types of failures are not the same, releasing a failure in the board management object and reflecting another failure in the failure information table in the board management object; If it is determined that the types of failures are the same, determining whether the failures in the board management object and the failures in the failure information table are the same; If it is determined that the grade of the failure is not the same, characterized in that it comprises the step of reflecting the failure grade in the failure information table to the board management object.

Hereinafter, a method of reinitializing a TMN agent according to a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

2 is a road illustrating an Asynchronous Transfer Mode (ATM) exchange management system to which a reinitialization method of a TMN agent according to the present invention is applied, a TMN agent 10, a CASS 20, an HMI server 30, and an HMI. A client 40 and an ATM switch 50 are provided.

In such a configuration, the TMN agent 10 manages the same shape and state information as the ATM switch 50 by using the management object modeled by the object-oriented model of the ATM switch 50 to be managed.

The CASS 20 is responsible for the interface between the TMN agent 10 and the ATM switch 50, and includes a connection module 21, a configuration interface module 23, and fault management. An interface module (Alarm Interface Module) 25, a connection management interface module (Connection Interface Module) 27, and a performance management interface module (Performance Monitoring Interface Module) 29 is provided.

As described above, the connection module 21 is connected to the HMI server 30 and plays a role of transmitting and receiving messages of the TMN and the TMN, and the configuration management interface module 23 converts messages related to configuration management. The fault management interface module 25 is responsible for the conversion of messages related to the failure management, the connection management interface module 27 is responsible for the conversion of messages related to the connection management, the performance management interface module 29 ) Is responsible for the conversion of messages related to performance management.

Meanwhile, the HMI server 30 transmits an encoding message handling the operation of the ATM switch 50 to the ATM switch 50, receives a result message sent from the ATM switch 50, and receives a TMN agent through the CASS 20. Transfer to (10). Then, a string message is received from the plurality of HMI clients 40 and transmitted to the ATM switch 50.

HMI client 40 receives a response message from ATM switch 50 via HMI server 30.

Hereinafter, the operation of the ATM switch management system will be described.

When the TMN agent 10 receives a command from the manager, the TMN agent 10 requests a command to the ATM switcher 50 through the HMI server 30 to reflect the command to the corresponding ATM switcher 50 resources. The message is converted in the CASS 20 between the HMI servers 30.

The CASS 20 requests the HMI server 30 for commands from the TMN agent 10, and transfers the results to the TMN agent 10, and the results of the commands from other HMI clients 40. In order to reflect the MIB of the TMN agent 10, it delivers it to the TMN agent 10 and delivers events occurring at the other ATM switch 50 to the TMN agent 10.

Then, processes such as the configuration management interface module 23, the failure management interface module 25, the connection management interface module 27, the performance management interface module 29, and the like are matched with the HMI server 30. The connection module 21 exists in the CASS 20. In the case of failure management, the TMN agent 10 sends an event of failure or an event of failure release from the ATM switch 50 to the connection module 21 of the CASS 20. And through the failure management interface module 25.

As described above, the TMN agent 10 that receives the event of failure or the event of failure release through the connection module 21 and the failure management interface module 25 of the CASS 20 reflects this to the MIB.

As described above, the TMN agent 10 receives a case of failure or an event of failure through the connection module 21 and the failure management interface module 25 of the CASS 20 to perform a failure management function. When the TMN agent 10 or the failure management interface module 25 or the connection module 21 of the CASS 20 is down and reinitialized, the failure state of the ATM switch 50 and the MIB state of the TMN agent 10 are reset. You must perform the process of matching.

3A and 3B are flowcharts illustrating a method of reinitializing a TMN agent according to the present invention.

The types of failures managed by the TMN agent can be broadly divided into failures related to boards and failures related to physical links, both of which are managed by the failure management interface module 25, but at the time of initialization, the failure management interface module 25 The board manages faults and the configuration management interface module 23 manages faults related to physical links.

First, when the connection module 21 is down and the connection module 21 is restarted, the reconfiguration initialization is requested to the failure management interface module 25 and the configuration management interface module 23 (S30, S32, S40). ).

In step S32, the configuration management interface module 23, which receives the re-initialization request from the connection module 21, checks the link state of the ATM switch 50, and reports each event on the normal link and the failed link. It transmits to TMN agent 10 (S34).

In step S34, the TMN agent 10, which has received the failure event report for each link from the configuration management interface module 23, checks the failure information and the incident report of the corresponding link stored in the MIB, respectively, and the configuration management interface. Failure information of each link received from the module 23 is reflected in the MIB (S36) and reported to the manager (S38).

On the other hand, the failure management interface module 25 that has received the re-initialization request from the connection module 21 in the above-described process S40 starts logging the failure event report message transmitted from the ATM switch 50 (S42). In addition, after retrieving all the information of the boards that are currently failing in the ATM switcher 50 to construct a failure information file, the TMN agent 10 requests reinitialization (S44 and S46).

In step S46, the TMN agent 10 that has been requested to reinitialize from the failure management interface module 25 uses a failure information file configured by the failure management interface module 25 in step S44 according to the reinitialization request. A failure information table such as 4 is configured (S48).

Thereafter, the MIB searches all the board management objects (circuitPack), which are management objects corresponding to the boards, from the beginning, and determines whether a failure exists in the found board management objects (S50, S52, and S54). As a result of the determination of step S54, if there is no failure in the detected board management object, it is determined whether a failure of the corresponding board exists in the failure information table (S56).

If the failure of the corresponding board does not exist in the failure information table as a result of the determination of step S56, the process proceeds to the above process S52 to search for the next board management object, and if the failure of the corresponding board exists in the failure information table, the failure information table. Reflect failure information in the reflected board management object (S58), and reports it to the administrator (S60).

On the other hand, if a failure exists in the detected board management object as a result of the determination of step S54, it is determined whether a failure of the corresponding board exists in the failure information table (S62).

If the failure of the corresponding board does not exist in the failure information table as a result of the determination of step S62, the failure in the board management object is released (S64), and reported to the administrator (S66).

On the other hand, if the failure of the board exists in the failure information table as a result of the determination in step S62, it is determined whether the failure in the board management object is the same by comparing the types of failures in the failure information table (S68). As a result of the determination in step S68, if the types of failures are not the same, the failure in the board management object is released (S70), and reported to the administrator, it is then determined whether other failures exist in the corresponding failure information table (S72). , S74).

If there is no other failure in the corresponding failure information table as a result of the determination of step S74, the process proceeds to the above-mentioned step S52 to search for the next board management object, and if another failure exists in the corresponding failure information table, After reflecting the failure information to the board management object (S76), and reporting it to the administrator (S78), the process proceeds to step S74 to determine whether there is another failure in the failure information table.

On the other hand, if the types of failures are the same as the result of the determination in step S68, it is determined whether the failures in the board management object are the same by comparing the failure grades in the failure information table (S80). If the grades of the failures are not the same as the result of the determination of step S80, the grade information of the failures in the failure information table is reflected in the board management object (S82). Determine if a disability exists.

On the other hand, if the grade of the disorder is the same as the result of the determination of step S80 proceeds to step S74 described above and determines whether there is another failure in the corresponding failure information table.

As described above, when the reinitialization is completed by repeating the processes S52 to S82, the TMN agent 10 transmits a message indicating that the reinitialization is completed to the failure management interface module 25 (S84), and reinitialization. The failure management interface module 25 receiving the termination message completes the logging of the failure event report message transmitted from the ATM switch 50, and transmits the failure event report message that has been logged since the process S42 to the TMN agent 10. (S86).

Secondly, if the failure management interface module 25 is down and the failure management interface module 25 is restarted (S88), the process proceeds to step S32 and requests for reinitialization to the configuration management interface module 23. At the same time, the process proceeds to step S42, and the failure management interface module 25 itself also starts logging the failure event report message transmitted from the ATM switcher 50 and undergoes a reinitialization process.

Thirdly, if the TMN agent 10 is down and the TMN agent 10 is restarted (S90), the process proceeds to step S32 described above and requests for re-initialization to the configuration management interface module 23. The flow proceeds to step S40 to request re-initialization to the failure management interface module 25.

4 is a diagram showing the configuration of the failure information table applied to the present invention, the failure information table applied to the present invention includes a failure information field (a) indicating the type of failure and board position information indicating the location of the board on which the failure has occurred. It has a form of a linked list consisting of a field (b), a flag field (c) indicating that the corresponding information is referenced, and a next point field (d) indicating a starting point of the next failure information table.

The reinitialization method of the TMN agent of the present invention is not limited to the above-described embodiments, and may be modified in various ways within the scope of the technical idea of the present invention.

According to the method of reinitialization of the TMN agent of the present invention as described above, a failure event report or a failure release event report that occurred at the exchange during the reinitialization of the TMN agent was logged when the reinitialization is completed. By delivering an event or fault release event report to the agent, there is an effect that the failure state between the exchange and the agent MIB can be matched.

1 is a flowchart illustrating a failure management method of a conventional TMN agent.

2 is a diagram illustrating an ATM switch management system to which a reinitialization method of a TMN agent according to the present invention is applied.

3A and 3B are flowcharts illustrating a method of reinitializing a TMN agent according to the present invention.

4 is a diagram showing the configuration of a failure information table applied to the present invention.

*** Explanation of symbols for the main parts of the drawing ***

10.TMN agent, 20.CAS,

21. Connectivity module, 23. Configuration management interface module,

25. fault management interface module, 27. connection management interface module,

29. Performance management interface module, 30. HMI server,

40. HMI client, 50. ATM switch

Claims (4)

Through the CASS (Connector for TMN Agent and ATM Switching System) having a connection module, a configuration management interface module, and a failure management interface module, the exchange is connected to a Telecommunications Network Agent (TMN) agent and the failure information of the exchange is exchanged by the TMN agent. In the case of managing, in the method of re-initialization of the TN agent for restarting the TMN agent when the connection module or failure management interface module of the CASS is down or the TMN agent is down, Requesting reinitialization with the failure management interface module and a configuration management interface module; A link failure information reinitialization process in which the configuration management interface module transmits link failure information of the exchange side to the TMN agent according to the reinitialization request to perform reinitialization of link failure information; And a board failure information reinitialization process of re-initializing board failure information by transmitting board failure information of the exchange side to the TMN agent in response to the reinitialization request. How to reinitialize an agent. The method of claim 1, wherein the link failure information reinitialization process, Transmitting, by the configuration management interface module, current failure information of each link to a TMN agent according to the reinitialization request; And retransmitting the current failure information of each link received by the TMN agent in a management information base (MIB). The method of claim 1, wherein the board failure information reinitialization process, In response to the reinitialization request, the failure management interface module starts logging a failure event report message transmitted from the exchange, retrieves current failure information of each board, constructs a failure information file, and requests reinitialization to the TMN agent. Process; Configuring a failure information table using the failure information file in a TMN agent according to a request for reinitialization of the failure management interface module; Matching all of the board management objects, which are management objects corresponding to the board retrieved from the MIB, with failure information of the failure information table; Transmitting a reinitialization termination message to the failure management interface module if all of the failure information match; Terminating the logging of the failure event report message transmitted from the exchange in the failure management interface module receiving the reinitialization termination message, and transmitting the logged failure event report message to the TMN agent. Reinitialization method of TEM agent. The process of claim 3, wherein the matching of all the disability information comprises: If a failure does not exist in the board management object retrieved from the MIB and a failure exists in the failure information table of the board, reflecting the failure information in the failure information table to the board management object; Releasing a failure present in the board management object when a failure exists in the board management object and a failure does not exist in the failure information table; If a failure exists in the board management object and a failure exists in the failure information table, determining whether the failure in the board management object is the same as the type of failure in the failure information table; If it is determined that the types of failures are not the same, releasing a failure in the board management object and reflecting another failure in the failure information table in the board management object; If it is determined that the types of failures are the same, determining whether the failures in the board management object and the failures in the failure information table are the same; If it is determined that the failure grades are not the same, reflecting the failure grades in the failure information table to the board management object.