Has this problem persisted for you? If so, restart the service manager
components (first making sure that any existing ones have been killed), and try
again. There is some local subnet host discovery (ala Bonjour) that could
account for the problem you're seeing. Either way, if this is a bug I'd like
to make sure it gets addressed.
Tom
On 1/10/08 5:04 PM, Ryan McVeigh wrote:
The hostnames properly resolve from the display machine in that the host
machine can find the other. But I'm not sure that the configuration is being
saved properly or that I'm loading the newly saved node config. The only step
I've attempted is changing the configuration in the AG node management by
starting from scratch and when I go to fill in the new names in the Add
Service Manager Dialog box and hit OK the name shows up as it was before within
the node management window. Is there a step I am missing?
Thanks,
Ryan McVeigh
National Center for Atmospheric Research
On Jan 10, 2008, at 3:54 PM, Thomas D. Uram wrote:
I'm sure the AG software is not meddling with the hostnames, as it does
no special caching of hostnames or anything. Two things come to mind:
- Are you sure that the node configuration is being saved properly, using
the new names? Are you sure you are loading the newly saved node configuration?
- Do the new hostnames properly resolve from the display machine?
Tom
On 1/10/08 4:42 PM, Ryan McVeigh wrote:
Hey everyone,
Our network team changed our network to DHCP over the holidays and
changed the network names of our multi-node system. Now neither pc can find
each other within the Access Grid software. If I try to create a new
configuration in AG node management it changes the name/IP to the name used
prior to the network change.
How do you rename the service managers/computers within the AG
software so that they recognize each other?
Thanks,
Ryan McVeigh
National Center for Atmospheric Research
