2012-04-24 05:52 AM
After installing WFA on the system (win2008R2V M) I am able to connect to the netapp controllers (3 * 8x-7m simulators-vm's), to the LDAP server (win2008 DC-vm) but not to the DFM server (win2008-vm).
Diagnosed this in Execution -> Credentials -> New -type: DFM
DFM/OnCommand 5 itself is functioning okay by the way (ie. prov./prot mgr and PA are working okay).
After installing wfa_oc5setup.exe I still have connection failure from WFA server to DFM server presented as follows:
failed to connect to DFM: dfm.vmdomain.local. Message: No connection could be made because the target machine actively refused it ip-address:22.
Disabled firewall for diagnostic purposes, but also to no solution unfortunately.
Only thing I had running was putty (SSH) on DFM server, but even after stopping all putty sessions, no WFA to DFM connection possible.
Solved! SEE THE SOLUTION
2012-04-24 06:05 AM
I did not understand your question to the full extent.
Is the problem with testing the credentials to the DFM or with acquiring information from it?
If it is the former - Use your own user/password to the DFM and SSH needs to be enabled and available on the DFM.
Does your DFM has SSH on it?
If it is the latter - No credentials (And no SSH) are needed.
After you run OC5Setup (Did it finish successfully?) you can set a data source in the "Datasources" screen.
Just make sure you replace the default user/pass in that screen with "wfa" and "Wfa123" respectively.
Then - try "Acquire Now" and see if it works. Don't change the port there - The acquisition works through 2638.
BTW - This process is fully documented in the WFA installation and Setup guide with additional commentary in the
tips and troubleshooting guide. Have you gone through these two documents?
2012-04-24 07:07 AM
The problem seemed to be on both parts, testing the credentials to DFM and acquiring info.
but, the acquiring info problem is solved..... problem seemed to be related to installing the oc5setup.exe on 64bit platforms (installation was defaulting to \Program Files (x86)\Netapp\DataFabric Manager\DFM which seems to be empty instead of installing to C:\Program Files\NetApp\DataFabric Manager\DFM ). So after setting up Data Sources, I am able to Acquire NOW.
I indeed installed conform WFA installation and Setup guide v1.1 (feb.28, 2012 rev.1.6) - but cannot find the tips and troubleshooting guide you mentioned.
As for the credentials part.... still no luck - Changed the security option on the DFM server from RSH to SSH, but still same problem as mentioned " failed to connect to DFM: dfm.vmdomain.local. Message: No connection could be made because the target machine actively refused it ip-address:22. ".
Tried credentials with Domain as well as local administrator accounts and offcourse with the wfa account from the WFA server to the DFM server; none of them succesfully unfortunately.
2012-04-24 08:01 AM
First, let's set the records straight about OC5Setup - It is not installing anything. It needs to be on the OC5 and when executed you should select the DFM folder (Based on where it was installed,
so obviously the default path is only a suggestion - Some install it at a different drive). When it finds it creates the internal user in the OC5 DB that allows WFA to acquire.
Regarding the credentials for the DFM - DFM credentials are needed only for running commands which via SSH on the DFM. There's a good chance that you won't need it for starting with WFA.
It has no impact on acquisition.
Obviously we would like to take a closer look at your issue.
Here's a link to the troubleshooting guide:
2012-05-18 03:30 PM
Is there a clarification on this? The install document has a comment that indicates if you want to use Protection Manager, Provisioning Manager or Service Catalog, you need to configure the DFM credentials. Yet we get this same error when we attempt to do so. Not sure why port 22 is being used for this. Is this comment in the install document wrong?
2012-05-23 07:23 AM
Well, connectivity testing to the DFM (To verify credentials) is currently done via SSH (Hence port 22).
We have a future task to work it out through ZAPI.
2012-06-12 06:19 AM
FYI, I ran into this same issue: Message: No connection could be made because the target machine actively refused it ip-address:22.
Windows host, 64-bit VM, Server 2008. Installation of FreeSSHd and creation of a separate SSH user was MANDATORY. If the user was not created I would receive "Auth null" error when trying to test connectivity through credentials.
2012-12-30 07:32 PM
I'm getting the same error:
It is obviously using port 22. My DFM server is a Windows 2008 R2 VM and the firewall is temporarily disabled. Port 22 is normally SSH. Does that mean I have to add an SSH service to my DFM server? Was it switched to ZAPI as the previous poster mentioned and the "ports required" section below suggests? What is ZAPI and do I need to add this to my DFM server (Windows)?
The section about Credentials in the same guide says nothing about adding entries for either DFM or vCenter, just storage systems. The only reason I started looking into this is because adding DFM to Credentials is briefly mentioned in the NetApp University video on installation. It still isn't clear to me what functions this would enable.