KR102376484B1 - Apparatus and method for automatic switching of duplication lines - Google Patents

Abstract

Disclosed are an apparatus and method capable of automatically switching redundant lines when a line failure occurs without STP domain interworking in providing a virtual private network service by connecting customer network equipment separated from each other through a redundant line. Network equipment constituting a redundant line for connecting customer network equipment spaced apart from each other according to an embodiment includes: an event generator for detecting the occurrence of a failure by monitoring the state of ports and generating an event according to the detected failure; a policy management unit that determines whether to process the event based on a policy; And receiving the event determined to be processed by the policy management unit, according to the received event, for the redundant network equipment of the large station, includes an event processing unit for controlling the port connected to the customer network equipment.

Description

Apparatus and method for automatic switching of redundant lines

The present invention relates to a virtual private network structure, and more particularly, to an apparatus and method for automatic switching of redundant lines constituting a virtual private network.

A telecommunication service provider provides a dedicated line through transmission network equipment, or provides a virtual private network (VPN) service through IP router equipment to connect corporate networks that are separated from each other via public networks such as the Internet. The virtual private network is composed of a Provider Edge (PE), which is a network equipment between the telecommunication service providers, and a Customer Edge (CE, Customer Edge), which is a network equipment of a corporate customer connected to the provider edge. The PE uses a tunneling technology such as IPSEC, MPLS, or VxLAN to deliver the traffic received from the CE to the large PE. The virtual private network can be classified into L2VPN, L3VPN, etc. as the connected customer's CE is connected based on L2 or L3.

The telecommunication service provider copes with CE-PE section failure by constructing a redundant line between CE and PE. At this time, the loop-free structure is automatically created by logically blocking one section of the line for the loop constructed via the PE by transmitting and receiving STP (Spanning Tree Protocol) messages between CEs. will make up If a failure occurs in the forwarding line for which blocking is not detected, the blocked line automatically switches to the forwarding state through the STP algorithm, so that the service continues even in the event of failure.

In this way, the telecommunication service provider can cope with the CE-PE section failure through the redundant line configuration, but if the STP domains are not interworking in the L2VPN network, the L2VPN service may not be provided due to a loop. In addition, in the case of some new tunneling technologies such as VxLAN recently, it may not be possible to configure a topology in which loops are eliminated because STP domain interworking is not essential.

The present invention provides an apparatus and method for automatically switching redundant lines when a line failure occurs without STP domain interworking in providing a virtual private network service by connecting customer network equipment spaced apart from each other through a redundant line. There is a purpose.

Another object of the present invention is to provide an apparatus and method capable of preventing an infinite loop from occurring when a specific line failure occurs in switching redundant lines.

Network equipment constituting a redundant line for connecting customer network equipment spaced apart from each other according to an embodiment includes: an event generator for detecting the occurrence of a failure by monitoring the state of ports and generating an event according to the detected failure; a policy management unit that determines whether to process the event based on a policy; And receiving the event determined to be processed by the policy management unit, according to the received event, for the redundant network equipment of the large station, includes an event processing unit for controlling the port connected to the customer network equipment.

The policy management unit determines that the interlink failure event is unprocessed, and processes the interlink failure event when a failure occurs in all interlinks with the internal redundant network equipment and the state of the port connected to the customer network equipment of the own equipment is in an active state. can decide

The event processing unit may switch, based on the interlink failure event, a port connected to a customer network equipment of a large power network equipment configuring the same line as the own equipment to an active state, and switch the redundant network equipment of the large station to an inactive state. .

The policy management unit, if a failure occurs in all of the duplicated links of the customer network equipment and the state of the port connected to the customer network equipment is in an active state, the customer failure event is unprocessed, and in an inactive state, it can be processed .

The event processing unit, based on the customer failure event, the port connected to the customer network equipment of the large power network equipment that configures the same line as the own equipment to an active state, the redundant network equipment of the large power can be switched to an inactive state .

The method for switching redundant lines of network equipment constituting a redundant line connecting customer network equipment spaced apart from each other according to an embodiment includes the steps of monitoring the status of ports to detect the occurrence of a failure, and generating an event according to the detected failure ; determining whether to process the event based on a policy; And according to the event determined to be processed, for the redundant network equipment of the large country, comprising the step of controlling the port connected to the customer network equipment.

In the determining step, if a failure occurs in all interlinks with the redundant network equipment in the home country and the state of the port connected to the customer network equipment of the own equipment is in the active state, the interlink failure event is determined not to be processed, and in the case of inactive state It may include the step of determining the process.

In the controlling step, based on the interlink failure event, the port connected to the customer network equipment of the large power network equipment configuring the same line as the own equipment is switched to an active state, and the redundant network equipment of the large station is switched to an inactive state may include.

In the determining step, if a failure occurs in all of the duplicated links of the customer network equipment and the state of the port connected to the customer network equipment is active, the customer failure event is unprocessed, and if it is inactive, the process is determined may include steps.

In the controlling step, based on the customer failure event, switching the port connected to the customer network equipment of the large power network equipment configuring the same line as the own equipment into an active state, and switching the redundant network equipment of the large country to an inactive state may include.

The present invention can provide a stable virtual private network service by automatically switching lines when a line failure occurs in an L2VPN in which an STP domain is not interlocked.

In addition, the present invention can provide a stable virtual private network service by preventing an infinite loop from occurring in the redundant line when all interlinks between the redundant provider edges within the same office office fail.

In addition, the present invention can provide a stable virtual private network service by preventing an infinite loop from occurring in the redundant line when a failure occurs in the redundant link at the customer's edge.

1 is a diagram illustrating a virtual private network structure according to an embodiment of the present invention.
FIG. 2 is a diagram for explaining a circuit switching method when a node failure occurs in PE#2-2 in FIG. 1 .
3 is a diagram illustrating a structure of a virtual private network according to another embodiment of the present invention.
FIG. 4 is a diagram for explaining a circuit switching method when a failure occurs in a link between PE#2-2 and CE#2 in FIG. 1 .
5 is a diagram illustrating a structure of a virtual private network according to another embodiment of the present invention.
6 is a diagram illustrating a configuration of a network device according to an embodiment of the present invention.
7 is a flowchart illustrating a duplex switching method of a network device according to an embodiment of the present invention.
8 is a flowchart illustrating a duplex switching method of a network device according to another embodiment of the present invention.

The above-described objects, features, and advantages will become more apparent through the following detailed description in relation to the accompanying drawings, whereby those of ordinary skill in the art to which the present invention pertains can easily implement the technical idea of the present invention. There will be. In addition, in the description of the present invention, if it is determined that a detailed description of a known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, a preferred embodiment according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a virtual private network structure according to an embodiment of the present invention. Telecommunication service providers provide a virtual private network (VPN) service that allows them to connect to a corporate network via a public network. 1 shows an example of such a virtual private network structure. Referring to FIG. 1 , the virtual private network structure is a network equipment of a telecommunication operator section, which is a Provider Edge (PE, Provider Edge) 102 to 106 and network equipment of a corporate customer connected to the corresponding provider edge 102 to 106. In Customer Edge (CE, Customer Edge) (101, 104) is configured to include. PEs 102 to 106 use a tunneling technology such as IPSEC or MPLS, VxLAN, etc. to deliver the traffic received from the CEs 101 and 104 to the large PE. Because it uses tunneling technology, there is no concern that the customer's traffic is exposed on the public network, so security can be enhanced. The virtual private network may be classified into L2VPN, L3VPN, etc. as the connected customer's CEs 101 and 104 are connected based on L2 and L3. The CEs 101 and 104 and the PEs 102 to 106 may be L3 switches or network equipment performing similar roles.

Referring to FIG. 1 , sites of a corporate customer may be geographically separated, and CE#1 101 and CE#2 104 are respectively located at the two sites in this embodiment. Duplicated PE#1-1(102) and PE#1-2(103) are located in the communication service provider office on the CE#1 (101) side, and the redundant PE# 2-1 (105) and PE#2-2 (106) are located. Accordingly, the lines between CE#1 (101) and CE#2 (104) spaced apart from each other are duplicated. PE#1-1 (102) and PE#2-1 (105) constitute the same line, and PE#1-2 (103) and PE#2-2 (106) constitute a different line and are duplicated. In accordance with the occurrence of a failure, the duplicated line is automatically switched over by the PE (102~106).

In this embodiment, when the CEs 101 and 104 are connected to the PEs 102 to 106, they are connected in a multi-homing manner, that is, in a redundant manner. In case of multi-homing, user traffic can be delivered normally even when one of the connected PEs 102 to 106 is stopped or a corresponding link fails in the CEs 101 and 104. Each PE 102-106 stores homing port information connected to the CEs 101 and 104 of other PEs participating in the VPN line. For example, PE#1-1 (102), homing port information for CE#2 (104) of PE#2-1 (105) constituting the same line located in the game, located in the diagonal, That is, homing port information for CE#2(104) of PE#2-2(106) that constitutes another duplicated line, and CE#1( 101) to store the homing port information. Each PE 102 to 106 can communicate with each other based on IP through a separate management network or a tunneled IP interworking section, and stores management network IP information for other PEs. For example, PE#1-1 (102) tables the access IP addresses (Loopback, etc.) for PE#2-1 (105), PE#1-2 (103), and PE#2-2 (106). pre-configured and saved. In the embodiment of FIG. 1 , the homing ports connected to CEs 101 , 104 of PE#1-2 103 and PE#2-2 106 are Up, ie, active, and PE#1-1 102 ) and the homing ports connected to CEs 101 and 104 of PE#2-1 105 are Down, that is, inactive. Accordingly, CE#1 (101) and CE#2 (104) transmit/receive packets through line A composed of PE#1-2 (103) and PE#2-2 (106). At this time, a node failure 120 may occur in PE#2-2 106 .

FIG. 2 is a diagram for explaining a circuit switching method when a node failure occurs in PE#2-2 106 in FIG. 1 . Referring to FIG. 2 , PE#2-1(105), which is a redundant equipment located in the same office as PE#2-2(106), connects two interlinks with PE#2-2(106) to a health check line use it as Therefore, when the failure of the equipment itself of PE#2-2 (106) occurs, that is, when both of these interlinks are down, in step S202, PE#2-1 (105) has a node failure in PE#2-2 (106). detect what has happened Accordingly, in step S230, PE#2-1 (105) makes a Telnet or SSH connection to PE#1-2 (103) to up, that is, CE#1 (101) of PE#1-2 (103) in the active state. ) of the homing port down, that is, make it inactive. Accordingly, CE#1101 detects the down, that is, inactive state of the homing port for CE#1101 of PE#1-2(103), and stops traffic transmission. In addition, in step S240, PE#2-1 (105) makes a Telnet or SSH connection to PE#1-1 (102) to set the homing port for CE#1 (101), which is in Down state, to Up state, that is, active. switch to state Accordingly, the CE#1101 detects that the homing port connected to the PE#1-1102 is switched to the Up state and starts traffic delivery through the PE#1-1102.

On the other hand, PE#1-1 (102) whose homing port for CE#1 (101) is in an Up state, that is, in an active state, establishes Telnet or SSH connection to PE#2-2 (106) in step S250. Thus, the homing port for the CE#2 104 in the Up state, that is, the active state, is switched to the Down state, that is, the inactive state. In addition, in step S260, PE#1-1 (102) makes a Telnet or SSH connection to PE#2-1 (105) to set the homing port for CE#2 (104), which is in Down state, to Up state, that is, active. switch to state Accordingly, in step S270 , CE#2 104 switches the traffic to PE#2-1 105 upon detecting that the homing port of PE#2-1 105 is Up, that is, in an active state.

Therefore, in conclusion, the line (A in Fig. 1) connected to CE#1(101), PE#1-2(103), PE#2-2(106), and CE#2(104) is, CE#1( 101), PE#1-1 (102), PE#2-1 (105), and CE#2 (104) are transferred to the line (B in FIG. 2).

1 and 2, the PEs 102 to 106 themselves control homing ports of other connected PEs when a node failure occurs without exchanging STP (Spanning Tree Protocol) messages between the CEs 101 and 104. so that the circuit is switched. In the case of interworking with conventional STP domains, line switching takes 30 seconds or longer because mutual STP messages must be exchanged. However, according to the present embodiment, line switching can be performed within a few seconds.

In the embodiment with reference to FIGS. 1 and 2 above, the occurrence of node failure of PE#2-2 (106) is taken as an example. The embodiment with reference to FIGS. 1 and 2 has one drawback. That is, if a failure occurs in all interlinks between PE#2-2 (106) and PE#2-1 (105), rather than the failure of PE#2-2 (106) itself, PE#2-1 (105) is determined as a node failure of PE#2-2 (106), and PE#2-2 (106) is determined as a node failure of PE#2-1 (105). Accordingly, PE#2-1 (105) switches the homing port for CE#1 (101) of PE#1-2 (103) to Down, that is, to an inactive state, while the CE# of PE#1-1 (102) Turns the homing port for 1 (101) Up, i.e., active, and conversely, PE#2-2 (106) turns the homing port for CE 101 of PE#1-1 (102) Down, i.e., inactive. While transitioning to the state, the homing port for CE#1 (101) of PE#1-2 (103) is switched to Up, that is, to an active state. Accordingly, the active/inactive states of each of the PEs 102 to 106 are crossed, and an infinite loop may occur, and all lines may become inactive. Therefore, it is necessary to prevent an infinite loop from occurring when a failure occurs in the interlink between duplicated PEs within the same office. This will be described in detail below.

3 is a diagram illustrating a structure of a virtual private network according to another embodiment of the present invention. In the embodiment with reference to FIG. 3 , elements of the same reference numerals as those shown in FIG. 1 include the functions and operations described with reference to FIG. 1 . However, when an interlink failure event occurs between duplicated PEs located within the same office, the operation of the PE is different from the operation and function described with reference to FIG. 1 .

As shown in FIG. 3 , the SDN (Software Defined Network) controller 310 is each PE 102 to 106 of a communication service provider when a failure event occurs in both interlinks between duplicated PEs located within the same office office. Set by sending a policy regarding the operation of the PE. The policy here includes two things. One is a semi-synchronization policy that anti-synchronizes the status of the homing ports of the duplicated PEs 102 to 106 in the same office company. For example, if the status of the homing port of PE#1-1 (102) is Down, the status of the homing port of PE#1-2 (103) is Up, which is the opposite. On the other hand, when an interlink failure event occurs between duplicated PEs located within the same office, the PEs 102 to 106 where the event occurred check whether the status of the homing port for the CEs 101 and 104 is Down, that is, inactive. And, the event processing operation only when in the inactive state, that is, controlling the homing ports of PEs of the large country, and in the active state, the event processing operation is not performed.

More specifically, referring to FIG. 3 , in step S301, a failure occurs in all interlinks between PE#1-1 102 and PE#1-2 103 within the same office company. After generating an interlink failure event, PE#1-1 (102) and PE#1-2 (103) determine whether to perform an event processing operation with reference to the policy. That is, the PE#1-1 (102) checks the status of the homing port for the CE#1 (101). In the present embodiment, since it is Down, that is, it is in an inactive state, an event processing operation is performed. On the other hand, PE#1-2 (103) checks the status of the homing port for CE#1 (101), but does not perform an event processing operation because it is Up, that is, an active state.

Accordingly, in step S302, PE#1-1 (102) makes a Telnet or SSH connection to PE#2-1 (105) and is down, that is, CE#2 (104) of PE#2-1 (105) in an inactive state. ) to Up, i.e., make the homing port active. Also, in step S303, PE#1-1 (102) makes a Telnet or SSH connection to PE#2-2 (106) to up, that is, CE#2 (104) of PE#2-2 (106) in an active state. ) of the homing port down, that is, make it inactive.

On the other hand, PE#2-1 (105) whose homing port for CE#2 (104) has been switched to the Up state, that is, to the active state, establishes Telnet or SSH connection to PE#1-1 (102) in step S304. This makes the homing port for the CE#1 (101) of the PE#1-1 (102) in the Down, that is, the inactive state, the Up, that is, the active state. In addition, in step S305, PE#2-1 (105) makes a Telnet or SSH connection to PE#1-2(103) to up, that is, CE#1(101) of PE#1-2(103) in an active state. ) of the homing port down, that is, make it inactive.

According to the above policy, the infinite loop described with reference to FIGS. 1 and 2 is solved.

FIG. 4 is a diagram for explaining a circuit switching method when a failure occurs in the link between PE#2-2 (106) and CE#2 (104) in FIG. 1 . Here, the link failure may include a port failure of the CE#2 104 or a failure of the node itself of the CE#2 104 . Referring to FIG. 4 , in step S410 , PE#2-2 106 detects a failure in the link between CE#2 104 . CE#2 (104) also detects the occurrence of a failure. Therefore, traffic transmission from PE#2-2 (106) to CE#2 (104) is stopped.

Therefore, in step S402, PE#2-2 (106), by Telnet or SSH connection to PE#1-1 (102) of the large country, the homing port for the CE#1 (101) in the Down state to the Up state, That is, it switches to the active state. Accordingly, CE#1 (101) detects that the homing port connected to PE#1-1 (102) is switched to the Up state. In addition, PE#2-2 (106), in step S403, Telnet or SSH connection to PE#1-2 (103), the homing port for CE#1 (101) in the up state down state, that is, inactive switch to state Accordingly, CE#1 (101) detects that the homing port connected to PE#1-2 (103) is switched to the Down state.

On the other hand, PE#1-1 (102) in which the homing port for CE#1 (101) is in the Up state, that is, in the active state, in step S404, Telnet or SSH to the PE#2-1 (105) of the large country After accessing, the homing port for CE#2 (104), which is in the Down state, is switched to the Up state, that is, the active state. Accordingly, CE#2 (104) detects that the homing port connected to PE#2-1 (105) is switched to the Up state. In addition, in step S405, PE#1-1 (102) makes a Telnet or SSH connection to PE#2-2 (106) and turns the homing port for CE#2 (104) in an Up state in a down state, that is, inactive. switch to state Accordingly, CE#2 (104) detects that the homing port connected to PE#2-2 (106) is switched to the Down state.

According to the embodiment with reference to FIG. 4 above, when a failure occurs in the link between the PEs 102 to 106 and the CEs 101 and 104, the PEs 102 to 106 access a remote PE through a process defined by themselves and access the CE By controlling the homing port for (101, 104), traffic can be delivered normally. In the case of interworking with conventional STP domains, line switching takes 30 seconds or longer because mutual STP messages must be exchanged. However, according to the present embodiment, line switching can be performed within a few seconds.

However, the embodiment with reference to FIG. 4 has one disadvantage. That is, when a link failure between PE#2-2 (106) and CE#2 (104) and a link failure between PE#2-1 (105) and CE#2 (104) occur at the same time, the implementation with reference to FIG. According to the example process, PE#2-1 105 transitions the homing port for CE 101 of PE#1-2 103 to Up, i.e., active state while the CE of PE#1-1 102 The homing port for #1 (101) is called Down, that is, inactive, and in contrast, PE#2-2 (106) raises the homing port for CE 101 of PE#1-1 (102) to Up, that is, While switching to the active state, the homing port for the CE#1 (101) of the PE#1-2 (103) is turned down, that is, the inactive state is switched. Accordingly, the active/inactive states of each of the PEs 102 to 106 are crossed, and an infinite loop may occur, and all lines may become inactive. Therefore, it is necessary to prevent an infinite loop from occurring when the redundant links of the customer's CEs 101 and 104 simultaneously fail. This will be described in detail below with reference to FIG. 5 .

5 is a diagram illustrating a structure of a virtual private network according to another embodiment of the present invention. In the embodiment with reference to FIG. 5 , elements of the same reference numerals as those shown in FIG. 4 include the functions and operations described with reference to FIG. 4 . However, when a failure occurs simultaneously in the duplicated links of the CEs 101 and 104, the operation of the PE is different from the operation and function described with reference to FIG. 4 .

As shown in Figure 5, the SDN (Software Defined Network) controller 510 to each PE (102 to 106) of the communication operator when a failure event occurs simultaneously in the two duplicated links of the CE (101, 104) of the PE Set the policy by sending it. The policy here includes two things. One is a semi-synchronization policy that anti-synchronizes the status of the homing ports of the duplicated PEs 102 to 106 in the same office company. For example, if the status of the homing port of PE#1-1 (102) is Down, the status of the homing port of PE#1-2 (103) is up, which is the opposite. On the other hand, when a failure event occurs in the duplicated link of CE(101, 104), the PE(102~106) where the event occurred checks whether the status of the homing port for the CE(101, 104) is Down, that is, inactive. And, only in the case of inactive state event processing operation, that is, controlling the homing ports of large stations and duplicated PEs, and in the active state, event processing operation is not performed.

More specifically, referring to FIG. 5, in step S501, a failure occurs in the duplicated link of CE#2 (104). That is, a failure occurs in the link between PE#2-1 (105) and CE#2 (104), and in the link between PE#2-2 (106) and CE#2 (104). After generating a failure event, PE#2-1 (105) and PE#2-2 (106) determine whether to perform an event processing operation with reference to the policy. That is, PE#2-1 (105) checks the status of the homing port for CE#2 (104). In the present embodiment, since it is Down, that is, it is in an inactive state, an event processing operation is performed. On the other hand, PE#2-2 106 checks the status of the homing port for CE#2 104, but does not perform an event processing operation because it is Up, that is, an active state.

Accordingly, in step S502, PE#2-1 (105) makes a Telnet or SSH connection to PE#1-1 (102) and is down, that is, CE#1 (101) of PE#1-1 (102) in an inactive state. ) to Up, i.e., make the homing port active. In addition, in step S503, PE#2-1 (105) makes a Telnet or SSH connection to PE#1-2(103) to up, that is, CE#1(101) of PE#1-2(103) in the active state. ) of the homing port down, that is, make it inactive.

On the other hand, the homing port for CE#1 (101) is in an Up state, that is, PE#1-1 (102) switched to an active state, in step S504, Telnet or SSH to PE#2-1 (105) of the other country After accessing, the homing port for CE#2 (104), which is in the Down state, is switched to the Up state, that is, the active state. In addition, in step S505, PE#1-1 (102) makes a Telnet or SSH connection to PE#2-2 (106) and turns the homing port for CE#2 (104) in an Up state in a down state, that is, inactive. switch to state

According to the above policy, the infinite loop described with reference to FIG. 4 is solved.

6 is a diagram illustrating a configuration of a network device according to an embodiment of the present invention. The network equipment, as an L3 switch, includes a memory and a processor, an x86-based operating system identical to that of a commercial server is installed in the memory, and an application for switching and routing is installed above the operating system. In addition, network equipment can be controlled based on user scripts by supporting applications (telnet, ssh, etc.) and shell programming (Bash and Python, etc.) provided by existing Linux, etc. with an x86-based structure. In addition, the network equipment supports the programmable API, so that it is possible to monitor the port and resource information of the network equipment based on a user script, etc. Referring to FIG. 6 , the network device includes an event generating unit 601 , a policy management unit 602 , and an event processing unit 603 , which may be implemented as applications, stored in a memory, and executed by a processor.

The event generator 601 monitors the status of ports of the network equipment, detects the occurrence of a failure in the port, and generates an event according to the detected failure. For example, the event generator 601 detects a failure of the redundant network equipment, a link failure with the redundant network equipment, or a link failure with a customer network equipment, and generates an event according to the detected failure. The event may include the location of the failure, the type of failure, and the like.

The policy management unit 602 receives and stores the policy from the SDN controllers 310 and 510 . The policy management unit 602, according to the semi-synchronization policy included in the received policy, manages the state of the port connected to the customer network equipment of the network equipment in reverse to the state of the redundant network equipment. For example, if the state of the port connected to the customer network equipment of the redundant network equipment is Down, the policy management unit 602 sets the state of the port connected to the customer network equipment of the present network equipment to Up.

Also, the policy management unit 602 receives the event generated by the event generating unit 601 and determines whether to process the received event according to the received policy. Here, the policy is a policy in case all interlinks with the redundant network equipment fail, or when a failure occurs in all redundant links of the customer network equipment. It is transmitted to the event processing unit 603 only when the state of is Down, that is, inactive. Therefore, the policy management unit 602, for an event that occurs because all interlinks with the redundant network equipment fail or a failure occurs in the redundant link of the customer network equipment, the state of the homing port connected to the customer network equipment is Down. That is, in an inactive state, it is transmitted to the event processing unit 603 for processing, and in an active state, it is not transmitted. The policy management unit 602 transmits other events to the event processing unit 603 .

The event processing unit 603 processes the event received from the policy management unit 602 . Specifically, the event processing unit 603 controls the homing port connected to the customer network equipment for the network equipment of the large country. The event processing unit 603 is, in the state that the homing port of the own device is down, the failure of the redundant network equipment in the home country, the failure of all interlinks with the redundant network equipment in the home country, or the failure of both links of the customer network equipment In the case of a disability, the homing port of the network equipment of the player is switched to the Up state, and the diagonal network equipment of the player is switched to the state of Down. Alternatively, the event processing unit 603, when the homing port of the own equipment is switched from the Down state to the Up state, switches the homing port of the network equipment of the counterpart to the Up state, and the diagonal network equipment of the counterpart is switched to the Down state. .

7 is a flowchart illustrating a duplex switching method of a network equipment according to an embodiment of the present invention, and is a flowchart when a failure occurs in all interlinks with the duplex network equipment in the home country.

Referring to FIG. 7 , in step S701, the network equipment generates an event according to the failure of the interlink used to check the status of the redundant network equipment in the local station. In step S702, the network equipment checks whether the state of the homing port connected to the customer network equipment is Down, that is, inactive, before processing the generated event.

If the Down state, that is, the inactive state, in step S703, the network device makes a Telnet or SSH connection to the large power equipment to change the state of the homing port connected to the customer network equipment to Up, that is, the active state. In addition, in step S704, the network equipment makes a Telnet or SSH connection to the diagonal equipment of the large country and switches the state of the homing port connected to the customer network equipment to Down, that is, to an inactive state.

8 is a flowchart illustrating a duplex switching method of a network equipment according to another embodiment of the present invention, and is a flowchart when a failure occurs in all duplexed links of a customer network equipment.

Referring to FIG. 8 , in step S801, the network equipment generates an event according to failure of all duplicated links of the customer network equipment. In step S802, the network equipment checks whether the state of the homing port connected to the customer network equipment is Down, that is, inactive, before processing the generated event.

If it is in the Down state, that is, the inactive state, in step S803, the network device makes a Telnet or SSH connection to the large power equipment to change the state of the homing port connected to the customer network equipment to the Up, that is, an active state. In addition, in step S804, the network equipment makes a Telnet or SSH connection to the diagonal equipment of the large country and switches the state of the homing port connected to the customer network equipment to Down, that is, to an inactive state.

While this specification contains many features, such features should not be construed as limiting the scope of the invention or the claims. Also, features described in individual embodiments herein may be implemented in combination in a single embodiment. Conversely, various features described herein in a single embodiment may be implemented in various embodiments individually, or may be implemented in appropriate combination.

Although acts are described in a particular order in the drawings, it should not be understood that the acts are performed in the particular order as shown, or that all of the described acts are performed in a continuous order, or to obtain a desired result. . Multitasking and parallel processing can be advantageous in certain circumstances. In addition, it should be understood that the division of various system components in the above-described embodiments does not require such division in all embodiments. The program components and systems described above may generally be implemented as a package in a single software product or multiple software products.

The method of the present invention as described above may be implemented as a program and stored in a computer-readable form in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.). Since this process can be easily performed by a person skilled in the art to which the present invention pertains, it will not be described in detail any longer.

The present invention described above, for those of ordinary skill in the art to which the present invention pertains, various substitutions, modifications and changes are possible within the scope without departing from the technical spirit of the present invention. It is not limited by the drawings.

102, 103, 105, 106 : PE
101, 104: CE
310, 510: SDN controller
601: event generator
602: policy management department
603: event processing unit

Claims (11)

In the network equipment for configuring a redundant line by connecting the customer network equipment separated from each other through the domestic redundant network equipment and the redundant network equipment of the large country,
an event generator for detecting the occurrence of a failure by monitoring the status of the ports and generating an event according to the detected failure;
a policy management unit that determines whether to process the event based on a policy; and
Network equipment comprising an event processing unit for receiving an event determined to be processed by the policy management unit, and controlling a port connected to a customer network equipment for the duplicated network equipment of the large station according to the received event. The method of claim 1,
The policy management unit,
When a failure occurs in all interlinks with the internal redundant network equipment and the state of the port connected to the customer network equipment of the own equipment is in an active state, the interlink failure event is determined not to be processed, and in an inactive state, it is determined to be processed network equipment with 3. The method of claim 2,
The event processing unit,
Network equipment, characterized in that, based on the interlink failure event, the port connected to the customer network equipment of the large power network equipment configuring the same line as the own equipment is switched to an active state, and the redundant network equipment of the large country is switched to an inactive state. The method of claim 1,
The policy management unit,
Network equipment, characterized in that if a failure occurs in all of the duplicated links of the customer network equipment and the status of the port connected to the customer network equipment is active, the customer failure event is not processed, and if it is inactive, the network equipment is determined . 5. The method of claim 4,
The event processing unit,
Network equipment, characterized in that, based on the customer failure event, the port connected to the customer network equipment of the large power network equipment configuring the same line as the own equipment is switched to an active state, and the redundant network equipment of the large country is switched to an inactive state. In the duplex line switching method of network equipment that forms a duplex line by connecting customer network equipment spaced apart from each other through duplex network equipment in the home country and duplicate network equipment in a large country,
detecting the occurrence of a failure by monitoring the status of the ports, and generating an event according to the detected failure;
determining whether to process the event based on a policy; and
In accordance with the event determined to be processed, the method comprising the step of controlling the port connected to the customer network equipment for the redundant network equipment of the large country. 7. The method of claim 6,
The determining step is
If a failure occurs in all interlinks with the internal redundant network equipment and the state of the port connected to the customer network equipment of the own equipment is in the active state, the interlink failure event is unprocessed, and in the inactive state, the decision to be processed; A method comprising: 8. The method of claim 7,
The controlling step is
Based on the interlink failure event, switching a port connected to a customer network equipment of a large power network equipment configuring the same line as the own equipment to an active state and switching the redundant network equipment of the large power to an inactive state How to. 7. The method of claim 6,
The determining step is
When a failure occurs in all of the redundant links of the customer network equipment and the state of the port connected to the customer network equipment is active, the customer failure event is determined not to be processed, and when it is inactive, it is determined to be processed. how to do it with 10. The method of claim 9,
The controlling step is
Based on the customer failure event, switching the port connected to the customer network equipment of the large power network equipment configuring the same line as the own equipment to an active state, comprising the step of switching the redundant network equipment of the large power to the inactive state, characterized in that How to. A computer program recorded on a recording medium as a computer program for executing the method according to any one of claims 6 to 10 through a computer system.

Images