Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

What's cf_hwassist_missedKeepAlive timeout and tolerant period?

Last Updated:

Applies to

  • NetApp AFF and FAS systems
  • Data ONTAP 8 7-Mode
  • Clustered Data ONTAP 8
  • Clustered Data ONTAP 9


cf_hwassist_missedKeepAlive incident is recorded in EMS after 60 seconds, after a hw-assist packet sent.

The hw-assist packets are sent by UDP every 180 seconds, so there is no retransmission of packets if the packets are sent and not received. If a UDP packet is dropped, blocked, wedged, redirected, etc.. and a node doesn't receive it, then the node will just wait for 180 seconds, until the next one is sent.

So if a cf_hwassist_recvKeepAlive event is showing within 120 seconds after cf_hwassist_missedKeepAlive, it can be ignored safely.

Additional Information

For the cause of cf_hwassist_missedKeepAlive, because hw-asssit configured and transmit with IP and port(default 4444) on e0M which goes through customer network environment, nearly every instance of this type of failure, is due to network dropped packets.