Grass Valley K2 System Guide v.9.0 - Manual (Page 142)

About managing stand-alone K2 clients with SiteConfig
The topics in this section apply to the following K2 client products:
• K2 Summit Production Client with internal storage
• K2 Summit Production Client with direct-connect storage
Work through the topics sequentially to get SiteConfig set up to remotely configure and manage
one or more K2 clients. Then you can use SiteConfig for software upgrades and other management
tasks.
SiteConfig and stand-alone K2 clients checklist
Use the following sequence of tasks as a guideline to set up SiteConfig and do your initial
configuration for one or more stand-alone K2 clients. This checklist outlines the recommended
workflow for a new system.
Comment Task
Review system requirements and network
access requirements about installing
SiteConfig. Select a PC to use as the SiteConfig control
point PC
— Install SiteConfig on the control point PC
If you already have a SiteConfig system
description managing other devices in your
facility, you can use that system description
also for your stand-alone K2 clients, rather
than creating a new system description. Create a system description and add a custom
site to the system description
— Add a control network to the site. You can
also add a FTP/streaming network if desired
— Add a group for your K2 clients to the system
description
— Add a placeholder K2 client to the system
description for each of your actual K2 clients
— Configure the names of the placeholder K2
clients
Specify IP address ranges and other network
details Configure the network interfaces of the
placeholder K2 clients
— Discover your K2 clients
— Assign each discovered K2 client to its
placeholder K2 client
On each K2 client, set the control network
interface IP address first, then the
FTP/streaming network interface, if present.
Also set the hostname. For each discovered and assigned K2 client,
edit each network interface. Specify network
settings and apply them to the K2 client.
142 K2 System Guide 06 November 2012
Managing stand-alone K2 systems with SiteConfig