How to deal with shutting down Quagga with VRR

  • 1
  • Problem
  • Updated 8 months ago
I'm doing some updates on our switches. We have a leaf spine architecture with VRR running on the leafs. I've noticed that if/when Quagga gets shutdown we start getting massive packet loss as the leaf switches are still accepting traffic to their VRR address, but have no routes to pass the traffic on.

How should one handle this situation. It seems to me that VRR should track route availability and remove its virtual IP if needed.
Photo of Nick Fisk

Nick Fisk

  • 360 Points 250 badge 2x thumb

Posted 9 months ago

  • 1
Photo of Eric Pulvino

Eric Pulvino, Official Rep

  • 4,082 Points 4k badge 2x thumb
That is not a default feature but it is a logical ask. I filed this feature request internally as FR-721.
Photo of Nick Fisk

Nick Fisk

  • 360 Points 250 badge 2x thumb
Thanks Eric. Is there anything I can do in the mean time? I want to apply updates to our leaf switches, but Quagga gets shutdown halfway through the update process. Is stopping switchd before the updates a potential solution?
Photo of Eric Pulvino

Eric Pulvino, Official Rep

  • 4,082 Points 4k badge 2x thumb
I would start with using the MLAG upgrade procedure documented here --> https://docs.cumulusnetworks.com/display/DOCS/Upgrading+Cumulus+Linux#UpgradingCumulusLinux-Upgradin... 

Personally once I've put a switch into the secondary role I will generally take the host-facing links down, followed by the uplinks and lastly the peerlink. At this point I'll perform the upgrade then reverse the procedure to bring things back up.