<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NTP on switch not talking to server in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26794#M1311</link>
    <description>Advice from a TSE:&lt;BR /&gt;Please use source-interface under NTP to use the correct VE in the Vlan for NTP. I assume it should be the VE in Vlan 100. &lt;BR /&gt;&lt;BR /&gt;
Debug:Oct&amp;nbsp; 8 13:04:56 NTP: ntp_peer_unfit: unreachable - peer 192.168.123.253 isnot reachable [peer-&amp;gt;reach 0]</description>
    <pubDate>Thu, 11 Oct 2018 18:32:16 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2018-10-11T18:32:16Z</dc:date>
    <item>
      <title>NTP on switch not talking to server</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26791#M1308</link>
      <description>Good morning,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I'm having problems getting NTP to work on our ICX 7150/7650 switches.&amp;nbsp; Based on the documentation, the configuration should work, but it does not appear to even be sending any packets to the NTP server.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The NTP server is in the specified VLAN, the switch has an IP address on that VLAN also.&amp;nbsp; It can ping the NTP server IP, so I know that the two can communicate.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The NTP service is running, other devices (Cisco switches, printers, ...) can connect to it just fine.&amp;nbsp; But from running tcpdump on the server, I see no packets from the Ruckus switches.&amp;nbsp; Enabling debugging and enabling the NTP client on the switch generates several errors, but not entirely sure how to identify the root problem from those or how to correct it.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Does anyone have any thoughts?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;configuration (I have tried with and without adding 'version 3' as the server software - openntpd - documentation says it is NTPv3, although it quite happily is responding to v4 requests from the Cisco switches):&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;PRE alt="" name="" rel="" target="" title="" type="" value=""&gt;ntp&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;server 192.168.123.253&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;access-control vlan 1000&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;/PRE&gt;debug logs:&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;PRE alt="" name="" rel="" target="" title="" type="" value=""&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_print_cloud_info ntp_cu_msg_callback 2&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: UDP ports are opened&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_clock_filter: Adding offset 0, delay 0, disp 16 to filter[0] for peer 192.168.123.253&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_clock_filter: No acceptable samples available&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_peer_unfit: bad sync/stratum - peer 192.168.123.253 is not in sync [peer leap = 3, stratum = 16]&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_peer_unfit: dist exceeded - root dist 15.937 of peer 192.168.123.253 has exceeded max dist 1.50096000&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_peer_unfit: unreachable - peer 192.168.123.253 is not reachable [peer-&amp;gt;reach 0]&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56&amp;nbsp; &amp;nbsp;NTP PEER 192.168.123.253 UNFIT 1600&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: ntp_clock_select: number of final survivors 0 and leap vote 0&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: No routing entry found for peer 192.168.123.253. Not sending the NTP packet&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Debug: Oct&amp;nbsp; 8 13:04:56 NTP: poll_update: for peer 192.168.123.253 hpoll 7 burst 0 retry 2 throttle 0 next poll 64&lt;/PRE&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Tue, 09 Oct 2018 08:37:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26791#M1308</guid>
      <dc:creator>steve_kersley</dc:creator>
      <dc:date>2018-10-09T08:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: NTP on switch not talking to server</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26792#M1309</link>
      <description>And nothing could be blocking UDP:123 ports?</description>
      <pubDate>Wed, 10 Oct 2018 23:01:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26792#M1309</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-10T23:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: NTP on switch not talking to server</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26793#M1310</link>
      <description>No.&amp;nbsp; Nothing on the server (and the packets would be received on the interface even if being blocked locally).&amp;nbsp; Server and switches are both on the management VLAN so no routers/firewalls between them.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If you look in the debug logs it actually says 'not sending packet' - although it says 'no routing entry found'.&amp;nbsp; I'm assuming it's not talking routing in the traditional sense as it doesn't need a routing entry to reach that network and can ping it.</description>
      <pubDate>Thu, 11 Oct 2018 10:20:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26793#M1310</guid>
      <dc:creator>steve_kersley</dc:creator>
      <dc:date>2018-10-11T10:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: NTP on switch not talking to server</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26794#M1311</link>
      <description>Advice from a TSE:&lt;BR /&gt;Please use source-interface under NTP to use the correct VE in the Vlan for NTP. I assume it should be the VE in Vlan 100. &lt;BR /&gt;&lt;BR /&gt;
Debug:Oct&amp;nbsp; 8 13:04:56 NTP: ntp_peer_unfit: unreachable - peer 192.168.123.253 isnot reachable [peer-&amp;gt;reach 0]</description>
      <pubDate>Thu, 11 Oct 2018 18:32:16 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/NTP-on-switch-not-talking-to-server/m-p/26794#M1311</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-11T18:32:16Z</dc:date>
    </item>
  </channel>
</rss>

