<?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: frequent 'spanning tree topology change from' alerts access switch in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216347#M277024</link>
    <description>&lt;P&gt;If you like to not to happen this regularly, i suggest to setup a spanning tree priorty and root bridge and alternative root bridge&lt;/P&gt;
&lt;P&gt;so the VLAN not have these kind of changes as regularly&lt;/P&gt;
&lt;P&gt;again this is high level - but again we need to look where this happening and what device model and how your network looks like.&lt;/P&gt;
&lt;P&gt;some guide lines :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/10556-16.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/10556-16.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/28943-170.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/28943-170.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Oct 2024 18:03:01 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2024-10-28T18:03:01Z</dc:date>
    <item>
      <title>frequent 'spanning tree topology change from' alerts access switches</title>
      <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216343#M277023</link>
      <description>&lt;P&gt;Hi everyone,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m experiencing frequent “spanning tree topology change from enterprise” alerts on several switches in different areas. I’ve already checked and confirmed that “spanning-tree portfast edge” and “spanning-tree bpduguard enable” are configured on all access switches. Has anyone dealt with this issue and can share their solution or insights?&amp;nbsp;Thanks!&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sem título.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/232574iACC61AA776318FF8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Sem título.png" alt="Sem título.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 17:57:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216343#M277023</guid>
      <dc:creator>JSNascimento</dc:creator>
      <dc:date>2024-10-28T17:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: frequent 'spanning tree topology change from' alerts access switch</title>
      <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216347#M277024</link>
      <description>&lt;P&gt;If you like to not to happen this regularly, i suggest to setup a spanning tree priorty and root bridge and alternative root bridge&lt;/P&gt;
&lt;P&gt;so the VLAN not have these kind of changes as regularly&lt;/P&gt;
&lt;P&gt;again this is high level - but again we need to look where this happening and what device model and how your network looks like.&lt;/P&gt;
&lt;P&gt;some guide lines :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/10556-16.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/10556-16.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/28943-170.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/28943-170.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 18:03:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216347#M277024</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2024-10-28T18:03:01Z</dc:date>
    </item>
    <item>
      <title>Re: frequent 'spanning tree topology change from' alerts access switch</title>
      <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216353#M277025</link>
      <description>&lt;P&gt;You config port connect two SW as edge ?&lt;/P&gt;
&lt;P&gt;That wrong you need to remove portfast edge in port connect SW&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 18:26:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216353#M277025</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-10-28T18:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: frequent 'spanning tree topology change from' alerts access switch</title>
      <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216364#M277027</link>
      <description>&lt;P&gt;Thanks for your reply. I have set the following configuration on all access ports of the access switches:&lt;BR /&gt;interface GigabitEthernet1/0/4&lt;BR /&gt;switchport access vlan 31&lt;BR /&gt;switchport mode access&lt;BR /&gt;switchport port-security violation protect&lt;BR /&gt;snmp trap mac-notification change added&lt;BR /&gt;snmp trap mac-notification change removed&lt;BR /&gt;spanning-tree portfast edge&lt;BR /&gt;spanning-tree bpduguard enable&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 18:40:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216364#M277027</guid>
      <dc:creator>JSNascimento</dc:creator>
      <dc:date>2024-10-28T18:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: frequent 'spanning tree topology change from' alerts access switch</title>
      <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216371#M277029</link>
      <description>&lt;P&gt;Share topolgy if you can&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 18:47:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216371#M277029</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-10-28T18:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: frequent 'spanning tree topology change from' alerts access switch</title>
      <link>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216379#M277030</link>
      <description>&lt;P&gt;On the trunk ports allow VLANS selectively specific vlans and not all vlans&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 18:56:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/frequent-spanning-tree-topology-change-from-alerts-access/m-p/5216379#M277030</guid>
      <dc:creator>shambhu.kumar</dc:creator>
      <dc:date>2024-10-28T18:56:25Z</dc:date>
    </item>
  </channel>
</rss>

