<?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: AVDECC Entity Available not sent in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35706#M7243</link>
    <description>Hello, Jakub!&lt;BR /&gt;
&lt;BR /&gt;
First of all, from your post there is no understanding switch configurations depends from connection Controller and LIstener.&lt;BR /&gt;
Also AVB configuration and license?&lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
    <pubDate>Tue, 28 Feb 2017 18:39:00 GMT</pubDate>
    <dc:creator>Alexandr_P</dc:creator>
    <dc:date>2017-02-28T18:39:00Z</dc:date>
    <item>
      <title>AVDECC Entity Available not sent</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35705#M7242</link>
      <description>Dear Experts,&lt;BR /&gt;
I have a Summit X440-8t AVB switch. I am running AVDECC on two devices connected to the switch. One device is AVDECC Controller, the second device is AVDECC Listener. When I run the Listener, I can see that it sends ADP Entity Available packet (Wireshark run on the Listener). I can also see on a network tap that this packet is sent on the wire. Despite that, the Controller does not see the packet, Wireshark run on the Controller does not see this packet. When I connect the Controller and Listener directly without a switch, then the packet is seen by the Controller.&lt;BR /&gt;
&lt;BR /&gt;
What could be the reason that packet is not sent to the Controller when connected via the switch?&lt;BR /&gt;
&lt;BR /&gt;
Kind regards,&lt;BR /&gt;
Jakub&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Feb 2017 18:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35705#M7242</guid>
      <dc:creator>Jakub_Mielczar1</dc:creator>
      <dc:date>2017-02-28T18:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: AVDECC Entity Available not sent</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35706#M7243</link>
      <description>Hello, Jakub!&lt;BR /&gt;
&lt;BR /&gt;
First of all, from your post there is no understanding switch configurations depends from connection Controller and LIstener.&lt;BR /&gt;
Also AVB configuration and license?&lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
      <pubDate>Tue, 28 Feb 2017 18:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35706#M7243</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2017-02-28T18:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: AVDECC Entity Available not sent</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35707#M7244</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
Seems to be solved. The AVDECC messages were sent with VLAN. Sending them without 802.1Q header solved the issue.&lt;BR /&gt;
&lt;BR /&gt;
Jakub&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Feb 2017 22:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/avdecc-entity-available-not-sent/m-p/35707#M7244</guid>
      <dc:creator>Jakub_Mielczar1</dc:creator>
      <dc:date>2017-02-28T22:09:00Z</dc:date>
    </item>
  </channel>
</rss>

