ned:

1.  When a node is affected by a CP failure and it attempts to recover its RSVP-TE state, synchronization becomes very difficult. This process involves synchronization with the neighbors, with the DP and with the NMP. Any of these three steps might fail for different reasons and this can directly impact the knowledge and states of the neighboring nodes. Such a process pertains mainly to the CP and possibly would affect only some of the connections. However, the fact is that an unsuccessful process of synchronization might lead to nodes operating in a state which is erroneous and potentially influencing the node’s service delivery capability.

2.  If a node fails, the neighbors of a node must update their state and the state of the network. In time, the neighbors will have moved towards a state they are not “used to be”, i.e., an untypical state (the typical state is when everything is properly functioning). Under this situation, the neighbors might move closer to an unstable state of operation (e.g., if a node switches from a functioning to non-functioning state and vice versa) and this can potentially bring these nodes into a dysfunctional state.

3.  Carrier-class components are typically undergoing very stringent tests and the requirements for robustness are extensive. Nevertheless, it is still possible to observe implementations where a failure in one single process might bring other processes in the same node to stop functioning. For example, this can occur if processes (routing and signaling) share CPUs (which might suffer HW/SW problems) or if they share memory (buffer overflows).

Finally, the TO indicated that RSVP-TE is highly vulnerable to problems, and when problems occur, recovering the functional state in the network is much more difficult (due to the synchronization process described earlier). OSPF (Open Shortest Path First) failures are simpler to fix and synchronization between nodes might be established in a shorter period of time. Nevertheless, mis-configured routing is one of the m