An upstream node, which is upstream from a downstream protected node in a primary label switched path (201, 203), LSP, in a network, wherein the upstream node comprises: a processor configured to: receive node protection backup route data from the downstream protected node, wherein traffic is transmitted from the upstream node to a receiver (208, 212), passing through the downstream protected node and at least one merge point node (206, 210); determine at least one backup LSP (218, 220) for the primary LSP (201, 203)according to the node protection backup route data, wherein the backup LSP (218, 220) does not include the downstream protected node; transmit traffic to the at least one merge point node (206, 210) along the backup LSP (218, 220) using forwarding information contained in the node protection backup route data following failure of the downstream protected node; cease transmitting traffic along the backup LSP (218, 220) using the forwarding information following a trigger event; and delete the backup LSP (218, 220) when the backup LSP (218, 220) is no longer needed; wherein the trigger event is selected from one of the following: expiration of label reserve timer; and receipt of a make before break, MBB, route completion status message. a processor configured to: receive node protection backup route data from the downstream protected node, wherein traffic is transmitted from the upstream node to a receiver (208, 212), passing through the downstream protected node and at least one merge point node (206, 210); determine at least one backup LSP (218, 220) for the primary LSP (201, 203)according to the node protection backup route data, wherein the backup LSP (218, 220) does not include the downstream protected node; transmit traffic to the at least one merge point node (206, 210) along the backup LSP (218, 220) using forwarding information contained in the node protection backup route data following failure of the downstream protected node; cease transmitting traffic along the backup LSP (218, 220) using the forwarding information following a trigger event; and delete the backup LSP (218, 220) when the backup LSP (218, 220) is no longer needed; receive node protection backup route data from the downstream protected node, wherein traffic is transmitted from the upstream node to a receiver (208, 212), passing through the downstream protected node and at least one merge point node (206, 210); determine at least one backup LSP (218, 220) for the primary LSP (201, 203)according to the node protection backup route data, wherein the backup LSP (218, 220) does not include the downstream protected node; transmit traffic to the at least one merge point node (206, 210) along the backup LSP (218, 220) using forwarding information contained in the node protection backup route data following failure of the downstream protected node; cease transmitting traffic along the backup LSP (218, 220) using the forwarding information following a trigger event; and delete the backup LSP (218, 220) when the backup LSP (218, 220) is no longer needed; wherein the trigger event is selected from one of the following: expiration of label reserve timer; and receipt of a make before break, MBB, route completion status message. expiration of label reserve timer; and receipt of a make before break, MBB, route completion status message.