PCM+ Getting switches to update

[Sudain]

Only 2 IP addresses on the server: 172.x.x.x to connect to the management vlan and the primary, 129.x.x.x which serves out DHCP and an RDP client so my local PC can connect to the server.

[KSimpson · Accepted solution]

Yea, That's the issue. For some reason PCM will not work correctly on a dual-homed server. Some features works correctly but some doesn't (ex. software upgrade). I opened a ticket with HP about the issue but they never fixed the issue. We finally put PCM on it's on server with one IP. It works like it should now.

[Sudain]

Alright thank you. I'll just live without that for now I guess. Hopefully they will fix this as this seems like a very useful feature!

[KSimpson]

If you need it now, you might want to put in a ticket with them. I had this issue over a year ago. According to a HP tech, the way the dual-homed server acted is some type of side effect. lol.

[KSimpson]

Good Luck!

[Jaap Laaij]

Hi all,

Having the same problem.
A lot of switches have to be reached over the WAN. No proxy has to be used.
Was able to update PCM+ after dumping the update .zip in the autoupdate dir.

In the log file s-AutomaticUpdate_X in the /PNM/Server-dir found this entry:

2010 May 20, 10:20:50:952 ftp.hp.com
java.net.UnknownHostException: ftp.hp.com

Anyone an idea?

Thanx Jaap