<?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 VDX 6740 SNMP VLAN port-channel Interfaces query in Data Center (VDX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-vdx/vdx-6740-snmp-vlan-port-channel-interfaces-query/m-p/65235#M313</link>
    <description>&lt;P&gt;Dear community, employees, wizards - I need help.&lt;/P&gt;&lt;P&gt;I have a few VDX6740s, vcs/rbridge, and they work just fine. I want to run an SNMP query against it, finding all the ports that are in a given VLAN.&lt;/P&gt;&lt;P&gt;Using dot1qVlanCurrentEgressPorts ( 1.3.6.1.2.1.17.7.1.4.2.1.4 ) together with dot1dBasePortIfIndex ( 1.3.6.1.2.1.17.1.4.1.2 ), I can get the correct interface(s), &lt;EM&gt;unless&lt;/EM&gt; I’m hitting a port channel. I do get a result from CurrentEgressPorts indicating a port, but there’s no corresponding entry in the dBasePortIfIndex - as a matter of fact, that table does &lt;EM&gt;not&lt;/EM&gt; contain any port channel entries - not the port-channel interface, not the member port interface, nothing&lt;/P&gt;&lt;P&gt;There’s also no obvious (to me) way to correlate that number with anything in the LAG-MIB, i.e. dot3adAggPortList/PortTable ( 1.2.840.10006.300.43.1…. )&lt;/P&gt;&lt;P&gt;Is there some magical piece of math that’s eluding me? Maybe some bit-math that involves the vcs-id or the rbridge-id? Do I have to re-run the query within some fancy snmp context?&lt;/P&gt;&lt;P&gt;Any help, documentation, pointers, etc. would be greatly appreciated. As a last resort I’m considering to query the FdbTable, but that feels improper.&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Frank M.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 28 Mar 2021 21:05:28 GMT</pubDate>
    <dc:creator>Frank</dc:creator>
    <dc:date>2021-03-28T21:05:28Z</dc:date>
    <item>
      <title>VDX 6740 SNMP VLAN port-channel Interfaces query</title>
      <link>https://community.extremenetworks.com/t5/data-center-vdx/vdx-6740-snmp-vlan-port-channel-interfaces-query/m-p/65235#M313</link>
      <description>&lt;P&gt;Dear community, employees, wizards - I need help.&lt;/P&gt;&lt;P&gt;I have a few VDX6740s, vcs/rbridge, and they work just fine. I want to run an SNMP query against it, finding all the ports that are in a given VLAN.&lt;/P&gt;&lt;P&gt;Using dot1qVlanCurrentEgressPorts ( 1.3.6.1.2.1.17.7.1.4.2.1.4 ) together with dot1dBasePortIfIndex ( 1.3.6.1.2.1.17.1.4.1.2 ), I can get the correct interface(s), &lt;EM&gt;unless&lt;/EM&gt; I’m hitting a port channel. I do get a result from CurrentEgressPorts indicating a port, but there’s no corresponding entry in the dBasePortIfIndex - as a matter of fact, that table does &lt;EM&gt;not&lt;/EM&gt; contain any port channel entries - not the port-channel interface, not the member port interface, nothing&lt;/P&gt;&lt;P&gt;There’s also no obvious (to me) way to correlate that number with anything in the LAG-MIB, i.e. dot3adAggPortList/PortTable ( 1.2.840.10006.300.43.1…. )&lt;/P&gt;&lt;P&gt;Is there some magical piece of math that’s eluding me? Maybe some bit-math that involves the vcs-id or the rbridge-id? Do I have to re-run the query within some fancy snmp context?&lt;/P&gt;&lt;P&gt;Any help, documentation, pointers, etc. would be greatly appreciated. As a last resort I’m considering to query the FdbTable, but that feels improper.&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Frank M.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 28 Mar 2021 21:05:28 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-vdx/vdx-6740-snmp-vlan-port-channel-interfaces-query/m-p/65235#M313</guid>
      <dc:creator>Frank</dc:creator>
      <dc:date>2021-03-28T21:05:28Z</dc:date>
    </item>
  </channel>
</rss>

