<?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: Easy steps to configure SNMPv3 to work with 3rd party NMS in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24922#M2910</link>
    <description>I think they can be different.  I use the same just for convenience.  Also, for security reasons, there isn't a big need for us.  Some places though, you might want to think about a more complex string that's unique.</description>
    <pubDate>Sat, 22 Jul 2017 20:11:00 GMT</pubDate>
    <dc:creator>Jeremy_Gibbs</dc:creator>
    <dc:date>2017-07-22T20:11:00Z</dc:date>
    <item>
      <title>Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24917#M2905</link>
      <description>What are the easy steps to configure snmpv3 on XOS switch that will be discovered by 3rd party NMS via snmpv3.&lt;BR /&gt;
&lt;BR /&gt;
in GTAC i can see some commands that is to connect the XOS device to Netsight.&lt;BR /&gt;
&lt;BR /&gt;
is defining snmpv3 user and snmpv3 would be enough for the xos device to be seen and managed by 3rd party NMS.&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Jul 2017 19:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24917#M2905</guid>
      <dc:creator>Arjumand_Qazi</dc:creator>
      <dc:date>2017-07-20T19:43:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24918#M2906</link>
      <description>Hi Arjumand,&lt;BR /&gt;
&lt;BR /&gt;
Take a look at the following script for EXOS switches. It will walk you through SNMPv3 configuration.&lt;BR /&gt;
&lt;A href="https://github.com/extremenetworks/ExtremeScripting/tree/master/EXOS/Python/snmpassist" target="_blank" rel="nofollow noreferrer noopener"&gt;https://github.com/extremenetworks/ExtremeScripting/tree/master/EXOS/Python/snmpassist&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Jul 2017 20:46:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24918#M2906</guid>
      <dc:creator>BrandonC</dc:creator>
      <dc:date>2017-07-20T20:46:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24919#M2907</link>
      <description>configure snmpv3 add user SNMPUSERNAMEE authentication md5 SOMERANDOMSTRING privacy SOMERANDOMSTRING  &lt;BR /&gt;
&lt;BR /&gt;
 configure snmpv3 add group GROUPNAME user SNMPUSERNAME sec-model usm&lt;BR /&gt;
&lt;BR /&gt;
 configure snmpv3 add access GROUPNAMEnetman sec-model usm sec-level priv read-view defaultAdminView write-view defaultAdminView notify-view defaultNotifyView&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Jul 2017 22:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24919#M2907</guid>
      <dc:creator>Jeremy_Gibbs</dc:creator>
      <dc:date>2017-07-20T22:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24920#M2908</link>
      <description>Thanks gentlemen&lt;BR /&gt;</description>
      <pubDate>Sat, 22 Jul 2017 19:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24920#M2908</guid>
      <dc:creator>Arjumand_Qazi</dc:creator>
      <dc:date>2017-07-22T19:03:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24921#M2909</link>
      <description>Hi Jeremy,&lt;BR /&gt;
&lt;BR /&gt;
while configuring user for snmpv3, md5 and privacy string should always be different ?&lt;BR /&gt;</description>
      <pubDate>Sat, 22 Jul 2017 19:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24921#M2909</guid>
      <dc:creator>Arjumand_Qazi</dc:creator>
      <dc:date>2017-07-22T19:05:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24922#M2910</link>
      <description>I think they can be different.  I use the same just for convenience.  Also, for security reasons, there isn't a big need for us.  Some places though, you might want to think about a more complex string that's unique.</description>
      <pubDate>Sat, 22 Jul 2017 20:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24922#M2910</guid>
      <dc:creator>Jeremy_Gibbs</dc:creator>
      <dc:date>2017-07-22T20:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24923#M2911</link>
      <description>hello,&lt;BR /&gt;
&lt;BR /&gt;
tried snmpv3 config with Brocade's BNA. it didnt work&lt;BR /&gt;
first tried with snmpv3 config&lt;BR /&gt;
then with snmpv2&lt;BR /&gt;
made an snmp user "xtreme"  password of this user and md5 is same.. &amp;lt;-- can this be a problem.&lt;BR /&gt;
&lt;BR /&gt;
the snmpv3 configuration made was..&lt;BR /&gt;
configure snmpv3 add user xtreme authentication md5 xtreme123 privacy des xtreme456&lt;BR /&gt;
configure snmpv3 add group x-group user xtreme sec-model usm&lt;BR /&gt;
configure snmpv3 add access x-group sec-model usm sec-level priv read-view defaultAdminView write-view defaultAdminView notify-view defaultAdminView&lt;BR /&gt;
&lt;BR /&gt;
disable snmp access snmp-v1v2c&lt;BR /&gt;
disable snmpv3 default-user&lt;BR /&gt;
disable snmpv3 default-group &lt;BR /&gt;
&lt;BR /&gt;
since this config did not work i had to remove the snmpv3 and now in the "sh config" i can see this&lt;BR /&gt;
&lt;BR /&gt;
# Module snmpMaster configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure snmpv3 add community "v1v2cNotifyComm1" name "xtreme@123" user "v1v2cNotifyUser1" &lt;BR /&gt;
configure snmpv3 add community "xtreme@123" name "xtreme@123" user "v1v2c_ro" &lt;BR /&gt;
disable snmpv3 community "xtreme@123"&lt;BR /&gt;
configure snmpv3 add target-addr "v1v2cNotifyTAddr1" param "v1v2cNotifyParam1" ipaddress 172.16.0.91 transport-port 162 tag-list "defaultNotify" &lt;BR /&gt;
configure snmpv3 add target-params "v1v2cNotifyParam1" user "v1v2cNotifyUser1" mp-model snmpv2c sec-model snmpv2c sec-level noauth &lt;BR /&gt;
enable snmp access&lt;BR /&gt;
enable snmp access snmp-v1v2c&lt;BR /&gt;
enable snmp access snmpv3&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module stp configuration.&lt;BR /&gt;
&lt;BR /&gt;
the above community defined "xtreme@123" was for snmpv2 and snmpv3 has taken over this.&lt;BR /&gt;
&lt;BR /&gt;
we need to remove this all configuration and add snmpv3 only.. &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Sun, 23 Jul 2017 15:12:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24923#M2911</guid>
      <dc:creator>Arjumand_Qazi</dc:creator>
      <dc:date>2017-07-23T15:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24924#M2912</link>
      <description>I understand you have a opened a GTAC case for this issue. One of our GTAC engineer will get back to you shortly.</description>
      <pubDate>Mon, 24 Jul 2017 07:45:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24924#M2912</guid>
      <dc:creator>Ram3</dc:creator>
      <dc:date>2017-07-24T07:45:00Z</dc:date>
    </item>
    <item>
      <title>RE: Easy steps to configure SNMPv3 to work with 3rd party NMS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24925#M2913</link>
      <description>Yes i did, i am hoping a quick resolution for this..&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jul 2017 13:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/easy-steps-to-configure-snmpv3-to-work-with-3rd-party-nms/m-p/24925#M2913</guid>
      <dc:creator>Arjumand_Qazi</dc:creator>
      <dc:date>2017-07-24T13:25:00Z</dc:date>
    </item>
  </channel>
</rss>

