<?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: snmp port status X670-48x in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70269#M18766</link>
    <description>We use snpmc and use that to get link status on all trunk links between switches.. This gives our NOC more intel about the link other than just a port showing down.  Here is how we have it set in our polling server.  I  don't know what you are doing your mib walks and polling with but the trick is to get the right interface id (1001) for port 1 and so on ... and set normal status to up to get a trap with link specific data you have labeled in the link object.  We always Poll closest switch to core.  Not sure what other attributes you may be trying to get from the port.  &lt;BR /&gt;
&lt;BR /&gt;
Still can't poll light levels via a mib form any of the optical links or ports like many other vendors can.  Would be great to be able to graph those levels for desegregation.</description>
    <pubDate>Wed, 31 Jul 2019 21:42:20 GMT</pubDate>
    <dc:creator>EtherMAN</dc:creator>
    <dc:date>2019-07-31T21:42:20Z</dc:date>
    <item>
      <title>snmp port status X670-48x</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70267#M18764</link>
      <description>how can I read the status of the ports via SNMP. oid .1.3.6.1.4.1.1916.1.4.2.1.3 not working.&lt;BR /&gt;
&lt;BR /&gt;
snmpwalk -v 2c -c a7V2Y9W 10.147.220.250  .1.3.6.1.4.1.1916.1.4.2.1.3&lt;BR /&gt;
SNMPv2-SMI::enterprises.1916.1.4.2.1.3 = No Such Object available on this agent at this OID&lt;BR /&gt;
&lt;BR /&gt;
 ExtremeXOS version 16.2.4.5 by release-manager</description>
      <pubDate>Wed, 31 Jul 2019 15:54:43 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70267#M18764</guid>
      <dc:creator>AntonR</dc:creator>
      <dc:date>2019-07-31T15:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: snmp port status X670-48x</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70268#M18765</link>
      <description>Why not simply use IF-MIB::ifOperStatus:&lt;BR /&gt;
&lt;BR /&gt;
.1.3.6.1.2.1.2.2.1.8.1001 = INTEGER: down(2)&lt;BR /&gt;
.1.3.6.1.2.1.2.2.1.8.1002 = INTEGER: down(2)&lt;BR /&gt;
.1.3.6.1.2.1.2.2.1.8.1003 = INTEGER: down(2)&lt;BR /&gt;
.1.3.6.1.2.1.2.2.1.8.1004 = INTEGER: down(2)</description>
      <pubDate>Wed, 31 Jul 2019 16:00:10 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70268#M18765</guid>
      <dc:creator>jeronimo</dc:creator>
      <dc:date>2019-07-31T16:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: snmp port status X670-48x</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70269#M18766</link>
      <description>We use snpmc and use that to get link status on all trunk links between switches.. This gives our NOC more intel about the link other than just a port showing down.  Here is how we have it set in our polling server.  I  don't know what you are doing your mib walks and polling with but the trick is to get the right interface id (1001) for port 1 and so on ... and set normal status to up to get a trap with link specific data you have labeled in the link object.  We always Poll closest switch to core.  Not sure what other attributes you may be trying to get from the port.  &lt;BR /&gt;
&lt;BR /&gt;
Still can't poll light levels via a mib form any of the optical links or ports like many other vendors can.  Would be great to be able to graph those levels for desegregation.</description>
      <pubDate>Wed, 31 Jul 2019 21:42:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70269#M18766</guid>
      <dc:creator>EtherMAN</dc:creator>
      <dc:date>2019-07-31T21:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: snmp port status X670-48x</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70270#M18767</link>
      <description>Well, there's the concept of snmptable which allows you to get all the data, make easy correlation between the fields, and finally extract what you need.&lt;BR /&gt;
&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;# snmptable switch IF-MIB::ifTable&lt;BR /&gt;SNMP table: IF-MIB::ifTable&lt;BR /&gt;&lt;BR /&gt; ifIndex                                 ifDescr         ifType ifMtu    ifSpeed  ifPhysAddress ifAdminStatus ifOperStatus  ifLastChange ifInOctets ifInUcastPkts ifInNUcastPkts ifInDiscards ifInErrors ifInUnknownProtos ifOutOctets ifOutUcastPkts ifOutNUcastPkts ifOutDiscards ifOutErrors ifOutQLen           ifSpecific&lt;BR /&gt;    1001                   X690-48x-2q-4c Port 1 ethernetCsmacd  1500          0 0:4:96:af:51:2          down         down  0:0:00:24.00          0             0              0            0          0                 0           0              0               0             0           0         0 SNMPv2-SMI::internet&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Of course, polling the entire table each time is quite heavy on the SNMP engine, so snmpget'ing specific values might be better. It all depends on the implementation (caching etc.) Each time you are confronted with these tasks it feels like a dark art ?</description>
      <pubDate>Thu, 01 Aug 2019 17:03:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70270#M18767</guid>
      <dc:creator>jeronimo</dc:creator>
      <dc:date>2019-08-01T17:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: snmp port status X670-48x</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70271#M18768</link>
      <description>It is surprising on how much polling even the lower performance models like the 430 can take before it impacts anything.  We have Cacti pulling port stats for bandwidth. errors. temp.  Solarwinds for sflow. SNMPC for traps and switch to switch links.  Extreme NMS for configs and management .  All grabbing stuff every 5 minutes on about 12K interfaces 3k or so devices.   Everything is still happy and doing it's job LOL.</description>
      <pubDate>Thu, 01 Aug 2019 21:52:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/snmp-port-status-x670-48x/m-p/70271#M18768</guid>
      <dc:creator>EtherMAN</dc:creator>
      <dc:date>2019-08-01T21:52:54Z</dc:date>
    </item>
  </channel>
</rss>

