<?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 snmp sysUpTime in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-sysuptime/m-p/46653#M11839</link>
    <description>So ,snmp counter is overflowed after ~ 497 days. How to deal with this ?&lt;BR /&gt;
&lt;BR /&gt;
snmpwalk -v 2c -c XXXXXX sw2.g50.kv 1.3.6.1.2.1.1.3&lt;BR /&gt;
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (56035204) 6 days, 11:39:12.04&lt;BR /&gt;
&lt;BR /&gt;
sw2.g50.kv.7 # show version | i ImageImage   : ExtremeXOS version 15.3.1.4 v1531b4-patch1-31 by release-manager&lt;BR /&gt;
sw2.g50.kv.8 # show switch  | i UpTime&lt;BR /&gt;
System UpTime:    503 days 14 hours 8 minutes 47 seconds &lt;BR /&gt;</description>
    <pubDate>Thu, 06 Aug 2015 18:41:00 GMT</pubDate>
    <dc:creator>AlexanderT</dc:creator>
    <dc:date>2015-08-06T18:41:00Z</dc:date>
    <item>
      <title>snmp sysUpTime</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-sysuptime/m-p/46653#M11839</link>
      <description>So ,snmp counter is overflowed after ~ 497 days. How to deal with this ?&lt;BR /&gt;
&lt;BR /&gt;
snmpwalk -v 2c -c XXXXXX sw2.g50.kv 1.3.6.1.2.1.1.3&lt;BR /&gt;
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (56035204) 6 days, 11:39:12.04&lt;BR /&gt;
&lt;BR /&gt;
sw2.g50.kv.7 # show version | i ImageImage   : ExtremeXOS version 15.3.1.4 v1531b4-patch1-31 by release-manager&lt;BR /&gt;
sw2.g50.kv.8 # show switch  | i UpTime&lt;BR /&gt;
System UpTime:    503 days 14 hours 8 minutes 47 seconds &lt;BR /&gt;</description>
      <pubDate>Thu, 06 Aug 2015 18:41:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-sysuptime/m-p/46653#M11839</guid>
      <dc:creator>AlexanderT</dc:creator>
      <dc:date>2015-08-06T18:41:00Z</dc:date>
    </item>
    <item>
      <title>RE: snmp sysUpTime</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-sysuptime/m-p/46654#M11840</link>
      <description>Pavel, as per the MIB definition, the sysUpTime object is a 32-bit  number. The elapsed time is represented as number of  TimeTicks i.e. 1/100the of a second. So, it will  wraparound after 497 days.    &lt;BR /&gt;
&lt;BR /&gt;
Given 2^32-1 = 42949672 (seconds), divide by 86,400 (seconds in a day) = 497 days&lt;BR /&gt;
&lt;BR /&gt;
There appears to be no workaround to this and it is designed per RFC1213.&lt;BR /&gt;
&lt;BR /&gt;
You   might be able to poll snmpEngineTime (1.3.6.1.6.3.10.2.1.3) for the   uptime of the SNMP  process, however this may not be as accurate.   However a 'show switch' output will always work. &lt;BR /&gt;</description>
      <pubDate>Thu, 06 Aug 2015 23:27:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-sysuptime/m-p/46654#M11840</guid>
      <dc:creator>Ty_Izzet</dc:creator>
      <dc:date>2015-08-06T23:27:00Z</dc:date>
    </item>
  </channel>
</rss>

