Server Management Suite

Hi All,

   We are having an odd issue with shared guids on Linux servers. Several servers appear to be sharing guids. They are named differently, are in different offices and are even different versions of OS.
 

We are running SMP 7.1 SP2

I have run the Shared Guid reports to find the details of these servers.

I have tried uninstalling the agents, deleting the servers from the console, then reinstalling, both using the agent push - in which case the server gets assigned a new guid initially, but when the agent first checks in it then assumes the guid in the same manner as before, ie each server is assigned the same guid again by the Notification server, and also by manually running the install on the Linux server.

I have tried stopping the agent, deleting the host.GUID file and restarting (having cleared the agent blacklist).

Each time the same servers get assigned the same guid as the other servers they originally matched with.

Anyone got any ideas?

Phil

Hi,

Can you check Merged Resource report to find out based on which key resource merge occurs.

Report is located under Reports->Notification Server Management->Server->Resource Reports->Merged Resources. Here you should find your linux boxes.

Post here merge  key name and its value.

Thanks,

Andrei

Hi Phil,

Can you please launch "aex-helper resource query" on these  boxes and see if name.domain values are the same ?

See KB http://www.symantec.com/business/support/index?page=content&id=HOWTO77403

As a quick workaround you can edit client.conf on affected boxes to disable name.domain key as resource keys - http://www.symantec.com/business/support/index?page=content&id=HOWTO60919

Thanks,

Andrei

Hi Andrei,

 The name.domain keys on each are showing the correct names for the servers, I followed the details in the second link, stopped the agents, deleted the host.GUID file, restarted, and looking at the log on the SMP server, again the servers are being merged.

Thanks

Phil

Hi Andrei,

  Continued looking through and thought i'd try the aex-helper agent -s MachineID ignore_resource_keys "macaddress" command

Deleting the host.GUID, deleting from the console, then restarting the agents appears to have done it, certainly for the first batch of servers.

I'll look at the others in the morning. If this solves it, I'll mark your post as the solution.

Thanks for pointing me at the article.

Phil

Hi Andrei,

Is one example

Thanks

Phil

(edited to remove actual server names)