KR101334459B1 - System and method for testing multicast distribution tree of multicast virtual private network - Google Patents

Abstract

The present invention discloses a system for testing a multicast distribution tree (MDT) configured in a multiprotocol label switching (MPLS) core network including a plurality of provider edges (PEs) and a test method thereof.

MDT test system of the present invention comprises a configuration information collection unit for detecting the configuration information change of the PE and collecting the changed configuration information; An MDT generation unit generating the MDT on a topology by using the collected configuration information; And a test unit configured to determine the failure of the MDT by analyzing a response result of the destination PEs of the PEs in response to the ICMP Echo message according to a test request from an operator. When the MDT is configured for the mVPN service in the MPLS core network, the verification of the MDT configuration work and the failure of the mVPN service can be easily and quickly performed by the operator.

Description

System and method for testing multicast distribution tree of multicast virtual private network

1 is a diagram showing the network configuration and flow of multicast traffic of mVPN to which the present invention is applied.

Figure 2 is a block diagram showing the configuration of a network of mVPN applied MDT test system according to the present invention.

3 is a flow chart for explaining the test method according to the invention.

DESCRIPTION OF THE REFERENCE NUMERALS

100: test system 110: configuration information collection unit

120: MDT generation unit 130: test unit

140: storage unit

The present invention relates to a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) network, and more specifically, to a multicast distribution tree (hereinafter referred to as mVPN) service in an MPLS VPN network. The present invention relates to a system for testing a failure and a test method thereof.

In line with the proliferation of high-speed Internet networks, fixed-line carriers are working to create new businesses based on the Internet.

As one of such efforts, the applicant, a wireline operator, is providing a VPN service for building an intranet or an extranet of an enterprise based on the MPLS network. Recently, multicast technology is applied to such a VPN service to enable broadcasting within a VPN. There is a demand to do so.

As such, mVPN is a technology that enables broadcasting within a VPN by applying a multicast technology to a VPN based on an MPLS network.

BGP / MPLS IP VPN (IETF RFC2547bis), a standard technology for VPN configuration in the MPLS core network, has a limitation that cannot provide a method for transmitting and controlling multicast traffic between VPN sites. Therefore, mVPN technology has been studied to solve such problems and is currently proposed as a draft-rosen-vpn-mcast-08 in IETF.

This standard describes protocols and procedures for transporting multicast traffic between VPN sites over existing BGP (Broader Gateway Protocol) / MPLS IP VPN networks, and has been adopted by major equipment vendors and applied to routers. .

1 is a diagram showing the network configuration and flow of multicast traffic of mVPN to which the present invention is applied.

When mVPN technology is applied to the existing MPLS core network, MDT as shown in FIG. 1 may be generated for each VPN, and thus multicast traffic may be transmitted. This will be described in more detail as follows.

When the multicast traffic is sent from the multicast source, the multicast traffic of the VPN subscribers flows into the MPLS core network through the CE (Customer Edge) -1 and PE (Provider Edge) -1 routers.

Since mVPN technology is applied to the MPLS core network, the MDT for the VPN is configured. Therefore, the incoming multicast traffic is transmitted to PE-2 and PE-3 through MDT, and then through CE-2 and CE-3, respectively. The destinations, hand signals 1 and 2, are reached.

The core of such mVPN management is MDT management generated for each VPN. To this end, first, the VPN-specific MDT topology should be visually displayed in the NMS (Network Management System) as shown in FIG. 1. This can be easily implemented by inquiring the configuration information of the PE router.

From the point of view of the operator, it is necessary to check whether the MDT topology appears in the NMS as set up by the PE router and to check whether the MDT topology has been configured for the normal flow of multicast traffic by ICMP (Internet Control Message Protocol) Echo message transmission. There is.

However, since the relationship between the source PE and the destination PE is 1: N and the destination PEs are not multicast hand signals, the MDT cannot receive the ICMP echo from the destination PEs. There is a problem that MDT does not know whether the environment in which multicast traffic flows properly is properly configured.

Accordingly, an object of the present invention for solving the above problems is to enable the operator to more easily and quickly identify the verification of the MDT configuration task and the failure of the mVPN service when configuring the MDT for the mVPN service.

MDT test system of the present invention for achieving the above object is a configuration information collection unit for detecting the configuration information changes of the PE and collecting the changed configuration information; An MDT generation unit generating an MDT on a topology using the collected configuration information; And a test unit configured to determine the failure of the MDT by analyzing a response result of the destination PEs of the PEs in response to the ICMP Echo message according to a test request from an operator. Equipped.

MDT test method of the present invention comprises a first step of collecting the changed configuration information when the configuration information of the PE changes; A second step of generating an MDT on a topology using the configuration information; A third step of configuring destination PEs among the PEs to respond to an ICMP Echo message according to a test request from an operator; Instructing a source PE designated by the operator to transmit the ICMP Echo message to the group address of the MDT; And a fifth step of analyzing a response result of the ICMP Echo message of the destination PEs to determine whether the MDT has failed.

Figure 2 is a block diagram showing the configuration of a network of mVPN applied MDT test system according to the present invention.

The configuration of Figure 2 is a multicast traffic to the MDLS generated in the MPLS core network and the MPLS core network including a plurality of PEs (PE-1, PE-2, PE-3) connected to the CE (not shown) of the subscriber network It is provided with a test system 100 for testing whether it can flow normally.

PEs (PE-1, PE-2, PE-3) have a multicast Virtual Routing and Forwarding Instance (VRF) (VRVR), which is a routing table created for each VPN for unicast and multicast traffic delivery. The received packets are forwarded to the destination CEs with reference. At this time, the mVRF is changed to match the set MDT when the MDT is set. In the MPLS core network, data exchange between PEs PE-1, PE-2, and PE-3 is already a common technology, and thus a detailed description thereof will be omitted.

The test system 100 monitors the configuration changes of the PEs PE-1, PE-2, and PE-3 and collects and collects the changed configuration information when the MDT is newly configured by the operator. The newly configured MDT is created on the topology using the configured configuration information. Next, the test system 100 determines the MTI (Multicast Tunnel Interface) of the destination PEs PE-2 and PE-3 in the newly configured MDT according to a test request from the operator. In the embodiment, 239.10.0.1) is used to configure the environment where the destination PEs PE-2 and PE-3 can respond to the ICMP Echo message. In addition, the test system 100 instructs the source PE (PE-1) designated by the operator to transmit the ICMP Echo message to the MDT group address and then analyzes the response result to determine whether the MDT has failed. At this time, the source PE (PE-1) is designated by the operator when the test request by the operator, the destination PE (PE-2, PE-2) are PEs other than the source PE (PE-1) of the PE of MDT Or at least one PE designated by the operator as the test subject.

The test system 100 includes a configuration information collecting unit 110, MDT generating unit 120, the test unit 130 and the storage unit 140.

The configuration information collecting unit 110 monitors configuration changes of the PEs (PE-1, PE-2, PE-3) included in the MPLS core network, detects the change, and collects the changed configuration information for each PE. Provided to the MDT generation unit 120.

The MDT generation unit 120 generates a newly constructed MDT on the topology by using the configuration information collected by the configuration information collecting unit 110 and displays it on the screen.

The test unit 130 joins the MTI of the destination PEs PE-2 and PE-3 to the MDT group address in the newly configured MDT according to a test request from the operator, and then sends the MDT group address to the source PE (PE-1). Instructs to send an ICMP echo message. Next, the test unit 130 analyzes the response results of the destination PEs PE-2 and PE-3 to the ICMP Echo message of the source PE PE-1 and displays the test results on the screen.

The storage 140 stores MTI information for the PEs PE-1, PE-2, and PE-3 and response messages from the MTIs of the destination PEs PE-2 and PE-3.

3 is a flowchart illustrating a test method according to the present invention.

The system operator logs into the PEs (PE-1, PE-2, PE-3) related to a specific VPN of the MPLS core network and performs tasks for MDT configuration. When the configuration information of 3) is changed, the configuration information collector 110, which monitors whether the configuration information of the PEs PE-1, PE-2, and PE-3 changes, detects the change and then converts the configuration information. That is, the MDT information newly configured by the operator is collected for each PE (step 310).

The collected configuration information is provided to the MDT generator 120, and the MDT generator 120 generates a newly configured MDT on the topology by using the configuration information and displays it on the screen (step 320).

When the MDT topology is displayed on the screen, the operator requests the test system 100 for an MDT test and selects one of the PEs on the MDT topology (PE-1) as the multicast source PE.

In response to a test request from the operator, the test unit 130 uses the MTI information of the storage unit 140, and PEs other than the source PE (PE-1) in the MDT (PE-2, PE-3: destination PE). By subscribing the MTI to the MDT group address via IGMP, a destination PEs (PE-2, PE-3) is configured to respond to the ICMP Echo message (step 330).

Next, the test unit 130 issues an ICMP echo message transmission command to the MDT group address (239.10.0.1) to the source PE (PE-1) so that the source PE (PE-1) is the MDT group address (239.10.0.1). The ICMP Echo message is transmitted (step 340).

Accordingly, in step 330, MTIs subscribed to the MDT group address respond to the ICMP Echo message from the source PE (PE-1).

The test unit 130 stores the response messages in the storage unit 140 when the response messages from the MTIs of the destination PEs PE-2 and PE-3 reach the source PE PE-1. When the response is completed, the test unit 130 compares the MTIs subscribed to the MDT group address with the MTIs in which the response message is normally received, finds the MTI that has not sent a response message, and displays information on the MTI and the MDT failure. Display (step 350).

If a response message is normally received from all MTIs, the MDT displays a screen indicating that there is no failure.

Next, the test unit 130 withdraws the MTI of the destination PE (PE-2, PE-3) from the MDT group address (step 360).

This is because if the MTIs of the destination PEs PE-2 and PE-3 remain subscribed to the MDT group address, they may cause unnecessary load on the PEs.

As described above, the MDT test system and method of the present invention allows the operator to more easily and quickly identify the verification of the MDT configuration task and the failure of the mVPN service when configuring the MDT for the mVPN service in the MPLS core network. .

Claims (8)

A system for testing a multicast distribution tree (MDT) configured in a multiprotocol label switching (MPLS) core network including a plurality of provider edges (PEs), A configuration information collection unit for detecting a configuration information change of the PEs and collecting the changed configuration information; An MDT generation unit generating the MDT on a topology by using the collected configuration information; And According to a test request from an operator, the destination PEs among the PEs may be configured to respond to the ICMP Echo message, and then the test unit may be configured to determine whether the MDT has failed by analyzing the response results of the ICMP Echo messages of the destination PEs. and, And the test unit joins the Multicast Tunnel Interface (MTI) of the destination PEs to an MDT group address so that the destination PEs can respond to the ICMP Echo message. delete The method of claim 1, wherein the test unit The operator instructs the designated source PE to transmit the ICMP Echo message to the MDT group address, and analyzes whether the MDT has failed by analyzing whether to respond to the ICMP Echo message from MTIs subscribed to the MDT group address. MDT test system, characterized in that judging. The method of claim 1 or 3, wherein the test unit MDT test system, characterized in that withdrawal of the MTI of the destination PE to the MDT group address when the determination of the failure of the MDT is completed. A method for testing a multicast distribution tree (MDT) configured in a multiprotocol label switching (MPLS) core network including a plurality of provider edges (PEs), A first step of collecting the changed configuration information when the configuration information of the PEs is changed; A second step of generating the MDT on a topology using the configuration information; A third step of configuring destination PEs among the PEs to respond to an ICMP Echo message according to a test request from an operator; Instructing a source PE designated by the operator to transmit the ICMP Echo message to the group address of the MDT; And And analyzing a response result of the destination PEs to the ICMP Echo message to determine whether the MDT has failed. The third step is to join the multicast tunnel interface (MTI) of the destination PE to the MDT group address. delete The method of claim 5, wherein the fifth step MDT test method, characterized in that the failure of the MDT comparing the MTI subscribed to the MDT group address and the MTI transmitted the response message to the ICMP Echo message. The method according to claim 5 or 7, And a sixth step of withdrawing the MTI of the destination PEs to the MDT group address when the determination of the failure of the MDT is completed.

Images