Cisco Cisco Expressway
Appendix 1: Troubleshooting
General troubleshooting techniques
Checking alarms and status
When troubleshooting any issue, we recommend that you first check if any alarms have been raised (
Status
> Alarms
). If alarms exist, follow the instructions provided in the Action column. You should check the
alarms on both Expressway-C and Expressway-E.
Next, go to
Status > Unified Communications
to see a range of status summary and configuration
information. You should check this status page on both Expressway-C and Expressway-E.
If any required configuration is missing or invalid an error message is shown and a link to the relevant
configuration page is provided.
configuration page is provided.
You may see invalid services or errors if you have changed any of the following items on Expressway:
n
server or CA certificates
n
DNS configuration
n
domain configuration
In these cases, a system restart is required to ensure that those configuration changes take effect.
Checking and taking diagnostic logs
Jabber for Windows
The Jabber for Windows log file is saved as csf-unified.log under
C:\Users\<UserID>\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs.
C:\Users\<UserID>\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs.
The configuration files are located under C:\Users\<UserID>\AppData\Roaming\Cisco\Unified
Communications\Jabber\CSF\Config.
Communications\Jabber\CSF\Config.
Performing Expressway diagnostic logging
The diagnostic logging tool in Expressway can be used to assist in troubleshooting system issues. It allows
you to generate a diagnostic log of system activity over a period of time, and then to download the log.
you to generate a diagnostic log of system activity over a period of time, and then to download the log.
Before taking a diagnostic log, you must configure the log level of the relevant logging modules:
1. Go to
Maintenance > Diagnostics > Advanced > Support Log configuration
.
2. Select the following logs:
l
developer.edgeconfigprovisioning
l
developer.trafficserver
l
developer.xcp
3. Click Set to debug.
You can now start the diagnostic log capture:
1. Go to
Maintenance > Diagnostics > Diagnostic logging
.
2. Optionally, select Take tcpdump while logging.
3. Click Start new log.
Unified Communications Mobile and Remote Access via Cisco Expressway Deployment Guide (X8.5)
Page 43 of 50
Appendix 1: Troubleshooting