KR20020084587A - System and Method of Duplicating Network Devices between a IP and a CMS - Google Patents

Abstract

PURPOSE: A duplexing system of network devices between an IP(Intelligent Peripheral) and a CMS(Centralized Management System) is provided to reciprocally manage and duplex processor devices connected to network devices for configuring a management network between an IP and a CMS, thereby collecting stable management information. CONSTITUTION: Duplexing routers(51,52) are connected to an exclusive network, and interwork with a CMS(60) through an SNMP(Simple Network Management Protocol). Duplexing hubs(41,42) operate as primaries or secondaries connected to each other. If the primaries are normal, the primaries perform active roles. If the primaries are abnormal, the secondaries perform active roles, to connect the duplexing routers(51,52) by the duplexing hubs(41,42). OAMPs(Operation and Management Processors)(31,32) of an IP(30) interwork with the CMS(60) by the SNMP, and operate as active modes or standby modes according to states of the duplexing hubs(41,42), then perform maintenance functions.

Description

System and Method of Duplicating Network Devices between a IP and a CMS

The present invention relates to a system and method for redundancy of network devices between IP and CMS, and more particularly, to manage not only network devices between IP and CMS but also devices of processors connected thereto. The present invention relates to a redundancy system and method for network devices between a CMS and a CMS.

An exemplary view schematically illustrating a relationship between general IPs and a CMS is illustrated in FIG. 1. Here, the plurality of IPs (10-1 to 10-n) is an intelligent information providing system among the elements of the advanced intelligent network (AIN), and is customized in order to exchange various information between the service user and the intelligent network. Announcements, speech recognition, speech synthesis, voice recording, dual tone multi-frequency (DTMF) digit collectors, protocol converters, FAX transceivers, audio conferencing bridges, information distribution bridges, etc. By providing the same special resources in the intelligent network, it enables flexible and effective information exchange between the service user and the intelligent network.

In addition, the CMS 20 is a centralized management system for integrating and managing a plurality of IPs 10-1 to 10-n, and the plurality of corresponding CMSs as a simple network management protocol (SNMP) which is one of network management protocols. It is connected to IP 10-1 to 10-n. In this case, the SNMP is a protocol used universally between the network management system CMS 20 and the management system IP 10-1 to 10-n for network management, and manages a management object as a MIB (Management Information Base). ), And it is a network management protocol that allows simple operations such as 'GET', 'SET', and 'TRAP' for each object defined in the MIB.

Then, looking at the duplex structure of the network device through the conventional dual network as follows.

As shown in FIG. 2, OAMPs 11 and 12, which are interface processors included in the IP 10, are duplicated, and stable information transfer, statistics, and system events between the IP 10 and the CMS are duplicated. Networks 15-1, which include hubs 13-1 and 13-2 and routers 14-1 and 14-2, which are network configuration devices for stably collecting management data such as (System Event), etc. 15-2) is dualized, and each of the corresponding OAMPs 11 and 12 is connected to the two hubs 13-1 and 13-2, respectively, to send messages through the two networks 15-1 and 15-2. Each can be sent and received. For example, for a dual network configuration, the first network 15-1 has a network address of '150.150.17.x' and the second network 15-2 has a network address of '150.150.18.x' Has

However, since there is no connection between the two hubs 13-1 and 13-2 in the duplexing scheme through the network having the above-described configuration, for example, the router 14-1 in the first network 15-1 If a failure occurs, the second network 15-1 receives a message received from the IP 10 even if the hub 13-1 in the first network 15-1 detects and determines the failure. It could not be delivered directly to the inner hub 13-2 side.

Therefore, if there is no response message from the CMS side for a predetermined time after delivering the message to the CMS in the application of the OAMP (11, 12), the application itself of the OAMP (11, 12) to send a message to the second network ( Must be communicated again via 15-2).

That is, in the conventional network configuration method, when configuring a management network, each network device, that is, a LAN port, a hub, a router, etc. must have a different network address, and if a corresponding network device fails, the corresponding network device is searched for. Judgment of the network needs a little time to recover, and there was a problem that can not guarantee a stable collection of management information.

In addition, in the case of a dual network, two identical IP addresses should be assigned to the duplicated OAMPs in the IP, for example, '150.150.17.x' and '150.150.18.x'. Since it is not allowed to have the same IP address, two MAC addresses cannot be assigned to one MAC address. Therefore, the port of the inactive processor must be kept down. As a result, in the event of an active processor failure, the user must explicitly down ports his processor and up the ports of the inactive processors. There is a problem that makes recovery of a network faster.

The present invention has been made to solve the above-described problems, and the present invention is integrated with the network devices constituting the management network between the IP and the CMS, as well as the devices of the processors connected thereto to perform the integrated management redundantly, By collecting more stable management information, it is possible to prevent the interruption of the collection of management information due to the abnormality of each network device, and to provide a stable and reliable network configuration.

In addition, the present invention provides a service in a redundant stand-by network device when a network device, such as a hub, a router, and a LAN port, which are network devices between an IP and a CMS, are duplexed, respectively, and a corresponding network device fails during network operation. Its purpose is to keep it running.

In addition, the present invention implements a single network having a single network address so that all network devices between IP and CMS have the same network address, so that each network device has a different network address when configuring a management network. Its purpose is to enable fast recovery in the event of a network device failure, rather than network configuration.

1 is a block diagram schematically showing a relationship between general intelligent peripherals (IP) and a centralized management system (CMS).

2 is a block diagram illustrating a duplex structure of a network device through a conventional dual network.

3 is a block diagram illustrating a redundancy system of IP and CMS network devices according to an embodiment of the present invention.

FIG. 4 is a block diagram illustrating a redundant configuration of an operation and management processor (OAMP) in FIG. 3. FIG.

5 is a flowchart illustrating a duplication method of network devices between an IP and a CMS according to an exemplary embodiment of the present invention.

6 is an exemplary diagram illustrating a data flow when a port failure occurs in FIG. 3.

7 is an exemplary diagram illustrating a data flow when a hub failure occurs in FIG. 3.

8 is an exemplary diagram illustrating data flow when a router failure occurs in FIG. 3.

Explanation of symbols on the main parts of the drawings

30: IP 31, 32: OAMP

31-1, 32-1: Redundancy Management Process

31-2, 32-2: Application Process

31-3, 32-3: Port Management Process

41 ~ 44: Hub 51 ~ 54: Router

60: CMS

According to an aspect of the present invention, there is provided a redundant system of network devices between IP and CMS, including: a duplicated router that allows a connection to a CMS through SNMP by accessing a dedicated network; A redundant hub that connects the redundant router by operating as a primary or secondary connected to each other by a trunk and performing an activation role if the primary is normal and an activation role if the primary is abnormal; It is characterized in that it comprises a duplicated OAMP in IP to operate in the activation or deactivation according to the state of the redundant hub in conjunction with the CMS by the SNMP to perform system operation and maintenance functions. Here, the redundant OAMP is a duplication management process for activating all applications by determining the activation side by sending and receiving a heartbeat message at regular intervals; An application process for delivering events and various statistical data of a system to the CMS by activating the redundancy management process, collecting various data required by the CMS through an internal database and other application programs, and delivering the data to the CMS; It includes a port management process that periodically checks the state of the redundant Ethernet ports and sets a representative IP address on the active Ethernet port so that applications always communicate through a single IP address regardless of the state of the Ethernet port. It is characterized by.

On the other hand, the duplexing method of the network devices between the IP and CMS according to an embodiment of the present invention for achieving the object as described above, all the application programs by determining the activation side by transmitting and receiving each other as a heartbeat message between the duplication management process at regular intervals Activating the process; Assigning an IP address to the redundant Ethernet port, inspecting the state of the Ethernet port at a predetermined period, and setting a representative IP address according to the state of the Ethernet port; In the event that a failure occurs in the Ethernet port, the failure information is reported, and a representative IP-address is set on the Ethernet port which is in an inactive state.

Preferably, the method of redundancy of the network devices between the IP and the CMS according to an embodiment of the present invention includes the steps of switching the deactivated hub to an activated state through a trunk when a hub in an activated state fails; The method may further include performing a switchover to the hub side of the inactive state by setting the representative IP-address to the Ethernet port in the inactive state by reporting the failure information.

Also, preferably, the duplexing method of the network devices between the IP and the CMS according to an embodiment of the present invention further detects the failure of the router in the activated state and routes the message through the hub in the inactive state through the trunk. Characterized in that the made up. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The present invention provides a redundant system and method of a network device, i.e., a hub, a router, a LAN port (or an Ethernet port), for stable information transfer between an IP and a CMS, and a redundant system and method of an OAMP, which is a processor interworking with a CMS in IP. 3 is a block diagram illustrating a duplexing system of IP devices between IP and CMS according to an exemplary embodiment of the present invention. The configuration is IP 30 and redundant IP side hubs 41 and 42. ), The redundant IP side routers 51 and 52, the duplicated CMS side routers 53 and 54, the duplicated CMS side hubs 43 and 44, and the CMS 60.

The IP 30 is an intelligent information management system managed by the CMS 60. The IP 30 includes redundant OAMPs 31 and 32 configured for redundancy for stable operation of the system. 32 is a processor that performs system operation and maintenance functions, and performs an agent function for interworking with the CMS 60 through SNMP. The configuration thereof is illustrated in FIG. 4, and the redundancy management process 31 is performed. -1, 32-1, application processes 31-2, 32-2, and port management processes 31-3, 32-3, respectively. In addition, each process (31-1, 32-1, 31-2, 32-2, 31-3, 32-3) in the redundant OAMP (31, 32) has two Ethernet ports for external network connection. Each of the corresponding Ethernet ports performs activation or deactivation according to the state of the redundant IP side hubs 41 and 42, and is connected to the redundant IP side hubs 41 and 42, respectively.

Here, the duplication management processes 31-1 and 32-1 transmit and receive information, that is, heart-beat messages, at regular intervals between the first OAMP 31 and the second OAMP 32, so that either side can receive the information. It decides whether to be active, and if it is decided to activate, it activates all applications to perform system operation and maintenance functions, whereas if it is determined to be stand-by, all applications To disable it to maintain the standby state. The heartbeat message is delivered using an Ethernet heartbeat channel connected between the first OAMP 31 and the second OAMP 32, and the Ethernet heartbeat channel is redundantly connected and activated. Alternatively, the operation can be performed by deactivation.

The application processes 31-2 and 32-2 perform a function of an SNMP application on the managed side (i.e., IP 30) that performs SNMP, that is, an SNMP agent that is an application of OAMPs 31 and 32. It is activated by the activation operation of the duplication management process (31-1, 32-1) and delivers the event (Alarm) and various statistical data of the system to the SNMP Manager (Manager) of the CMS (60) side, Various data required by the SNMP manager are collected through the duplicated OAMP (31, 32) database and other application programs, and then transferred to the corresponding SNMP manager.

The port management processes 31-3 and 32-3 perform a function of maintaining a redundant Ethernet port, that is, periodically checking the status of the redundantly connected Ethernet port, and representing a representative IP according to the state of the corresponding Ethernet port. It sets the address, that is, by setting a representative IP address on an active Ethernet port so that applications can always communicate through a single IP address regardless of the state of the Ethernet port.

The duplicated IP side hubs 41 and 42 serve as a layer 3 switch for connecting the IP 30 to a network, and operate as a primary or a secondary. The primary side hub, for example, the first hub 41 to perform the activation role when performing the normal operation, and when the abnormal operation the secondary side hub, for example the second hub 42 performs the activation role In addition, if the first hub 41 and the second hub 42 is connected to the trunk (Trunk) by the trunk (Trunk) if one of the redundant IP side routers (51, 52) other failure that does not occur Allows routing to hubs connected to one. Here, the layer 3 switch refers to a hub having a capability of routing data in units of IP packets, which is the third of the OSI 7 layer protocols.

The redundant IP side routers 51 and 52 are connected to the redundant IP side hubs 41 and 42, respectively, and serve to connect to a dedicated network.

The duplicated CMS side routers 53 and 54 and the duplicated CMS side hubs 43 and 44 operate similarly to the duplicated IP side routers 51 and 52 and the duplicated IP side hubs 41 and 42. Do this.

The CMS 60 is a system that integrates and manages a plurality of IPs 30, and a remote status detection function, a remote monitoring function, a remote login function, a remote file transmission function, a voice file listening function, and a voice file of each IP 30. It performs editing function, software version management function, statistics collection function, voice recognition data processing function, etc., and interworking with IP 30 through SNMP, and consists of a single processor.

The duplexing method of network devices between IP and CMS according to an embodiment of the present invention is as follows. Here, all network devices between the corresponding IP and the CMS are implemented in a single network having one network address and have the same network address.

First, the IP 30, which is an intelligent information management system managed by the CMS 60, performs system operation and maintenance functions including the redundant OAMPs 31 and 32 configured for the stable operation of the system.

At this time, the duplication management processes 31-1 and 32-1 in the OAMPs 31 and 32 transmit and receive heartbeat messages to each other at regular intervals to determine which side is to be activated. After checking whether it is set to the head (e.g., the first redundancy management process 31-1), it is checked whether there is an abnormality, and if it is a primary and there is no abnormality, it determines that it is activated (step S1). ). In this case, when the self has a primary or abnormality, the state is reported to the higher process and the second redundant management process (eg, the second redundancy management process 32-1) is routed to the inactive state. 32-1) is activated.

If it is determined in the first step (S1) to be deactivated (Stand-by), it is to deactivate all applications in the second OAMP 32 of the deactivated state to maintain the standby state (step S2).

On the other hand, if the self is determined to be activated in the first step (S1), it activates all applications in the first OAMP (31) of the activated state to perform the system operation and maintenance functions. Accordingly, the first application process 31-2 in the first OAMP 31 performs a function of an SNMP agent. The event and various statistical data of the system are activated by the activation operation of the first redundancy management process 31-1. It delivers to the SNMP manager of the CMS (30) side, and collects the various data required by the SNMP manager through the database and other applications of the first OAMP (31) and then delivers to the SNMP manager. (Step S3).

On the other hand, each process in the redundant first OAMP (31) uses two Ethernet ports for external network connection, each Ethernet port to enable or disable depending on the state of the redundant IP side hub (41, 42) The function of maintaining the duplicated Ethernet port and performing the operation is performed by the first port management process 31-3 in the first OAMP 31.

In other words, the first port management process 31-3 periodically checks the state of the redundantly connected Ethernet port and sets a representative IP address according to the state of the Ethernet port. By setting a representative IP address, the application can always communicate through a single IP address regardless of the state of the Ethernet port.

In more detail, the first port management process 31-3 manages an Ethernet port connected to the first OAMP 31. First, IP addresses for process duplication and Ethernet port duplication are shown in Table 1 below. Give it together.

process Ethernet port IP address Representative IP Address First OAMP 1st port 150.150.52.1 150.150.52.3 2nd port 150.150.52.2 2OAMP 1st port 150.150.52.10 150.150.52.13 2nd port 150.150.52.11

That is, after assigning an IP address to each Ethernet port (step S4), a representative IP address capable of representing each process is assigned, wherein the first port management process 31-3 performs the duplication at regular intervals. Check the status of the connected Ethernet port to see if there is a failure (step S5).

If there is no failure in the Ethernet port connected by the duplication in the fifth step S5, the representative IP address is assigned according to the representative IP address assignment principle as shown in Table 2 below (step S6). Here, the representative IP address is to represent the process according to the Ethernet port state of each process, the application program of the first OAMP 31 can exchange messages with the CMS 60 side through the corresponding representative IP address. Will be.

1st port 2nd port Representative IP Address Normal (150.150.52.1) Normal (150.150.52.2) First side (150.150.52.3) Normal (150.150.52.1) Disability (150.150.52.2) First side (150.150.52.3) Disability (150.150.52.1) Normal (150.150.52.2) Second side (150.150.52.3) Disability (150.150.52.1) Disability (150.150.52.2) First side (150.150.52.3)

On the other hand, if there is a failure in the Ethernet port connected by the duplication in the fifth step (S5), as shown in Figure 6, it is an exemplary view showing the data flow when the failure of the corresponding Ethernet port, the first port The management process 31-3 reports to the first redundancy management process 31-1 that the first port and the second port fail in the table 2 (step S7). Accordingly, the first redundancy management process 31-1 operates only one port by setting a representative IP-address shown in Table 2 to the Ethernet port that is in an inactive state and performing a switch over to the second side. It can be performed so that it can always be communicated without interruption of service (step S8).

On the other hand, the redundant IP side hubs 41 and 42, which are layer 3 switches for connecting the IP 30 to the network, operate in a primary or secondary manner. After checking whether it is set to this primary (for example, the first hub 41), it is confirmed whether or not there is an abnormality, and when it is the primary and there is no abnormality, it decides to activate.

If it is determined that the self is activated, the first hub 41 performs a normal activation role and transfers a message of the SNMP manager of the CMS 60 to the IP 30 and is authorized from the IP 30. The message is delivered to the SNMP manager of the CMS 60, while maintaining the standby state when it is determined to be inactive.

In this case, when a failure occurs in the first hub 41 that is operating in the activated state, as shown in FIG. 7, an example of data flow when the failure occurs in the first hub 41 is shown. The port management processes 31-3 and 32-3 manage similarly to the operation when the above-described Ethernet port fails.

That is, the secondary (eg, the second hub 42) is transferred from the deactivated state to the activated state through a trunk that always maintains the link of data, and at the same time, the failure contents of the first hub 41 are changed. This first port management process 31-3 is reported to the first redundancy management process 31-1.

Accordingly, the first redundancy management process 31-1 sets the representative IP-address shown in Table 2 to the Ethernet port in the inactive state and switches over to the second hub 42, without interruption of service. It allows communication at all times.

In addition, a trunk is connected between the first hub 41 and the second hub 42 so that one of the redundant IP side routers 51 and 52 is connected to the other that does not occur when a failure occurs. Allows routing to hubs.

On the other hand, Figure 8 is an exemplary view showing the data flow when the failure of the first router 51, the first hub 41 monitors the failure of the first router 34, the first When a failure occurs in the router 51, the message is routed through the second hub 31 directly through the trunk, so that communication can be always performed without interruption of service.

As described above, the present invention collects more stable management information by collectively performing redundant management by connecting and managing network devices constituting the management network between IP and CMS, as well as devices of processors connected thereto. The interruption of the collection of management information due to the abnormality of each network device can be prevented in advance, and a stable and reliable network configuration can be provided.

In addition, according to the present invention, the hub, router, and LAN ports, which are network devices between the IP and the CMS, are duplicated, respectively, and if the corresponding network device fails during network operation, the service is activated by activating the redundant inactive network device. Can be done. In addition, the present invention implements a single network having one network address so that all network devices between the IP and the CMS have the same network address, so that each network device has a different network address when configuring a management network. Faster recovery can be performed in the event of a network device failure than the network configuration method.

Claims (5)

A duplicated router connecting to a private network and interworking with the CMS through SNMP; A redundant hub that connects the redundant router by operating as a primary or secondary connected to each other by a trunk and performing an activation role if the primary is normal and an activation role if the primary is abnormal; IP and CMS network, characterized in that it comprises a duplicated OAMP in the IP to operate or maintain the function by operating or maintenance depending on the state of the redundant hub in conjunction with the CMS by the SNMP Redundancy system of devices. The method of claim 1, The redundant OAMP is a duplication management process for activating all applications by determining the activation side by sending and receiving a heartbeat message at regular intervals; An application process for delivering events and various statistical data of a system to the CMS by activating the redundancy management process, collecting various data required by the CMS through an internal database and other application programs, and delivering the data to the CMS; It includes a port management process that periodically checks the state of the redundant Ethernet ports and sets a representative IP address to an active Ethernet port so that applications always communicate through one IP address regardless of the state of the Ethernet port. Redundancy system of network devices between IP and CMS. Activating all applications by transmitting and receiving each other as a heartbeat message between the redundancy management processes at regular intervals; Assigning an IP address to the redundant Ethernet port, inspecting the state of the Ethernet port at a predetermined period, and setting a representative IP address according to the state of the Ethernet port; In the event of a failure of the Ethernet port by reporting the details of the failure of the Ethernet port in the inactive state by setting a representative IP-address comprising the process of performing the switchover to the inactive side, characterized in that the network between the IP and CMS Redundancy Method. The method of claim 3, Switching a deactivated hub to an activated state through a trunk when a hub in an activated state fails; Reporting the failure and setting a representative IP address to an Ethernet port in an inactive state, and performing a switchover to the hub side in the inactive state. . The method of claim 3, The method of redundancy between the IP and the CMS network device, characterized in that further comprising the step of routing the message through the hub in the inactive state by detecting the failure of the router in the active state.