something funny.. i mean that i don't understand..

1/ usually to make sure that a S2S circuit is up i ping the remote
tunnel address from a server -> tunnel server1 is 192.168.128.1 and
tunnel server2 is 192.168.128.2, then if from server1's console i've a
reply from 192.168.128.2, then it's ok, and NRM show an active connection

2/ for some servers (didn't identify yet a difference in the config..)
i've just discovered that i've to ping the public ip address of the
remote to have the tunnel up and marked active in NRM

it happens only for IKE to IKE servers, from IKE/SKIP to SKIP only it
works as described in 1/

3/ and at the reverse, for most of the servers the ping from the console
to the remote public never works.. for all i've a static nat of the
private address to itself in the public bind...

some advises ?? just to understand

Other question.. when there is several ping running from the console
following the point 3/, the response time is normal.. except as soon as
at least 1 (or perhaps 2) circuits not up.. in this case the running
ping have a response time doubled or triple regularly, let say each 5-6
packets... some explanations ?

And to finish i'm also interested to know what mean the following messages :

Send update cfg to 2 for type of mask = 31, typeofcfg = 8
Send update cfg to 2 for type of mask = 31, typeofcfg = 16
Send update cfg to 2 for type of mask = 31, typeofcfg = 1

Perhaps the answer to some questions about the "ping" is very obvious
but i don't see... and i like to understand !

Thanks
Robin