<?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: Device not registering in fdb in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67854#M18471</link>
    <description>Are you perhaps tagging a vlan on the handoff port instead having the vlan untagged?   One thing you could also do is plug the ap into a laptop with wireshark and see if it chirps and sends out a dhcp request.</description>
    <pubDate>Thu, 25 Jul 2019 21:03:37 GMT</pubDate>
    <dc:creator>EtherMAN</dc:creator>
    <dc:date>2019-07-25T21:03:37Z</dc:date>
    <item>
      <title>Device not registering in fdb</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67851#M18468</link>
      <description>I am trying to connect 8 Motorola SLR 5000 series repeaters to my network.  They have 10/100 interfaces set to auto negotiate with IP addresses assigned.  When I connect them I am getting a link light, and the switch is showing it connected at 100BT, but when I do a "show fdb port" I do not see the MAC address in the forwarding table.  Obviously they are not reachable via IP --layer 2 does not get setup up so layer 3 is not usable.  This is happening at different sites, different repeaters, different stacks (All Summit 450 G2's running 22.6.1.4-patch1-8).  --btw I have tried setting them to manually negotiate.&lt;BR /&gt;
&lt;BR /&gt;
My radio vendor had these repeaters successfully connected at their shop using unmanaged switches.  They were pingable and were communicating with each other via IP.&lt;BR /&gt;
&lt;BR /&gt;
Today I am going to set one up on a old D2 I have sitting around to see if I can see it register in the mac table on Enterasys gear.  For the life of me I don't see how something can come up at layer 1 but not come up on layer 2 --barring patch cord problems, and of course I have swapped out cables.&lt;BR /&gt;
&lt;BR /&gt;
Anyone have any ideas of where to go next?</description>
      <pubDate>Thu, 25 Jul 2019 17:58:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67851#M18468</guid>
      <dc:creator>Keith_Obermeie1</dc:creator>
      <dc:date>2019-07-25T17:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: Device not registering in fdb</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67852#M18469</link>
      <description>Are those devices trying to initiate &lt;I&gt;some&lt;/I&gt; sort of outbound traffic? If they are totally silent, they will not appear in the FDB and therefore you will not be able to reach them. A classic.</description>
      <pubDate>Thu, 25 Jul 2019 18:00:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67852#M18469</guid>
      <dc:creator>jeronimo</dc:creator>
      <dc:date>2019-07-25T18:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: Device not registering in fdb</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67853#M18470</link>
      <description>I've set the device to DHCP  and rebooted just to make sure that it would have some traffic to send.  No luck.</description>
      <pubDate>Thu, 25 Jul 2019 19:51:07 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67853#M18470</guid>
      <dc:creator>Keith_Obermeie1</dc:creator>
      <dc:date>2019-07-25T19:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: Device not registering in fdb</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67854#M18471</link>
      <description>Are you perhaps tagging a vlan on the handoff port instead having the vlan untagged?   One thing you could also do is plug the ap into a laptop with wireshark and see if it chirps and sends out a dhcp request.</description>
      <pubDate>Thu, 25 Jul 2019 21:03:37 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67854#M18471</guid>
      <dc:creator>EtherMAN</dc:creator>
      <dc:date>2019-07-25T21:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Device not registering in fdb</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67855#M18472</link>
      <description>laptop on the port gets a lease and works perfectly.&lt;BR /&gt;
&lt;BR /&gt;
I put an old Enterasys D2 between the Summit Stack and the repeaters, and I get L2 and L3. &lt;BR /&gt;
&lt;BR /&gt;
My only conclusion is that there is something in XOS that is preventing the repeaters from establishing L2. Time for GTAC.</description>
      <pubDate>Fri, 26 Jul 2019 01:17:37 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/device-not-registering-in-fdb/m-p/67855#M18472</guid>
      <dc:creator>Keith_Obermeie1</dc:creator>
      <dc:date>2019-07-26T01:17:37Z</dc:date>
    </item>
  </channel>
</rss>

