Label switched path reporting
First Claim
1. A method comprising:
- receiving, by a first network device that is not an ingress label edge router (LER) for a traffic engineering label switched path (TE LSP) and from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for the TE LSP through a network;
generating, by the first network device in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP; and
sending, by the first network device to a path computation element (PCE) for a path computation domain that includes the ingress LER for the TE LSP, the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP.
1 Assignment
0 Petitions
Accused Products
Abstract
Techniques are described for reporting, by non-ingress routers for traffic engineering label switched paths (TE LSPs) and to a path computation element, actual paths taken by the TE LSPs through the network. A first network device: receives, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for TE LSP through a network, wherein the first network device is not an ingress label edge router for the TE LSP; generates, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP; and sends, to a path computation element, the LSP path report message to notify the PCE.
-
Citations
23 Claims
-
1. A method comprising:
-
receiving, by a first network device that is not an ingress label edge router (LER) for a traffic engineering label switched path (TE LSP) and from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for the TE LSP through a network; generating, by the first network device in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP; and sending, by the first network device to a path computation element (PCE) for a path computation domain that includes the ingress LER for the TE LSP, the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A first network device comprising:
-
one or more processors coupled to a memory; a routing protocol daemon configured for execution by the one or more processors to receive, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for a traffic engineering label switched path (TE LSP) through a network, wherein the first network device is not an ingress label edge router (LER) for the TE LSP; and a path computation client configured for execution by the one or more processors to generate, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP, wherein the path computation client is further configured to send, to a path computation element (PCE) for a path computation domain that includes the ingress LER for the TE LSP, the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18)
-
-
19. A system comprising:
-
a software-defined networking (SDN) controller for a network, the SDN controller comprising a path computation element (PCE) for a path computation domain of a network; a second network device of the network; a first network device of the network, the first network device configured to receive, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for a traffic engineering label switched path (TE LSP) through a network, wherein the first network device is not an ingress label edge router (LER) for the TE LSP, and wherein the path computation domain includes the ingress LER for the TE LSP, wherein the first network device is further configured to generate, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP, and wherein the first network device is further configured to send, to the SDN controller, the LSP path report message to notify the SDN controller of the at least the sub-path of the path for the TE LSP. - View Dependent Claims (20)
-
-
21. A first network device comprising:
-
one or more processors coupled to a memory; a routing protocol daemon configured for execution by the one or more processors to receive, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for a traffic engineering label switched path (TE LSP) through a network; and a path computation client configured for execution by the one or more processors to generate, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP and an indication that the first network device is one of an ingress label edge router (LER), a transit label switching router, and an egress LER for the TE LSP, wherein the path computation client is further configured to send, to a path computation element (PCE), the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP. - View Dependent Claims (22, 23)
-
Specification