Setup guide

Migrating a Stream Server

ISIS Connections

The Interplay Stream Server has been qualified with one network connection and with two

network connections. Connections to the ISIS network should be through PRO/1000 PT port

2, port 4, or both.

There is no performance benefit to dual-connecting the Interplay Stream Server to an ISIS

network, since there is enough bandwidth to support 100 simultaneous clients. If a second

network connection is required to segment your Stream Server client for security purposes,

then it should be connected to the outgoing streaming VLAN. If you use more than one

network connection, you must ensure that DNS assigns the appropriate IP address to the

Stream Server clients and Interplay Engine.

MediaNetwork Connection

For connection to Avid Unity MediaNetwork, insert the qualified Fibre Channel card in

either the top or bottom PCIe slot.

Partitions on the Stream Server

The AS3000 Interplay Stream Server ships with two 1 TB (930 GB) drives that are mirrored

by the embedded Intel RAID controller. The RAID1 array contains the following partitions:

• An unmapped 10GB recovery partition

• C:\ with 80 GB of storage

• D:\ with the remaining 840 GB of storage

You can add an optional expansion kit that adds 4 TB of unmirrored storage. For additional

information, see the Avid Interplay Stream Server AS3000 Expansion Kit Upgrade Readme

on the Knowledge Base.

Port Usage for the Interplay Stream Server

To enable streaming from the Interplay Stream Server to Interplay Access clients, the

network must allow UDP and TCP traffic on the following ports:

• Direct client/server communications: 554, 7070 TCP

• UDP streaming: 6970 - 6999 UDP

• Interplay Engine communication: 80 TCP

If UDP packets are lost on the way from the server to the client there is no direct feedback.

The Stream Server does not get any feedback that the packets were lost, and the Access client

must wait until a timeout occurs.