CN1960366A - Cross-domain connection method of label exchange virtual dedicated network in multiprotocol - Google Patents
Cross-domain connection method of label exchange virtual dedicated network in multiprotocol Download PDFInfo
- Publication number
- CN1960366A CN1960366A CNA2005101009127A CN200510100912A CN1960366A CN 1960366 A CN1960366 A CN 1960366A CN A2005101009127 A CNA2005101009127 A CN A2005101009127A CN 200510100912 A CN200510100912 A CN 200510100912A CN 1960366 A CN1960366 A CN 1960366A
- Authority
- CN
- China
- Prior art keywords
- boundary router
- router
- neighbours
- multiprotocol
- label
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The method comprises: starting label distribution protocol between autonomic system edge routers; using the layer-2 label to switch traffic; starting MPBGP protocol between autonomic system edge routers, and using non direct connection address to build MPBGP neighbor; on the autonomic system edge routers, configuring the non direct address routing protocol pointing to the domain of opposite side, and shielding other routes being needless. In the invention, the LDP and MPBGP neighbors are built between ASBRs by using non direct connection address so as to use lower layer routing protocol to implement load balance and route backup.
Description
Technical field
The present invention relates to the router technology field in the communication network, refer more particularly to the cross-domain interconnection technique field of three-layer VPN.
Background technology
VPN (VPN (virtual private network)) business is one of telecommunication service of new generation of tool potentiality.Realize that based on the Multi-Protocol Label Switch (MPLS) network technology of VPN improved the defective of traditional IP greatly, can provide the fail safe the same to guarantee simultaneously again, adapted to the demand of vpn service well with the frame relay/atm network.Traditional IP network is all carried out the 3rd layer route querying at each routing node, and the time-delay of total capaciated flow network is bigger; Traditional IP network can't provide good fail safe for user's private network; Traditional network QOS do neither be very good.The appearance of MPLS technology is fine to be solved these problems, and the especially release of MPLS VPN can provide abundant business to the user on IP network.Each telecommunications producer all in the product of oneself, has increased the support to MPLS VPN, to adapt to the variation that telecommunication market develops rapidly.
When making up MPLS VPN network, often need to cross over a plurality of autonomous systems, even cross over a plurality of different operators.At this time the problem that need consider of the MPLS VPN of Kua Yueing is just many, mainly contains following Several Factors:
1, whether the route of autonomous system domains leaks mutually;
2, stride the how route of switched vpc N of autonomous system;
3, to the influence of the other side's autonomous system how cross-domain MPLS VPN.
Each top problem all needs careful consideration and research.The route of switched vpc N between different operators how, do not influence the normal route calculation of the other side's autonomous system, in other words the other side is produced minimum influence, three kinds of cross-domain connection methods of three-layer VPN introduced in one piece of article on the juniper website " BGP/MPLS VPN Hierarchical and RecursiveApplications ", and describe the exchanged form of label in detail.
Wherein, the connected mode of second kind of leap is on the border router of two cross-domain connections (ASBR), uses the address of direct-connected interface to set up MP-EBGP neighbours, comes the label of switched vpc N.The deficiency of this mode maximum is that the interface of setting up MP-EBGP neighbours is relied on very much.Can not normally move if set up this interface, will cause the failure of cross-domain MPLS VPN.Especially can not handle following situation flexibly:
The router of two cross-domain connections (representing with ASBR-A and ASBR-B respectively), the ASBR-A router has two interface A1, and A2 is connected respectively to the B1 of ASBR-B router, the B2 interface.ASBR-A router and ASBR-B router have two interconnected circuit (A1-B1 like this, A2-B2), if on the circuit of A1-B1, pass through two straight chain interface A1 of router, B1 sets up the neighbours of cross-domain MP-EBGP, when the A1-B1 line failure, overstate that the ASBR-A in territory and ASBR-B MPLS-VPN just can't operate as normal, though this time A2-B2 the circuit operate as normal.
Summary of the invention
Technical problem to be solved by this invention is: solve in the prior art, set up cross-domain connection to the problem that the interface of setting up MP-EBGP neighbours relies on very much, propose a kind of new connected mode.
Technical scheme of the present invention is to go up the route that adopts MP-BGP (MPBGP) and tag distribution protocol (LDP) switched vpc N at Autonomous System Boundary Router, AS Boundary Router (ASBR).
Particularly, can may further comprise the steps:
Step 1, between Autonomous System Boundary Router, AS Boundary Router (ASBR), enable tag distribution protocol (LDP agreement), adopt two-layer label to come switching traffic;
Step 2, between Autonomous System Boundary Router, AS Boundary Router (ASBR), enable the MPBGP agreement, adopt the indirectly connected address of Autonomous System Boundary Router, AS Boundary Router to set up MPBGP neighbours;
Step 3, point to the Routing Protocol of the indirectly connected address in the other side territory, shield other unwanted routes in Autonomous System Boundary Router, AS Boundary Router configuration.
We are compared with prior art bright, following advantage:
1, adopt indirectly connected address (as LOOPBACK) to set up LDP and MPBGP neighbours between the ASBR, more unified with the LDP MPBGP configuration style of other routers in the entire domain.
2, ASBR sets up MPBGP LDP neighbours by indirectly connected address, can use the Routing Protocol of lower floor to realize load balancing and route backup.
Description of drawings
Fig. 1 is the most basic networking diagram in the cross-domain connected mode of a kind of VPN;
Fig. 2 is to be the label distribution process schematic diagram of example with the concrete route of certain bar among Fig. 1;
Fig. 3 is to be the flow transport process schematic diagram of example with the concrete route of certain bar among Fig. 1.
Embodiment
In the present invention, if two routers all move MPBGP in same autonomous system, claim that the MPBGP between these two routes is MP-IBGP (a multi-protocols Internal BGP); If two routers claim that at different autonomous system operation MPBGP the MPBGP that moves between these two routers is MP-EBGP.
As shown in Figure 1, concrete connected mode is as follows:
1, R1 (PE1) and R2 (ASBR1) set up MP-IBGP neighbours, and the vpn label of the VPN of R1 is exchanged to R2; R1 (PE1) and R2 (ASBR1) are in same territory.
R1 router and R2 router are served as the functional role difference in Fig. 1 as follows:
The R1 router is a pe router, is responsible for three-layer VPN user's access; The R1 router is the router in the autonomous system domains, does not generally set up MP-EBGP and LDP neighbours with other autonomous systems router outward.
The R2 router is a core router, the forwarding capability of responsible three-layer VPN only, not responsible three-layer VPN user's access; The R2 router is the router of striding autonomous system domains, and router general and other autonomous system is set up MP-EBGP and LDP neighbours.
Pe router (supplier's border router) is responsible for the access of three-layer VPN on function.The function of representing this router to serve as with PE is also refered in particular to the router of serving as the three-layer VPN access function traditionally.
2, set up LDP neighbours between R1 (PE1) and R2 (ASBR1), the LDP agreement will be set up the outer layer label path from R1 (PE1) to R2 (ASBR1).
3, R4 (PE2) and R3 (ASBR2) set up MP-IBGP neighbours, and the vpn label of the VPN of R4 is exchanged to R3; R4 (PE2) is in another different territory with R3 (ASBR2).
4, set up LDP neighbours between R4 (PE2) and the R3 (ASBR2), the LDP agreement will be set up the outer layer label path from R4 (PE2) to R3 (ASBR2).
5, R2 (ASBR1) and R3 (ASBR2) are increased to the route of the indirectly connected address of the other side mutually, as increasing the static routing of pointing to the other side loopback address.
6, between R2 (ASBR1) and R3 (ASBR2), pass through indirectly connected address,, set up the neighbours of MP-EBGP as the loopback address.
7, set up LDP neighbours between R2 (ASBR1) and the R3 (ASBR2), as on direct-connected circuit (fa0/0-fa0/0) open the LDP agreement.
Fig. 2 is a label distribution process schematic diagram, and the process of distribution label is:
1, R1 distributes outer layer label and distributes vpn label to MPBGP neighbours R2 to adjacent LDP neighbours;
2, R2 is to adjacent MP-EBGP and LDP neighbours R3 distribution vpn label and outer layer label;
3, R3 distributes outer layer label and vpn label to adjacent LDP and MP-IBGP neighbours R4.
After connecting according to above-mentioned connected mode, the mode that cross-domain VPN flow transmits as shown in Figure 3:
1, because next jumping that ASBR1 announces to the VPN route of PE1 is ASBR1 itself, cross-domain the arrivals PE2 router VPN flow that PE1 sets out exchanges arrival ASBR1 according to outer layer label.
2, outer layer label was ejected after packet arrived ASBR1, only remaining vpn label, ASBR1 directly searches three-layer VPN vpn label route, finds next to jump (loopback of the other side ASBR2), and then searches route and the label of the loopback of the other side ASBR2 according to next jumping.
3, the vpn label that finds according to step 2 exchanges to the other side ASBR2 to the three-layer VPN flow, thereby finishes cross-domain process.
Claims (5)
1, a kind of cross-domain connection method of label exchange virtual dedicated network in multiprotocol, the route of employing MPBGP and tag distribution protocol secure virtual private network on Autonomous System Boundary Router, AS Boundary Router.
2, the described cross-domain connection method of label exchange virtual dedicated network in multiprotocol of claim 1 is characterized in that,
Step 1, between Autonomous System Boundary Router, AS Boundary Router, enable tag distribution protocol, adopt two-layer label to come switching traffic;
Step 2, between Autonomous System Boundary Router, AS Boundary Router, enable the MPBGP agreement, adopt the indirectly connected address of Autonomous System Boundary Router, AS Boundary Router to set up MPBGP neighbours;
Step 3, point to the Routing Protocol of the indirectly connected address in the other side territory, shield other unwanted routes in Autonomous System Boundary Router, AS Boundary Router configuration.
3, the described cross-domain connection method of label exchange virtual dedicated network in multiprotocol of claim 2, it is characterized in that, set up MP-IBGP neighbours and tag distribution protocol neighbours between two routers in same territory, the Autonomous System Boundary Router, AS Boundary Router of same area is not enabled Routing Protocol, learn the route of the indirectly connected address of the other side, and set up neighbours and the tag distribution protocol neighbours of MP-EBGP by indirectly connected address.
4, claim 2 or 3 described cross-domain connection method of label exchange virtual dedicated network in multiprotocol is characterized in that, described indirectly connected address is meant the lookback address.
5, the described cross-domain connection method of label exchange virtual dedicated network in multiprotocol of claim 3 is characterized in that, described Routing Protocol is that static routing protocol also can be a dynamic routing protocol.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005101009127A CN100571264C (en) | 2005-10-31 | 2005-10-31 | A kind of cross-domain connection method of label exchange virtual dedicated network in multiprotocol |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005101009127A CN100571264C (en) | 2005-10-31 | 2005-10-31 | A kind of cross-domain connection method of label exchange virtual dedicated network in multiprotocol |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1960366A true CN1960366A (en) | 2007-05-09 |
CN100571264C CN100571264C (en) | 2009-12-16 |
Family
ID=38071857
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB2005101009127A Active CN100571264C (en) | 2005-10-31 | 2005-10-31 | A kind of cross-domain connection method of label exchange virtual dedicated network in multiprotocol |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN100571264C (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101127723B (en) * | 2007-09-24 | 2010-12-01 | 中兴通讯股份有限公司 | QoS guarantee method for multi-protocol tag exchange L3 virtual private network |
CN101552710B (en) * | 2008-03-31 | 2011-04-06 | 中国移动通信集团公司 | Method, system and router for realizing virtual special network cross-domain |
CN101340372B (en) * | 2008-08-21 | 2012-09-19 | 中国移动通信集团公司 | Number automatic routing method, updating method, eliminating method, router and equipment |
CN112787935A (en) * | 2016-02-01 | 2021-05-11 | 华为技术有限公司 | VPN route notification method, data flow forwarding method and related equipment |
CN113630324A (en) * | 2021-08-10 | 2021-11-09 | 中电积至(海南)信息技术有限公司 | Novel cross-domain interconnection method based on MPLS-VPN |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040059829A1 (en) * | 2002-09-24 | 2004-03-25 | Chu Thomas P. | Methods and devices for converting routing data from one protocol to another in a virtual private network |
CN1254059C (en) * | 2002-12-10 | 2006-04-26 | 华为技术有限公司 | Method of realizing special multiple-protocol label exchanging virtual network |
US6970464B2 (en) * | 2003-04-01 | 2005-11-29 | Cisco Technology, Inc. | Method for recursive BGP route updates in MPLS networks |
-
2005
- 2005-10-31 CN CNB2005101009127A patent/CN100571264C/en active Active
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101127723B (en) * | 2007-09-24 | 2010-12-01 | 中兴通讯股份有限公司 | QoS guarantee method for multi-protocol tag exchange L3 virtual private network |
CN101552710B (en) * | 2008-03-31 | 2011-04-06 | 中国移动通信集团公司 | Method, system and router for realizing virtual special network cross-domain |
CN101340372B (en) * | 2008-08-21 | 2012-09-19 | 中国移动通信集团公司 | Number automatic routing method, updating method, eliminating method, router and equipment |
CN112787935A (en) * | 2016-02-01 | 2021-05-11 | 华为技术有限公司 | VPN route notification method, data flow forwarding method and related equipment |
CN112787935B (en) * | 2016-02-01 | 2022-12-06 | 华为技术有限公司 | VPN route notification method, data flow forwarding method and related equipment |
CN113630324A (en) * | 2021-08-10 | 2021-11-09 | 中电积至(海南)信息技术有限公司 | Novel cross-domain interconnection method based on MPLS-VPN |
Also Published As
Publication number | Publication date |
---|---|
CN100571264C (en) | 2009-12-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1938997B (en) | Method, connection controller and system for differential forwarding in address-based carrier networks | |
CN100558111C (en) | Metro Ethernet provides reliability processing method and the system under the multi-service networking | |
CN100450039C (en) | Fast convergence method and device of the end-to-end service | |
US7894450B2 (en) | Implementation of VPNs over a link state protocol controlled ethernet network | |
US7693979B2 (en) | Traffic fencing mechanism for control plane enabled networks | |
US8199755B2 (en) | Method and apparatus establishing forwarding state using path state advertisements | |
CN102037685B (en) | IP forwarding across a link state protocol controlled Ethernet network | |
CN102325073B (en) | A kind of message processing method based on VPLS and device thereof | |
US20070177597A1 (en) | Ethernet connection-based forwarding process | |
US20040255028A1 (en) | Functional decomposition of a router to support virtual private network (VPN) services | |
US20060047851A1 (en) | Computer network with point-to-point pseudowire redundancy | |
Ali et al. | Traffic engineering in metro ethernet | |
US20030026209A1 (en) | Avoiding overlapping segments in transparent lan services on ring-based networks | |
EP2183887A1 (en) | Layer 2 virtual private network over pbb-te/pbt and seamless interworking with vpls | |
US20050141504A1 (en) | Methods, systems, and computer program products for encapsulating packet traffic associated with multiple layer two technologies | |
CN101667954A (en) | Network of multilayer virtual private LAN (local area network) service and data processing method thereof | |
CN1960366A (en) | Cross-domain connection method of label exchange virtual dedicated network in multiprotocol | |
US20040025054A1 (en) | MPLS/BGP VPN gateway-based networking method | |
CN107645446A (en) | A kind of information determines method and apparatus | |
US20130077473A1 (en) | Protection switching method and system for a multi-rooted point-to- multi-point service in a provider backbone bridge (pbb) network | |
CN102394804A (en) | VPN system building method and VPN system | |
CN1529456A (en) | Multi-business united network platform | |
CN102377645A (en) | Exchange chip and realization method thereof | |
CN102571449B (en) | The switching method and device of link | |
EP1650898A1 (en) | Packet switch network link |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant |