10-12-2010 07:16 AM - edited 03-11-2019 11:53 AM
I'm hoping someone might be able to assist with this issue I am seeing. My 5505's "outside" interface drops about every 30 minutes and the log is registering a lot of "%ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =" very close to the time the interface goes down. Any ideas what could be causing this issue and how I should go about troubleshooting it?
I am running a 5505 (base license) with 8.3(2) and I was seeing the same issue with 8.3(1).
Thanks in advance for any help you can give!!!
Oct 12 2010 09:07:19: %ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:07:19: %ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:13:04: %ASA-4-711004: Task ran for 387 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:13:04: %ASA-4-711004: Task ran for 387 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:22:49: %ASA-4-411002: Line protocol on Interface Ethernet0/0, changed state to down
Oct 12 2010 09:22:49: %ASA-4-411002: Line protocol on Interface OUTSIDE, changed state to down
Oct 12 2010 09:22:49: %ASA-4-411002: Line protocol on Interface Ethernet0/0, changed state to down
Oct 12 2010 09:22:51: %ASA-4-411001: Line protocol on Interface OUTSIDE, changed state to up
Oct 12 2010 09:22:51: %ASA-4-411001: Line protocol on Interface Ethernet0/0, changed state to up
Oct 12 2010 09:22:51: %ASA-4-411001: Line protocol on Interface Ethernet0/0, changed state to up
Oct 12 2010 09:37:24: %ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:37:24: %ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:39:34: %ASA-4-711004: Task ran for 387 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:39:34: %ASA-4-711004: Task ran for 387 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:40:39: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:40:39: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:41:44: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:41:44: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:42:44: %ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:42:44: %ASA-4-711004: Task ran for 389 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:45:34: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:45:34: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:47:15: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack =
Oct 12 2010 09:47:15: %ASA-4-711004: Task ran for 388 msec, Process = Dispatch Unit, PC = 81bed79, Call stack = 0x081BED79 0x08062873
Oct 12 2010 09:53:27: %ASA-4-411002: Line protocol on Interface Ethernet0/0, changed state to down
Oct 12 2010 09:53:27: %ASA-4-411002: Line protocol on Interface OUTSIDE, changed state to down
Oct 12 2010 09:53:27: %ASA-4-411002: Line protocol on Interface Ethernet0/0, changed state to down
Oct 12 2010 09:53:29: %ASA-4-411001: Line protocol on Interface OUTSIDE, changed state to up
Oct 12 2010 09:53:29: %ASA-4-411001: Line protocol on Interface Ethernet0/0, changed state to up
Oct 12 2010 09:53:29: %ASA-4-411001: Line protocol on Interface Ethernet0/0, changed state to up
10-12-2010 07:36 AM
Dispatch Unit is a packet processing process. If you have interface errors I would suggest you investigating if your ASA is oversubscribed and potential solutions for that following doc http://supportforums.cisco.com/docs/DOC-12439
If you are not oversubscribed you would need to see why this process is hogging the CPU and TAC could be a good resource for that.
I hope it helps.
PK
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide