This article contains a list what to collect for Junos Content Encore
What information should I collect to assist in troubleshooting prior to opening a case?
The goal of this document is to reduce the time spent on initial data collection and reduce time to resolve by providing a comprehensive list of what to collect or gather to troubleshoot an issue.
Please collect the following for Junos Content Encore issues:
A. Tech Support Report
Ideally the best data to collect is the
Tech Support Report. It is available in the WEB UI under the System Config tab:
The Snapshots menu also on this screen contains any coredumps. If any are present, please download those as well.
Warning: The tech-support log can be very large, gigs of data. Use KB23337 - How to upload large files to a JTAC Case to upload the tech-support and any snapshots available. If it is not possible to collect and send the Tech Support Report in, then collect the following and attach it to your case:
mfc # show running-config
mfc # show accesslog default last 500
mfc # show cachelog last 500
mfc # show log
mfc # show counters
mfc # show service
B. Additional data to collect:
If the issue is with a specific Namespace, please collect the following. (example: namespace tproxy)
mfc # show namespace tproxy counters
login to the shell with "_shell"
[admin@mfc ~]# cat /var/log/nkn/access.log | grep trpoxy
[admin@mfc ~]# cat /var/log/nkn/cache.log | grep trpoxy
If the issue is with a particular source or client IP address and an origin server. Collect a packet capture as follows:
mfc (config) # tcpdump -nn -i eth0 -S -s 1024 host 10.10.10.10 or host 20.20.20.20 -w mfc.pcap
Run the problem traffic, then Ctrl-c to stop the capture.
You can then tftp, ftp, sftp or SCP the capture off the MFC to view in wireshark.
(config) # file tcpdump upload mfc.pcap tftp://30.30.30.30/mfc.pcap
Attach your data to the case or SFTP as per
KB23337 - How to upload large files to a JTAC Case for JTAC to reference.