Quantcast
Channel: VMware Communities: Message List - Add new platform bug
Viewing all articles
Browse latest Browse all 28

Re: Add new platform bug

$
0
0

Is this still an issue?

 

On my system I find that monitoring a new resource replaces my old resource.

 

I see "fqdn changed, server set changed"

 

It's identical to "New Auto-Discovered Platforms Appearing under Existing Platforms" and "Auto discovery problem - new resource is linked to one currently inthe DB"

 

https://lists.springsource.com/archives/hq-users/2009-March/009223.html and https://lists.springsource.com/archives/hq-users/2009-January/008370.html

 

I am on a virtualized platform (linux-vservers) where the servers do not have eth0 - they have only a local loopback (127.0.0.1) address reported by ifconfig

 

EDIT: I tested to see whether changing agent.listenPort would make them distinct. It didn't. Anyhow, assigning a different port for each different server is less than ideal as I like to keep servers as identically configured as possible.

 

EDIT: http://communities.vmware.com/thread/357269 notes you can set agent.fdqn and agent.name - these properties did not show - or I couldn't see them making a difference (where should they appear in HQ Server)?

 

I am running agent 4.6.6 and server 4.6.6

 

 

Thanks,

   Martin.

 

After too much trial and error, I finally found that specifying in each agent.properties file was sufficed:

 

platform.name=shortname
platform.fqdn=shortname.domainname.com
platform.ip=199.x.x.x
agent.listenPort=214X

 

I presently have different listenPorts for each platform - I suspect that with the other platform.X setting that's no longer necessary.

 

I hope this of help to someone else!

 

M.


Viewing all articles
Browse latest Browse all 28

Latest Images

Trending Articles





Latest Images