<?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 Enable SNMP to send interface blocked due to network loop in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791505#M938149</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for you explanation, this is very clear now,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will simulate this in lab, thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Aug 2011 06:08:30 GMT</pubDate>
    <dc:creator>holzhirt1</dc:creator>
    <dc:date>2011-08-24T06:08:30Z</dc:date>
    <item>
      <title>Enable SNMP to send interface blocked due to network loop</title>
      <link>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791503#M938147</link>
      <description>&lt;P&gt;Dear community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We had a customer who created a loop on his access layer and STP blocked some interfaces in order to protect the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So far normal behavior &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;, however we would like to receive from the device when such events happen, typically when an interface is set onto err-disable or shut down (I guess it is more err-disable).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We noticed that somehow the concerned interface was sometimes staying down without checking back and maybe change its status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried some commands like :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency&lt;/P&gt;&lt;P&gt;snmp-server enable traps port-security (This is probably more for MAC quantity excess over the interface)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found also a nice MIB called Cisco-Err-Disable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I have the feeling I miss something on the device side,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help to put this in place would be greatly appreciated,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 12:26:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791503#M938147</guid>
      <dc:creator>holzhirt1</dc:creator>
      <dc:date>2020-02-21T12:26:24Z</dc:date>
    </item>
    <item>
      <title>Enable SNMP to send interface blocked due to network loop</title>
      <link>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791504#M938148</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;STP will not put the port into err-disable mode.&amp;nbsp;&amp;nbsp; The CISCO-ERR-DISABLE mib will report when the port is placed into a&amp;nbsp; err-disable state from one of these events published in the MIB:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CErrDisableFeatureID ::= TEXTUAL-CONVENTION&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; STATUS&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; current&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DESCRIPTION&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "An integer-value assigned to various features/events&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; that can error disable a system entity&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; udld: Unidirectional Link Detection&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; bpduGuard: Spanning Tree BPDU Guard feature that prevents&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; processing BPDU packets on an access interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; channelMisconfig: General Link Aggregation mis-configuration&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pagpFlap: Cisco's PAGP Link Aggregation protocol errors&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dtpFlap: Dynamic Trunking Protocol errors&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; linkFlap: Link State flapping&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; l2ptGuard: L2 Protocol Tunnel errors&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dot1xSecurityViolation: 802.1x authentication violations&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; portSecurity: Port Security violations&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; gbicInvalid: Invalid GBIC errors (examples include&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unsupported GBIC being inserted)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dhcpRateLimit: DHCP snooping rate limit violation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unicastFlood: Unicast Flooding threshold violations&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vmps: VLAN Membership Policy Server feature related errors&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; stormControl: storm control (broadcast/multicast/unicast)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; threshold violations&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inlinePower: Errors in inline power&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; arpInspection: Errors detected by Dynamic Arp Inspection&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (DAI) feature&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; portLoopback: Interface Loopback Error&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; packetBuffer: Packet Buffer Error&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; macLimit: Errors detected by Mac Address Limit feature&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; linkMonitorFailure: Link Monitoring failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; oamRemoteFailure: Remote Failure detected by Ethernet OAM&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (Operations, Administration, and Maintenance) feature&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dot1adIncompEtype: 802.1ad Ether-type Incompatible errors&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dot1adIncompTunnel: 802.1ad Pdu Tunnel Incompatible errors&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; sfpConfigMismatch: Mismatch on SFP configuration&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; communityLimit: Vlan Community Limit violations&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; invalidPolicy: QoS Policy violation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; lsGroup: Errors detected by Link State Group Tracking feature&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ekey: Errors detected by Error Key Mechanism&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; portModeFailure: Port mode change failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pppoeIaRateLimit: Errors detected by PPPoE Intermediate Agent&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Rate Limit feature&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; oamRemoteCriticalEvent: Ethernet OAM Remote Critical Event&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; oamRemoteDyingGasp: Ethernet OAM Remote Dying Gasp Failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; oamRemoteLinkFault: Ethernet OAM Remote Link Fault Failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mvrp: Errors detected by Multiple VLAN Registration Protocol&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The switch will generate the traps with:&lt;/P&gt;&lt;P&gt;#snmp-server enable traps errdisable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Aug 2011 17:47:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791504#M938148</guid>
      <dc:creator>Dan Frey</dc:creator>
      <dc:date>2011-08-23T17:47:15Z</dc:date>
    </item>
    <item>
      <title>Enable SNMP to send interface blocked due to network loop</title>
      <link>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791505#M938149</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for you explanation, this is very clear now,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will simulate this in lab, thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2011 06:08:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enable-snmp-to-send-interface-blocked-due-to-network-loop/m-p/1791505#M938149</guid>
      <dc:creator>holzhirt1</dc:creator>
      <dc:date>2011-08-24T06:08:30Z</dc:date>
    </item>
  </channel>
</rss>

