https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-391 Instrument control development <p>mcs(133.40.164.208) vm guest is trying to communicate with outside NTP server.</p> <p><span class="error">&#91;Ref&#93;</span></p> <p>ccs# show logging ip access-list cache </p> <p>Src IP        Dst IP     S-Port    D-Port    Src Intf         Protocol     Hits    </p> <p>------------------------------------------------------------------------------------------------</p> <p>91.189.94.4      133.40.164.208     123     46789     Ethernet7/48 (17)UDP                1 </p> <p>91.189.89.199    133.40.164.208     123     52822     Ethernet7/48 (17)UDP                1 </p> <p> </p> <p>Please check ntp setting to see if it is using ntp-ics(133.40.164.50). Otherwise it may not have or end up not having correct time...</p> <p>Not sure who manages it and no pfs user login on mcs vm as of now. </p> <p> </p> <p>Regards,</p> <p>Eiji</p> INSTRM-391

NTP setting on MCS VM(133.40.164.208)

Task Normal Won't Fix Won't Fix Unassigned kyono Fri, 22 Jun 2018 20:23:35 +0000 Fri, 31 Mar 2023 08:45:26 +0000 Fri, 31 Mar 2023 08:45:26 +0000 0 3 <p>I'll quietly and gently point out that if the mcs host was using a DHCP server it could get the NTP server address dynamically. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a></p> <p>following listings in SSN-00028 as recommended configuration, <br/> &gt; <a href="https://github.com/Subaru-PFS/ics_doc/blob/master/SSN-00028/index.rst#site-specific-dnsmasq-configurations" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/ics_doc/blob/master/SSN-00028/index.rst#site-specific-dnsmasq-configurations</a><br/> &gt; Some of this section is RECOMMENDED for instrument development sites (or branch in git repository) but is NOT REQUIRED.<br/> &gt; dhcp-authoritative: In the PFS network, the dnsmasq service is the only one DHCP server on a network, and this should be set (but could work without this configuration).</p> <p>we have a line of ntp-server configuration in our dnsmasq<br/> &gt; dnsmasq-site.subaru:dhcp-option=option:ntp-server,133.40.164.50</p> <p>is this what <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> wants?</p> <p>so, seems host side is not on/using dhcp.</p> <p>I have changed the setting of NTP server on MCS.  Now it is pointed to 133.40.164.50.   <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kyono" class="user-hover" rel="kyono">kyono</a> Please let me know if it is still trying to connect to outside world.  Thanks</p> <p>No logs for mcs communicating with outside NTP service now, but it can be because of polling time. </p> <p>Can you do "ntpstat" on mcs vm?</p> <p>Although i am not sure change you made, based on Craig and Shimono-san's comments, is how PFS ICS should be, you can check ntp status like below. <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a></p> <p><span class="error">&#91;command&#93;</span></p> <p>pfs@gw-ics:~$ ntpstat </p> <p>synchronised to NTP server (133.40.164.50) at stratum 4 </p> <p>   time correct to within 76 ms</p> <p>   polling server every 1024 s</p> <p> </p> <p>we have 'ntp-ics' service name registered in dnsmasq, and I suppose we may be better to use canonical name rather than having ip address directly.</p> <p>I would prefer all hosts to use DHCP, and thus allow both consistent and simple (re-)configuration of NTP/DNS servers. And slightly better tracking of booting/liveness, etc. </p> <p>If a host is configured manually it should use hostnames, except for DNS servers which must obviously be by IP. </p> <p>One advantage of using DHCP would show up if we wanted to switch from a single server NTP config to a multiple server config. Since we are not using a dedicated clock we might want to at some point. Seeing that "stratum 4" above is not very comforting.</p> <p>[ I think this particular ticket can be closed. It has been fixed. ]</p> <p>This is just comment, but I now see that mcs machine is not vm running on ICS.</p> <p>Sorry for confusion...</p> <ul> <li>if this host is configured by dhcp for address-ish things, i agree that we shall follow dhcp-way.</li> <li>i agree we shall have another ticket for further server side configuration.</li> <li>i don't think we can prepare four ntp servers within PFS-LAN, so i assume we will not go to multiple ntp server configuration using physical hosts.</li> <li>both dns and dhcp configuration should work for multiple server configuration (e.g. using chrony for client). in any case we need both, for boxes (non-pc) need to be configured statically.</li> </ul> <p>This was for the old mcs PC.</p> Development Rank 0|ii059j: