Cisco Cisco TelePresence Video Communication Server Expressway 문제 해결 가이드
Crash logs
Every time there is an application fail an incident report is written to disk, into the /tandberg/crash/directory.
Incident reports are included in the snapshot archive.
The Cisco support engineers host an externally routable server, onto which the VCS/TelePresence
Conductor can be configured to post incident reports. If administrators are willing to configure the system to
post incident reports it will speed up notification of application failures.
Conductor can be configured to post incident reports. If administrators are willing to configure the system to
post incident reports it will speed up notification of application failures.
The automatic uploading of crash reports to the ACR (automated crash report) server is configured on the
Maintenance > Incident reporting > Configuration
page (in X7.0 / XC1.1 and later this is
Maintenance >
Diagnostics > Incident reporting > Configuration
).
n
The incident reports sending mode needs to be set to On (it is Off by default).
n
The incident reports URL needs to be set to https://cc-reports.cisco.com/submitapplicationerror/ (The
legacy URL https://vcser.tandberg.com/submitapplicationerror/ will also reach the incident reporting
server).
legacy URL https://vcser.tandberg.com/submitapplicationerror/ will also reach the incident reporting
server).
n
Following an ‘incident’ (crash) an incident report is posted to this URL using HTTPS (system source port
4000-4999).
4000-4999).
It might not be the whole application crashing; ACRs can also be generated by subcomponents in the
system.
system.
If crash reporting cannot be turned on for any reason, or the system does not have routable access to the
server, any ACRs generated can be separately copied off the system, and then attached to a support ticket.
The Cisco support engineers can then manually upload the ACRs to the reporting server for investigation. Be
aware that in most cases a system snapshot is also required to understand the origin of the issue.
server, any ACRs generated can be separately copied off the system, and then attached to a support ticket.
The Cisco support engineers can then manually upload the ACRs to the reporting server for investigation. Be
aware that in most cases a system snapshot is also required to understand the origin of the issue.
Incident reports can be viewed and copied off the system from the
Maintenance > Incident reporting >
View
page (in X7.0 / XC1.1 and later this is
Maintenance > Diagnostics > Incident reporting > View
).
Sensor logs
The appliance hardware includes a number of sensors, the values of which can be read by the Linux OS.
These can be retrieved by typing sensors at the command prompt. The output can then be attached to the
Support ticket.
These can be retrieved by typing sensors at the command prompt. The output can then be attached to the
Support ticket.
~ # sensors
acpitz-virtual-0
Adapter: Virtual device
it8712.7-isa-0290
Adapter: ISA adapter
VCore: +1.22 V (min = +0.83 V, max = +1.39 V)
DDR 1.8V: +1.78 V (min = +1.62 V, max = +1.98 V)
VCC 3.3V: +3.31 V (min = +3.14 V, max = +3.47 V)
VCC 5V: +5.00 V (min = +4.76 V, max = +5.24 V)
+12V: +12.22 V (min = +9.60 V, max = +14.40 V)
VCC 1.5V: +1.49 V (min = +1.42 V, max = +1.57 V)
VBat: +3.26 V (min = +2.99 V)
Fan 1: 9375 RPM (min = 7670 RPM, div = 8)
Fan 2: 9375 RPM (min = 7670 RPM, div = 8)
Fan 3: 10546 RPM (min = 7670 RPM, div = 8)
RMA Procedures for Cisco VCS and TelePresence Conductor Appliances Reference Guide (X8.2)
Page 10 of 19
Logs and evidence