<?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: ICX 8200 port-profile questions in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/104209#M7271</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What issue # says this is fixed? I cannot find it&lt;/P&gt;</description>
    <pubDate>Thu, 03 Apr 2025 23:08:20 GMT</pubDate>
    <dc:creator>matthewlampe</dc:creator>
    <dc:date>2025-04-03T23:08:20Z</dc:date>
    <item>
      <title>ICX 8200 port-profile questions</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/86458#M5973</link>
      <description>&lt;P&gt;Hello. Is there a way to exclude ports from being assigned LLDP or OUI dynamic port profiles? Our issue is that we have some OUI-based dynamic port profiles that are getting assigned to ports that actually have other switches attached. I assume it is because it sees the MACs of the devices attached to that remote switch and they match the OUI so it assigns the profile to that port.&lt;/P&gt;&lt;P&gt;Also, when specifying a dynamic port profile based on LLDP, is it possible to use a wildcard or partial match in the system-name and system-desc fields? I think this was the case in the 10010a firmware- it seemed I could use just the first few characters of each and it would match, but in the 10010c_cd3 version is seems to require an exact match in both for a device to match.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sun, 14 Jul 2024 01:19:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/86458#M5973</guid>
      <dc:creator>KabalVT</dc:creator>
      <dc:date>2024-07-14T01:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: ICX 8200 port-profile questions</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/88898#M6007</link>
      <description>&lt;P&gt;Hi KabalVT&lt;/P&gt;&lt;P&gt;Thank you for reaching us.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you let us know if you are using dynamic port-profile for AP devices ?&lt;/P&gt;&lt;P&gt;Below are few links that will help you setup&amp;nbsp;dynamic port-profile for ICX switches.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT face="courier new,courier" size="2"&gt;&lt;A href="https://docs.commscope.com/bundle/fastiron-10010-managementguide/page/GUID-42BFFDF9-E71F-4C81-99F6-2792F0A7CF79.html" target="_blank"&gt;https://docs.commscope.com/bundle/fastiron-10010-managementguide/page/GUID-42BFFDF9-E71F-4C81-99F6-2792F0A7CF79.html&lt;/A&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="courier new,courier" size="2"&gt;&lt;A href="https://docs.commscope.com/bundle/fastiron-10010-managementguide/page/GUID-866F083F-8206-4F16-A309-BA3CE419FCEF.html" target="_blank"&gt;https://docs.commscope.com/bundle/fastiron-10010-managementguide/page/GUID-866F083F-8206-4F16-A309-BA3CE419FCEF.html&lt;/A&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Please run though them and let us know if any concerns.&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2024 16:51:35 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/88898#M6007</guid>
      <dc:creator>Chandini</dc:creator>
      <dc:date>2024-07-15T16:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: ICX 8200 port-profile questions</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/89547#M6033</link>
      <description>&lt;P&gt;Yes, I am using dynamic port-profile, for APs and other devices. I am trying to use lldp-device for this. It seems in the 10010c_cd3 firmware, an exact match of the system-name and system-desc fields are both required, or it won't apply. Previously it seemed to be OK with a partial match. For example:&lt;/P&gt;&lt;PRE&gt;lldp-device system-name "RuckusAP" system-desc "Ruckus T310D Multimedia Hotzone Wireless AP/SW Version: 108.0.0.0.703"&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;is now required, where before&lt;/P&gt;&lt;PRE&gt;lldp-device system-name "Ruck" system-desc "Ruckus T3"&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;would have worked, because Ruck matched the first part of the lldp system name and Ruckus T3 matched the first part of the system description.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2024 17:05:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/89547#M6033</guid>
      <dc:creator>KabalVT</dc:creator>
      <dc:date>2024-07-16T17:05:13Z</dc:date>
    </item>
    <item>
      <title>Re: ICX 8200 port-profile questions</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/92637#M6471</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi KabalVT&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ack and noted. I did take a look into 10.0.10c_cd3 release notes to check if any enhancement on the port-profile feature. I noticed that port profile feature was introduced in 10.0.10 version and one issue which is related to port profile was fixed in 10.0.10b.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Below is the link you can refer:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT face="courier new,courier" size="2"&gt;&lt;SPAN&gt;&lt;A href="https://support.ruckuswireless.com/documents/4765" target="_blank"&gt;https://support.ruckuswireless.com/documents/4765&lt;/A&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I suppose this could be the reason you are seeing a difference in 10.0.10a and 10.0.10c_cd3 for port profile setup.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2024 14:11:58 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/92637#M6471</guid>
      <dc:creator>Chandini</dc:creator>
      <dc:date>2024-07-22T14:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: ICX 8200 port-profile questions</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/104209#M7271</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What issue # says this is fixed? I cannot find it&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 23:08:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/104209#M7271</guid>
      <dc:creator>matthewlampe</dc:creator>
      <dc:date>2025-04-03T23:08:20Z</dc:date>
    </item>
    <item>
      <title>Re: ICX 8200 port-profile questions</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/104210#M7272</link>
      <description>&lt;P&gt;Did you ever figure out a workaround or fix to this?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 23:11:02 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/ICX-8200-port-profile-questions/m-p/104210#M7272</guid>
      <dc:creator>matthewlampe</dc:creator>
      <dc:date>2025-04-03T23:11:02Z</dc:date>
    </item>
  </channel>
</rss>

