<?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 DFE's SNMP MIB Walk Runs Slow when encountering TimeFiltered OIDs in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/dfe-s-snmp-mib-walk-runs-slow-when-encountering-timefiltered/m-p/43941#M223</link>
    <description>Article ID: 10162 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
Matrix N-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Performing an SNMP MIB walk. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
High CPU utilization. &lt;BR /&gt;
&lt;BR /&gt;
Some OIDs such as...                lldpRemEntry=1.0.8802.1.1.2.1.4.1.1            (ieee/lldp-mib)&lt;BR /&gt;
       dot1qVlanCurrentEntry=1.3.6.1.2.1.17.7.1.4.2.1          (ietf/Q-BRIDGE-MIB)&lt;BR /&gt;
              ptopoConnEntry=1.3.6.1.2.1.79.1.1.1.1            (ietf/PTOPO-MIB)&lt;BR /&gt;
ctDot1qVlanForbidEgressPorts=1.3.6.1.4.1.52.4.1.2.16.7.1.3.1.1 (ctron-q-bridge-mib-ext)&lt;BR /&gt;
          ctCDPNeighborEntry=1.3.6.1.4.1.52.4.1.2.19.1.3.1     (ctron-cdp-mib)&lt;BR /&gt;
                ctAliasEntry=1.3.6.1.4.1.52.4.1.3.7.1.1.1.1    (ctron-alias-mib)                                          ...take a long time to parse. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
These OIDs are time-filtered, so per the RFCs (e.g. &lt;A href="http://www.ietf.org/rfc/rfc3512.txt" target="_blank" rel="nofollow noreferrer noopener"&gt;RFC3512&lt;/A&gt;, &lt;A href="http://www.ietf.org/rfc/rfc4502.txt" target="_blank" rel="nofollow noreferrer noopener"&gt;RFC4502&lt;/A&gt;) must return entries for all valid timeMarks. &lt;BR /&gt;
&lt;BR /&gt;
The SNMP browser should understand the behavior of a timeFiltered MIB and move on after seeing the timeFilter index increment. However, not all browsers behave in this manner. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Ensure you are using an appropriate SNMP tool - such as NetSight MIB tools - that behaves correctly. &lt;BR /&gt;
&lt;BR /&gt;
Workaround:&lt;BR /&gt;
DFE firmware 6.01.01.0020 introduced a new command which can accommodate SNMP browsers that are not timeFilter-aware. &lt;BR /&gt;
&lt;BR /&gt;
Release notes state, in the "Software Changes and Enhancements" section:A new SNMP control, "set snmp timefilter break", allows users to configure the&lt;BR /&gt;
GET-NEXT behavior of MIBs indexed with timeMark. When this is set to 'enabled',&lt;BR /&gt;
SNMP will not return incrementing index values. Many SNMP tools do not properly&lt;BR /&gt;
support timefiltered MIBs and will benefit from this new setting. When disabled,&lt;BR /&gt;
SNMP returns RFC conformant indexing.&lt;BR /&gt;
Here is the command syntax, as seen in a sample cli session:  NSeries(rw)-&amp;gt;set snmp timefilter&lt;BR /&gt;
 &lt;BR /&gt;
  Command: set snmp Create SNMP agent entries&lt;BR /&gt;
 &lt;BR /&gt;
  Object: timefilter             SNMP timefilter configuration&lt;BR /&gt;
  Usage:  set snmp timefilter break {disable | enable}&lt;BR /&gt;
 &lt;BR /&gt;
          break                  Set SNMP timefilter break (default: disabled)&lt;BR /&gt;
            disable              Disable timefilter break&lt;BR /&gt;
            enable               Enable timefilter break&lt;BR /&gt;
  NSeries(rw)-&amp;gt;&lt;BR /&gt;
Pre-upgrade workaround:&lt;BR /&gt;
In the SNMP configuration, exclude (&lt;A href="http://bit.ly/1c2ANeF" target="_blank" rel="nofollow noreferrer noopener"&gt;5610&lt;/A&gt;) the lldpRemEntry, dot1qVlanCurrentEntry,ptopoConnEntry, ctDot1qVlanForbidEgressPorts, ctCDPNeighborEntry, and ctAliasEntrybranches from the visible MIB Tree:  set snmp view viewname All subtree 1&lt;BR /&gt;
  set snmp view viewname All subtree 0.0&lt;BR /&gt;
  set snmp view viewname All subtree 1.0.8802.1.1.2.1.4.1.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.2.1.17.7.1.4.2.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.2.1.79.1.1.1.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.4.1.52.4.1.2.16.7.1.3.1.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.4.1.52.4.1.2.19.1.3.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.4.1.52.4.1.3.7.1.1.1.1 excluded</description>
    <pubDate>Wed, 04 Dec 2013 00:03:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-04T00:03:00Z</dc:date>
    <item>
      <title>DFE's SNMP MIB Walk Runs Slow when encountering TimeFiltered OIDs</title>
      <link>https://community.extremenetworks.com/t5/faqs/dfe-s-snmp-mib-walk-runs-slow-when-encountering-timefiltered/m-p/43941#M223</link>
      <description>Article ID: 10162 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
Matrix N-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Performing an SNMP MIB walk. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
High CPU utilization. &lt;BR /&gt;
&lt;BR /&gt;
Some OIDs such as...                lldpRemEntry=1.0.8802.1.1.2.1.4.1.1            (ieee/lldp-mib)&lt;BR /&gt;
       dot1qVlanCurrentEntry=1.3.6.1.2.1.17.7.1.4.2.1          (ietf/Q-BRIDGE-MIB)&lt;BR /&gt;
              ptopoConnEntry=1.3.6.1.2.1.79.1.1.1.1            (ietf/PTOPO-MIB)&lt;BR /&gt;
ctDot1qVlanForbidEgressPorts=1.3.6.1.4.1.52.4.1.2.16.7.1.3.1.1 (ctron-q-bridge-mib-ext)&lt;BR /&gt;
          ctCDPNeighborEntry=1.3.6.1.4.1.52.4.1.2.19.1.3.1     (ctron-cdp-mib)&lt;BR /&gt;
                ctAliasEntry=1.3.6.1.4.1.52.4.1.3.7.1.1.1.1    (ctron-alias-mib)                                          ...take a long time to parse. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
These OIDs are time-filtered, so per the RFCs (e.g. &lt;A href="http://www.ietf.org/rfc/rfc3512.txt" target="_blank" rel="nofollow noreferrer noopener"&gt;RFC3512&lt;/A&gt;, &lt;A href="http://www.ietf.org/rfc/rfc4502.txt" target="_blank" rel="nofollow noreferrer noopener"&gt;RFC4502&lt;/A&gt;) must return entries for all valid timeMarks. &lt;BR /&gt;
&lt;BR /&gt;
The SNMP browser should understand the behavior of a timeFiltered MIB and move on after seeing the timeFilter index increment. However, not all browsers behave in this manner. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Ensure you are using an appropriate SNMP tool - such as NetSight MIB tools - that behaves correctly. &lt;BR /&gt;
&lt;BR /&gt;
Workaround:&lt;BR /&gt;
DFE firmware 6.01.01.0020 introduced a new command which can accommodate SNMP browsers that are not timeFilter-aware. &lt;BR /&gt;
&lt;BR /&gt;
Release notes state, in the "Software Changes and Enhancements" section:A new SNMP control, "set snmp timefilter break", allows users to configure the&lt;BR /&gt;
GET-NEXT behavior of MIBs indexed with timeMark. When this is set to 'enabled',&lt;BR /&gt;
SNMP will not return incrementing index values. Many SNMP tools do not properly&lt;BR /&gt;
support timefiltered MIBs and will benefit from this new setting. When disabled,&lt;BR /&gt;
SNMP returns RFC conformant indexing.&lt;BR /&gt;
Here is the command syntax, as seen in a sample cli session:  NSeries(rw)-&amp;gt;set snmp timefilter&lt;BR /&gt;
 &lt;BR /&gt;
  Command: set snmp Create SNMP agent entries&lt;BR /&gt;
 &lt;BR /&gt;
  Object: timefilter             SNMP timefilter configuration&lt;BR /&gt;
  Usage:  set snmp timefilter break {disable | enable}&lt;BR /&gt;
 &lt;BR /&gt;
          break                  Set SNMP timefilter break (default: disabled)&lt;BR /&gt;
            disable              Disable timefilter break&lt;BR /&gt;
            enable               Enable timefilter break&lt;BR /&gt;
  NSeries(rw)-&amp;gt;&lt;BR /&gt;
Pre-upgrade workaround:&lt;BR /&gt;
In the SNMP configuration, exclude (&lt;A href="http://bit.ly/1c2ANeF" target="_blank" rel="nofollow noreferrer noopener"&gt;5610&lt;/A&gt;) the lldpRemEntry, dot1qVlanCurrentEntry,ptopoConnEntry, ctDot1qVlanForbidEgressPorts, ctCDPNeighborEntry, and ctAliasEntrybranches from the visible MIB Tree:  set snmp view viewname All subtree 1&lt;BR /&gt;
  set snmp view viewname All subtree 0.0&lt;BR /&gt;
  set snmp view viewname All subtree 1.0.8802.1.1.2.1.4.1.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.2.1.17.7.1.4.2.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.2.1.79.1.1.1.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.4.1.52.4.1.2.16.7.1.3.1.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.4.1.52.4.1.2.19.1.3.1 excluded&lt;BR /&gt;
  set snmp view viewname All subtree 1.3.6.1.4.1.52.4.1.3.7.1.1.1.1 excluded</description>
      <pubDate>Wed, 04 Dec 2013 00:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/dfe-s-snmp-mib-walk-runs-slow-when-encountering-timefiltered/m-p/43941#M223</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-04T00:03:00Z</dc:date>
    </item>
  </channel>
</rss>

