CN101442491B - Route transmission method and routing device for nesting VPN - Google Patents
Route transmission method and routing device for nesting VPN Download PDFInfo
- Publication number
- CN101442491B CN101442491B CN200810241146XA CN200810241146A CN101442491B CN 101442491 B CN101442491 B CN 101442491B CN 200810241146X A CN200810241146X A CN 200810241146XA CN 200810241146 A CN200810241146 A CN 200810241146A CN 101442491 B CN101442491 B CN 101442491B
- Authority
- CN
- China
- Prior art keywords
- attribute
- route
- routing
- correspondence
- routing iinformation
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a route sending method and route equipment applied to a nested virtual private network (VPN), wherein the method comprises the following steps: before sending route information to next hop of the route equipment in a downlink direction, the route equipment in nested VPN networking judges whether the RT attribute corresponding to the route information to be sent is a subset of the route identifier (RT) attribute corresponding to VPN containing the next hop stored by the route equipment; if so, the route information to be sent is carried in an IPv4 route to be sent to the next hop; or else, the route information to be sent is carried in a VPNv4 route to be sent to the next hop. The route sending method and the route equipment can ensure that no useless internal private network route exists in IP routing lists of the route equipment, thereby realizing the removal of redundant routes and saving system resources.
Description
Technical field
The present invention relates to the route technology in the network service, particularly a kind of route sending method and routing device that is applied to nested VPN(Virtual Private Network).
Background technology
Multi-protocol label switching three-layer Virtual Private Network (MPLS L3VPN) is a kind of three-layer technology based on provider edge equipment (PE) in service provider's vpn solution, it uses Border Gateway Protocol (BGP) to issue the VPN route on service provider backbone, uses MPLS to transmit the VPN message on service provider backbone.It uses the Route Distinguisher (RT in the BGP extended community attribute, Route Target) attribute is controlled the issue of VPN routing iinformation, and each routing device is stored by the RT attribute that receives the RT that carries in the route and self storage is mated the route that determines whether receiving.
In the basic MPLS L3VPN networking, each VPN in the user network is by the PE apparatus interconnection of CE equipment and operator, and user network is common IP network, and user network can not be divided sub-VPN.And the user network complexity is various in the actual networking, user network further need be divided into a plurality of VPN, if the VPN of user network inside directly is configured on the PE equipment, then can cause the VPN quantity of carrying on the PE equipment huge, not only increase the operation cost of network, also brought the problem of management and secure context.At this problem, nested VPN technologies are arisen at the historic moment, thereby configuration VPN makes the inner VPN of each CE equipment control oneself divide on each CE equipment, transmits IPv4 route and VPNv4 route between PE and CE equipment, thereby realizes the transmission of the inner VPN routing iinformation of user network.
In the nested VPN technologies, the transmission of routing iinformation mainly comprises with the lower part between each routing device: with framework shown in Figure 1 is example, the RT attribute that configuration PE-A1 and PE-A2 go up VPNA is 100: 1, the RT attribute that CE-B1 and CE-B2 go up VPNB1 is 200: 1, the RT attribute of VPNC1 on CE-C1 and the CE-C3 is 300: 1, and the RT attribute of the last VPND of PE-A3 is 100: 1 and 800: 1.
At up direction, each CE equipment in the user network sends the VPN information that the VPNv4 route is carried each CE inside to PE equipment, after PE equipment receives up VPNv4 route, preserve routing iinformation wherein, and the RT attribute of inciting somebody to action wherein is kept in the interim RT attribute list, affix MPLSVPN attribute is transferred to other PE equipment by the MPLS backbone network, for example, PE-A1 to the VPNv4 route that PE-A2 sends is: the VPNv4 route of carrying routing iinformation 10.1.1.0/24 and RT attribute and be 100: 1, carry routing iinformation 20.1.1.0/24 and RT attribute and be the VPNv4 route of 100: 1 and 200: 1 and carry routing iinformation 30.1.1.0/24 and the RT attribute is 100: 1, the VPNv4 route of 200: 1 and 300: 1.
At down direction, PE equipment and CE equipment are after receiving the VPNv4 route, with RT attribute that carries in the VPNv4 route and the introducing Route Distinguisher (IRT that self stores, Import Route target) attribute mates, if the match is successful then receive and the routing iinformation that carries in the VPNv4 route is stored in the VPN routing table, again the routing iinformation in the VPN routing table and its corresponding RT attribute are sent to its next jumping CE equipment by VPNv4 route and IPv4 route, until final jump CE equipment; If receive the IPv4 route, then need not matching operation, directly the routing iinformation that will wherein carry is stored in the IP route table.
The present invention is chiefly directed to the operation of (comprising PE equipment and CE equipment) of each routing device on the down direction, after sending route by above-mentioned mode of the prior art, PE-A2 equipment, CE-B2 equipment and CE-C3 equipment receive and the routing iinformation of storage as shown in table 1.RD shown in the table 1 is a route-distinguisher, and the present invention is to it and be indifferent to.
Table 1
As can be seen from Table 1, when adopting route sending method of the prior art, PE-A2 equipment only receives the VPNv4 route, but owing to when each routing device on the down direction is sending the VPNv4 route, also can send the IPv4 route, and the VPNv4 route that sends is identical with the routing iinformation that the IPv4 route comprises, make CE-B2 equipment and CE-C3 equipment except receiving the VPNv4 route, also receive the IPv4 route, and the routing iinformation that carries in the IPv4 route all is stored in the IP route table.This will cause in the IP route table on CE equipment and both store outside the routing iinformation of VPN at the corresponding levels, also stored the VPN route information of next stage VPN, for example the routing iinformation 30.1.1.0/24 that carries in the IPv4 route that routing iinformation 20.1.1.0/24 that carries in the IPv4 route that CE-B2 equipment receives and 30.1.1.0/24 and CE-C3 equipment receive.Yet in symmetrical networking structure as shown in Figure 1, do not allow CE and PE equipment to stride the visit of level (for example not allowing CE-B2 device access CE-C2 equipment and CE-C1 equipment), therefore the VPN route information of storage next stage VPN is that redundant promptly there is no need stored in IP route table, and the method that sends route in the prior art obviously can cause the waste of system.
Summary of the invention
In view of this, the invention provides a kind of route sending method and routing device that is applied to nested VPN, so that remove redundant route, conserve system resources.
A kind of route sending method that is applied to nested VPN, this method comprises:
Routing device in the nested VPN networking on the down direction to it before next jump to send routing iinformation, the Route Distinguisher RT attribute of judging routing iinformation correspondence to be sent whether for this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, if then will this routing iinformation to be sent be carried at and send to described next jumping in the IPv4 route; Otherwise the routing iinformation that this is to be sent is carried at and sends to described next jumping in the VPNv4 route.
A kind of routing device, this routing device are used for nested VPN networking, and this routing device comprises: first judging unit, the first via are by transmitting element and secondary route transmitting element;
Described first judging unit, be used for this routing device on the down direction to it before next jump to send routing iinformation, the RT attribute of judging routing iinformation correspondence to be sent whether for this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, if, then this routing iinformation to be sent is offered the described first via by transmitting element, otherwise this routing iinformation to be sent is offered described secondary route transmitting element;
The described first via is used for that the routing iinformation that described first judging unit provides is carried at the IPv4 route and is sent to described next jumping by transmitting element;
Described secondary route transmitting element is used for that the routing iinformation that described first judging unit provides is carried at the VPNv4 route and sends to described next jumping.
As can be seen from the above technical solutions, routing device in the nested in the present invention VPN networking on the down direction to it before next jump to send routing iinformation, RT attribute by judging routing iinformation correspondence to be sent whether for next of this routing device storage jump under the subclass of IRT attribute of VPN correspondence select one to select to adopt the mode of IPv4 route still be that the mode of VPNv4 route is carried this routing iinformation and sent to next jumping, be specially: if the subclass of the IRT attribute of VPN correspondence under this next jumping that the RT attribute of routing iinformation correspondence to be sent is this routing device to be stored, illustrate that then this routing iinformation is the outside route rather than the inner VPN route of routing device, therefore need be carried at this routing iinformation and send to next jumping in the IPv4 route; Otherwise illustrate that this routing iinformation is the inside VPN route of routing device, therefore this routing iinformation is carried at and sends to next jumping in the VPNv4 route, useless inside VPN route be will can not store in the IP route table of next jumping this moment, thereby the removing of redundant route, conserve system resources realized.
Description of drawings
Fig. 1 is the symmetrical networking structure figure of a kind of nested VPN;
The detailed method flow chart that Fig. 2 provides for the embodiment of the invention;
The structure chart of the routing device that Fig. 3 provides for the embodiment of the invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
Method provided by the invention mainly comprises: each routing device in the nested VPN networking on the down direction to it before next jump to send routing iinformation, whether the RT attribute of judging routing iinformation correspondence to be sent is the subclass of the IRT attribute of VPN correspondence under this next jumping of self storing, if then will this routing iinformation to be sent be carried in the IPv4 route and send; Otherwise the routing iinformation that this is to be sent is carried in the VPNv4 route and sends.
The detailed method flow chart that Fig. 2 provides for the embodiment of the invention, routing device 1 sends routing iinformation to routing device 2 on down direction process can be as shown in Figure 2, wherein, routing device 1 can be PE equipment or CE equipment, and routing device 2 can be CE equipment.This method can may further comprise the steps:
Step 201: the IRT attribute that routing device 1 is corresponding with the routing device 2 affiliated VPN that self store with the RT attribute of routing iinformation correspondence to be sent is got common factor.
Owing to can dispose the IRT attribute respectively at the VPN under each next jumping in its private network in advance in the routing device, be about to each next jump under RT property store of VPN be in the routing device at the IRT attribute of this VPN, each next the IRT of VPN correspondence under jumping identifies the VPN route information of this next jumping.
Step 202: partly delete if routing device 1 is judged the common factor that step 301 in the RT attribute of routing iinformation correspondence to be sent is obtained, then whether the RT attribute of routing iinformation correspondence to be sent is empty after the deletion action, if then execution in step 203, if not, execution in step 204.
Above-mentioned steps 201 and step 202 are whether the RT attribute of judging routing iinformation correspondence to be sent is wherein a kind of implementation of the subclass of the IRT attribute of VPN correspondences under the routing device 2 of routing device 1 storage, also can adopt the RT attribute of judging routing iinformation correspondence to be sent one by one whether all to be present in the IRT attribute of VPN correspondences under the routing device 2 of routing device 1 storage, perhaps adopt other implementations, exhaustive no longer one by one at this.
Step 203: routing device 1 is carried at routing iinformation to be sent and sends to routing device 2, process ends in the IPv4 route.
The subclass of the IRT attribute of VPN correspondences under the routing device 2 that if if the RT attribute of routing iinformation correspondence to be sent is a routing device 1 to be stored, illustrate that then this routing iinformation is the outside route of routing device 2, rather than the VPN route of routing device 2 inside, therefore, this routing iinformation need send to routing device 2 by the IPv4 route.
After routing device 2 receives the IPv4 route, the routing iinformation that carries in this IPv4 route is stored in the IP route table of self.
Step 204: route equipment 2 sent to the RT attribute that carries in the VPNv4 route of routing device 1 and exists and occur simultaneously when whether the RT attribute of routing iinformation correspondence to be sent was with up direction after the deletion action in routing device 1 determining step 202, if, execution in step 205, if not, execution in step 206 then.
Judgement in this step is at not having the processing that routing iinformation that other routing devices of symmetrical structure send carries out with routing device 1, other routing devices that if there is no do not have symmetrical structure with routing device 1, then this step can not carried out yet, direct execution in step 205 after step 203.
The RT property store that each routing device routing iinformation that each next jumping is sent during to up direction carries is interim RT attribute list, in this step, whether the routing device 1 RT attribute that can judge routing iinformation correspondence to be sent after the deletion action exists with the interim RT attribute list of the routing device 2 of self storage and occurs simultaneously.
Step 205: routing device 1 with routing iinformation to be sent and deletion action thereof after corresponding RT attribute be carried at and send to routing device 2, process ends in the VPNv4 route.
After routing device 2 receives the VPNv4 route, judge whether the RT attribute that carries in the VPNv4 route exists common factor with the IRT attribute of self storing, if, then the routing iinformation that carries in this VPNv4 route is stored in the VPN routing table, otherwise does not store the routing iinformation that carries in this VPNv4 route.
Step 206: routing device 1 is carried at routing iinformation to be sent and sends to routing device 2, process ends in the IPv4 route.
In the symmetrical networking of nested VPN, PE equipment and CE equipment are all carried out the said method flow process on the down direction, and until final jump CE equipment, this method is being handled same as the prior art to the reception of IPv4 route and VPNv4 route.
Be example with structure shown in Figure 1 still below, the process that each routing device on the down direction is carried out by said method is described.Because the present invention does not change the process that each routing device receives route, therefore, IPv4 route and VPNv4 route that PE-A2 equipment receives still do not change, and the IP route table of storage and VPN routing table are also same as the prior art.The routing iinformation that PE-A2 equipment need send to the CE-B2 of next jumping equipment be: corresponding RT attribute is that 100: 1 10.1.1.0/24, corresponding RT attribute are that 100: 1 and 200: 1 20.1.1.0/24, corresponding RT attribute are that the 30.1.1.0/24 of 100: 1,200: 1 and 300: 1 and corresponding RT attribute are the 15.1.1.0/24 of 100: 1 and 800: 1.
For routing iinformation 10.1.1.0/24, PE-A2 equipment is before sending this routing iinformation, whether the RT attribute of judging this routing iinformation correspondence is the subclass of the IRT attribute of VPN correspondence under the CE-B2 that self stores, it promptly whether is the subclass of IRT attribute of the VPN A correspondence of self storage, because the RT attribute of this routing iinformation correspondence is 100: 1, the IRT attribute of the VPN A correspondence of PE-A2 device storage is 100: 1, the RT attribute of determining this routing iinformation correspondence is the subclass of IRT attribute of the VPN A correspondence of self storage, therefore, this routing iinformation 10.1.1.0/24 is carried at send in the IPv4 route CE-B2 equipment for the CE-B2 device storage in IP route table.
For routing iinformation 20.1.1.0/24, PE-A2 equipment is before sending this routing iinformation, whether the RT attribute of judging this routing iinformation correspondence is the subclass of IRT attribute of the VPN A correspondence of self storage, because the RT attribute of this routing iinformation correspondence is 100: 1 and 200: 1, the IRT attribute of the VPNA correspondence of PE-A2 device storage is 100: 1, the RT attribute of determining this routing iinformation correspondence is not the subclass of IRT attribute of the VPN A correspondence of self storage, behind the common factor between further that the RT attribute deletion of this routing iinformation correspondence is corresponding with the VPN A that self the stores IRT attribute is 200: 1, judge 200: 1 and whether send to the RT attribute existence common factor that carries in the VPNv4 route of PE-A2 equipment with CE-B2 equipment, because it is 200: 1 and 300: 1 that CE-B2 equipment sends to the RT attribute that carries in the VPNv4 route of PE-A2 equipment, exist and occur simultaneously, therefore its corresponding RT attribute after this routing iinformation 20.1.1.0/24 and the deletion action is carried at 200: 1 and sends to CE-B2 equipment confession CE-B2 device storage in the VPNv4 route in the VPN routing table.
For routing iinformation 30.1.1.0/24, PE-A2 equipment is before sending this routing iinformation, whether the RT attribute of judging this routing iinformation correspondence is the subclass of IRT attribute of the VPN A correspondence of self storage, because the RT attribute of this routing iinformation correspondence is 100: 1,200: 1 and 300: 1, the IRT attribute of the VPN A correspondence of PE-A2 device storage is 100: 1, the RT attribute of determining this routing iinformation correspondence is not the subclass of IRT attribute of the VPN A correspondence of self storage, behind the common factor between further that the RT attribute deletion of this routing iinformation correspondence is corresponding with the VPN A that self the stores IRT attribute is 200: 1 and 300: 1, judge 200: 1 and whether with CE-B2 equipment send to the RT attribute that in the VPNv4 route of PE-A2 equipment carry at 300: 1 and have common factor, because it is 200: 1 and 300: 1 that CE-B2 equipment sends to the RT attribute that carries in the VPNv4 route of PE-A2 equipment, exist and occur simultaneously, therefore its corresponding RT attribute after this routing iinformation 30.1.1.0/24 and the deletion action was carried in 200: 1 and 300: 1 and sends to CE-B2 equipment confession CE-B2 device storage in the VPNv4 route in the VPN routing table.
For routing iinformation 15.1.1.0/24, PE-A2 equipment is before sending this routing iinformation, whether the RT attribute of judging this routing iinformation correspondence is the subclass of IRT attribute of the VPN A correspondence of self storage, because the RT attribute of this routing iinformation correspondence is 100: 1 and 800: 1, the IRT attribute of the VPNA correspondence of PE-A2 device storage is 100: 1, the RT attribute of determining this routing iinformation correspondence is not the subclass of IRT attribute of the VPN A correspondence of self storage, behind the common factor between further that the RT attribute deletion of this routing iinformation correspondence is corresponding with the VPN A that self the stores IRT attribute is 800: 1, judge 800: 1 and whether send to the RT attribute existence common factor that carries in the VPNv4 route of PE-A2 equipment with CE-B2 equipment, because it is 200: 1 and 300: 1 that CE-B2 equipment sends to the RT attribute that carries in the VPNv4 route of PE-A2 equipment, there is not common factor, therefore, this routing iinformation 15.1.1.0/24 is carried at send in the IPv4 route CE-B2 equipment for the CE-B2 device storage in IP route table.
The routing iinformation that CE-B2 equipment need send to CE-C3 equipment be that corresponding RT attribute is that 200: 1 20.1.1.0/24, corresponding RT attribute are the 30.1.1.0/24 of 200: 1 and 300: 1.
For routing iinformation 20.1.1.0/24, CE-B2 equipment is before sending this routing iinformation, whether the RT attribute of judging this routing iinformation correspondence is the subclass of the IRT attribute of VPN correspondence under the CE-C3 that self stores, promptly judge whether the subclass of IRT attribute into the VPN B1 correspondence of self storage, because the RT attribute of this routing iinformation correspondence is 200: 1, the IRT attribute of the VPN B1 correspondence of CE-B2 device storage is 200: 1, the RT attribute of determining this routing iinformation correspondence is the subclass of IRT attribute of the VPN B1 correspondence of self storage, therefore this routing iinformation 20.1.1.0/24 is carried at send in the IPv4 route CE-C3 equipment for the CE-C3 device storage in IP route table.
For routing iinformation 30.1.1.0/24, PE-A2 equipment is before sending this routing iinformation, whether the RT attribute of judging this routing iinformation correspondence is the subclass of IRT attribute of the VPN B1 correspondence of self storage, because the RT attribute of this routing iinformation correspondence is 200: 1 and 300: 1, the IRT attribute of the VPNB1 correspondence of PE-A2 device storage is 200: 1, the RT attribute of determining this routing iinformation correspondence is not the subclass of IRT attribute of the VPN B1 correspondence of self storage, behind the common factor between further that the RT attribute deletion of this routing iinformation correspondence is corresponding with the VPN B1 that self the stores IRT attribute is 300: 1, judge 300: 1 and whether send to the RT attribute existence common factor that carries in the VPNv4 route of CE-B2 equipment with CE-C3 equipment, because it is 300: 1 that CE-C3 equipment sends to the RT attribute that carries in the VPNv4 route of CE-B2 equipment, exist and occur simultaneously, therefore its corresponding RT attribute after this routing iinformation 30.1.1.0/24 and the deletion action is carried at 300: 1 and sends to CE-C3 equipment confession CE-C3 device storage in the VPNv4 route in the VPN routing table.
As shown in table 2 by the routing iinformation that said process PE-A2 equipment, CE-B2 equipment and CE-C3 equipment receive and stores.
Table 2
CE-B2 equipment can not receive the IPv4 route of carrying routing iinformation 20.1.1.0/24 and 30.1.1.0/24, and CE-C3 equipment can not receive the IPv4 route of carrying routing iinformation 30.1.1.0/24 yet.
More than be the description that method provided by the invention is carried out, below routing device provided by the present invention be described in detail.The structure chart of the routing device that Fig. 3 provides for the embodiment of the invention, as shown in Figure 3, this routing device can comprise: first judging unit 301, the first via are by transmitting element 302 and secondary route transmitting element 303.
The first via is used for that the routing iinformation that first judging unit 301 provides is carried at the IPv4 route and is sent to next jumping by transmitting element 302.
Secondary route transmitting element 303 is used for that the routing iinformation that first judging unit 301 provides is carried at the VPNv4 route and sends to next jumping.
Wherein, the RT attribute of first judgment unit judges routing iinformation correspondence to be sent whether for this routing device storage this next jump under the mode of subclass of IRT attribute of VPN correspondence can be following two kinds:
First kind: the IRT attribute that first judging unit 301 is corresponding with the affiliated VPN of this next jumping of this routing device storage with the RT attribute of routing iinformation correspondence to be sent is got common factor; After judging the common factor deletion that obtains in the RT attribute with routing iinformation correspondence to be sent, whether the RT attribute of routing iinformation correspondence to be sent is empty, if, the RT attribute of then determining routing iinformation correspondence to be sent be this routing device storage this next jump under the subclass of IRT attribute of VPN correspondence, otherwise the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage this next jump under the subclass of IRT attribute of VPN correspondence.
At this moment, between first judging unit 301 and secondary route transmitting element 303, can also comprise: second judging unit 304, be used to receive the routing iinformation that first judging unit 301 sends, and judge RT attribute that first judging unit 301 carries out routing iinformation correspondence to be sent after the deletion actions whether with up direction on next jumping send to the RT attribute that carries in the VPNv4 route of routing device and exist and occur simultaneously, if, then routing iinformation is offered secondary route transmitting element 303, otherwise, routing iinformation is offered the first via by transmitting element 302.
Also carry first judging unit 301 in the VPNv4 route that secondary route transmitting element 303 sends and carry out the deletion action RT attribute of routing iinformation correspondence afterwards.
The first via can also be used for that the routing iinformation that second judging unit 304 provides is carried at the IPv4 route and be sent to next jumping by transmitting element 302.
Second kind: first judging unit 301 can judge one by one the RT attribute of routing iinformation correspondence to be sent whether all be present in the storage of this routing device this next jump under in the IRT attribute of VPN correspondence, if, the RT attribute of then determining routing iinformation correspondence to be sent be this routing device storage this next jump under the subclass of IRT attribute of VPN correspondence, otherwise the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage this next jump under the subclass of IRT attribute of VPN correspondence.
Because routing device is except having the above-mentioned transmission processing capacity to route information, also can have reception processing capacity simultaneously to route information, therefore, this routing device can also comprise: route receiving element 305, the 3rd judging unit 306, VPN routing table memory cell 307 and IP route table memory cell 308.
Route receiving element 305, be used to receive the VPNv4 route after, this VPNv4 route is offered the 3rd judging unit 306; After receiving the IPv4 route, the routing iinformation in this IPv4 route is stored in the IP route table.
The 3rd judging unit 306, after being used to receive the VPNv4 route, judge whether the RT attribute that carries in this VPNv4 route occurs simultaneously with the IRT attribute existence of this routing device storage, if then the routing iinformation that carries in this VPNv4 route is stored in the VPN routing table.
VPN routing table memory cell 307 is used to store the VPN routing table.
IP route table memory cell 308 is used for the storing IP routing table.
Above-mentioned route receiving element 305, the 3rd judging unit 306, VPN routing table memory cell 307 and IP route table memory cell 308 are existing unit in the prior art, and its function and annexation can be same as the prior art.
By above description as can be seen, routing device in the nested in the present invention VPN networking on the down direction to it before next jump to send routing iinformation, RT attribute by judging routing iinformation correspondence to be sent whether for this routing device storage this next jump under the subclass of IRT attribute of VPN correspondence select one to select to adopt the mode of IPv4 route still be that the mode of VPNv4 route is carried this routing iinformation and sent to next jumping, be specially: if the subclass of the IRT attribute of VPN correspondence under this next jumping that the RT attribute of routing iinformation correspondence to be sent is this routing device to be stored, illustrate that then this routing iinformation is the outside route rather than the inner VPN route of routing device, therefore need be carried at this routing iinformation and send to next jumping in the IPv4 route; Otherwise illustrate that this routing iinformation is the inside VPN route of routing device, therefore this routing iinformation is carried at and sends to next jumping in the VPNv4 route, useless inside VPN route be will can not store in the IP route table of next jumping this moment, thereby the removing of redundant route, conserve system resources realized.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being made, is equal to replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (10)
1. route sending method that is applied to nested virtual private network is characterized in that this method comprises:
Routing device in the nested VPN networking on the down direction to it before next jump to send routing iinformation, the Route Distinguisher RT attribute of judging routing iinformation correspondence to be sent whether for this routing device storage described next jump under the subclass of introducing Route Distinguisher IRT attribute of VPN correspondence, if then will this routing iinformation to be sent be carried at and send to described next jumping in the IPv4 route; Otherwise the routing iinformation that this is to be sent is carried at and sends to described next jumping in the VPNv4 route.
2. method according to claim 1 is characterized in that, the RT attribute of judging routing iinformation correspondence to be sent whether for this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence specifically comprise:
Described routing device with the RT attribute of described routing iinformation correspondence to be sent and self storage described next jump under the corresponding IRT attribute of VPN get common factor; After judging the described common factor deletion that obtains in the RT attribute with routing iinformation correspondence to be sent, whether the RT attribute of described routing iinformation correspondence to be sent is empty, if, the RT attribute of then determining routing iinformation correspondence to be sent be this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, otherwise the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence.
3. method according to claim 2, it is characterized in that, the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage described next jump under after the subclass of IRT attribute of VPN correspondence, and will this routing iinformation to be sent be carried at send in the VPNv4 route before, also comprise:
Described routing device judges whether the RT attribute of the routing iinformation correspondence that described deletion action is afterwards to be sent sends to the RT attribute that carries in the VPNv4 route of described routing device with the above next jumping of up direction and have common factor, if, then carry out described will this routing iinformation to be sent be carried at send in the VPNv4 route described next jump, and also carry the RT attribute of routing iinformation correspondence to be sent after the described deletion action in the described VPNv4 route that sends of routing device; Otherwise routing iinformation to be sent is carried at sends to described next jumping in the IPv4 route.
4. method according to claim 1, it is characterized in that, the RT attribute of judging routing iinformation correspondence to be sent whether for this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence specifically comprise: described routing device judge one by one the RT attribute of routing iinformation correspondence to be sent whether all be present in this routing device storage described next jump under in the IRT attribute of VPN correspondence, if, the RT attribute of then determining routing iinformation correspondence to be sent be this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, otherwise the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence.
5. according to the described method of the arbitrary claim of claim 1 to 4, it is characterized in that, after described next jumper connection is received the VPNv4 route, judge whether the RT attribute that carries in this VPNv4 route exists common factor with the IRT attribute of self storing, if then the routing iinformation that carries in this VPNv4 route is stored in the VPN routing table;
After described next jumper connection is received the IPv4 route, the routing iinformation that carries in this IPv4 route is stored in the IP route table.
6. routing device, this routing device is used for nested VPN networking, it is characterized in that, and this routing device comprises: first judging unit, the first via are by transmitting element and secondary route transmitting element;
Described first judging unit, be used for this routing device on the down direction to it before next jump to send routing iinformation, the RT attribute of judging routing iinformation correspondence to be sent whether for this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, if, then this routing iinformation to be sent is offered the described first via by transmitting element, otherwise this routing iinformation to be sent is offered described secondary route transmitting element;
The described first via is used for that the routing iinformation that described first judging unit provides is carried at the IPv4 route and is sent to described next jumping by transmitting element;
Described secondary route transmitting element is used for that the routing iinformation that described first judging unit provides is carried at the VPNv4 route and sends to described next jumping.
7. routing device according to claim 6 is characterized in that, described first judging unit with the RT attribute of described routing iinformation correspondence to be sent and this routing device storage described next jump under the corresponding IRT attribute of VPN get common factor; After judging the described common factor deletion that obtains in the RT attribute with routing iinformation correspondence to be sent, whether the RT attribute of described routing iinformation correspondence to be sent is empty, if, the RT attribute of then determining routing iinformation correspondence to be sent be this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, otherwise the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence.
8. routing device according to claim 7, it is characterized in that, between described first judging unit and secondary route transmitting element, also comprise: second judging unit, be used to receive the routing iinformation that described first judging unit sends, and judge that whether RT attribute that described first judging unit carries out routing iinformation correspondence to be sent after the deletion action sends to the RT attribute that carries in the VPNv4 route of described routing device with the above next jumping of up direction and exist and occur simultaneously, if, then described routing iinformation is offered described secondary route transmitting element, otherwise, described routing iinformation is offered the described first via by transmitting element;
Also carry described first judging unit in the VPNv4 route that described secondary route transmitting element sends and carry out the described deletion action RT attribute of described routing iinformation correspondence afterwards;
The described first via is used for that also the routing iinformation that described second judging unit provides is carried at the IPv4 route and is sent to described next jumping by transmitting element.
9. routing device according to claim 6, it is characterized in that, described first judging unit judge one by one the RT attribute of described routing iinformation correspondence to be sent whether all be present in this routing device storage described next jump under in the IRT attribute of VPN correspondence, if, the RT attribute of then determining routing iinformation correspondence to be sent be this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence, otherwise the RT attribute of determining routing iinformation correspondence to be sent be not this routing device storage described next jump under the subclass of IRT attribute of VPN correspondence.
10. according to the described routing device of the arbitrary claim of claim 6 to 9, it is characterized in that this routing device also comprises: route receiving element, the 3rd judging unit, VPN routing table memory cell and IP route table memory cell;
Described route receiving element, be used to receive the VPNv4 route after, this VPNv4 route is offered described the 3rd judging unit; After receiving the IPv4 route, the routing iinformation in this IPv4 route is stored in the IP route table;
Described the 3rd judging unit, after being used to receive the VPNv4 route, judge whether the RT attribute that carries in this VPNv4 route occurs simultaneously with the IRT attribute existence of this routing device storage, if then the routing iinformation that carries in this VPNv4 route is stored in the VPN routing table;
Described VPN routing table memory cell is used to store the VPN routing table;
Described IP route table memory cell is used for the storing IP routing table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810241146XA CN101442491B (en) | 2008-12-26 | 2008-12-26 | Route transmission method and routing device for nesting VPN |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810241146XA CN101442491B (en) | 2008-12-26 | 2008-12-26 | Route transmission method and routing device for nesting VPN |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101442491A CN101442491A (en) | 2009-05-27 |
| CN101442491B true CN101442491B (en) | 2011-03-30 |
Family
ID=40726738
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810241146XA Expired - Fee Related CN101442491B (en) | 2008-12-26 | 2008-12-26 | Route transmission method and routing device for nesting VPN |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101442491B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8654652B2 (en) | 2011-05-30 | 2014-02-18 | Hewlett-Packard Development Company, L.P. | System for managing the size of a hardware routing table |
| CN102624623B (en) * | 2012-03-13 | 2015-07-22 | 杭州华三通信技术有限公司 | Virtual private network (VPN) routing information publication method and equipment |
| US10275376B2 (en) * | 2016-03-02 | 2019-04-30 | Western Digital Technologies, Inc. | Efficient cross device redundancy implementation on high performance direct attached non-volatile storage with data reduction |
| CN111385204B (en) * | 2018-12-27 | 2022-03-29 | 中国移动通信集团贵州有限公司 | Service transmission method, device, equipment and medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101014014A (en) * | 2007-02-09 | 2007-08-08 | 华为技术有限公司 | Routing aggregation method, packet transmitting method and border router of autonomous system |
| CN101322341A (en) * | 2005-11-30 | 2008-12-10 | 思科技术公司 | Method and apparatus providing prioritized recursion resolution of border gateway protocol forwarding information bases |
-
2008
- 2008-12-26 CN CN200810241146XA patent/CN101442491B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101322341A (en) * | 2005-11-30 | 2008-12-10 | 思科技术公司 | Method and apparatus providing prioritized recursion resolution of border gateway protocol forwarding information bases |
| CN101014014A (en) * | 2007-02-09 | 2007-08-08 | 华为技术有限公司 | Routing aggregation method, packet transmitting method and border router of autonomous system |
Non-Patent Citations (2)
| Title |
|---|
| Yeim-Kuan Chang et al.Dynamic Segment Trees for.《IEEE TRANSACTIONS ON COMPUTERS》.2007,第56卷(第6期),769-784. * |
| 董玲等.BGP/MPLS VPN实现细节探讨.《计算机工程与应用》.2005,(第29期),117-120. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101442491A (en) | 2009-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100536407C (en) | Fast convergence method of point to point services and the provider edge device thereof | |
| CN102571587B (en) | Method and equipment for forwarding messages | |
| CN101052022B (en) | System and method for virtual special net user to access public net | |
| CN102291455B (en) | Distributed cluster processing system and message processing method thereof | |
| CN106453025A (en) | Tunnel creating method and device | |
| CN102137024B (en) | Message processing method, exit routing device and border routing device | |
| WO2010135957A1 (en) | Virtual private network message forwarding method and routing label assignment and deletion method thereof | |
| CN101141382A (en) | Routing update method and router | |
| WO2022121466A1 (en) | Data processing method and device for ethernet virtual private network, and storage medium | |
| CN101355486A (en) | Method, equipment and system for switching route | |
| CN101442491B (en) | Route transmission method and routing device for nesting VPN | |
| CN102347889A (en) | Message forwarding method, system and device in H-VPLS (Hierarchical Virtual Private local area network service) | |
| WO2016192618A1 (en) | Method, apparatus and system for collecting access control list | |
| CN101132374B (en) | Method and device for transmitting message | |
| CN102394804A (en) | VPN system building method and VPN system | |
| CN101827366B (en) | Method, unit and device for isolating wireless network user | |
| CN107294849B (en) | Method, device and system for establishing service path | |
| CN102025641A (en) | Message filtering method and exchange equipment | |
| CN107528788B (en) | Method and device for realizing automatic stacking between network devices | |
| CN101635656B (en) | Fault detection method in layered ordered address packet network, system and equipment | |
| CN101656740A (en) | Method and routing equipment for controlling label sending | |
| EP2573987A1 (en) | Method for label distribution in multi-topology | |
| CN101827023B (en) | Processing method of data and device thereof | |
| CN103117913A (en) | Method and equipment for informing MAC (media access control) address information | |
| CN113497830A (en) | Cloud network communication method, platform, equipment and storage medium |
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 | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee 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 Patentee before: Huasan Communication Technology Co., Ltd. |
|
| CP03 | Change of name, title or address | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110330 Termination date: 20191226 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |