Skip to main content
NetApp Knowledge Base

Failed to Receive Load Balancer Probe

  1. Last updated
  2. Save as PDF
Views:
1,017
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
microsoft_azure
Last Updated:

Applies to

  • Cloud Manager (CM)
  • Azure Load Balancer

Issue

  • Load balancer fails to send probe and then sends it successfully seconds later.

Thu Mar 10 20:45:27 +0000 [cluster1: nlbd: vsa.azure.nlb.probeInactive:alert]: Failed to receive Load Balancer probe (now inactive) for 1 ports (port range: 63004 to 63004), within 15 seconds.

Thu Mar 10 20:49:44 +0000 [cluster1: nlbd: vsa.azure.nlb.probeActive:notice]: Received Load Balancer probe (now active) for 1 ports (port range: 63004 to 63004).

Cause

Possibly related to a network error that causes temporary latency.

Solution

  1. Check ASUPs to see how often this error has occurred
  2. If the issue has not been seen for a number of days then this was related to a network error that caused temporary latency.

Additional Information

  • If the problem is persistent, check for changes made to the Azure Network Load Balancer Front End Rule.
  • If there were changes made, re-add Azure Network Load Balancer Front End Rule for cluster-mgmt LIF manually from Azure Portal or from Azure CLI.
  • If the problem still persist, reach out to Microsoft for assistance.
  • Cloud Manager only monitors the Azure load balancer and logs information from the load balancer, Microsoft is responsible for troubleshooting the Azure load balancer.

Internal Notes

internalNotes_text

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.