CN102882797A - VPNv4 or VPNv6 route batch deleting method and PE (Provider Edge) - Google Patents
VPNv4 or VPNv6 route batch deleting method and PE (Provider Edge) Download PDFInfo
- Publication number
- CN102882797A CN102882797A CN2012103924816A CN201210392481A CN102882797A CN 102882797 A CN102882797 A CN 102882797A CN 2012103924816 A CN2012103924816 A CN 2012103924816A CN 201210392481 A CN201210392481 A CN 201210392481A CN 102882797 A CN102882797 A CN 102882797A
- Authority
- CN
- China
- Prior art keywords
- private network
- route
- network tags
- vpnv6
- vpnv4
- 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
Abstract
The invention discloses a VPNv4 or VPNv6 route batch deleting method. The method comprises the following steps of: acquiring at least one private network tag by a first PE (Provider Edge) router; for each private network tag in the private network tag, encapsulating a route cancelling message containing the private network tag and sending the route cancelling message to a second PE, wherein the route cancelling message is used for triggering the second PE according to the private network tag in the route cancelling message; and in a VPNv4 or VPNv6 route table, deleting all VPNv4 or VPNv6 routes which adopt the private network tag as an output tag, wherein the second PE is a VPNv4 or VPNv6 neighbor of a BGP (Border Gateway Protocol) of the first PE. The invention also discloses the provider edge router PE. The load of the PE equipment and a network can be reduced, and the performance of the network can be improved.
Description
Technical field
The application relates to the route withdraw technical field, relates in particular to delete in batches method and the provider edge router (PE) of VPNv4 or VPNv6 route.
Background technology
Multiprotocol label switching (mpls) is that the core router utilization contains the label (label) of the forward direction information that edge router provides or a kind of exchanged form that mark (tag) is realized network layer (3 layers) exchange in IP grouping, it provides a kind of mode, the IP address is mapped as the label that simply has regular length, is used for different bags and transmits and packet technology.MPLS L3VPN is a kind of Layer3 Virtual Private Network based on provider edge router (PE) (L3VPN) technology in service provider's VPN(Virtual Private Network) solution, it uses Border Gateway Protocol (BGP) in service provider backbone issue VPN route, uses multiprotocol label switching (mpls) to transmit the VPN message at service provider backbone.
BGP VPNv4(is VPN-IPv4 at present, virtual private network internet agreement the 4th edition) or VPNv6(be VPN-IPv6, virtual private network internet agreement sixth version) cancelling of route be with reference to BGP IPv4(Internet protocol the 4th edition) or BGP IPv6(Internet protocol sixth version) flow process of route withdraw.When the link communication that occurs between PE and the CE breaks down, BGP VPNv4 or VPNv6 neighbours are broken or during PE local deletion VPN route forwarding table (VRF) operation, local end PE equipment need to encapsulate all routing iinformations that down hop is broken route withdraw (withdrawn routes) messages and send to BGP VPNv4 or the VPNv6 neighbours of described PE, local end PE is designated as a PE, BGP VPNv4 or the VPNv6 neighbours of described local end PE are designated as the 2nd PE, the route withdraw message carries all VPNv4 or the VPNv6 routing iinformation that down hop is broken, network between the one PE and the 2nd PE need to transmit these update information, the 2nd PE need to resolve these update information, the VPNv4 or the VPNv6 routing iinformation that extract among the withdrawn routes are cancelled, and processing like this can be to a PE, network between the 2nd PE and a PE and the 2nd PE all brings very large instantaneous pressure.
Here take the L3VPN networking as example, as shown in Figure 1, in the L3VPN networking, Customer Edge router CE sets up syntople with a PE who directly links to each other, and CE is distributed to a PE to the VPN route of this website, and acquires the route of far-end VPN from a PE; Use BGP or IGP(Interior Gateway Protocol between CE and the PE) exchanging routing information, also can use static routing; After the one PE acquires the VPN routing iinformation of CE this locality from CE, by BGP and the 2nd PE switched vpc Nv4 routing iinformation.Pe router is only safeguarded the routing iinformation of the VPN that directly links to each other with it, all the VPN routes in the not maintenance service provider network; Operator backbone router P only is maintained into the route of PE, does not need to understand any VPN routing iinformation.
When the link communication between a PE and the CE breaks down, the one PE need to send the message of cancelling of all routes that down hop breaks, in other network of carrier-class, the VPNv4 of the one PE station maintenance or VPNv6 route quantity are very huge, that is to say that when the private network interface breaks the cost that sends route withdraw message is very large.For example, if 1,000,000 VPNv4 or VPNv6 route are arranged need be cancelled, the one PE needs constantly group bag, until all be encapsulated into these 1,000,000 VPNv4 or VPNv6 routing iinformation in the route withdraw message and send it to the 2nd PE, carry 1,000,000 VPNv4 or VPNv6 routing iinformation in the described route withdraw message, network between the one PE and the 2nd PE need to transmit these update information, after the 2nd PE receives update information, need to resolve these update information, 1,000,000 VPNv4 or the VPNv6 routing iinformation that extract among the withdrawn routes are cancelled, and this processes for a PE, the instantaneous pressure of network is very large between the 2nd PE and a PE and the 2nd PE.
Summary of the invention
In view of this, the application proposes the method for a kind of batch deletion VPNv4 or VPNv6 route, can alleviate the burden of PE equipment and network, improves network performance.
The application proposes a kind of provider edge router (PE) simultaneously, can alleviate the burden of PE equipment and network, improves network performance.
For achieving the above object, the technical scheme of the embodiment of the present application is achieved in that
The method of a kind of batch deletion VPNv4 or VPNv6 route may further comprise the steps:
The first provider edge router PE obtains at least one private network tags, and for each private network tags in the described private network tags, encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE; VPNv4 or the VPNv6 neighbours of the Border Gateway Protocol (BGP) that described the 2nd PE is a PE;
Described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
A kind of provider edge router (PE) comprising: label acquisition module, message package module and packet sending and receiving module; Wherein,
The label acquisition module is used for obtaining at least one private network tags;
The message package module is used for each private network tags for described private network tags, and encapsulation contains the route withdraw message of this private network tags;
The packet sending and receiving module, the route withdraw message after being used for encapsulating is sent to the 2nd PE, and the 2nd PE is VPNv4 or the VPNv6 neighbours of the Border Gateway Protocol (BGP) of described provider edge router PE; Described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and in VPNv4 or VPNv6 routing table, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label.
The application's beneficial effect is, when the link communication between PE and the CE break down or PE between the BGPVPNv4 Routing Protocol break or during the local deletion of PE VRF table, PE takes full advantage of BGP VPNv4 or the VPNv6 neighbours PE` that effective private network tags is come packaging V PNv4 or VPNv6 route withdraw message and sent to this PE, PE` utilizes the private network tags in the described route withdraw message, delete in batches VPNv4 or VPNv6 route, can greatly alleviate the burden of PE equipment and network, improve network performance.
Description of drawings
Fig. 1 is the Layer3 Virtual Private Network networking structure schematic diagram of prior art;
Fig. 2 is the method flow diagram of the embodiment of the present application one;
Fig. 3 is the optional capability class parameter format schematic diagram of the embodiment of the present application;
Fig. 4 is the method flow diagram of the embodiment of the present application two;
Fig. 5 is the method flow diagram of the embodiment of the present application three;
Fig. 6 is the cross-domain networking structure schematic diagram of the OptionB class of prior art;
Fig. 7 is the method flow diagram of the embodiment of the present application four;
Fig. 8 is the PE functions of the equipments structural representation of the embodiment of the present application.
Embodiment
In order to make purpose of the present invention, technical scheme and advantage clearer, below by specific embodiment and referring to accompanying drawing, the present invention is described in detail.
Among the application, the one PE and the 2nd PE be BGP VPNv4 or VPNv6 neighbours each other, the one PE obtains at least one private network tags, and for each private network tags in the described private network tags, encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE; Described route withdraw message is used for triggering the 2nd PE according to the private network tags of described route withdraw message, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table, namely trigger described the 2nd PE and resolve described route withdraw message, extract in the described route withdraw message private network tags and with it as index, in VPNv4 or VPNv6 routing table, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label.That is to say, use a route withdraw message that contains above-mentioned private network tags, just can delete in batches VPNv4 or VPNv6 route, thereby can greatly reduce because send PE equipment and the offered load that too much route withdraw message causes.
The method flow of the embodiment of the present application one as shown in Figure 2, the method for a kind of batch deletion VPNv4 or VPNv6 route may further comprise the steps:
Step 201: the first provider edge router (PE) obtains at least one private network tags.
The private network tags here is that a PE this locality is distributed, and obtains private network tags and divides three kinds of scenes, is:
Scene 1: in the Layer3 Virtual Private Network as shown in Figure 1, when the link communication between a PE and the Customer Edge router (CE) breaks down, the one PE inquiry down hop is whether the private network tags of described CE has other forwarding equivalence class FEC to use, if, then a PE sends the route withdraw message to the 2nd PE, and described route withdraw message carries all VPNv4 or the VPNv6 routing iinformation that down hop is described CE.If not, then obtain described private network tags.
Scene 2: when the BGP VPNv4 between a PE and the 3rd PE or VPNv6 Routing Protocol broke, a PE obtained private network tags, and described private network tags is for entering one to one label with outgoing label from the 3rd PE; Wherein, a PE can carry out the private network tags exchange, and the 3rd PE is BGP VPNv4 or the VPNv6 neighbours of a PE and is different from the 2nd PE.The 3rd PE and a PE can be in same territory, also can be cross-domain.
Scene 3: when a PE local deletion VPN route forwarding table (VRF), obtain all private network tags that described VRF distributes.
The back can enumerate three embodiment for these three kinds of scenes and specify: be respectively how to obtain private network tags in each scene, and how utilize the private network tags of obtaining to delete in batches VPNv4 or VPNv6 route.
As preferred embodiment, under above-mentioned three kinds of scenes, after the one PE obtains at least one private network tags, also can utilize described private network tags to delete in batches VPNv4 or the VPNv6 route of a PE this locality, namely a PE with the described private network tags of obtaining as index, in the VPNv4 or VPNv6 routing table of a PE this locality, delete with described private network tags as the whole VPNv4 that enter label or VPNv6 route.
Step 202: a PE is for each private network tags in the described private network tags, and encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE; The 2nd PE is Border Gateway Protocol (BGP) VPNv4 or the VPNv6 neighbours of a PE.
The described route withdraw message that contains this private network tags is divided into two types, be VPNv4 route withdraw message and VPNv6 route withdraw message, include following field: the unreachable information prefix length of multi-protocols (MP unreach NLRI Prefix length, be called for short " prefix length "), the unreachable information labels stack of multi-protocols (MP unreach NLRI Label Stack, be called for short " label stack "), the unreachable information router sign of multi-protocols (MP unreach NLRI Route Distinguisher, be called for short " Route Distinguisher "), the unreachable information IPv4 of multi-protocols or IPv6 route prefix (MP unreach NLRI IPv4/IPv6Prefix is called for short " IPv4 or IPv6 route prefix ");
If described route withdraw message is VPNv4 route withdraw message, the signal field is as shown in table 1 below:
| MP unreach NLRI Prefix length(prefix length) | 120 |
| MP unreach NLRI Label Stack(label stack) | Label |
| MP unreach NLRI Route Distinguisher(Route Distinguisher) | 0:0 |
| MP unreach NLRI IPv4/IPv6Prefix(IPv4 or IPv6 route prefix) | 255.255.255.255 |
Table 1
As known from Table 1, the value of label stack is above-mentioned private network tags after the encapsulation, the IPv4 route prefix is 255.255.255.255, and prefix length is 120, is the length of 32 route masks of IPv4, Route Distinguisher is self-defining value, can establish arbitrary value, just passable as long as a PE and the 2nd PE consult, such as being made as 0:0 or 100:0, show it is VPNv4 or VPNv6 route, add that before IPv4 or IPv6 address it has been VPNv4 or VPNv6 address that Route Distinguisher just shows.
If described route withdraw message is VPNv6 route withdraw message, the signal field is as shown in table 2 below:
Table 2
As can be seen from Table 2, the value of label stack is above-mentioned private network tags after the encapsulation, and the IPv6 route prefix is FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, and prefix length is 216, be the length of 64 route masks of IPv6, Route Distinguisher is self-defining value.
In the existing route withdraw message, the label stack field contents is in disarmed state all the time, and such as being set to 0 or maximum, what IPv4 or IPv6 route prefix were inserted is effective IPv4 or IPv6 address.
In the application's the route withdraw message, what the label stack field was inserted is effective private network tags, the application utilizes this effective private network tags to realize deleting in batches VPNv4 or VPNv6 route just, what IPv4 or IPv6 route prefix were inserted is disabled IPv4 or IPv6 address, such as, the IPv4 address 255.255.255.255 that inserts, or IPv6 address FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, when resolving the route withdraw message, the back can use these disabled IPv4 or IPv6 address.
Step 203: trigger described the 2nd PE according to the private network tags in the described route withdraw message by the route withdraw message, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
After the 2nd PE receives route withdraw message from a PE, private network tags in the described route withdraw message is resolved and extracted to described route withdraw message, process is as follows:
For VPNv4 route withdraw message, if Route Distinguisher RD is 0:0, judge whether that RD is that 0:0 and IPv4 address are: 255.255.255.255, judge that namely whether the VPNv4 address is: 0:0255.255.255.255, if so, then extract private network tags in the described VPNv4 route withdraw message.
Here actual is to determine first that the IPv4 address is disabled, then just can go to read private network tags, if the IPv4 address is available, has just deleted according to existing procedure, is exactly to have deleted route according to described available IPv4 address.
For VPNv6 route withdraw message, if Route Distinguisher RD is 0:0, judge whether that RD is that 0:0 and IPv6 address are: FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, judge namely whether the VPNv6 address is 0:0FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, if so, then extract private network tags in the described VPNv6 route withdraw message.
If above-mentioned judgement for VPNv4 or VPNv6 route withdraw message is no, be that the VPNv4 address is not: Route Distinguisher 255.255.255.255, or the VPNv6 address is not: Route Distinguisher FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, then according to original flow process deletion VPNv4 or VPNv6 route, namely delete item by item VPNv4 or VPNv6 route according to the IPv4 in the route withdraw message or IPv6 route prefix, rather than delete in batches with private network tags.
The 2nd PE carries out extracting private network tags after the analysis judgment to VPNv4 or the VPNv6 route withdraw message that a PE sends, with described private network tags as index, in the VPNv4 or VPNv6 routing table of the 2nd PE, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label.
Preferably, before step 201, in BGP OPEN message, add in advance the optional capability class parameter of supporting to delete in batches with private network tags VPNv4 or VPNv6 route;
Before a PE and the 2nd PE set up BGP VPNv4 or VPNv6 neighbours, the one PE sends the BGPOPEN message, after a PE received the BGP OPEN message that described the 2nd PE sends, the optional capability class of supporting according to the optional capability class parameter of carrying in the described OPEN message that receives and a PE this locality carried out capability negotiation.Capability negotiation mechanism back can be introduced.
Optional capability class parameter in the described OPEN message comprises following field as shown in Figure 3: capability class (Parm.Type), parameter length (Parm.Length); Wherein,
The capability class value is self-defining value consensus between a PE and the 2nd PE, and not identical with arbitrary capability class value of stipulating in the bgp protocol, to avoid conflict, for example:
Delete in batches the capability class of VPNv4 route for supporting with private network tags, the type field can be 101.
Delete in batches the capability class of VPNv6 route for supporting with private network tags, the type field can be 102.
Here 101,102 be self-defining value, it is unimportant that what value is the type field get, as long as consult just passablely between a PE and the 2nd PE, but the value of getting can not be conflicted mutually with arbitrary capability class value of stipulating in the bgp protocol.
Parameter length value (Length field) is 0, reality only needs the information of capability class value to get final product, but in order to meet the negotiation packet reference format of BGP, reads message information when being convenient to carry out capability negotiation between the PE, here kept the Length field, its value is made as 0.
Send mutually above-mentioned OPEN message between the one PE and the 2nd PE, for a PE, the capability negotiation mechanism that support is deleted VPNv4 or VPNv6 route in batches with private network tags is as follows:
1) carries this optional capability class parameter in the OPEN message that the far-end BGP VPNv4 of PE reception or VPNv6 neighbours the 2nd PE send, the one PE does not support this ability, then ignore this optional capability class parameter field, fail to consultations, VPNv4 or VPNv6 route are deleted by original flow process.
2) PE supports this ability, does not carry this optional capability class parameter from the OPEN message that the 2nd PE sends, and fails to consultations, and VPNv4 or VPNv6 route are deleted by original flow process.
3) carry this optional capability class parameter in the OPEN message that the 2nd PE of PE reception sends, a PE also supports this ability, then consults successfully, supports between a PE and the 2nd PE to delete in batches VPNv4 or VPNv6 route with private network tags.
For the 2nd PE, process equally after receiving the OPEN message that a PE sends.
Described optional capability class parameter comprises following field: capability class, parameter length; Wherein, the capability class value be a PE with the 2nd PE between consensus self-defining value and not with bgp protocol in arbitrary capability class value of stipulating identical, the parameter length value is 0.
The below enumerates three embodiment for above-mentioned three kinds of scenes and specifies: be respectively how to obtain private network tags in each scene, and how utilize the private network tags of obtaining to delete in batches VPNv4 or VPNv6 route.VPNv4 or VPNv6 route withdraw message format among following three embodiment are identical with embodiment one.
The method flow of the embodiment of the present application two may further comprise the steps as shown in Figure 4:
Step 401: when the link communication between a PE and the CE breaks down, do not have other forwarding equivalence class FEC to use if down hop is the private network tags of described CE, then obtain described private network tags.
In the Layer3 Virtual Private Network as shown in Figure 1, when the link communication between a PE and the CE breaks down, shake such as link, then a PE is the direct-connected route deletion of private network interface of described CE with down hop, the one PE inquires about down hop in its VPNv4 or VPNv6 route table items be whether the private network tags of described CE has other forwarding equivalence class FEC to use, and judges whether that namely other route next jump is used:
If have, then according to prior art deletion VPNv4 or VPNv6 route.
If no, then a PE discharges this private network tags from its VPNv4 or VPNv6 route table items, thereby obtains this private network tags.
Here why will carry out the operation of above-mentioned inquiry, be that each VPN only divides a label because the PE equipment of the manufacturers produce that has is at present applied for private network tags by VPN; How many down hops the PE equipment of the manufacturers produce that has has what private network tags are just arranged by VPN route next jump application private network tags in the VPN route.For the PE equipment of pressing VPN application private network tags, if by private network tags deletion route, the route that then breaks down except meeting deletion down hop also can be deleted the routing iinformation of many normal operations by mistake.
Therefore, among the application, for taking into account the PE equipment of present two class manufacturer production, before obtaining private network tags, must guarantee that described private network tags does not have other forwarding equivalence class FEC to use, therefore, as preferred embodiment, whether the private network tags that need to inquire about first down hop and be above-mentioned CE also has other forwarding equivalence class FEC to use, if have, just can not delete in batches VPNv4 or VPNv6 routing iinformation according to private network tags, but according to the method for cancelling VPNv4 or VPNv6 route in the prior art, namely a PE sends the route withdraw message to the 2nd PE, and described route withdraw message carries all VPNv4 or the VPNv6 routing iinformation that down hop is described CE, after the 2nd PE receives described route withdraw message, can only delete item by item according to a large amount of VPNv4 that carry in the described route withdraw message or VPNv6 routing iinformation.
Step 401 is corresponding to the step 201 of embodiment one.
Step 402: PE encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE, described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
Be that described route withdraw message is resolved described route withdraw message for triggering the 2nd PE, extract the private network tags in the described route withdraw message, with the private network tags extracted as index, in VPNv4 or VPNv6 routing table, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label.
After the one PE gets access to private network tags, encapsulate VPNv4 or a VPNv6 route withdraw message that contains described private network tags, here take VPNv4 route withdraw message as example, the processing of VPNv6 route withdraw message is similar, VPNv4 route withdraw message is as shown in table 1, described VPNv4 route withdraw message is sent to the 2nd PE, and the 2nd PE resolves it after receiving described VPNv4 route withdraw message, judges namely whether the VPNv4 address is 0:0255.255.255.255:
If so, then extract the private network tags in the described VPNv4 route withdraw message, as index, in the VPNv4 routing table, deletion is with the whole VPNv4 routes of described private network tags as outgoing label with the private network tags extracted;
If not, then according to the prior art deletion, namely according to the deletion of the IPv4 route prefix in described VPNv4 route withdraw message VPNv4 route.
Preferably, before step 401, a PE is identical with embodiment one with the process that the 2nd PE carries out capability negotiation.
The method flow of the embodiment of the present application three may further comprise the steps as shown in Figure 5:
Step 501: when the BGP VPNv4 between a PE and the 3rd PE or VPNv6 Routing Protocol broke, a PE obtained private network tags, and described private network tags is for entering one to one label with outgoing label from the 3rd PE; Wherein, a PE can carry out the private network tags exchange, and the 3rd PE is BGP VPNv4 or the VPNv6 neighbours of a PE and is different from the 2nd PE.
Step 501 is corresponding to the step 201 of embodiment one.Illustrate as follows:
In the cross-domain networking of OptionB class as shown in Figure 6, ASBR-PE is Autonomous System Boundary Router, AS Boundary Router, it also is provider edge router, ASBR-PE1(the one PE) can carry out the private network tags exchange, thereby the BGP LSP(label switched path of ASBR-PE1) can have one or more outlabel(outgoing label in the private network list item) enter label with inlabel() list item one to one, wherein the outlabel on the ASBR-PE1 is by downstream PE 1(the 3rd PE) distribute, inlabel is that ASBR-PE1 distributes to upstream AS BR-PE2(the 2nd PE) use, when ASBR-PE1 and PE1 and between BGP VPNv4 or VPNv6 Routing Protocol when breaking, ASBR-PE1 is one or more at the upstream private network tags outlabel(that cancels from PE1) in, according to the corresponding list item of outlabel with inlabel, obtain that private network tags inlabel(is one or more one to one with described upstream private network tags outlabel from PE1).
Step 502: a PE is for each private network tags in the described private network tags, encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE, described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
After the one PE gets access to private network tags inlabel, all inlabel are packaged into VPNv4 or the VPNv6 route withdraw message that contains described private network tags inlabel according to table 1 or table 2, be sent to the 2nd PE, after the 2nd PE receives the route withdraw message, resolve described route withdraw message, extract the private network tags inlabel in the route withdraw message, according to described private network tags, delete in batches VPNv4 or VPNv6 route, the processing that the 2nd PE receives behind the route withdraw message is identical with embodiment one, does not repeat them here.
Step 502 is corresponding to step 202, the step 203 of embodiment one.
Preferably, before step 501, a PE is identical with embodiment one with the process that the 2nd PE carries out capability negotiation.
The method flow of the embodiment of the present application four may further comprise the steps as shown in Figure 7:
Step 701: when a PE local deletion VPN route forwarding table (VRF), obtain all private network tags that described VRF distributes.
When the local deletion of PE VRF table, a PE is when cancelling the private network tags inlabel of all these VRF distribution, and all private network tags inlabel(that obtain described VRF distribution are one or more).
Step 701 is corresponding to the step 201 of embodiment one.
Step 702: a PE is for each private network tags in the described private network tags, encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE, described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
The one PE is packaged into VPNv4 or the VPNv6 route withdraw message that contains described private network tags inlabel with all private network tags inlabel that obtain according to table 1 or table 2, be sent to the 2nd PE, the 2nd PE is BGP VPNv4 or the VPNv6 routing neighbor of a PE, the processing that the 2nd PE receives behind the route withdraw message is identical with embodiment one, does not repeat them here.
Step 702 is corresponding to step 202, the step 203 of embodiment one.
Preferably, before step 701, a PE is identical with embodiment one with the process that the 2nd PE carries out capability negotiation.
The PE functions of the equipments structural representation of the embodiment of the present application as shown in Figure 8, a kind of provider edge router (PE) comprising: label acquisition module, message package module and packet sending and receiving module; Wherein,
The label acquisition module is used for obtaining at least one private network tags;
The message package module is used for each private network tags for described private network tags, and encapsulation contains the route withdraw message of this private network tags;
The packet sending and receiving module, the route withdraw message after being used for encapsulating is sent to the 2nd PE, and the 2nd PE is VPNv4 or the VPNv6 neighbours of the Border Gateway Protocol (BGP) of described provider edge router PE; Described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
Preferably, described provider edge router also comprises the capability negotiation module, also be used for adding the optional capability class parameter of supporting to delete in batches with private network tags VPNv4 or VPNv6 route at BGP OPEN message, before described provider edge router PE and the 2nd PE set up BGP VPNv4 or VPNv6 neighbours, the BGPOPEN message is sent to the 2nd PE, and the optional capability class of supporting according to the optional capability class parameter of carrying in the described OPEN message that receives and a PE this locality carries out capability negotiation.
Preferably, described label acquisition module, also be used for when the link communication between described provider edge router PE and the Customer Edge router CE breaks down, do not have other forwarding equivalence class FEC application if down hop is the private network tags of described CE, then obtain described private network tags;
Perhaps,
When the BGP VPNv4 between described provider edge router PE and the 3rd PE or VPNv6 Routing Protocol break, obtain private network tags, described private network tags is for entering one to one label with outgoing label from the 3rd PE; Wherein, described provider edge router PE can carry out the private network tags exchange, and the 3rd PE is BGP VPNv4 or the VPNv6 neighbours of described provider edge router PE and is different from the 2nd PE;
Perhaps,
When this locality deletion VPN route forwarding table VRF, obtain all private network tags that described VRF distributes.
Preferably, described label acquisition module also is used for the described private network tags of obtaining as index, in the VPNv4 or VPNv6 routing table of this locality, deletion with described private network tags as the whole VPNv4 that enter label or VPNv6 route.
Described optional capability class parameter comprises following field: capability class, parameter length; Wherein, the capability class value be described provider edge router PE with its BGP VPNv4 or VPNv6 routing neighbor between consensus self-defining value and not with bgp protocol in arbitrary capability class value of stipulating identical, the parameter length value is 0.
Preferably, described label acquisition module, whether the private network tags that also is used for the inquiry down hop and is described CE has other forwarding equivalence class FEC to use, if, then notify the packet sending and receiving module to send the route withdraw message to the 2nd PE, described route withdraw message carries all VPNv4 or the VPNv6 routing iinformation that down hop is described CE;
The packet sending and receiving module is also for the message processing module (MPM) that sends described route withdraw message to the two PE according to the above-mentioned notice of label acquisition module.
The described route withdraw message that contains this private network tags comprises following field: prefix length, label stack, Route Distinguisher, IPv4 or IPv6 route prefix;
If described route withdraw message is VPNv4 route withdraw message, then the value of label stack is described private network tags, and the IPv4 route prefix is 255.255.255.255, and prefix length is 120, and Route Distinguisher is self-defining value;
If described route withdraw message is VPNv6 route withdraw message, then the value of label stack is described private network tags, and the IPv6 route prefix is FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, and prefix length is 216, and Route Distinguisher is self-defining value.
Described the 2nd PE is behind the route withdraw message that receives from described provider edge router PE, for VPNv4 route withdraw message, judge that whether the VPNv4 address is: Route Distinguisher 255.255.255.255, if so, then extract the private network tags in the described VPNv4 route withdraw message;
For VPNv6 route withdraw message, judge that whether the VPNv6 address is: Route Distinguisher FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, if so, then extract the private network tags in the described VPNv6 route withdraw message.
Described the 2nd PE is behind the route withdraw message that receives from described provider edge router PE, the VPNv4 address of judging VPNv4 route withdraw message is not: Route Distinguisher 255.255.255.255, or the VPNv6 address of VPNv6 route withdraw message is not: during Route Distinguisher FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, according to the IPv4 in the route withdraw message or IPv6 route prefix deletion VPNv4 or VPNv6 route;
Adopt the application's scheme, when the private network interface communication break down or PE between BGP VPNv4 or the VPNv6 agreement is broken or during the local deletion of PE VRF, by utilizing private network tags deletion VPNv4 or VPNv6 route, only need encapsulation and send a route withdraw message or a small amount of route withdraw message, just can delete in batches a large amount of VPNv4 or VPNv6 route, with respect to prior art, can greatly alleviate the burden of PE equipment and network, improve network performance.
The above only is preferred embodiment of the present invention, and is in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of making, is equal to replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (10)
1. a batch is deleted the method for VPNv4 or VPNv6 route, it is characterized in that, may further comprise the steps:
The first provider edge router PE obtains at least one private network tags, and for each private network tags in the described private network tags, encapsulation contains the route withdraw message of this private network tags and sends it to the 2nd PE; VPNv4 or the VPNv6 neighbours of the Border Gateway Protocol (BGP) that described the 2nd PE is a PE;
Described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label in VPNv4 or VPNv6 routing table.
2. method according to claim 1 is characterized in that, a described PE obtains before at least one private network tags, further comprises:
In BGP OPEN message, add the optional capability class parameter of supporting to delete in batches with private network tags VPNv4 or VPNv6 route;
Before a PE and the 2nd PE set up BGP VPNv4 or VPNv6 neighbours, the one PE sends BGP OPEN message, after a PE received the BGP OPEN message that described the 2nd PE sends, the optional capability class of supporting according to the optional capability class parameter of carrying in the described OPEN message that receives and a PE this locality carried out capability negotiation.
3. method according to claim 1 is characterized in that, a described PE obtains at least one private network tags, comprising:
When the link communication between a PE and the Customer Edge router CE breaks down, if being the private network tags of described CE, down hop do not have other forwarding equivalence class FEC to use, then a PE obtains described private network tags;
Perhaps,
When the BGP VPNv4 between a PE and the 3rd PE or VPNv6 Routing Protocol broke, a PE obtained private network tags, and described private network tags is for entering one to one label with outgoing label from the 3rd PE; Wherein, a PE can carry out the private network tags exchange, and the 3rd PE is BGP VPNv4 or the VPNv6 neighbours of a PE and is different from the 2nd PE;
Perhaps,
When the local deletion of PE VPN route forwarding table VRF, a PE obtains all private network tags that described VRF distributes.
4. method according to claim 1, it is characterized in that, a described PE obtains after at least one private network tags, further comprise: a PE with described private network tags as index, in the VPNv4 or VPNv6 routing table of a PE, delete with described private network tags as the whole VPNv4 that enter label or VPNv6 route.
5. method according to claim 1 is characterized in that, the described route withdraw message that contains this private network tags comprises following field: prefix length, label stack, Route Distinguisher, IPv4 or IPv6 route prefix;
If described route withdraw message is VPNv4 route withdraw message, then the value of label stack is described private network tags, and the IPv4 route prefix is 255.255.255.255, and prefix length is 120, and Route Distinguisher is self-defining value;
If described route withdraw message is VPNv6 route withdraw message, then the value of label stack is described private network tags, and the IPv6 route prefix is FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, and prefix length is 216, and Route Distinguisher is self-defining value.
6. a provider edge router PE is characterized in that, comprising: label acquisition module, message package module and packet sending and receiving module; Wherein,
The label acquisition module is used for obtaining at least one private network tags;
The message package module is used for each private network tags for described private network tags, and encapsulation contains the route withdraw message of this private network tags;
The packet sending and receiving module, the route withdraw message after being used for encapsulating is sent to the 2nd PE, and the 2nd PE is VPNv4 or the VPNv6 neighbours of the Border Gateway Protocol (BGP) of described provider edge router PE; Described route withdraw message is used for triggering described the 2nd PE according to the private network tags of described route withdraw message, and in VPNv4 or VPNv6 routing table, deletion is with whole VPNv4s or the VPNv6 route of described private network tags as outgoing label.
7. provider edge router according to claim 6, it is characterized in that, described provider edge router also comprises the capability negotiation module, be used for adding the optional capability class parameter of supporting to delete in batches with private network tags VPNv4 or VPNv6 route at BGP OPEN message, before described provider edge router PE and the 2nd PE set up BGP VPNv4 or VPNv6 neighbours, BGP OPEN message is sent to the 2nd PE, and the optional capability class of supporting according to the optional capability class parameter of carrying in the described OPEN message that receives and a PE this locality carries out capability negotiation.
8. provider edge router according to claim 6, it is characterized in that, described label acquisition module, also be used for when the link communication between described provider edge router PE and the Customer Edge router CE breaks down, do not have other forwarding equivalence class FEC to use if down hop is the private network tags of described CE, then obtain described private network tags;
Perhaps,
When the BGP VPNv4 between described provider edge router PE and the 3rd PE or VPNv6 Routing Protocol break, obtain private network tags, described private network tags is for entering one to one label with outgoing label from the 3rd PE; Wherein, described provider edge router PE can carry out the private network tags exchange, and the 3rd PE is BGPVPNv4 or the VPNv6 neighbours of described provider edge router PE and is different from the 2nd PE;
Perhaps,
When this locality deletion VPN route forwarding table VRF, obtain all private network tags that described VRF distributes.
9. provider edge router according to claim 6, it is characterized in that, described label acquisition module, also be used for the described private network tags of obtaining as index, in the VPNv4 or VPNv6 routing table of this locality, delete with described private network tags as the whole VPNv4 that enter label or VPNv6 route.
10. provider edge router according to claim 6 is characterized in that, the described route withdraw message that contains this private network tags comprises following field: prefix length, label stack, Route Distinguisher, IPv4 or IPv6 route prefix;
If described route withdraw message is VPNv4 route withdraw message, then the value of label stack is described private network tags, and the IPv4 route prefix is 255.255.255.255, and prefix length is 120, and Route Distinguisher is self-defining value;
If described route withdraw message is VPNv6 route withdraw message, then the value of label stack is described private network tags, and the IPv6 route prefix is FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF, and prefix length is 216, and Route Distinguisher is self-defining value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210392481.6A CN102882797B (en) | 2012-10-16 | 2012-10-16 | Batch deletes the method and PE of VPNv4 or VPNv6 routes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210392481.6A CN102882797B (en) | 2012-10-16 | 2012-10-16 | Batch deletes the method and PE of VPNv4 or VPNv6 routes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102882797A true CN102882797A (en) | 2013-01-16 |
| CN102882797B CN102882797B (en) | 2018-03-23 |
Family
ID=47483947
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210392481.6A Active CN102882797B (en) | 2012-10-16 | 2012-10-16 | Batch deletes the method and PE of VPNv4 or VPNv6 routes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102882797B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106059924A (en) * | 2016-08-19 | 2016-10-26 | 华为技术有限公司 | Information management method, devices and system |
| CN108243102A (en) * | 2016-12-27 | 2018-07-03 | 迈普通信技术股份有限公司 | A kind of implementation method of quick heavy-route and PE equipment |
| CN108768859A (en) * | 2018-05-17 | 2018-11-06 | 迈普通信技术股份有限公司 | Data processing method, apparatus and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101510889A (en) * | 2009-04-03 | 2009-08-19 | 杭州华三通信技术有限公司 | Method and equipment for obtaining dynamic route |
| CN101572669A (en) * | 2009-05-27 | 2009-11-04 | 中兴通讯股份有限公司 | Transmitting method of VPN message as well as allocating and deleting method of the router marks thereof |
| US20120120957A1 (en) * | 2007-01-17 | 2012-05-17 | Rockstar Bidco, LP | Border Gateway Protocol Procedures for Multi-Protocol Label Switching and Layer-2 Virtual Private Networks Using Ethernet-Based Tunnels |
| CN102594714A (en) * | 2012-03-29 | 2012-07-18 | 杭州华三通信技术有限公司 | BGP (Border Gateway Protocol) routing processing method and BGP routing equipment |
-
2012
- 2012-10-16 CN CN201210392481.6A patent/CN102882797B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120120957A1 (en) * | 2007-01-17 | 2012-05-17 | Rockstar Bidco, LP | Border Gateway Protocol Procedures for Multi-Protocol Label Switching and Layer-2 Virtual Private Networks Using Ethernet-Based Tunnels |
| CN101510889A (en) * | 2009-04-03 | 2009-08-19 | 杭州华三通信技术有限公司 | Method and equipment for obtaining dynamic route |
| CN101572669A (en) * | 2009-05-27 | 2009-11-04 | 中兴通讯股份有限公司 | Transmitting method of VPN message as well as allocating and deleting method of the router marks thereof |
| CN102594714A (en) * | 2012-03-29 | 2012-07-18 | 杭州华三通信技术有限公司 | BGP (Border Gateway Protocol) routing processing method and BGP routing equipment |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106059924A (en) * | 2016-08-19 | 2016-10-26 | 华为技术有限公司 | Information management method, devices and system |
| CN106059924B (en) * | 2016-08-19 | 2020-04-03 | 华为技术有限公司 | Method, device and system for managing information |
| US11855877B2 (en) | 2016-08-19 | 2023-12-26 | Huawei Technologies Co., Ltd. | Information management method, apparatus, and system |
| CN108243102A (en) * | 2016-12-27 | 2018-07-03 | 迈普通信技术股份有限公司 | A kind of implementation method of quick heavy-route and PE equipment |
| CN108243102B (en) * | 2016-12-27 | 2022-03-11 | 迈普通信技术股份有限公司 | Method for realizing fast rerouting and PE equipment |
| CN108768859A (en) * | 2018-05-17 | 2018-11-06 | 迈普通信技术股份有限公司 | Data processing method, apparatus and system |
| CN108768859B (en) * | 2018-05-17 | 2021-05-25 | 迈普通信技术股份有限公司 | Data processing method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102882797B (en) | 2018-03-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110557316B (en) | Message transmission method, system, device and computer readable storage medium | |
| CN104221332B (en) | LAN multiplexer | |
| CN102724118B (en) | Label distribution method and device | |
| CN104243270B (en) | A kind of method and apparatus for establishing tunnel | |
| CN101160850B (en) | Method and device for forwarding packet | |
| CN108023815B (en) | Information transmission method, device and system | |
| CN102571426B (en) | Double-homing protection method and device | |
| CN101316260B (en) | Packaging conversion method and packaging conversion equipment | |
| WO2008092357A1 (en) | A method and device for establishing a pseudo wire tunnel and transmitting message using it | |
| CN110401599A (en) | The processing method and processing device of data packet, storage medium, electronic device | |
| CN101286922A (en) | Signalling control method, system and apparatus | |
| CN103825818B (en) | A kind of more topological network retransmission methods and device | |
| CN106487537A (en) | Business chain implementation method and policy control platform | |
| CN103067278B (en) | A kind of method for transmission processing of Frame, equipment and system | |
| CN108390812B (en) | Message forwarding method and device | |
| CN105553810A (en) | Method and device for forwarding special line service packet | |
| CN102882797A (en) | VPNv4 or VPNv6 route batch deleting method and PE (Provider Edge) | |
| CN109218176B (en) | Message processing method and device | |
| CN109743758A (en) | Multi link communications method, communication device and communication system | |
| CN100561981C (en) | Multiprotocol label switching retransmission method and forwarding unit | |
| CN105187320A (en) | MPLS load sharing processing method and device | |
| CN103716240B (en) | Message forwarding method, message receiving method and corresponding equipment | |
| CN103986637B (en) | A kind of error message processing method and tunnel device | |
| CN102611603B (en) | The foundation of the static tunnel MPLS forwarding table, data transmission method and device | |
| JP4383216B2 (en) | Communication terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Applicant before: Huasan Communication Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220129 Address after: 100082 room 402, building 2, yard 1, Zhongguancun East Road, Haidian District, Beijing Patentee after: Ziguang Hengyue Technology Co.,Ltd. Address before: 310052 Changhe Road, Binjiang District, Hangzhou, Zhejiang Province, No. 466 Patentee before: NEW H3C TECHNOLOGIES Co.,Ltd. |