Grass Valley NewsShare v.5.5 - Manual (Page 13)

Before you Begin
Digital News Production 11
Before you Begin
Please read the following notes before beginning the upgrade process.
Open SAN Systems Only
• Before creating a NewsShare environment, you first need to install and
configure an Open SAN system (MAN).
• Many Open SAN components, particularly the CentraVision File System
(CVFS), require all clients and servers to use fixed IP addresses. If your
network uses a DHCP server, you must create address reservations or a fixed
address subnet.
Complete IP connectivity must exist between all FSMs, Profile Media Servers,
and NewsShare workstations for a particular Open SAN. You may find it
convenient to assign all machines on an Open SAN to the same Workgroup. For
secure configurations, domain membership is necessary as discussed in the
document,
Open SAN Security Instruction Guide .
• A Profile Media Server’s Fibre Channel switch cannot handle both SCSI and
IP interfaces. For a NewsShare workstation to work with shared storage, you
must configure one Fibre Channel fabric for SCSI and one for IP.
• An Open SAN cluster is comprised of FSMs, Profile Media Servers, NewsEdit
workstations, and ContentShare Open SAN Servers that share a common
volume. You must use a common-prefix convention (e.g.,
prefix_machine) to
name each machine within a cluster; NewsEdit uses these prefixes to determine
if files can be accessed within the local cluster or whether a stream exchange to
another cluster is necessary.
For example, you could identify one Open SAN cluster as OSAN1; you would
then use that prefix to name all machines in that cluster — a Profile Media
Server could be OSAN1_PRO1 and a NewsEdit workstation could be
OSAN1_EDIT1. Machines in a different Open SAN cluster require a different
prefix (such as OSAN2).
• Note the naming convention that must apply to common-cluster Profile,
DNP, and ContentShare Open SAN Broker machines (the
OPENSAN_MACHINE morphology) in order for winking (shallow copy)
of shared files to work. Without this, send commands will deep-copy
through GXF video networking paths or fail completely if no GXF is
available. The naming convention does not apply to FSMs, which we