Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
170
D14049.08
November 2010
November 2010
Grey Headline (continued)
CISCO TELEPRESENCE
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Incident reporting
The incident reporting feature of the VCS automatically saves information about critical system
issues such as application failures. You can:
issues such as application failures. You can:
from the VCS web interface
to Cisco (usually at the request of Cisco customer
support)
•
configure the VCS to
to Cisco
The information contained in these reports can then be used by Cisco customer support to
diagnose the cause of the failures. All information gathered during this process will be held in
confidence and used by Cisco personnel for the sole purpose of issue diagnosis and problem
resolution.
This feature is only intended for use at the request of Cisco customer support in exceptional
situations, and is off by default.
diagnose the cause of the failures. All information gathered during this process will be held in
confidence and used by Cisco personnel for the sole purpose of issue diagnosis and problem
resolution.
This feature is only intended for use at the request of Cisco customer support in exceptional
situations, and is off by default.
Warning: privacy-protected personal data
!
IN NO EVENT SHOULD PRIVACY-PROTECTED PERSONAL DATA BE INCLUDED IN ANY
REPORTS TO CISCO. Privacy-Protected Personal Data means any information about persons
or entities that the Customer receives or derives in any manner from any source that
REPORTS TO CISCO. Privacy-Protected Personal Data means any information about persons
or entities that the Customer receives or derives in any manner from any source that
contains any personal information about prospective, former, and existing customers, employees or
any other person or entity. Privacy-Protected Personal Data includes, without limitation, names,
addresses, telephone numbers, electronic addresses, social security numbers, credit card
numbers, customer proprietary network information (as defined under 47 U.S.C. § 222 and its
implementing regulations), IP addresses or other handset identifiers, account information, credit
information, demographic information, and any other information that, either alone or in
combination with other data, could provide information specific to a particular person.
PLEASE BE SURE THAT PRIVACY-PROTECTED PERSONAL DATA IS NOT SENT TO CISCO WHEN THE
VCS IS CONFIGURED TO AUTOMATICALLY SEND REPORTS.
IF DISCLOSURE OF SUCH INFORMATION CANNOT BE PREVENTED, PLEASE DO NOT USE THE
AUTOMATIC CONFIGURATION FEATURE. Instead, copy the data from the Incident detail page
and paste it into a text file. You can then edit out any sensitive information before forwarding the
file on to Cisco customer support. See the section
any other person or entity. Privacy-Protected Personal Data includes, without limitation, names,
addresses, telephone numbers, electronic addresses, social security numbers, credit card
numbers, customer proprietary network information (as defined under 47 U.S.C. § 222 and its
implementing regulations), IP addresses or other handset identifiers, account information, credit
information, demographic information, and any other information that, either alone or in
combination with other data, could provide information specific to a particular person.
PLEASE BE SURE THAT PRIVACY-PROTECTED PERSONAL DATA IS NOT SENT TO CISCO WHEN THE
VCS IS CONFIGURED TO AUTOMATICALLY SEND REPORTS.
IF DISCLOSURE OF SUCH INFORMATION CANNOT BE PREVENTED, PLEASE DO NOT USE THE
AUTOMATIC CONFIGURATION FEATURE. Instead, copy the data from the Incident detail page
and paste it into a text file. You can then edit out any sensitive information before forwarding the
file on to Cisco customer support. See the section
for more
information.
Overview
The information contained in the report is:
Time
the date and time at which the incident occurred.
Version
the version of software running when the incident occurred.
Build
the internal build number for the software.
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).
development build).
User name
the name of the person that built this software. This is blank for release
builds.
builds.
Stack
the trace of the thread of execution that caused the incident.
Debug information
a full trace of the application call stack for all threads and the values of
the registers.
the registers.
!
For each call stack the Debug information will include 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
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 Warning: privacy-protected personal data section (left) before you decide
whether to enable automatic incident reporting.
If you choose not to enable automatic incident reporting, you can still manually send the reports to
Cisco customer support. See the
whether to enable automatic incident reporting.
If you choose not to enable automatic incident reporting, you can still manually send the reports to
Cisco customer support. See the
section for more information.
What information does the report contain?