Specifications

5-43
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 5 System Monitoring
Recommended Monitoring Schedule
Step 3 Check the CServer interfaces to verify the status of the Ethernet adapters. Choose Monitor > Server
Level NIC Monitor, or log in to each server and use the following commands
a. Use the grep -i Link command to verify that all adapters should have a status of “link up,” except
those adapters that are not being used.
grep –i Link /proc/net/PRO_LAN_Adapters/*.info
b. Use the grep -i Speed command to verify that each adapter that has a “link up” status should have
a speed of 1000.
grep –i Speed /proc/net/PRO_LAN_Adapters/*.info
c. Use the grep -i State command to verify that all adapters should have an “up” state, except those
adapters that are not being used.
grep –i State /proc/net/PRO_LAN_Adapters/*.info
Step 4 Check the CServer streaming and cache-fill interfaces using the following command:
/home/stats/ifstats
Step 5 Check the database thread count using the following command:
netstat –an | grep 9999
Two connections for each Vault and Streamer should be listed with a status of “ESTABLISHED.
Step 6 Check the protocol timing logs for errors or problems. Also, look at the protocol timing logs for packet
retransmissions.
tail –f /arroyo/log/protocoltiming.log.{date} | grep retransmissions
Step 7 Look for warning messages.
grep –i warning /arroyo/log/protocoltiming.log.<date> | more
Note The “WARNING” messages can sometimes be misleading; for example, “datawait” and “slow
disk” messages occur normally and do not indicate a problem.
Step 8 The number of GOIDs for a particular content object must be the same on all servers (Vaults and
Streamers) that are supposed to have the content. The number of Vaults that must have the same number
of GOIDs for a particular content object is determined by the mirrored copy configuration (see the
“Configuring the Servers” section on page 4-112). The number of GOIDs is also dependent on the trick
speeds configured you configured (see the “Configuring Ingest Tuning” section on page 4-26). If the
GOID is different between a Vault and a Streamer, session setup is not created properly because of an
issue of “no content available.” This is because there is no content on the Vault that matches the GOID
of the Streamer has.
Monitoring Tasks for Vaults
In addition to the weekly monitoring tasks for both the Vaults and Streamers, the Vaults can also be
monitored in the following ways:
1. Check the available space on the Vault hard drives. Choose Monitor > Server Level > Disk
Monitor. The disk availability is shown as a percentage and as a number of gigabytes. Alternatively,
view the protocol timing logs by running the following command: