KR20120002176A - Server for managing mpls vpn routing information and method thereof - Google Patents

Abstract

PURPOSE: An MPLS(Multi Protocol Label Switching) VPN(Virtual Private Network) routing information management server and method thereof are provided to effectively manage a present condition and address errors in real time by collecting MPLS VPN routing information through a BGP protocol. CONSTITUTION: A VRF(Virtual Routing Function) creation unit(111) searches routing information database. In case an RD(Route Distinguisher) is matched with other distinguisher, the VRF creation unit stores routing information in the RD group of the routing information DB(Data Base). When the RD is not matched any distinguisher, a department creation unit(113) stores the routing information by adding an entry to the VRF table of the routing information DB. The routing information DB(116) stores the routing information in which RD and RT(Route Target) are assorted.

Description

Server for managing MPLS VPN Routing Information and Method

The present invention relates to an MPLS VPN (Multi Protocol Label Switching Virtual Private Network) routing information management server and a method thereof. In particular, MPLS VPN routing information is collected and analyzed through a Border Gateway Protocol (BGP) protocol. The present invention relates to an MPLS VPN routing information management server and a method for managing address errors and status in real time.

1 is a view for explaining a conventional routing information management method. Referring to FIG. 1, in the conventional routing information management method, an LDP neighbor is formed by using a Generic Routing Encapsulation (GRE) tunnel when the management server interworks with a LDP (Label Distribution Protocol) in a service network. Therefore, a method of collecting and managing required MPLS-VPN routing information was used.

However, in the conventional routing information management method, each management server must form a GRE tunnel with all routers of the service network, and MPLS in the MIB (Management Information Base) table using the Simple Network Management Protocol (SNMP). -Because the VPN routing information is collected from the router in a polling manner, routing is not only complicated and difficult, but it also imposes a load on equipment (servers and routers) and also is vulnerable to security in obtaining a large amount of routing information. .

Accordingly, an object of the present invention is to solve the above-described problems, and an object of the present invention is to collect and analyze MPLS VPN routing information through a BGP protocol to effectively manage address error and status in real time. A server and a method thereof are provided.

First, to summarize the features of the present invention, MPLS VPN routing information management method in the management server for managing the routing information of the MPLS VPN, according to an aspect of the present invention for achieving the object of the present invention, a plurality of routers Forming a BGP neighbor with a central router and collecting routing information including an RD, an RT, and an IP address from the central router; And dividing the routing information into groups for each RD and dividing the routing information into a database based on RT in each group.

Client routers forming a neighbor only with the central router among the plurality of routers and interworking with the central router among the plurality of routers manage themselves by interworking with the management server through the central router using BGP. Redistribute VRF table information.

The updating of the routing information in a database may include: searching whether the same delimiter as the RD exists by referring to the database; And storing the routing information in a corresponding RD group according to the search result or adding an entry to the VRF table of the database by using the RD as a separator.

In the storing of the routing information, when a plurality of RTs of subscriber information mapped to the RD are referenced by referring to a database, a department code is generated in each RT and a region of a VRF table corresponding to the RD and the RT is distinguished. Storing the routing information.

Client routers interworking with the central router among the plurality of routers may add a RD information to an IP address using BGP and export routing information including RT designation information and a corresponding RT. And a router for importing routing information through the processing means.

The MPLS VPN routing information management method may further include generating alarm information when a change rate of the update number of the routing information for a predetermined period is larger than a reference.

According to another aspect of the present invention, the MPLS VPN routing information management server managing routing information of the MPLS VPN forms a BGP neighbor only with a central router among a plurality of routers to form RD, RT, and IP from the central router. A server for collecting routing information including an address, comprising: means for dividing the routing information into groups by RD and dividing the RTs in each group based on RT; And a first database for storing the routing information in which the RD and the RT are separated.

The means may include: a VRF generation unit for searching the first database and storing the routing information in a corresponding RD group of the first database when there is the same identifier as the RD; And a department generating unit for storing the routing information by adding an entry to the VRF table of the first database using the RD as a separator when there is no delimiter according to the search result.

The means includes a second database for storing subscriber information corresponding to RD and department information corresponding to RT; And an inquiry unit for inquiring whether the RT of the subscriber information mapped to the RD is plural by referring to the second database, wherein the department generating unit generates a department code in each of the plurality of RTs and corresponds to the corresponding RD and RT. The routing information is stored in the second database by dividing an area of the VRF table.

According to the MPLS VPN routing information management server and the method according to the present invention, by collecting and analyzing the MPLS VPN routing information through the BGP protocol to effectively manage the address error and status in real time, reducing the load on the equipment and effectively cope with security problems Is possible.

1 is a view for explaining a conventional routing information management method.
2 is a diagram for describing routing information including RD information and IP address according to an embodiment of the present invention.
3 is a diagram illustrating an MPLS VPN environment using MP-BGP according to an embodiment of the present invention.
4 is a diagram illustrating an MPLS VPN routing information management server according to an embodiment of the present invention.
5 is a flowchart illustrating the operation of the management server according to an embodiment of the present invention.
6 is a diagram for describing generation of a plurality of departments according to RD information according to an embodiment of the present invention.
7 is a block diagram of a management server 110 according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout.

First, since MPLS can be used to create 'virtual circuits' or 'tunnels' across an Internet Protocol (IP) network, IP service providers are introducing MPLS to provisioning VPN services. Some standards have been proposed that allow service providers to use MPLS as a provisioning VPN service to segregate customer traffic to IP networks and provide secure end-to-end access to customer sites.

Using MPLS for a VPN is an important advantage that can lead to further simplified traffic separation than Asynchronous Transfer Mode (ATM) or Frame Relay services. Since MPLS currently does not have any mechanism for packet encryption, it must be satisfied if customer requirements include encryption or require other methods such as IPsec. The best way to look at MPLS VPNs is to provide equivalent functionality to a frame relay or ATM virtual circuit.

There are various ways to use MPLS to provision IP-based VPNs. MPLS / BGP VPNs enable the implementation of MPLS-VPN by extending to Border Gateway Protocol (BGP). In this way, MPLS / BGP VPNs pass VPN-IPv4 information using BGP Multiprotocol Extensions (MP-BGP) to handle extended addresses, which are reachable between edge label switch routers (provider edge routers). (VPN-IPv4 address). Reachable information for a given VPN is only disseminated by other members of the VPN. Another way to create IP-VPNs using MPLS is to maintain separate routing tables for various virtual private networks in Network Based IP-VPN Architecture Using Virtual Routers, and not use BGP.

Recently, since a network operator provides a BGP-based VPN service, the present invention collects and analyzes MPLS VPN routing information using MP-BGP to effectively manage address errors and current conditions in real time, thereby reducing the load on equipment and preventing hacking. We propose a method and apparatus for managing MPLS-VPN routing information that can be effectively coped with.

MPLS provides two-layer forwarding using a label that is a logical identifier that can distinguish any stream instead of the conventional three-layer. The label has a meaning only in the corresponding node. The label switching router (LSR), which is a device used for label switching, performs packet forwarding by swapping the label. MPLS VPN configuration consists of Ingress Label Edge Router (LER), Core LSR, and Output LSR (LER).

To use a label, you have to assign and distribute the label. The protocol responsible for this function is the Label Distribution Protocol (LDP). LDP is a protocol composed of messages and procedures necessary for LSR to establish Label Switching Paths (LSPs) in a network in which three-layer routing information is directly mapped to a two-layer path. Looking at the network operation, a forwarding information base (FIB) table is created using existing IP routing protocols RIP, OSPF, BGP, etc., and then a packet information is forwarded based on a label information base (LIB) table by LDP. MPLS VPNs refer to a Label Information Base (LIB) to switch using MPLS labels. Since the LIB is basically based on the Forward Information Base (FIB), errors in routing information appear to be fundamentally an obstacle to label switching. Therefore, there is a need to monitor and manage errors of logical disability routing information of MPLS. In MPLS, however, logically importing all routing information can be loaded with SNMP or CLI (Command Line Interface). In addition, there is a method of collecting routing information using LDP, which creates a peer in only one hop, so to use LDP, a GRE tunnel or another tunneling protocol must be used. This has the disadvantage of complicated management and inconsistency in routing configuration.

In this patent, MP-BGP peer with a central router of VPN network is connected to receive routing information from MP-BGP peer.In this case, RT (Route Target) information, VPN-IPv4, which is a community extension of BGP, is configured. By classifying routing information by route distinguisher (RD), it is possible to efficiently manage routing information of each VPN subscriber.

2 is a diagram for describing routing information including RD information and IP address according to an embodiment of the present invention.

As shown in FIG. 2, RD is composed of 8-bytes including TYPE, ADM, and AN fields, and forms VPN-IPv4 routing information in front of 4-bytes of the IP address. The TYPE consists of 2 bytes and determines the length of the ADM and AN fields. ADM is an Administrator Field, which identifies an assigned number authority, and AN is an Assigned Number Field, which is assigned a number by the identified authority for a particular purpose. purpose). This is defined in the RFC4364-BGP / MPLS IP Virtual Private Networks document. The MPLS VPN consists of a Customer Edge (CE) router and a Provider Edge (PE) router. In MPLS VPN, PE router adds RD to routing (address) information generated by specific CE to make VPN-IPv4 routing information.

3 is a diagram illustrating an MPLS VPN environment using MP-BGP according to an embodiment of the present invention.

For example, as shown in FIG. 3, the PE router adds RD information (e.g., RD1 ..) to routing information (e.g., IP address of Net1 .., etc.) it owns, and the RT community. When information is specified and exported, other PE routers import the information through processing means designated by the corresponding RT information. In this case, RD is unique to most VPN subscribers, and RT can be filtered by a specific department divided into subscriber's area, branch office, and branch office. Accordingly, if the subscriber and department information corresponding to the RD is known in advance by the MPLS routing information management server 110, routing information may be provided by grouping according to the information.

4 is a diagram illustrating an MPLS VPN routing information management server 110 according to an embodiment of the present invention.

4, the management server 110 according to an embodiment of the present invention, TCP / IP (Transmission Control Protocol / Internet Protocol) only with the central router 120 (for example, a provider router) in the MPLS VPN By using the BGP neighbor (Neighbor) is formed to collect, update and efficiently manage all routing information. The client routers 130 (eg, PE routers or CE routers) may interwork with the management server 110 via the central router 120 using the BGP to update the routing information of the management server 110. Accordingly, the information of the Virtual Routing Function (VRF) table managed by the user is redistributed based on a predetermined policy. The client routers 130 may be one or more plurality of PE routers or CE routers.

The central router 120 relays the packet transmission and reception between the client routers 130. At this time, the management server 110 forming a neighbor with the central router 120 is an IP address routed by the client routers 130. Collect both RD information and RT information, including. The management server 110 stores the collected information in a database by using a predetermined processing means. At this time, the routing information (RD, RT, IP address, etc.) is divided into groups by RD and by RT in each group. Can be stored. At this time, code mapping of RD to VPN subscriber name, RT to department name, etc., and accordingly, it is possible to manage VPN routing information by subscriber and department in real time.

5 is a flowchart illustrating the operation of the MPLS VPN routing information management server 110 according to an embodiment of the present invention.

First, the management server 110 drives the collection process of MPLS to form a BGP (or MP-BGP) neighbor using a central router 120 (for example, a provider router) and TCP / IP. It may be (S510). The management server 110 can set the RT target to be received (import) as a whole, accordingly all VPN IP information (RD, RT, routing information that is updated (update) from the central router 120 through the MP-BGP) IP addresses, etc.) can be collected and updated in the database.

When VPN IP information (RD, RT, IP address, etc.) is collected, the management server 110 searches the database and checks whether there is a pre-stored same RD (the only delimiter in the VPN subscriber) (S520). If there is the same RD pre-stored in the routing information of the database, the management server 110 stores the routing information in a region separated by RT of the corresponding RD group of the database. In this case, when storing routing information, a date, time, traffic amount, and the like may be stored together. In addition, the routing information may be additionally stored without deleting the existing information so that the history of the routing information is updated.

If there is no identical RD previously stored in the routing information of the database in S520, the management server 110 adds an entry to the corresponding area of the RTF VR-delimited table of the corresponding RD group of the database by using the new RD as a delimiter. Can be stored (S530).

Here, the management server 110 can query the subscriber information (unique identifier in the VPN subscriber) mapped to the new RD with reference to the database (S540), and the department information based on the RT information of the database mapped to the new RD. Can be inquired (S550). When there are a plurality of RTs mapped to RD as shown in FIG. 6 (S560), the management server 110 generates a department code so that each department corresponds to each RT, and each department code corresponds to a corresponding department name (region, branch, branch, etc.). Name)) to be mapped (S570). After generating the department code in this way, the management server 110 updates the routing information (RD, RT, IP address, etc.) of the database by adding an entry by dividing the area of the VRF table corresponding to the RD and RT. It may be (S580). In this case, when storing routing information, a date, time, traffic amount, and the like may be stored together.

The management server 110 may provide the department information of the RT mapped to the RD based on the routing information (RD, RT, IP address, etc.) stored and managed in the database as described above. The management server 110 may periodically extract statistical information on the update count of the routing information corresponding to the RD or RT through the statistical process, and may manage the update history of the routing information. When there is a request from an operator or the like through a user interface or a request from another operator server, the management server 110 may provide the update history of the above statistical information or routing information in response to the request. In addition, the management server 110 calculates a change rate for the number of updates of the routing information corresponding to the RD or RT at regular intervals based on the above statistical information, and generates alarm information when the corresponding change rate for a certain period is greater than the reference The operator terminal may be notified to, for example, a user interface screen of the management server 110, a user interface screen of another server linked with the management server 110, or a mobile communication terminal.

7 is a block diagram of a management server 110 according to an embodiment of the present invention. 7, the management server 110 according to an embodiment of the present invention, VRF generation unit 111, inquiry unit 112, department generation unit 113, subscriber / department information database 115, And routing information database 116. Here, the VRF generation unit 111, the inquiry unit 112, and the department generation unit 113 stores the collected information in the routing information database 116, as shown in FIG. Corresponding to the main processing means of the management server 110 for storing the routing information (RD, RT, IP address, etc.) by dividing the RT based on each group in the routing information database 116. The server 110 may further include a processor that is in charge of overall control of each component. Each component of the management server 110 may be implemented in software, hardware, or a combination thereof.

The subscriber / department information database 115 may maintain subscriber information and department information. The subscriber / department information database 115 stores subscriber information (e.g., the name of a network operator such as KT) corresponding to RD, and department information (e.g., name of region, branch office, branch, etc.) corresponding to RT. Can be maintained. The routing information database 116 may maintain routing information (RD, RT, IP address, etc.). For example, a plurality of entries for routing information (RD, RT, IP address, etc.) may be stored and maintained in the VRF table of the routing information database 116.

The inquiry unit 112 may query the subscriber / department information database 115 to inquire subscriber information mapped to the RD, and the VRF generation unit 111 may route information about the routing information collected from the central router 120. If there is routing information for the same RD previously stored in the database 116, the collected routing information may be updated in the routing information database 116. In addition, when there is no routing information for the same RD previously stored in the routing information database 116 with respect to the routing information collected from the central router 120 according to the determination of the VRF generation unit 111, the inquiry unit 112 returns to the inquiry unit 112. If there are a plurality of RTs corresponding to the corresponding RD according to the inquiry of the subscriber / department information database 115 by the department, the department generating unit 113 generates a department code of the corresponding RT and the routing information database corresponding to the RD and the RT. An entry may be added to 116 to update corresponding routing information (RD, RT, IP address, etc.).

For example, the management server 110 drives the collection process of MPLS to establish a BGP (or MP-BGP) neighbor using a central router 120 (eg, a provider router) and TCP / IP. When forming, the VRF generation unit 111 may receive all VPN IP information (RD, RT, IP address, etc.) that is routing information collected from the central router 120 through the MP-BGP. The VRF generation unit 111 searches the routing information database 116 for the collection information (RD, RT, IP address, etc.) and checks whether there is a same RD previously stored. If there is the same RD pre-stored in the routing information maintained in the routing information database 116, the VRF generation unit 111 stores the corresponding routing information in a region separated by RT of the corresponding RD group of the routing information database 116. . In this case, when storing routing information, a date, time, traffic amount, and the like may be stored together. In addition, the VRF generation unit 111 may additionally store the corresponding routing information without deleting the existing routing information of the same RD so that the history of the routing information is updated.

If the VRF generation unit 111 determines that the routing information of the routing information database 116 has the same RD as the collected routing information, the inquiry unit 112 opens the subscriber / department information database 115. By referring to the subscriber information (unique information in the VPN subscriber) mapped to the new RD can be inquired, the department information can be inquired based on the RT information of the subscriber / department information database 115 mapped to the new RD.

In this case, when there are a plurality of RTs mapped to RD as shown in FIG. 6 according to the determination of the inquiry unit 112, the department generating unit 113 generates a department code so that each department corresponds to each RT, and each department code is Allows mapping to the department name (region, branch, branch, etc.). After generating the department code as described above, the department generating unit 113 divides the area of the VRF table corresponding to the RD and the RT and adds an entry to the VRF table of the routing information database 116 in such a manner as to add an entry. , RT, IP address, etc.). In this case, when storing routing information, a date, time, traffic amount, and the like may be stored together.

The management server 110 may provide the department information of the RT mapped to the RD based on the routing information (RD, RT, IP address, etc.) stored and managed in the database as described above. The management server 110 may periodically extract statistical information on the update count of the routing information corresponding to the RD or RT through the statistical process, and may manage the update history of the routing information. When there is a request from an operator or the like through a user interface or a request from another operator server, the management server 110 may provide the update history of the above statistical information or routing information in response to the request. In addition, the management server 110 calculates a change rate for the number of updates of the routing information corresponding to the RD or RT at regular intervals based on the above statistical information, and generates alarm information when the corresponding change rate for a certain period is greater than the reference The operator terminal may be notified to, for example, a user interface screen of the management server 110, a user interface screen of another server linked with the management server 110, or a mobile communication terminal.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains various modifications and variations from such descriptions. This is possible. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the claims below but also by the equivalents of the claims.

110: management server
120: central router
130: client routers
111: VRF generator
112: Views
113: department generating unit
115: subscriber / department information database
116: routing information database

Claims (9)

In the management server for managing routing information of MPLS VPN, MPLS VPN routing information management method,
Forming a BGP neighbor with a central router among a plurality of routers to collect routing information including RD, RT, and IP addresses from the central router; And
Dividing the routing information into groups for each RD, and dividing the routing information into a database based on RT in each group to update the routing information in a database.
MPLS VPN routing information management method comprising a. The method of claim 1,
Client routers forming a neighbor only with the central router among the plurality of routers and interworking with the central router among the plurality of routers manage themselves by interworking with the management server through the central router using BGP. MPLS VPN routing information management method characterized by redistributing VRF table information. The method of claim 1,
Updating the routing information in the database,
Searching whether there is the same delimiter as the RD by referring to the database; And
Storing the routing information in a corresponding RD group according to the search result or adding an entry to the VRF table of the database by using the RD as a separator;
MPLS VPN routing information management method comprising a. The method of claim 3,
The storing of the routing information may include:
When the RT of the subscriber information mapped to the RD is plural with reference to a database, generating the department code in each RT, and storing the routing information by dividing a region of the VRF table corresponding to the RD and the RT.
MPLS VPN routing information management method comprising a. The method of claim 1,
Client routers interworking with the central router among the plurality of routers may add a RD information to an IP address using BGP and export routing information including RT designation information and a corresponding RT. MPLS VPN routing information management method comprising a router for importing routing information through a processing means. The method of claim 1,
Generating alarm information when a change rate of the update number of the routing information for a predetermined period is greater than a reference;
MPLS VPN routing information management method further comprising. In the MPLS VPN routing information management server for managing routing information of the MPLS VPN,
A server that forms a BGP neighbor only with a central router among a plurality of routers to collect routing information including RD, RT, and IP addresses from the central router.
Means for dividing the routing information into RD groups and dividing the RTs based on RTs in each group; And
A first database for storing the routing information in which the RD and the RT are separated
MPLS VPN routing information management server comprising a. The method of claim 7, wherein
The means,
A VRF generation unit for searching the first database and storing the routing information in a corresponding RD group of the first database when there is the same identifier as the RD; And
If there is no delimiter equal to the RD according to the search result, the department generating unit for storing the routing information by adding an entry to the VRF table of the first database with the RD as a delimiter
MPLS VPN routing information management server comprising a. The method of claim 8,
The means,
A second database for storing subscriber information corresponding to RD and department information corresponding to RT; And
And an inquiry unit for inquiring whether RTs of subscriber information mapped to the RD are plural by referring to the second database,
The department generating unit generates a department code in each of a plurality of RTs, and separates the region of the VRF table corresponding to the RD and the RT and stores the routing information in the second database.

Images