<?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 RUCKUS AP - POE | Syslog error: PD stopped responding to LLDP PoE TLVs from PSE. in RUCKUS Self-Help</title>
    <link>https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/RUCKUS-AP-POE-Syslog-error-PD-stopped-responding-to-LLDP-PoE/m-p/57575#M131</link>
    <description>&lt;P&gt;&lt;SPAN&gt;It's been reported that in some HP or Aruba PoE switches, continuous logs will be printed on the switch's console saying: &lt;STRONG&gt;"&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;STRONG&gt;PD stopped responding to&amp;nbsp;LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will&amp;nbsp;&lt;/STRONG&gt;&lt;STRONG&gt;be retained" &lt;/STRONG&gt;when certain models of RUCKUS APs are serviced by these switches.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;RUCKUS's engineering has identified and corrected this LLDP behavior for some specific affected AP models with a secondary ethernet uplink port.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The fix for this issue will be found on the AP patch 5.2.2.0.2116&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Feel free to open a support case with RUCKUS TAC to get this specific bug fix.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;There is also a workaround that can be applied on the PoE switch to avoid the syslog buffer being filled with those continuous logs:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;no lldp config dot3TlvEnable poeplus_config
no lldp config dot3TlvEnable eee_config&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jul 2023 16:36:45 GMT</pubDate>
    <dc:creator>Orlando_Elias</dc:creator>
    <dc:date>2023-07-12T16:36:45Z</dc:date>
    <item>
      <title>RUCKUS AP - POE | Syslog error: PD stopped responding to LLDP PoE TLVs from PSE.</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/RUCKUS-AP-POE-Syslog-error-PD-stopped-responding-to-LLDP-PoE/m-p/57575#M131</link>
      <description>&lt;P&gt;&lt;SPAN&gt;It's been reported that in some HP or Aruba PoE switches, continuous logs will be printed on the switch's console saying: &lt;STRONG&gt;"&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;STRONG&gt;PD stopped responding to&amp;nbsp;LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will&amp;nbsp;&lt;/STRONG&gt;&lt;STRONG&gt;be retained" &lt;/STRONG&gt;when certain models of RUCKUS APs are serviced by these switches.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;RUCKUS's engineering has identified and corrected this LLDP behavior for some specific affected AP models with a secondary ethernet uplink port.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The fix for this issue will be found on the AP patch 5.2.2.0.2116&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Feel free to open a support case with RUCKUS TAC to get this specific bug fix.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;There is also a workaround that can be applied on the PoE switch to avoid the syslog buffer being filled with those continuous logs:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;no lldp config dot3TlvEnable poeplus_config
no lldp config dot3TlvEnable eee_config&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 16:36:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/RUCKUS-AP-POE-Syslog-error-PD-stopped-responding-to-LLDP-PoE/m-p/57575#M131</guid>
      <dc:creator>Orlando_Elias</dc:creator>
      <dc:date>2023-07-12T16:36:45Z</dc:date>
    </item>
  </channel>
</rss>

