CCIE blueprint: 3.4.a Implement and troubleshoot RIPv2
This post is part of a multipost series about RIP. Other posts in this series are:
RIP RIP configuration part 2 RIP authentication RIP summarization Miscelanious RIP commands RIPng This post will cover the configuration of RIP. Basic RIP configuration is peanuts and done in seconds. There are some additional features that can be configured, but most of the time these won’t really be necessary.
CCIE blueprint: 3.4.a Implement and troubleshoot RIPv2
This post is part of a multipost series about RIP. Other posts in this series are:
RIP RIP configuration part 1 RIP authentication RIP summarization Miscelanious RIP commands RIPng This post is a continuation of the previous post. This post will cover the following configuration items for RIP:
RIPv1 and Ripv2 interoperability Bidirectional Forwarding Detection RIPv1 and RIPv2 interoperability By default, when you enable RIP it enables version 1.
CCIE blueprint: 3.4.a Implement and troubleshoot RIPv2
RIP is the easiest routing protocol on the CCIE R&S 5.1 blueprint. It is not a very widely used protocol anymore, but it is interesting to look into.
I will create several posts about RIP in the near future. These are:
RIP configuration part 1 RIP configuration part 2 RIP authentication RIP summarization Miscelanious RIP commands RIPng This first post will cover RIP basics
Direct Server Loadbalancing is a loadbalancing mechanism in which traffic is sent via a Virtual IP (VIP) to one or more Real Servers. These servers are in the same Layer 2 domain as the loadbalancer itself and will respond directly to the client without the return traffic going through the loadbalancer on the way back. This differs from loadbalancing based on source NAT or when using the loadbalancer as gateway. The following image shows Direct Server Return (DSR) Loadbalancing.