Virtual Router Redundancy Protocol (VRRP) and Hot Standby Router Protocol (HSRP)

Von: Thomas Trenz | Datum: 12. Dezember 2013 | Kommentar: 0 | Kategorie: Virtualization

FailoverCluster VRRP and HSRP router and switch redundencyRedundancy is a key concept for protecting critical environments against single points of failures. Server cluster assure the availability of critical applications on the corporate network.

However, redundancy doesn’t help if every component of a critical system is designed in a redundant manner. For network infrastructure devices such as switches and routers, there are protocols that create a cluster of redundant switches and routers. The protocols work in a similar manner: Several switches or routers get connected as a virtual switch or router. The virtual switch or router has its own IP and mac address. The algorithms determine the master router or switch of the cluster. The master router or switch handles the traffic and forwards network packets to their destination. In case of a failure, the cluster can select one of its backup switches or routers to be the new master. Usually, this is done within a few seconds and network interruption is minimal.

Examples for this kind of protocols are VRRP (Virtual Router Redundancy Protocol) or HSRP (host standby router protocol from Cisco).

Our latest JDisc Discovery build identifies VRRP and HSRP clusters. It finds out

  • what clusters are available on the network
  • which cluster services are available on a switch /router (there might be more than one)
  • which routers/switches participate in what cluster

Whenever JDisc detects a VRRP or HSRP cluster, it creates a cluster component within its database. Once it finds the members for the cluster (by scanning the participating switches), it assigns them to the cluster. The cluster gets named by the VRRP cluster id and the cluster’s primary IP address. In the following example, we detected two VRRP clusters. Both clusters have two switches that belong to the cluster.

All Clusters the list of all clusters

A double-click on the cluster brings you to the list of cluster members for the selected cluster. In this case, we have two Arista switches participating in the cluster:

DevicesOfCluster VRRP Cluster Devices

Once you open the device details, you can see the VRRP interfaces with their primary and secondary VRRP addresses within the interfaces tab.

Device Details for test-sw1.test.com Device Details VRRP Cluster Interfaces.

Finally, the cluster services section within the software tab displays the list of available cluster services on that cluster member.

Device Details for test-sw1.test.com (2) cluster services for the switch cluster.

At this point, I would also say thanks to the customer who helped us with his expertise to implement this pretty nice feature. Although, I am not allowed to disclose the customer name, I would really like to say again “Thank you Mr. E.” 🙂

Über den Autor

Thomas Trenz

Thomas Trenz ist Gründer und Geschäftsführer der JDisc GmbH und begeistert sich seit mehr als zwei Jahrzehnten für die Netzwerkinventarisierung. Nach vielen Jahren in der Entwicklung von Enterprise-Discovery-Lösungen gründete er 2009 JDisc mit einer klaren Vision: eine Discovery-Plattform zu entwickeln, die außergewöhnliche technische Tiefe mit einer intuitiven Bedienung, hoher Zuverlässigkeit und erstklassigem Kundensupport verbindet.

Heute verantwortet Thomas die strategische Ausrichtung und Produktentwicklung von JDisc Discovery und unterstützt Unternehmen weltweit dabei, vollständige Transparenz über ihre IT-Infrastrukturen zu gewinnen. Seine Fachgebiete umfassen die Netzwerkinventarisierung, IT Asset Management, CMDB, Cybersicherheit, Virtualisierung, Cloud-Technologien sowie das Lizenzmanagement für Unternehmenssoftware.

Im JDisc-Blog teilt Thomas praxisnahe Einblicke, technische Hintergrundartikel und bewährte Vorgehensweisen, die auf realen Herausforderungen aus Kundenprojekten basieren – stets mit dem Ziel, Enterprise-IT transparenter, sicherer und einfacher zu verwalten.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert