I’m seeing some strange activity with one of my hosts and ndmp... hoping someone can shed some light.
I have a cluster I’ve added to DFM using the NMC.... when adding the hosts using the wizard, I’m prompted to enable ndmp, I select yes and enter the ndmp cred's. The problem I’m facing is that I’m only getting to the point where I’m asked to enable ndmp, no prompt to specify the cred's. Funny thing is as soon as I complete the wizard and have enabled ndmp, I see that the host status of ndmp is down and cred's are bad. I go through the wizard again (and again) and each time, it tells me ndmp is down. I have verified that ndmp is in fact enabled from the cli....
What you mentioned is what I would normally do if I add a client using the WebUi. I've attempted this but, for whatever reason, it will not allow me to specify the ndmp credentials... it doesn't even give me the option. Even if i enable ndmp at the cli, it still shows as disabled through the nmc.
It's certainly odd. I don't ever recall the host diagnostic wizard skipping the NDMP credentials page.
From the DFM CLI, you can user "dfm host set <hostname> hostNdmpLogin=plugh hostNdmpPassword=xyzzy" to set the credentials (fill in the right values, of course). From there, "dfm host diag" should show the NDMP conectivity working. This is essentially what the host diag wizard does. Once that's working, the rest of Protection Manager should start working.
When I hit ndmp problems I go through these steps.
1) On the filer, run 'options ndmpd' and make sure ndmp is enable and access is set correctly
ndmpd.access all ndmpd.authtype challenge ndmpd.connectlog.enabled off ndmpd.enable on ndmpd.ignore_ctime.enabled off ndmpd.offset_map.enable on ndmpd.password_length 16 ndmpd.preferred_interface disable ndmpd.tcpnodelay.enable off
2) On the filer, run 'ndmp status'
ndmpd ON. No ndmpd sessions active.
3) On the DFM system, use the command line like this, assuming the filer is already known to DFM
dfm host set <file_name> hostNdmpLogin=<user> hostNdmpPassword=<password>
4) Run 'dfm host diag <filer_name>' to make sure the NDMP status is good.