Skip to main content
NetApp Knowledge Base

SVM Client Connectivity Issues After Node Reboot Due to Multiple Default Routes

  1. Last updated
  2. Save as PDF
Views:
28
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • NetApp ONTAP 9.16.1P10 
  • AFF-C250 and similar FAS/AFF platforms
  • SVM (Storage Virtual Machine) routing configuration

Issue

  • After node panics and subsequent reboots, some SVMs (e.g., SVM1) picked up an incorrect default route, resulting in client connectivity outages.
  • The issue was observed when multiple default routes with equal weighting were configured for the SVM. Log output examples:
SVM1 0.0.0.0/0 192.168.16.254 20
SVM1 0.0.0.0/0 192.168.19.254 20
  • After these events, clients experienced outages until the incorrect default route was removed.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.