DPA6.1.0 issues adding NW Servers running Solaris OS
All,
I am trying to add a NW server running Solaris 10 to our DPA 6.1.0 server. The issues is after getting dpaagent installed locally on the NW server when I run the discovery wizard the DPA GUI doesn't discover the server at all. If I select "new host" in the GUI and proceed with the wizard the test fail with an error message " Test Failed! No agent installed on the target host xyz (agent.install.error) but this time the node gets configured.
I tried proceeding with the error as I read in some article that sometimes after the node gets configured, the data collection could work but in my case it never worked.
I raised an SR with support and we upgraded the DPA server and collectors. The DPA server is already on patch 101 and we also increased the agent request timeout to 8 HRS ( 28800 )but we still don't seem to get anywhere.
I was wondering if anyone else encountered this problem and if there is a work around for the same. DPA Support is currently checking with engineering but its getting a bit frustrating as we have already done close to 4 upgrades on our DPA server in the last 4 months and things are still broke :-(
Have you done the obvious things - checked agent is running (I have found in 6.1 if you reboot backup server it does not automatically restart DPA, engineering are currently investigating this), check you can telnet to DPA application server on port 9002 and from on port 3741. Anything in logs on DPA agent? Have you verified DPA app server is specified correctly in /opt/emc/dpa/agent/etc/dpa.config?
If you've put patch 101 it may have caused some issues if you have DataDomains, you may want to verify those are still working!
Data Domains use SNMP which use different ports but you have confirmed telnet is okay to the backup server so there should be no port issues. What kind of link is there between the DPA server and the backup server? Can you for example transfer data by FTP or similar without problems? Are the servers in the same domain?
That does not necessarily follow as the DPA agent will communicate with Networker on different ports than the DPA agent itself. But if you can communicate on 3741/9002 by telnet it should be okay unless your firewall team are blocking specific protocols on those ports.
Does your dpa.config specify IP or hostname? Are you able to successfully resolve that hostname from the backup server?
Is saying a connection was established but the DPA server had a problem with it; I also believe you are having problems with all your backup servers which suggests that perhaps the problem lies on the DPA application server...
I confirmed that the right DPA application server is mentioned in "/opt/emc/dpa/agent/etc/dpa.config"'
I am also seeing some error message on the agentlogs as see below and have no idea what they mean.
INFO 27302.4 20140226:131033 clctr.mod.hostmonito - getFileSystems(): Unsupported or procfs type for filesystem 'mnttab' mounted at: '/zoneroot/ftwldscimw157/root/etc/mnttab'.. skipping.
INFO 27302.4 20140226:131033 clctr.mod.hostmonito - getFileSystems(): Unsupported or procfs type for filesystem 'objfs' mounted at: '/zoneroot/ftwldscimw157/root/system/object'.. skipping.
INFO 27302.4 20140226:131036 clctr.mod.hostmonito - getFileSystems(): Unsupported or procfs type for filesystem '/dev/odm' mounted at: '/dev/odm'.. skipping
PS: We have DD's configured on the DPA server and some of the reports seem to have come out well this morning. I will continue to monitor for issues?
David, I have verified there is no port issues. I confirmed this by telnet and also checked with our internal FW team.
Another interesting observation I made:-
I used DPA AS as a proxy collector and configured it to monitor the NW servers running Solaris and guess what the "test" succeeded and the proxy servers (DPA AS) was able to gather the data. This confirms that there is absolutely no connectivity issues. The issue is only when the dpaagent installed locally on the NW server tries to collect and send data to the DPA AS.
PS: DD monitoring using SNMP works fine without any issues.
yes, we finally got the issue resolved by upgrading and applying the DPA server with a server hot patch (I don't recall the exact patch version but DPA support can help you out with that)
What version of DPA are you on currently? We am currently on DPA v6.1.1 Patch 306. This is so far the better patch version that I have seen. Also make sure your dpaagent are on v6.1.1 as well.
Let me know if you need any additional information.
DavidHampson-rY
1 Rookie
•
294 Posts
1223
0
Posted February 26th, 2014 07:00
What version of the agent are you on?