Step 1: check configurations, Step 2: check connections and external equipment, Step 3: check system status messages – Grass Valley K2 Summit Client Service Manual Nov.23 2009 User Manual
Page 76
76
K2 Summit Production Client Service Manual
12 October 2009
Chapter 4 Troubleshooting problems
Step 1: Check configurations
Many times what appears to be a K2 Summit Client fault is actually an easy-to-fix
configuration problem. Check settings in Configuration Manager and verify that the
system is configured as you expect. Refer to the K2 AppCenter User Manual and the
K2 System Guide.
Step 2: Check connections and external equipment
Loose or improperly connected cables are the most likely source of problems for the
system. A quick check of all the cable connections can easily solve these problems.
Refer to the K2 System Guide for help with making connections. Refer to the
troubleshooting topic
“Checking external equipment” on page 79
if you suspect a
failure in a device connected to the K2 Summit Client.
Step 3: Check system status messages
While the K2 Summit Client is in operation, some problems are detected and reported
in system status messages. To view system status messages, in AppCenter select
Help
| System Status
. Also refer to
“Viewing AppCenter system status messages” on
.
When connecting to a K2 Summit Client from a control point PC using remote
AppCenter, if there is an AppCenter system startup error, the error is reported during
the connection attempt.
If the system status message indicates a problem, refer to the related troubleshooting
topic later in this chapter.
NOTE: Do not use the MegaRAID utility on a K2 Summit Client. This utility is for
use by qualified Grass Valley Service personnel only. When this utility is opened it
scans the SCSI bus and interferes with record and play operations.
Step 4: Identify problems using the startup
sequence
The startup sequence is your primary tool for identifying a K2 Summit Client fault.
As the different levels of the K2 Summit Client system become operational in the
startup process, the primary components of the system are checked. You can identify
most problems by evaluating the messages and other indicators that occur during the
startup sequence.
NOTE: This procedure assumes that the K2 Summit Client is not in Storage
Utility’s “offline” mode.
To identify problems using the startup sequence, do the following:
1. Connect mouse, keyboard, and monitor. You must observe the VGA screen and be
able to interact with the system via keyboard and mouse to fully identify problems.
2. Restart the K2 Summit Client. If you have problems, refer to