Skip to main content
NetApp Knowledge Base

SP HW Assist - Fail to bind UDP Socket in ONTAP 9

Views:
1,295
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • SP
  • BMC
  • AFF systems
  • FAS systems

Issue

After performing an SP update including updating the Internal switch hwassist fails to connect to its partner

  • EMS

Cluster-1b ERROR cf.hwassist.missedKeepAlive: HW-assisted takeover missing keep-alive messages from HA partner (Cluster-1a).

  • Command Line
Cluster::> storage failover hwassist show
Node
-----------------
Cluster-1a
Partner: Cluster-1b
Hwassist Enabled: true
Hwassist IP: 10.4.17.224
Hwassist Port: 4444
Monitor Status: inactive
Inactive Reason: Fail to bind UDP socket.
Corrective Action: Run 'storage failover modify -hwassist-partner-ip <Cluster-1a's node management IP> -node Cluster-1b' 
and/or run 'storage failover modify -hwassist-partner-port <Cluster-1a's UDP port> -node Cluster-1b'
Keep-Alive Status: -
Cluster-1b

Partner: Cluster-1a
Hwassist Enabled: true
Hwassist IP: 10.4.17.225
Hwassist Port: 4444
Monitor Status: inactive
Inactive Reason: Fail to bind UDP socket.
Corrective Action: Run 'storage failover modify -hwassist-partner-ip <Cluster-1b's node management IP> -node Cluster-1a' 
and/or run 'storage failover modify -hwassist-partner-port <Cluster-1b's UDP port> -node Cluster-1a'
Keep-Alive Status: -
2 entries were displayed.

 

 

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.