<?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 Unknown Protocol Drop observed on router interfaces in Switching</title>
    <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564393#M421107</link>
    <description>&lt;P&gt;Dear Friends,&lt;/P&gt;&lt;P&gt;Couple of months ago we have upgraded our network infrastructure, before the activity we had only one core router both primary and secondary WAN links were terminated on the same router. Now we have two core routers primary WAN link is terminated on primary router (Cisco 2911) and secondary link is on secondary router (Cisco 2811). Both core routers are connected in core switches (Cisco 3560). The juniper firewalls are also connected in the core switches which is gateway for our LAN. I have attached the logical core network design for reference.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We created BVI interfaces on both routers and bridge two physical interfaces in it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Primary router = int BVI1 (fa0/0/0 &amp;amp; Gi0/1) IP addresses 66.77.88.13 &amp;amp; 1.1.1.3 sec&lt;/P&gt;&lt;P&gt;Secondary router = int BVI1 (fa0/0 &amp;amp; fa0/1) IP addresses 66.77.88.11 &amp;amp; 1.1.1.4 sec&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To control the redundancy we have configured HSRP on both BVI interfaces,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HSRP VIP: 66.77.88.9 &amp;amp; 1.1.1.1 sec&lt;/P&gt;&lt;P&gt;Firewall is forwarding internet and data traffic to HSRP VIPs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have also configured EIGRP to get the secondary WAN link routes on primary router, in case of primary link down the primary router will forward the traffic to secondary router. The EIGRP neighbouship is also build on BVI interfaces. I have also BGP neighbourship with my Service Provider for Internet and Data MPLS connectivity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above scenario was working fine but a week ago the whole WAN connectivity went down and there was no failover to secondary router. I was unable to access the routers from the LAN. When I checked the routers through console the IP routing was disabled and all routing protocols and static routes were vanished from both routers. No log found for the incident. I reconfigured the both routers, connectivity went up for some hours and went down again, the situation of both routers was same. I faced this issue for whole week.&lt;/P&gt;&lt;P&gt;When I dig out the issue I observed that there were unkown protocol drops on both router interfaces connected to core switches. I am running STP on switched network including core switches and &lt;!--MEDIA-WRAPPER-START-1--&gt;no DTP or LLDP is enabled, CDP is also enabled on all cisco devices. I am unable to understand which type of traffic from the switches is causing for "Unknown Protocol Drops", please also tell me that is this issue can be cause for the incident stated above?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;!--MEDIA-WRAPPER-START-2--&gt;&lt;IMG alt="Logical Core Network Design" class="image-style-none media-element file-default" data-file_info="%7B%22fid%22:%221088736%22,%22view_mode%22:%22default%22,%22fields%22:%7B%22format%22:%22default%22,%22field_file_image_alt_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22Logical%20Core%20Network%20Design%22,%22field_file_image_title_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22Logical%20Core%20Network%20Design%22,%22field_media_description%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22Logical%20Core%20Network%20Design%22%7D,%22type%22:%22media%22%7D" src="https://community.cisco.com/legacyfs/online/media/new_network_diagram_logicalcisco.jpg" title="Logical Core Network Design" typeof="foaf:Image" /&gt;&lt;!--MEDIA-WRAPPER-END-2--&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Mar 2019 06:08:13 GMT</pubDate>
    <dc:creator>shuaib.khalid</dc:creator>
    <dc:date>2019-03-08T06:08:13Z</dc:date>
    <item>
      <title>Unknown Protocol Drop observed on router interfaces</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564393#M421107</link>
      <description>&lt;P&gt;Dear Friends,&lt;/P&gt;&lt;P&gt;Couple of months ago we have upgraded our network infrastructure, before the activity we had only one core router both primary and secondary WAN links were terminated on the same router. Now we have two core routers primary WAN link is terminated on primary router (Cisco 2911) and secondary link is on secondary router (Cisco 2811). Both core routers are connected in core switches (Cisco 3560). The juniper firewalls are also connected in the core switches which is gateway for our LAN. I have attached the logical core network design for reference.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We created BVI interfaces on both routers and bridge two physical interfaces in it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Primary router = int BVI1 (fa0/0/0 &amp;amp; Gi0/1) IP addresses 66.77.88.13 &amp;amp; 1.1.1.3 sec&lt;/P&gt;&lt;P&gt;Secondary router = int BVI1 (fa0/0 &amp;amp; fa0/1) IP addresses 66.77.88.11 &amp;amp; 1.1.1.4 sec&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To control the redundancy we have configured HSRP on both BVI interfaces,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HSRP VIP: 66.77.88.9 &amp;amp; 1.1.1.1 sec&lt;/P&gt;&lt;P&gt;Firewall is forwarding internet and data traffic to HSRP VIPs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have also configured EIGRP to get the secondary WAN link routes on primary router, in case of primary link down the primary router will forward the traffic to secondary router. The EIGRP neighbouship is also build on BVI interfaces. I have also BGP neighbourship with my Service Provider for Internet and Data MPLS connectivity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above scenario was working fine but a week ago the whole WAN connectivity went down and there was no failover to secondary router. I was unable to access the routers from the LAN. When I checked the routers through console the IP routing was disabled and all routing protocols and static routes were vanished from both routers. No log found for the incident. I reconfigured the both routers, connectivity went up for some hours and went down again, the situation of both routers was same. I faced this issue for whole week.&lt;/P&gt;&lt;P&gt;When I dig out the issue I observed that there were unkown protocol drops on both router interfaces connected to core switches. I am running STP on switched network including core switches and &lt;!--MEDIA-WRAPPER-START-1--&gt;no DTP or LLDP is enabled, CDP is also enabled on all cisco devices. I am unable to understand which type of traffic from the switches is causing for "Unknown Protocol Drops", please also tell me that is this issue can be cause for the incident stated above?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;!--MEDIA-WRAPPER-START-2--&gt;&lt;IMG alt="Logical Core Network Design" class="image-style-none media-element file-default" data-file_info="%7B%22fid%22:%221088736%22,%22view_mode%22:%22default%22,%22fields%22:%7B%22format%22:%22default%22,%22field_file_image_alt_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22Logical%20Core%20Network%20Design%22,%22field_file_image_title_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22Logical%20Core%20Network%20Design%22,%22field_media_description%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22Logical%20Core%20Network%20Design%22%7D,%22type%22:%22media%22%7D" src="https://community.cisco.com/legacyfs/online/media/new_network_diagram_logicalcisco.jpg" title="Logical Core Network Design" typeof="foaf:Image" /&gt;&lt;!--MEDIA-WRAPPER-END-2--&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 06:08:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564393#M421107</guid>
      <dc:creator>shuaib.khalid</dc:creator>
      <dc:date>2019-03-08T06:08:13Z</dc:date>
    </item>
    <item>
      <title>Hi,On your 3560 interfaces</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564394#M421108</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;On your 3560 interfaces tat face the routers can you check that DTP is definately off&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;interface gig 0/5&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;Routers will not understand DTP packets and show them as unknown protocol&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;Regards&lt;BR /&gt;Alex&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jan 2015 16:25:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564394#M421108</guid>
      <dc:creator>acampbell</dc:creator>
      <dc:date>2015-01-11T16:25:22Z</dc:date>
    </item>
    <item>
      <title>Alex has suggested checking</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564395#M421109</link>
      <description>&lt;P&gt;Alex has suggested checking on one of the common causes of unknown protocol drops which is DTP. But there are other kinds of traffic from a switched environment which might cause unknown protocol drops. It might be helpful if the original poster would share with us the output from the core switch of the commands show interface gi0/5 and show interface switchport gi0/5.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the unknown protocol drops are an interesting problem, the real problem here is what is causing the router to change its configuration and to disable ip routing. I find it difficult to see how an unknown protocol drop could have that effect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I correct in understanding that the router continues to run when this problem happens (there is not a reboot or reload)? If so then perhaps one step that I would suggest would be to enable logging buffer debug with a fairly large logging buffer. Then when the problem happens again log into the console and do a show log to get what is in the logging buffer. Hopefully there will be sign of some event at the time that the problem begins.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jan 2015 21:00:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564395#M421109</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2015-01-11T21:00:06Z</dc:date>
    </item>
    <item>
      <title>Hi Bros,Thanks for your</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564396#M421110</link>
      <description>&lt;P&gt;Hi Bros,&lt;/P&gt;&lt;P&gt;Thanks for your responses,&lt;/P&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Below are the required configs. DTP status on both switches is also attached (data &amp;amp; time was not set on switches which i have set now)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Primary router&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/1&lt;BR /&gt;description *** CONNECTED WITH PRIMARY SWITCH ****&lt;BR /&gt;no ip address&lt;BR /&gt;ip flow ingress&lt;BR /&gt;ip flow egress&lt;BR /&gt;ip virtual-reassembly in&lt;BR /&gt;duplex auto&lt;BR /&gt;speed auto&lt;BR /&gt;bridge-group 1&lt;/P&gt;&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Secondary Router:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;interface FastEthernet0/1&lt;BR /&gt;description *** CONNECTED WITH BACKUP SWITCH ***&lt;BR /&gt;no ip address&lt;BR /&gt;ip flow ingress&lt;BR /&gt;ip flow egress&lt;BR /&gt;ip virtual-reassembly&lt;BR /&gt;duplex auto&lt;BR /&gt;speed auto&lt;BR /&gt;bridge-group 1&lt;/P&gt;&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Core Switch1&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/5&lt;BR /&gt;description *****PRI-ROUTER*****&lt;BR /&gt;switchport access vlan 30&lt;BR /&gt;switchport trunk encapsulation dot1q&lt;BR /&gt;switchport trunk allowed vlan 30&lt;BR /&gt;switchport mode access&lt;/P&gt;&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Core Switch2&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/5&lt;BR /&gt;description ****SEC-ROUTER****&lt;BR /&gt;switchport access vlan 30&lt;BR /&gt;switchport trunk encapsulation dot1q&lt;BR /&gt;switchport trunk allowed vlan 30&lt;BR /&gt;switchport mode access&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;!--MEDIA-WRAPPER-START-3--&gt;&lt;IMG alt="DTP Status on Pri Switch" class="image-style-none media-element file-default" data-file_info="%7B%22fid%22:%221089816%22,%22view_mode%22:%22default%22,%22fields%22:%7B%22format%22:%22default%22,%22field_file_image_alt_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22DTP%20Status%20on%20Pri%20Switch%22,%22field_file_image_title_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22DTP%20Status%20on%20Pri%20Switch%22,%22field_media_description%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22DTP%20Status%20on%20Pri%20Switch%22%7D,%22type%22:%22media%22%7D" src="https://community.cisco.com/legacyfs/online/media/dtp_pri.jpg" title="DTP Status on Pri Switch" typeof="foaf:Image" /&gt;&lt;!--MEDIA-WRAPPER-END-3--&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;!--MEDIA-WRAPPER-START-3--&gt;&lt;IMG alt="DTP Status on Sec Switch" class="image-style-none media-element file-default" data-file_info="%7B%22fid%22:%221089821%22,%22view_mode%22:%22default%22,%22fields%22:%7B%22format%22:%22default%22,%22field_file_image_alt_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22DTP%20Status%20on%20Sec%20Switch%22,%22field_file_image_title_text%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22DTP%20Status%20on%20Sec%20Switch%22,%22field_media_description%5Bund%5D%5B0%5D%5Bvalue%5D%22:%22DTP%20Status%20on%20Sec%20Switch%22%7D,%22type%22:%22media%22%7D" src="https://community.cisco.com/legacyfs/online/media/dtp_sec.jpg" title="DTP Status on Sec Switch" typeof="foaf:Image" /&gt;&lt;!--MEDIA-WRAPPER-END-3--&gt;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 12 Jan 2015 05:24:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564396#M421110</guid>
      <dc:creator>shuaib.khalid</dc:creator>
      <dc:date>2015-01-12T05:24:33Z</dc:date>
    </item>
    <item>
      <title>Hi,Why have you configured</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564397#M421111</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Why have you configured the switch ports to be both access &amp;amp; trunk ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If the routers are purely just end devices in vlan 30 then reconfigure&lt;BR /&gt;your switch ports :-&lt;/P&gt;&lt;P&gt;int gig 0/5&lt;BR /&gt;shut&lt;BR /&gt;description *****PRI-ROUTER*****&lt;BR /&gt;no switchport trunk encapsulation dot1q&lt;BR /&gt;no switchport trunk allowed vlan 30&lt;BR /&gt;switchport mode access&lt;BR /&gt;switchport access vlan 30&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;no shut&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;Regards&lt;BR /&gt;Alex&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 10:09:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564397#M421111</guid>
      <dc:creator>acampbell</dc:creator>
      <dc:date>2015-01-12T10:09:48Z</dc:date>
    </item>
    <item>
      <title>Hi Alex, Thank you for</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564398#M421112</link>
      <description>&lt;P&gt;Hi Alex,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for guidance, I have to take some downtime for this configuration change because this port contains traffic of all switched network towards primary router, i will let you know after getting it done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Shuaib&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 13:14:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564398#M421112</guid>
      <dc:creator>shuaib.khalid</dc:creator>
      <dc:date>2015-01-12T13:14:20Z</dc:date>
    </item>
    <item>
      <title>Shuaib In the original post</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564399#M421113</link>
      <description>&lt;P&gt;Shuaib&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the original post you tell us that " the IP routing was disabled and all routing protocols and static routes were vanished from both routers." I would like clarification on a couple of points.&lt;/P&gt;&lt;P&gt;- was this the condition on both routers, that IP routing was disabled and all routing protocols and routes were removed?&lt;/P&gt;&lt;P&gt;- has this happened more than once?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2015 18:54:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564399#M421113</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2015-01-12T18:54:41Z</dc:date>
    </item>
    <item>
      <title>Hi Rick, Yes I face same</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564400#M421114</link>
      <description>&lt;P&gt;Hi Rick,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes I face same issue on both routers for multiple time, at that time i was unable to ping my routers from LAN until i reload them. I have checked the CPU usage which was normal and also checked the hardware health of both routers with Cisco authorized vendor and they also reported that they are fine.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jan 2015 12:13:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564400#M421114</guid>
      <dc:creator>shuaib.khalid</dc:creator>
      <dc:date>2015-01-13T12:13:00Z</dc:date>
    </item>
    <item>
      <title>It is interesting that it</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564401#M421115</link>
      <description>&lt;P&gt;It is interesting that it happens on both routers and that it has happened multiple times. How often does this happen (how frequently)? I will repeat my suggestion about setting up logging buffered with a good sized buffer and then monitoring what is in the logs as a way to identify what is going on.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jan 2015 19:15:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564401#M421115</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2015-01-13T19:15:17Z</dc:date>
    </item>
    <item>
      <title>Hi Shuaib,Do you have snmp</title>
      <link>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564402#M421116</link>
      <description>&lt;P&gt;Hi Shuaib,&lt;/P&gt;&lt;P&gt;Do you have snmp-server commands enabled on your WAN routers?&lt;/P&gt;&lt;P&gt;snmp-server community &amp;lt;community name&amp;gt; RW&lt;/P&gt;&lt;P&gt;With the above command in place without any ACL, any one from outside can disable the "ip routing" on your device.&lt;/P&gt;&lt;P&gt;in ideal scenario you must see a log generated whenever "ip routing" is disabled. But you may not be able to see the logs because of below bug.&lt;/P&gt;&lt;P&gt;https://tools.cisco.com/bugsearch/bug/CSCup37781&lt;/P&gt;&lt;P&gt;You may need to change the snmp command as per below&lt;/P&gt;&lt;P&gt;snmp-server community &amp;lt;community name&amp;gt; RO&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;-Amit&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2015 05:57:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/unknown-protocol-drop-observed-on-router-interfaces/m-p/2564402#M421116</guid>
      <dc:creator>Amit Goyal</dc:creator>
      <dc:date>2015-01-14T05:57:26Z</dc:date>
    </item>
  </channel>
</rss>

