This document shows the steps required to take Diagnostic logs from a VCS server and upload them to a TAC case.
When facing B2B call failure it is important to take the logs from the server which will be involved in the call flow. In newer versions of VCS this will also include a xstatus and xconfiguration from the server. Be aware that this document applies for systems from x8.2 and up, lower versions such x8.1 or x7.x do not include some of these features seen in the web interface that are found on this document.
1) Under Maintenance> Diagnostics> Diagnostic logging:
2) Then, the next step will be to enable the Debug level on the Network level. This is set to Info level by default, however in order to have more information within the log we need to change this to Debug. Be aware that once we swap to "debug" the system will generate an alarm which is expected and clear up once it is set back to Info.
Click on Advanced Network Log configuration:
3) Once you click on it check the network box and click on Set to debug:
4) Once the Network level is set to debug we need to go back to Maintenance> Diagnostics> Diagnostic logging> Take tcpdump while logging
and then Start new log:
5) Once the start new log has been enabled the call can be started so the issue will be recreated from beginning to end.
When the issue is completely recreated click on Stop log and then Download log:
6) Look for the file under Downloads in your PC and use this link to upload the files to the case: https://cway.cisco.com/csc in the field shown below add your Service Request number.
7) Drag and drop, and then choose Log/Trace File as category and then click on next:
Remember to add the IP addresses of the devices involved in the call flow such VCS Control, VCS Expressway, endpoints, etc.
... View more