Grass Valley GV STRATUS Installation v.3.1 - Manual (Page 174)

Additional information Task flow context and policies Operation
— Rename first in SiteConfig. Then rename in
K2Config. Do not import\merge into SiteConfig
or K2Config. Rename Site\SAN
— Remove first in SiteConfig. Then remove in
K2Config. Do not import\merge into SiteConfig
or K2Config. Remove Site\SAN
— Remove from both SiteConfig and K2Config. Remove device
— Add in SiteConfig first, do network
configuration and software deployment. Then,
add in K2Config and configure using K2Config. Add device
— Use SiteConfig to create site, add devices,
configure network and deploy software, then
import into K2Config and configure each device Create a new site\SAN
— Perform hostname change using SiteConfig.
Remove and re-add to K2Config. If changing
the hostname of a media file system/metadata
K2 Media Server, re-configure all clients on the
K2 SAN using K2Config Change hostname
— Use SiteConfig for IP address changes. Then in
K2Config, click on the changed device's
network configuration node. This refreshes the
K2Config view of IPs from the device. Change IP address (except
address of TOE on K2
Media Server)
— For TOE IP changes and/or TOE card removal,
use K2Config. Change IP address of TOE
on K2 Media Server
— Use SiteConfig to recreate the site using the
appropriate redundancy models and configure
network and deploy software. Remove K2 SAN
from K2Config. Import site into K2Config.
Configure using K2Config. Modify K2 SAN
redundancy - redundant to
non-redundant or vice
versa
About Control Panel, SiteConfig, and K2Config settings
During system commissioning or system reconfiguration, the SiteConfig and K2Config applications
are first used to set up or modify K2 SAN and network configurations. The GV STRATUS Control
Panel application is then used to complete the setup of the GV STRATUS system-wide workflow
components.
The GV STRATUS Control Panel application imports the configuration information and populates
the GV STRATUS view of the available K2 systems. For example, information about K2 SANs
comes from K2Config while information about standalone K2 Summit systems comes from
SiteConfig. The information transfer is uni-directional, where the GV STRATUS Control Panel
application imports the SiteConfig/K2Config generated configurations.
174 GV STRATUS Installation and Service Manual 2013 12 19
Understanding system concepts