Cisco Cisco Expressway Maintenance Manual
Note that:
n
Only one diagnostic log can be produced at a time; creating a new diagnostic log will replace any previously
produced log.
produced log.
n
The Expressway continually logs all system activity to a unified log file. The diagnostic logging facility
works by extracting a portion of this unified log. On busy systems the unified log file may become full over
time and will discard historic log data so that it can continue logging current activity. This means that all or
part of your diagnostic log could be overwritten. The system will warn you if you attempt to download a
partial diagnostic log file.
works by extracting a portion of this unified log. On busy systems the unified log file may become full over
time and will discard historic log data so that it can continue logging current activity. This means that all or
part of your diagnostic log could be overwritten. The system will warn you if you attempt to download a
partial diagnostic log file.
n
The diagnostic log will continue logging all system activity until it is stopped, including over multiple login
sessions and system restarts.
sessions and system restarts.
n
When starting a diagnostic log, the relevant system modules have their log levels automatically set to
"debug". You can ignore any "Verbose log levels configured" alarms; the log levels are reset to their original
values when you stop logging.
"debug". You can ignore any "Verbose log levels configured" alarms; the log levels are reset to their original
values when you stop logging.
n
Diagnostic logging can only be controlled through the web interface; there is no CLI option.
n
The tcpdump has a maximum file size limit of 50 MB.
Clustered systems
Diagnostic logging can also be used if your Expressway is a part of a cluster, however some activities only
apply to the "current" peer (the peer to which you are currently logged in to as an administrator):
apply to the "current" peer (the peer to which you are currently logged in to as an administrator):
n
The start and stop logging operations are applied to every peer in the cluster, regardless of the current peer.
n
The taking a tcpdump operation is applied to every peer in the cluster, regardless of the current peer.
n
Each cluster peer maintains its own unified log, and logs activity that occurs only on that peer.
n
Marker text is only applied to log of the current peer.
n
You can only download the diagnostic log from the current peer.
n
To add markers to other peers' logs, or to download diagnostic logs from other peers, you must log in as an
administrator to that other peer.
administrator to that other peer.
To collect comprehensive information for debugging purposes, we recommend that you extract the
diagnostic log for each peer in a cluster.
diagnostic log for each peer in a cluster.
Creating a system snapshot
The
System snapshot
page (
Maintenance > Diagnostics > System snapshot
) lets you create files that
can be used for diagnostic purposes. The files should be sent to your support representative at their request
to assist them in troubleshooting issues you may be experiencing.
to assist them in troubleshooting issues you may be experiencing.
You can create several types of snapshot file:
n
Status snapshot: contains the system's current configuration and status settings.
n
Logs snapshot: contains log file information (including the Event Log, Configuration Log and Network
Log).
Log).
n
Full snapshot: contains a complete download of all system information. The preparation of this snapshot
file may take several minutes to complete and may lead to a drop in system performance while the
snapshot is in progress.
file may take several minutes to complete and may lead to a drop in system performance while the
snapshot is in progress.
Cisco Expressway Administrator Guide (X8.2)
Page 222 of 378
Maintenance
Diagnostics tools