<?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 Services Restart - VDX VCS_Logical Chassis in Data Center (VDX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118781#M1012</link>
    <description>&lt;P&gt;We completely removed the NTP and re-added it - still not correct. The primary node would not disseminate it. We manually set the Timezone on each of the nodes and that seemed to work - but it reverted (on the nodes that were not primary).&lt;/P&gt;&lt;P&gt;*But, we did not try stripping the NTP config and re-adding it with a dummy IP.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 May 2025 19:08:00 GMT</pubDate>
    <dc:creator>TL</dc:creator>
    <dc:date>2025-05-22T19:08:00Z</dc:date>
    <item>
      <title>NTP Services Restart - VDX VCS_Logical Chassis</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118755#M1010</link>
      <description>&lt;P&gt;Greetings - We have approx a half dozen groups of VDX chassis (6740F, 6740-T) configured as VCS_Logical Chassis - each with 4-6 nodes.&lt;/P&gt;&lt;P&gt;Two of the VCS are showing mismatched timestamps between the primary node of the VCS and all the other nodes in that group - the others being (4) hours ahead - as if the NTP configuration is not being distributed to all the nodes in the VCS.&lt;/P&gt;&lt;P&gt;We use the same NTP configuration across all of our VCS groups - and the others are not exhibiting the issue. We tried completely removing and re-adding the NTP config, but the condition persists.&lt;/P&gt;&lt;P&gt;*Is there any way to recycle the NTP services on a VCS - without a reboot?&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 23:01:01 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118755#M1010</guid>
      <dc:creator>TL</dc:creator>
      <dc:date>2025-05-20T23:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Services Restart - VDX VCS_Logical Chassis</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118760#M1011</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Please confirm if the timezone is set the same for all VDX as it's set per RB:&lt;/P&gt;&lt;P&gt;VDX1# sh run rb clock&lt;BR /&gt;rbridge-id 1&lt;BR /&gt;clock timezone America/Los_Angeles&lt;BR /&gt;!&lt;BR /&gt;rbridge-id 2&lt;BR /&gt;clock timezone America/Los_Angeles&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;There are no user level commands to restart the NTP service. You can try removing the NTP server configuration, then setting it to a dummy IP (ex. 192.168.0.1) which will update the config. Then, remove it again and re-enter the correct NTP server configuration. After, the principal RB will then push a time sync to the rest of the VCS.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2025 17:17:47 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118760#M1011</guid>
      <dc:creator>Truyen_Phan</dc:creator>
      <dc:date>2025-05-21T17:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Services Restart - VDX VCS_Logical Chassis</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118781#M1012</link>
      <description>&lt;P&gt;We completely removed the NTP and re-added it - still not correct. The primary node would not disseminate it. We manually set the Timezone on each of the nodes and that seemed to work - but it reverted (on the nodes that were not primary).&lt;/P&gt;&lt;P&gt;*But, we did not try stripping the NTP config and re-adding it with a dummy IP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 19:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/ntp-services-restart-vdx-vcs-logical-chassis/m-p/118781#M1012</guid>
      <dc:creator>TL</dc:creator>
      <dc:date>2025-05-22T19:08:00Z</dc:date>
    </item>
  </channel>
</rss>

