The K2 Media Server restarts. This restart is required.
9. On the K2 Media Server, to enable port range limits for passive transfers, create
the following two DWORDs in the registry at
HKEY_LOCAL_MACHINE/SOFTWARE/Grass Valley Group/Streaming/:
•
FtpPasvStart (starting port number, inclusive : DWORD)
•
FtpPasvEnd (ending port number, inclusive : DWORD)
10. Open MediaFrame Con
fi
guration and for the News MDI, con
fi
gure the transfer
server to the K2 Media Server that is your K2-Aurora FTP server.
Distribute devices into deployment groups
You can gather devices of different types into a SiteCon
fi
g deployment group. This
allows you to deploy software to all the devices in the deployment group at the same
time, as part of the same deployment session. Based on the roles you have assigned
to the devices, SiteCon
fi
g deploys the proper software to each device. This increases
the ef
fi
ciency of your software deployment with SiteCon
fi
g.
If you have not already done so, con
fi
gure your deployment groups. The recommended
deployment group distribution is as follows. Depending on your system design, your
system might not have all the device types listed.
•
In a deployment group named "Aurora_Edit_Ingest_Playout", place the following
devices:
•
Aurora Edit workstation of any storage options: Shared storage, NAS storage,
and stand-alone.
•
Aurora Edit LD computer
•
DSM
•
Conform Server
•
SmartBin Server
•
FTP Server
•
Aurora Ingest Platform
•
IEP
•
Aurora Playout Platform
•
In a deployment group named "Aurora_Browse_MediaFrame", place the following
devices:
•
MediaFrame server
•
MDI server
•
Aurora Proxy Encoder
•
K2 Basecamp Express
•
If you have a K2 Nearline SAN (NAS), in a deployment group named for the SAN
system, place the following devices:
•
The Nearline SAN's K2 Media Servers.
18 October 2010
Aurora Edit and Edit LD Version 7.1.0 Release Notes and Upgrade Instructions
29
Upgrading Aurora Edit and Aurora Edit LD systems
