<?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: IHQ constant packets in incoming queue in Switching</title>
    <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5097063#M564209</link>
    <description>&lt;P&gt;BTW, what's the capacity license on this 4331?&lt;/P&gt;
&lt;P&gt;I'm wondering, as overrunning license capacity shapes, whether that might queue ingress traffic.&lt;/P&gt;</description>
    <pubDate>Thu, 09 May 2024 16:45:10 GMT</pubDate>
    <dc:creator>Joseph W. Doherty</dc:creator>
    <dc:date>2024-05-09T16:45:10Z</dc:date>
    <item>
      <title>IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093676#M564075</link>
      <description>&lt;P&gt;Good morning&lt;/P&gt;
&lt;P&gt;I am facing the following problem on a customer location with main and backup router.&amp;nbsp;cisco ISR4331/K9&lt;/P&gt;
&lt;P&gt;We see constant incoming IHQ packets on the WAN Interfaces on both routers. At the same time there is almost no traffic on the WAN Interface Gi0/0/2 on the standby router.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we lost TACACS connection to the main router and "fixed" it by increasing the hold-que in to 2000 pakets. I do not see any other irregularities like high cpu load or massive packet counts.&lt;/P&gt;
&lt;P&gt;has anyone encountered the same problem or can tell me in which direction I have to investigate.&lt;/P&gt;
&lt;P&gt;sh interface summary (see attached doc)&lt;/P&gt;
&lt;P&gt;thanks in advance&lt;/P&gt;
&lt;P&gt;Chris&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 07:37:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093676#M564075</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-08T07:37:37Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093899#M564097</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Check software version being used on the ISR and or use&lt;STRONG&gt; latest advisory&lt;/STRONG&gt; (if applicable) ; &lt;FONT color="#008000"&gt;&lt;U&gt;&lt;EM&gt;check if that can help ,&amp;nbsp;&lt;/EM&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 08:38:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093899#M564097</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-05-08T08:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093905#M564099</link>
      <description>&lt;P&gt;Hi marce1000&lt;/P&gt;
&lt;P&gt;we are currently using&amp;nbsp;isr4300-universalk9.03.16.03.S.155-3.S3-ext.SPA.bin&lt;/P&gt;
&lt;P&gt;I am not able to change iOS unless it has been evaluated from Service Development Engineering .&lt;/P&gt;
&lt;P&gt;Are you aware of any iOS Problems which are causing this behavior.&lt;/P&gt;
&lt;P&gt;thanks&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Chris&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 08:46:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093905#M564099</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-08T08:46:10Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093910#M564103</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Not exactly , but such issues should be evaluated against a (the) advisory release , if it is all possible. Note that on Cisco software downloads site , if the release is gold-starred it's considered to be safe to use (too) ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 08:57:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5093910#M564103</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-05-08T08:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094000#M564107</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;post the output of:&lt;/P&gt;
&lt;P&gt;show buffers&lt;/P&gt;
&lt;P&gt;show interfaces GigabitEthernet0/0/2&lt;/P&gt;
&lt;P&gt;PS: Use a .txt file to post the output, as not everybody has a paid Word subscription.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 10:20:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094000#M564107</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2024-05-08T10:20:03Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094076#M564113</link>
      <description>&lt;P&gt;Hello Georg&lt;/P&gt;
&lt;P&gt;Please find attached the requested outputs&lt;/P&gt;
&lt;P&gt;thanks Chris&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 11:33:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094076#M564113</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-08T11:33:03Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094242#M564117</link>
      <description>&lt;P&gt;Is the WAN connection Internet?&amp;nbsp; If so, running BGP?&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 14:01:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094242#M564117</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2024-05-08T14:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094246#M564118</link>
      <description>&lt;P&gt;VPN not Internet but we are using BGP&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 14:06:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094246#M564118</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-08T14:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094488#M564130</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/433486"&gt;@Chrizhitz&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;VPN not Internet but we are using BGP&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Ah, then likely not what I had in mind.&lt;/P&gt;
&lt;P&gt;IHQ, in my experience, is rare.&amp;nbsp; Assuming you're not dealing with some bug, it can be caused by a bunch of packets, that arrive quickly, which the device NIC is able to queue, but the device is "slow" emptying the ingress queue.&lt;/P&gt;
&lt;P&gt;Your router is just a 4331 supporting gig interfaces, and the 4331 is far, far from being a gig capable router.&lt;/P&gt;
&lt;P&gt;I notice in the second stat posting, g0/0/0 is also showing 124 packets in its ingress queue.&lt;/P&gt;
&lt;P&gt;So, it's very possible, some gig bursts are delayed processed by the CPU.&lt;/P&gt;
&lt;P&gt;Personally, I've seen this with Internet BGP route updates, that "flood" the receiving the device, but it's unable to keep up with the burst.&lt;/P&gt;
&lt;P&gt;Sometimes, mitigation is as simple as increasing ingress queue size to handle the burst, to avoid packet drops.&amp;nbsp; (Which if I'm reading your OP correctly, "fixed" the TACAS issue.)&lt;/P&gt;
&lt;P&gt;I'm surprised that you note CPU doesn't show high load.&amp;nbsp; For that, you mean you CPU history doesn't shown any 100% spikes?&amp;nbsp; I.e. it doesn't have to be a sustained overall high average load.&lt;/P&gt;
&lt;P&gt;Since you increased ingress queue depth, having any other issues?&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 17:15:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5094488#M564130</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2024-05-08T17:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5096514#M564189</link>
      <description>&lt;P&gt;Yes, very rare. I think I only saw it in combination with the 4331. Meanwhile the constant input increased to 412 packets.&lt;/P&gt;
&lt;P&gt;Main Router&lt;/P&gt;
&lt;P&gt;GigabitEthernet0/0/2 412 0 0 41029 1033000 879 21028000 1869 0&lt;/P&gt;
&lt;P&gt;Backup Router Gig0/0/0 now 138 Packets / Gig0/0/2 still 368&lt;/P&gt;
&lt;P&gt;GigabitEthernet0/0/0 138 0 0 0 6000 11 2000 4 0&amp;nbsp;&lt;/P&gt;
&lt;P&gt;GigabitEthernet0/0/2 368 0 0 0 0 1 5000 4 0&lt;/P&gt;
&lt;P&gt;Yes CPU history does not show any dramatic spikes the 72 hours average is somewhat around 10%&lt;/P&gt;
&lt;P&gt;To me it looks like some sort of loop. Could it be useful to configure site-of-origin?&lt;/P&gt;
&lt;P&gt;No further issues observed since I increased the ingress queue depth.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 15:30:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5096514#M564189</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-09T15:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5097063#M564209</link>
      <description>&lt;P&gt;BTW, what's the capacity license on this 4331?&lt;/P&gt;
&lt;P&gt;I'm wondering, as overrunning license capacity shapes, whether that might queue ingress traffic.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 16:45:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5097063#M564209</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2024-05-09T16:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5098915#M564249</link>
      <description>&lt;P&gt;Main Router#sh platform hardware throughput level &lt;BR /&gt;Load for five secs: 0%/0%; one minute: 1%; five minutes: 1%&lt;BR /&gt;Time source is NTP, 07:07:04.189 CEST Fri May 10 2024&lt;BR /&gt;The current throughput level is 300000 kb/s&lt;/P&gt;
&lt;P&gt;Two shaping policies of 212mbps and 21mbps (which of course is not optimal but should in my opinion not be the reason for this problem)&lt;/P&gt;
&lt;P&gt;Main Router#sh platform hardware throughput-license-enforcement &lt;BR /&gt;Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%&lt;BR /&gt;Time source is NTP, 07:07:52.124 CEST Fri May 10 2024&lt;BR /&gt;Throughput License Mode: Oversubscription-buffered&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 05:12:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5098915#M564249</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-10T05:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5100603#M564283</link>
      <description>&lt;P&gt;Again, don't know "where" capacity shaping is queued.&lt;/P&gt;
&lt;P&gt;Consider, two gig interfaces can submit 2 Gbps but you're limited to 300 Mbps throughput.&amp;nbsp; The 300 Mbps, depending on traffic "kind" and config, may require little CPU loading.&amp;nbsp; I.e. low CPU usage does not exclude this as a possible issue.&lt;/P&gt;
&lt;P&gt;Also consider, the time needed to handle 368 packets at "only" 300 Mbps.&amp;nbsp; If all were 1500 bytes, that would be 4,416,000 bits, and at 300 Mbps, it would take about 15 ms to process.&lt;/P&gt;
&lt;P&gt;What would be an interesting test, if possible, is run with a "boost" (evaluation) license, and see if traffic still is shown in ingress queues.&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 15:44:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5100603#M564283</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2024-05-10T15:44:52Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102024#M564338</link>
      <description>&lt;P&gt;on the standby Router we also do have a constant IHQ of 159 but traffic is only some 2000 bits/sec (RXBS and TXBS)&lt;/P&gt;
&lt;P&gt;no boost license available.&lt;/P&gt;
&lt;P&gt;another "fun fact" when I admin shut the gig0/0/0 (LAN) the IHQ remains 159 (clear counters done) Don't know if this is a feature or a bug.&lt;/P&gt;
&lt;P&gt;however I am going to reload the standby Router to see if this is going to change anything.&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 08:43:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102024#M564338</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-11T08:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102037#M564340</link>
      <description>&lt;P&gt;21 minutes after reload of Standby Router&lt;/P&gt;
&lt;P&gt;IHQ on both Gig Interfaces 0&lt;/P&gt;
&lt;P&gt;Main Router Gig 0/0/2 still IHQ 450 (no reload)&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 09:11:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102037#M564340</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-11T09:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102084#M564344</link>
      <description>&lt;P&gt;If the count remains the same and occasionally increases, remaining the same, basically behaving like a "high water mark", that may be a bug as I believe it's supposed to show the current ingress queue depth, not the highest seen to date.&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 09:48:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102084#M564344</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2024-05-11T09:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102464#M564362</link>
      <description>&lt;P&gt;after 5 hours 56 minutes no new IHQ packets.&lt;/P&gt;
&lt;P&gt;IHQ (if working normal) always shows the current situation on the ingress queue with every refresh.&lt;/P&gt;
&lt;P&gt;If there are 0 the IHQ shows 0 and so on.&lt;/P&gt;
&lt;P&gt;I agree it behaves like a bug but then how come we lost TACACS access when Ingress queue exceeded approx. 300 packets and we where able to fix it by increasing the hold-queue in?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 15:02:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102464#M564362</guid>
      <dc:creator>Chrizhitz</dc:creator>
      <dc:date>2024-05-11T15:02:11Z</dc:date>
    </item>
    <item>
      <title>Re: IHQ constant packets in incoming queue</title>
      <link>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102513#M564363</link>
      <description>&lt;P&gt;The possible bug would have been the IHQ never showing lower values than prior values.&amp;nbsp; If that's not happening, I misunderstood what you described as happening.&lt;/P&gt;
&lt;P&gt;As to having IHQ non-zero values. even if usages appears low, much can happen in milliseconds that won't be seen in longer term averages.&lt;/P&gt;
&lt;P&gt;Generically, if unfamiliar, look up "microburstimg".&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 16:14:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ihq-constant-packets-in-incoming-queue/m-p/5102513#M564363</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2024-05-11T16:14:21Z</dc:date>
    </item>
  </channel>
</rss>

