Specifications

4-118
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 4 Configuring the CDS
Server Level Configuration
Configuring the Route Table
The Route Table provides the ability to define multiple subnets on a server that apply equally to stream
and cache-fill interfaces. With multiple subnets you have the ability to group interfaces into separate
subnets. One of the uses for multiple subnets is to configure half of the interfaces on the server to connect
to one switch or router, and the other half of the interfaces to connect to a different switch or router for
redundancy. The Route Table page allows for multiple subnets for cache, stream, and stream/cache
interfaces.
The Route Table page has three different route types:
• CServer Source (written to the SubnetTable file)
• CServer Destination (written to the RoutingTable file)
• Stream Control (written to the Linux OS route table)
Each route type has a different function, and each route type is written to a different file on the CDS
server.
Note You cannot have intersecting subnets for any defined routes for CServer Source or CServer Destination.
Table 4-40 AF Class Drop Probability Configured on Each CDS Server
AF1x AF2x AF3x AF4x Data Types
AF11 AF21 AF31 AF41 The following data types are set to low drop probability:
• Lost packet recovery for committed rate traffic (Vault or Caching
Node or Streamer to Vault or Caching Node or Streamer)
• High-priority lost packet recovery for committed rate traffic
(Vault or Caching Node or Streamer to Vault or Caching Node or
Streamer)
• iGate and index file transmission (Vault or Caching Node to
Streamer)
• First part of mirror data going to a new Vault (Vault to Vault)
• Control traffic
AF12 AF22 AF32 AF42 Committed rate traffic (Vault or Caching Node or Streamer to Vault or
Caching Node or Streamer) is set for medium drop.
AF13 AF23 AF33 AF43 The following data types are set to high drop probability:
• Remote smoothing traffic (Vault to Vault) and prefetched traffic
(Vault to Caching Node to Streamer)
• Mirroring traffic for creating additional mirrored copies (Vault to
Vault)
• Repair traffic that is recovering striped data lost because of a drive
failure (Vault to Vault)
• Mirroring of live ingest traffic (Vault to Vault)
• Lost packet recovery of mirroring traffic (Vault to Vault)