12-16-2016 12:14 AM
Hi everybody,
I'm facing a problem now when my cisco ironport take too long to start to deliver message, like image below:
It take 15 minutes for queue for delivery (13:39) to start to delivery (13:52).
Every message are stuck like that.
The System CPU, RAM of Cisco ESA is normal
So where are further logs on IronPort so that i could find the solution
Solved! Go to Solution.
12-16-2016 10:43 AM
Hi,
The message tracking shows the email was processed without issues and the ESA could not create a delivery connection (DCID) with the destination server.
Below article describes some steps to troubleshoot delivery issues.
http://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118467-technote-esa-00.html
If the destination IP is the same on all these emails I would recommend setting up a packet capture for the IP from Help and Support -> Packet Capture to determine if this is a network related problem.
As this is an inbound email the destination server should be an internal exchange server IP and I would expect outbound emails to other destination IP's are working normally. It could very well be the internal exchange throttling connections from the ESA, do you see any errors on that server?
The packet capture would be the best method to begin troubleshooting.
Regards
Libin
12-16-2016 10:43 AM
Hi,
The message tracking shows the email was processed without issues and the ESA could not create a delivery connection (DCID) with the destination server.
Below article describes some steps to troubleshoot delivery issues.
http://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118467-technote-esa-00.html
If the destination IP is the same on all these emails I would recommend setting up a packet capture for the IP from Help and Support -> Packet Capture to determine if this is a network related problem.
As this is an inbound email the destination server should be an internal exchange server IP and I would expect outbound emails to other destination IP's are working normally. It could very well be the internal exchange throttling connections from the ESA, do you see any errors on that server?
The packet capture would be the best method to begin troubleshooting.
Regards
Libin
12-18-2016 11:25 PM
Hi Libin, Thank you for your reply and sorry for reply you lately.
I've found out that the Internal Exchange Server have lost connection to queury DNS so that the Anti-Spam Engine on Exchange Server takes so long time to process the Incoming Messages from IronPort.
Finally, everything is OK now.
Brs
12-19-2016 02:37 AM
Glad to hear that. Thank you for sharing what caused the issue.
- Libin
12-21-2016 12:43 AM
thanks you.
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