<?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 Expectations for Setting and Clearing SNMP Commands on Enterasys Switching products in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/expectations-for-setting-and-clearing-snmp-commands-on-enterasys/m-p/41943#M80</link>
    <description>Article ID: 10308 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2, B3, B2, A2&lt;BR /&gt;
D-Series&lt;BR /&gt;
G-Series&lt;BR /&gt;
I-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt; &lt;BR /&gt;
'&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command is present after clearing a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command. &lt;BR /&gt;
'&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command is present after overriding or removing a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
The SNMP commands for the SecureStacks, D-Series, G-Series, and I-Series are designed a little differently than the SNMP commands for the other cli-based Enterasys switching products. &lt;BR /&gt;
&lt;BR /&gt;
On these products; if you Clear a default Set command (by issuing the Clear command), the Set command is removed and a Clear command appears; and if you eliminate the Clear command (by issuing the Set command or by removing the Clear command before downloading/activating the configuration), the Set command reappears. &lt;BR /&gt;
&lt;BR /&gt;
For example... &lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e7e&lt;BR /&gt;
0657521e0641967b150156:&lt;BR /&gt;
 . . .&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;clear snmp community public&lt;/B&gt;&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
clear snmp community :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e&lt;BR /&gt;
7e0657521e0641967b150156:&lt;BR /&gt;
 . . .&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;set snmp community public&lt;/B&gt;&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e7e&lt;BR /&gt;
0657521e0641967b150156:&lt;BR /&gt;
 . . .&lt;BR /&gt;
C2(su)-&amp;gt;&lt;BR /&gt;
On the other products, if you Clear a default Set command (by issuing the Clear command or by removing the Set command before downloading/activating the configuration), the Set command is removed and there is no visible command for that feature; and if you issue the Set command, the Set command reappears. &lt;BR /&gt;
&lt;BR /&gt;
For example... &lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community public&lt;BR /&gt;
 . . .&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;clear snmp community public&lt;/B&gt;&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;set snmp community public&lt;/B&gt;&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community public&lt;BR /&gt;
 . . .&lt;BR /&gt;
N7(su)-&amp;gt;&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
FAD (Functions as Designed). &lt;BR /&gt;
&lt;BR /&gt;
The difference in the SNMP command sets of these two sets of hardware is largely irrelevant to the flexibility and effectiveness of SNMP operation. However, there is at least one possible caveat that deserves mention: &lt;BR /&gt;
&lt;BR /&gt;
If it is desired to "simplify" a (for example) SecureStack's non-default SNMP configuration by offloading the configuration, removing the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' commands, then reloading the configuration and booting off of it (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;), it will be observed that the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' commands are indeed no longer present. However, if the user then does not notice that the original associated '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set snmp...&lt;/PRE&gt;&lt;/DIV&gt;' commands (establishing a public SNMPv1 community name, default SNMPv2C/SNMPv3 users, and read/write access to all MIBs) have been re-established, this can lead to a security hole that could be exploited. &lt;BR /&gt;
&lt;BR /&gt;
As with any configuration change, review the resulting configuration to ensure that it is as you intended. &lt;BR /&gt;
&lt;BR /&gt;
For a more general discussion about clearing commands, please refer to &lt;A href="http://bit.ly/1gGLIj1" target="_blank" rel="nofollow noreferrer noopener"&gt;5542&lt;/A&gt;.</description>
    <pubDate>Tue, 04 Feb 2014 00:14:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2014-02-04T00:14:00Z</dc:date>
    <item>
      <title>Expectations for Setting and Clearing SNMP Commands on Enterasys Switching products</title>
      <link>https://community.extremenetworks.com/t5/faqs/expectations-for-setting-and-clearing-snmp-commands-on-enterasys/m-p/41943#M80</link>
      <description>Article ID: 10308 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2, B3, B2, A2&lt;BR /&gt;
D-Series&lt;BR /&gt;
G-Series&lt;BR /&gt;
I-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt; &lt;BR /&gt;
'&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command is present after clearing a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command. &lt;BR /&gt;
'&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command is present after overriding or removing a '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' command. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
The SNMP commands for the SecureStacks, D-Series, G-Series, and I-Series are designed a little differently than the SNMP commands for the other cli-based Enterasys switching products. &lt;BR /&gt;
&lt;BR /&gt;
On these products; if you Clear a default Set command (by issuing the Clear command), the Set command is removed and a Clear command appears; and if you eliminate the Clear command (by issuing the Set command or by removing the Clear command before downloading/activating the configuration), the Set command reappears. &lt;BR /&gt;
&lt;BR /&gt;
For example... &lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e7e&lt;BR /&gt;
0657521e0641967b150156:&lt;BR /&gt;
 . . .&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;clear snmp community public&lt;/B&gt;&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
clear snmp community :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e&lt;BR /&gt;
7e0657521e0641967b150156:&lt;BR /&gt;
 . . .&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;set snmp community public&lt;/B&gt;&lt;BR /&gt;
C2(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community :3fb03022e4966512343b511c263dcf1240739359ec6cad7d8c6277007e7e&lt;BR /&gt;
0657521e0641967b150156:&lt;BR /&gt;
 . . .&lt;BR /&gt;
C2(su)-&amp;gt;&lt;BR /&gt;
On the other products, if you Clear a default Set command (by issuing the Clear command or by removing the Set command before downloading/activating the configuration), the Set command is removed and there is no visible command for that feature; and if you issue the Set command, the Set command reappears. &lt;BR /&gt;
&lt;BR /&gt;
For example... &lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community public&lt;BR /&gt;
 . . .&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;clear snmp community public&lt;/B&gt;&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;set snmp community public&lt;/B&gt;&lt;BR /&gt;
N7(su)-&amp;gt;&lt;B&gt;show config snmp&lt;/B&gt;&lt;BR /&gt;
 . . .&lt;BR /&gt;
set snmp community public&lt;BR /&gt;
 . . .&lt;BR /&gt;
N7(su)-&amp;gt;&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
FAD (Functions as Designed). &lt;BR /&gt;
&lt;BR /&gt;
The difference in the SNMP command sets of these two sets of hardware is largely irrelevant to the flexibility and effectiveness of SNMP operation. However, there is at least one possible caveat that deserves mention: &lt;BR /&gt;
&lt;BR /&gt;
If it is desired to "simplify" a (for example) SecureStack's non-default SNMP configuration by offloading the configuration, removing the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' commands, then reloading the configuration and booting off of it (&lt;A href="http://bit.ly/1nz1lHy" target="_blank" rel="nofollow noreferrer noopener"&gt;5623&lt;/A&gt;), it will be observed that the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;clear snmp...&lt;/PRE&gt;&lt;/DIV&gt;' commands are indeed no longer present. However, if the user then does not notice that the original associated '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set snmp...&lt;/PRE&gt;&lt;/DIV&gt;' commands (establishing a public SNMPv1 community name, default SNMPv2C/SNMPv3 users, and read/write access to all MIBs) have been re-established, this can lead to a security hole that could be exploited. &lt;BR /&gt;
&lt;BR /&gt;
As with any configuration change, review the resulting configuration to ensure that it is as you intended. &lt;BR /&gt;
&lt;BR /&gt;
For a more general discussion about clearing commands, please refer to &lt;A href="http://bit.ly/1gGLIj1" target="_blank" rel="nofollow noreferrer noopener"&gt;5542&lt;/A&gt;.</description>
      <pubDate>Tue, 04 Feb 2014 00:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/expectations-for-setting-and-clearing-snmp-commands-on-enterasys/m-p/41943#M80</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2014-02-04T00:14:00Z</dc:date>
    </item>
  </channel>
</rss>

