Patent Application
20140269737
The invention relates to the field of communication networks such as multi-protocol label switching (MPLS) networks and, more particularly but not exclusively, to an Area Border Router (ABR) awareness mechanism for Label Switched Paths (LSP).
Multiprotocol Label Switching (MPLS) enables efficient delivery of a wide variety of differentiated, end-to-end services. Multiprotocol Label Switching (MPLS) traffic engineering (TE) provides a mechanism for selecting efficient paths across an MPLS network based on bandwidth considerations and administrative rules. Each label switching router maintains a TE link state database with a current network topology. Once a path is computed, TE is used to maintain a forwarding state along that path.
As described in more detail in various Internet Engineering Task Force (IETF) Requests for Comment (RFC), such as RFC4726 and RFC5151, an Area Border Router (ABR) is a router located between several areas in a hierarchical Open Shortest Path First (OSPF) network. ABRs maintain topology information from multiple areas. In the case of Resource Reservation Protocol (RSVP) Inter-Domain TE-LSPs of type Contiguous LSP each Area Border Router (ABR) triggers a path computation (also referred to as an Explicit Route Object (ERO) expansion), before forwarding the RSVP Path message downstream. Thus, each ABR is responsible for calculating TE constrained path for its successive TE-Domain(s) or Area(s).
Every such ABR that triggers path computation for its TE-Domain can have multiple equal-cost paths and has to choose one of them. Currently this is achieved by configuring and signaling the ABR node as a so-called “loose-hop” via a RSVP Hop object, and configuring an option on the ABR to perform a Constrained Shortest Path First (CSPF) computation for the next segment.
Unfortunately, this mechanism is unwieldy and does not scale well.
Various deficiencies in the prior art are addressed by systems, methods and apparatus for causing network routers such as Area Border Routers (ABRs) to perform an ERO expansion in response to ERO expansion trigger indicia included within an RSVP Path message.
Various embodiments provide systems, methods and apparatus forwarding, toward a next hop in a label switched path (LSP), an RSVP Path message including ERO expansion trigger indicia associated with one or more provider edge (PE) routers.
Various embodiments provide systems, methods and apparatus for triggering a Constrained Shortest Path First (CSPF) computation at one or more provider routers within a label switched path (LSP) by forwarding to a next hop an RSVP Path message including an Explicit Route Object (ERO) having an ERO sub-object including a first flag, said first flag being set to a first state to indicate that a router is an Area Border Router (ABR) and set to a second state to indicate that the router is not an ABR.
The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
Various embodiments will be described within the context of a network supporting Resource Reservation Protocol (RSVP) Inter-Domain Traffic Engineering Label Switched Paths (TE-LSPs) of type Contiguous LSP, such as defined in IETF RFC4726 and RFC5151, each of which is incorporated by reference in its respective entirety.
The network 100 includes three IP/MPLS communication networks (CN) 105-1, 105-2 and 105-3, where each communication network 105 is associated with a respective area. The network 100 also includes at least one network management system (NMS) 120. As depicted, NMS 120 is operative to control a plurality of routers 110-1 through 110-11 distributed among the communication network areas 105-1 through 105-3.
First area 105-1 comprises the first 110-1, second 110-2 and fourth 110-4 routers, second area 105-2 comprises the third 110-3, fifth 110-5, sixth 110-6 and seventh 110-7 routers, while third area 105-3 comprises the eighth 110-8, ninth 110-9, tenth 110-10 and eleventh 110-11 routers. It is noted that various routers are interconnected to form thereby paths. Specifically, the following sequence of router connections is depicted in
The third 110-3 (R3) and fifth 110-5 (R5) routers operate as Area Border Routers (ABRs) separating the first 105-1 and second 105-2 areas. Similarly the sixth 110-6 (R6) and seventh 110-7 (R7) routers operate as ABRs separating the second 105-2 and third 105-3 areas.
Data packets or datagrams are routed according to ingress and egress virtual connection (VC) labels on a per-service basis. The VC labels are used by the PE routers 130 for demultiplexing traffic arriving from different services over the same set of LSP tunnels.
The NMS 120 is a network management system adapted for performing the various management functions described herein. The NMS 120 is adapted to communicate with nodes of CN 105. The NMS 120 may also be adapted to communicate with other operations support systems (e.g., Element Management Systems (EMSs), Topology Management Systems (TMSs), and the like, as well as various combinations thereof).
The NMS 120 may be implemented at a network node, network operations center (NOC) or any other location capable of communication with the CN 105 and various elements related thereto. The NMS 120 may support user interface capabilities to enable one or more users to perform various network management, configuration, provisioning or control related functions (e.g., enter information, review information, initiate execution of various methods as described herein and the like). Various embodiments of the NMS 120 are adapted to perform functions as discussed herein. The NMS 120 may be implemented as a general purpose computing device or specific purpose computing device, such as described below with respect to
The NMS 120 and the various routers 110 operate to support Resource Reservation Protocol (RSVP) Inter-Domain Traffic Engineering Label Switched Paths (TE-LSPs) of type Contiguous LSP.
Various embodiments utilize an RSVP path message modified to include additional information adapted to identify which nodes are ABRs or are to be treated as ABRs. In this manner, the need to define ABR nodes as loose hop nodes is avoided.
In one embodiment, an RSVP path message created by an ingress node (e.g., router R1) includes an Explicit Route Object (ERO) such as defined in IETF RFC 3209, and further includes ERO sub-object information identifying specific routers as ABRs, or routers to be treated as ABRs. When the ERO is present, the Path message is forwarded towards its destination along a path specified by the ERO. Each node along the path records the ERO in its path state block. Nodes may also modify the ERO before forwarding the Path message. This mechanism is adapted by including within the ERO information identifying ABR nodes and/or nodes to be treated as ABR nodes.
Various embodiments contemplate nodes or routers being configured to be responsive to the various RSVP path messages defined herein to perform an ERO expansion, Constrained Shortest Path First (CSPF) computation and the like as described herein.
Various embodiments contemplate nodes or routers being configured to be responsive to network management system commands such as to modify the ERO information identifying ABR nodes and/or nodes to be treated as ABR nodes.
TLV Attribute
Various embodiments enable the communication of ABR indicative information using a new flag or bit setting in an existing LSP attribute or, optionally, a newly defined LSP attribute encoded in Type-Length-Value (TLV) format.
Various embodiments enable the communication of loose-loose hop indicative information using a new flag or bit setting in an existing LSP attribute or, optionally, a newly defined LSP attribute encoded in Type-Length-Value (TLV) format.
In one embodiment, to specifically indicate which node or nodes in an LSP are to be treated as an ABR, one or more of the bits within an ERO sub-object, existing LSP attribute TLV and/or newly defined LSP attribute TLV is set or cleared, such as an attribute TLV according to RFC5420.3. For example, attributes carried by new objects are encoded within TLVs as follows, where a Type Field is an identifier of the TLV, a Length Field is used to indicate the total length of the TLV in octets, and a Value Field is used to carry the data.
In one embodiment, specific bits within the Reserved field (or other field) are used to indicate whether or not the hop having an address indicated by the ERO sub-object is an ABR, whether the hop is to be considered as loose-loose hop, and so on. The specific bits denoted herein to provide these indications are for illustrative purposes only. Different bits within the reserved field or other fields may be used to provide these indications.
For example, in one embodiment a specific bit number(s) (e.g., bit 0, bit 3, bit 4 or some other bit) is assigned a designation of “ABR Bit” or “ABR Flag” or some other designation. If the ABR Bit or Flag is set, then the hop indicated by the ERO sub-object is to be treated as an ABR such that an ERO expansion or Constrained Shortest Path First (CSPF) computation is to be performed. Optionally, a different specific bit number is assigned a designation of “loose-loose Bit” (“L Bit”) or “loose-loose Flag” (“L Flag”) or some other designation. If the L Bit or L Flag is set, then the hop indicated by the ERO sub-object is to be treated as a loose-loose hop.
Thus, in various embodiments an indication of an ABR node and/or a loose-loose hop is provided via a LSP attribute encoded in Type-Length-Value (TLV) format. In particular, a state of a predefined bit of a LSP_ATTRIBUTES object is used to indicate an ABR node and/or a loose-loose hop.
In various embodiments, modifications to selected cost constraint are communicated via additional bits in the LSP_ATTRIBUTES object. For example, additional bits can be used to provide additional information for use in the LSP path calculation, such as service provider preferences, user preferences, historical or instantaneous loading/congestion and so on. Each of these and other factors may be assigned a cost and the use or weight of this cost may be adapted over time.
Thus, various embodiments contemplate an LSP_ATTRIBUTES object, ERO object, ERO sub-object and the like having one or more bits or flags indicative of whether a node is an ABR and/or loose-loose node. Additional embodiments contemplate one or more bits associated with a modification to the selected metric or cost constraint due to any of service provider preferences, user preferences, historical or instantaneous loading/congestion and the like.
In various embodiments, the ABR Bit comprises bit 0 of eh Reserved Field and the L Bit comprises bit 1 of the Reserved Field.
As previously noted, each of the ABRs depicted in the network 105 of
The LSP setup is typically defined at the Ingress Label Edge Routers (LERs). Thus, for example, the various ABR and L flags may be set to appropriate states as the LER generates an ERO for the LSP. In various embodiments, the various ABR and L flags may be adapted to be subsequent nodes (ABR or otherwise) within the LSP, such as in response to a NMS command.
At step 210, an ingress LER selects various nodes to form thereby an LSP between the ingress LER and an egress LER.
At step 220, one or more nodes are identified as ABR nodes or to be treated as ABR nodes. Referring to box 225, the ABR identified nodes may be preferred LSP nodes, backup LSP nodes, alternative LSP nodes and/or other nodes.
At step 230, any nodes to be treated as loose-loose hop nodes are identified. As with the ABR nodes identified at step 220/225, the loose-loose hop nodes may be preferred LSP nodes, backup LSP nodes, alternative LSP nodes and/or other nodes.
At step 240, the ABR nodes and any loose-loose nodes are indicated as such within the context of an RSVP Path message. Referring to box 245, such indications may be made according to an ABR Bit, ABR Flag, L Bit, L Flag and the like as discussed herein via any of a new or existing LSP attribute encoded in a Type-Length-Value (TLV) format, via an ERO object, via an ERO sub-object and the like.
At step 250, the RSVP Path message is transmitted toward a next hop.
At step 260, the RSVP message is received by a node (e.g., next hop node) such as a primary LSP router or ABR, secondary LSP router or ABR or other node.
At step 270, the receiving node inspects the RSVP Message to determine if it is associated with an ABR and/or loose-loose identification, and responds as appropriate.
If defined as an ABR then the receiving node performs an ERO expansion whether or not the next hop is a loose hop (i.e., not directly connected to the receiving node). Thus, even if the next hop is a strict hop (i.e., directly connected to the receiving node), an ERO expansion is performed. If defined as loose-loose, then an ERO expansion operation is performed to reach the next loose hop.
At step 280, the receiving node optionally modifies the RSVP message, such as in response to NMS commands, EOR expansion and the like. Modification to the RSVP Path message may be performed using any of the techniques described herein, such as described above with respect to steps 210-240.
At step 290, the receiving node forwards the modified or unmodified RSVP Path message toward the next hop.
Example of LSP Setup with ABR Node Indication
The various embodiments described herein provide a mechanism for LSP setup with ABR node indication in, illustratively, an ERO sub-object. As an example, and referring to
The Ingress LER creates an RSVP Path message with ERO as specified in RFC 3209, and sets the ABR Bit or Flag as discussed above to indicate that hops R3, R8 and R11 are the ABR nodes.
When the path message is received by a node defined as an ABR node (such as R3 or R8), the receiving node performs a CSPF computation to reach the next ABR in the ERO. In this manner, a rapid setup of an inter-domain TE LSP is provided.
Advantageously, the various embodiments eliminate the need to necessarily define ABR nodes as loose hop nodes and having a configuration knob on the ABR nodes to perform ERO expansion. Further, since an ABR node may be indicated in, illustratively, the ERO sub-object, it can also be a strict hop. In this manner, additional flexibility is provided by allowing non-ABR nodes (i.e., routers between ABR nodes) to be defined or treated as ABR nodes.
Examples of LSP Setup with ABR as Loose-Loose Hop
The various embodiments described herein provide a mechanism for LSP setup with loose-loose hop indication in, illustratively, an ERO sub-object. As an example, and referring to
The Ingress LER creates an RSVP Path message with ERO as specified in RFC 3209, and sets the ABR Bit or Flag as discussed above to indicate that hops R3, R8 and R11 are the ABR nodes.
The Ingress LER additionally sets the L Bit or Flag as discussed above to indicate that one or more ABR nodes are loose-loose (e.g., L bit in the ERO sub-object is set in addition to ABR bit).
For a hop considered as loose-loose, when the LSP setup does not succeed using the loose hop defined in the ERO sub-object (e.g., network reachability problem or constraints not being met via the loose hop), the hop may be avoided (excluded) such that LSP setup operates to bypass the hop. Similarly, when the LSP setup does succeed using the loose hop defined in the ERO sub-object (e.g., network reachability problem resolved or constraints now met via the loose hop), the hop may now be included such that LSP setup may operate to include the hop.
If the ingress LER determines that a path can be found to a loose-loose ABR node (i.e., the node is now reachable), then the RSVP Path message to establish the LSP would be generated and sent towards the next hop.
When the path message is received by a node defined as an ABR node (such as R3 or R8), the receiving node performs a CSPF computation to reach the next ABR in the ERO. In this manner, a rapid setup of an inter-domain TE LSP is provided. If due to network failures and the like, the receiving node (e.g., R3) is unable to find a path to a loose-loose defined next node (e.g., R8), then the receiving node would perform an ERO expansion to determine a path toward the egress LER (e.g., R11).
In this manner, LSP setup is achieved while avoiding ABR node R8, which is unreachable, outside of the required constraints, possessing insufficient bandwidth or QoS and the like).
As depicted in
It will be appreciated that the functions depicted and described herein may be implemented in software and/or in a combination of software and hardware, e.g., using a general purpose computer, one or more application specific integrated circuits (ASIC), and/or any other hardware equivalents. In one embodiment, the cooperating process 305 can be loaded into memory 304 and executed by processor 303 to implement the functions as discussed herein. Thus, cooperating process 305 (including associated data structures) can be stored on a computer readable storage medium, e.g., RAM memory, magnetic or optical drive or diskette, and the like.
It will be appreciated that computing device 300 depicted in
It is contemplated that some of the steps discussed herein as software methods may be implemented within hardware, for example, as circuitry that cooperates with the processor to perform various method steps. Portions of the functions/elements described herein may be implemented as a computer program product wherein computer instructions, when processed by a computing device, adapt the operation of the computing device such that the methods and/or techniques described herein are invoked or otherwise provided. Instructions for invoking the inventive methods may be stored in tangible and non-transitory computer readable medium such as fixed or removable media or memory, transmitted via a tangible or intangible data stream in a broadcast or other signal bearing medium, and/or stored within a memory within a computing device operating according to the instructions.
Although various embodiments which incorporate the teachings of the present invention have been shown and described in detail herein, those skilled in the art can readily devise many other varied embodiments that still incorporate these teachings. Thus, while the foregoing is directed to various embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. As such, the appropriate scope of the invention is to be determined according to the claims.
This application claims the benefit of pending U.S. Provisional Patent Application Ser. No. 61/676,796, filed Jul. 27, 2012, entitled SYSTEM, METHOD AND APPARATUS FOR IMPROVED MPLS MANAGEMENT, which application is incorporated herein by reference in its entirety.
