Virtual Router Redundancy Protocol

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

The Virtual Router Redundancy Protocol (VRRP) is a computer networking protocol that provides for automatic assignment of available Internet Protocol (IP) routers to participating hosts. This increases the availability and reliability of routing paths via automatic default gateway selections on an IP subnetwork.

The protocol achieves this by creation of virtual routers, which are an abstract representation of multiple routers, i.e. Primary/Active and Secondary/Standby routers, acting as a group. The virtual router is assigned to act as a default gateway of participating hosts, instead of a physical router. If the physical router that is routing packets on behalf of the virtual router fails, another physical router is selected to automatically replace it. The physical router that is forwarding packets at any given time is called the Primary/Active router.

VRRP provides information on the state of a router, not the routes processed and exchanged by that router. Each VRRP instance is limited, in scope, to a single subnet. It does not advertise IP routes beyond that subnet or affect the routing table in any way. VRRP can be used in Ethernet, MPLS and Token Ring networks with Internet Protocol Version 4 (IPv4), as well as IPv6.

The protocol is described in Internet Engineering Task Force (IETF) publication RFC 5798, which is an open standard, but Cisco claims that a similar protocol with essentially the same facility is patented and licensed;[1] however, in 2001, in reply to a direct request, Robert Barr of Cisco replied that they will not assert any patent claims unless someone tried to assert a claim against Cisco.[2] IBM also claims covering patents and their statement is readable on the IETF webpage.[3][clarification needed]

Implementation[edit]

A virtual router must use 00-00-5E-00-01-XX as its Media Access Control (MAC) address. The last byte of the address (XX) is the Virtual Router IDentifier (VRID), which is different for each virtual router in the network. This address is used by only one physical router at a time, and it will reply with this MAC address when an ARP request is sent for the virtual router's IP address.

Physical routers within the virtual router must communicate within themselves using packets with multicast IP address 224.0.0.18 and IP protocol number 112.[4]

Routers have a priority of between 1 and 254 and the router with the highest priority will become the Primary/Active. The default priority is 100; for MAC address owner the priority is always 255.

Elections of Primary/Active routers[edit]

A failure to receive a multicast packet from the Primary/Active router for a period longer than three times the advertisement timer causes the Secondary/Standby routers to assume that the Primary/Active router is dead. The virtual router then transitions into an unsteady state and an election process is initiated to select the next Primary/Active router from the Secondary/Standby routers. This is fulfilled through the use of multicast packets.

Secondary/Standby router(s) are only supposed to send multicast packets during an election process. One exception to this rule is when a physical router is configured with a higher priority than the current Primary/Active, which means that on connection to the network it will preempt the Primary/Active status. This allows a system administrator to force a physical router to the Primary/Active state immediately after booting, for example when that particular router is more powerful than others within the virtual router. The Secondary/Standby router with the highest priority becomes the Primary/Active router by raising its priority above that of the current Primary/Active. It will then take responsibility for routing packets sent to the virtual gateway's MAC address. In cases where Secondary/Standby routers all have the same priority, the Secondary/Standby router with the highest IP address becomes the Primary/Active router.

All physical routers acting as a virtual router must be in the same local area network (LAN) segment. Communication within the virtual router takes place periodically. This period can be adjusted by changing advertisement interval timers. The shorter the advertisement interval, the shorter the black hole period, though at the expense of more traffic in the network. Security is achieved by responding only to first hop packets, though other mechanisms are provided to reinforce this, particularly against local attacks. Election process is made orderly through the use of skew time, derived from a router's priority and used to reduce the chance of the thundering herd problem occurring during election. The skew time is given by the formula (256 − Priority)/256 (expressed in milliseconds).

Secondary/Standby router utilization can be improved by load sharing.[5]

History[edit]

VRRP is based on Cisco's proprietary Hot Standby Router Protocol (HSRP) concepts. The protocols, while similar in concept, are not compatible.

Derivatives[edit]

Mellanox offers MAGP, a proprietary protocol based on VRRP that allows active-active operation.[6]

Foundry Networks developed VRRP-E(Extended), a proprietary version of VRRP that avoids a few limitation of RFC 3768[7][1]

See also[edit]

References[edit]

  1. ^ IETF source[dead link]
  2. ^ Alexandre Cassen (2001-11-30). "[VRRP & OpenSource] Cisco answer". LVS mailing list. Retrieved 2013-11-28. Robert Barr, from CISCO Systems: Cisco will not assert any patent claims against anyone for an implementation of IETF standard for VRRP unless a patent claim is asserted against Cisco, in which event Cisco reserves the right to assert patent claims defensively.
  3. ^ Chuck Adams, IBM (2003-04-15). "IBM Patent Disclosure and Licensing Statement Regarding IETF RFC 2338". IETF. Retrieved 2013-11-28.
  4. ^ Nadas, Stephen (March 2010). "Protocol". VRRPv3 for IPv4 and IPv6. sec. 5.1.1.4. doi:10.17487/RFC5798. RFC 5798.
  5. ^ Nadas, Stephen (March 2010). "Sample Configuration 2". VRRPv3 for IPv4 and IPv6. sec. 4.2. doi:10.17487/RFC5798. RFC 5798.
  6. ^ "HowTo Configure MAGP on Mellanox Switches". Retrieved 2010-01-21.
  7. ^ "VRRP-Ev2 overview". docs.ruckuswireless.com. Retrieved 2021-06-07.

External links[edit]