Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Maintenance
Cisco VCS Administrator Guide (X7.0)
Page 296 of 488
n
Only one diagnostic log can be produced at a time; creating a new diagnostic log will replace any
previously produced log.
previously produced log.
n
The VCS 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.
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.
login sessions and system restarts.
n
The various log level settings cannot be changed while a diagnostic log is in progress. The log levels
are reset to their original values when you stop the diagnostic log.
are reset to their original values when you stop the diagnostic log.
n
Diagnostic logging can only be controlled through the web interface; there is no CLI option.
Clustered VCS systems
Diagnostic logging can also be used if your VCS 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) :
to the "current" peer (the peer to which you are currently logged in to as an administrator) :
n
Each cluster peer maintains its own unified log, and logs activity that occurs only on that peer.
n
The start and stop logging operations are applied to every peer in the cluster, regardless of the current
peer.
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.
as an administrator to that other peer.
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.
request to assist them in troubleshooting issues you may be experiencing.
You can create 3 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.
snapshot file may take several minutes to complete and may lead to a drop in system performance
while the snapshot is in progress.
To create a system snapshot file:
1. Click one of the snapshot buttons to start the download of the snapshot file. Typically your support
representative will tell you which type of snapshot file is required.