<?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 We are having a NTP server in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595581#M198249</link>
    <description>&lt;P&gt;We are having a NTP server but we are using the ASA box as outside of network and down the box in inside we are having other firewall. So we are able to ping the NTP from ASA&lt;/P&gt;&lt;P&gt;I just wasn't to know that is a normal behavior or there is some issue with the box.&lt;/P&gt;</description>
    <pubDate>Fri, 02 Jan 2015 11:20:59 GMT</pubDate>
    <dc:creator>Sunil Patil</dc:creator>
    <dc:date>2015-01-02T11:20:59Z</dc:date>
    <item>
      <title>Clock is not Updating After Hard reboot.</title>
      <link>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595579#M198247</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I am having 1 Cisco 5520 in our network. we don't have the NTP Server so we manually configured the Clock for the devices. We observed that when we give a soft (Command) reboot the box the time and day is updated. But we faced issue when we give a hand reboot (Power down by switch off the Power button) the date and time is not updated and go to 2003 year.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kindly suggest what issue with the ASA.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:17:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595579#M198247</guid>
      <dc:creator>Sunil Patil</dc:creator>
      <dc:date>2019-03-12T05:17:19Z</dc:date>
    </item>
    <item>
      <title>I am not authoritative on</title>
      <link>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595580#M198248</link>
      <description>&lt;P&gt;I am not authoritative on this issue. But it seems to me likely that when you issue the reload command that the ASA is doing an orderly shutdown and saving some data that allow it to recover the date and time. But when you power down the ASA that it does not have the valid and current&amp;nbsp;state of that data and so must use the default date and time. If this causes problems then perhaps you should investigate implementing NTP server access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2015 11:09:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595580#M198248</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2015-01-02T11:09:15Z</dc:date>
    </item>
    <item>
      <title>We are having a NTP server</title>
      <link>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595581#M198249</link>
      <description>&lt;P&gt;We are having a NTP server but we are using the ASA box as outside of network and down the box in inside we are having other firewall. So we are able to ping the NTP from ASA&lt;/P&gt;&lt;P&gt;I just wasn't to know that is a normal behavior or there is some issue with the box.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2015 11:20:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595581#M198249</guid>
      <dc:creator>Sunil Patil</dc:creator>
      <dc:date>2015-01-02T11:20:59Z</dc:date>
    </item>
    <item>
      <title>I would guess that this is</title>
      <link>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595582#M198250</link>
      <description>&lt;P&gt;I would guess that this is normal and not a problem with the box. And it is a good example of the benefit from running ntp with some server rather than depending on manual intervention which is needed only sometimes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2015 15:52:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595582#M198250</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2015-01-02T15:52:28Z</dc:date>
    </item>
    <item>
      <title>I am not entirely sure that</title>
      <link>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595583#M198251</link>
      <description>&lt;P&gt;I am not entirely sure that this is normal...As Richard has mentioned when you do a "soft" reboot the ASA goes through a series of shutdow procedures which may include taking a snapshot of the current time during reboot.&lt;/P&gt;&lt;P&gt;But when you change the system time on the ASA the ASA updates the system BIOS which is powered by a battery on the motherboard.&amp;nbsp; So in the case of even a "hard" reboot that time should still be stored in BIOS which is powered seperately.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Before, thinking this is normal behavior, and if this is a really important issue to resolve in the case that you can not use an NTP server, I would suggest changing the battery on the motherboard, perhaps it has gone flat.&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2015 16:56:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/clock-is-not-updating-after-hard-reboot/m-p/2595583#M198251</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2015-01-02T16:56:12Z</dc:date>
    </item>
  </channel>
</rss>

