<?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 we have upgraded to 8.3.121.0 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057182#M208357</link>
    <description>&lt;P&gt;we have upgraded to 8.3.121.0&lt;/P&gt;
&lt;P&gt;and we had a lot of Interferences. On 5GHz we've found a radar detection that would make the radios reset and go through negotiation again...&lt;/P&gt;
&lt;P&gt;good luck,&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jul 2017 19:55:14 GMT</pubDate>
    <dc:creator>ruimartins1000</dc:creator>
    <dc:date>2017-07-07T19:55:14Z</dc:date>
    <item>
      <title>BAD TLV ENTRY</title>
      <link>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057179#M208354</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a problem getting 2 1832is to talk to each other... They are both K9C controller capable mobility express App with the same software version 8.3.x. One is set up as a controller and has a fixed IP for the controller part and DHCP for the AP part. second one is joined to the same network and subnet. DNS CAPWAP discovery is used with a DNS record pointing to the controller fixed IP. I can see in the console of the connecting AP that it sends out a CAPWAP request and get an answer from the controller IP. it then starts DTLS setup. this is most of the times followed by a DTLS Teardown and a new discovery is initiated. But occasionally the process continues and I get CAPWAP Status: Join. I can see that it connects &amp;nbsp;to the controller but before the process is done and root should occur I get BAD TLV Received followed by a packet was received that caused the connection to close and everything starts over again...&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have tried different cables and switch ports, no change... the only thing I can think of is that the switches are L2 but not L3 capable and also non managed. I told the customer that they need to get a managed L3 switch since they want to enable the guest network, but I didn't have one to test with.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Does anyone have an idea or have seen this before?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;/Hasse&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 13:26:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057179#M208354</guid>
      <dc:creator>driver_288</dc:creator>
      <dc:date>2021-07-05T13:26:32Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057180#M208355</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Did you come up with something? I'm experiencing the same with a small setup of 3 1832's with ME in version: 8.3.112.0&lt;/P&gt;
&lt;P&gt;Today we've set the following:&lt;/P&gt;
&lt;P&gt;Enabled CleanAir RRM&lt;BR /&gt;Disabled lower Data Rates.&lt;BR /&gt;Disabled Green IT stuff from Cisco Switch.&lt;BR /&gt;Passed the Power Inline config to Critical in the Switch.&lt;/P&gt;
&lt;P&gt;Start monitoring the solution again.&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 16:37:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057180#M208355</guid>
      <dc:creator>ruimartins1000</dc:creator>
      <dc:date>2017-05-09T16:37:26Z</dc:date>
    </item>
    <item>
      <title>I'm having the same issue</title>
      <link>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057181#M208356</link>
      <description>&lt;P&gt;I'm having the same issue here. &amp;nbsp;Any ideas on what could be the cause and possible solution?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2017 18:54:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057181#M208356</guid>
      <dc:creator>Jeremy Scho</dc:creator>
      <dc:date>2017-07-07T18:54:20Z</dc:date>
    </item>
    <item>
      <title>we have upgraded to 8.3.121.0</title>
      <link>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057182#M208357</link>
      <description>&lt;P&gt;we have upgraded to 8.3.121.0&lt;/P&gt;
&lt;P&gt;and we had a lot of Interferences. On 5GHz we've found a radar detection that would make the radios reset and go through negotiation again...&lt;/P&gt;
&lt;P&gt;good luck,&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2017 19:55:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/bad-tlv-entry/m-p/3057182#M208357</guid>
      <dc:creator>ruimartins1000</dc:creator>
      <dc:date>2017-07-07T19:55:14Z</dc:date>
    </item>
  </channel>
</rss>

