Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Maintenance
To view the information contained in a particular incident report, click on the report's Time. You will be
taken to the
taken to the
page, from where you can view the report on screen, or download it as an
XML file for forwarding manually to Cisco customer support.
Incident report details
The Incident detail page (
Maintenance > Incident reporting > View
, then click on a report's Time)
shows the information contained in a particular incident report.
This is the information that is sent to the external web service if you have enabled Incident reports
sending mode (via
sending mode (via
Maintenance > Incident reporting > Configuration
). It is also the same
information that is downloaded as a Base64-encoded XML file if you click Download incident report.
The information contained in the report is:
Field
Description
Time
The date and time when the incident occurred.
Version
The VCS software version running when the incident occurred.
Build
The internal build number of the VCS software version running when the incident
occurred.
occurred.
Name
The name of the software.
System
The configured system name.
Serial number
The hardware serial number.
Process ID
The process ID the VCS application had when the incident occurred.
Release
A true/false flag indicating if this is release build (rather than a development
build).
build).
User name
The name of the person that built this software. This is blank for release builds.
Stack
The trace of the thread of execution that caused the incident.
Debug
information
information
A full trace of the application call stack for all threads and the values of the
registers.
registers.
Warning: for each call stack, the Debug information includes the contents of variables which may
contain some sensitive information, for example alias values and IP addresses. If your deployment is
such that this information could contain information specific to a particular person, please read the
contain some sensitive information, for example alias values and IP addresses. If your deployment is
such that this information could contain information specific to a particular person, please read the
regarding privacy-protected personal data before you decide whether to enable automatic
incident reporting.
Checking the effect of a pattern
The Check pattern page (
Maintenance > Tools > Check pattern
) lets you test whether a pattern or
transform you intend to configure on the VCS will have the expected result.
Patterns can be used when configuring:
n
and
to specify aliases to be included in the lists
n
to specify aliases to be transformed before any searches take place
Cisco VCS Administrator Guide (X6.1)
Page 219 of 401