There can be issues when the primary interface (check /etc/hosts and see where the hostname FAS3210B is used.. the one with more than one name with both the interface and host names) then make sure that interface is up. Often we find when it is down ndmp local won't work...even though it uses the loopback adapter it needs the primary interface defined to the host online.
We could solve this issue. This is due to a bug in OnTap 8.1 and some others too, but fixes in Release 8.1.1
There are Zombie NDMP Sessions left which prevent to start new ndmp jobs. Here´s the Solution:
OEM: Data ONTAP 8.1 NDMP daemon does not allow new NDMP sessions
Protection manager jobs or NDMP backups fail for a NetApp storage controller running Data ONTAP 8.1.
The following error message is displayed:
ERROR: maximum number of NDMP processes (392) forked.
The ndmpd status command displays no ndmpd sessions.
In Data ONTAP 8.1, the ndmpd daemon follows the UNIX convention of forking a copy of itself for each NDMP session. For some reason, the daemon gest corrupt and cannot fork any copies, even though there are no copies running.
The following is a BUG in Data ONTAP 8.1:
BUG 587756 - NDMP service disruption, NDMP does not serve any client requests
In the public BUG report, the workaround says 'Restart NDMP service,' but is sparse on details. The following is the procedure to do that:
The ndmpd daemon needs to be restarted to clear it and allow it to start spawning copies again. Rebooting the storage system will accomplish this, but getting permission to reboot is difficult for many users.
Perform the following steps to stop and restart only the ndmpd daemon process:
Open the systemshell
Unlock the 'diag' userid if not done previously For more information, see article 1012484: Data ONTAP 8: How to unlock the diag user account
Find the current NDMP daemon filer% ps aux | grep ndmpd The output will look similar to the following: root 1693 0.0 0.6 20364 4328 ?? Ss Fri12PM 0:05.38 /sbin/ndmpd
Stop the current daemon: filer% sudo killall ndmpd Messages similar to the following will be displayed, indicating the daemon process has been terminated: Tue Sep 4 13:43:46 EDT [fas2220cl1-rtp:spm.ndmpd.process.exit:error]: Network Data Management Protocol server (ndmpd) with ID 1693 exited as a result of signal 15. This server will attempt to restart.
Tue Sep 4 13:43:46 EDT [fas2220cl1-rtp:spm.ndmpd.procesfas2220cl1-rtp% s.exit:error]: Network Data Management Protocol server (ndmpd) with ID 1693 exited as a result of signal 15. This server will attempt to restart.
Determine if the daemon has restarted: filer% ps aux | grep ndmpd If one /sbin/ndmpd process is displayed, the daemon has restarted normally. If multiple '/sbin/ndmpd' processes are displayed, the daemon has restarted normally and NDMP jobs have started running. The ndmpd status command run at the Data ONTAP prompt should display an NDMP session for each of the 'extra' daemon processes.
Exit the systemshell, and reset the privilege mode: filer% exit filer*> priv set admin filer>
Note: BUG 587756 is listed as fixed in Data ONTAP 8.1.1.