Loading...
Loading...
This is a documentation defect. The Accelerated Security Path (ASP) drop captures with the reason dispatch-queue-limit do show captures packets, despite the fix of the defect CSCvx54235 "ASP capture dispatch-queue-limit shows no packets". FPR1140# show asp drop Frame drop: Dispatch queue tail drops (dispatch-queue-limit) 30274952 Last clearing: 15:49:33 UTC Jan 1 2026 by enable_15 Flow drop: Last clearing: 15:49:33 UTC Jan 1 2026 by enable_15 FPR1140# show asp drop Frame drop: Dispatch queue tail drops (dispatch-queue-limit) 30946186 Last clearing: 15:49:33 UTC Jan 1 2026 by enable_15 Flow drop: Last clearing: 15:49:33 UTC Jan 1 2026 by enable_15 FPR1140# show capture asp capture asp type asp-drop dispatch-queue-limit [Capturing - 0 bytes]
Packets are dropped with the reason dispatch-queue-limit drop reason in ASP and ASP drop captures with the same reason are configured.
If you want to capture packets where the accelerated security path (ASP) drop reason is dispatch-queue-limit, you need to enable debug to delay the packet drops. Otherwise, the packets have been dropped and they cannot be captured. If you have used show asp drop command and see that dispatch queue tail drops (dispatch-queue-limit) are increasing, enable debug on asp 38 before performing the capture. Do the following: Enable delayed drop for 20 packets. You can specify 0-100. When the delayed drop count hits zero, the delayed drop behavior stops automatically. You can see how many drops are still available using debug menu asp 38 with no number. Example usage: > debug menu asp 38 20 > capture drop type asp-drop dispatch-queue-limit (Start the capture) (Generate the traffic that has been causing the drops, then view the capture.) > show capture drop
None.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.