Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Nodes not "Globally Registered" after rename

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Nodes not "Globally Registered" after rename


Chronological Thread 
  • From: Szymon Trocha <>
  • To:
  • Cc:
  • Subject: Re: [perfsonar-user] Nodes not "Globally Registered" after rename
  • Date: Wed, 3 Aug 2016 11:04:02 +0200
  • Organization: PCSS

W dniu 02.08.2016 o 20:35, Charley Kneifel pisze:

Hello –

 

I have a test lab running 4 VMs on two distinct VMWare ESXi servers.

 

The lab environment is working well – after tuning things and using the latest vmware tools, I can reliably get 10+ Gbps between servers on the same host and 1 G between hosts on different ESXi hosts and it’s a good place to see how updates work before applying them to production.

 

Servers are all internal IP addresses and I have set the allow_internal_addresses flags in both locations.  Everything was shown as globally registered until I renamed two of the servers.

 

After renaming those two servers they no longer show up as globally registered, but all of the details of the servers and services (such as MTU) do show up when I look at graphs of the performance.

 

Is there something I need to do after renaming a server (or a configuration file I need to update)?

 

Charley

 


Hi Charley,

You usually need to give the LS some time to see and propagate the change.

You may try restarting the ls registration daemon with:

service perfsonar-lsregistrationdaemon restart

and see the log if there is any suspicious message

regards,

-- 
Szymon Trocha

Poznań Supercomputing & Networking Center
Tel. +48 618582022 ::: http://noc.pcss.pl



Archive powered by MHonArc 2.6.19.

Top of Page