Unsolved
This post is more than 5 years old
8 Posts
0
2301
EMC PowerPath Viewer - Unable to discover hosts
EMC PowerPath Viewer v1.0.2.00.00.b019
PowerPath Administration Console v5.2 (build 146)
Unable to discover hosts using default TCP port 9083, as recommended by PowerPath Viewer Help.
PowerPath Viewer has been installed on a VM (Microsoft® Windows Server® 2008 Standard SP2 x64)
PowerPath Administration Console has been installed on ProLiant BL680c G5 (Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition SP2)
Looks like, PowerPath Viewer (source & random TCP Port) communicates to the host (destination & TCP port 9083), but it is the host that is not able to communicate back to the viewer.
Already confirmed that the firewall is not the problem.
I'm under the impression that the viewer should be installed only on one server and it should be able to discover the hosts, hence there's no agent like application needs to be installed on every host, except the fact that the PowerPath Administration Console should be installed.
Could someone help me?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 13th, 2013 08:00
Powerpath viewer component comes pre-installed on latest version of PowerPath, it still needs to be configured on each host to point to your PowerPath viewer console.
npresourcesfr
8 Posts
0
June 14th, 2013 07:00
Thanks.
I tried to discover a couple of hosts that had 5.3 (build 311) installed and Viewer was able to discover them. Looks like its a problem with version 5.2
Can PowerPath Console be upgraded to 5.3 on top of the previous version (in my case, it is 5.3 build 146) or it should be uninstalled, the host must be restarted and install 5.3?
Fenglin1
2 Intern
2 Intern
•
2.1K Posts
0
June 18th, 2013 22:00
Have you tried to install PP Viewer on other host and scan the problematic host? just make sure it's not the problem on your current PP viewer management host.
npresourcesfr
8 Posts
0
June 19th, 2013 00:00
Yes, I have. I was under the impression that the server that had the PP viewer installed, was not able to communicate to the problematic host and that I tried installing it on another VM, but the result was same (it still couldn't discover the host).
Then I figured out that there was a problem with the PowerPath Administration Console v5.2 (build 146) installed on hosts, because I tried to discover a couple of hosts that had 5.3 (build 311) installed, they were indeed discovered.
Hence, I'm thinking that upgrading the PowerPath Administration Console v5.2 (build 146) to 5.3 (build 311) will help. I just don't know if the upgrade can be done on top of the existing version or current version should be uninstalled, host must be restarted and install the latest version.
Fenglin1
2 Intern
2 Intern
•
2.1K Posts
0
June 19th, 2013 01:00
loot at PP Viewer release notes. It appears the PP Viewer supports PowerPath 5.3 or later. In your case, the host you want to monitor by PP viewer should upgrade to PowerPath 5.3.
Yes, you're able to upgrade the version on top of the existing version. As, PP installation will upgrade the driver, reboot is required.
npresourcesfr
8 Posts
0
June 19th, 2013 01:00
Thanks for your update, Fenglin. I'll plan for upgrade and reboot.