Fate sharing in networking – Is fate sharing bad thing in network design? Someone asked this question recently on my youtube channel and I want to share a post for the website followers as well.
First of all, what is fate sharing ? Below is the Wikipedia definition of fate sharing.
” Fate-sharing is an engineering design philosophy where related parts of a system are yoked together, so that they either fail together or not at all “
We use this term a lot of time when we suggest a design recommendation for Multi Service PE (Provider Edge) devices in the Service Provider networks. Multi Service PE provides more than one service in the Service Provider networks.
Many Service Providers follow this design philosophy. Main reason for SPs to use more than one service (Ex: Internet and VPN) on the same router is cost. In order to reduce cost by better utilizing the router resources is not a bad idea but there is a fate sharing in this case.
Internet based attack can bring down the Multi Service PE and VPN customers on the same device are affected as well. In this case fate sharing is harmful.
But is fate sharing always a bad thing ? Actually no. As always it depends.
I can hear the voice of Transport Engineers right now 🙂
When there is a connection between two routers for example, if link fails and only one side of the link goes down (This is the case when you have a transport equipment or routers connected via the Ethernet switch), for the failure detection upper layer protocol is used (BFD, Protocol hellos etc.).
But of course it is better if both sides of the link go down at the same time. This is called fate sharing as well and in this type of situation, Transport people want fate sharing. (In fact one of the capabilities of MPLS-TP is fate sharing through the inline OAM messages).
Thus we can’t say that fate sharing is always a bad thing but depends on the situation.
To keep this post as short and understandable I won’t give another example but if you would like me to provide more example let me know, share your thoughts in the comment box below.