12-21-2009 09:27 AM - edited 03-14-2019 05:01 AM
Hello,
Partner is asking if we have best practice guidelines/documentation for setting Trace Log file sizes on ICM 7.2.X
thanks!
12-22-2009 05:10 AM
This is an oldie, but a goodie. http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_tech_note09186a00800b6a82.shtml Also, if you open a TAC case the TAC will provide you with recommended levels depending on your issue.
david
12-23-2009 12:52 PM
Actually we did open a TAC. Cisco was not able to make a recommendation because the issue is intermittent and we cannot leave tracing on indefinitely. Because of this they instead recommended installing a packet sniffer. However our network support team came back with a similar response - cannot leave packet sniffing turned on indefinitely.
This is a difficult situation in which we cannot reproduce the issue, we don't know when it will happen again. And we cannot take any proactive action to ensure that we capture the logs on the next occurrence.
So, has anyone else been through something like this?
Thanks!
Joe
12-24-2009 04:27 AM
For a lot of issues I've found that the packet capture is the best way to go. Assuming you don't have a "proper" sniffer, you can always put an old PC with a big harddrive and have it sniff only the IP range you need, this should easily give you a few weeks of capture. The other option is to spend a day or two trying to recreate the issue, it might take a few hours, but at the end if mithgt be worth spending the time.
david
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: