Techniques for performing a failover from a protected connection to a backup connection

1. A router comprising:

a control plane; and

a data plane comprising a linecard;

wherein the linecard is adapted to:

store information identifying a plurality of protected connections and a backup connection for each protected connection in the plurality of protected connections, wherein the information is received by the linecard prior to the occurrence of a network event;

receive a message from the control plane, the message generated by the control plane upon the occurrence of the network event;

determine, based upon the message and the stored information, a set of protected connections from among the plurality of protected connections, the set of protected connections including multiple connections to be failed over; and

for each connection from the set of protected connections:

determine, based upon the stored information, a backup connection for the protected connection; and

perform a failover for the protected connection to the determined backup connection.

2. The router of claim 1 wherein the plurality of protected connections comprises protected label switched paths (LSPs).

3. The router of claim 1 wherein:

the network event indicates that an interface has failed; and

information identifying the interface is included in the message sent to the linecard.

4. The router of claim 3 wherein the linecard is adapted to:

identify the set of protected connections to include protected connections from the plurality of protected connections that use the interface identified in the message, wherein the identified interface is as an egress interface.

5. The router of claim 3 wherein the linecard is adapted to:

determine, from a data structure storing information about a plurality of egress interfaces, a first entry corresponding to the interface identified in the message received from the control plane; and

determine the set of protected connections to be failed over using the first entry.

6. The router of claim 1 wherein the control plane is adapted to:

determine two or more protected connections to be failed over due to the network event;

include, in the message sent to the linecard, information identifying each of the two or more protected connections.

7. The router of claim 6 wherein:

each of the two or more protected connections is a protected label switched path (LSP); and

the message comprises an in-label for each of the two or more protected connections.

8. The router of claim 6 wherein:

the network event indicates a reduction in bandwidth on a link; and

the control plane is adapted to determine the two or more protected connections to be failed over from connections supported by the link.

9. The router of claim 6 wherein:

the network event indicates a priority-related event for a first connection; and

the control plane is adapted to determine the two or more protected connections to be failed over based on the priority-related event for the first connection.

10. A method comprising:

storing, by a linecard in a router, information identifying a plurality of protected connections and a backup connection for each protected connection in the plurality of protected connections, wherein the information is received by the linecard prior to the occurrence of a network event;

sending, by a control plane in the router, a message to the linecard in the router, the message generated by control plane upon the occurrence of the network event; and

upon the linecard receiving the message from the control plane:

determining, by the linecard, based upon the message and the stored information, a set of protected connections from among the plurality of protected connections, the set of protected connections including connections to be failed over; and

for each connection from set of protected connections:

determining, by the linecard, based upon the stored information, a backup connection for the protected connection; and

performing, by the linecard, a failover for the protected connection to the determined backup connection.

11. The method of claim 10 wherein the plurality of protected connections comprises protected label switched paths (LSPs).

12. The method of claim 10 wherein the network event indicates that an interface has failed, the method further comprising;

including, by the control plane, information identifying the interface in the message sent to the linecard.

13. The method of claim 12 wherein determining the set of protected connections comprises:

identifying the set of protected connections to include protected connections from the plurality of protected connections that use the interface identified in the message, wherein the identified interface is as an egress interface.

14. The method of claim 12 wherein determining the set of protected connections comprises:

determining, from a data structure storing information about a plurality of egress interfaces, a first entry matching the interface identified in the message received from the control plane; and

determining the set of protected connections to be failed over using the first entry.

15. The method of claim 10 wherein:

determining, by the control plane, two or more protected connections to be failed over due to the network event; and

sending the message to the linecard comprises including in the message, by the control plane, information identifying each of the two or more protected connections.

16. The method of claim 15 wherein:

each of the two or more connections is a protected label switched path (LSP); and

the message comprises an in-label for each of the two or more protected connections.

17. The method of claim 15 wherein the network event indicates a reduction in bandwidth on a link, the method further comprising:

determining, by the control plane, the two or more protected connections to be failed over from connections supported by the link.

18. The method of claim 15 wherein the network event indicates a priority-related event for a first connection, the method further comprising:

determining, by the control plane, the two or more protected connections to be failed over based on the priority-related event for the first connection.

19. A computer-readable memory storing a plurality of instructions for controlling a router device, the plurality of instructions comprising:

instructions that cause a linecard in the router device to store information identifying a plurality of protected connections and a backup connection for each protected connection in the plurality of protected connections, wherein the information is received by the linecard prior to the occurrence of a network event;

instructions that cause a control plane in the router device to send a message to the linecard in the router device, the message generated by the control plane upon the occurrence of the network event;

upon the linecard receiving the message from the control plane, instructions that cause the linecard to:

determine, based upon the message and the stored information, a set of protected connections from among the plurality of protected connections, the set of protected connections including connections to be failed over; and

for each connection from the set of protected connections, instructions that cause the linecard to:

determine, based upon the stored information, a backup connection for the protected connection; and

perform a failover for the protected connection to the determined backup connection.

20. The computer-readable memory of claim 19 wherein the network event indicates that an interface has failed, and wherein the plurality of instructions further comprise instructions that cause the linecard to determine the set of protected connections to include protected connections from the plurality of protected connections that use the interface identified in the message, wherein the identified interface is an egress interface.

21. The computer-readable memory of claim 19 wherein the message sent to the linecard identifies two or more protected connections to be failed over.