Gateway Load Balancing Protocol

Abstract: Gateway load balancing and failover methods, apparatus and systems use more than one gateway device in a gateway device group for communications directed outside of a LAN. In the load balancing arrangement, hosts that send ARP messages to a shared virtual IP address receive replies from one of the gateway devices in the gateway device group, directing the host to address outgoing communications to a virtual MAC address assigned to one of the gateway devices. Hosts are assigned virtual MAC addresses for the gateway devices according to a prescribed algorithm or methodology. In the event that one member of the gateway device group fails, the outgoing communications that would have been handled by the failed gateway device are re-assigned to another member of the gateway device group. A master gateway device controls address assignment and failover features. In the event that the master fails, additional steps are taken to appoint or elect a new master and ensure continuity in the load balancing function.

Abstract: Wireless Mesh Networks (WMNs) provide a cost-effective way of deploying a network and providing broadband Internet access. In WMNs a subset of nodes called gateways provide connectivity to the wired infrastructure (typically the Internet). Because traffic volume of WMNs is expected to be high, and due to limited wireless link capacity, gateways are likely to become a potential bottleneck. In this paper, we propose a distributed load-balancing protocol where gateways coordinate to reroute flows from congested gateways to under-utilized gateways. Unlike other approaches, our scheme takes into account the effects of interference. This makes it suitable for implementation in practical scenarios, achieving good results, and improving on shortest path routing. Also, it is load-sensitive and can improve network utilization in both balanced and skewed topologies. Simulation results prove the effectiveness of our approach, which outperforms all schemes tested. We have observed throughput gains of up to 80% over the shortest path algorithm.

Abstract: Realtime (streaming) data communication has become a major requirement for companies and government institutions. Communication that occurs is not only limited to one particular local area but covers other areas so as to form a broad network (WAN). In building network infrastructure, one of the most important things is how networks can deal with failure (failure) on a computer network consists of failure of devices (devices) that affect Quality of Services (QoS). In every internet network design process, a redundant line is always added to complete the main line. So that if the main line is disrupted, data traffic can be transferred to the backup path, this process is called network redundancy. So that if one gateway dies, another gateway will immediately replace the dead gateway. There are two protocols included in the FHRP, namely Hot Standby Routing Protocol (HSRP), and Gateway Load Balancing Protocol (GLBP), these two protocols that can overcome this problem. So from that this study will discuss which protocol between the two protocols has the best performance in overcoming the problem. Methods of data collection with literature studies and literature studies, simulations carried out with 8 stages (problem formulation, conceptual models, input & output data, modeling, simulation, verification & validation, experimentation, and output analysis). The results of this study provide the best QoS value for the delay value is the HSRP ROUTER protocol, and for the value of packet loss is HSRP, and for throughput value is HSRP and the routing protocol that is appropriate for the network for video streaming services is HSRP

Abstract: First Hop Redundancy Protocols are an important part of high availability network design. The common ones are hot standby redundancy protocol, gateway load balancing protocol, and virtual router redundancy protocol. This paper compares the performance of the three protocols by measuring the time the network of an industrial enterprise takes to recover from a fault. A simple network topology is presented using GNS3 network emulator. After the tests are concluded, suggestions are given to improve the performance of these protocols.