Comment 7 for bug 1800207

Hi Ritam,

I understand. When this issue occurs, please collect the following logs:

Controller Logs:
We will need the config-api.log. You would rather collect all the logs in /var/log/contrail on all the controller nodes, that's easier.

Analytics Logs:
1. contrail-logs --object-type config --last 1h ===> The last argument can be changed based on when the issue occurred.
2. contrail-logs --object-type config-user --last 1h ===> The last argument can be changed based on when the issue occurred.
More info on analytic logs can be found at: https://github.com/Juniper/contrail-controller/wiki/Contrail-utility-scripts-for-getting-logs,-stats-and-flows-from-analytics

Config DB dump:
From any one of the config_api docker, you will need to collect the Config DB dump as:
1. cd to /usr/lib/python2.7/dist-packages/cfgm_common(or /usr/lib/python2.7/site-packages/cfgm_common depending on the underlying OS).
2. python db_json_exim.py --export-to db-dump.json

More info about this is at:
https://www.juniper.net/documentation/en_US/contrail5.0/topics/concept/backup-using-json-40.html

The logs i've requested here are not limited to this issue actually. In general, for any config related issue, we will generally require these logs.

-Sathish