{'fraction_non_alphanumeric': 0.02127659574468085, 'fraction_numerical': 0.0, 'mean_word_length': 5.089285714285714, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Fault-Tolerant OpenFlow-Based Software Switch Architecture with LINC Switches for a Reliable Network Data Exchange

The switches are essential for forwarding the packets in a local area network. If a switch fails, then the packets are not able to reach their destination, in spite of their long journey from the source. The new trend in Software Defined Networking (SDN) has made the use of software switches such as the OpenvSwitch quite popular. These software switches are used in data centers to connect virtual machines on which application servers are deployed. Such switches have the advantages of software: ease of development and flexibility, with less optimal testing and reliability measures than hardware systems. The Software switches are required to be resilient to failure because the applications servers which are running from the VMs which are connected through them should always be connected with its clients. So fault-tolerance becomes an important aspect in the use of software switches. In this paper, we explore one mechanism for fault tolerance of LINC (Link Is Not Closed), an open source OpenFlow switch, which is written in Erlang programming language. Distributed system, concurrency, and fault-tolerance are built-in features of Erlang. We leverage these features of Erlang to realize a fault-tolerant distributed LINC switch system.