<?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: log skips days in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/log-skips-days/m-p/59167#M17534</link>
    <description>This is because some log messages are stored in Non-Volatile RAM, and others are stored in a memory-buffer.  If I remember correctly, only Critical, Warning, and Error level messages are stored in NVRAM.  Info and Notice messages are stored in the message-buffer, which is cleared at reboot.&lt;BR /&gt;
&lt;BR /&gt;
When the switch comes back up, you'll see new Info messages pertaining to the reboot.&lt;BR /&gt;</description>
    <pubDate>Wed, 29 Jul 2015 02:15:00 GMT</pubDate>
    <dc:creator>Drew_C</dc:creator>
    <dc:date>2015-07-29T02:15:00Z</dc:date>
    <item>
      <title>log skips days</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/log-skips-days/m-p/59166#M17533</link>
      <description>We have a x460-48p running 15.5.2.9 v1552b9-patch1-5.  The switch rebooted after a System Failure.  After it rebooted we looked at the log on the switch and it doesn't show any messages in the log for 6 days.  Here is a little cut and paste.    7/28/2015 09:48:48.96 &lt;I&gt; telnetd listening on port 23    07/28/2015 09:48:41.66 &lt;DM.NOTICE&gt; DM started  07/28/2015 09:48:41.56 &lt;NM.STRTPROC&gt; The Node Manager (NM) has started processing.  07/28/2015 09:48:40.67 &lt;EPM.START&gt; EPM Started  07/28/2015 09:48:40.66 &lt;EPM.UNEXPCTREBOOTDTECT&gt; Booting after System Failure.  07/28/2015 09:48:40.31 &lt;EPM.WD_WARM_RESET&gt; Changing to watchdog warm reset mode  07/22/2015 06:01:08.66 &lt;NETTOOLS.SNTP.SRVRNAMENOTRSLVED&gt; Host name dist-fr2.crcsd.abc is not DNS resolved yet  07/22/2015 06:01:08.66 &lt;NETTOOLS.SNTP.SRVRNAMENOTRSLVED&gt; Host name dist-fr1.crcsd.abc is not DNS resolved yet  07/22/2015 06:01:02.77 &lt;TECHSUPPORT.CNCTCLCTFAIL&gt; Failed to connect to the collector 12.38.14.200:800 with SSL disabled (VLAN Mgmt does not have an IP address.)    The switch worked fine during these days, in fact it's running as a layer 3 switch with ospf running.  Is this a known problem, has anyone else run into this problem before?    Thanks,    B&lt;/TECHSUPPORT.CNCTCLCTFAIL&gt;&lt;/NETTOOLS.SNTP.SRVRNAMENOTRSLVED&gt;&lt;/NETTOOLS.SNTP.SRVRNAMENOTRSLVED&gt;&lt;/EPM.WD_WARM_RESET&gt;&lt;/EPM.UNEXPCTREBOOTDTECT&gt;&lt;/EPM.START&gt;&lt;/NM.STRTPROC&gt;&lt;/DM.NOTICE&gt;&lt;/I&gt;</description>
      <pubDate>Tue, 28 Jul 2015 20:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/log-skips-days/m-p/59166#M17533</guid>
      <dc:creator>bw447</dc:creator>
      <dc:date>2015-07-28T20:05:00Z</dc:date>
    </item>
    <item>
      <title>RE: log skips days</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/log-skips-days/m-p/59167#M17534</link>
      <description>This is because some log messages are stored in Non-Volatile RAM, and others are stored in a memory-buffer.  If I remember correctly, only Critical, Warning, and Error level messages are stored in NVRAM.  Info and Notice messages are stored in the message-buffer, which is cleared at reboot.&lt;BR /&gt;
&lt;BR /&gt;
When the switch comes back up, you'll see new Info messages pertaining to the reboot.&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Jul 2015 02:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/log-skips-days/m-p/59167#M17534</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2015-07-29T02:15:00Z</dc:date>
    </item>
  </channel>
</rss>

