Loading...
Loading...
An ASP drop capture output may display incorrect drop reason in the output of the "show capture" command. Examples: firepower# cap cap type asp-drop cluster-ccl-backup <=== firepower# show capture capture cap type asp-drop cluster-stub-to-full [Capturing - 0 bytes] <=== firepower# cap capasp type asp-drop fragment-reassembly-failed firepower# show capture capture capasp type asp-drop df-bit-set [Capturing - 0 bytes] <=== firepower# cap capasp type asp-drop unable-to-find-vpn-context <=== firepower# show capture capture capasp type asp-drop unable-to-find-owner [Capturing - 0 bytes] <===
On ASA/FTD configure one or more ASP drop captures with a drop reason.
None.
Due to this defect, the ASP drop captures cannot be deleted if the reason is specified. Example: firepower# show capture capture capasp type asp-drop unable-to-find-owner [Capturing - 0 bytes] firepower# no capture capasp type asp-drop unable-to-find-owner ERROR: Capture configured for a different drop-code. <=== The workaround is to skip the reason in the negation command: firepower# no capture capasp
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.