CN103916303A - MPLS TE tunnel configuration device and method - Google Patents

MPLS TE tunnel configuration device and method Download PDF

Info

Publication number
CN103916303A
CN103916303A CN201410159015.2A CN201410159015A CN103916303A CN 103916303 A CN103916303 A CN 103916303A CN 201410159015 A CN201410159015 A CN 201410159015A CN 103916303 A CN103916303 A CN 103916303A
Authority
CN
China
Prior art keywords
tunnel
fec
static routing
acl
group
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
Application number
CN201410159015.2A
Other languages
Chinese (zh)
Other versions
CN103916303B (en
Inventor
顾雷雷
沈岭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou H3C Technologies Co Ltd
Original Assignee
Hangzhou H3C Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Priority to CN201410159015.2A priority Critical patent/CN103916303B/en
Publication of CN103916303A publication Critical patent/CN103916303A/en
Application granted granted Critical
Publication of CN103916303B publication Critical patent/CN103916303B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Abstract

The invention provides an MPLS TE tunnel configuration device and method. The MPLS TE tunnel configuration device and method are applied to a network device. The method includes the steps that predefined TE tunnels which are established for a plurality of FECs with the same destination address are stored, and the predefined TE tunnels do not comprise reserved bandwidths; static routes configured for the FECs are stored, and the static routes comprise tunnel bandwidths and bound predefined TE tunnels which are needed by the FECs; according to the static routes, corresponding TE sub-tunnels are generated for the FECs, and the reserved bandwidths of the TE sub-tunnels are equal to the tunnel bandwidths needed by the FECs. According to the technical scheme, the configuration workload of managers is greatly reduced.

Description

A kind of MPLS traffic engineering tunnel inking device and method
Technical field
The present invention relates to communication technical field, relate in particular to a kind of MPLS traffic engineering tunnel inking device and method.
Background technology
MPLS(Multi-Protocol Label Switching, multiprotocol label switching) TE (Traffic Engineering, traffic engineering) combine MPLS technology and traffic engineering, by setting up the LSP(Label Switched Path along specified path, label switched path) tunnel carries out resource reservation, make network traffics get around congested node, reach the object of balancing network flow.
MPLS traffic engineering tunnel is that the virtual point-to-point of from head node to destination node connects.Under normal conditions, MPLS traffic engineering tunnel is by a CRLSP(Constraint-based Routed Label Switched Paths, based on the LSP of constraint route) form.On head node, MPLS traffic engineering tunnel is identified by the tunnel face of MPLS TE pattern.In the time that the outgoing interface of message is tunnel face, this message will forward by the CRLSP that forms MPLS traffic engineering tunnel.
MPLS by have same characteristic features (such as: destination address is identical) message be classified as a class, be called FEC(Forwarding Equivalence Class, forwarding equivalence class), the message that belongs to identical FEC obtains identical processing in MPLS network.Such as: the message that belongs to identical FEC forwards by same MPLS traffic engineering tunnel.
Summary of the invention
In view of this, the invention provides a kind of MPLS traffic engineering tunnel inking device and method, can reduce administrative staff's configuration effort amount.
Particularly, the present invention is achieved through the following technical solutions:
A kind of MPLS traffic engineering tunnel inking device, is applied on the network equipment, and described device comprises:
Tunnel storage unit, for saving as the predefine traffic engineering tunnel of the forwarding equivalence class FEC establishment that multiple destination addresses are identical, does not include bandwidth reserved in described predefine traffic engineering tunnel;
Route storage unit, for saving as the static routing of FEC configuration, includes the predefine traffic engineering tunnel of the required tunnel bandwidth of described FEC and binding in this static routing;
Automatically generation unit, for according to described static routing, for described FEC generates corresponding TE tunnel, the bandwidth reserved in described TE tunnel equals the required tunnel bandwidth of described FEC.
Further, the process that described route storage unit saves as the static routing of FEC configuration comprises, saves as respectively the static routing of each unshared FEC configuration, saves as a static routing of multiple FEC configurations of sharing same tunnel;
Described automatic generation unit is that the process that described FEC generates corresponding TE tunnel comprises, according to described static routing, be respectively each unshared FEC and generate corresponding TE tunnel, for the multiple FEC that share same tunnel generate a corresponding TE shared Sub tunnel.
Further, described device also comprises:
Tunnel delete cells, for deleting after static routing, deletes TE tunnel corresponding to described static routing or TE shared Sub tunnel.
Further, the process that described route storage unit saves as the static routing of FEC configuration comprises, save as respectively a static routing of default each group ACL configuration, in described static routing, include the required tunnel bandwidth of FEC that this group ACL is corresponding and the predefine traffic engineering tunnel of binding;
Described automatic generation unit is that the process that described FEC generates corresponding TE tunnel comprises, according to described static routing, for FEC corresponding to each group ACL generates corresponding TE tunnel.
Further, in described default each group ACL, include many rules, the wherein corresponding FEC of each rule, the required tunnel bandwidth of each FEC is identical;
When in one group of ACL, FEC corresponding to strictly all rules is unshared FEC, described automatic generation unit is that the process that each group FEC corresponding to ACL generates corresponding TE tunnel comprises, is respectively the unshared FEC that in this group ACL, strictly all rules is corresponding and generates corresponding TE tunnel;
When the FEC that strictly all rules is corresponding in one group of ACL shares same tunnel, described automatic generation unit is that the process that each group FEC corresponding to ACL generates corresponding TE tunnel comprises, is that multiple FEC in the shared same tunnel that in this group ACL, strictly all rules is corresponding generate a corresponding TE shared Sub tunnel.
Further, described device also comprises:
Tunnel delete cells, for deleting after the rule of ACL, deletes the corresponding TE of FEC tunnel corresponding to described rule.
Further, in described each default group ACL, include many rules, wherein have a rule at least to there being multiple FEC;
Described route storage unit, is further used for saving as the triggering static routing of the rule configuration to there being multiple FEC;
Described automatic generation unit, is further used for receiving coupling to should have the regular flow of multiple FEC time, for FEC corresponding to described flow generates corresponding TE tunnel.
A kind of MPLS traffic engineering tunnel collocation method, is applied on the network equipment, and described method comprises:
The predefine traffic engineering tunnel that saves as the forwarding equivalence class FEC establishment that multiple destination addresses are identical, does not include bandwidth reserved in described predefine traffic engineering tunnel;
Save as the static routing of FEC configuration, in this static routing, include the predefine traffic engineering tunnel of the required tunnel bandwidth of described FEC and binding;
According to described static routing, for described FEC generates corresponding TE tunnel, the bandwidth reserved in described TE tunnel equals the required tunnel bandwidth of described FEC.
Further, described in save as the static routing of FEC configuration process comprise, save as respectively the static routing of each unshared FEC configuration, save as a static routing of multiple FEC configurations of sharing same tunnel;
The described process that generates corresponding TE tunnel for described FEC comprises, according to described static routing, is respectively each unshared FEC and generates corresponding TE tunnel, is that the multiple FEC that share same tunnel generate a corresponding TE shared Sub tunnel.
Further, described method also comprises:
Deleting after static routing, delete TE tunnel corresponding to described static routing or TE shared Sub tunnel.
Further, the process of the static routing of the described FEC of saving as configuration comprises, save as respectively a static routing of default each group ACL configuration, in described static routing, include the required tunnel bandwidth of FEC that this group ACL is corresponding and the predefine traffic engineering tunnel of binding;
The described process that generates corresponding TE tunnel for described FEC comprises, according to described static routing, for FEC corresponding to each group ACL generates corresponding TE tunnel.
Further, in described default each group ACL, include many rules, the wherein corresponding FEC of each rule, the required tunnel bandwidth of each FEC is identical;
When in one group of ACL, FEC corresponding to strictly all rules is unshared FEC, the described process that generates corresponding TE tunnel for each group FEC corresponding to ACL comprises, is respectively the unshared FEC that in this group ACL, strictly all rules is corresponding and generates corresponding TE tunnel;
When the FEC that strictly all rules is corresponding in one group of ACL shares same tunnel, the described process that generates corresponding TE tunnel for each group FEC corresponding to ACL comprises, is that multiple FEC in the shared same tunnel that in this group ACL, strictly all rules is corresponding generate a corresponding TE shared Sub tunnel.
Further, described method also comprises:
After the rule of deleting in ACL, delete the corresponding TE of FEC tunnel corresponding to described rule.
Further, in described each default group ACL, include many rules, wherein have a rule at least to there being multiple FEC;
Described method also comprises:
Save as the triggering static routing of the rule configuration to there being multiple FEC;
Receiving coupling to should have the regular flow of multiple FEC time, for FEC corresponding to described flow generates corresponding TE tunnel.
Can be found out by above description, in the present invention, be the pre-configured predefined traffic engineering tunnels of multiple FEC by administrative staff, and then be the static routing of the described predefine traffic engineering tunnel of FEC configuration binding, according to described predefine traffic engineering tunnel and static routing, can automatically generate TE tunnel for FEC, greatly reduce administrative staff's configuration effort amount and complexity.
Brief description of the drawings
Fig. 1 is the building-block of logic of MPLS traffic engineering tunnel inking device in one embodiment of the present invention;
Fig. 2 is the schematic flow sheet of MPLS traffic engineering tunnel collocation method in one embodiment of the present invention;
Fig. 3 is that in one embodiment of the present invention, destination address is all 100 FEC route schematic diagrames of router D.
Embodiment
In configuration MPLS traffic engineering tunnel, because partial service needs different bandwidth reserveds, partial service needs identical bandwidth reserved, partial service is shared certain bandwidth reserved, in current realization, be generally same LSR(Label Switched Router, LSR) and share a MPLS traffic engineering tunnel of FEC configuration that uses certain bandwidth reserved, and bind this tunnel by static routing.For other FEC that do not share bandwidth reserved configure respectively MPLS traffic engineering tunnel, and corresponding static routing.For instance, there are 100 FEC to arrive an identical LSR by MPLS traffic engineering tunnel, if these 100 FEC do not share bandwidth reserved, keeper need to be respectively these 100 FEC and configure corresponding MPLS traffic engineering tunnel so, and configure respectively 100 static routing and bind corresponding MPLS traffic engineering tunnel, workload is huge, and easily occurs mistake.
In view of this, the invention provides a kind of MPLS traffic engineering tunnel allocation plan, by bandwidth reserved and MPLS traffic engineering tunnel configured separate, for arriving a predefined MPLS traffic engineering tunnel of FEC configuration of same destination address, then specify required bandwidth and predefine MPLS traffic engineering tunnel by static routing, realize and automatically issue tunnel configuration with this, and then automatically generate MPLS traffic engineering tunnel, to reduce configuration complexity, reduce administrative staff's workload.
Be embodied as example with software below, describe specific implementation of the present invention in detail.Mpls-te tunnel inking device provided by the invention, is applied on the network equipment, and the described network equipment includes but not limited to switch, router.As the operation carrier of apparatus of the present invention, the described network equipment at least includes conventionally: CPU, internal memory and nonvolatile memory, also may include the hardware such as various forwarding chips and I/O interface certainly.Please refer to Fig. 1 and Fig. 2, described device includes: tunnel storage unit, route storage unit, automatic generation unit and tunnel delete cells.In an exemplary embodiment, this device is carried out following treatment step in running:
Step 101, tunnel storage unit saves as the predefine traffic engineering tunnel of the forwarding equivalence class FEC establishment that multiple destination addresses are identical, in described predefine traffic engineering tunnel, does not include bandwidth reserved.
Step 102, route storage unit saves as the static routing of FEC configuration, includes the predefine traffic engineering tunnel of the required tunnel bandwidth of described FEC and binding in this static routing.
Step 103, generation unit is according to described static routing automatically, and for described FEC generates corresponding TE tunnel, the bandwidth reserved in described TE tunnel equals the required tunnel bandwidth of described FEC.
Can be found out by above step, for realizing the object that automatically generates traffic engineering tunnel in the present invention, for the multiple FEC that arrive same destination address, needing administrative staff is the pre-configured predefined traffic engineering tunnel of described multiple FEC.Described predefined traffic engineering tunnel is not actual traffic engineering tunnel, but is equivalent to female tunnel in logic.And then be the static routing of the described predefine traffic engineering tunnel of described FEC configuration binding by administrative staff.Described automatic generation unit is according to described predefine traffic engineering tunnel and static routing, follow-uply can automatically generate actual TE tunnel for described FEC.
Particularly, please refer to Fig. 3, suppose that router D issues 100 routes, be respectively 10.1.1.0/24 to 10.1.100.0/24, router-A is exactly 100 FEC to the business of these 100 destination addresses, and wishes that these FEC walk MPLS traffic engineering tunnel and forward.Administrative staff can give this 100 route numbering 1-100, wherein route 1-25 wishes that each FEC reserves 5M bandwidth resources, route 26-50 wishes that each FEC reserves 10M bandwidth resources, route 51-75 shares same tunnel, reserved 200M bandwidth resources, route 76-100 shares same tunnel, reserved 300M bandwidth resources.
Originally need to create 100 MPLS traffic engineering tunnels, in an exemplary configuration, taking bandwidth reserved wherein as the configuration of 5M as follows:
[RouterA]interface?tunnel1mode?mpls-te
[RouterA-Tunnel1]ip?address7.1.1.1255.255.255.0
[RouterA-Tunnel1]destination1.1.1.4
[RouterA-Tunnel1]mpls?te?signaling?rsvp-te
[RouterA-Tunnel1]mpls?te?bandwidth5000
[RouterA-Tunnel1]quit
Wherein, tunnel1 represents traffic engineering tunnel numbering, and ip address represents the source IP address of traffic engineering tunnel, the bandwidth reserved that bandwidth is this traffic engineering tunnel.
And in the present invention, administrative staff need to be only TE predefine tunnels of these 100 establishing routes, be called test as example taking this tunnel name, configuration change is as follows:
[RouterA]interface?tunnel?pre-tunnle?test?mode?mpls-te
[RouterA-Tunnel1]ip?address7.1.1.1255.255.255.0ingress0.0.1.0
[RouterA-Tunnel1]destination1.1.1.4
[RouterA-Tunnel1]mpls?te?signaling?rsvp-te
[RouterA-Tunnel1]using1to100
[RouterA-Tunnel1]quit
Contrast original configuration, in creating predefine traffic engineering tunnel, increased an optional parameters pre-tunnel, what represent now configuration is TE predefine tunnel, and test is predefine tunnel title.In the time of assigned ip Address, increase an optional parameters ingress, be used to specify the TE tunnel IP address change rule of automatic generation, ingress represents that IP address adopts the variation pattern increasing progressively, 0.0.1.0 represent that the 3rd changes, other positions are that 0 expression does not change, and the IP address in the Article 1 TE tunnel so automatically generating is 7.1.1.1, the IP address in Article 2 TE tunnel is 7.1.2.1, by that analogy.Order using1to100 is used for representing that this predefine tunnel can generate 1-100 strip tunnel.In configuration predefine traffic engineering tunnel, do not specify reserved bandwidth, bandwidth reserved is separated with tunnel configuration, can make the scope of application of predefine traffic engineering tunnel larger.Certainly, above configuration is an exemplary configuration mode, and those skilled in the art can carry out by other parameters or mode the configuration in predefine tunnel.
Described tunnel storage unit is preserved after above-mentioned predefined traffic engineering tunnel, and administrative staff then also need for each FEC configuration and the static routing of described predefine traffic engineering tunnel binding, and are preserved by described route storage unit.
Particularly, for the configuration of static routing, conventionally can be divided into two classes.One class is not share each other the FEC of traffic engineering tunnel, is referred to as unshared FEC.Another kind of is the FEC that shares same traffic engineering tunnel.Below this two class is described respectively.
For the FEC in unshared tunnel, administrative staff need to configure the static routing of binding with predefine traffic engineering tunnel one by one for each FEC, and are preserved respectively by described route storage unit.Such as, originally to realize FEC corresponding to 10.1.1.0/24 route to walk 1, one exemplary configuration of traffic engineering tunnel as follows:
[RouterA]ip?route-static10.1.1.024tunnel1preference1
And in the present invention, administrative staff need to specify reserved bandwidth in static routing, specifically can revise configuration as follows:
[RouterA]ip?route-static10.1.1.024tunnel?pre-tunnel?test?bandwidth5000preference1
Contrast original configuration, increased accordingly optional parameters pre-tunnel, what represent this static routing binding is predefine tunnel, according to design parameter, can automatically generate corresponding sub-tunnel.Increase optional parameters bandwidth, this order is with respect to bandwidth reserved order in original configuration traffic engineering tunnel " mpls tebandwidth ", and this parameter b andwidth is expressed as the bandwidth reserved configuration that the traffic engineering tunnel of automatic generation issues.Use mentioned order, static routing of every configuration, described automatic generation unit all can generate a TE tunnel and its correspondence automatically.With the example that is configured to of above-mentioned predefine traffic engineering tunnel and static routing, the TE tunnel automatically generating is as follows:
interface?tunnel1mode?mpls-te
ip?address7.1.1.1255.255.255.0
destination1.1.1.4
mpls?te?signaling?rsvp-te
mpls?te?bandwidth5000
And for the FEC that shares same tunnel, administrative staff need to be only route of binding with predefine traffic engineering tunnel of its configuration, described route storage unit also only needs to preserve a corresponding static routing.Particularly, in configuration, can increase optional parameters " shared ".Such as, can configuration order as follows for route 51:
[RouterA]ip?route-static10.1.51.024tunnel?pre-tunnel?test?bandwidth200000shared1preference1
Wherein, the Article 1 TE in the FEC of the shared parameter shared bandwidth reserved of " 1 " expression below shares tunnel.The TE shared Sub tunnel that described automatic generation unit generates automatically according to this static routing is as follows:
interface?tunnel51mode?mpls-te
ip?address7.1.51.1255.255.255.0
destination1.1.1.4
mpls?te?signaling?rsvp-te
mpls?te?bandwidth200000
MPLS traffic engineering tunnel allocation plan provided by the invention is supported the recovery in tunnel equally.In original configuration, because tunnel and static routing are separate configuration, so tunnel and route also can separately be deleted.If deletion tunnel, static routing due to specify tunnel do not had, the deletion so the configuration of static routing also can link.If deletion static routing, the tunnel of its binding can not be deleted, but corresponding FEC has forwarded with regard to not walking tunnel.And in the present invention, owing to taking the configuration mode of predefine traffic engineering tunnel, actual sub-tunnel is according to the automatic generation of static routing, so the sub-tunnel that design generates automatically does not allow deletion, but links and delete TE tunnel by deletion static routing.Particularly, if want to reclaim certain TE tunnel, administrative staff only need to delete the static routing into corresponding FEC configuration, and described route delete cells, after described static routing is deleted, is deleted TE tunnel corresponding to described static routing or TE shared Sub tunnel.
Can be found out by above description, MPLS traffic engineering tunnel allocation plan provided by the invention is by configuring TE predefine tunnel, can reduce administrative staff the quantity that configures actual traffic engineering tunnel.But for unshared FEC, administrative staff still need to configure one by one the static routing of binding with described predefine traffic engineering tunnel.One preferred embodiment in, the present invention introduces a kind of new departure, can be to ACL(Access Control List, Access Control List (ACL)) divide into groups, make the corresponding one group of FEC that bandwidth reserved is identical of each group ACL, then reduce the quantity of administrative staff's configuring static route by the unified static routing that configures binding predefine traffic engineering tunnel of FEC comprising for each group of ACL.
Particularly, ACL be made up of rule (rule) one by one, and the flow of a destination address of each rule permission passes through, and this destination address is the destination address of FEC namely.So, can be understood as all corresponding FEC of each rule in ACL.Still taking the situation shown in Fig. 3 as example.In these 100 FEC of route 1-100, in fact can be divided into 4 groups according to the difference of required bandwidth reserved.That is, route 1-25 is first group, needs bandwidth reserved 5M, and route 26-50 is second group, needs bandwidth reserved 10M, and route 51-75 is the 3rd group, shares bandwidth reserved 200M, and route 76-100 is the 4th group, shares bandwidth reserved 300M.Administrative staff, in configuration ACL, according to the grouping of above-mentioned FEC, can configure respectively 4 groups of ACL.And whether sharing the situation in tunnel according to FEC, these 4 groups of ACL can be divided into again two classes.First group and second group of ACL belong to a class, and in each group ACL, the corresponding FEC of each rule is unshared FEC.The 3rd group and the 4th group of ACL belong to a class, and the FEC that in each group, each rule is corresponding shares same tunnel.The specific implementation of the present embodiment is described from FEC two aspects in unshared FEC and shared same tunnel respectively below.
Please refer to a kind of exemplary configuration of first group of ACL:
[RouterA]acl?number3000name?user1
[RouterA-acl-adv-3000-user1]rule1permit?ip?destination10.1.1.00.0.0.255
[RouterA-acl-adv-3000-user1]rule2permit?ip?destination10.1.2.00.0.0.255
……
[RouterA-acl-adv-3000-user1]rule24permit?ip?destination10.1.24.00.0.0.255
[RouterA-acl-adv-3000-user1]rule25permit?ip?destination10.1.25.00.0.0.255
In configuring static route, administrative staff need to be only the static routing of a binding predefine traffic engineering tunnel of this group ACL configuration.In an exemplary configuration, corresponding static routing can configure as follows:
[RouterA]ip?route-static?acl3000tunnel?pre-tunnel?test?bandwidth5000preference1
Described automatic generation unit, according to above-mentioned static routing and first group of ACL, is respectively the unshared FEC that in this group ACL, strictly all rules is corresponding and generates corresponding TE tunnel:
Wherein, the IP address generating mode in TE tunnel is with previously described the same, and the parameter ingress being increased newly by predefine traffic engineering tunnel determines, is not repeated at this.
Be while sharing the FEC in same tunnel for FEC corresponding to strictly all rules in one group of ACL, please refer to a kind of exemplary configuration of the 3rd group of ACL:
[RouterA]acl?number3000name?user1
[RouterA-acl-adv-3002-user3]rule1permit?ip?destination10.1.51.00.0.0.255
[RouterA-acl-adv-3002-user3]rule2permit?ip?destination10.1.52.00.0.0.255
……
[RouterA-acl-adv-3002-user3]rule24permit?ip?destination10.1.74.00.0.0.255
[RouterA-acl-adv-3002-user3]rule25permit?ip?destination10.1.75.00.0.0.255
In configuring static route, administrative staff are the static routing of a shared binding predefine traffic engineering tunnel of this group ACL configuration.In an exemplary configuration, corresponding static routing can configure as follows:
[RouterA]ip?route-static?acl3002tunnel?pre-tunnel?test?bandwidth200000shared1preference1
Described automatic generation unit, according to above-mentioned static routing and the 3rd group of ACL, is that multiple FEC in the shared same tunnel that in this group ACL, strictly all rules is corresponding generate a corresponding TE shared Sub tunnel automatically:
#
interface?tunnel51mode?mpls-te
ip?address7.1.51.1255.255.255.0
destination1.1.1.4
mpls?te?signaling?rsvp-te
mpls?te?bandwidth200000
This shows, carry out corresponding all kinds of FEC with the each rule in ACL, be only required to be a corresponding static routing of each group ACL configuration, and no longer need one by one, for FEC configures corresponding static routing, greatly to have saved administrative staff's configuration effort amount.
For the deletion in TE tunnel, only need administrative staff in corresponding ACL, to delete corresponding rule just passable, described tunnel delete cells will be deleted the corresponding TE of FEC tunnel corresponding to described rule.It should be noted that, for the FEC that shares same tunnel, only delete wherein rule corresponding to some FEC, can't cause the deletion in this TE shared Sub tunnel.Only have and deleted after rules all in this group ACL, described tunnel delete cells just can be deleted corresponding TE shared Sub tunnel.
Preferably, in order further to reduce configuration, the present invention also provides a kind of tunnel generating mode of trigger-type, triggers the generation in tunnel by flow.Particularly, in the time configuring F EC by ACL, can further reduce configuration to the continuous network segment.For instance, for 100.1.1.0/24,100.1.2.0/24 and these three network segments of 100.1.3.0/24, can be write as 100.1.0.0/22 by the mode of change mask.100.1.0.0/22 this network segment can be split as 100.1.0.0/24,100.1.1.0/24,100.1.2.0/24 and 100.1.3.0/24, three network segments above of comparing actual needs configuration have had more network segment 100.1.0.0/24, in the time guaranteeing not have in network the flow of this network segment of 100.1.0.0/24, can adopt the mode of change mask.Particularly, for above-mentioned three network segments, administrative staff can directly be configured in ACL:
rule1permit?ip?destination100.1.0.00.0.3.255
This rule reality is to there being three FEC, and according to the aforesaid implementation of the present invention, described automatic generation unit only can generate a TE tunnel for this rule, but in fact will generate three TE tunnels for three network segments that this rule comprises.So the present embodiment design adopts the mode of flow triggering to generate TE tunnel.Particularly, administrative staff are can configure trigger static routing as follows:
[RouterA]ip?route-static?acl3000tunnel?pre-tunnle?test?bandwidth5000flow-active?preference1
In this triggering static routing, increased parameter f low-active newly, this Parametric Representation is by the generating mode in the sub-tunnel of flow triggering.Described automatic generation unit gets after the flow-active parameter triggering in static routing, just can for triggering static routing, this not generate corresponding TE tunnel at once, but in the time receiving the flow of coupling 100.1.1.0/24,100.1.2.0/24 and these three network segments of 100.1.3.0/24, the FEC corresponding for the described network segment generates TE tunnel.It should be noted that, reduce the configuration mode of the continuous network segment by the mode of change mask, must guarantee not have in network the flow of this network segment of 100.1.0.0/24, because in the time having the flow of this network segment of 100.1.0.0/24, described automatic generation unit can be also that this network segment generates a TE tunnel automatically.
Can be found out by above description, in the present invention, be the pre-configured predefined traffic engineering tunnels of multiple FEC by administrative staff, and then be the static routing of the described predefine traffic engineering tunnel of FEC configuration binding, according to described predefine traffic engineering tunnel and static routing, can automatically generate TE tunnel for FEC, greatly reduce administrative staff's configuration effort amount and complexity.
The foregoing is only preferred embodiment of the present invention, in order to limit the present invention, within the spirit and principles in the present invention not all, any amendment of making, be equal to replacement, improvement etc., within all should being included in the scope of protection of the invention.

Claims (14)

1. a multi-protocol label switching traffic engineering MPLS traffic engineering tunnel inking device, is applied on the network equipment, it is characterized in that, described device comprises:
Tunnel storage unit, for saving as the predefine traffic engineering tunnel of the forwarding equivalence class FEC establishment that multiple destination addresses are identical, does not include bandwidth reserved in described predefine traffic engineering tunnel;
Route storage unit, for saving as the static routing of FEC configuration, includes the predefine traffic engineering tunnel of the required tunnel bandwidth of described FEC and binding in this static routing;
Automatically generation unit, for according to described static routing, for described FEC generates corresponding TE tunnel, the bandwidth reserved in described TE tunnel equals the required tunnel bandwidth of described FEC.
2. device according to claim 1, is characterized in that,
The process that described route storage unit saves as the static routing of FEC configuration comprises, saves as respectively the static routing of each unshared FEC configuration, saves as a static routing of multiple FEC configurations of sharing same tunnel;
Described automatic generation unit is that the process that described FEC generates corresponding TE tunnel comprises, according to described static routing, be respectively each unshared FEC and generate corresponding TE tunnel, for the multiple FEC that share same tunnel generate a corresponding TE shared Sub tunnel.
3. device according to claim 2, is characterized in that, described device also comprises:
Tunnel delete cells, for deleting after static routing, deletes TE tunnel corresponding to described static routing or TE shared Sub tunnel.
4. device according to claim 1, is characterized in that,
The process that described route storage unit saves as the static routing of FEC configuration comprises, save as respectively a static routing of default each group ACL configuration, in described static routing, include the required tunnel bandwidth of FEC that this group ACL is corresponding and the predefine traffic engineering tunnel of binding;
Described automatic generation unit is that the process that described FEC generates corresponding TE tunnel comprises, according to described static routing, for FEC corresponding to each group ACL generates corresponding TE tunnel.
5. device according to claim 4, is characterized in that,
In described default each group ACL, include many rules, the wherein corresponding FEC of each rule, the required tunnel bandwidth of each FEC is identical;
When in one group of ACL, FEC corresponding to strictly all rules is unshared FEC, described automatic generation unit is that the process that each group FEC corresponding to ACL generates corresponding TE tunnel comprises, is respectively the unshared FEC that in this group ACL, strictly all rules is corresponding and generates corresponding TE tunnel;
When the FEC that strictly all rules is corresponding in one group of ACL shares same tunnel, described automatic generation unit is that the process that each group FEC corresponding to ACL generates corresponding TE tunnel comprises, is that multiple FEC in the shared same tunnel that in this group ACL, strictly all rules is corresponding generate a corresponding TE shared Sub tunnel.
6. device according to claim 4, is characterized in that, described device also comprises:
Tunnel delete cells, for deleting after the rule of ACL, deletes the corresponding TE of FEC tunnel corresponding to described rule.
7. device according to claim 4, is characterized in that,
In described each default group ACL, include many rules, wherein have a rule at least to there being multiple FEC;
Described route storage unit, is further used for saving as the triggering static routing of the rule configuration to there being multiple FEC;
Described automatic generation unit, is further used for receiving coupling to should have the regular flow of multiple FEC time, for FEC corresponding to described flow generates corresponding TE tunnel.
8. a MPLS traffic engineering tunnel collocation method, is applied on the network equipment, it is characterized in that, described method comprises:
The predefine traffic engineering tunnel that saves as the FEC establishment that multiple destination addresses are identical, does not include bandwidth reserved in described predefine traffic engineering tunnel;
Save as the static routing of FEC configuration, in this static routing, include the predefine traffic engineering tunnel of the required tunnel bandwidth of described FEC and binding;
According to described static routing, for described FEC generates corresponding TE tunnel, the bandwidth reserved in described TE tunnel equals the required tunnel bandwidth of described FEC.
9. method according to claim 8, is characterized in that,
The process of the static routing of the described FEC of saving as configuration comprises, saves as respectively the static routing of each unshared FEC configuration, saves as a static routing of multiple FEC configurations of sharing same tunnel;
The described process that generates corresponding TE tunnel for described FEC comprises, according to described static routing, is respectively each unshared FEC and generates corresponding TE tunnel, is that the multiple FEC that share same tunnel generate a corresponding TE shared Sub tunnel.
10. method according to claim 9, is characterized in that, described method also comprises:
Deleting after static routing, delete TE tunnel corresponding to described static routing or TE shared Sub tunnel.
11. methods according to claim 8, is characterized in that,
The process of the static routing of the described FEC of saving as configuration comprises, saves as respectively a static routing of each default group ACL configuration, includes the required tunnel bandwidth of FEC that this group ACL is corresponding and the predefine traffic engineering tunnel of binding in described static routing;
The described process that generates corresponding TE tunnel for described FEC comprises, according to described static routing, for FEC corresponding to each group ACL generates corresponding TE tunnel.
12. methods according to claim 11, is characterized in that,
In described default each group ACL, include many rules, the wherein corresponding FEC of each rule, the required tunnel bandwidth of each FEC is identical;
When in one group of ACL, FEC corresponding to strictly all rules is unshared FEC, the described process that generates corresponding TE tunnel for each group FEC corresponding to ACL comprises, is respectively the unshared FEC that in this group ACL, strictly all rules is corresponding and generates corresponding TE tunnel;
When the FEC that strictly all rules is corresponding in one group of ACL shares same tunnel, the described process that generates corresponding TE tunnel for each group FEC corresponding to ACL comprises, is that multiple FEC in the shared same tunnel that in this group ACL, strictly all rules is corresponding generate a corresponding TE shared Sub tunnel.
13. methods according to claim 11, is characterized in that, described method also comprises:
After the rule of deleting in ACL, delete the corresponding TE of FEC tunnel corresponding to described rule.
14. methods according to claim 11, is characterized in that,
In described each default group ACL, include many rules, wherein have a rule at least to there being multiple FEC;
Described method also comprises:
Save as the triggering static routing of the rule configuration to there being multiple FEC;
Receiving coupling to should have the regular flow of multiple FEC time, for FEC corresponding to described flow generates corresponding TE tunnel.
CN201410159015.2A 2014-04-18 2014-04-18 A kind of MPLS traffic engineering tunnels configuration device and method Active CN103916303B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410159015.2A CN103916303B (en) 2014-04-18 2014-04-18 A kind of MPLS traffic engineering tunnels configuration device and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410159015.2A CN103916303B (en) 2014-04-18 2014-04-18 A kind of MPLS traffic engineering tunnels configuration device and method

Publications (2)

Publication Number Publication Date
CN103916303A true CN103916303A (en) 2014-07-09
CN103916303B CN103916303B (en) 2018-01-09

Family

ID=51041719

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410159015.2A Active CN103916303B (en) 2014-04-18 2014-04-18 A kind of MPLS traffic engineering tunnels configuration device and method

Country Status (1)

Country Link
CN (1) CN103916303B (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104243268A (en) * 2014-09-19 2014-12-24 杭州华三通信技术有限公司 Association method and device between virtual extensible local area networks (VXLAN) and tunnel
WO2016165299A1 (en) * 2015-04-16 2016-10-20 中兴通讯股份有限公司 Node device and label forwarding table establishment method therefor
CN107995084A (en) * 2017-11-09 2018-05-04 新华三技术有限公司 Tunnel selecting method and device
CN108141410A (en) * 2015-10-17 2018-06-08 思科技术公司 For the make-before-break mechanism of label switched path
CN109525493A (en) * 2018-10-29 2019-03-26 中国联合网络通信集团有限公司 A kind of network path method for building up and device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101378349A (en) * 2007-08-30 2009-03-04 华为技术有限公司 Method for calculating data transmission tunnel and device for managing data transmission tunnel
CN101594289A (en) * 2008-05-28 2009-12-02 华为技术有限公司 Realize the method and apparatus of Differentiated Services traffic engineering
US20130259067A1 (en) * 2012-03-27 2013-10-03 Eci Telecom Ltd. Method for Providing an MPLS Tunnel with Shared Bandwidth

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101378349A (en) * 2007-08-30 2009-03-04 华为技术有限公司 Method for calculating data transmission tunnel and device for managing data transmission tunnel
CN101594289A (en) * 2008-05-28 2009-12-02 华为技术有限公司 Realize the method and apparatus of Differentiated Services traffic engineering
US20130259067A1 (en) * 2012-03-27 2013-10-03 Eci Telecom Ltd. Method for Providing an MPLS Tunnel with Shared Bandwidth

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104243268A (en) * 2014-09-19 2014-12-24 杭州华三通信技术有限公司 Association method and device between virtual extensible local area networks (VXLAN) and tunnel
CN104243268B (en) * 2014-09-19 2017-05-10 新华三技术有限公司 Association method and device between virtual extensible local area networks (VXLAN) and tunnel
US11012261B2 (en) 2014-09-19 2021-05-18 Hewlett Packard Enterprise Development Lp Associating VXLANs with tunnels
WO2016165299A1 (en) * 2015-04-16 2016-10-20 中兴通讯股份有限公司 Node device and label forwarding table establishment method therefor
CN108141410A (en) * 2015-10-17 2018-06-08 思科技术公司 For the make-before-break mechanism of label switched path
CN107995084A (en) * 2017-11-09 2018-05-04 新华三技术有限公司 Tunnel selecting method and device
CN107995084B (en) * 2017-11-09 2020-12-01 新华三技术有限公司 Tunnel selection method and device
CN109525493A (en) * 2018-10-29 2019-03-26 中国联合网络通信集团有限公司 A kind of network path method for building up and device

Also Published As

Publication number Publication date
CN103916303B (en) 2018-01-09

Similar Documents

Publication Publication Date Title
EP3817446B1 (en) Method and apparatus for creating network slices
CN111385206B (en) Message forwarding method, network system, related equipment and computer storage medium
US7602702B1 (en) Fast reroute of traffic associated with a point to multi-point network tunnel
Filsfils et al. Segment routing use cases
CN104954288B (en) Method for sending information, device and communication system
CN105051688A (en) Extended tag networking
EP2541847B1 (en) Method and system for establishing an associated bidirectional label-switched path
CN103916303A (en) MPLS TE tunnel configuration device and method
US9832121B1 (en) Next hop instruction associations for forwarding unit programming within a network device
CN104429021A (en) System and method for efficient point-to-multi-point traffic engineering (P2MP-TE) path protection
CN103493443B (en) Subpath maintenance unit (SPME) is used to share grid protection for multiprotocol label switching (MPLS)
US20170310581A1 (en) Communication Network, Communication Network Management Method, and Management System
CN103078794B (en) A kind of Message processing control method and device
CN106936713A (en) A kind of label management method, data flow processing method and equipment
US11509588B2 (en) Method and apparatus for service provision in a communication network
US7463580B2 (en) Resource sharing among network tunnels
CN113395735A (en) Message transmission method, device and network equipment
EP2648382B1 (en) Method, device and system for establishing lsp
CN112436990B (en) Data forwarding method, data forwarding equipment and computer-readable storage medium
CN109600291B (en) Cross-domain QoS (quality of service) adjusting method and device
CN102480377B (en) Management method and system of aggregation link
CN104618235B (en) A kind of cross-layer establishes the method and device in Bu Gong roads path
CN106330701B (en) Rapid rerouting method and device for ring network
CN109327390B (en) Traffic scheduling method and device
CN108123871B (en) Equivalent multipath ECMP processing method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into 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: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No.

Applicant before: Huasan Communication Technology Co., Ltd.

GR01 Patent grant
GR01 Patent grant