Cisco Cisco Virtual Managed Services 1.02 Troubleshooting Guide

6. Elastic Services Controller (ESC)

166

6.5 Logs

This  section  covers  logs  available  on  ESC  for  monitoring  its  functionality,  communication,  debugging  and
real-time troubleshooting.

ESC has a built-in log collection script 

/cisco/esc-init/collect_esc_log.sh

. The ESC log collector utility

will collect all log files and create a tarball of ESC logs that can be sent to Cisco TAC for assistance. Here is an
example of the command being run. Note that at the end, it prints out where the log file is stored in the 

/tmp

directory and that it should be removed to clean up disk space. Important log files used for troubleshooting
are listed below.

 [admin@esc-2 esc-init]$ /cisco/esc-init/collect_esc_log.sh

 Copying files to temporary folder: /tmp/esc_log-2015-12-08_19.57.46_UTC

 Creating log tarball /tmp/esc_log-2015-12-08_19.57.46_UTC.tar.bz2
 manager.2015-12-04.log
 rules_mona.log
 debug_yangesc.log
 <<< ABBREVIATED OUTPUT >>>
 netconf.log
 mona.2015-11-21.0.log
 catalina.out
 mona.2015-11-26.0.log
 tar: Removing leading `/' from member names
 /media/cdrom/openstack/2012-08-10/meta_data.json
 /media/cdrom/openstack/2013-04-04/meta_data.json
 /media/cdrom/openstack/2013-10-17/meta_data.json
 /media/cdrom/openstack/2013-10-17/vendor_data.json
 /media/cdrom/openstack/latest/meta_data.json
 /media/cdrom/openstack/latest/vendor_data.json
 /media/cdrom/openstack/content/0000
 /media/cdrom/openstack/content/0001
 /media/cdrom/openstack/content/0002

 

Tarball created:

   /tmp/esc_log-2015-12-08_19.57.46_UTC.tar.bz2
 Suggestions:

1. Transfer the tarball file from the esc vm to your storage location.
2. Remove the tarball from the esc vm disk.
3. List contents of tarball:

 tar jtvf esc_log-2015-12-08_19.57.46_UTC.tar.bz2