Skip to main content
NetApp Knowledge Base

What does "Nblade.CallbackTimedOut" error from SM NOTIFY mean after node upgrade/reboot ?

  1. Last updated
  2. Save as PDF
Views:
3,574
Visibility:
Public
Votes:
6
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFS V3
  • Network Lock Manager (NLM)
  • Network Status Monitor (NSM)

Answer

  • Upgrade/Reboot of a node is equivalent to a Server Crash with respect to locking in NFS V3, achieved using ancillary protocols like NLM and NSM
  • When the server is ready to serve data again after an upgrade/reboot, it needs to notify all the clients which were previously holding locks
  • Clients can then reclaim all their existing locks as the server has lost all the information about locks issued before the crash
  • This notification work is being done by Status Monitor (NSM) via SM_NOTIFY call using the callback information of clients, saved in a file
  • If the SVM cannot reach to the PORTMAP program of a client/list of clients, then below error messages will appear in EMS logs

    [?] Tue May 05 16:47:27 CEST [Cluster01-01: nblade2: Nblade.CallbackTimedOut:error]: SM NOTIFY: Vserver 11, Vif 1057: PORTMAP program (Program number:100000 Program version:2) on client 10.11.12.10 is not responding.
  • No action is required as the " Nblade.CallbackTimedOut " messages should stop approximately 24 hours after the reboot event.

    Tue May 05 20:04:12 CEST [Cluster01-01: nblade2: Nblade.CallbackTimedOut:error]: SM NOTIFY: Vserver 11, Vif 1175: PORTMAP program (Program number:100000 Program version:2) on client 10.11.12.10 is not responding.
    Tue May 05 20:14:13 CEST [Cluster01-01: nblade2: Nblade.CallbackTimedOut:error]: SM NOTIFY: Vserver 11, Vif 1175: PORTMAP program (Program number:100000 Program version:2) on client 10.11.12.10 is not responding.
    Tue May 05 20:24:14 CEST [Cluster01-01: nblade2: Nblade.CallbackTimedOut:error]: SM NOTIFY: Vserver 11, Vif 1175: PORTMAP program (Program number:100000 Program version:2) on client 10.11.12.10 is not responding.

Additional Information

  • NetApp Support Site - Bugs Online - Syslog Translator
  • The reason why SVM cannot reach to the PORTMAP program can vary and needs network connectivity troubleshooting between the SVM and the reported client
    • In some cases, the clients may have had connectivity with ONTAP removed prior to releasing 
    • If some clients are not reachable by the server repetitively, then these messages are expected to be present in EMS periodically (almost every 10 minutes)

 

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.